reassign 328479 kdm On 15.09.05 17:51:15, Thomas Dickey wrote: > On Thu, Sep 15, 2005 at 10:49:25PM +0200, Andreas Pakulat wrote: > > > For the same reason, (or perhaps they're using old-style pty's) several > > > other programs (I see Eterm, aterm, rxvt) are setuid. gnome-terminal > > > and konsole aren't (but they're end-user applications designed to be run > > > in sessions - though google hints that they might want to write to utmp > > > - I see many bug reports ;-) > > > > I actually am using konsole and I don't have this variable in my > > export-list. Is there any way for me to find out who unsets the variable > > (i.e. which program is setuid)? Because I think some kde program does > > that - either kdm or something during kde startup. If I use > > xfce4-terminal (which isn't setuid) with startx I have my > > LD_LIBRARY_PATH. > > I'm not sure - konsole involves a lot of programs when it starts up.
With "Try and Error" I found that it actually is kdm, a startx /usr/bin/konsole works as well as startx /usr/bin/startkde > > If there's no easy way to do this, I guess I have to move the bug over > > to kdm and take it from there... > > That sounds right. Done (I hope)... > > PS: Can it be, that this only happens with the "new" libc? Because I > > know for sure that some time back (maybe even half a year..) it worked. > > no - this has been (with xterm anyway) an issue for 4-5 years. If xterm's > not setuid, it'll still work except for the utmp feature. I usually test > xterm during development without setuid. Occasionally I see some comment > regarding systems where the setuid's been removed, etc. Perhaps you were > using one of those. Then I guess it was introduced with KDE 3.4. To the KDE Maintainers: Please note that I currently still run the "old" experimental KDE 3.4.1 and 3.4.0 (from alioth) packages, because I don't have high-bandwidth-access until Friday afternoon (CET), so if this issue is fixed in kdm 3.4.2 please feel free to close the bug. Andreas -- Make a wish, it might come true. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]