gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-terminal (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
1) (login with xubuntu session)
2) (install gnome-terminal)
3) start gnome-terminal
4) create new tab in running gnome-terminal (Shift+Ctrl+T)
5) detach this new tab
6) run vi, vim or mc in this detached tab
Expected: start application vi, vim or mc without problem
But: crash all running gnome terminal
-------
Without detaching tab is no problem.
-------
Ubuntu precise (development branch)
Release: 12.04
-------
gnome-terminal:
Installed: 3.2.1-2ubuntu1
Candidate: 3.2.1-2ubuntu1
Version table:
*** 3.2.1-2ubuntu1 0
500 http://
100 /var/lib/
-------
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-terminal 3.2.1-2ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-10-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Fri Jan 27 17:26:08 2012
ExecutablePath: /usr/bin/
InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha i386 (20111129.2)
ProcCmdline: gnome-terminal
ProcEnviron:
PATH=(custom, no user)
LANG=cs_CZ.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x15fa48 <g_type_
PC (0x0015fa48) ok
source "(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%ebp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
g_type_
?? () from /usr/lib/
g_cclosure_
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
Title: gnome-terminal crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to precise on 2012-01-26 (0 days ago)
UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #838765, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.