Custom Query (1145 matches)
Results (151 - 153 of 1145)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#168 | fixed | busyd doesn't work | rbasch | jdreed |
Description |
Debathena machines don't respond to udp/49154 packets correctly. Querying an Athena 9 machine: $ nc -u w20-575-37 49154 <CR> 1w20-575-37.mit.edui686 C $ Querying an Athena 10 machine: $ nc -u w20-575-37 49154 <CR> (no output) C $ |
|||
#627 | fixed | byobu postinst interacts poorly with NSS_NONLOCAL_IGNORE | broder | |
Description |
Debathena wraps dpkg to set NSS_NONLOCAL_IGNORE=ignore (so that when dpkg tries to create new local system users, they don't conflict with Hesiod users): From /usr/bin/dpkg.debathena: #!/bin/sh export NSS_NONLOCAL_IGNORE=ignore /usr/bin/dpkg.debathena-orig "$@" byobu attempts to trigger a profile reload on upgrade by trying to create a file for each user with an active screen session: From /var/lib/dpkg/info/byobu.postinst: # Notify users that they should reload their profile DIR="/var/run/screen" if [ -d "$DIR" ]; then for d in "$DIR"/*; do [ -d "$d" ] || continue touch "$d/$PKG.reload-required" u=$(echo "$d" | sed "s:^.*/S-::") chown $u "$d/$PKG.reload-required" chmod 700 "$d/$PKG.reload-required" done fi Unfortunately, because NSS_NONLOCAL_IGNORE means that non-local users don't exist, the byobu postinst attempts to chown files to nonexistant users: Processing triggers for libc-bin ... ldconfig deferred processing now taking place Errors were encountered while processing: byobu E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up byobu (2.68-0ubuntu1.1) ... chown: invalid user: `geofft' dpkg: error processing byobu (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: byobu Reading package lists... Done |
|||
#310 | fixed | Can't log in graphically if quota is exceeded | broder | quentin |
Description |
I just observed a user who wasn't able to log in because he had exceeded his quota; he got as far as the zenity dialog telling him his quota was exceeded, and then the login session completely hung when he pressed the OK button in the dialog. The zenity window hung with the button depressed, and the login didn't continue. I had to walk him through sshing in from another machine to delete some files; that's not something that the average user is expected to be able to do. |