This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested in
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Fix Released => Incomplete
--
USB camera is not automatically mounted
https://bugs.launchpad.net/bugs/157700
You received this bug notification because you are a member of Ubunt
Addition: I do not know when it was re-introduced. I switched from Hardy
directly to Karmic.
--
USB camera is not automatically mounted
https://bugs.launchpad.net/bugs/157700
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
This seems not to be working again in 2.6.31-15-generic
USB-sticks are mounted automatically, but my camera is not.
lsusb finds it:
Bus 004 Device 005: ID 0784:1691 Vivitar, Inc.
dmesg (first line is disconnecting camera, then connecting again):
[ 8110.264058] usb 4-2: USB disconnect, address 5
Hi Johan,
Thanks for testing and the update. The kernel should be the same for
both the Ubuntu and Kubuntu flavors so I'd assume you do not need to
test the Kubuntu flavor. I'm going to close this report for now. If
you notice any sort of regression, please feel free to reopen (ie switch
the st
Thank you for notification.
Tested with Ubuntu 8.04 Hardy Heron-Alpha 2 liveCD on 07-01-2008.
This time my camera (USB Mass Storage Traveler DC-9400) is detected, while in
Kubuntu Gutsy, the camera is not.
Because it concerns the kernel I'd say that I do not need to test also with
Kubuntu Hardy
Hardy Heron Alpha2 was recently released. It contains an updated
version of the kernel. You can download and try the new Hardy Heron
Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ .
You should be able to then test the new kernel via the LiveCD. If you
can, please verify if
I'm retargeting this bug towards the upcoming Hardy kernel. I've tagged
this as "hardy-kernel-candidate" so that we make sure to retarget this
report once the new release is out. However against the linux-
source-2.6.22 package this is being marked as "Won't Fix" as it does not
meet the criteria
