GNOME Bugzilla – Bug 99206
Battstat applet crash
Last modified: 2009-08-15 18:40:50 UTC
Package: gnome-applets Severity: critical Version: 0 Synopsis: Battstat applet crash Bugzilla-Product: gnome-applets Bugzilla-Component: battery BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: Description of Problem: Applet crashed on boot (I switched an AC power while booting) Steps to reproduce the problem: 1. Boot 2. Switch on AC power 3. Actual Results: Crash Expected Results: No crash How often does this happen? Only happened once Additional Information: ------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-11-21 11:21 ------- The original reporter (JuBColding@yorkref.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gnome-applets-maint@bugzilla.gnome.org.
Without a stack trace, this bug will be difficult to fix. Please try to capture a trace (using gdb or bug-buddy) and attach it to this report. Thanks!
I was using bug-buddy, but it did not produce any stack trace. But see bug #99205 which happen just after this one (and has a stack trace).
I have also seen this same basic problem--a battstat crash followed by a panel crash. I've seen it several times, so it is repeatable (around 5% of the time, or so). Getting the panel to crash following the battstat crash is repeatable around 1% of the time (yes, I've logged in and out hundreds of times--see bug 94422 which is the bug I was trying to duplicate when I found I could also duplicate this one). However, the biggest problem is that bug-buddy will not get the stacktrace from the battstat crash. I'm not sure how to get around this, so I'm asking on #bugs right now... Also, this may be related to bug 86458 (and 87245). If so, this may be fixed by now. But I can't tell until I can get a stack trace.
I obtained a stack trace for a battstat applet crash (bug 100202), but it may not be the same (this time and most times it isn't followed by a panel crash for me). Jules, can you get this crash again and obtain a stack trace? I believe that bug-buddy will have a problem obtaining a stack trace, but you just have to do the following when bug-buddy comes up: 1) Open a gnome-terminal 2) run 'gdb /usr/libexec/battstat-applet-2' 3) Enter 'attach <pid>' at the "(gdb)" prompt, where <pid> is the process ID number that should show up in the bug-buddy screen. 4) Enter 'thread apply all bt' at the next "(gdb)" prompt 5) Paste the output here You may have to modify the command line in step 2 if your battstat applet is in a different location. Also, I believe that you should be able to duplicate this just by logging in and out several times (About 10-15 times; I was lucky and it only took me 7). If for some reason you can't duplicate anymore you can just let us know in that case too. One more thing--thanks for submitting these bug reports and following up to help us make Gnome better, Jules.
I have tried to log in and out a *lot* of times now, but I can not reproduce it.
Jules: Thanks for following up. If you can't reproduce it, then we'll just assume it's fixed for now. Let us know if it happens again, though.