gnome-terminal crashes

Bug #63874 reported by Milad Fatenejad
4
Affects Status Importance Assigned to Milestone
gnome-terminal (Ubuntu)
Invalid
Undecided
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-terminal

Under the following sequence of events, gnome-terminal seems to always crash for me:

1) Open 2 terminals
2) Close 1 terminal
3) Open another terminal

The following message is displayed:

"""The Application "gnome-terminal" has quit unexpectedly.

You can inform the developers of what happened to help them fix it. Or you can restart the application right now."""

It happens whenever I have 1 or more terminals open, close some but not all of them and try to open another terminal. I tried running gnome-terminal from the command line to see if it would print any additional information, but it didnt.

Thanks
Milad

Milad Fatenejad (icksa1)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. What version of Ubuntu do you use? Could you get a backtrace from the bug-buddy dialog opened after the crash?

Changed in gnome-terminal:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Milad Fatenejad (icksa1) wrote :
Download full text (6.6 KiB)

Hi:
I'm kind of new to this, so bear with me...I'm using dapper and running on an intel xeon.

Here is what the bug-buddy dialog said, I see a lot of "no debugging symbols found", if it would help, is there someway to get this information? Anyway, here is what was printed:

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)
(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 -1225718080 (LWP 2653)]
[New Thread -1237410896 (LWP 2656)]
(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 ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb772248b in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7e9d8e6 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0x0806f736 in ?? ()
#5 0xb7782f40 in g_param_spec_types () from /usr/lib/libgobject-2...

Read more...

Revision history for this message
Vassilis Pandis (pandisv) wrote :

It would be really helpful if you repeated what you did to get the backtrace from bug-buddy with the debug packages installed. To build a debug package please follow the instructions on http://wiki.ubuntu.com/DebuggingProgramCrash . Build the debug package, install it and try to reproduce the problem. The backtrace that you will get will be far more useful to the developers. Thanks for reporting this. (if you have any trouble, feel free to e-mail me personally)!

Revision history for this message
Milad Fatenejad (icksa1) wrote :

Hi:
I think I found the problem...aparently I had unknowingly upgraded several packages past dapper by having a non-standard repository in my sources.list. After a couple hours of manually identifying/downgrading/reinstalling I managed to get everything back to normal, and gnome-terminal no longer causes the error I identified before.

Trying to install the debug package led me down this path, I think we can mark this as "resolved" or whatever the appropriate comment is (but I dont know how to do this). I'm sorry for the confusion.

Thanks
Milad

Revision history for this message
Vassilis Pandis (pandisv) wrote :

OK then, I'm closing this bug. At any rate, thanks for reporting your problem!

Changed in gnome-terminal:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.