** Changed in: linux (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
Title:
webcam regression after 2.6.32 under vmware
To manage notifications about
Unfortunately this is happening again. vmware fusion 5.0.3, os x
10.8.3, ubuntu precise guest with kernel 3.2.0-38-generic.
It might be related to USB bandwidth. USB webcams seem to work but only
at low resolution, 320x240. Attempting 640x480 gives a frame or two and
then freezes with
As of 12/11/12, this seems to still be happening with a fresh install of
precise.
1) flash ubuntu-12.04-preinstalled-desktop-armhf+omap4.img
2) boot pandaboard, run os configuration
3) sudo apt-get dist-upgrade
4) sudo apt-add-repository ppa:tiomap-dev/release
5) sudo apt-get install
I didn't change the status. However, I changed institutions and no
longer use AFS, so this doesn't affect me any more and I'm not set up to
work on it either. I am not sure if it is even still an issue.
Best luck!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Here is a workaround that has been working for me for a while (maybe 3y
or more). After adding an image, right click on it, select Image
Properties. Manually edit URL to be a relative path. Save and the
resulting svg will have the relative path (and it should not get changed
back to absolute).
You may close the bug, it seems still working precise and that is enough
for me. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
Title:
webcam regression after 2.6.32 under vmware
To
Several webcams as well as Kinect (via libfreenect) seem to be working
now in Precise with the default kernel 3.2.0-24.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
Title:
webcam regression
This appears to affect both packages nvidia-current and nvidia-current-
updates. The whole setup of the nvidia-provided libraries is kind of
crazy. The postinst script uses update-alternatives to add an
ld.so.conf entry for the directory /usr/lib/nvidia-current[-updates].
However, and this is
I thought this was catching me (on oneiric) but it turns out that the
only variable that wasn't taking effect from my .profile was
LD_LIBRARY_PATH. And that seems to be due to bug 47958.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Recently I've reverted to a 2.6.32 kernel in oneiric under vmware. This
is not that fun but was the only way I could work around another very
annoying regression that I documented in bug 941945.
Since reverting to 2.6.32 I've also gone back to using hgfs, and have
not seen the invalid argument
Recently I've reverted to a 2.6.32 kernel in oneiric under vmware. This
is not that fun but was the only way I could work around another very
annoying regression that I documented in bug 941945.
Since reverting to 2.6.32 I've also gone back to using hgfs, and have
not seen the invalid argument
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
Title:
webcam regression after 2.6.32 under vmware
To manage notifications
Public bug reported:
USB webcams which worked fine under lucid running as a vmware client (OS
X host) no longer work under natty or oneiric. I have yet to get *any*
webcam to work in natty or oneiric using the default kernel under
vmware; they do work in a standard non vmware setting.
The
apport information
** Tags added: apport-collected oneiric
** Description changed:
USB webcams which worked fine under lucid running as a vmware client (OS
X host) no longer work under natty or oneiric. I have yet to get *any*
webcam to work in natty or oneiric using the default kernel
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787876/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
apport information
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787877/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787878/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
Title:
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787879/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787880/+files/Card0.Codecs.codec97.0.ac97.0.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787881/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787882/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787883/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
Title:
webcam
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787884/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
Title:
webcam
apport information
** Attachment added: PciMultimedia.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787885/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787886/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787887/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787888/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787889/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
apport information
** Attachment added: PulseSources.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787891/+files/PulseSources.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787892/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787894/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787896/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: PulseSinks.txt
https://bugs.launchpad.net/bugs/941945/+attachment/2787890/+files/PulseSinks.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941945
my host is OS X 10.6.8 with vmware fusion 4.1.1
I also tested running the vm with virtualbox 4.1.8 which always gave
select timeout errors, even with kernel 2.6.32 (I don't think I ever saw
a webcam work inside virtualbox, but vmware did work before this
regression)
--
You received this bug
Joseph -
I was not able to test the v3.3-rc5-precise because the directory you
referenced only contains amd64 bins. But I did just test
v3.3-rc4-precise and the problem was still present there.
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream
--
You received
Xerxes -
This is great! Thanks for your work. I am testing now but so far I
have not seen the bug again. Of course, it was an intermittent issue,
so we should test further. The speed also looks good. Some more
details are also now updated in the above referenced bug in our ohmm-sw
project.
Public bug reported:
Some java code frequently crashes in native code with this error
message. For one reproducable example, see
http://code.google.com/p/ohmm-sw/issues/detail?id=3
This is using the default server vm in openjdk-6 6b18-1.1.10 natty
armel (pandaboard).
This appears to be a
I should add that the workaround I suggested is quite annoying, as in
order to unmount hgfs you first have to exit it in all shells
(pushd/popd does not help). I have actually had to downgrade to ubuntu
10.04; 11.04 is effectively unusable in vmware fusion for me. Is it
working for anyone else?
I should add that the workaround I suggested is quite annoying, as in
order to unmount hgfs you first have to exit it in all shells
(pushd/popd does not help). I have actually had to downgrade to ubuntu
10.04; 11.04 is effectively unusable in vmware fusion for me. Is it
working for anyone else?
Public bug reported:
Ubuntu 11.04 client, OSX 10.6.8 host, vmware fusion 4.02
Accessing files on the host via hgfs seems to work initially (after
working around 376639), but usually begins to report invalid argument
upon trying to access files within the client that have been recently
modified
Public bug reported:
Ubuntu 11.04 client, OSX 10.6.8 host, vmware fusion 4.02
Accessing files on the host via hgfs seems to work initially (after
working around 376639), but usually begins to report invalid argument
upon trying to access files within the client that have been recently
modified
Just updated to 10.04 and I can confirm this bug. And that unmounting
the drive (which apparently is now only doable from command line) works
around the problem.
--
You do not have the required permissions to use this drive.
https://bugs.launchpad.net/bugs/511302
You received this bug
I just tested this on 9.10, and was not able to reproduce. The test
machine did not have brltty removed (it still appears to be installed by
default). I hotplugged two usb to serial devices. The first was not an
FTDI, but the second was. Both /dev/ttyUSB0 and /dev/ttyUSB1 appeared
and
Public bug reported:
Binary package hint: seahorse
First, where is the documentation that gnome-keyring-manager has been
replaced by seahorse? How about telling me about this change when I
type gnome-keyring-manager like I used to. Google shows several threads
in various places where people
I stopped using krb5-auth-dialog, now I use kredentials, which works for
me.
--
RFE: optionally refresh AFS tokens too
https://bugs.launchpad.net/bugs/113347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I am seeing this too, after switching from a static IP address to DHCP.
This may be a duplicate of 249240, see comments there.
--
slow boot and network racecondition
https://bugs.launchpad.net/bugs/224220
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You can close this if you want, I don't care about it anymore.
Marty
Andreas Moog writes:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still
Yup. As I said, I did confirm that removing brltty appears to work
around the issue. I am reporting the bug because this truly is a
problem, even though there is a workaround -- you should not have to
remove a standard and obscure part of a default install just to get a
usb to serial adaptor
Public bug reported:
Binary package hint: hal
I plugged in an FTDI usb to serial adaptor. I could see in syslog that
it was detected and initially set up correctly as /dev/ttyUSB1, since
this was the second usb to serial that I'd plugged into the machine at
this point (the first has always
Bjorn - thanks for the thoughts help on this. I've been traveling a
lot and unfortunately don't have time to work on this issue for the
foreseeable future. I'll probably revisit it when I upgrade my systems
to ubuntu 7.1, which will hopefully be sometime in the next year. For
now I'm just
Yes, I am aware of the symlink workaround, and no, it does not solve the
problem, which is pretty surprising. Details below.
It also appears that my evaluation and workaround above was also
incorrect, or at least incomplete.
And it looks like I never mentioned the all details of the setup,
Alexandre Otto Strube writes:
Marty, it doesn't look like a bug, does it? may we close it?
Yes, go ahead and close, in any event I can't reproduce it anymore, I
switched to atheros.
Thanks for getting in touch with me though.
Luck,
Marty
--
regression: prism2 fails to connect to some
I used the Desktop CD.
In fact I used the very same CD to install on two different machines.
One had this issue and the other did not.
Colin Watson writes:
Did you install using the desktop CD or the alternate install CD? I ask
because squashfs in Feisty is known not to detect errors
Update: I just realized I may have been on the wrong track here. I saw
the same DHCP failure yesterday even using prism54 drivers, and I think
it was due to a misconfigured firewall. At some point I had configured
firestarter on my laptop, but of course it is simple minded and does not
work
Public bug reported:
Been trying to track down a problem with my new ubuntu 7.04 install for
a week or two. The issue manifests when I come in to work each morning.
At that point my workstation is typically showing a screensaver. The
screensaver is running and the machine is not hung. However
** Attachment added: krb5-auth-dialog-aklog-patch-vona-5-8-07.patch
http://librarian.launchpad.net/7584191/krb5-auth-dialog-aklog-patch-vona-5-8-07.patch
--
RFE: optionally refresh AFS tokens too
https://bugs.launchpad.net/bugs/113347
You received this bug notification because you are a
Public bug reported:
Binary package hint: krb5-auth-dialog
krb5-auth-dialog is getting better and better. One thing it seems to
still lack, even in current svn, is a feature to also refresh AFS tokens
after getting or renewing kerberos tickets.
Such a feature is important to people like me who
Public bug reported:
Binary package hint: linux-source-2.6.20
Just installed ubuntu 7.04. My machine has
Network controller: Intersil Corporation ISL3890 [Prism GT/Prism
Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)
which I has been stable for years using the prism54 (fullmac) drivers.
** Attachment added: config-2.6.20-15-generic
http://librarian.launchpad.net/7572404/config-2.6.20-15-generic
--
regression: prism2 fails to connect to some access points, prism54 works
https://bugs.launchpad.net/bugs/112919
You received this bug notification because you are a member of
** Attachment added: config-2.6.20.3-ubuntu1-vonadell
http://librarian.launchpad.net/7572406/config-2.6.20.3-ubuntu1-vonadell
--
regression: prism2 fails to connect to some access points, prism54 works
https://bugs.launchpad.net/bugs/112919
You received this bug notification because you are
** Attachment added: nm-dhcp-fail-syslog.txt
http://librarian.launchpad.net/7572408/nm-dhcp-fail-syslog.txt
--
regression: prism2 fails to connect to some access points, prism54 works
https://bugs.launchpad.net/bugs/112919
You received this bug notification because you are a member of Ubuntu
oops guess I don't have a successful-case syslog snip handy.
--
regression: prism2 fails to connect to some access points, prism54 works
https://bugs.launchpad.net/bugs/112919
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: kernel-package
For whatever reason it appears that the initial install of
/usr/sbin/mkinitramfs on one of my systems, as laid down by the ubuntu
7.04 installer, was borked. The file was present, had the same date and
size as on another (working) ubuntu
Forgot to mention: I did run the media verify on the install cd, and it
did not report any problem.
--
RFE: [ubuntu installer and] make-kpkg should be resilient to failure of
mkinitramfs
https://bugs.launchpad.net/bugs/112365
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Binary package hint: gnome-panel
It appears that my fresh install of ubuntu 7.04 laid down a faulty
/usr/lib/libglib-2.0.so.0.1200.11 file. That's bad (installer media did
verify ok). But that's not what I'm intending to report here.
The file was present and had the
Public bug reported:
Binary package hint: debian-installer
It appears that my fresh install of ubuntu 7.04 laid down a a few faulty
binary files, including
/usr/sbin/mkinitramfs
/usr/lib/libglib-2.0.so.0.1200.11
In each case the file was present and had the correct size and date, but
had
66 matches
Mail list logo
