GNOME Bugzilla – Bug 420615
crash in Terminal: Creating a new profile
Last modified: 2007-03-21 18:52:59 UTC
Version: 2.16.0 What were you doing when the application crashed? Creating a new profile 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.19-1.2911.6.5.fc6 #1 SMP Sun Mar 4 16:41:13 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 136060928 vsize: 0 resident: 136060928 share: 0 rss: 30683136 rss_rlim: 0 CPU usage: start_time: 1174401070 rtime: 0 utime: 907 stime: 0 cutime:862 cstime: 0 timeout: 45 it_real_value: 0 frequency: 13 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 -1208637744 (LWP 3327)] [New Thread -1217082480 (LWP 3406)] (no debugging symbols found) 0x004f7402 in __kernel_vsyscall ()
+ Trace 120417
Thread 1 (Thread -1208637744 (LWP 3327))
----------- .xsession-errors --------------------- (gnome-terminal:3327): Gtk-CRITICAL **: gtk_tree_model_get_iter: assertion `path != NULL' failed (gnome-terminal:3327): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `VALID_ITER (iter, list_store)' failed (gnome-terminal:3327): Gtk-CRITICAL **: gtk_tree_model_get_iter: assertion `path != NULL' failed (gnome-terminal:3327): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `VALID_ITER (iter, list_store)' failed (gnome-terminal:3327): Gtk-CRITICAL **: gtk_tree_model_get_iter: assertion `path != NULL' failed (gnome-terminal:3327): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `VALID_ITER (iter, list_store)' failed ** (gnome-terminal:3327): CRITICAL **: terminal_profile_new: assertion `terminal_profile_lookup (name) == NULL' failed ** (bug-buddy:17882): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
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 405239 ***