| 1 |
Doug Goldstein <cardoe@g.o> posted |
| 2 |
eafa4c130903191112t50cef619l1a2eeb8c45898e7b@××××××××××.com, excerpted |
| 3 |
below, on Thu, 19 Mar 2009 13:12:15 -0500: |
| 4 |
|
| 5 |
> Unless someone has some better ideas for a reasonable default. (IMHO, |
| 6 |
> removing all of PolicyKit is a reasonable default but it looks like |
| 7 |
> going forward GNOME is just using it without really any documentation or |
| 8 |
> any forethought into the real world implications of PolicyKit and the |
| 9 |
> inherent support/issues with ConsoleKit) |
| 10 |
|
| 11 |
Just asking, can the following be made to avoid #4 in the following |
| 12 |
sequence with policykit, now? It used to be a terrible issue with |
| 13 |
consolekit or whatever it was called. Or is that still one of the |
| 14 |
problems? |
| 15 |
|
| 16 |
1. Boot to a VT. |
| 17 |
2. Login at VT. |
| 18 |
3. startx by sourcing a script that logs out of the VT after the startx, |
| 19 |
as that login is now unneeded. |
| 20 |
4. Have sound and various other device permissions break as there's no |
| 21 |
active login, despite X and all its apps otherwise running normally. |
| 22 |
|
| 23 |
-- |
| 24 |
Duncan - List replies preferred. No HTML msgs. |
| 25 |
"Every nonfree program has a lord, a master -- |
| 26 |
and if you use the program, he is your master." Richard Stallman |
Archives