GNOME Bugzilla – Bug 471462
crash in Terminal: i configure a new profil...
Last modified: 2007-09-18 10:19:26 UTC
Version: 2.18.1 What were you doing when the application crashed? i configure a new profile from a existant profile 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.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 95932416 vsize: 95932416 resident: 30535680 share: 21254144 rss: 30535680 rss_rlim: 4294967295 CPU usage: start_time: 1188370713 rtime: 917 utime: 842 stime: 75 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 -1209050896 (LWP 3162)] [New Thread -1215226992 (LWP 3167)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 158790
Thread 1 (Thread -1209050896 (LWP 3162))
----------- .xsession-errors (6 sec old) --------------------- (evolution:2982): libebook-WARNING **: ENCODING specified twice warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 30c9ecf8 (evolution:2982): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) BBDB spinning up... (evolution:2982): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa6bf020' (evolution:2982): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa6bf140' inside eab_vcard_control_new (gnome-terminal:3162): Vte-WARNING **: Aucune manipulation définie pour la séquence de contrôle « device-control-string ». ** (gnome-terminal:3162): CRITICAL **: terminal_profile_new: assertion `terminal_profile_lookup (name) == NULL' failed --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 444068 ***