You are not logged in.
I've just about got everything sorted out now after the upgrade to gnome 2.24 but I'm still getting a few errors and warnings when I start/shutdown and wondered whether there are any easy fixes before I start posting bug reports.
On startup:
Oct 25 09:53:23 bonobo-activation-server (david-6475): could not associate with desktop session: Failed to connect to socket /tmp/dbus-4DCzwZ4GTH: Connection refused
Oct 25 09:53:47 darkstar gnome-session[6510]: WARNING: Application 'libcanberra-login-sound.desktop' failed to register before timeout
Oct 25 09:59:26 bonobo-activation-server (david-7070): could not associate with desktop session: Failed to connect to socket /tmp/dbus-C1a5A6WFBC: Connection refused
Oct 25 09:59:51 darkstar gnome-session[7105]: WARNING: Application 'libcanberra-login-sound.desktop' failed to register before timeout
On shutdown:
Oct 25 00:12:33 darkstar gnome-session[4241]: WARNING: Running '/usr/bin/gconftool-2 --shutdown' at logout returned an exit status of '15'
An exit status of '15' is GCONF_ERROR_NO_WRITABLE_DATABASE, i.e. nowhere to write a value. Running /usr/bin/gconftool-2 --shutdown from the console stops gconfd-2 without any errors, so I guess that something is happening out of order at shutdown.
Offline
error: cannot resolve "gnome-menus>=2.24.1", a dependency of "gnome-panel"
error: failed to prepare transaction (could not satisfy dependencies)
:: gnome-panel: requires gnome-menus>=2.24.1
http://ispconfig.lt - ISPConfig 3 based hosting. Coming Soon!
Offline
error: cannot resolve "gnome-menus>=2.24.1", a dependency of "gnome-panel" error: failed to prepare transaction (could not satisfy dependencies) :: gnome-panel: requires gnome-menus>=2.24.1
Without looking, I suspect that you need to wait for the mirror you are using to update completely.
Last edited by azleifel (2008-10-25 21:45:15)
Offline
Well, my bonobo-activation-server/dbus and gconftool-2 problems were down to PolicyKit and went away after adding
<match user="david">
<return result="yes"/>
</match>
and, to get polkit-gnome-authorization to work fully with sudo and no root password (I use the wheel group to grant sudo privileges),
<define_admin_auth group="wheel"/>
to /etc/PolicyKit/PolicyKit.conf
Offline
Without looking, I suspect that you need to wait for the mirror you are using to update completely.
Now it's working
http://ispconfig.lt - ISPConfig 3 based hosting. Coming Soon!
Offline
I think your disabled root account is the source of all your problems. I've read reports on the forums about user accounts that couldn't get created because the root account is disabled or expired. When the policykit user and group are not created correctly, you'll run into these weird problems.
About the extra policykit configuration "needed": Why don't you run your desktop as root instead, granting all permissions to an account has the same effects as making every binary setuid root that hooks into policykit.
Offline
I looked and I already had:
policykit:x:1005:
in /etc/group and
policykit:x:102:1005:PolicyKit:/:/sbin/nologin
in /etc/passwd. These entries both seem to be consistent with the actions in the policykit package's install script. There was nothing in /etc/PolicyKit/PolicyKit.conf but the template structure before I started editing it.
If I wanted to have a whinge then I would say that, as a home user running Linux on his home PC, I have little or no need for something like PolicyKit and it's perhaps a bit worrying that I'm getting close to running Linux in administrator mode, much like I used to do when running Windows XP.
EDIT: After reading a little more of the PolicyKit documentation and also taking a peek at what Ubuntu includes in its policykit deb, I changed /etc/PolicyKit/PolicyKit.conf to:
<config version="0.1">
<match user="root">
<return result="yes"/>
</match>
<define_admin_auth group="wheel"/>
</config>
and everything still seems to work. Maybe this is a little more secure.
Last edited by azleifel (2008-10-26 13:27:11)
Offline