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 366048 - crash in Terminal: creating a profile for t...
crash in Terminal: creating a profile for t...
Status: RESOLVED DUPLICATE of bug 363609
Product: gnome-terminal
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 387022 390758 394323 406307 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-28 02:04 UTC by quigonjin
Modified: 2007-02-10 19:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description quigonjin 2006-10-28 02:04:36 UTC 
Version: 2.16.1

What were you doing when the application crashed?
creating a profile for terminal with the same name as a previously created profile


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

Memory status: size: 54906880 vsize: 0 resident: 54906880 share: 0 rss: 16502784 rss_rlim: 0
CPU usage: start_time: 1161986610 rtime: 0 utime: 115 stime: 0 cutime:34 cstime: 0 timeout: 81 it_real_value: 0 frequency: 10

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 -1226152272 (LWP 11451)]
[New Thread -1249731680 (LWP 11455)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79073

Thread 1 (Thread -1226152272 (LWP 11451))

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





          2006-10-28 03:58:53 UTC
        



This should be a duplicate of bug 363609. It is impossible to be sure from looking at the stack trace...

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


Mariano Suárez-Alvarez





          2006-11-23 19:47:44 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!







Comment 3


Susana





          2006-12-18 10:38:36 UTC
        



*** Bug 387022 has been marked as a duplicate of this bug. ***






Comment 4


venkatesh.nandakumar





          2006-12-19 04:54:40 UTC
        



Additional stack trace....I hope this is what u wanted.


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

Memory status: size: 82497536 vsize: 0 resident: 82497536 share: 0 rss: 17235968 rss_rlim: 0
CPU usage: start_time: 1166503534 rtime: 0 utime: 128 stime: 0 cutime:116 cstime: 0 timeout: 12 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)
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1226475856 (LWP 8451)]
[New Thread -1280398432 (LWP 8457)]
(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)
(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)
0xffffe410 in __kernel_vsyscall ()




+
Trace
    95313






Thread 1
          (Thread -1226475856 (LWP 8451))


    

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


Susana





          2006-12-29 21:00:33 UTC
        



*** Bug 390758 has been marked as a duplicate of this bug. ***






Comment 6


Susana





          2006-12-30 02:26:10 UTC
        



Hi Venkatesh,

Unfortunately that stack trace is just like the previous one. Can you install debugging packages for gnome-terminal, gtk+, libvte, glib, pango, libgnome, libgnomeui, and then try to reproduce the crash? 

Thanks in advance!






Comment 7


Susana





          2006-12-30 02:28:52 UTC
        



Reopening because of duplicates.






Comment 8


venkatesh.nandakumar





          2006-12-30 04:11:33 UTC
        



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

Memory status: size: 82124800 vsize: 0 resident: 82124800 share: 0 rss: 16781312 rss_rlim: 0
CPU usage: start_time: 1167451684 rtime: 0 utime: 82 stime: 0 cutime:74 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226795344 (LWP 9592)]
[New Thread -1280738400 (LWP 9596)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    97937






Thread 1
          (Thread -1226795344 (LWP 9592))


    

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

    
                at terminal-profile.c
                  line
                  1975

    

    • 

  • 
#5
new_profile_response_callback

    
                at terminal.c
                  line
                  2386

    

    • 

  • 
#6
g_cclosure_marshal_VOID

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#7
g_closure_invoke

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#8
g_signal_chain_from_overridden

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#9
g_signal_emit_valist

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#10
g_signal_emit

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#11
gtk_dialog_response

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#12
gtk_dialog_response

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#13
g_cclosure_marshal_VOID__VOID

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#14
g_closure_invoke

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#15
g_signal_chain_from_overridden

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#16
g_signal_emit_valist

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#17
g_signal_emit

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#18
gtk_button_clicked

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#19
gtk_button_set_alignment

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#20
gtk_button_set_alignment

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#21
_gtk_marshal_BOOLEAN__BOXED

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#22
g_value_set_boxed

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#23
g_closure_invoke

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#24
g_signal_chain_from_overridden

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#25
g_signal_emit_valist

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#26
g_signal_emit

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#27
gtk_widget_get_default_style

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#28
gtk_propagate_event

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#29
gtk_main_do_event

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#30
_gdk_events_init

    
                from
                /usr/lib/libgdk-x11-2.0.so.0

    

    • 

  • 
#31
g_main_context_dispatch

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#32
g_main_context_check

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#33
g_main_loop_run

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#34
gtk_main

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#35
main

    
                at terminal.c
                  line
                  1773

    

    • 

  • 
#36
__libc_start_main

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#37
_start

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 9


Susana





          2007-01-08 01:12:34 UTC
        



Venkatesh, thanks for the stack trace! :)

Mariano, is it a dup?






Comment 10


palfrey





          2007-01-12 21:03:57 UTC
        



*** Bug 394323 has been marked as a duplicate of this bug. ***






Comment 11


Susana





          2007-02-10 11:08:12 UTC
        



*** Bug 406307 has been marked as a duplicate of this bug. ***






Comment 12


Mariano Suárez-Alvarez





          2007-02-10 19:34:01 UTC
        



(In reply to comment #9)

> Mariano, is it a dup?

Yup, dupping.


Thanks all. 

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