nautilus-sendto crashed with SIGSEGV in __find_specmb()

Bug #966089 reported by Frederik Elwert
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

nautilus-sendto crashes when calling it. I get this message from the command line:

/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: specified class size for type `PyGtkGenericCellRenderer' is smaller than the parent type's `GtkCellRenderer' class size
  from gtk import _gtk
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_type_get_qdata: assertion `node != NULL' failed
  from gtk import _gtk
Speicherzugriffsfehler (Speicherabzug geschrieben)

This looks familiar and I guess this often happens when mixing PyGTK (GTK2) and PyGI (GTK3) in the same application. Maybe this causes it?

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus-sendto 3.0.1-2ubuntu2 [modified: usr/bin/nautilus-sendto]
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Tue Mar 27 12:04:31 2012
ExecutablePath: /usr/bin/nautilus-sendto
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
ProcCmdline: nautilus-sendto file:///home/username/Arbeitsfl%C3%A4che/rubriken
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus-sendto
Title: nautilus-sendto crashed with SIGSEGV in g_return_if_fail_warning()
UpgradeStatus: Upgraded to precise on 2012-01-22 (64 days ago)
UserGroups: adm admin cdrom dialout games libvirtd lpadmin plugdev sambashare

Revision history for this message
Frederik Elwert (frederik-elwert) wrote :
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus-sendto (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __find_specmb (format=0x4b63c922 "dex") at printf-parse.h:99
 _IO_vfprintf_internal (s=0xbf136580, format=0x4b63c922 "dex", ap=0xbf136b4c "\270\020vK\351\346uK\020:\373\t2") at vfprintf.c:1329
 __GI___vasprintf_chk (result_ptr=0xbf13668c, flags=1, format=0x4b63c922 "dex", args=0xbf136b4c "\270\020vK\351\346uK\020:\373\t2") at vasprintf_chk.c:68
 ?? () at /build/buildd/glib2.0-2.32.0/./glib/glib-unix.c:175 from /tmp/tmpSN84k_/lib/i386-linux-gnu/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus-sendto (Ubuntu):
importance: Undecided → Medium
summary: - nautilus-sendto crashed with SIGSEGV in g_return_if_fail_warning()
+ nautilus-sendto crashed with SIGSEGV in __find_specmb()
tags: removed: need-i386-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could do you a ls /usr/lib/nautilus-sendto/plugins and add that list to the bug?

Changed in nautilus-sendto (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Frederik Elwert (frederik-elwert) wrote :

Sure, here it is:

$ ls /usr/lib/nautilus-sendto/plugins/
libnstblueman.a libnstburn.so libnstpidgin.so
libnstblueman.la libnstempathy.so libnstremovable_devices.so
libnstblueman.so libnstevolution.so libnstupnp.so
libnstbluetooth.so libnstgajim.so

Changed in nautilus-sendto (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

does it work if you uninstall whatever provides libnstblueman.so (I guess some blueman package)?

Revision history for this message
Frederik Elwert (frederik-elwert) wrote :

Yes, indeed. After uninstalling blueman, nautilus-sendto starts without crashing.

Revision history for this message
Sebastien Bacher (seb128) wrote :

ok, reassigning to blueman then

affects: nautilus-sendto (Ubuntu) → blueman (Ubuntu)
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.