abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: glade-3 component: glade3 crash_function: raise executable: /usr/bin/glade-3 kernel: 2.6.36-0.16.rc3.git0.fc14.x86_64 package: glade3-3.7.1-2.fc14 rating: 4 reason: Process /usr/bin/glade-3 was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1285913921 uid: 500 How to reproduce ----- 1. start with yer basic Window object 2. drop in a Notebook container 3. don parachute
Created attachment 450947 [details] File: backtrace
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. start glade-3 2. add Dialog Box Comment ----- glade-3 is very unstable. Basically just adding any of the basic widgets, such as Dialog Box, About Dialog, or File Chooser will crash it.
duplicate of bug #646111
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start Glade 2. Add a window 3. Add a notebook container to the window 4. Crash
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start Glade-3 2. add a new GtkWindow called wndMain 3. add a vbox of 3 elements called vbxMain 4. add a label in the first line of vbxMain 5. click to add the GtkNotebook Glade close when clicking this last icon Comment ----- Bug also happen when : 1. Start Glade-3 2. add a new GtkWindow 3. click to add the GtkNotebook Glade close when clicking this last icon
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open glade3 2. Click on "Dialog Box" widget in Toplevels to add 3. Crash!
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open Glade-3. 2. In component palette on the right, in "Toplevels" section, click on any dialog's button, other than "Window". 3. Glade crashes. Comment ----- I've caught also another crash case - when clicking on any folded palette section, the X-server gets restarted. It didn't get caught by ABRT, so I don't have a stacktrace for it. I'll provide you with it if you give me instructions how to get it.
There are instructions for Xorg server debugging here: http://wiki.x.org/wiki/Development/Documentation/ServerDebugging The "Debugging on one machine" section on that page can be really helpful.
*** This bug has been marked as a duplicate of bug 646111 ***