GNOME Bugzilla – Bug 446097
crash in Battery Charge Monitor: Plugging in a USB mouse
Last modified: 2020-11-06 19:56:18 UTC
What were you doing when the application crashed? Plugging in a USB mouse Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 25292800 vsize: 25292800 resident: 10493952 share: 8359936 rss: 10493952 rss_rlim: 4294967295 CPU usage: start_time: 1181457136 rtime: 12 utime: 10 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/battstat-applet-2' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208464784 (LWP 8456)] (no debugging symbols found) 0x00910402 in __kernel_vsyscall ()
+ Trace 139837
Thread 1 (Thread -1208464784 (LWP 8456))
----------- .xsession-errors (40258 sec old) --------------------- File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 230, in __init__ _dbus_bindings.UInt32(0)) File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 169, in __call__ reply_message = self._connection.send_message_with_reply_and_block(message, timeout) dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files compiz: pixmap 0x1200edd can't be bound to texture (process:3726): GStreamer-WARNING **: The GStreamer function gst_init_get_option_group() was called, but the GLib threading system has not been initialised yet, something that must happen before any other GLib function is called. The application needs to be fixed so that it calls if (!g_thread_supported ()) g_thread_init(NULL); as very first thing in its main() function. Please file a bug against this application. compiz: pixmap 0x126de61 can't be bound to texture --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 446377 has been marked as a duplicate of this bug. ***
*** Bug 449248 has been marked as a duplicate of this bug. ***
*** Bug 449953 has been marked as a duplicate of this bug. ***
*** Bug 448164 has been marked as a duplicate of this bug. ***
Reopening due to dupes.
*** Bug 456666 has been marked as a duplicate of this bug. ***
*** Bug 457547 has been marked as a duplicate of this bug. ***
*** Bug 457819 has been marked as a duplicate of this bug. ***
*** Bug 459591 has been marked as a duplicate of this bug. ***
*** Bug 447104 has been marked as a duplicate of this bug. ***
It's worth adding that every time this applet crashed I was having trouble with my USB mouse. The mouse, as it turns out, was flaky - jostling the USB connector even a little bit would cause it to stop working... until I jostled it some more. This problem occurred on a laptop, and I'd have times where the logs would show the mouse disconnecting and reconnecting dozens of times inside of a couple minutes. The battery applet crashes seemed to only occur when the mouse was "reconnected" - though not consistently, if frequently. No other USB devices showed these symptoms, and, suffice to say, the mouse has since been replaced. I've had no further crashes of the battery applet (nor, thankfully, any more problems with my mouse).
*** Bug 463983 has been marked as a duplicate of this bug. ***
*** Bug 465311 has been marked as a duplicate of this bug. ***
*** Bug 466315 has been marked as a duplicate of this bug. ***
*** Bug 466883 has been marked as a duplicate of this bug. ***
*** Bug 467970 has been marked as a duplicate of this bug. ***
*** Bug 468698 has been marked as a duplicate of this bug. ***
*** Bug 470831 has been marked as a duplicate of this bug. ***
*** Bug 472014 has been marked as a duplicate of this bug. ***
*** Bug 472319 has been marked as a duplicate of this bug. ***
*** Bug 474936 has been marked as a duplicate of this bug. ***
*** Bug 475097 has been marked as a duplicate of this bug. ***
*** Bug 475856 has been marked as a duplicate of this bug. ***
*** Bug 476090 has been marked as a duplicate of this bug. ***
*** Bug 476429 has been marked as a duplicate of this bug. ***
*** Bug 477927 has been marked as a duplicate of this bug. ***
*** Bug 478014 has been marked as a duplicate of this bug. ***
*** Bug 478517 has been marked as a duplicate of this bug. ***
*** Bug 479017 has been marked as a duplicate of this bug. ***
*** Bug 482436 has been marked as a duplicate of this bug. ***
*** Bug 482454 has been marked as a duplicate of this bug. ***
From bug 477927: "This bug seems to have some relationship with the ThinkFinger package and modifications to pam configuration, I had the following config in /etc/pam.d/system.auth - auth required pam_env.so auth sufficient pam_thinkfinger.so auth sufficient pam_unix.so nullok_secure try_first_pass auth requisite pam_succeed_if.so uid >= 500 quiet auth required pam_deny.so which prevented login via ssh ( not sure if it is correct ). The login attempt directly correlates with the battery monitor app crash, I have commented out the thinkfinger line at present to work around this."
*** Bug 491073 has been marked as a duplicate of this bug. ***
*** Bug 485829 has been marked as a duplicate of this bug. ***
*** Bug 485968 has been marked as a duplicate of this bug. ***
*** Bug 489299 has been marked as a duplicate of this bug. ***
*** Bug 489557 has been marked as a duplicate of this bug. ***
*** Bug 490663 has been marked as a duplicate of this bug. ***
*** Bug 456028 has been marked as a duplicate of this bug. ***
*** Bug 474739 has been marked as a duplicate of this bug. ***
*** Bug 485212 has been marked as a duplicate of this bug. ***
*** Bug 491237 has been marked as a duplicate of this bug. ***
*** Bug 492135 has been marked as a duplicate of this bug. ***
*** Bug 492947 has been marked as a duplicate of this bug. ***
Dear reporters, can anybody of you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
This problem has stopped occuring for me. Sometime in the last couple of updates. I'm currently running 2.6.22.9.91.fc7. So the problem may have been solved by one of the updates. Note. It was occuring previously everytime I plugged in a USB memory stick.
I upgrade to Fedora 8 and the problem has disappeared. I think the Fedora people updated the thinkfinger package... I think this bug can be closed.
I'd be happy to grab a stack trace with debugging symbols, except the problem went away when I disposed of the USB mouse. I've seen no sign of it since.
*** Bug 492367 has been marked as a duplicate of this bug. ***
*** Bug 492405 has been marked as a duplicate of this bug. ***
*** Bug 492674 has been marked as a duplicate of this bug. ***
*** Bug 492789 has been marked as a duplicate of this bug. ***
*** Bug 492914 has been marked as a duplicate of this bug. ***
*** Bug 496268 has been marked as a duplicate of this bug. ***
*** Bug 497592 has been marked as a duplicate of this bug. ***
*** Bug 497981 has been marked as a duplicate of this bug. ***
*** Bug 498272 has been marked as a duplicate of this bug. ***
*** Bug 500250 has been marked as a duplicate of this bug. ***
*** Bug 501605 has been marked as a duplicate of this bug. ***
*** Bug 502209 has been marked as a duplicate of this bug. ***
according to two comments this problem has vanished by installing updates or updating to fedora 8. would be nice to get more feedback, though. can anybody still reproduce this issue with fedora 8?
*** Bug 503434 has been marked as a duplicate of this bug. ***
*** Bug 503311 has been marked as a duplicate of this bug. ***
*** Bug 503708 has been marked as a duplicate of this bug. ***
*** Bug 503709 has been marked as a duplicate of this bug. ***
*** Bug 505010 has been marked as a duplicate of this bug. ***
*** Bug 505597 has been marked as a duplicate of this bug. ***
*** Bug 506044 has been marked as a duplicate of this bug. ***
*** Bug 506137 has been marked as a duplicate of this bug. ***
*** Bug 506375 has been marked as a duplicate of this bug. ***
*** Bug 506380 has been marked as a duplicate of this bug. ***
*** Bug 506994 has been marked as a duplicate of this bug. ***
*** Bug 508525 has been marked as a duplicate of this bug. ***
*** Bug 508627 has been marked as a duplicate of this bug. ***
*** Bug 509534 has been marked as a duplicate of this bug. ***
bug #509534 have a little better trace.
*** Bug 509557 has been marked as a duplicate of this bug. ***
can anybody still reproduce this issue with fedora 8?
yap, the following trace is from Fedora 8 and from the next duplicate. It happened when the computer woke up from sleep mode.
+ Trace 188073
*** Bug 514364 has been marked as a duplicate of this bug. ***
After reading the earlier comments about the defective USB mouse, I should add a few details. I arrived at work with my laptop, woke it up, logged in, and connected the mouse, keyboard, power, and network. I don't remember what order I did these things, but the next thing I noticed was that bug-buddy was analyzing the crash.
*** Bug 515173 has been marked as a duplicate of this bug. ***
*** Bug 515352 has been marked as a duplicate of this bug. ***
*** Bug 515241 has been marked as a duplicate of this bug. ***
*** Bug 515506 has been marked as a duplicate of this bug. ***
*** Bug 515644 has been marked as a duplicate of this bug. ***
*** Bug 508985 has been marked as a duplicate of this bug. ***
*** Bug 507741 has been marked as a duplicate of this bug. ***
*** Bug 507313 has been marked as a duplicate of this bug. ***
*** Bug 504219 has been marked as a duplicate of this bug. ***
Created attachment 105052 [details] [review] Free dbus error Looking at the trace from comment #80, it seems the applet sets dbus errors on top of each other which isn't allowed. I can't reproduce the bug so I don't know whether this patch makes any difference.
*** Bug 516460 has been marked as a duplicate of this bug. ***
*** Bug 516547 has been marked as a duplicate of this bug. ***
*** Bug 517219 has been marked as a duplicate of this bug. ***
*** Bug 519049 has been marked as a duplicate of this bug. ***
*** Bug 531045 has been marked as a duplicate of this bug. ***
*** Bug 531046 has been marked as a duplicate of this bug. ***
only very few duplicates in the last months, removing blocker status.
*** Bug 548544 has been marked as a duplicate of this bug. ***
*** Bug 532186 has been marked as a duplicate of this bug. ***
Updating version due to latest duplicates.
*** Bug 553239 has been marked as a duplicate of this bug. ***
*** Bug 566789 has been marked as a duplicate of this bug. ***
*** Bug 575194 has been marked as a duplicate of this bug. ***
*** Bug 579081 has been marked as a duplicate of this bug. ***
*** Bug 579755 has been marked as a duplicate of this bug. ***
*** Bug 591251 has been marked as a duplicate of this bug. ***
*** Bug 597462 has been marked as a duplicate of this bug. ***
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-applets/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.