CID: 201201-10377, 201201-10378
On 12.10 and 13.04
The "safely remove" option was gone, thus the card reader itself won't be
removed.
However, this bug still affecting 12.04.3 Precise (3.8 kernel), series
nominated
--
You received this bug notification because you are a member of Ubuntu
Deskto
Also affects Realtek [0bda:0129] Card reader.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/504440
Title:
sd card "safely remove drive" kills reader device
To manage notifications a
** Changed in: gvfs (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/504440
Title:
sd card "safely remove drive" kills reader device
To manage
oshunluvr: If you're still seeing this bug, please open a new bug, and
add a comment here with the bug number (and mention this bug in your new
bug).
In your new bug please state the model/make of the card reader you're
using (include the output of lsusb if USB attached).
Dave
--
You received
This was actually fixed in 13.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/504440
Title:
sd card "safely remove drive" kills reader device
To manage notifications about this bu
Wow, this bug has persisted from 9.10 to 13.04. Is this ever going to be
addressed?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/504440
Title:
sd card "safely remove drive" kills re
This bug has been reported on the Ubuntu laptop testing tracker.
A list of all reports related to this bug can be found here:
http://laptop.qa.ubuntu.com/qatracker/reports/bugs/504440
** Tags added: laptop-testing
--
You received this bug notification because you are a member of Ubuntu
Desktop
Would be nice to see a fix to this, if I'm copying data from a few
memory cards I have to reboot between each one because the whole card
reader is disconnected rather than just the media in the drive. (Card
reader using m-board USB, 11.10).
--
You received this bug notification because you are a
@Jonathan: I know what you mean about lots of bug reports, but having
them separate is most pragmatic. Bug reports easily get muddled up with
people going in different directions, so it works out best to have
multiple clearly-defined reports.
--
You received this bug notification because you are
Dave Gilbert [2011-01-22 15:59 -]:
> Is there no way to differentiate between a storage device that needs to
> be safely removed and a media in a reader?
There is, it works fine for e. g. CD-ROMs, SD card readers, and so on.
The problem is that most USB sticks lie and claim that they would hav
David Tombs wrote:
> how about opening up a new bug for the text change?
> Trying to transform this bug into a UI change might create too much
> confusion. :)
OK. There is also bug #404185 which seems highly relevant to all of
this.
I'm a little concerned about having too many bugs all relate
I like idea #2. Jonathan, how about opening up a new bug for the text
change? Trying to transform this bug into a UI change might create too
much confusion. :)
@Dave: Not sure exactly what you're asking. An external USB HDD and an
internal USB-attached card reader appear exactly the same to the sy
Two ideas:
(1) Is there any way to implement a "reconnect device" option, as
suggested in comment #7 some months ago?
While less than ideal, this would be one way to help people who make
this mistake to recover from it themselves.
(2) Alternatively, a language change to the context menu, so the
Is there no way to differentiate between a storage device that needs to
be safely removed and a media in a reader?
Dave
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in ubuntu.
https://bugs.launchpad.net/bugs/504440
Title:
s
As Martin Pitt wrote, the default option is now "Eject", which mostly
fixes the usability issue. One actually has to right-click and choose a
non-default option to encounter this bug. Note also that I regularly do
use "Safely Remove Drive" when removing a USB HDD because that is the
option which po
The fact that it's still possible to disable an internal USB device such
that a reboot or opening up the case is required screams very loudly
that this issue is NOT settled in the slightest. This should NOT be
labeled "WON'T FIX". I've seen references to forcing the operating
system to rescan all
Although "Won't Fix" may be right for the bug against gvfs, there is a
bug here which really, really needs fixing. Steps to reproduce on my
machine:
1. Boot to desktop and log in.
2. Insert a memory card and wait for the icon to appear on desktop.
3. Select "Safely Remove Drive" in the contextual
@oriolpont
See my last comment .. reboot did nothing, but shut down the PC and
waiting a little before starting it did the trick.
Now what I don't get is that I did another "Safely remove" by accident,
and it did not kill the internal card reader this time.
Go figure.
--
sd card "safely remove
h3, it seems that you have a different issue. If you read the bug
description it says that "kills reader device" just means that it stops
being powered and it is not repowered until next reboot. Apparently,
what you experience is a permanent break, so it is something unrelated
to this bug report.
Just found how to fix my problem .. a simple reboot wont do it. I must
"Shut Down" my computer, wait a couple of seconds and start it.
Really convenient.
--
sd card "safely remove drive" kills reader device
https://bugs.launchpad.net/bugs/504440
You received this bug notification because you are
Just rebooted again just to be 100% sure. My internal card is still dead
(no lights when i insert a SD card).
This god damn button should be called "Brick your drive", not "Safely
remove drive".
--
sd card "safely remove drive" kills reader device
https://bugs.launchpad.net/bugs/504440
You recei
I'm on Ubuntu 10.04 and I have the same problem .. Since I did a "Safely
remove" on my internal card reader it stopped working .. even after
rebooting.
Then I started using my external USB card reader since I needed to keep
working, and after a while I always ended up clicking "Safely remove" ..
a
Is there at least somewhere we could turn for instructions on how to
restart the device without rebooting? Or is that impossible?
--
sd card "safely remove drive" kills reader device
https://bugs.launchpad.net/bugs/504440
You received this bug notification because you are a member of Ubuntu
Desk
We changed the default action (in the nautilus bar) to do an eject, not
a safe removal, for this very reason. You really do not want to remove
the internal drive. :-)
I'm afraid there is nothing we can do about this right now, since this
kind of hardware unhelpfully does not say that it is not rea
Affects me in the latest 10.04! Nothing done about the bug. Whatever
decision, do anything on this, please!
--
sd card "safely remove drive" kills reader device
https://bugs.launchpad.net/bugs/504440
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subs
Let "safely remove" work as it does. But it is very necessary to add
"reconnect device" command for internal card readers (or maybe for any
removable storage). This would solve the problem perfectly.
--
sd card "safely remove drive" kills reader device
https://bugs.launchpad.net/bugs/504440
You r
I cannot see a regression here: In up-to-date Jaunty (supported updates,
at least), the "safely remove" option that I see in desktop and nautilus
sidebar is actually called "Unmount" and it does the same as Unmount
does in Karmic: it unmounts the filesystem.
Unmounting the filesystem does not prev
FYI In the previous version 9.04. "Safely remove" worked correctly and
didn't kill the internal reader. I discovered that unmount and eject do
work correctly in 9.10 as others have mentioned but to those who are
used to using usb in windows, safely remove seems like the obvious
choice. I believe al
Jouni, the problem is with internal readers, which cannot be reconnected
without disassembling the computer.
Also, the description says "Drive worked fine until last couple of weeks": do
you mean that this has been a regression in a Karmic update? This is not my
case: since the release of the "s
Nautilus has also option to unmount memory card. Then you can change
card. Safely remove drive option is useful to remove whole card reader
You can then use it as external card reader.
After card reader has been safely removed it can be physically
reconnected and it works again. Hope this helps.
I found the same problem in my 32bit Ubuntu 9.10 as well.
--
sd card "safely remove drive" kills reader device
https://bugs.launchpad.net/bugs/504440
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in ubuntu.
--
desktop-bugs mailin
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37570440/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/37570442/XsessionErrors.txt
--
sd card "safely remove drive" kills reader device
https://bugs.launchpad.net/bugs/504440
Y
32 matches
Mail list logo
