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 447104 - crash in Battery Charge Monitor: trying to make a chart o...
crash in Battery Charge Monitor: trying to make a chart o...
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
: 455914 457481 457495 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-13 12:02 UTC by adam_c79
Modified: 2008-12-08 14:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description adam_c79 2007-06-13 12:02:56 UTC
What were you doing when the application crashed?
trying to make a chart of figures in a spread sheet, this getting very frustrating...


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 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: 23859200 vsize: 23859200 resident: 7323648 share: 6295552 rss: 7323648 rss_rlim: 4294967295
CPU usage: start_time: 1181735216 rtime: 4 utime: 3 stime: 1 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 -1208407440 (LWP 3320)]
(no debugging symbols found)
0x00aae402 in __kernel_vsyscall ()

Thread 1 (Thread -1208407440 (LWP 3320))

  • #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 (410 sec old) ---------------------
(gnome-panel:3197): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
(gnome-panel:3197): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
(gnome-panel:3197): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
(gnome-panel:3197): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
error getting update info:  Cannot open/read repomd.xml file for repository: livna
** Message: <info>  You are now connected to the wireless network 'SpeedStream1867'.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600aaf (Assignment)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3607d2f (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 palfrey 2007-07-12 11:23:32 UTC
*** Bug 455914 has been marked as a duplicate of this bug. ***
Comment 2 Pedro Villavicencio 2007-07-16 22:43:17 UTC
*** Bug 457495 has been marked as a duplicate of this bug. ***
Comment 3 Pedro Villavicencio 2007-07-16 22:46:18 UTC
*** Bug 457481 has been marked as a duplicate of this bug. ***
Comment 4 Philip Withnall 2007-07-26 05:01:33 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 ***
Comment 5 Kevin Sacry 2007-07-26 14:34:33 UTC
I'm not really clear on if I'm supposed to be answering for this ticket or not.
But just in case, here it is:
I was doing two things.
1. I had just fired up vmware
2. I had just plugged in a usb external hard drive

I hope this helps.

Thanks,
Kevin

(In reply to comment #0)
> What were you doing when the application crashed?
> trying to make a chart of figures in a spread sheet, this getting very
> frustrating...
> 
> 
> Distribution: Fedora release 7 (Moonshine)
> Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
> BugBuddy Version: 2.18.0
> 
> System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 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: 23859200 vsize: 23859200 resident: 7323648 share: 6295552
> rss: 7323648 rss_rlim: 4294967295
> CPU usage: start_time: 1181735216 rtime: 4 utime: 3 stime: 1 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 -1208407440 (LWP 3320)]
> (no debugging symbols found)
> 0x00aae402 in __kernel_vsyscall ()
> #0  0x00aae402 in __kernel_vsyscall ()
> #1  0x00d28c33 in __waitpid_nocancel () from /lib/libpthread.so.0
> #2  0x04694a46 in ?? () from /usr/lib/libgnomeui-2.so.0
> #3  <signal handler called>
> #4  0x00aae402 in __kernel_vsyscall ()
> #5  0x00ba7fa0 in raise () from /lib/libc.so.6
> #6  0x00ba98b1 in abort () from /lib/libc.so.6
> #7  0x001f4f65 in ?? () from /lib/libdbus-1.so.3
> #8  0x001f0ee6 in ?? () from /lib/libdbus-1.so.3
> #9  0x001db9c4 in dbus_move_error () from /lib/libdbus-1.so.3
> #10 0x008c162b in libhal_device_property_exists () from /usr/lib/libhal.so.1
> #11 0x08051be0 in ?? ()
> #12 0x008c323d in ?? () from /usr/lib/libhal.so.1
> #13 0x001d99c2 in dbus_connection_dispatch () from /lib/libdbus-1.so.3
> #14 0x00491e1d in ?? () from /usr/lib/libdbus-glib-1.so.2
> #15 0x00d80622 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
> #16 0x00d835ff in ?? () from /lib/libglib-2.0.so.0
> #17 0x00d839a9 in g_main_loop_run () from /lib/libglib-2.0.so.0
> #18 0x006cb7e3 in bonobo_main () from /usr/lib/libbonobo-2.so.0
> #19 0x006c9a49 in bonobo_generic_factory_main_timeout ()
>    from /usr/lib/libbonobo-2.so.0
> #20 0x006c9ad3 in bonobo_generic_factory_main ()
>    from /usr/lib/libbonobo-2.so.0
> #21 0x00858041 in panel_applet_factory_main_closure ()
>    from /usr/lib/libpanel-applet-2.so.0
> #22 0x00858125 in panel_applet_factory_main ()
>    from /usr/lib/libpanel-applet-2.so.0
> #23 0x0804d493 in main ()
> 
> Thread 1 (Thread -1208407440 (LWP 3320)):
> #0  0x00aae402 in __kernel_vsyscall ()
> No symbol table info available.
> #1  0x00d28c33 in __waitpid_nocancel () from /lib/libpthread.so.0
> No symbol table info available.
> #2  0x04694a46 in ?? () from /usr/lib/libgnomeui-2.so.0
> No symbol table info available.
> #3  <signal handler called>
> No symbol table info available.
> #4  0x00aae402 in __kernel_vsyscall ()
> No symbol table info available.
> #5  0x00ba7fa0 in raise () from /lib/libc.so.6
> No symbol table info available.
> #6  0x00ba98b1 in abort () from /lib/libc.so.6
> No symbol table info available.
> #7  0x001f4f65 in ?? () from /lib/libdbus-1.so.3
> No symbol table info available.
> #8  0x001f0ee6 in ?? () from /lib/libdbus-1.so.3
> No symbol table info available.
> #9  0x001db9c4 in dbus_move_error () from /lib/libdbus-1.so.3
> No symbol table info available.
> #10 0x008c162b in libhal_device_property_exists () from /usr/lib/libhal.so.1
> No symbol table info available.
> #11 0x08051be0 in ?? ()
> No symbol table info available.
> #12 0x008c323d in ?? () from /usr/lib/libhal.so.1
> No symbol table info available.
> #13 0x001d99c2 in dbus_connection_dispatch () from /lib/libdbus-1.so.3
> No symbol table info available.
> #14 0x00491e1d in ?? () from /usr/lib/libdbus-glib-1.so.2
> No symbol table info available.
> #15 0x00d80622 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
> No symbol table info available.
> #16 0x00d835ff in ?? () from /lib/libglib-2.0.so.0
> No symbol table info available.
> #17 0x00d839a9 in g_main_loop_run () from /lib/libglib-2.0.so.0
> No symbol table info available.
> #18 0x006cb7e3 in bonobo_main () from /usr/lib/libbonobo-2.so.0
> No symbol table info available.
> #19 0x006c9a49 in bonobo_generic_factory_main_timeout ()
>    from /usr/lib/libbonobo-2.so.0
> No symbol table info available.
> #20 0x006c9ad3 in bonobo_generic_factory_main ()
>    from /usr/lib/libbonobo-2.so.0
> No symbol table info available.
> #21 0x00858041 in panel_applet_factory_main_closure ()
>    from /usr/lib/libpanel-applet-2.so.0
> No symbol table info available.
> #22 0x00858125 in panel_applet_factory_main ()
>    from /usr/lib/libpanel-applet-2.so.0
> No symbol table info available.
> #23 0x0804d493 in main ()
> No symbol table info available.
> #0  0x00aae402 in __kernel_vsyscall ()
> The program is running.  Quit anyway (and detach it)? (y or n) [answered Y;
> input not from terminal]
> 
> 
> ----------- .xsession-errors (410 sec old) ---------------------
> (gnome-panel:3197): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion
> `GTK_IS_MENU_SHELL (menu_shell)' failed
> (gnome-panel:3197): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion
> `GTK_IS_MENU_SHELL (menu_shell)' failed
> (gnome-panel:3197): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion
> `GTK_IS_MENU_SHELL (menu_shell)' failed
> (gnome-panel:3197): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion
> `GTK_IS_MENU_SHELL (menu_shell)' failed
> error getting update info:  Cannot open/read repomd.xml file for repository:
> livna
> ** Message: <info>  You are now connected to the wireless network
> 'SpeedStream1867'.
> Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a
> timestamp of 0 for 0x3600aaf (Assignment)
> Window manager warning: meta_window_activate called by a pager with a 0
> timestamp; the pager needs to be fixed.
> Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a
> timestamp of 0 for 0x3607d2f (OpenOffice)
> Window manager warning: meta_window_activate called by a pager with a 0
> timestamp; the pager needs to be fixed.
> --------------------------------------------------
> 

Comment 6 Philip Withnall 2007-07-26 15:42:28 UTC
(In reply to comment #5)
> I'm not really clear on if I'm supposed to be answering for this ticket or not.
> But just in case, here it is:
> I was doing two things.
> 1. I had just fired up vmware
> 2. I had just plugged in a usb external hard drive
> 
> I hope this helps.

Hi. If you have experienced this bug, then you can certainly comment in this ticket. ;-) What would help is if you could install packages with the debug symbols for libdbus and libhal, reproduce the crash, and then post the stacktrace in bug #446097 (i.e the bug of which this is a duplicate). Thanks. :-)
Comment 7 Kevin Sacry 2007-07-26 16:21:57 UTC
Sorry if this is a stupid question, but what are those packages named?
I will gladly install those and give it a try, but I don't see anything in the repositories that have names that indicate to me that they are debug

[user@host ~]$ yum list | egrep "dbus|hal"
dbus.i386                                1.0.2-6.fc7            installed       
dbus-devel.i386                          1.0.2-6.fc7            installed       
dbus-glib.i386                           0.73-1.fc7             installed       
dbus-glib-devel.i386                     0.73-1.fc7             installed       
dbus-python.i386                         0.81.1-1.fc7           installed       
dbus-sharp.i386                          0.63-6.fc6             installed       
dbus-x11.i386                            1.0.2-6.fc7            installed       
hal.i386                                 0.5.9-8.fc7            installed       
hal-cups-utils.i386                      0.6.9.2-1.fc7          installed       
hal-info.noarch                          20070516-2.fc7         installed       
hal-libs.i386                            0.5.9-8.fc7            installed       
dbus-python-devel.i386                   0.81.1-1.fc7           updates         
dbus-qt.i386                             0.70-1.fc7             fedora          
dbus-qt-devel.i386                       0.70-1.fc7             fedora          
dbus-sharp-devel.i386                    0.63-6.fc6             fedora          
fonts-sinhala.noarch                     0.2.2-1.fc7            fedora          
hal-devel.i386                           0.5.9-8.fc7            fedora          
hal-docs.i386                            0.5.9-8.fc7            fedora          
hal-gnome.i386                           0.5.9-8.fc7            fedora          
halberd.noarch                           0.2.2-2.fc7            updates         
m17n-db-sinhala.noarch                   1.3.4-9.fc7            fedora          
scim-sinhala.i386                        0.2.0-2.fc6            fedora

Thanks,
Kevin
Comment 8 Philip Withnall 2007-07-26 16:29:01 UTC
You need the hal-debuginfo and dbus-debuginfo packages. You might also want to look at this page: http://fedoraproject.org/wiki/StackTraces. Thanks.