GNOME Bugzilla – Bug 425836
crash in XChat-GNOME IRC Chat: Just starting XChat-GNOM...
Last modified: 2007-06-13 06:36:47 UTC
Version: 0.17 What were you doing when the application crashed? Just starting XChat-GNOME from the menu. Distribution: Fedora release 6.92 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.3038.fc7 #1 SMP Sat Mar 31 19:51:12 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299903 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 23658496 vsize: 23658496 resident: 7811072 share: 6680576 rss: 7811072 rss_rlim: 4294967295 CPU usage: start_time: 1175601299 rtime: 6 utime: 3 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/xchat-gnome' (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 -1208215840 (LWP 18952)] (no debugging symbols found) 0x00904402 in __kernel_vsyscall ()
+ Trace 124605
Thread 1 (Thread -1208215840 (LWP 18952))
----------- .xsession-errors (9 sec old) --------------------- Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory (xchat-gnome:18952): libglade-CRITICAL **: glade_xml_get_widget: assertion `self != NULL' failed (xchat-gnome:18952): libglade-CRITICAL **: glade_xml_get_widget: assertion `self != NULL' failed (xchat-gnome:18952): libglade-CRITICAL **: glade_xml_get_widget: assertion `self != NULL' failed (xchat-gnome:18952): Gtk-CRITICAL **: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed (xchat-gnome:18952): Gtk-CRITICAL **: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 85794 [details] Bug Buddy Dump with debuginfo packages installed
I have added the dump generated by Bug Buddy, when xchat-gnome is started. I have installed the following debuginfo packages. gtk2-debuginfo-2.10.11-3.fc7 gnome-vfs2-debuginfo-2.18.0.1-1.fc7 glib2-debuginfo-2.12.11-1.fc7 xchat-gnome-debuginfo-0.17-2.fc7
*** Bug 426502 has been marked as a duplicate of this bug. ***
*** Bug 427010 has been marked as a duplicate of this bug. ***
*** Bug 427172 has been marked as a duplicate of this bug. ***
*** Bug 427387 has been marked as a duplicate of this bug. ***
*** Bug 427712 has been marked as a duplicate of this bug. ***
*** Bug 427874 has been marked as a duplicate of this bug. ***
*** Bug 429448 has been marked as a duplicate of this bug. ***
*** Bug 429228 has been marked as a duplicate of this bug. ***
*** Bug 429497 has been marked as a duplicate of this bug. ***
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report. 2007-04-14 David Trowbridge <trowbrds@gmail.com> * src/fe-gnome/setup-dialog.c: - Fix some bogus widget handling. Bug #425836.
Tested latest svn, and it is working very well. Thank you for the fix!
*** Bug 430442 has been marked as a duplicate of this bug. ***
*** Bug 430569 has been marked as a duplicate of this bug. ***
*** Bug 446287 has been marked as a duplicate of this bug. ***