I do not get the syslog spam about not being able to acquire the name
"org.freedesktop.ConsoleKit". So that does look to be fixed.
I would like to point out that this bug is marked as a duplicate of
#216511, where the issue definitely is that the console-kit session is
not recovered after a dbus r
I don't think you do get a reboot prompt. Running with the existing dbus
until you next reboot is generally going to work.
> For what it's worth, I was able to reproduce this just now. Restart
> dbus, consolekit no-longer thinks I am logged in.
That's not what the bug is about though. Did you get
Lucas - The postinst script for dbus will attempt to start the service
if it isn't already started (new installation) but will ask you to
reboot if it is an upgrade
--
PolicyKit fails after restarting dbus (restarting all dbus services)
https://bugs.launchpad.net/bugs/231180
You received this bug
I'm pretty sure that apt-get update/upgrade does restart dbus and no
prompt for reboot appears. I would not accept boot anyway.
--
PolicyKit fails after restarting dbus (restarting all dbus services)
https://bugs.launchpad.net/bugs/231180
You received this bug notification because you are a membe
> Lukas - Upgrading dbus doesn't restart the dbus service. After upgrading
> dbus, you will be prompted to reboot.
Ubuntu95 has detected a change in your system configuration. Reboot to
activate?
:P
For what it's worth, I was able to reproduce this just now. Restart
dbus, consolekit no-longer th
Lukas - Upgrading dbus doesn't restart the dbus service. After upgrading
dbus, you will be prompted to reboot.
--
PolicyKit fails after restarting dbus (restarting all dbus services)
https://bugs.launchpad.net/bugs/231180
You received this bug notification because you are a member of Ubuntu
Bugs,
> As Chris said, restarting dbus is a really bad idea, and you should
never do it.
are you kidding?? what about upgrading dbus package that restarts dbus?
do not even think of saying upgrading dbus is a really bad idea.
--
PolicyKit fails after restarting dbus (restarting all dbus services)
http
Hi,
Has anyone reproduced this on latest Intrepid?
As Chris said, restarting dbus is a really bad idea, and you should never
do it. I believe this issue may have been fixed regardless of that.
Thanks,
James
** Changed in: policykit (Ubuntu)
Status: Confirmed => Invalid
** Changed in:
I am seeing this bug, too. Here is a summary:
- because of dbus buggyness I have to restart it sometimes:
# /etc/init.d/dbus restart
(I know how to fix the mess afterward and how to get networkmanager
working again :>)
- one of the consequences is that two console-kit-daemon processes are
ru
Whenever I run Likewise-Open-gui to connect to the corporate domain in my
office, after successfully joining the domain it seems my desktop jumps through
some hoops, screen flickers a few times, nautilus opens a window to my home
folder, nm-applet disappears, and when I check my syslog it is be
** Also affects: consolekit (Ubuntu)
Importance: Undecided
Status: New
--
PolicyKit fails after restarting dbus (restarting all dbus services)
https://bugs.launchpad.net/bugs/231180
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Right. Manually killing and restarting console-kit-daemon is sufficient
to trigger this problem. I don't have complete information, but I still
believe this is a bug in PolicyKit as well as console-kit-daemon.
My educated guess is that when console-kit-daemon is restarted, it
forgets who's logge
Sorry, I meant dbus, i.e.
/etc/init.d/dbus restart
and I'm aware that this does involve restarting a lot of stuff. I
suspect you're right and this may not a bug specific to PolicyKit, but
it is a valid bug. DBus services should be able to cope with being
stopped and restarted like runlevel serv
You mention DBUS in the title and HAL later on. Which one is it?
Obviously, if you restart DBUS then HAL gets restarted anyway (along
with lots of other stuff).
Why are you trying to restart DBUS anyway? It causes all sorts of
horrible problems (not just with PolicyKit). I've just tried restarting
14 matches
Mail list logo
