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 423584 - crash in Glade Interface Designer: I was deleteing the Font...
crash in Glade Interface Designer: I was deleteing the Font...
Status: RESOLVED DUPLICATE of bug 325759
Product: glade-legacy
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Damon Chaplin
Damon Chaplin
Depends on:
Blocks:
 
 
Reported: 2007-03-28 04:20 UTC by David C. Chipman
Modified: 2007-04-12 20:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description David C. Chipman 2007-03-28 04:20:21 UTC 
What were you doing when the application crashed?
I was deleteing the Font Slection Dialog from the widget tree


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 10:42:48 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled

Memory status: size: 99692544 vsize: 0 resident: 99692544 share: 0 rss: 18341888 rss_rlim: 0
CPU usage: start_time: 1175054962 rtime: 0 utime: 361 stime: 0 cutime:338 cstime: 0 timeout: 23 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208452896 (LWP 13724)]
(no debugging symbols found)
0x0098c402 in __kernel_vsyscall ()

+ Trace 122799

Thread 1 (Thread -1208452896 (LWP 13724))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 gail_tree_view_new
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #11 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 g_cclosure_marshal_VOID__OBJECT
  • #17 __libc_start_main
    from /lib/libc.so.6
  • #18 g_cclosure_marshal_VOID__OBJECT
  • #0 __kernel_vsyscall 


----------- .xsession-errors (2146 sec old) ---------------------
sox: Can't open input file '/usr/share/gnome/sounds/email.wav': No such file or directory
sox: Can't open input file '/usr/share/gnome/sounds/email.wav': No such file or directory
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00002 (Blender [/)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Compiled with Python version 2.4.
Checking for installed Python... got it!
Saved session recovery to /tmp/quit.blend
Blender quit
sox: Can't open input file '/usr/share/gnome/sounds/email.wav': No such file or directory
sox: Can't open input file '/usr/share/gnome/sounds/email.wav': No such file or directory
sox: Can't open input file '/usr/share/gnome/sounds/email.wav': No such file or directory
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
sox: Can't open input file '/usr/share/gnome/sounds/email.wav': No such file or directory
--------------------------------------------------
Comment 1 André Klapper 2007-04-12 20:46:27 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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