http://qa.mandrakesoft.com/show_bug.cgi?id=159
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|i18n |i18n
------- Additional Comments From [EMAIL PROTECTED] 2003-03-04 17:55 -------
floppy-switching bug is still in the latest 9.1 cooker version I have here.
When I read a floppy with gnome or kde (using the floppy icon), and hit refresh,
the floppy can't be read anymore.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date:
description:
Again, I am not sure, where to put the bug-report, hopefully this category is at
least a little bit appropriate ;-)
I don't know if all of this problem has the same bug as origin, but there are a
lot of similar symptoms:
- if I click on floppy in KDE, Konqueror opens and shows the contents of the
diskette. When i delete some files, the files are gone but the space on disk
doesn't grow. So if I delete a file from a full disk and try to copy the SAME
file onto the disk afterwards, it fails ("No free space available").
- When I view a diskette with Gnome/Nautilus, eject the diskette, put it in the
drive again and click on the refresh-button, Nautilus says, it has "no
permissions" to view the diskette. From this moment, the same message appears
also in Konqueror. When I try to access the floppy with the shell, it says "cd:
/mnt/floppy/: Input/output error". After a restart everthing is fine again. This
bugs renders it nearly impossible to use a lot of disks, because after every
refresh, a restart is needed.
- After I have formatted a disk in gfloppy, I often cannot access the floppy
afterwards (no permissions).
- When these things happens, there is always one of the following messages
while the shutdown: "/mnt/floppy illegal seek" and "umount2: device or ressource
busy"
- is it normal, that df -h shows "none" as the filesystem?
I hope this helps to find the underlying failure. BTW: I also had similar
failures with 8.2 on another computer. If I should try anything specific with my
9.0b4-Installation to help Mandrake-team with this bug, just mail me,
Michael
