Bug 654946
| Summary: | [abrt] nautilus-2.32.1-1.fc14: gdu_device_get_object_path: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David M. <skaturn> | ||||
| Component: | gnome-disk-utility | Assignee: | David Zeuthen <davidz> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 14 | CC: | amturnip, ccecchi, davidz, mclasen, skaturn, tbzatek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:bd70a7cc8a0ddd655fc8d5ea5dda011ff83b5f50 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-12-20 22:16:54 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
David M.
2010-11-19 06:14:15 UTC
Created attachment 461466 [details]
File: backtrace
Package: nautilus-2.32.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Having completely finished the Fedora 14 installation, but with the live USB still in the socket, I rebooted. 2. I opened "Computer" using the icon on the desktop. 3. In the "Computer" window, I right-clicked an icon representing the live USB. 4. I chose "Remove Safely". Comment ----- Before opening "Computer", I noticed that the live USB was represented by not one but two icons on the desktop - one 8GB (the size of the USB stick) and the other 3GB. I did not inspect those two more closely. They both disappeared from the desktop at about the time of the crash. *** This bug has been marked as a duplicate of bug 650380 *** |