GNOME Bugzilla – Bug 494554
crash in Terminal: Creating a new profile b...
Last modified: 2007-11-27 02:35:24 UTC
Version: 2.18.1 What were you doing when the application crashed? Creating a new profile based upon default (second profile created in a row). Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 100028416 vsize: 100028416 resident: 29839360 share: 20508672 rss: 29839360 rss_rlim: 4294967295 CPU usage: start_time: 1194399223 rtime: 354 utime: 309 stime: 45 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 -1209042704 (LWP 3338)] [New Thread -1215943792 (LWP 3345)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176012
Thread 1 (Thread -1209042704 (LWP 3338))
----------- .xsession-errors --------------------- [00000289] main playlist: stopping playback lirc: cannot initialise - disabling remote control lirc: maybe lircd isn't running or you can't connect to the socket? CDROMREADTOCHDR: No medium found WARN: open (/dev/cdrom): No medium found error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again ** Message: <info> You are now connected to the wireless network 'tmobile'. ** Message: <info> Activating VPN connection 'Boston'. CalDAV Eplugin starting up ... ** (evolution:6632): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:6632): DEBUG: mailto URL program: evolution ** (gnome-terminal:3338): 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 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 499797 ***