GNOME Bugzilla – Bug 124841
Creating a new Terminal profile
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Unknown Package: gnome-terminal Severity: normal Version: GNOME2.4.0 2.4.0.1 Gnome-Distributor: Gentoo Linux Synopsis: Creating a new Terminal profile Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.4.0.1 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Terminal-window crashes during creation of new profile Steps to reproduce the crash: 1. On desktop click right mouse button and select Open Terminal 2. Add new profile using Default -profile as a draft 3. The name of the new profile contains & -character Expected Results: Window opens where you can modify just created profile How often does this happen? Every time Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 7202)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x40571187 in waitpid () from /lib/libpthread.so.0
+ Trace 40953
Thread 1 (Thread 16384 (LWP 7202))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-17 10:48 ------- Unknown version 2.4.0.1 in product gnome-terminal. Setting version to the default, "unspecified". Reassigning to the default owner of the component, gnome-terminal-maint@bugzilla.gnome.org.
What was the name of the profile you tried to create? If this is reproducible, could you paste any information relevant to this crash appearing ing your ~/.xsession-errors file?
I first notest this when I tried to create profile named B&W. I tested creating profiles a bit more and it seems that it does not matter what the name of the new profile is as long as it contains atleast some of these chars: !"#¤%&/()= Also if the name is only one of those characters I mentioned earlier it crashes the Terminal. Nevertheless when I open the Terminal again I can use the profile OK even it has crashed before and I can change the name and other setting without crashing it again. No information will be generated to .xsession-errors -file.
Arghh, I couldn't reproduce this... but only because this has been fixed!
*** This bug has been marked as a duplicate of 122349 ***