Bug 402092 – crash in Terminal: creating new profile

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 402092 - crash in Terminal: creating new profile


Summary:	crash in Terminal: creating new profile


Status:	RESOLVED DUPLICATE of bug 324227

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-29 13:20 UTC by ilijak
Modified:	2007-01-30 17:58 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description ilijak 2007-01-29 13:20:54 UTC

Version: 2.16.1

What were you doing when the application crashed?
creating new profile


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 90431488 vsize: 0 resident: 90431488 share: 0 rss: 21241856 rss_rlim: 0
CPU usage: start_time: 1170074580 rtime: 0 utime: 1067 stime: 0 cutime:999 cstime: 0 timeout: 68 it_real_value: 0 frequency: 553

Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226508624 (LWP 10185)]
[New Thread -1246053472 (LWP 10189)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 106277

Thread 1 (Thread -1226508624 (LWP 10185))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 ??
#6 _IO_stdin_used
#7 _IO_stdin_used
#8 ??
#9 ??
#10 ??
#0 __kernel_vsyscall

Comment 1 Mariano Suárez-Alvarez 2007-01-29 20:52:08 UTC

Did you perchance use a profile name which coincides with an existing profile?

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 ilijak 2007-01-30 16:38:17 UTC

(In reply to comment #1)
> Did you perchance use a profile name which coincides with an existing profile?

Probably yes. I had created a profile, than by accident instead of creating a new one I renamed the old one. Then when I tried to create new profile with name of old (i.e. renamed) profile and that caused a crash.

Comment 3 Mariano Suárez-Alvarez 2007-01-30 17:58:27 UTC

Ok. Then this is a dup of bug 324227.

Thanks for the report!

*** This bug has been marked as a duplicate of 324227 ***