GNOME Bugzilla – Bug 491907
crash in Terminal: going poop
Last modified: 2007-11-02 22:09:23 UTC
Version: 2.18.0 What were you doing when the application crashed? going poop Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 85753856 vsize: 85753856 resident: 18206720 share: 11579392 rss: 18206720 rss_rlim: 4294967295 CPU usage: start_time: 1193776585 rtime: 76 utime: 67 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-terminal' (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 -1208481552 (LWP 14176)] [New Thread -1214854256 (LWP 14184)] (no debugging symbols found) 0x0077f402 in __kernel_vsyscall ()
+ Trace 174044
Thread 1 (Thread -1208481552 (LWP 14176))
----------- .xsession-errors --------------------- (nautilus:10792): libgnomevfs-CRITICAL **: gnome_vfs_uri_get_parent: assertion `uri != NULL' failed (nautilus:10792): libgnomevfs-CRITICAL **: gnome_vfs_uri_unref: assertion `uri != NULL' failed (nautilus:10792): libgnomevfs-CRITICAL **: gnome_vfs_uri_get_parent: assertion `uri != NULL' failed (nautilus:10792): libgnomevfs-CRITICAL **: gnome_vfs_uri_unref: assertion `uri != NULL' failed (nautilus:10792): libgnomevfs-CRITICAL **: gnome_vfs_uri_get_parent: assertion `uri != NULL' failed (nautilus:10792): libgnomevfs-CRITICAL **: gnome_vfs_uri_unref: assertion `uri != NULL' failed ** (gnome-terminal:14136): CRITICAL **: terminal_profile_new: assertion `terminal_profile_lookup (name) == NULL' failed ** (gnome-terminal:14176): CRITICAL **: terminal_profile_new: assertion `terminal_profile_lookup (name) == NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 457825 ***