Bug 555768
| Summary: | [abrt] crash in gvfs-1.4.3-2.fc12 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gerard Ryan <fedora> | ||||
| Component: | gvfs | Assignee: | Tomáš Bžatek <tbzatek> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 12 | CC: | alexl, bnocera, julian.amani, mclasen, tbzatek, tsmetana | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:79858c28fe61e17800c53e658d515d0f11a511ea | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-02-17 01:06:33 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
Gerard Ryan
2010-01-15 13:30:47 UTC
Created attachment 384616 [details]
File: backtrace
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? 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... *** This bug has been marked as a duplicate of bug 550307 *** |