Launchpad has imported 15 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=962080.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-05-11T14:41:15+00:00 Lawrenc wrote: Version-Release number of selected component: upower-0.9.20-1.fc19 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/libexec/upowerd crash_function: dbus_g_connection_register_g_object executable: /usr/libexec/upowerd kernel: 3.9.1-301.fc19.x86_64 runlevel: N 5 uid: 0 Truncated backtrace: Thread no. 1 (6 frames) #2 dbus_g_connection_register_g_object at dbus-gobject.c:2859 #3 up_device_register_device at up-device.c:838 #4 up_device_coldplug at up-device.c:564 #5 up_backend_device_new at up-backend.c:175 #6 up_backend_device_add at up-backend.c:258 #11 monitor_event at src/gudev/gudevclient.c:103 Potential duplicate: bug 817352 Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/20 ------------------------------------------------------------------------ On 2013-05-11T14:41:17+00:00 Lawrenc wrote: Created attachment 746570 File: backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/21 ------------------------------------------------------------------------ On 2013-05-11T14:41:18+00:00 Lawrenc wrote: Created attachment 746571 File: cgroup Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/22 ------------------------------------------------------------------------ On 2013-05-11T14:41:19+00:00 Lawrenc wrote: Created attachment 746572 File: core_backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/23 ------------------------------------------------------------------------ On 2013-05-11T14:41:21+00:00 Lawrenc wrote: Created attachment 746573 File: dso_list Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/24 ------------------------------------------------------------------------ On 2013-05-11T14:41:23+00:00 Lawrenc wrote: Created attachment 746574 File: environ Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/25 ------------------------------------------------------------------------ On 2013-05-11T14:41:24+00:00 Lawrenc wrote: Created attachment 746575 File: limits Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/26 ------------------------------------------------------------------------ On 2013-05-11T14:41:26+00:00 Lawrenc wrote: Created attachment 746576 File: maps Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/27 ------------------------------------------------------------------------ On 2013-05-11T14:41:27+00:00 Lawrenc wrote: Created attachment 746577 File: open_fds Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/28 ------------------------------------------------------------------------ On 2013-05-11T14:41:29+00:00 Lawrenc wrote: Created attachment 746578 File: proc_pid_status Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/29 ------------------------------------------------------------------------ On 2013-05-11T14:41:30+00:00 Lawrenc wrote: Created attachment 746579 File: var_log_messages Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/30 ------------------------------------------------------------------------ On 2013-06-29T06:57:15+00:00 Mikhail wrote: Occurs every time when my Apple Magic Mouse reconnect to Bluetooth. Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/31 ------------------------------------------------------------------------ On 2013-09-20T16:41:57+00:00 Martin wrote: For the record, I track this in https://launchpad.net/bugs/1112907 . I am now able to reproduce this in a new test case, based on udev monitor logs that reporters sent me. Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/39 ------------------------------------------------------------------------ On 2015-01-09T18:06:27+00:00 Fedora wrote: This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/45 ------------------------------------------------------------------------ On 2015-02-17T15:13:32+00:00 Fedora wrote: Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/46 ** Changed in: upower Status: Unknown => Won't Fix ** Changed in: upower Importance: Unknown => Undecided -- 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 Linux: Unknown Status in Upower: Won't Fix Status in upower package in Ubuntu: Fix Released 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/linux/+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
