Bug 567406 – crash in System Monitor: i opened it to kill a pr...

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 567406 - crash in System Monitor: i opened it to kill a pr...


Summary:	crash in System Monitor: i opened it to kill a pr...


Status:	RESOLVED INCOMPLETE

Product:	system-monitor
Classification:	Core
Component:	general
Version:	2.24.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	System-monitor maintainers
QA Contact:	System-monitor maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-01-11 19:59 UTC by Nikola Yanev
Modified:	2011-11-11 10:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.25/2.26

Description Nikola Yanev 2009-01-11 19:59:13 UTC

Version: 2.24.1

What were you doing when the application crashed?
i opened it to kill a proc.


Distribution: Ubuntu 9.04 (jaunty)
Gnome Release: 2.25.4 2009-01-06 (Ubuntu)
BugBuddy Version: 2.24.1

System: Linux 2.6.28-4-generic #9-Ubuntu SMP Tue Jan 6 19:34:01 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10599003
Selinux: No
Accessibility: Disabled
GTK+ Theme: eGTK
Icon Theme: elementary

Memory status: size: 74518528 vsize: 74518528 resident: 24129536 share: 18427904 rss: 24129536 rss_rlim: 18446744073709551615
CPU usage: start_time: 1231703911 rtime: 340 utime: 264 stime: 76 cutime:13 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-system-monitor'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ba5750 (LWP 26956)]
[New Thread 0xb51e2b90 (LWP 26958)]
(no debugging symbols found)
0xb80ba430 in __kernel_vsyscall ()

+ Trace 211474

Thread 1 (Thread 0xb6ba5750 (LWP 26956))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 <signal handler called>
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 ??
#10 ??
from /usr/lib/libglibmm-2.4.so.1
#11 ??
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#13 ??
from /usr/lib/libglib-2.0.so.0
#14 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#15 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#16 Gtk::Main::run_impl
from /usr/lib/libgtkmm-2.4.so.1
#17 Gtk::Main::run
from /usr/lib/libgtkmm-2.4.so.1
#18 ??
#19 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#20 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(gnome-system-monitor:26956): Gtk-WARNING **: Error parsing gtk-icon-sizes string:
	'panel-menu=24,24:panel=24:gtk-small-toolbar=16,16:gtk-large-toolbar=24,24:gtk-button=24,24'
** ERROR **: Child 26957 failed with status 256
aborting...
/home/gericom/.themes/eGTK/gtk-2.0/panel.rc:54: Unable to locate image file in pixmap_path: "Menubar/menubar-item.png"
/home/gericom/.themes/eGTK/gtk-2.0/panel.rc:57: Background image options specified without filename
/home/gericom/.themes/eGTK/gtk-2.0/panel.rc:107: Unable to locate image file in pixmap_path: "Menubar/menubar-item.png"
/home/gericom/.themes/eGTK/gtk-2.0/panel.rc:110: Background image options specified without filename
/home/gericom/.themes/eGTK/gtk-2.0/gtkrc:147: Unable to locate image file in pixmap_path: "Menu/menubar.png"
/home/gericom/.themes/eGTK/gtk-2.0/gtkrc:150: Background image options specified without filename
(bug-buddy:26973): Gtk-WARNING **: Error parsing gtk-icon-sizes string:
	'panel-menu=24,24:panel=24:gtk-small-toolbar=16,16:gtk-large-toolbar=24,24:gtk-button=24,24'
checking for valid crashreport now
--------------------------------------------------

Comment 1 palfrey 2009-01-12 01:27:52 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!