On 13 October 2010 18:14, Timothy Pearson kb9vqf@pearsoncomputing.net 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-anothe...

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.

Timothy Pearson wrote:

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

Just so you know, removing kdesudo-trinity does get kmenu "run as a different user" working, thanks. :-)

But at the same time my Squeeze install with kde4 has the kdesudo file installed and does not have the "run as a different user" problem. :-(

And something is going on that's causing a 15min sudo timeout, that is not the Debian Way, root passwd should be asked for each time elevated permissions are needed and something besides the sudoers file is causing this and I don't know what it is, what ever it is I want to kill it.

Just thought I'd let you know.

David Hare wrote:

Ok, getting somewhere now but still some odd behaviour. Purged kdesudo-trinity and disabled my user from /etc/sudoers.

~/trinity/share/config/kdesurc reads:

[Passwords] Keep=false

I have that.

[super-user-command] super-user-command=su

I know what that is.

Now, if I do, e.g. <kdesu kwrite> in konsole:

dzz@exelinux:~$ kdesu kwrite Error: "/tmp/kde-dzz" is owned by uid 1000 instead of uid 0. Error: "/tmp/ksocket-dzz" is owned by uid 1000 instead of uid 0. kdeinit: Shutting down running client. /usr/bin/iceauth: creating new authority file /root/.ICEauthority Error: "/tmp/ksocket-dzz" is owned by uid 1000 instead of uid 0. Error: "/tmp/kde-dzz" is owned by uid 1000 instead of uid 0. kbuildsycoca running... Error: "/var/tmp/kdecache-dzz" is owned by uid 1000 instead of uid 0. Error: "/tmp/kde-dzz" is owned by uid 1000 instead of uid 0. DCOP Cleaning up dead connections. Error: "/var/tmp/kdecache-dzz" is owned by uid 1000 instead of uid 0. Error: "/var/tmp/kdecache-dzz" is owned by uid 1000 instead of uid 0. Error: "/var/tmp/kdecache-dzz" is owned by uid 1000 instead of uid 0.

It opens but then I can't use kicker or the menu to open anything else, dcop server crashes:

"KLauncher could not be reached via DCOP"

If I then issue (as user) <kdeinit> everything then behaves normally for the rest of the session! The error reappears on next login though.

This is now consistent over numerous reboots/relogins and for a second user account also

Similar behaviour with sux

An annoyance but not a showstopper so far.

@Jimmy:

help:/kdesu/using-kdesu.html (in a konq window) might have a clue to the password retention issue, seems a kde thing (probably configurable)

Note my kdesurc

[Passwords] Keep=false

David, just so you know, I don't know what's going on, maybe if you get it figure out you can do a step-by-step rundown on the changes you made and the expected behavior !?! After more than 8 years using Debian I'm still just a point-n-click user. :-P

Thanks,

I have tested various workarounds for getting GUI stuff as root (without enabling sudo) for the past week. Some Debian users are not comfortable with sudo at all (especially if configured for root access without password) and prefer the root password to be required for administration.

I have now settled on a workable solution with Trinity.

Using:

kdesu <kdeapp> --nonewdcop

with the configs I posted earlier has not failed once. (must create file kdesurc and purge kdesudo-trinity)

It seems the user's dcop and/or klauncher crashes if/when root gets a new dcop. I don't know why, when I used sudo initially, that did not happen.

I edited the menu with a new "root apps" section (konq, kwrite, kuser) configured like that, with "run as different user" unchecked so can now use terminal, run box or menu.

Non-trinity, gtk apps (synaptic, gparted, zenity) I had problems with before seem fixed by adding to ~/.bashrc:

export XAUTHORITY=$HOME/.Xauthority

Needed reboot (or relogin) to register that. Don't know if that has security issues but it works.

I can now open, error-free, as root from terminal or via custom script with:

dbus-launch <gtk-app>

That will not work for trinity apps.

sux gives the same problem as kdesu without --nonewdcop; can't use that (for Trinity apps) now but never mind

Am 30.10.2010 01:09, schrieb Jimmy Johnson:

David Hare wrote:

...

I have tested various workarounds for getting GUI stuff as root (without enabling sudo) for the past week. Some Debian users are not comfortable with sudo at all (especially if configured for root access without password) and prefer the root password to be required for administration.

I have now settled on a workable solution with Trinity.

Using:

kdesu <kdeapp> --nonewdcop

with the configs I posted earlier has not failed once. (must create file kdesurc and purge kdesudo-trinity)

It seems the user's dcop and/or klauncher crashes if/when root gets a new dcop. I don't know why, when I used sudo initially, that did not happen.

I edited the menu with a new "root apps" section (konq, kwrite, kuser) configured like that, with "run as different user" unchecked so can now use terminal, run box or menu.

Non-trinity, gtk apps (synaptic, gparted, zenity) I had problems with before seem fixed by adding to ~/.bashrc:

export XAUTHORITY=$HOME/.Xauthority

Needed reboot (or relogin) to register that. Don't know if that has security issues but it works.

I can now open, error-free, as root from terminal or via custom script with:

dbus-launch <gtk-app>

That will not work for trinity apps.

sux gives the same problem as kdesu without --nonewdcop; can't use that (for Trinity apps) now but never mind

I now have a recipe too, of course I have only tested this with Squeeze and have been using it since yesterday and it seems to work perfect.

Using synaptic Install:

gksu gksu-polkit sudo

And completely Remove:

kdesudo kdesudo-trinity sudo-trinity

As "User" run 'gksu-properties' and change "su" to "sudo" and you will always be prompted for a password when you need elevated privileges.

At first it was a good idea. But there is no packet gksu-polkit in Debian Lenny. And when you will remove sudo-trinity he will remove also a many packets from trinity. So you have no change with this workaround under Debian Lenny, sorry. Best wishes bernd

Am 31.10.2010 06:57, schrieb Jimmy Johnson:

Bernd Müffeler wrote:

...

Am 30.10.2010 01:09, schrieb Jimmy Johnson:

...

David Hare wrote:

...

I have tested various workarounds for getting GUI stuff as root (without enabling sudo) for the past week. Some Debian users are not comfortable with sudo at all (especially if configured for root access without password) and prefer the root password to be required for administration.

I have now settled on a workable solution with Trinity.

Using:

kdesu <kdeapp> --nonewdcop

with the configs I posted earlier has not failed once. (must create file kdesurc and purge kdesudo-trinity)

It seems the user's dcop and/or klauncher crashes if/when root gets a new dcop. I don't know why, when I used sudo initially, that did not happen.

I edited the menu with a new "root apps" section (konq, kwrite, kuser) configured like that, with "run as different user" unchecked so can now use terminal, run box or menu.

Non-trinity, gtk apps (synaptic, gparted, zenity) I had problems with before seem fixed by adding to ~/.bashrc:

export XAUTHORITY=$HOME/.Xauthority

Needed reboot (or relogin) to register that. Don't know if that has security issues but it works.

I can now open, error-free, as root from terminal or via custom script with:

dbus-launch <gtk-app>

That will not work for trinity apps.

sux gives the same problem as kdesu without --nonewdcop; can't use that (for Trinity apps) now but never mind

I now have a recipe too, of course I have only tested this with Squeeze and have been using it since yesterday and it seems to work perfect.

Using synaptic Install:

gksu gksu-polkit sudo

And completely Remove:

kdesudo kdesudo-trinity sudo-trinity

As "User" run 'gksu-properties' and change "su" to "sudo" and you will always be prompted for a password when you need elevated privileges.

At first it was a good idea. But there is no packet gksu-polkit in Debian Lenny.

No, but 'gksu-properties' still works, just not as expected.

...

And when you will remove sudo-trinity he will remove also a many packets from trinity.

Installing sudo will remove sudo-trinity, but things in Lenny are not working as expected.

...

So you have no change with this workaround under Debian Lenny, sorry. Best wishes bernd

I just now installed Lenny with trinity and I will see what I can do, right now nothing is working as expected. :-(

Thanks for the answer, I hope you will find a solution. I love the trinity project and I will work with this KDE. Best wishes bernd

Am 31.10.2010 22:53, schrieb Jimmy Johnson:

Bernd Müffeler wrote:

...

Am 31.10.2010 06:57, schrieb Jimmy Johnson:

...

Bernd Müffeler wrote:

...

Am 30.10.2010 01:09, schrieb Jimmy Johnson:

...

David Hare wrote:

...

I have tested various workarounds for getting GUI stuff as root (without enabling sudo) for the past week. Some Debian users are not comfortable with sudo at all (especially if configured for root access without password) and prefer the root password to be required for administration.

I have now settled on a workable solution with Trinity.

Using:

kdesu <kdeapp> --nonewdcop

with the configs I posted earlier has not failed once. (must create file kdesurc and purge kdesudo-trinity)

It seems the user's dcop and/or klauncher crashes if/when root gets a new dcop. I don't know why, when I used sudo initially, that did not happen.

I edited the menu with a new "root apps" section (konq, kwrite, kuser) configured like that, with "run as different user" unchecked so can now use terminal, run box or menu.

Non-trinity, gtk apps (synaptic, gparted, zenity) I had problems with before seem fixed by adding to ~/.bashrc:

export XAUTHORITY=$HOME/.Xauthority

Needed reboot (or relogin) to register that. Don't know if that has security issues but it works.

I can now open, error-free, as root from terminal or via custom script with:

dbus-launch <gtk-app>

That will not work for trinity apps.

sux gives the same problem as kdesu without --nonewdcop; can't use that (for Trinity apps) now but never mind

I now have a recipe too, of course I have only tested this with Squeeze and have been using it since yesterday and it seems to work perfect.

Using synaptic Install:

gksu gksu-polkit sudo

And completely Remove:

kdesudo kdesudo-trinity sudo-trinity

As "User" run 'gksu-properties' and change "su" to "sudo" and you will always be prompted for a password when you need elevated privileges.

At first it was a good idea. But there is no packet gksu-polkit in Debian Lenny.

No, but 'gksu-properties' still works, just not as expected.

...

And when you will remove sudo-trinity he will remove also a many packets from trinity.

Installing sudo will remove sudo-trinity, but things in Lenny are not working as expected.

...

So you have no change with this workaround under Debian Lenny, sorry. Best wishes bernd

I just now installed Lenny with trinity and I will see what I can do, right now nothing is working as expected. :-(

Thanks for the answer, I hope you will find a solution. I love the trinity project and I will work with this KDE. Best wishes bernd

Sorry I got your hopes up, but I deleted trinity on Lenny last night, it should just work but it don't and it's to easy to install KDE 3.5.10 to try and fix trinity. I think it's a lot more important to have trinity working on Squeeze anyways.

Regards,

Sorry for the late answer. I cant work with trinity on Squeeze. I have many problems with my hardware on Squeeze. Ok I work with trinity on Lenny with the end for Lenny, and when I work as root I went to console and work with the midnightcommander. KDE 4 is no way for me and so I work with trinity. also thanks for your help and best wishes bernd