I found that problem is in function gvm_console_kit_seat_get_sessions.
do {
if (dbus_message_iter_get_arg_type (elem) ==
DBUS_TYPE_OBJECT_PATH) {
dbus_message_iter_get_basic (elem, path);
g_ptr_array_add (sessions, g_strdup (path));
the problem will be probably in console kit or something as ck-list-
sessions does not show any session.
--
not using gdm does not create a ConsoleKit session
https://bugs.launchpad.net/bugs/186353
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I do not use gdm so consolekit did not show any session. I installed
libpam-ck-connector and now the gnome-volume-manager starts.
However, it used to work even without libpam-ck-connector in edgy. I
wonder why it does not work in hardy.
--
gnome-volume-manager does not start in Hardy
hal is running.
$ ps ax |grep hal
3308 ?Ss 0:05 /usr/sbin/hald
3373 ?S 0:00 hald-runner
3388 ?S 0:00 hald-addon-input: Listening on /dev/input/event4
/dev/input/event3 /dev/input/event5 /dev/input/event0 /dev/input/event1
/dev/input/event2
3397 ?
Thanks for your report, is that reproducible with another new user
created on your system?
** Changed in: gnome-volume-manager (Ubuntu)
Status: New = Incomplete
--
gnome-volume-manager does not start in Hardy
https://bugs.launchpad.net/bugs/186353
You received this bug notification
yes, it is.
--
gnome-volume-manager does not start in Hardy
https://bugs.launchpad.net/bugs/186353
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Summary changed:
- gnome-volume-manager does not start in Hurdy
+ gnome-volume-manager does not start in Hardy
** Description changed:
Binary package hint: gnome-volume-manager
- In the current Hurdy (I know it is unstable/developement branch), the
+ In the current Hardy (I know it is
