Bug 571337 – gnome-system-monitor crashes on File Systems tab with external hard drive mounted

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 571337 - gnome-system-monitor crashes on File Systems tab with external hard drive mounted


Summary:	gnome-system-monitor crashes on File Systems tab with external hard drive mou...


Status:	RESOLVED DUPLICATE of bug 567253

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-02-11 19:30 UTC by Mark D.
Modified:	2011-11-11 10:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description Mark D. 2009-02-11 19:30:02 UTC

Steps to reproduce:
1. Plug in 1TB WD MyBook external hard drive (usb)
2. Run gnome-system-monitor
3. Click on the File Systems tab
4. CRASH!

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

[?1034hUsing host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x7f58b05c2750 (LWP 22620)]
0x00007f58ab31e3b5 in waitpid () from /lib/libc.so.6

+ Trace 212476

Thread 1 (Thread 0x7f58b05c2750 (LWP 22620))

#0 waitpid
from /lib/libc.so.6
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 __assert_fail
from /lib/libc.so.6
#8 _cairo_error
at cairo.c line 87
#9 cairo_clip
at cairo.c line 2413
#10 ??
from /usr/lib64/gtk-2.0/2.10.0/engines/libclearlooks.so
#11 ??
from /usr/lib64/gtk-2.0/2.10.0/engines/libclearlooks.so
#12 gtk_cell_renderer_progress_render
at gtkcellrendererprogress.c line 601
#13 gtk_tree_view_column_cell_process_action
at gtktreeviewcolumn.c line 2802
#14 _gtk_tree_view_column_cell_render
at gtktreeviewcolumn.c line 3135
#15 gtk_tree_view_expose
at gtktreeview.c line 4714
#16 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 ??
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gtk_widget_event_internal
at gtkwidget.c line 4745
#22 IA__gtk_main_do_event
at gtkmain.c line 1553
#23 gdk_window_process_updates_internal
at gdkwindow.c line 2598
#24 IA__gdk_window_process_all_updates
at gdkwindow.c line 2664
#25 gtk_container_idle_sizer
at gtkcontainer.c line 1309
#26 gdk_threads_dispatch
at gdk.c line 473
#27 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#28 ??
from /usr/lib/libglib-2.0.so.0
#29 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#30 IA__gtk_main
at gtkmain.c line 1200
#31 main
at procman.cpp line 742
#32 __libc_start_main
from /lib/libc.so.6
#33 _start
#0 waitpid
from /lib/libc.so.6


Other information:
Command line Output:
gnome-system-monitor: cairo.c:87: _cairo_error: Assertion `(status != CAIRO_STATUS_SUCCESS && status <= CAIRO_STATUS_INVALID_WEIGHT)' failed.

Comment 1 Benoît Dejean 2009-02-11 20:43:02 UTC

It looks like a cairo/theme bug.
If you can reproduce it at will, could you please try it with another gtk theme (not based on clearlooks) ?

Comment 2 Mark D. 2009-02-12 07:20:35 UTC

Good call, it doesn't crash when I use either Industrial or Glory-Simplex themes.

Comment 3 palfrey 2009-02-12 11:47:50 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

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