blueman-applet crashed with SIGSEGV in pa_context_new_with_proplist()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
blueman (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crashed on report
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: blueman 1.22~bzr707-
ProcVersionSign
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 2 10:54:57 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7ff2b0c2d0c0: cmp %rax,0x8(%rdi)
PC (0x7ff2b0c2d0c0) ok
source "%rax" ok
destination "0x8(%rdi)" (0xac002818) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: blueman
StacktraceTop:
?? () from /usr/lib/
pa_context_
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
_ctypes_callproc () from /usr/lib/
Title: blueman-applet crashed with SIGSEGV in pa_context_
UpgradeStatus: Upgraded to precise on 2012-01-28 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
visibility: | private → public |
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()