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 506994 - crash in Battery Charge Monitor: Was running on a desktop...
crash in Battery Charge Monitor: Was running on a desktop...
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: 2008-01-03 10:17 UTC by alar
Modified: 2008-01-08 20:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description alar 2008-01-03 10:17:07 UTC 
What were you doing when the application crashed?
Was running on a desktop PC, so there is no battery to check for. I activated it for mistake


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 23:05:33 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 24248320 vsize: 24248320 resident: 6402048 share: 5595136 rss: 6402048 rss_rlim: 4294967295
CPU usage: start_time: 1199303189 rtime: 60 utime: 47 stime: 13 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 -1208559904 (LWP 3685)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 183891

Thread 1 (Thread -1208559904 (LWP 3685))

  • #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 (52136 sec old) ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3755
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Impossibile aprire il file .desktop «/usr/share/applications/openoffice.org-1.9-writer.desktop» per l'icona di avvio: No such file or directory
Impossibile aprire il file .desktop «/usr/share/applications/openoffice.org-1.9-impress.desktop» per l'icona di avvio: No such file or directory
Impossibile aprire il file .desktop «/usr/share/applications/openoffice.org-1.9-calc.desktop» per l'icona di avvio: No such file or directory
--------------------------------------------------
Comment 1 André Klapper 2008-01-08 20:16:39 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 ***