gnome-system-log Gtk-CRITICAL Segmentation fault

Bug #235897 reported by ethanay
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-utils (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-utils

Description: Ubuntu 8.04
Release: 8.04
2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux
Dell XPS m1330 w/latest updates

terminal output:

~$ gnome-system-log

(gnome-system-log:15623): Gtk-CRITICAL **: gtk_tree_selection_real_modify_range: assertion `start_node != NULL' failed

(gnome-system-log:15623): Gtk-CRITICAL **: gtk_tree_view_scroll_to_cell: assertion `tree_view->priv->tree != NULL' failed
Segmentation fault
--------------------------------
steps to reproduce:
open system log viewer
add /var/log/pm-suspend.log
use arrow keys, tab, shift-tab to navigate and ctrl-f to filter
eventually, the gnome-system-monitor will crash with a segfault

Revision history for this message
ethanay (ethan-y-us) wrote :
Download full text (9.9 KiB)

gnome-utils | 2.20.0.1-1ubuntu5 | http://us.archive.ubuntu.com hardy/main Packages
--------------------------------
output from the last crash
-------------------------------
:~$ gnome-system-log

(gnome-system-log:16087): Gtk-CRITICAL **: _gtk_tree_view_find_path: assertion `node != NULL' failed

(gnome-system-log:16087): Gtk-CRITICAL **: _gtk_tree_view_find_path: assertion `node != NULL' failed

(gnome-system-log:16087): Gtk-CRITICAL **: _gtk_tree_view_find_path: assertion `node != NULL' failed

(gnome-system-log:16087): Gtk-CRITICAL **: gtk_tree_row_reference_new_proxy: assertion `path->depth > 0' failed

(gnome-system-log:16087): Gtk-CRITICAL **: gtk_tree_row_reference_new_proxy: assertion `path->depth > 0' failed

(gnome-system-log:16087): Gtk-CRITICAL **: gtk_tree_row_reference_new_proxy: assertion `path->depth > 0' failed

(gnome-system-log:16087): Gtk-CRITICAL **: _gtk_tree_view_find_path: assertion `node != NULL' failed

(gnome-system-log:16087): Gtk-CRITICAL **: _gtk_tree_view_find_path: assertion `node != NULL' failed

(gnome-system-log:16087): Gtk-CRITICAL **: gtk_tree_row_reference_new_proxy: assertion `path->depth > 0' failed

(gnome-system-log:16087): Gtk-CRITICAL **: gtk_tree_row_reference_new_proxy: assertion `path->depth > 0' failed

(gnome-system-log:16087): Gtk-CRITICAL **: gtk_tree_row_reference_new_proxy: assertion `path->depth > 0' failed

(gnome-system-log:16087): Gtk-CRITICAL **: gtk_tree_row_reference_new_proxy: assertion `path->depth > 0' failed
^[[Z
(gnome-system-log:16087): Gtk-CRITICAL **: gtk_tree_selection_real_modify_range: assertion `start_node != NULL' failed

(gnome-system-log:16087): Gtk-CRITICAL **: gtk_tree_view_scroll_to_cell: assertion `tree_view->priv->tree != NULL' failed
*** glibc detected *** gnome-system-log: double free or corruption (out): 0x0849dae0 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb73caa85]
/lib/tls/i686/cmov/libc.so.6(cfree+0x90)[0xb73ce4f0]
/usr/lib/libglib-2.0.so.0(g_free+0x31)[0xb75068b1]
/usr/lib/libgtk-x11-2.0.so.0(gtk_tree_path_free+0x29)[0xb7b57049]
/usr/lib/libgtk-x11-2.0.so.0[0xb7b7f1d5]
/usr/lib/libgtk-x11-2.0.so.0[0xb7a784dc]
/usr/lib/libgobject-2.0.so.0[0xb7589079]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x129)[0xb758a759]
/usr/lib/libgobject-2.0.so.0[0xb759eea0]
/usr/lib/libgobject-2.0.so.0(g_signal_emitv+0x13e)[0xb75a0d9e]
/usr/lib/libgtk-x11-2.0.so.0[0xb7995ff1]
/usr/lib/libgtk-x11-2.0.so.0[0xb799654c]
/usr/lib/libgtk-x11-2.0.so.0[0xb79966fe]
/usr/lib/libgtk-x11-2.0.so.0(gtk_bindings_activate_event+0x10b)[0xb799690b]
/usr/lib/libgtk-x11-2.0.so.0[0xb7b7c71b]
/usr/lib/libgtk-x11-2.0.so.0[0xb7a788d4]
/usr/lib/libgobject-2.0.so.0[0xb7589079]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x1ff)[0xb758a82f]
/usr/lib/libgobject-2.0.so.0[0xb759eea0]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x5fe)[0xb75a064e]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x29)[0xb75a0c59]
/usr/lib/libgtk-x11-2.0.so.0[0xb7b97667]
/usr/lib/libgtk-x11-2.0.so.0(gtk_window_propagate_key_event+0x110)[0xb7ba8df0]
/usr/lib/libgtk-x11-2.0.so.0[0xb7babf5c]
/usr/lib/libgtk-x11-2.0.so.0[0xb7a788d4]
/usr/lib/libgobject-2.0.so.0[0xb7589079]
/usr/lib/libgobject-2.0.so.0(g_cl...

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gnome-utils:
status: New → Invalid
Revision history for this message
ethanay (ethan-y-us) wrote :

I am running Ubuntu (gnome) desktop. After following your advice no crash report was generated in /var/crash

In addition, I have tried enabling the "automated crash reporting" service and it does not work. Manually launching "report a problem" doesn't do a thing.

apport-gtk is installed but my system says it is missing, even after attempted reinstallation.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.