Bug 469082 - Nautilus - not controlled addition of several storage devices
Nautilus - not controlled addition of several storage devices
Product: Fedora
Classification: Fedora
Component: nautilus (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomáš Bžatek
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-10-29 15:48 EDT by Piotr
Modified: 2015-03-03 17:33 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-29 23:55:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Piotr 2008-10-29 15:48:57 EDT
Description of problem:
The problem appears when you install new updates along with the kernel I do not remember whether the update was among the Nautilus. After the upgrade and restart the computer, run the Nautilus. In the main dialog box appeared on 23 storage devices. You can not mount. You can not delete or add. I think that it's the Linux kernel, and the way in which he makes the hardware. But I'm not sure, maybe it's the individual parcels, but please check and rectify the error.

Version-Release number of selected component (if applicable):
GNOME nautilus 2.24.1

How reproducible:

Steps to Reproduce:
Before upgrading Nautilus normally display device. But as soon as they install and run it, I saw several storage devices.

Additional info:
I have too little time to search for flaws in the system. If you can give it commands that you try to discover the error. In the near future will try to give their results. With the top sorry for my English.

Expected results:
These are very important considerations for me not only from the aesthetic, but also from the side of use. Please correct the problem.

The screen:
Comment 1 Matthias Clasen 2008-10-29 23:55:48 EDT
This was a hal bug, which has snce been fixed.

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