I start supposing that we're having a different problem here. You say that the webcam isn't recognized as a v4l device, so it cannot be used by
cheese, and other hal-enabled programs.
However, as your sysfs.tar.gz file says (and as I can reproduce locally on my machine), the
/sys/class/video4linux/video0
symlink is created when the cam is connected (and deleted when it's removed). This lets me think that the webcam is actually recognized as a video4linux device.
Still, I can reproduce the bug in Hardy.
Btw, I noticed that in freedesktop, the bug is reported with low priority (and here as undecided). I would say this bug is
more than low priority, because it makes (non-fundamental) hardware unusable, so it should be at least rated as normal.
I start supposing that we're having a different problem here. You say that the webcam isn't recognized as a v4l device, so it cannot be used by
cheese, and other hal-enabled programs.
However, as your sysfs.tar.gz file says (and as I can reproduce locally on my machine), the video4linux/ video0
/sys/class/
symlink is created when the cam is connected (and deleted when it's removed). This lets me think that the webcam is actually recognized as a video4linux device.
Still, I can reproduce the bug in Hardy.
Btw, I noticed that in freedesktop, the bug is reported with low priority (and here as undecided). I would say this bug is
more than low priority, because it makes (non-fundamental) hardware unusable, so it should be at least rated as normal.
Cheers,
Alfredo