apport-kde crashed with SIGSEGV in QWidgetPrivate::deleteExtra()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apport
apport -kde crashes during kde initialization procedure (in the seconds right after the splash screen has gone away but before the desktop is fully functional (e.g. so it is impossible for the user to click/start anything)).
I am currently running 2.6.31-11-generic #38-Ubuntu, x86_64 GNU/Linux from the Ubuntu karmic (development branch), with all installed packages up to date.
The bug concerns apport-kde, with the output: $: apt-cache policy apport-kde
apport-kde:
Installed: 1.9.2-0ubuntu1
Candidate: 1.9.2-0ubuntu1
Version table:
*** 1.9.2-0ubuntu1 0
500 http://
100 /var/lib/
ProblemType: Crash
ApportLog: Error: [Errno 13] Permission denied: '/var/log/
Architecture: amd64
CrashCounter: 1
CrashReports:
600:1001:
600:1001:
600:1001:
600:1001:
Date: Sat Oct 3 17:53:25 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
Package: apport-kde 1.9.2-0ubuntu1
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
LANGUAGE=
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7fa89ee2c1d0: mov 0x10(%rax),%rdi
PC (0x7fa89ee2c1d0) ok
source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
QWidgetPrivate
QWidgetPrivate
?? () from /usr/lib/
Title: apport-kde crashed with SIGSEGV in QWidgetPrivate:
Uname: Linux 2.6.31-11-generic x86_64
UserGroups:
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 #403361, 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.