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 504219 - crash in Battery Charge Monitor: I was compiling vmware s...
crash in Battery Charge Monitor: I was compiling vmware s...
Status: RESOLVED DUPLICATE of bug 446097
Product: gnome-applets
Classification: Other
Component: battery
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-18 11:41 UTC by goxk
Modified: 2008-02-11 09:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description goxk 2007-12-18 11:41:23 UTC 
What were you doing when the application crashed?
I was compiling vmware server for the new installed kernel kernel-2.6.23.1-21.fc7


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 20:39:56 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 255385600 vsize: 255385600 resident: 9822208 share: 7360512 rss: 9822208 rss_rlim: 18446744073709551615
CPU usage: start_time: 1197976061 rtime: 5 utime: 3 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496383728 (LWP 3651)]
(no debugging symbols found)
0x000000358040d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 182220

Thread 1 (Thread 46912496383728 (LWP 3651))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_str_hash
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_str_hash
    from /lib64/libdbus-1.so.3
  • #6 g_str_hash
    from /lib64/libdbus-1.so.3
  • #7 libhal_device_property_exists
    from /usr/lib64/libhal.so.1
  • #8 ??
  • #9 g_str_hash
    from /usr/lib64/libhal.so.1
  • #10 dbus_connection_dispatch
    from /lib64/libdbus-1.so.3
  • #11 g_str_hash
    from /usr/lib64/libdbus-glib-1.so.2
  • #12 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #13 g_str_hash
    from /lib64/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #16 bonobo_generic_factory_main_timeout
    from /usr/lib64/libbonobo-2.so.0
  • #17 panel_applet_factory_main_closure
    from /usr/lib64/libpanel-applet-2.so.0
  • #18 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Cosimo Cecchi





          2008-02-11 09:57:02 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 446097 ***