synaptic Gtk-CRITICAL gtktreeview.c: line 4881 (gtk_tree_view_bin_expose): assertion `has_next' failed

Bug #315827 reported by Alan Jenkins
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: synaptic

Performing certain operations in synaptic causes the following message:

(synaptic:8990): Gtk-CRITICAL **: file /build/buildd/gtk+2.0-2.14.4/gtk/gtktreeview.c: line 4881 (gtk_tree_view_bin_expose): assertion `has_next' failed.
There is a disparity between the internal view of the GtkTreeView,
and the GtkTreeModel. This generally means that the model has changed
without letting the view know. Any display from now on is likely to
be incorrect.

I can reproduce this by:
1. Open synaptic
2. Search for "kdebase"
3. Mark for installation "kdebase-dbg" (and it's dependencies)
4. Switch to "Custom Filters->Marked Changes"
5. Unmark "kdepimlibs-dbg" and its dependencies (kdelibs5-dbg and libqt4-dbg)

That's how I found it, but I think it's pretty generic. It also happens if I install "3dchess", without searching, automatically selecting it's dependency "xaw3dg", then go into "marked changes" and unmark xaw3dg (and hence 3dchess).

Kubuntu 8.10, fully updated
synaptic 0.62.1ubuntu10
libgtk2.0-0 2.14.4-0ubuntu1

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report.

I can't reproduce it with the latest release. Is it still an issue for you ?

Changed in synaptic (Ubuntu):
status: New → Incomplete
Revision history for this message
Alan Jenkins (aj504) wrote :

I can still reproduce it using the 3dchess example. Note that the message is on stdout/stderr - you have to run synaptic from a terminal in order to see it.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Confirmed with the 3dchess example in lucid.

Thanks.

Changed in synaptic (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Triaged
Revision history for this message
Robert Roth (evfool) wrote :

Still happening on Quantal.

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.