My guess is that something delays DBus initialization (something related
to the Live CD), and it's not ready to talk to gdu-notification-daemon
when it wants to. The error message in gdu_pool_new() (gdu-pool.c) is
the first warning that something will not be OK (you can see this in the
attached .xsession-errors file). Then in recompute_presentables(), the
parameter "pool" is used several times without NULL checking, this
causes the NULL pointer warnings. Then finally an assertion catches it.

But how do I prove this? The only way to reproduce this is booting the
Live CD. My usual way of going about this would be adding debug messages
to gdu_pool_new_for_address() in gdu-pool.c to pinpoint where exactly
the process stops, then recompile it and test. But how do I do that for
a Live CD? Is there a well-documented way to assemble my own version of
the CD with the customized daemon? Or is there an easier way to do it?

-- 
gdu-notification-daemon closed unexpectedly - Lucid RC Live CD  
https://bugs.launchpad.net/bugs/568565
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to