thg crashed with SIGSEGV in QMetaObject::methodOffset()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-qt4 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
tortoisehg (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Simply starting thg causes the issue, even after rm -rf ~/.config/
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: tortoisehg 2.8-1
ProcVersionSign
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Thu Oct 3 10:12:43 2013
ExecutablePath: /usr/bin/thg
InstallationDate: Installed on 2013-09-30 (2 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/thg --nofork
SegvAnalysis:
Segfault happened at: 0x7f0f3caad237 <_ZNK11QMetaObj
PC (0x7f0f3caad237) ok
source "0x10(%rcx)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tortoisehg
StacktraceTop:
QMetaObject:
?? () from /usr/lib/
QObject:
?? () from /usr/lib/
?? () from /usr/lib/
Title: thg crashed with SIGSEGV in QMetaObject:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Status changed to 'Confirmed' because the bug affects multiple users.