Bug 555768 - [abrt] crash in gvfs-1.4.3-2.fc12
Summary: [abrt] crash in gvfs-1.4.3-2.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 550307
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:79858c28fe61e17800c53e658d5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-15 13:30 UTC by Gerard Ryan
Modified: 2015-03-03 22:43 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-17 01:06:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (6.05 KB, text/plain)
2010-01-15 13:30 UTC, Gerard Ryan
no flags Details

Description Gerard Ryan 2010-01-15 13:30:47 UTC
abrt 1.0.3 detected a crash.

Attached file: backtrace
cmdline: /usr/libexec/gvfs-gdu-volume-monitor
component: gvfs
executable: /usr/libexec/gvfs-gdu-volume-monitor
kernel: 2.6.31.9-174.fc12.x86_64
package: gvfs-1.4.3-2.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)

Comment 1 Gerard Ryan 2010-01-15 13:30:49 UTC
Created attachment 384616 [details]
File: backtrace

Comment 2 Julian A. 2010-01-18 23:05:11 UTC
I've got the same problem. I am using a fresh install of Fedora LXDE spin. Crash first appeared after making several updates. Is the recent SLIM update causeing troubles?

Comment 3 Julian A. 2010-01-19 08:52:37 UTC
Problem (for me) only appears when using Kernel 2.6.31.9-174.fc12.i686!
I have no problems when using Kernel 2.6.31.5-127.fc12.i686 instead of 2.6.31.9-174.fc12.i686.

Detailed explination:
- First time using Rythmbox this crash was reported. (Could be a coincidence!?)
- After that my home-folder could not anymore be listed, e.g. ls -la, nautilus or pcmanfm freez while showing my home-folder.
- Even as root I was unable to delete the .gvfs-folder in my home directory.
- Booting from a live-CD allows deleting ~/.gvfs afterwards cleaning with fschk(.ext4) -f will correct some errors.
- Booting with 2.6.31.9-174 will make the same trouble again every restart of the system
- Using the older 2.6.31.5-127 I have no problems so far...

Comment 4 Matthias Clasen 2010-02-17 01:06:33 UTC

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


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