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 665280 - Editing GtkTreeView causes crash
Editing GtkTreeView causes crash
Status: RESOLVED DUPLICATE of bug 664474
Product: glade
Classification: Applications
Component: user interface
3.10.x
Other Linux
: High critical
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-12-01 12:09 UTC by Paul Sorensen
Modified: 2011-12-01 12:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
glade file saved just prior to editing TreeView (729 bytes, application/x-glade)
2011-12-01 12:09 UTC, Paul Sorensen 		Details

Description Paul Sorensen 2011-12-01 12:09:58 UTC 
Created attachment 202514 [details]
glade file saved just prior to editing TreeView

Consistently reproducible:
1. Create window
2. Add TreeView to window with new default liststore model
3. Edit listore1 to add a single gchar string type column
4. Select TreeView widget in widget tree
5. Right click for menu and select Edit
6. Crash!

Completely precludes the usability of TreeViews

Additionally, Glade likes to crash at other places. But not reproducibly or predictably. However, probability of crash seems to follow complexity of project. Projects containing more widgets are more probable to crash.
However, this crash seems to be consistent no matter the complexity.

My platform is Xubuntu Oneiric using their package for Glade.
Comment 1 André Klapper 2011-12-01 12:27:44 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Tristan Van Berkom 2011-12-01 12:40:58 UTC 
Or... people can please start searching for duplicates before filing bugs...

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