[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

suidregister problems after dist-upgrade today



I got the following errors after a apt-get dist-upgrade today.
apt-get failed on setting up, so I ran dpkg --configure --pending to fix the
remaining packages.  Below is the output.

tsuess:~# dpkg --configure --pending
Setting up eterm (0.8.10-7) ...
Checking available versions of eterm-pixmaps, updating links in /etc/alternatives ...
(You may modify the symlinks there yourself if desired - see `man ln'.)
Automatic updates of /etc/alternatives/eterm-pixmaps are disabled, leaving it alone.
To return to automatic updates use `update-alternatives --auto eterm-pixmaps'.
Checking available versions of x-terminal-emulator, updating links in /etc/alternatives ...
(You may modify the symlinks there yourself if desired - see `man ln'.)
Leaving x-terminal-emulator (/usr/bin/x-terminal-emulator) pointing to /usr/bin/X11/xterm.
Leaving x-terminal-emulator.1.gz (/usr/share/man/man1/x-terminal-emulator.1.gz) pointing to /usr/X11R6/man/man1/xterm.1x.gz.
Global symbol "$username" requires explicit package name at /usr/sbin/suidregister line 173.
Global symbol "$groupname" requires explicit package name at /usr/sbin/suidregister line 174.
Global symbol "$inode" requires explicit package name at /usr/sbin/suidregister line 178.
Execution of /usr/sbin/suidregister aborted due to compilation errors.
dpkg: error processing eterm (--configure):
 subprocess post-installation script returned error exit status 255
Setting up xscreensaver (3.22-2) ...
Global symbol "$username" requires explicit package name at /usr/sbin/suidregister line 173.
Global symbol "$groupname" requires explicit package name at /usr/sbin/suidregister line 174.
Global symbol "$inode" requires explicit package name at /usr/sbin/suidregister line 178.
Execution of /usr/sbin/suidregister aborted due to compilation errors.
dpkg: error processing xscreensaver (--configure):
 subprocess post-installation script returned error exit status 255
Errors were encountered while processing:
 eterm
 xscreensaver
tsuess:~#  

If anyone has any idea what the problem might be, and/or how to fix it, please
let me know.    Thanks!

Todd


Reply to: