GNOME Bugzilla – Bug 380741
crash in Terminal: I had two tabs open with...
Last modified: 2006-11-30 18:39:13 UTC
Version: 2.16.1 What were you doing when the application crashed? I had two tabs open within gnome-terminal; one containing an ssh session, one with crontab -e running (which was the active tab), and attempted to open another tab by pressing ctrl-shift-t. beryl was running as my window manager at the time (although from within the session in the a third tab, I had issued 'killall beryl && metacity --replace', followed a few minutes later by the reverse.) Closed the third tab then gave focus to Firefox for a short time, refocused to gnome-terminal, then invoked the hotkey. Also had beryl-manager, azureus, desklets, skype, and gaim open on different desktops; none of them seemed to grab focus during the events leading to crash. For whomever is reading this bug report, thank you for taking the time to look it over! If you need any further information, I have recently gotten my machine in the state at which I plan to leave it for a while, so I should be able to answer any questions you have. (I also work in a QA department for a small software company, so I'm pretty familiar with terminology.) Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 54870016 vsize: 0 resident: 54870016 share: 0 rss: 17354752 rss_rlim: 0 CPU usage: start_time: 1164842838 rtime: 0 utime: 3648 stime: 0 cutime:3307 cstime: 0 timeout: 341 it_real_value: 0 frequency: 1905 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 -1226320208 (LWP 16961)] [New Thread -1248818272 (LWP 16968)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 90442
Thread 1 (Thread -1226320208 (LWP 16961))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? There have been lots of duplicates of this issue, but no one seems to be able to provide us an usable stack trace. Could you install -dbgsym packages for gtk+, gnome-terminal and vte and see if you can reproduce this? Thanks! *** This bug has been marked as a duplicate of 358785 ***