Bug 641916

Summary: [abrt] nautilus-2.91.0.1-1.fc15: vfprintf: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Tom London <selinux>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:4850a266e52d99f5af3dc06ef80f8a745fa528e9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 15:44:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Tom London 2010-10-11 14:13:39 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: nautilus --no-desktop /media/Backup1TB
component: nautilus
crash_function: vfprintf
executable: /usr/bin/nautilus
kernel: 2.6.36-0.35.rc7.git0.fc15.x86_64
package: nautilus-2.91.0.1-1.fc15
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1286805941
uid: 500

comment
-----
Tried to decrypt/mount encrypted USB hard drive.

Decrypt/mount appears to have worked before the crash.

See this in ~/.xsession-errors:
Initializing nautilus-gdu extension
/usr/lib64/python2.7/site-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/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_type_get_qdata: assertion `node != NULL' failed
  from gtk import _gtk

Stack trace appears "messed up": If I run gdb manually, the call stack for the crashing thread runs to over 2000 frames...

I'm up to #2330 and it's still running ...

Let me know if posting the core file would be helpful.

How to reproduce
-----
1. powered on Luks encrypted ext4 USB hard drive
2. Selected '1TB Encrypted' from 'Places' to decrypt/mount
3. got crash
Comment 1 Tom London 2010-10-11 14:13:41 UTC 
Created attachment 452715 [details]
File: backtrace
Comment 2 Tom London 2010-10-11 14:20:35 UTC 
Stack trace appears to show a 'tight' recursion among the following:

#52 0x00007ff13e75b8d2 in pygobject_new_with_interfaces (gtype=0) at pygobject.c:699
        state = PyGILState_LOCKED
        o = <value optimized out>
        type = <value optimized out>
        dict = <value optimized out>
        py_parent_type = <value optimized out>
        bases = <value optimized out>
        modules = <value optimized out>
        module = <value optimized out>
        type_name = <value optimized out>
        mod_name = <value optimized out>
        gtype_name = <value optimized out>
#53 0x00007ff13e75b7df in pygobject_lookup_class (gtype=0) at pygobject.c:910
        py_type = <value optimized out>
#54 0x00007ff13e75b823 in pyg_type_get_bases (gtype=0) at pygobject.c:656
        interfaces = <value optimized out>
        parent_type = <value optimized out>
        interface_type = <value optimized out>
        n_interfaces = 0
        py_parent_type = <value optimized out>
        py_interface_type = <value optimized out>
        bases = <value optimized out>
        i = 0

Not sure its helpful, but I'm running with these:

pygobject2-doc-2.26.0-4.fc15.x86_64
pygobject2-debuginfo-2.26.0-4.fc15.x86_64
glib2-2.27.0-3.fc15.x86_64
pygobject2-2.26.0-4.fc15.x86_64
pygobject2-devel-2.26.0-4.fc15.x86_64
glibc-2.12.90-15.x86_64
glib2-2.27.0-3.fc15.i686
pygobject2-codegen-2.26.0-4.fc15.x86_64
glibc-2.12.90-15.i686
Comment 3 abrt-bot 2012-03-20 15:44:06 UTC 
Backtrace analysis found this bug to be similar to bug #731405, closing as duplicate.

Bugs which were found to be similar to this bug: 
  pygobject2: bug #731405
  pygtk2: bug #578931, bug #584076
  tortoisehg: bug #605347

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 731405 ***