python2.7 crashed with SIGSEGV in dbus_connection_send_with_reply()

Bug #1052087 reported by Martin Yrjölä on 2012-09-17
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
dbus-python (Ubuntu)
Undecided
Unassigned

Bug Description

Crashed after ending a skype call. I use skype-wrapper.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: python2.7-minimal 2.7.3-5ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 17 20:28:13 2012
ExecutablePath: /usr/bin/python2.7
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120905.2)
ProcCmdline: python indicator-applet-skype.py
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f52743d4680: mov 0x8(%rdi),%rax
 PC (0x7f52743d4680) ok
 source "0x8(%rdi)" (0x00000009) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_send_with_reply () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: python2.7 crashed with SIGSEGV in dbus_connection_send_with_reply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Martin Yrjölä (martin-yrjola) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
visibility: private → public
Matthias Klose (doko) on 2012-10-04
affects: python2.7 (Ubuntu) → dbus-python (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dbus-python (Ubuntu):
status: New → Confirmed
John (vanuan) wrote :

unfortunately there is not libdbus-dbg package, so bt doesn't show anything interesting:

#0 0x00007ffff091a820 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#1 0x00007ffff0919440 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#2 0x00007ffff09194a9 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#3 0x00007ffff09188b7 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#4 0x00007ffff0919093 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#5 0x00007ffff09015f4 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#6 0x00007ffff090216e in dbus_connection_get_dispatch_status () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#7 0x00007fffefbce453 in message_queue_prepare (source=<optimized out>, timeout=<optimized out>) at dbus-gmain.c:71
#8 0x00007fffef916846 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x00007fffef916f5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007fffef91749a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007fffee6a3ea1 in ?? () from /usr/lib/python2.7/dist-packages/glib/_glib.so

John (vanuan) wrote :

Actually there is (dbus-1-dbg):

#0 0x00007ffff6a0ef0d in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007ffff091ead8 in delete (len=90, start=<optimized out>, real=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:58
#2 delete (len=90, start=<optimized out>, real=<optimized out>) at ../../dbus/dbus-string.c:2979
#3 _dbus_string_delete (str=0xbcc308, start=<optimized out>, len=90) at ../../dbus/dbus-string.c:1447
#4 0x00007ffff09113d1 in load_message (body_len=10, header_len=80, fields_array_len=<optimized out>, byte_order=<optimized out>, message= 0xada930, loader=0xbcc300) at ../../dbus/dbus-message.c:4107
#5 _dbus_message_loader_queue_messages (loader=0xbcc300) at ../../dbus/dbus-message.c:4181
#6 0x00007ffff0918f47 in _dbus_transport_get_dispatch_status (transport=0x9c9580) at ../../dbus/dbus-transport.c:1099
#7 0x00007ffff0919071 in _dbus_transport_queue_messages (transport=0x9c9580) at ../../dbus/dbus-transport.c:1126
#8 0x00007ffff09015f4 in _dbus_connection_get_dispatch_status_unlocked (connection=0xbba1f0) at ../../dbus/dbus-connection.c:4183
#9 0x00007ffff090216e in dbus_connection_get_dispatch_status (connection= 0xbba1f0) at ../../dbus/dbus-connection.c:4314
#10 0x00007fffefbce453 in message_queue_prepare (source=<optimized out>, timeout=<optimized out>) at dbus-gmain.c:71
#11 0x00007fffef916846 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007fffef916f5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007fffef91749a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007fffee6a3ea1 in ?? () from /usr/lib/python2.7/dist-packages/glib/_glib.so

John (vanuan) wrote :

Here's an example code (you have to have Skype4Py package):

import Skype4Py

skype = Skype4Py.Skype()
skype.Attach()

John (vanuan) wrote :

The original Skype4Py was here: https://github.com/awahlig/skype4py

Here is a fixed version:

https://github.com/stigkj/Skype4Py

I'm not sure whether it's a bug on dbus-python or in Skype4Py.

IMO python program should not crash. But you cannot protect any native library from being crashed by improper use.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers