Gnome-panel loads very late after session start

Another issue , is the system shutdown icon is missing from the panel , since the FUSA is still being reworked , the user-switch-applet doesnt have a shutdown option.
At present shutdown/reboot only from the terminal is possible.

Thank you for your bug report. I can't reproduce this though. The error messages there suggest that the session manager cannot be contacted (which explains the panel delay and lack of shutdown options).

How are you starting your session? You're just using a standard configuration (with GDM) right?

I do a regular session start with auto login.

Luckily i caught Chris on irc :)
other info
~$ env | grep DBUS
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-O5fzOQAWbm,guid=c89acb85b14c09506690a54a4a91b08d

~$ ck-list-sessions
Session1:
 unix-user = '1000'
 realname = 'Vishnoo'
 seat = 'Seat1'
 session-type = ''
 active = TRUE
 x11-display = ':0'
 x11-display-device = '/dev/tty7'
 display-device = ''
 remote-host-name = ''
 is-local = TRUE
 on-since = '2009-08-23T21:11:39.592045Z'
 login-session-id = ''

~$ dbus-send --session --dest='org.gnome.SessionManager' --print-reply --type=method_call /org/gnome/SessionManager org.gnome.SessionManager.CanShutdown
method return sender=:1.3 -> dest=:1.88 reply_serial=2
   boolean true

Attaching the gnome-session log from a failsafe xterm session
 ~$ gnome-session --debug 2>&1 | tee gnome-session-debug.log

And the .xsession-errors file

Running $ gnome-power-manager --verbose
(gnome-power-manager:26070): devkit-power-gobject-WARNING **: Couldn't enumerate devices: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(gnome-power-manager:26070): devkit-power-gobject-WARNING **: Error invoking GetAll() to get properties: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

These two errors keep repeating

I also notice a delay when I select from the panel ,
- update manager
- logout or any option from the user-switch-applet
- power management preferences

I guess all these call upon the power status and keep waiting.

I cannot reproduce this behavior and I don't get the d-bus timeouts on gnome-power-manager either. Can you please do these three commands in a Terminal and check if any of them time out?

dbus-send --system --print-reply --dest=org.freedesktop.DeviceKit.Power /org/freedesktop/DeviceKit/Power org.freedesktop.DBus.Properties.GetAll string:''

dbus-send --system --print-reply --dest=org.freedesktop.DeviceKit.Power /org/freedesktop/DeviceKit/Power/Policy org.freedesktop.DBus.Properties.GetAll string:''

dbus-send --system --print-reply --dest=org.freedesktop.DeviceKit.Power /org/freedesktop/DeviceKit/Power/Wakeups org.freedesktop.DBus.Properties.GetAll string:''

Those commands dont time out , as per Martin Pitt's suggestion to run dbus-monitor --system, i'm attaching the log.
I'v done the following steps:
$ killall gnome-power-manager
$ dbus-monitor --system 2>&1 | tee dbus-monitor.log.txt
$ gnome-power-manager --verbose --no-daemon 2>&1 | tee gpm.debug.log.txt

the gpm debug keeps repeating these 2 lines :

(gnome-power-manager:31208): devkit-power-gobject-WARNING **: Couldn't enumerate devices: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(gnome-power-manager:31208): devkit-power-gobject-WARNING **: Error invoking GetAll() to get properties: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Attaching the dbus-monitor output.

While running the dbus-monitor also tried to open update-manager and power manager prefs.

So something about those might be there in the log too.

OK, I checked the code in dkp_client_enumerate_devices_private() which throws that timeout, and it tries this D-Bus call:

$ dbus-send --system --print-reply --dest=org.freedesktop.DeviceKit.Power /org/freedesktop/DeviceKit/Power org.freedesktop.DeviceKit.Power.EnumerateDevices
method return sender=:1.24 -> dest=:1.86 reply_serial=2
   array [
      object path "/org/freedesktop/DeviceKit/Power/devices/line_power_AC"
   ]

What does it print for you? Does it time out?

I don't think it's a D-Bus ACL problem, the default policy is alright. I suspect that doing that call might crash devkit-power-daemon. If that dbus-send call reproduces the bug, please do

  sudo killall devkit-power-daemon
  sudo /usr/lib/devicekit-power/devkit-power-daemon -v 2>&1 | tee /tmp/dkp.log

switch to another terminal, do above dbus call, and then check whether this crashes the devkit-power-daemon process. Please attach /tmp/dkp.log if it does.

I don't think this is a panel bug, closing for now.

I first ran the dbus command , it *did* give a reply ,somewhat similar to what you have posted above in comment #10

so then i did:
$sudo killall devkit-power-daemon
$sudo /usr/lib/devicekit-power/devkit-power-daemon -v 2>&1 | tee /tmp/dkp.log

$ dbus-send --system --print-reply --dest=org.freedesktop.DeviceKit.Power /org/freedesktop/DeviceKit/Power org.freedesktop.DeviceKit.Power.EnumerateDevices
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

now it failed.
attaching the /tmp/dkp.log

Thanks for the ssh access. I confirmed that dk-p doesn't crash, but just suffers from a lot of delays from system calls due to problems with the webcam:

[92197.690399] vc032x: I2c Bus Busy Wait 2c
[92197.690406] vc032x: Unknown sensor...
[92197.690439] vc032x: probe of 1-8:1.0 failed with error -22
[92197.690563] usb 1-8: USB disconnect, address 26
[92197.929053] usb 1-8: new high speed USB device using ehci_hcd and address 27
[92198.088360] usb 1-8: configuration #1 chosen from 1 choice
[92198.089233] gspca: probing 046d:0892
[92198.089633] vc032x: check sensor header 2c
[92198.115266] vc032x: I2c Bus Busy Wait 2c

(repeated over and over)

When gspca_vc032x gets blacklisted, everything works normally.

Problem still excists on LTS2

 gnome-power-manager --verbose --no-daemon 2>&1 | tee gpm.debug.log.txt

(gnome-power-manager:2280): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.1/gobject/gsignal.c:2273: signal `proxy-status' is invalid for instance `0x896b330'

** (gnome-power-manager:2280): WARNING **: Either HAL or DBUS are not working!

** (gnome-power-manager:2280): WARNING **: proxy failed

** (gnome-power-manager:2280): WARNING **: failed to get Computer root object

** (gnome-power-manager:2280): WARNING **: proxy NULL!!