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 597565 - Crash in gtk_tree_view_bin_expose
Crash in gtk_tree_view_bin_expose
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
unspecified
Other Linux
: Normal critical
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2009-10-06 15:42 UTC by Pedro Villavicencio
Modified: 2018-02-10 04:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Pedro Villavicencio 2009-10-06 15:42:28 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/gnome-panel/+bug/440547

"I've opened the calendar, select town and tried to add my town. At moment it crashed."

Is this more like a gtk+ crash?

backtrace:

".

Thread 1 (process 2030)

  • #0 gtk_tree_view_bin_expose
    at /build/buildd/gtk+2.0-2.18.1/gtk/gtktreeview.c line 4320
  • #1 gtk_tree_view_bin_expose
    at /build/buildd/gtk+2.0-2.18.1/gtk/gtktreeview.c line 4567
  • #2 gtk_tree_view_bin_expose
    at /build/buildd/gtk+2.0-2.18.1/gtk/gtktreeview.c line 4631
  • #3 IA__gdk_cairo_set_source_pixbuf
    at /build/buildd/gtk+2.0-2.18.1/gdk/gdkcairo.c line 243
  • #4 ??
    from /lib/libglib-2.0.so.0
  • #5 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #8 gtk_marshal_VOID__POINTER_POINTER_UINT_UINT
    at /build/buildd/gtk+2.0-2.18.1/gtk/gtkmarshal.c line 829
  • #9 main
    at main.c line 154

Comment 1 Vincent Untz 2010-01-14 03:01:36 UTC
This looks like a GtkTreeView crash. Do you know which version of gtk+ this was? This would help a bit to identify the code from the line numbers...
Comment 2 Matthias Clasen 2018-02-10 04:36:42 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.