This is probably the same as #376128, which has been fixed in newer
kernels (anything not 2.6.28).
--
killing slattach with bytes in buffer freezes system
https://bugs.launchpad.net/bugs/396930
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I sent the patch to sta...@kernel.org, so hopefully it will get included
in 2.6.28.11. I assume it will make its way into Ubuntu after that?
--
ftdi_sio doesnt work propertly
https://bugs.launchpad.net/bugs/376128
You received this bug notification because you are a member of Ubuntu
Bugs, which
The output of "dmesg" after you have this problem would be helpful in
tracking the bug down. It may be a hardware issue, but dmesg would help
determine that.
--
conflicts between two USB FTDI devices
https://bugs.launchpad.net/bugs/239794
You received this bug notification because you are a mem
Hi Ambricka,
All 2.6.28 kernels have a problem where FTDI devices will cause problems if the
device is closed when the FTDI still has data in its buffer. I'd suggest
trying a new kernel -- it's easy. Just download and install:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30.2/linux-ima
OK, there's no such thing as 2.6.28-stable anymore :) I'll send to the
Ubuntu kernel team instead.
--
ftdi_sio doesnt work propertly
https://bugs.launchpad.net/bugs/376128
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Newer Broadcom cards need new versions of ndiswrapper. Newer versions
of ndiswrapper (since 1.13) also fix problems with wpa_supplicant, as
long as the recommend "wext" wpa_supplicant driver is used. Network-
Manager selects "ndiswrapperoblem" instead. Changing the network-
manager source to rem
Sorry, cut&paste error, the current network-manager selects
"ndiswrapper".
--
Cannot associate with unencrypted networks using bcm43xx
https://launchpad.net/bugs/42504
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Yeah, I think it does:
$ X >/tmp/foo 2>&1
$ grep -A1 ^sh /tmp/foo
sh: sed: not found
sh: grep: not found
Not loading fglrx module; not used in /etc/X11/xorg.conf
sh: sed: not found
sh: grep: not found
Not loading fglrx module; not used in /etc/X11/xorg.conf
$ which sed
/bin/sed
BTW that seems like a bogus check anyway; you could easily be running
multiple X servers with different config files.
--
Module fglrx isn't loaded
https://launchpad.net/bugs/63912
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
There's a lot of confusing and unrelated info in here, but one clear
point (to me, at least) is that the "wext" wpa_supplicant driver should
be used with the version of ndiswrapper in Edgy, not "ndiswrapper".
This was discovered by me in comment #37, rediscovered by Jean Pierre in
comment #48, and
Public bug reported:
Binary package hint: linux-source-2.6.22
The gusty livecd from 2007/06/13 (gutsy-desktop-powerpc+ps3.iso) does
not boot on the PS3.
At the kboot prompt, it prints
Loading kernel with initrd...success.
Booting system...
and then freezes (cursor stops blinking, ctrl-alt-de
I ran into the same problem and the attached patch fixes the problem for
me
** Attachment added: "fix-swcursor-crash"
http://launchpadlibrarian.net/36236768/fix-swcursor-crash
--
[RV570] X crashes with SIGSEGV in xf86_reload_cursors() with SWcursor
https://bugs.launchpad.net/bugs/371405
You r
On Debian, downgrading "pdftk" from 1.41+dfsg-7 to version 1.41-3 fixes
the problem.
--
hyperlinks do not work
https://bugs.launchpad.net/bugs/437074
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Public bug reported:
I didn't experience this bug, but I was looking through the code and
just noticed that it can't work as intended. This is from rev 5600:
--- bin/ubiquity-dm 2012-07-16 14:29:13 +
+++ bin/ubiquity-dm 2012-08-20 05:17:16 +
@@ -359,6 +359,7 @@
# Acc
Hi Jan,
The later hang is probably because of a change in the kernel (>2.6.32) that
breaks open-iscsi 2.0.871.
I just reported that one to Debian http://bugs.debian.org/603990
But partman-iscsi is definitely the culprit for this installation bug.
What's the hold-up? In the interest of trying to
Public bug reported:
Binary package hint: open-iscsi
Open-iscsi needs this patch
http://git.kernel.org/?p=linux/kernel/git/mnc/open-iscsi.git;a=commitdiff;h=f0b670c016c85c882bb0583eaef8ea2f7147d4af
for kernels after 2.6.32 to work correctly, particularly when connecting to
iSCSI targets that
Creating the symlink manually with
ln -s /lib/init/upstart-job /etc/init.d/whoopsie
allows the upgrade to complete.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1272269
Title:
package whoopsie
Public bug reported:
Binary package hint: partman-iscsi
On a recent Maverick install to iscsi root, the file
/etc/iscsi.initramfs contained these four lines at the end:
ISCSI_USERNAME="(null)"
ISCSI_PASSWORD="(null)"
ISCSI_IN_USERNAME="(null)"
ISCSI_IN_PASSWORD="(null)"
This seems to have come
18 matches
Mail list logo
