mountmanager crashed with SIGSEGV in QMetaObject::activate()

Bug #474656 reported by Alexander Skiba
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mountmanager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: mountmanager

I tried to mount an ntfs partition within nautilus when this message appeared. (What do you need to type when you don't even know what caused a bug? Like when apport files something you have absolutely no clue about??)

ProblemType: Crash
Architecture: i386
Date: Wed Nov 4 14:28:03 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/mountmanager
NonfreeKernelModules: nvidia
Package: mountmanager 0.2.6-0ubuntu4
ProcCmdline: /usr/bin/mountmanager
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x805ac76: movl $0x0,0x6c(%eax)
 PC (0x0805ac76) ok
 source "$0x0" ok
 destination "0x6c(%eax)" (0x0000006c) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: mountmanager
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 QMetaObject::activate(QObject*, int, int, void**) ()
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
Title: mountmanager crashed with SIGSEGV in QMetaObject::activate()
Uname: Linux 2.6.31-02063105-generic i686
UserGroups: gdm

Revision history for this message
Alexander Skiba (ghostlyrics) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()
QMetaObject::activate (sender=0x9a8fa60,
QMetaObject::activate (sender=0x9a8fa60, m=0x80e14a0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in mountmanager (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libudev0: installed version 147~-6, latest version: 147~-6.1
udev: installed version 147~-6, latest version: 147~-6.1
tzdata: installed version 2009o+repack-0ubuntu0.9.04.2, latest version: 2009r-0ubuntu9.10

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.