> On 13 October 2010 18:14, Timothy Pearson <kb9vqf@...> > wrote: >>> Firstly my thanks and congratulations to the Trinity project for such >>> great work and the support for Debian. It is my desktop of choice for >>> Debian Squeeze and looks really nice, more so than the (old) kde >>> defaults. In fact I have run Trinity (ubuntu packsges) on Debian >>> Squeeze since last November. It idles at around 100MB ram usage. >>> >>> I now have a fresh Squeeze install with Trinity from the new >>> Trinity-Debian repos. This was done using debootstrap and chroot. >>> Trinity-kde was installed with apt-get (in the chroot) using a text >>> list of specific packages. I use these methods to minimise bloat. >>> >>> The only issue is, kdesu. I saw an earlier post on this but no >>> resolution. Is nobody else getting this? >>> >>> I can't change the clock or get root from kcontrol, kuser, etc. The >>> workaround is sudo or sux (/opt/trinity/bin needs to go in roots >>> $PATH) in a konsole to open kde apps >>> >>> I do not like to use sudo by preference but in this case I have set my >>> user in /etc/sudoers. (works as expected otherwise, e.g. <sudo kwrite> >>> is successful) >>> >>> Ideally I would like to disable sudo altogether and just use su, sux >>> and >>> kdesu. >>> >>> kdesudo-trinity is installed. >>> >>> In my old Squeeze install I fixed kdesu by adding a text file >>> ~/.kde3/share/config/kdesurc containing: >>> >>> [super-user-command] >>> super-user-command=su >>> >>> No luck with that on the new install >>> >>> In konsole: >>> >>> dzz@exelinux:~$ kdesudo kwrite >>> /usr/bin/xauth: (argv):1: couldn't query Security extension on display >>> ":0.0" >>> No protocol specified >>> >>> kwrite: cannot connect to X server :0.0 >>> >>> dzz@exelinux:~$ kdesu kwrite >>> /usr/bin/xauth: (argv):1: couldn't query Security extension on display >>> ":0.0" >>> No protocol specified >>> >>> kwrite: cannot connect to X server :0.0 >>> >>> >>> >>> . Any ideas what is wrong? >>> >> >> I do not know of a workaround at this point, but here is some additional >> information I found: >> >> http://crunchbanglinux.org/forums/topic/9786/how-to-run-gui-apps-with-another-user/ >> >> Can you post the output of: >> >> ls -l /opt/trinity/bin/kdesu >> >> Thanks! >> >> Tim >> >> > > > dzz@exelinux:~$ ls -l /opt/trinity/bin/kdesu > -rwxr-xr-x 1 root root 45912 Oct 2 22:33 /opt/trinity/bin/kdesu > > Thanks for the link but not much of a solution there, I already use > sux mostly as a workaround. Trinity-kde is good enough generally that > I can live with thatfor now. > > i'm doing quite a bit of testing at the moment, building a live cd. > Nearly there, just a few minor cosmetic glitches. > OK, I have a workaround: deinstall kdesudo-trinity Yes, it seems odd. However, kdesu is provided by kdelibs, and functions correctly under Debian. kdesudo is an addon program, and functions correctly under Ubuntu, but not Debian. I think this has something to do with the X server as mentioned in the link I posted earlier, but I am not sure. I do know that the same problem with kdesudo is also present (sporadically) on KDE4 up to version 4.2, and possibly even after that. Hope this helps! Tim