After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 103949 - battstat_applet crashes upon login
battstat_applet crashes upon login
Status: RESOLVED DUPLICATE of bug 86458
Product: gnome-applets
Classification: Other
Component: battery
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-01-20 08:54 UTC by Adam Monsen
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Terminal session captured with 'script' getting backtrace for all threads (9.23 KB, text/plain)
2003-02-15 19:41 UTC, Adam Monsen
Details

Description Adam Monsen 2003-01-20 09:10:26 UTC
Package: gnome-applets
Severity: normal
Version: 0
Synopsis: battstat_applet crashes upon login
Bugzilla-Product: gnome-applets
Bugzilla-Component: battery
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
Battstat Applet crashes on login.

Steps to reproduce the problem:
1. login
2. load battstat applet
3. logout, "saving changes"
4. login....

Actual Results:
battstat_applet crashes

Expected Results:
doesn't crash but simply appears on panel

How often does this happen?
every time

Additional Information:
Red Hat 8.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-20 04:10 -------

Reassigning to the default owner of the component, gnome-applets-maint@bugzilla.gnome.org.

Comment 1 Alex Duggan 2003-01-20 16:18:35 UTC
Please include a backtrace of the crash using bug-buddy or gdb.  See
http://bugzilla.gnome.org/getting-traces.cgi for more information. 
Thanks.
Comment 2 Adam Monsen 2003-01-20 21:36:00 UTC
I'm unable to get a stack backtrace from bug buddy, and gdb says 'no
debugging symbols found' when I try 'gdb /usr/libexec/battstat-applet-2'.

The version of battstat-applet-2 I have came with a stock install of
Red Hat 8.0, the package is called 'gnome-applets-2.0.1-6'. Do I need
to get a different version of battstat-applet-2 to get a backtrace?
Comment 3 Elijah Newren 2003-02-14 20:34:27 UTC
You don't need debugging symbols in order to get a stack trace. 
Here's what you can do:

  1) Do whatever you normally do to get the crash
  2) When bug-buddy comes up, it should report the PID (Process ID #) of
     the crashed battstat-applet-2 program
  3) Run 'gdb /usr/libexec/battstat-applet-2'
  4) Enter 'attach <PID>' at the gdb prompt (where PID is the process ID 
     # that bug-buddy reported)
  5) Enter 'thread apply all bt' at the gdb prompt
Comment 4 Adam Monsen 2003-02-15 19:41:58 UTC
Created attachment 14358 [details]
Terminal session captured with 'script' getting backtrace for all threads
Comment 5 Elijah Newren 2003-02-15 21:48:57 UTC
Don't have time to check for duplicates right now, so I'll simply
reopen for now...
Comment 6 Adam Monsen 2003-02-15 22:26:51 UTC
possibly a dupe of bug #104160 (or vice-versa, since this one was first).

I'm using a Dell Latitude C610, and kernel 2.4.18 (with Red Hat's
latest patches). I haven't tried kernel 2.4.19 to see if it fixes Dell
BIOS power management issues.

bug #104926 may also be related.
Comment 7 Kevin Vandersloot 2003-02-17 03:31:08 UTC
This should be fixed in later versions of gnome-applets (it is a dup
of a different bug). 
Comment 8 Elijah Newren 2003-02-17 15:53:45 UTC
Pasting backtrace inline to make it easier to search:

(gdb) thread apply all bt

Thread 1 (Thread 8192 (LWP 31014))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 gdk_draw_drawable
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 pixmap_timeout
  • #8 battstat_applet_fill
  • #9 battstat_applet_factory
  • #10 panel_applet_marshal_BOOLEAN__STRING
    from /usr/lib/libpanel-applet-2.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 bonobo_closure_invoke_va_list
    from /usr/lib/libbonobo-2.so.0
  • #13 bonobo_closure_invoke
    from /usr/lib/libbonobo-2.so.0
  • #14 panel_applet_control_bound
    from /usr/lib/libpanel-applet-2.so.0
  • #15 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 impl_Bonobo_Control_setFrame
    from /usr/lib/libbonoboui-2.so.0
  • #21 _ORBIT_skel_small_Bonobo_Control_setFrame
    from /usr/lib/libbonobo-2.so.0
  • #22 ORBit_POAObject_invoke
    from /usr/lib/libORBit-2.so.0
  • #23 ORBit_OAObject_invoke
    from /usr/lib/libORBit-2.so.0
  • #24 ORBit_small_invoke_adaptor
    from /usr/lib/libORBit-2.so.0
  • #25 ORBit_POAObject_handle_request
    from /usr/lib/libORBit-2.so.0
  • #26 ORBit_POA_handle_request
    from /usr/lib/libORBit-2.so.0
  • #27 ORBit_handle_request
    from /usr/lib/libORBit-2.so.0
  • #28 giop_connection_handle_input
    from /usr/lib/libORBit-2.so.0
  • #29 linc_connection_io_handler
    from /usr/lib/liblinc.so.1
  • #30 linc_source_dispatch
    from /usr/lib/liblinc.so.1
  • #31 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #32 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #33 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #34 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #35 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #36 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #37 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #38 panel_applet_factory_main
    from /usr/lib/libpanel-applet-2.so.0
  • #39 main
  • #40 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6

Comment 9 Elijah Newren 2003-02-17 16:00:34 UTC
Not related to bug 104160 (stack traces are totally different), and
it's impossible to tell if it's related to bug 104926 (since neither
of the people having problems in that bug have provided a stack trace
yet).

Looks like a duplicate of bug 100202, which is marked as a duplicate
of 86458.  So I'll mark it as a duplicate of bug 86458.

Adam: Thanks for following up with this bug.  Few people do but it
helps a lot.  Note that bug 86458 wasn't marked as fixed until late
last October, so it wasn't in time before Redhat 8.0 came out.  The
next version of Redhat should have this fixed (or you can recompile
from source if you want it fixed before then...)

*** This bug has been marked as a duplicate of 86458 ***
Comment 10 Adam Monsen 2003-02-18 05:10:50 UTC
Happy to help. Thank /you/!