Public bug reported:
I'm not sure if it's bug in upstart or libdbus, but (2) points to
upstart, I see only two issues:
1. 100% CPU usage of the daemon
2. `upstart-udev-bridge --daemon` running as pid 472 floods /dev/null
with following messages according to strace:
...
write(2, "process 472: ", 13) = 13
write(2, "arguments to dbus_message_iter_append_basic() were incorrect,
assertion \"_dbus_check_is_valid_utf8 (*string_p)\" failed in file
../../dbus/dbus-message.c line 2534.\nThis is normally a bug in some
application using the D-Bus library.\n", 232) = 232
...
and strace shows nothing else.
gdb backtrace samples are useless due to lack of debug symbols and I see
no upstart-dbg package to get them.
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942453
Title:
100% CPU usage - upstart-udev-bridge
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/942453/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
