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 466315 - crash in Battery Charge Monitor: i was trying to set the ...
crash in Battery Charge Monitor: i was trying to set the ...
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-08-13 17:54 UTC by coleyjunkmail
Modified: 2007-08-24 20:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description coleyjunkmail 2007-08-13 17:54:49 UTC
What were you doing when the application crashed?
i was trying to set the workspace toolbar up


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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve-Lime
Icon Theme: Crux

Memory status: size: 39538688 vsize: 39538688 resident: 18808832 share: 16297984 rss: 18808832 rss_rlim: 4294967295
CPU usage: start_time: 1186940764 rtime: 77 utime: 69 stime: 8 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 -1209066896 (LWP 3127)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

Thread 1 (Thread -1209066896 (LWP 3127))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 g_str_hash
    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 g_str_hash
    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 (180 sec old) ---------------------
localuser:Sydney being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2942
compiz: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager.
compiz: No manageable screens found on display :0.0
--------------------------------------------------
Comment 1 Susana 2007-08-24 20:53:44 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 ***