qutim crashed with SIGSEGV in qutim_sdk_0_3::ActionGenerator::actions()

Bug #940451 reported by Владислав
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qutim (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Упал(

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: qutim 0.2.80+201202230317-21~oneiric1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CrashCounter: 1
CrashDB: qutim
Date: Fri Feb 24 21:01:09 2012
ExecutablePath: /usr/bin/qutim
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120224)
LocalModules:

ProcCmdline: qutim
SegvAnalysis:
 Segfault happened at: 0xb67d550d: mov (%eax),%eax
 PC (0xb67d550d) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: qutim
StacktraceTop:
 ?? () from /usr/lib/libqutim.so.0
 qutim_sdk_0_3::ActionGenerator::actions() const () from /usr/lib/libqutim.so.0
 ?? () from /usr/lib/qutim/plugins/libsimpleactions.so
 ?? () from /usr/lib/qutim/plugins/libsimpleactions.so
 ?? () from /usr/lib/qutim/plugins/libsimpleactions.so
ThirdParty: True
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Владислав (funit09-3) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb67d550d in ?? ()
 No symbol table info available.
 #1 0x00000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in qutim (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 a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

package libattica0 does not exist, ignoring
qutim version 0.2.80+201202230317-21~oneiric1 required, but 0.2.0-0ubuntu6 is available
package libattica0 does not exist, ignoring
outdated debug symbol package for libv4l-0: package version 0.8.5-6ubuntu1 dbgsym version 0.8.5-3ubuntu2

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.