| 1 |
Mick, |
| 2 |
|
| 3 |
On Thursday, 2019-12-19 18:30:47 +0000, you wrote: |
| 4 |
|
| 5 |
> ... |
| 6 |
> consolekit will work for this purpose - is it running? It should be in your |
| 7 |
> default runlevel. |
| 8 |
|
| 9 |
$ rc-update show|grep consolekit |
| 10 |
$ |
| 11 |
|
| 12 |
Gosh! It's missing! Maybe I just started it to see whether or not it |
| 13 |
works and then forgot to add it to default. So add and start it now: |
| 14 |
|
| 15 |
$ sudo rc-update add consolekit default |
| 16 |
Password: |
| 17 |
* service consolekit added to runlevel default |
| 18 |
$ sudo rc-service consolekit start |
| 19 |
* Caching service dependencies ... [ ok ] |
| 20 |
* Starting consolekit ... |
| 21 |
* start-stop-daemon: /usr/sbin/console-kit-daemon is already running |
| 22 |
* Failed to start consolekit [ !! ] |
| 23 |
* ERROR: consolekit failed to start |
| 24 |
$ ps -ef|grep console |
| 25 |
rainer 3928 12250 0 19:53 pts/0 00:00:00 grep console |
| 26 |
root 11675 1 0 Dec18 ? 00:00:00 /usr/sbin/console-kit-daemon --no-daemon |
| 27 |
$ |
| 28 |
|
| 29 |
So it's not in the default run-level, but it's running anyway? Whazzat? |
| 30 |
So I decided to reboot and see what happens. But this helped neither |
| 31 |
with automounting nor with hibernating. The only thing that changed was |
| 32 |
the command line of the console-kit command: |
| 33 |
|
| 34 |
$ ps -ef|grep console |
| 35 |
root 7320 1 0 Dec19 ? 00:00:00 /usr/sbin/console-kit-daemon |
| 36 |
rainer 32639 10242 0 12:21 pts/0 00:00:00 grep console |
| 37 |
$ |
| 38 |
|
| 39 |
By the way, these are its USE flags for consolekit, in case it matters: |
| 40 |
|
| 41 |
$ eix -l consolekit|grep Installed |
| 42 |
Installed versions: 1.2.1(15:11:46 22/10/19)(acl pam pm-utils policykit udev -cgroups -debug -doc -evdev -selinux -test KERNEL="linux") |
| 43 |
$ |
| 44 |
|
| 45 |
Sincerely, |
| 46 |
Rainer |
Archives