Bug 435641 - ConsoleKit forgets sessions when restarted
ConsoleKit forgets sessions when restarted
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: ConsoleKit (Show other bugs)
8
All Linux
medium Severity high
: ---
: ---
Assigned To: jmccann
Fedora Extras Quality Assurance
:
Depends On:
Blocks: 435642
  Show dependency treegraph
 
Reported: 2008-03-02 16:41 EST by Nils Philippsen
Modified: 2015-01-14 18:20 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-02 21:09:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nils Philippsen 2008-03-02 16:41:50 EST
Description of problem:

When restarting ConsoleKit, for instance if a new version is available,
ConsoleKit seems to forget about the current sessions which makes subsequent
actions which need privileges fail.

Version-Release number of selected component (if applicable):
ConsoleKit-0.2.3-3.fc8.1

How reproducible:
Reproducible

Steps to Reproduce:
1. Login
2. "ck-list-sessions"
3. "service ConsoleKit restart"
4. "ck-list-sessions"
  
Actual results:
nils@wombat:~> ck-list-sessions 
nils@wombat:~> 

Expected results:
List of sessions, in this case there would have been two active X11 sessions

Additional info:
When this is solved, ConsoleKit should probably "service ConsoleKit condrestart"
when updated to ensure that e.g. security fixes are active after the update is
finished.
Comment 1 David Zeuthen 2008-03-02 21:09:15 EST
No, it's a bug to restart ConsoleKit daemon. And it's not possible either,
there's no initscript anymore in Rawhide at least. See bug 435642 for why.
Comment 2 David Zeuthen 2008-03-02 21:16:42 EST
(In reply to comment #1)
> No, it's a bug to restart ConsoleKit daemon. And it's not possible either,
> there's no initscript anymore in Rawhide at least. See bug 435642 for why.

(of course sending it SIGUSR1, SIGUSR2 is always possible etc. etc.. But from
where I'm sitting it's (currently) pointless to teach CK the same dance that
init does; e.g. reloading and passing state to the new process. Of course it's
up to Jon if he wants to add such a feature later on. We have bigger fish to fry
right now.)

Note You need to log in before you can comment on or make changes to this bug.