Bug 691110

Summary: [abrt] nautilus-2.91.91-1.fc15: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Fabio Duran-Verdugo <bugs>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: 1rafools1, ccecchi, mclasen, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:2724417aea601538361c181a8c37ce57f9728de4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-07 23:02:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Fabio Duran-Verdugo 2011-03-26 19:49:04 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 44964 bytes
cmdline: nautilus
component: nautilus
Attached file: coredump, 62926848 bytes
crash_function: nautilus_file_get_volume_free_space
executable: /usr/bin/nautilus
kernel: 2.6.38-1.fc15.i686
package: nautilus-2.91.91-1.fc15
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
time: 1301163623
uid: 500

How to reproduce
-----
1.
2.
3.
aAD
Comment 1 Fabio Duran-Verdugo 2011-03-26 19:49:07 UTC 
Created attachment 487949 [details]
File: backtrace
Comment 2 Fabio Duran-Verdugo 2011-03-26 20:11:09 UTC 
steps for reproduce:

- disable statusbar from nautilis (view -> statusbar)
- logout.
- login.
- open nautilus and enable statusbar.
- nautilus crash.
Comment 3 Matthias Clasen 2011-04-07 23:02:11 UTC 
This doesn't seem to happen here with nautilus 3.0.0.
I'll assume it is fixed.
Please reopen if it still happens for you
Comment 4 Cosimo Cecchi 2011-06-04 00:36:35 UTC 
*** Bug 688895 has been marked as a duplicate of this bug. ***