Agreed with the initial analysis, there's nothing in device assignment
to limit to 32 devices except where downstream distros have
intentionally added a limit for support purposes. The issue here is
that the host hit a PCIe Downstream Port Containment uncorrectable
error, apparently causing at lea
Fix confirmed on Lucid 2.6.32-28.55. Arduino is back to working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690798
Title:
arduino USB serial device breaks on lucid kernel upgrade
--
ubuntu-bug
Just to be clear, 677aeafe19e88c282af74564048243ccabb1c590 is NOT in the
lucid kernel, while 6a1a82df91fa0eb1cc76069a9efe5714d087eccd is. So
lucid is carrying a patch that has been reverted upstream and as
described, changes the kernel back to the previous way of working. Git
says it was added to
Me too, seen on both the -13 and -14.25 openvz kernel. Attempting to
run on an Intel Core 2 Duo, Intel chipset.
--
linux-image-2.6.24-13-openvz refuses to boot
https://bugs.launchpad.net/bugs/210672
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I'm really surprised this is wishlist status yet seahorse seems to be
the default ssh-agent in hardy. I would consider this a serious
security issue for a shipping release (especially an LTS release).
--
keyring manager GUI offers no way to timeout ssh-agent keys
https://bugs.launchpad.net/bugs/
Public bug reported:
I have a system configured to mount /var/lib/mythtv/recordings from an
lvm logical volume, my root disk and swap are not on lvm. This worked
fine under gutsy, but since upgrading to hardy, the logical volume is
not automatically activated and I drop to a single user shell bec
*** This bug is a duplicate of bug 152505 ***
https://bugs.launchpad.net/bugs/152505
I applied the patch from 152505 and it does allow Xnest to connect,
however, there's still a problem. I have a thin client running an nfs
root installation of Fiesty. It connects to a gutsy server with xdmcp
** Attachment added: "crash file"
http://launchpadlibrarian.net/10002444/_usr_lib_gdm_gdmgreeter.108.crash.bz2
--
xdmcp/gdmchooser breakage from 2.20.0-0ubuntu3 -> 4
https://bugs.launchpad.net/bugs/152824
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Public bug reported:
Upgrading from gdm_2.20.0-0ubuntu3 to gdm_2.20.0-0ubuntu4 broken my
xdmcp setup. I have the following in /etc/gdm/gdm.conf-custom:
[daemon]
RemoteGreeter=/usr/lib/gdm/gdmgreeter
[xdmcp]
Enable=true
On a remote system, I run:
Xnest -query :1
With ubuntu3, this works fine
