On jaunty RC, this issue is gone. Works a treat.
The SCSI ZIP drive now shows as a mass storage device, and is getting
seen correctly.
Jaunty is very slick indeed. It's very impressive.
--
Nautilus can't open usb flash drive
https://bugs.launchpad.net/bugs/246189
You received this bug
I know Nautilus is confusing the virtual and real SCSI world because-
taking the ZIP drive out clears the issue. I happen to have hardware
that the GNOME project has not seen in a good long while, that's all.
They haven't tested their code against this hardware because it has
become rare over the
Nautilus is trying to open the ZIP drive when double-clicking on the
USB drive icon. It's not really using /dev/sdc.
--
Nautilus can't open usb flash drive
https://bugs.launchpad.net/bugs/246189
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
This system has a ZIP 100 internal SCSI drive. This is a real SCSI
removable media drive, which is confusing Nautilus, which treats USB
flash drives as fake SCSI devices. It's likely that nobody expects
such a dinosaur to still be in use, so I have a hardware configuration
that is, er, untested,
gvfs-bin was most assuredly NOT available when I tried to install it,
and I did have to resort to the installation of the downloaded .deb
file. Don't call me a liar. I got 404 file not found using the
standard shipped repositories.
If something gets quite some work, does it not follow that it
And now lshal after drive insertion. It seems to find /dev/sdc and
/dev/sdc1, which is the partition.
** Attachment added: Output of lshal after key plugged in
http://launchpadlibrarian.net/16495364/lshal-after
--
Nautilus can't open usb flash drive
https://bugs.launchpad.net/bugs/246189
When the flash drive is inserted, kernel modules are modprobed and hal
gets fired up, causing the icon to appear. Evidence: nothing in
.xsession-errors, happy kernel module activity in /var/log/messages, and
happy kernel modules and hal activity in /var/log/syslog, which is
attached as syslog to
Ok, attached here is gvfs-mount -li, per request.
It appears this isn't Nautilus after all, nor a kernel or hal problem.
It seems gvfs on amd64 is broken. I note I can manually mount the usb
flash drive, which doesn't need gvfs or fuse, but Nautilus does now need
this for a mount. Nautilus is
Public bug reported:
Binary package hint: nautilus
Hardy Heron, Nautilus 2.22.3
When inserting a USB flash drive (formatted vfat) the USB drive icon
appears in Places|Computer.
Double-clicking this yields the generic Nautilus Unable to mount
location - Can't mount file dialog.
Putting
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/15867116/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/15867117/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/15867118/ProcStatus.txt
--
Nautilus
10 matches
Mail list logo
