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 406307 - crash in Terminal: Creating a new terminal ...
crash in Terminal: Creating a new terminal ...
Status: RESOLVED DUPLICATE of bug 366048
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-02-10 05:42 UTC by Frodo Baggins
Modified: 2007-02-10 11:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Frodo Baggins 2007-02-10 05:42:57 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Creating a new terminal profile.
had already made one.
then wanted to create one more based on this new one


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

Memory status: size: 74842112 vsize: 0 resident: 74842112 share: 0 rss: 20500480 rss_rlim: 0
CPU usage: start_time: 1171085302 rtime: 0 utime: 671 stime: 0 cutime:633 cstime: 0 timeout: 38 it_real_value: 0 frequency: 0

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 -1225926992 (LWP 4717)]
[New Thread -1246913632 (LWP 4721)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 109454

Thread 1 (Thread -1225926992 (LWP 4717))

  • #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


Susana





          2007-02-10 11:08:12 UTC
        



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 366048 ***