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 665862 - Crash when editing a combobox
Crash when editing a combobox
Status: RESOLVED DUPLICATE of bug 660139
Product: glade
Classification: Applications
Component: general
3.10.x
Other Linux
: Normal blocker
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-12-09 11:51 UTC by Ian Liu Rodrigues
Modified: 2012-01-03 08:34 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Backtrace of the crash (14.18 KB, text/plain)
2011-12-09 11:51 UTC, Ian Liu Rodrigues 		Details

Description Ian Liu Rodrigues 2011-12-09 11:51:44 UTC 
Created attachment 203140 [details]
Backtrace of the crash

Steps to reproduce the bug:
1. Add a combobox as toplevel or inside any container
2. Right-click the combobox and choose "Edit"

Result:
Glade receives a SIGTRAP and closes.

The backtrace is attached.
Comment 1 Micah Carrick 2011-12-19 17:50:18 UTC 
Based on the stacktrace (it's happening to me too) I'm pretty sure this is a duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=664474 which was actually GTK+ bug https://bugzilla.gnome.org/show_bug.cgi?id=660139. Looks like that bug is fixed as of GTK+ 3.2.2.
Comment 2 Paul Sorensen 2011-12-30 12:59:15 UTC 
Confirmed that with GTK+ 3.2.0 and Glade 3.10 on Ubuntu Ocelot, I get the crash as reported. However, with GTK+ 3.3.4 and Glade 3.10.2 on Ubuntu Precise alpha, the problem no longer exists. So looks like this one will be solved by GTK fixes.
Comment 3 Tristan Van Berkom 2012-01-03 08:34:21 UTC 
Yes this is a (very well known now) GTK+ bug, I've been aware of the
fix in GTK+ git master since over than a month now, I mistakenly mentioned
that I expected to see a fix in a GTK+ 3.2.x release, I didn't take care
of backporting the fix myself so I don't know if it will be backported...

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