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 126533 - Segmentation Fault
Segmentation Fault
Status: RESOLVED DUPLICATE of bug 105694
Product: glade-legacy
Classification: Deprecated
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Damon Chaplin
Damon Chaplin
Depends on:
Blocks:
 
 
Reported: 2003-11-09 06:00 UTC by olsongd
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description olsongd 2003-11-09 06:00:17 UTC
Package: glade
Severity: normal
Version: 1.1.3
Synopsis: Segmentation Fault
Bugzilla-Product: glade
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
Double clicking on a widget caused a segmentation fault; I was double
clicking on a button.

Steps to reproduce the problem:
1. Create a Window
2. Drop a button on the window
3. double click the button

Actual Results:
Segmentation fault

Expected Results:
not sure but certainly not a fault

How often does this happen?
Everytime I do it.

Additional Information:




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 1086105664 (LWP 7560)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...0xffffe002
in ??
    ()

Thread 1 (Thread 1086105664 (LWP 7560))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gb_image_new
  • #4 gb_image_new
  • #5 gb_widget_show_properties
  • #6 editor_select_widget
  • #7 editor_new_placeholder
  • #8 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 gtk_widget_send_expose
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #17 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #22 main
  • #23 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-09 01:00 -------

Unknown version 1.1.x in product glade. Setting version to the default, "unspecified".
The original reporter (olsongd@comcast.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, damon@gnome.org.

Comment 1 Damon Chaplin 2003-11-09 14:07:13 UTC
Try upgrading to Glade 2.0.1. The problem is probably fixed there:

  http://ftp.gnome.org/pub/GNOME/sources/glade/2.0/


Are you using RedHat 9?
Comment 2 Damon Chaplin 2003-11-30 11:44:44 UTC
I think we have to assume this is a duplicate of bug #105694.
But reopen if you still see the problem in Glade > 2.0.1.

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