| Summary: | sys-apps/openrc-0.9.8.4 fails to correctly start sys-auth/consolekit-0.4.5-r1 | ||
|---|---|---|---|
| Product: | Gentoo Hosted Projects | Reporter: | Sergey S. Starikoff <Ikonta> |
| Component: | OpenRC | Assignee: | OpenRC Team <openrc> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | freedesktop-bugs |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Sergey S. Starikoff
2012-02-22 16:00:15 UTC
Today I've discovered that consolekit (removed from auto-start, waiting start as a dependency) totally failes to start: # /etc/init.d/consolekit status * status: stopped # /etc/init.d/consolekit start * Starting ConsoleKit daemon ... * start-stop-daemon: /usr/sbin/console-kit-daemon is already running [ !! ] * ERROR: consolekit failed to start Error looks very similiar with described in bug #396173 The difference is in that apache soon comes into startable state, with consolekit I've failes to do it. Is this still an issue with openrc-0.9.9.2? I an closing this due to no response from reporter. Please re-open if this is still an issue with the latest OpenRC. (In reply to comment #2) > Is this still an issue with openrc-0.9.9.2? Excuse me for long timeount on response. It's my home PC, turned on rather rarely. Resume: 1. consolekit fails to start (even manually) if not listed an auto-start list (i.e. rc-update show); 2. Power management and granting mount privileges (managed by policy kit, with correct rules) works fine independently on status of consolekit daemon (works even if daemon is not started). 3. With sys-apps/openrc-0.9.9.3 the issue was reproduced. I don't think this bug has enough information to be processed. The reporter will need to do some more debugging on his own. Maybe this is a duplicate of bug 369811 ? (In reply to comment #5) > I don't think this bug has enough information to be processed. > The reporter will need to do some more debugging on his own. Excude for long response. sys-apps/openrc-0.11.8, similiar issue: # rc-update show | grep consolekit (not listed) # /etc/init.d/consolekit status * status: stopped # /etc/init.d/consolekit start * Starting ConsoleKit daemon ... * start-stop-daemon: /usr/sbin/console-kit-daemon is already running [ !! ] * ERROR: consolekit failed to start But: # ps ax | grep console-kit 2775 ? Sl 0:00 /usr/sbin/console-kit-daemon --no-daemon 4498 pts/0 S+ 0:00 grep --colour=auto console-kit (process is listed) So, personal init script for consolekit seems to be optional item and could be removed. In about week or two I can see my another Gentoo installation, where consolekit is autostarted, for some additional info. (In reply to comment #6) > Maybe this is a duplicate of bug 369811 ? Not exact. (In reply to comment #7) > (In reply to comment #5) > > I don't think this bug has enough information to be processed. > > The reporter will need to do some more debugging on his own. > > Excude for long response. > > sys-apps/openrc-0.11.8, similiar issue: > # rc-update show | grep consolekit > (not listed) > > # /etc/init.d/consolekit status > * status: stopped > # /etc/init.d/consolekit start > * Starting ConsoleKit daemon ... > * start-stop-daemon: /usr/sbin/console-kit-daemon is already running > [ !! ] > * ERROR: consolekit failed to start > > But: > # ps ax | grep console-kit > 2775 ? Sl 0:00 /usr/sbin/console-kit-daemon --no-daemon > 4498 pts/0 S+ 0:00 grep --colour=auto console-kit > (process is listed) > > So, personal init script for consolekit seems to be optional item and could > be removed. init script is the only way to ensure it starts early enough for other services, leaving it for the display manager and/or desktop will only result failures as some of the started services won't be included in the consolekit session the behavior is undefined, might work for some, propably fails for most still nothing to go on with in this bug :/ |
