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 323394 - glade- segfaults when selecting a widget
glade- segfaults when selecting a widget
Status: RESOLVED DUPLICATE of bug 322044
Product: glade-legacy
Classification: Deprecated
Component: general
2.12.x
Other other
: Normal critical
: ---
Assigned To: Damon Chaplin
Damon Chaplin
Depends on:
Blocks:
 
 
Reported: 2005-12-06 19:03 UTC by Gaute Hope
Modified: 2005-12-06 22:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gaute Hope 2005-12-06 19:03:03 UTC
Distribution: Slackware Slackware 10.2.0
Package: glade
Severity: Normal
Version: GNOME2.12.1 2.12.1
Gnome-Distributor: Dropline GNOME
Synopsis: glade- segfaults when selecting a widget
Bugzilla-Product: glade
Bugzilla-Component: general
Bugzilla-Version: 2.12.1
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
When I have openend a project or created one. It crashes after a while,
normally right after I have selected a widget in my new window. It is a
bit hard to know exactly when it crashes. I can't get anything done
because it happens so fast after startup.

Steps to reproduce the crash:
1. Open a project
2. Open a window
3. Select a widget

Expected Results:
Not to exit

How often does this happen?
Every time. But sometimes it doesn't crash so fast.

Additional Information:
I have tried different versions of glade, but with no results.
dropline-gnome's, cvs, some earlier 2.10 slackware packages. I also
tried to use the cvs version of libglade.


Debugging Information:

Backtrace was generated from '/usr/bin/glade-2'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225627968 (LWP 7745)]
[New Thread -1241085008 (LWP 7753)]
[Thread debugging using libthread_db enabled]
[New Thread -1225627968 (LWP 7745)]
[New Thread -1241085008 (LWP 7753)]
[New Thread -1240822864 (LWP 7752)]
[Thread debugging using libthread_db enabled]
[New Thread -1225627968 (LWP 7745)]
[New Thread -1241085008 (LWP 7753)]
0xb71d5411 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 ??
  • #3 ??
  • #4 ??
  • #5 ??
  • #6 pthread_mutex_lock
    from /lib/tls/libpthread.so.0




------- Bug moved to this database by unknown@gnome.bugs 2005-12-06 19:03 UTC -------


Unknown version 2.12.1 in product glade.  Setting version to "2.12.x".

Comment 1 Damon Chaplin 2005-12-06 22:01:19 UTC
Most crashes in Glade lately have been caused by the gail accessibility library.
Do you know what version of gail you have?

You could try moving the gail library temporarily to see if that fixes the
problem. (Glade will still work without it.)
On Fedora it is in:
  /usr/lib/gtk-2.0/modules/libgail.so
Comment 2 Gaute Hope 2005-12-06 22:46:58 UTC
This seems to fix it. I also recive this output in the terminal when I run
glade(with libgail*)

gaute@eple:/usr/lib/gtk-2.0/modules$ glade-2

(glade-2:31568): Gdk-WARNING **: locale not supported by Xlib

(glade-2:31568): Gdk-WARNING **: cannot set locale modifiers
GTK Accessibility Module initialized

(glade-2:31568): GLib-GObject-WARNING **: invalid uninstantiatable type
`<invalid>' in cast to `GtkAccessible'

(gnome_segv:31571): Gdk-WARNING **: locale not supported by Xlib

(gnome_segv:31571): Gdk-WARNING **: cannot set locale modifiers
GTK Accessibility Module initialized
gaute@eple:/usr/lib/gtk-2.0/modules$

(when using glade-2.10.. it didn't show the 'report to developers' dialog but
said seg fault)

--
$ pkg-config gail --modversion
1.8.6
$ pkg-config libgail-gnome --modversion
1.1.1
Comment 3 Damon Chaplin 2005-12-06 22:56:49 UTC
Yes, this looks like a duplicate of bug 322044, which was fixed in gail 1.8.7.

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