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 402283 - crash in Terminal: Selecting Add in the pro...
crash in Terminal: Selecting Add in the pro...
Status: RESOLVED DUPLICATE of bug 324227
Product: gnome-terminal
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-29 23:24 UTC by druid
Modified: 2007-01-29 23:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description druid 2007-01-29 23:24:35 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Selecting Add in the profile manager for Gnome Terminal, based on another profile.


Distribution: Slackware Slackware 11.0.0
Gnome Release: 2.16.2 2006-11-22 (Dropline GNOME)
BugBuddy Version: 2.16.0

Memory status: size: 26361856 vsize: 0 resident: 45998080 share: 0 rss: 26361856 rss_rlim: 0
CPU usage: start_time: 1170107269 rtime: 0 utime: 2042 stime: 0 cutime:1849 cstime: 0 timeout: 193 it_real_value: 0 frequency: 7

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 16384 (LWP 3653)]
[New Thread 32769 (LWP 3730)]
[New Thread 16386 (LWP 3732)]
(no debugging symbols found)
0x406b862b in waitpid () from /lib/libpthread.so.0

+ Trace 106418

Thread 3 (Thread 16386 (LWP 3732))

  • #0 read
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libglib-2.0.so.0
  • #2 ?? 






Comment 1


Mariano Suárez-Alvarez





          2007-01-29 23:26:09 UTC
        



Did you try to use the same name as an exiting profile when doing this?

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


druid





          2007-01-29 23:30:33 UTC
        



No, it was a different name, however the name was "Default".  The profile I was basing my new Default profile on was called "Center Screen".  Perhaps it didn't like me trying to create a profile named "Default"...






Comment 3


druid





          2007-01-29 23:36:49 UTC
        



I'll have to look into finding debug packages for Dropline Gnome, however I was able to reliably reproduce the crash with this procedure:

1. Right-click on terminal context menu->Edit Current Profile
2. Change the name from Default to something else
3. From the menubar, Edit->Profiles
4. Click New, name it Default, and base it on the profile you just renamed







Comment 4


Mariano Suárez-Alvarez





          2007-01-29 23:38:23 UTC
        



Thanks for your response!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 324227 ***