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 482436 - crash in Battery Charge Monitor: Just plugged in an ipod
crash in Battery Charge Monitor: Just plugged in an ipod
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-10-02 03:23 UTC by trq
Modified: 2007-10-06 09:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description trq 2007-10-02 03:23:06 UTC 
What were you doing when the application crashed?
Just plugged in an ipod


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

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 57085952 vsize: 57085952 resident: 5185536 share: 4014080 rss: 5185536 rss_rlim: 4294967295
CPU usage: start_time: 1191060849 rtime: 315 utime: 263 stime: 52 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 -1208232224 (LWP 2859)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 167009

Thread 1 (Thread -1208232224 (LWP 2859))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 ??
    from /lib/libdbus-1.so.3
  • #8 ??
    from /lib/libdbus-1.so.3
  • #9 dbus_move_error
    from /lib/libdbus-1.so.3
  • #10 libhal_device_property_exists
    from /usr/lib/libhal.so.1
  • #11 ??
  • #12 ??
    from /usr/lib/libhal.so.1
  • #13 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #14 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #20 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #21 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #22 panel_applet_factory_main
    from /usr/lib/libpanel-applet-2.so.0
  • #23 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (1569 sec old) ---------------------
We apologize for the inconvenience, but Google Earth has crashed.
 This is a bug in the program, and should never happen under normal
 circumstances. A bug report and debugging data are now being written
 to this text file:
    /home/trq/.googleearth/crashlogs/crashlog-ED5B5232.txt
This bug report will be sent to Google automatically next time you run
 Google Earth. Its data, which contains no personal information, will help
 us correct problems without bothering you further. If you would rather
 this info not be transmitted, please delete the above file before running
 the program again. If you want bug reports to NEVER be sent, remove the
 above 'crashlogs' directory's read/write permissions.
--------------------------------------------------
Comment 1 Susana 2007-10-06 09:46:34 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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