Bug 674279 - [abrt] nautilus-2.32.2.1-1.fc14: split_mimetype: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.32.2.1-1.fc14: split_mimetype: Process /usr/bin/nautilus wa...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:41c264e8d80d55621fc9d262d26...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-01 09:31 UTC by "FeRD" (Frank Dana)
Modified: 2015-03-03 22:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 16:01:10 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (28.35 KB, text/plain)
2011-02-01 09:31 UTC, "FeRD" (Frank Dana)
no flags Details
Log entries from /var/log/messages during a crash (2.42 KB, text/plain)
2011-02-01 09:35 UTC, "FeRD" (Frank Dana)
no flags Details

Description "FeRD" (Frank Dana) 2011-02-01 09:31:13 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: split_mimetype
executable: /usr/bin/nautilus
kernel: 2.6.37-0.rc7.git0.2.fc15.x86_64
package: nautilus-2.32.2.1-1.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296432923
uid: 500

comment
-----
For some reason, nautilus has begun exhibiting frequent crashes inside nautilus-actions, when opening/changing folders. This despite the fact that I only have one action defined (to enqueue video files to Totem), and that action hasn't changed in months.

Removing the action seems to have cleared the problems up, for the most part -- but perhaps not entirely. (Separate crash report to follow, I can't tell whether that one is attributable to nautilus-actions or not.)

How to reproduce
-----
1. Double-click on desktop folder
2. Nautilus window briefly appears, then *boom*
3. ("...There's no step 3!")

Comment 1 "FeRD" (Frank Dana) 2011-02-01 09:31:17 UTC
Created attachment 476342 [details]
File: backtrace

Comment 2 "FeRD" (Frank Dana) 2011-02-01 09:32:04 UTC
The following section of /var/log/messages illustrates the messages logged when a crash occurs. (Actually, three crashes. As you can see, they occurred in very short order, prompting me to remove the action using nautilus-actions-config-tool.)

Jan 30 19:09:53 HOSTNAME kernel: [611144.044827] nautilus[8640]: segfault at 0 ip 00007fbca949edd5 sp 00007fff4b33e470 error 4 in libna-core.so[7fbca9488000+41000]
Jan 30 19:09:56 HOSTNAME abrt[11570]: saved core dump of pid 8640 (/usr/bin/nautilus) to /var/spool/abrt/ccpp-1296432593-8640.new/coredump (61325312 bytes)
Jan 30 19:10:00 HOSTNAME nautilus: [N-A] Nautilus-Actions Tracker 3.0.6 initializing...
Jan 30 19:10:00 HOSTNAME nautilus: [N-A] Nautilus-Actions Menu Extender 3.0.6 initializing...
Jan 30 19:10:03 HOSTNAME dbus: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.497" (uid=500 pid=11574 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.15" (uid=0 pid=2053 comm="/usr/sbin/console-kit-daemon))
Jan 30 19:10:29 HOSTNAME kernel: [611179.452631] nautilus[11574]: segfault at 0 ip 00007f4854cc4dd5 sp 00007fffb4dbdce0 error 4 in libna-core.so[7f4854cae000+41000]
Jan 30 19:10:29 HOSTNAME abrt[11609]: saved core dump of pid 11574 (/usr/bin/nautilus) to /var/spool/abrt/ccpp-1296432629-11574.new/coredump (67588096 bytes)
Jan 30 19:14:33 HOSTNAME nautilus: [N-A] Nautilus-Actions Tracker 3.0.6 initializing...
Jan 30 19:14:36 HOSTNAME nautilus: [N-A] Nautilus-Actions Menu Extender 3.0.6 initializing...
Jan 30 19:14:40 HOSTNAME dbus: [system] Rejected send message, 3 matched rules; type="method_call", The following section of /var/log/messages illustrates the messages logged when a crash occurs. (Actually, three crashes. As you can see, they occurred in very short order, prompting me to remove the action using nautilus-actions-config-tool.)

Jan 30 19:09:53 HOSTNAME kernel: [611144.044827] nautilus[8640]: segfault at 0 ip 00007fbca949edd5 sp 00007fff4b33e470 error 4 in libna-core.so[7fbca9488000+41000]
Jan 30 19:09:56 HOSTNAME abrt[11570]: saved core dump of pid 8640 (/usr/bin/nautilus) to /var/spool/abrt/ccpp-1296432593-8640.new/coredump (61325312 bytes)
Jan 30 19:10:00 HOSTNAME nautilus: [N-A] Nautilus-Actions Tracker 3.0.6 initializing...
Jan 30 19:10:00 HOSTNAME nautilus: [N-A] Nautilus-Actions Menu Extender 3.0.6 initializing...
Jan 30 19:10:03 HOSTNAME dbus: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.497" (uid=500 pid=11574 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.15" (uid=0 pid=2053 comm="/usr/sbin/console-kit-daemon))
Jan 30 19:10:29 HOSTNAME kernel: [611179.452631] nautilus[11574]: segfault at 0 ip 00007f4854cc4dd5 sp 00007fffb4dbdce0 error 4 in libna-core.so[7f4854cae000+41000]
Jan 30 19:10:29 HOSTNAME abrt[11609]: saved core dump of pid 11574 (/usr/bin/nautilus) to /var/spool/abrt/ccpp-1296432629-11574.new/coredump (67588096 bytes)
Jan 30 19:14:33 HOSTNAME nautilus: [N-A] Nautilus-Actions Tracker 3.0.6 initializing...
Jan 30 19:14:36 HOSTNAME nautilus: [N-A] Nautilus-Actions Menu Extender 3.0.6 initializing...
Jan 30 19:14:40 HOSTNAME dbus: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.56" (uid=500 pid=2326 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.14" (uid=0 pid=2006 comm="/usr/sbin/console-kit-daemon))
Jan 30 19:15:23 HOSTNAME kernel: [  143.820009] nautilus[2326]: segfault at 0 ip 00007feeb06e1dd5 sp 00007fff18da6c40 error 4 in libna-core.so[7feeb06cb000+41000]
Jan 30 19:15:24 HOSTNAME abrt[2803]: saved core dump of pid 2326 (/usr/bin/nautilus) to /var/spool/abrt/ccpp-1296432923-2326.new/coredump (61407232 bytes)
Jan 30 19:15:24 HOSTNAME nautilus: [N-A] Nautilus-Actions Tracker 3.0.6 initializing...
Jan 30 19:15:25 HOSTNAME nautilus: [N-A] Nautilus-Actions Menu Extender 3.0.6 initializing...
Jan 30 19:15:25 HOSTNAME dbus: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.64" (uid=500 pid=2804 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.14" (uid=0 pid=2006 comm="/usr/sbin/console-kit-daemon))

sender=":1.56" (uid=500 pid=2326 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.14" (uid=0 pid=2006 comm="/usr/sbin/console-kit-daemon))
Jan 30 19:15:23 HOSTNAME kernel: [  143.820009] nautilus[2326]: segfault at 0 ip 00007feeb06e1dd5 sp 00007fff18da6c40 error 4 in libna-core.so[7feeb06cb000+41000]
Jan 30 19:15:24 HOSTNAME abrt[2803]: saved core dump of pid 2326 (/usr/bin/nautilus) to /var/spool/abrt/ccpp-1296432923-2326.new/coredump (61407232 bytes)
Jan 30 19:15:24 HOSTNAME nautilus: [N-A] Nautilus-Actions Tracker 3.0.6 initializing...
Jan 30 19:15:25 HOSTNAME nautilus: [N-A] Nautilus-Actions Menu Extender 3.0.6 initializing...
Jan 30 19:15:25 HOSTNAME dbus: [system] Rejected send message, 3 matched rules; type="method_call", sender=":1.64" (uid=500 pid=2804 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.14" (uid=0 pid=2006 comm="/usr/sbin/console-kit-daemon))

Comment 3 "FeRD" (Frank Dana) 2011-02-01 09:35:39 UTC
Created attachment 476343 [details]
Log entries from /var/log/messages during a crash

Ugh. Apologies for the messed-up paste, my mouse has a twitchy wheelbutton. Let's try that again, as an attachment.

The ATTACHED section of /var/log/messages illustrates the messages logged when a crash occurs. (Actually, three crashes. As you can see, they occurred in very short order, prompting me to remove the action using nautilus-actions-config-tool.)

Comment 4 Fedora End Of Life 2012-08-16 16:01:13 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.