Bug 463901 – gnome system log crashes under glib2.14/gtk+2.11.6

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 463901 - gnome system log crashes under glib2.14/gtk+2.11.6


Summary:	gnome system log crashes under glib2.14/gtk+2.11.6


Status:	RESOLVED DUPLICATE of bug 497489

Product:	gtk+
Classification:	Platform
Component:	Widget: GtkComboBox
Version:	2.11.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	gtk-bugs
QA Contact:	gtk-bugs

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-06 07:44 UTC by Hussam Al-Tayeb
Modified:	2007-11-30 18:27 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Attachments
Full backtrace. (43.29 KB, text/plain) 2007-08-06 07:53 UTC, Hussam Al-Tayeb	Details
New backtrace (20.95 KB, text/plain) 2007-10-25 17:43 UTC, Hussam Al-Tayeb	Details
trace under gtk+ 2.12.2 and gnome 2.20.2 (50.26 KB, text/plain) 2007-11-30 07:19 UTC, Hussam Al-Tayeb	Details

Description Hussam Al-Tayeb 2007-08-06 07:44:09 UTC

Steps to reproduce:
1. open gnome-system-log
2. click on different log files that are monitored.
3. On the 3rd file, gnome-system-log crashes.


Stack trace:
gdb gnome-system-log
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/gnome-system-log 
[Thread debugging using libthread_db enabled]
[New Thread -1225914688 (LWP 4229)]

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

Program received signal SIGSEGV, Segmentation fault.

+ Trace 153128

Thread NaN (LWP 4229)

#0 logview_version_selector_changed
at logview.c line 435
#1 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#2 IA__g_closure_invoke
at gclosure.c line 490
#3 signal_emit_unlocked_R
at gsignal.c line 2440
#4 IA__g_signal_emit_valist
at gsignal.c line 2199
#5 IA__g_signal_emit
at gsignal.c line 2243
#6 gtk_combo_box_set_active_internal
at gtkcombobox.c line 4739
#7 IA__gtk_combo_box_set_active
at gtkcombobox.c line 4674
#8 logview_update_version_bar
at log_repaint.c line 239
#9 logview_select_log
at logview.c line 217
#10 loglist_selection_changed
at loglist.c line 253
#11 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#12 IA__g_closure_invoke
at gclosure.c line 490
#13 signal_emit_unlocked_R
at gsignal.c line 2440
#14 IA__g_signal_emit_valist
at gsignal.c line 2199
#15 IA__g_signal_emit
at gsignal.c line 2243
#16 _gtk_tree_selection_internal_select_node
at gtktreeselection.c line 1409
#17 gtk_tree_view_real_set_cursor
#18 gtk_tree_view_button_press
at gtktreeview.c line 2679
#19 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#20 g_type_class_meta_marshal
at gclosure.c line 567
#21 IA__g_closure_invoke
at gclosure.c line 490
#22 signal_emit_unlocked_R
at gsignal.c line 2478
#23 IA__g_signal_emit_valist
at gsignal.c line 2209
#24 IA__g_signal_emit
at gsignal.c line 2243
#25 gtk_widget_event_internal
at gtkwidget.c line 4674
#26 IA__gtk_propagate_event
at gtkmain.c line 2317
#27 IA__gtk_main_do_event
at gtkmain.c line 1537
#28 gdk_event_dispatch
at gdkevents-x11.c line 2351
#29 IA__g_main_context_dispatch
at gmain.c line 2061
#30 g_main_context_iterate
at gmain.c line 2694
#31 IA__g_main_loop_run
at gmain.c line 2898
#32 IA__gtk_main
at gtkmain.c line 1144
#33 main
at main.c line 203



Other information:

Comment 1 Hussam Al-Tayeb 2007-08-06 07:53:44 UTC

Created attachment 93138 [details]
Full backtrace.

Attached full backtrace.

Comment 2 Emmanuele Bassi (:ebassi) 2007-08-06 08:01:45 UTC

the code in the system log viewer did not change and from what I can see, it's doing a perfectly legitimate call:

  gtk_combo_box_set_active (GTK_COMBO_BOX (logview->version_selector),
                            log->current_version);

where "log->current_version" in your stack trace is 0, which is a valid value - as the combo box in question will always have a first element:

  gtk_combo_box_append_text (GTK_COMBO_BOX (logview->version_selector),
                             _("Current"));

looks more like a bug in gtk+ itself, so re-assigning to get an opinion.

Comment 3 Jan de Groot 2007-08-06 08:10:14 UTC

log is actually NULL, so log->current_version is a nullpointer dereference.

Comment 4 Emmanuele Bassi (:ebassi) 2007-08-06 09:15:55 UTC

if log was NULL then it wouldn't even have reached that part of the function, since we check for this condition at the very beginning. the function is logview_update_version_bar(), at line 205 of log_repaint.c in gnome-utils/logview.

Comment 5 Hussam Al-Tayeb 2007-08-15 09:53:29 UTC

Crash is still there in latest gtk+ svn

Comment 6 Pedro Villavicencio 2007-08-16 01:47:32 UTC

Also an Ubuntu bug about this here: https://bugs.launchpad.net/gnome-utils/+bug/132637

Comment 7 Hussam Al-Tayeb 2007-08-23 22:46:56 UTC

Seems to be fixed in gtk+ svn r18682

Comment 8 Sebastien Bacher 2007-10-07 20:26:10 UTC

The ubuntu bug has GNOME 2.20 duplicates

Comment 9 Hussam Al-Tayeb 2007-10-07 20:33:48 UTC

Sorry but why did you reopen? This is already fixed in 2.12.0

Comment 10 Hussam Al-Tayeb 2007-10-25 17:43:01 UTC

Created attachment 97865 [details]
New backtrace

It seems to be crashing again in gtk+ 2.12.1
I'm attaching a new backtrace.

Please someone confirm the bug.

Comment 11 Hussam Al-Tayeb 2007-11-30 07:19:34 UTC

Created attachment 99885 [details]
trace under gtk+ 2.12.2 and gnome 2.20.2

Still crashes under gtk+ 2.12.2

Comment 12 Matthias Clasen 2007-11-30 14:05:44 UTC

Check out the patch in bug 497489

Comment 13 Hussam Al-Tayeb 2007-11-30 18:05:17 UTC

(In reply to comment #12)
> Check out the patch in bug 497489
> 

Yes, that patch in bug 497489 does fix it. Should I mark this bug as a duplicate of bug 497489?

Comment 14 Matthias Clasen 2007-11-30 18:15:54 UTC

Yes, please

Comment 15 Hussam Al-Tayeb 2007-11-30 18:27:31 UTC


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