gedit crashed with SIGSEGV in g_type_get_qdata()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gedit (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
gedit fails to start neither from terminal, icon nor with text-file opened.
Description: Ubuntu oneiric (development branch)
Release: 11.10
/var/crash$ apt-cache policy gedit
gedit:
Installiert: 3.2.0-0ubuntu1
Kandidat: 3.2.0-0ubuntu1
Versionstabelle:
*** 3.2.0-0ubuntu1 0
500 http://
100 /var/lib/
I expected gedit to open, with a textfile, what didnt work. i tried to open it from the menubar unity which failed same as when i tried to open gedit from terminal.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gedit 3.2.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon Oct 3 13:00:19 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: gedit /home/hans/
ProcEnviron:
LANGUAGE=de_AT:de
PATH=(custom, user)
LANG=de_AT.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7eff19de658b <vfprintf+155>: callq 0x7eff19e2ae60 <strchrnul>
PC (0x7eff19de658b) ok
source "0x7eff19e2ae60" (0x7eff19e2ae60) ok
destination "(%rsp)" (0x7fff8518af70) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
g_type_get_qdata () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gedit crashed with SIGSEGV in g_type_get_qdata()
UpgradeStatus: Upgraded to oneiric on 2011-10-01 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #846063, 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.