kbluetooth crashed with SIGSEGV in Solid::Control::BluetoothManager::~BluetoothManager()

Bug #437732 reported by jarkod
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebluetooth (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: kdebluetooth

The error message appeared just after logging in - didn't tried to connect, recconect, add a device whatsoever. Just a simple logging in with a bluetooth dongle plugged in.

ProblemType: Crash
Architecture: i386
Date: Sun Sep 27 19:14:53 2009
Disassembly: 0x6: Cannot access memory at address 0x6
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kbluetooth
NonfreeKernelModules: nvidia
Package: kdebluetooth 1:0.4~beta1b-0ubuntu1
ProcCmdline: /usr/bin/kbluetooth
ProcEnviron:
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x6: Cannot access memory at address 0x6
 PC (0x00000006) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: kdebluetooth
StacktraceTop:
 ?? ()
 Solid::Control::BluetoothManager::~BluetoothManager() ()
 ?? () from /usr/lib/libsolidcontrol.so.4
 ?? () from /usr/lib/libsolidcontrol.so.4
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: kbluetooth crashed with SIGSEGV in Solid::Control::BluetoothManager::~BluetoothManager()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare vboxusers video

Revision history for this message
jarkod (rydberg-o2) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
~BluetoothManager (this=0x88f7778)
destroy ()
~KCleanUpGlobalStatic (this=0x2e2394)
__run_exit_handlers (status=0, listp=0x3db0304,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdebluetooth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
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.