kupfer.py crashed with SIGSEGV

Bug #1038434 reported by David Leal
54
This bug affects 10 people
Affects Status Importance Assigned to Milestone
kupfer
Fix Committed
Undecided
Unassigned
dbus-python (Ubuntu)
Invalid
Undecided
Unassigned
kupfer (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Kupfer seems to crash "spontaneously", even if I'm not directly using it. If I start it again, I am able to use it to launch a program or 2, but after a time, if I try to use it, I find it has crashed. I don't see any relevant information in .xsession-errors.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: kupfer 0+v208-2
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu8
Architecture: i386
CrashCounter: 1
Date: Sat Aug 18 13:14:27 2012
ExecutablePath: /usr/share/kupfer/kupfer.py
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/kupfer/kupfer.py --no-splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0xb49ddac4: movl $0xffffffff,0x4(%eax)
 PC (0xb49ddac4) ok
 source "$0xffffffff" ok
 destination "0x4(%eax)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: kupfer
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
Title: kupfer.py crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare video

Revision history for this message
David Leal (dgleal) wrote :
visibility: private → public
Revision history for this message
Karol Będkowski (karol-bedkowski) wrote :

Please run Kupfer with debug option:
kupfer --debug 2>&1 | tee log.txt
and attach result after crash.

Revision history for this message
David Leal (dgleal) wrote :

Karol, attaching log.txt as you instructed. Thanks for looking into this.

Revision history for this message
David Leal (dgleal) wrote :

Btw, I just tried running kufper through strace, but it didn't crash. If I remove strace, it segfaults again.

Revision history for this message
Karol Będkowski (karol-bedkowski) wrote :

Thanks,
Please try to disable virtualbox plugin. I guess it may be broken. Also please give us information about version of virtualbox.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /tmp/tmp2JMTy1/lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmp2JMTy1/lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmp2JMTy1/lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmp2JMTy1/lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/tmp2JMTy1/lib/i386-linux-gnu/libdbus-1.so.3

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in kupfer (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:

libglib2.0-0 version 2.33.8-1 required, but 2.33.8-1ubuntu1 is available
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu3 dbgsym version 3.16-1ubuntu2

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
Revision history for this message
David Leal (dgleal) wrote :

Karol, not sure what kind of stack trace information would be useful here but, for reference, it seems the plugin causing the problem is Gwibber. I disabled the Virtualbox plugin and Kupfer still crashed. But disabling the Gwibber plugin will cause Kupfer to stop segfaulting. I re-enabled the Virtualbox plugin and Kupfer is still up.

Feel free to close this bug again if you are unable to reproduce it. I just wanted to make sure this information reaches you.

Changed in kupfer (Ubuntu):
status: Invalid → New
Revision history for this message
X (u78qir8a9-deactivatedaccount) wrote :

Hi, this is a crash inside D-Bus but it may be that we somehow use dbus wrong in Kupfer, or in the Gwibber plugin. Thanks for researching which plugin might be causing this!

Revision history for this message
Karol Będkowski (karol-bedkowski) wrote :

Thanks.
I checked Kupfer+Gwibber in today updated Ubuntu and I can't reproduce this problem. Please try to update system.

Revision history for this message
David Leal (dgleal) wrote :

Ok, my system is fully updated. I enabled the Gwibber plugin (clicked "Gwibber", it took a few seconds before the checkbox was updated and the Gwibber plugin settings appeared). Kupfer crashed after a few seconds. I started it again, went to the plugins window again and Gwibber was disabled. With Gwibber disabled, kupfer stays up.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in kupfer (Ubuntu):
status: New → Confirmed
Revision history for this message
Karol Będkowski (karol-bedkowski) wrote :

Seems to be well known bug in dbus python package - #768109, #858836, #1052045.
I can't fix this problem in Kupfer...

Revision history for this message
mcsan (octagonhead) wrote :

^ Yes, for me changing plugin settings can delay this crash for a bit, but not prevent it.
(even tried removing kupfer cache files and direct editing of .config/kupfer/kupfer.cfg)

This probably is a duplicate of one of the other dbus-python bugs.

Revision history for this message
mcsan (octagonhead) wrote :

Aha, looks like I still had some DBUS-using plugins enabled,

For me Kupfer seems stable now with basic functionality, since disabling all the included plugins that use dbus.

So the workaround is to ensure all of the following are disabled:

Empathy
Gajim
Getting Things GNOME
Gwibber
Gwibber (Simple)
Selected File
Notes
Pidgin
System Services
Skype
Thunar
Tracker
Tracker 0.6

Revision history for this message
Karol Będkowski (karol-bedkowski) wrote :

Hi,
Please check attached patch.
I don't sure why, but seems to fix problem - Kupfer don't crash.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "0001-dbus-fix-problem-with-crashing-kupfer.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Revision history for this message
magnus (magnusanderssen) wrote :

I had the same kind of issue with kupfer crashing and therefore being unusable.
Tried the above patch and it has not crashed since.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in dbus-python (Ubuntu):
status: New → Confirmed
Changed in kupfer:
status: New → Fix Committed
Changed in kupfer (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
teranex (teranex) wrote :

I can confirm that the patch in #19 fixes the issue.
I'm writing a plugin for Hamster (https://github.com/teranex/kupfer-plugins/blob/master/hamster.py) which uses D-Bus. When I implemented a Source which returned another Source (as a SourceLeaf), Kupfer would crash with a Segmentation Fault. After I applied the patch it works without any problems.

Revision history for this message
Pablo Lalloni (plalloni) wrote :

I can confirm the patch in #19 works here too.

I'm on Xubuntu Quantal.

Revision history for this message
luis.nando (luis-nando) wrote :

Guys, but how to apply a patch on kupfer? I`ve been googling it but couldn`t find the answer...

Revision history for this message
Karol Będkowski (karol-bedkowski) wrote :

if you use package from official repository please install version from our ppa https://launchpad.net/~kupfer-team/+archive/ppa

To apply a patch you should:
1. save patch is i.e. /tmp/
2. from terminal enter to directory, where Kupfer is installed (usually /usr/share/kupfer)
3. run: patch -p1 < /tmp/patch-name
(use sudo if Kupfer is in /usr/share/)

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kupfer - 0+v208-3

---------------
kupfer (0+v208-3) unstable; urgency=medium

  * Acknowledge NMU, thanks Sebastian!
  * debian/patches/dbus.patch:
    - Fix crash by initializing D-Bus (Closes: #717105) (LP: #1038434).
  * debian/patches/help.patch:
    - Workaround missing xml file, which prevents documentation from
      being loaded (Closes: #679296).
  * debian/patches/locales.patch:
    - Fix crash with locales not supporting dot as decimal point
      separator (Closes: #680008).
  * debian/patches/tracker-needle.patch:
    - Spawn tracker-needle instead of tracker-search-tool (Closes: #680003).
  * debian/control:
    - Use canonical URIs for Vcs-* fields.
    - Bump Standards-Version to 3.9.5.
  * debian/watch:
    - Adjust watch file to point to GitHub.

 -- Luca Falavigna <email address hidden> Thu, 19 Dec 2013 21:23:22 +0100

Changed in kupfer (Ubuntu):
status: Fix Committed → Fix Released
Simon McVittie (smcv)
Changed in dbus-python (Ubuntu):
status: Confirmed → Invalid
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.