kernel-packages team mailing list archive

["C.H.E.W.S." <tchews@xxxxxxxxx>]

This bug has been fixed for quite some time for me I am running the latest
stable release 13.04


On Sat, Aug 10, 2013 at 4:52 AM, Christopher M. Penalver <
christopher.m.penalver@xxxxxxxxx> wrote:

> C.H.E.W.S., could you please confirm this issue exists with the latest
> development release of Ubuntu? ISO images are available from
> http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
> could you please run the following command in the development release
> from a Terminal (Applications->Accessories->Terminal), as it will
> automatically gather and attach updated debug information to this
> report:
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, could you please test the latest upstream kernel available following
> https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
> upstream developers to examine the issue. Please do not test the daily
> folder, but the one all the way at the bottom. Once you've tested the
> upstream kernel, please comment on which kernel version specifically you
> tested. If this bug is fixed in the mainline kernel, please add the
> following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested. For
> example:
> kernel-fixed-upstream-v3.11-rc4
>
> This can be done by clicking on the yellow circle with a black pencil icon
> next to the word Tags located at the bottom of the bug description. As
> well, please remove the tag:
> needs-upstream-testing
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> As well, please remove the tag:
> needs-upstream-testing
>
> If you are unable to test the mainline kernel, please comment as to why
> specifically you were unable to test it and add the following tags:
> kernel-unable-to-test-upstream
> kernel-unable-to-test-upstream-VERSION-NUMBER
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results. Thank you for your
> understanding.
>
> ** This bug is no longer a duplicate of bug 1082920
>    usb-storage: Not Ready: Medium not present after scsi eject command
>
> ** Package changed: udisks (Ubuntu) => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
>        Status: Confirmed => Incomplete
>
> ** Tags added: needs-kernel-logs needs-upstream-testing oneiric
> regression-potential
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/863364
>
> Title:
>   Ubuntu 11.10 amd64 won't mount flash drive after ejected without
>   restart
>
> Status in “linux” package in Ubuntu:
>   Incomplete
>
> Bug description:
>   If I safe remove my fat 32 flash drive on any of the other linux
>   machines plugging it in does not auto-mount. When I open nautilus it
>   and click it, it say not authorized cannot mount. Restarting with
>   flash-drive in mounts it but when clicking eject it says not
>   authorized but ejects anyway, but will no longer mount. read and write
>   to it works on restarts. This is a recent bug since an update or
>   package install since I have had it for 3days and first day it has
>   done this.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/863364/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/863364

Title:
  Ubuntu 11.10 amd64 won't mount flash drive after ejected without
  restart

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  If I safe remove my fat 32 flash drive on any of the other linux
  machines plugging it in does not auto-mount. When I open nautilus it
  and click it, it say not authorized cannot mount. Restarting with
  flash-drive in mounts it but when clicking eject it says not
  authorized but ejects anyway, but will no longer mount. read and write
  to it works on restarts. This is a recent bug since an update or
  package install since I have had it for 3days and first day it has
  done this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/863364/+subscriptions