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 640297 - glade crashes if you drag the "< define a new column >" row of List Stores & Tree Stores when no columns are defined
glade crashes if you drag the "< define a new column >" row of List Stores & ...
Status: RESOLVED DUPLICATE of bug 633943
Product: glade
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-01-22 23:02 UTC by Jan Claeys
Modified: 2011-01-23 04:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jan Claeys 2011-01-22 23:02:34 UTC 
Based on an Ubuntu bug report:
https://bugs.edge.launchpad.net/ubuntu/+source/glade-3/+bug/706432

Steps to reproduce this:
* start Glade in GtkBuilder mode and create a "List Store" tree model
* make sure the new list store is selected in the object tree
* in the properties editor, there is a treeview to add columns to the list store; do NOT add any columns
* drag the row that reads "< define a new column >" to the empty space below it in the treeview

This makes Glade "crash" with the following line:

GladeUI-GTK:ERROR:glade-column-types.c:456:columns_changed_idle: assertion failed: (columns)

First discovered by somebody using a wacom tablet, as it's easy then to accidentally drag something when you just try to click.

Tested with 3.7.0 & 3.7.3 official packages on Ubuntu.
Comment 1 Jan Claeys 2011-01-22 23:49:07 UTC 
Actually, that should be versions 3.6.7 & 3.7.3 packages in Ubuntu, not 3.7.0, sorry!

I have also tested 3.6.7 in Fedora 14 with the same crash as a result.
Comment 2 Jan Claeys 2011-01-23 00:13:02 UTC 
Same happens when editing Tree Stores...
Comment 3 Tristan Van Berkom 2011-01-23 04:10:20 UTC 
I fixed this last week in master.

Its a duplicate of some bug...
Comment 4 Tristan Van Berkom 2011-01-23 04:40:25 UTC 

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