Bug 529982

Summary: [abrt] crash detected in gvfs-1.4.0-6.fc12
Product: [Fedora] Fedora Reporter: Jens Knutson <jensk.maps>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: alexl, awilliam, bnocera, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:7e72dc358fd349a0e250018de1e0888788c2ad60
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-02 17:28:44 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 Jens Knutson 2009-10-21 01:52:21 UTC 
abrt detected a crash.


How to reproduce
-----
1.
2.
3.


Comment
-----
I had just created a ext4 partition on a RAID-1 array in Palimpsest

Additional information
======


Attached files
----
backtrace

cmdline
-----
/usr/libexec/gvfs-gdu-volume-monitor 


component
-----
gvfs


executable
-----
/usr/libexec/gvfs-gdu-volume-monitor


kernel
-----
2.6.31.1-56.fc12.i686


package
-----
gvfs-1.4.0-6.fc12


reason
-----
Process was terminated by signal 11
Comment 1 Jens Knutson 2009-10-21 01:52:27 UTC 
Created attachment 365451 [details]
File: backtrace
Comment 2 Tomáš Bžatek 2009-10-23 14:05:22 UTC 
(In reply to comment #0)
> Comment
> -----
> I had just created a ext4 partition on a RAID-1 array in Palimpsest

May I ask for proper repro steps leading to crash? I've just tried to create a RAID1 array on a USB flashdisk, formatted as ext4 in palimpsest but gvfs-gdu-volume-monitor stands still, no indication of problem.
Comment 3 Jens Knutson 2009-11-02 11:34:00 UTC 
Hm.   Well, perhaps gvfs 1.4.1 or a newer kernel fixed this....  I can no longer repro this on the same computer using the same drives and (at least in theory) the same steps.

I'm comfortable with this getting closed.  I'm trying to learn about RAID right now, which is how I discovered the bug.  If I uncover this issue again in the course of my testing, I'll open a new bug.
Comment 4 Adam Williamson 2009-11-02 17:28:44 UTC 
Thanks a lot.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 5 Tomáš Bžatek 2009-11-03 12:48:55 UTC 
FYI, I've recently discovered several places in the code prone to crashes, fixed gnome-disk-utility-2.28.1-1.fc12 and gvfs-1.4.1-3.fc12 packages should help prevent the issues.