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 53 - restart a kde session with Synaptic running, disconnects KdeSudo
Summary: restart a kde session with Synaptic running, disconnects KdeSudo
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdeadmin (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: i386 Linux
: P5 minor
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2009-03-12 11:53 CDT by James
Modified: 2018-05-27 11:11 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James 2009-03-12 11:53:17 CDT 
When restarting a kde session with running applications, if restarting the Synaptic Package Manager, which had been originally started from a panel button with the command ¨synaptic¨, then two popup windows appear:

 Starting without administrative privileges

and

 Information - KdeSudo
 No command arguments supplied!

There seems to have been a disconnection somewhere in the restart...
Comment 1 Darrell 2013-05-22 23:44:35 CDT 
Is this report still valid?
Comment 2 James 2013-06-03 18:20:06 CDT 
Hmm - I don't have synaptic right now, running Arch and Trinity from about 2012 August.  I tried this with the Login Manager running, and the Login Manager did not restart with the new session.  I tried this with the Font Installer running, and the Session Manager crashed when I tried to log-out.  I tried this with the Monitor and Display app, but it could not recognize my multiple monitors and the KDE Control Module crashed with SIGSEGV when I clicked the "OK" button.

I tried this with the Date and Time app.  I got the "saving settings" window, and then the display background went black with just the Date and Time module still running.  The session never went back to the display manager, "kdm" in this case.  When I restarted the display manager, with systemd, there were many many instances of artsd still running, which would not respond to SIGTERM, and I had to kill with SIGKILL.

So generally, yes, I'd say there are still problems with trying to close a Trinity session with any of these "administrative mode" apps still running.  That they all respond differently to ending the session suggests that there is no uniform approach to this not usual circumstance - closing a Trinity session with an administrative-mode app still running.  Not a "show stopper", but still, a little "buggy".

Perhaps the default approach should be as with the Login Manager - to simply terminate the app when the session ends, and not restart when the session restarts.  Certainly, nothing should crash when the session ends, and the session should close cleanly.  In a "perfect world", I would otherwise expect the apps to restart, but should they actually re-start "enabled" with the root password?  Probably not.

With synaptic, at least there is the message "Starting without administrative privileges", and it is just KdeSudo which complains, but perhaps should not.


James
Comment 3 Timothy Pearson 2014-10-08 12:53:08 CDT 
When I tested this with R14 sources any tdecontrol modules loaded with administrative privileges did not crash on logout and were not restarted on next login, which is as expected.

That leaves Synaptic.  Synaptic saves itself with the legacy session management code, thus it is difficult to determine the effective UID of the process.  If a reliable method can be found to do this I should be able to prevent automatic startup of root-privileged applications, which should resolve this report.

The affected code is in tdebase/ksmserver/legacy.cpp in KSMServer::storeLegacySession.