By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 451

Summary:	Problems with DCOP after using kdesu (Debian Squeeze)
Product:	TDE	Reporter:	David Hare <dzfixes-box1>
Component:	tdelibs	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	bugwatch, darrella
Priority:	P5
Version:	3.5.12 [Trinity]
Hardware:	i386
OS:	Debian Squeeze
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description David Hare 2011-03-03 18:22:29 CST

In reference to http://bugs.pearsoncomputing.net/show_bug.cgi?id=394

This also affects Trinity 3.5.12 in Debian Squeeze

After using kdesu to open any Trinity app as root using a panel shortcut returns an error dialog box :

KLauncher could not be reached via DCOP

Nothing at all works from the main menu.

It is then necessary to issue 'kdeinit' in a terminal (possible only if one is already open) or relogin to return to normal.

Workarounds are possible, as posted in the mailing lists.

Ubuntu-style sudo should not be an enforced default on a Debian system (kdesudo-trinity does work) It is either not used or is set up only by specific user action. 

This behaviour is observed in Trinity/Squeeze installations here on 3 different machines

Comment 1 Darrell 2011-05-04 16:32:10 CDT

Probably a duplicate of Bugs 393 and 394.

I agree that Ubuntu-style sudo should not be an enforced default on other systems.

Comment 2 David Hare 2011-05-05 07:19:35 CDT

Bugs 393 and 394 are similar, However they relate specifically to Slackware so a new one was filed.

Surprising, with more Debian users around now, almost nobody has taken an interest in this even though an interim workaround was posted in the mailing list.

Comment 3 Darrell 2011-05-05 14:47:40 CDT

Understood. I added the reference to Bugs 393 and 394 so the person resolving the reports can look at all of them concurrently. I'm guessing that all of the related bugs can be solved together.

The problem is not interest in solving the bugs, but the transition to cmake. Testing any patches is difficult because many people cannot yet build the basic packages. When the cmake transition settles then more people can build packages and bug patching and testing will resume.

This is a somewhat frustrating period for users as everybody must wait until the cmake conversion is complete. :)

Would you provide links to the workaround solutions?

Comment 4 David Hare 2011-05-08 20:31:15 CDT

I do not know how to link a specific post in a mailing list nor a topic in a no-longer-accessible forum.

I know *** all abut cmake. An official solution, for users who do not want default sudo. would be superb. 

This has worked consistently here but is a personal solution. 

1. Purge kdesudo-trinity

2. Edit every menu entry requiring root (e.g. kuser) like this:
kdesu kuser --nonewdcop
Uncheck "run as different user"

3. Create file ~/.trinity/share/config/kdesurc with this text :

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

MAYBE needed in ~/.bashrc :
export XAUTHORITY=$HOME/.Xauthority

Comment 5 Timothy Pearson 2011-10-26 14:03:27 CDT


*** This bug has been marked as a duplicate of bug 394 ***