Thanks for your report. I really doubt that it's due to the negative value, since (1) a SIGPIPE is very unlikey in this case, and (2) it crashes deep in D-BUS code which usually doesn't care about particular message values.
Unfortunately the stack trace isn't very clear. You seem to be able to reproduce this reliably, any chance you could install some debugging symbols and use gdb again? https://wiki.ubuntu.com/DebuggingProgramCrash describes how to set up the debug symbol repository. You'll need these packages: sudo apt-get install devicekit-power-dbgsym libdbus-1-3-dbgsym libdbus-glib-1-2-dbgsym libdevkit-power-gobject1-dbgsym libgudev-1.0-0-dbgsym libglib2.0-0-dbgsym Thanks! Or even easier, the dk-power backend crash should be caught by Apport, and you should get offered to file a bug about it. This will automatically get post-processed to get a fully symbolic stack trace. ** Changed in: devicekit-power (Ubuntu) Status: New => Incomplete -- Karmic Alpha 6: devicekit-power-daemon crash with SIGPIPE https://bugs.launchpad.net/bugs/434771 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
