Martin, Please find attached monitor.txt as you requested. Here is how I can reproduce the crash:
- Enable my hp bluetooth mouse, and use it normally with the computer. - Go away and come back some time later after the mouse has gone to sleep. - As soon as I try use the mouse (i.e. it wakes up), the crash occurs. Regards, Tony. On September 6, 2013 at 9:12 AM Martin Pitt <[email protected]> wrote: > I'm afraid I still don't understand what happens there; it's not just a > simple removal and re-adding of these devices when they power down (I > just tried that in the test suite, and it works fine). For anyone who > can reproduce this, can you please open a terminal, and start > > udevadm monitor -e --udev | tee /tmp/monitor.txt > > then wait a bit, or do whatever is necessary to trigger that crash, then > go back to the terminal with the udevadm command, press Control-C to > stop it, and attach /tmp/monitor.txt here? Thanks! > > ** Changed in: upower (Ubuntu) > Status: Triaged => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1112907 > > Title: > abort with wireless HID devices: A handler is already registered for > <battery> > > Status in Upower: > Unknown > Status in “upower” package in Ubuntu: > Incomplete > > Bug description: > . > > ProblemType: Crash > DistroRelease: Ubuntu 13.04 > Package: upower 0.9.19-1ubuntu4 > ProcVersionSignature: Ubuntu 3.5.0-216.23-omap4 3.5.7.1 > Uname: Linux 3.5.0-216-omap4 armv7l > ApportVersion: 2.8-0ubuntu3 > Architecture: armhf > Date: Fri Feb 1 22:25:19 2013 > ExecutablePath: /usr/lib/upower/upowerd > InstallationDate: Installed on 2013-01-17 (15 days ago) > InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha armhf+omap4 > (20130116) > MarkForUpload: True > ProcCmdline: /usr/lib/upower/upowerd > ProcEnviron: > > Signal: 5 > SourcePackage: upower > StacktraceTop: > dbus_g_connection_register_g_object () from > /usr/lib/arm-linux-gnueabihf/libdbus-glib-1.so.2 > ?? () > ?? () > Title: upowerd crashed with signal 5 in dbus_g_connection_register_g_object() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/upower/+bug/1112907/+subscriptions " ** Attachment added: "monitor.txt" https://bugs.launchpad.net/bugs/1112907/+attachment/3809637/+files/monitor.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1112907 Title: abort with wireless HID devices: A handler is already registered for <battery> Status in Upower: Unknown Status in “upower” package in Ubuntu: Incomplete Bug description: . ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: upower 0.9.19-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-216.23-omap4 3.5.7.1 Uname: Linux 3.5.0-216-omap4 armv7l ApportVersion: 2.8-0ubuntu3 Architecture: armhf Date: Fri Feb 1 22:25:19 2013 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2013-01-17 (15 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha armhf+omap4 (20130116) MarkForUpload: True ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: Signal: 5 SourcePackage: upower StacktraceTop: dbus_g_connection_register_g_object () from /usr/lib/arm-linux-gnueabihf/libdbus-glib-1.so.2 ?? () ?? () Title: upowerd crashed with signal 5 in dbus_g_connection_register_g_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1112907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
