Public bug reported:
This is for hardy-proposed. The latest kernel series causes virtual-
box-2.1.4 to fail in compilation -- somewhere around an include for
posix_types.h. No problems with earlier series -- and I don't see any
bug reports on VirtualBox about compilation failures.
I don't have an
Sorry -- can't help. I already switch back to the hardy-updates kernel,
and debian package management makes switching between kernel & linux-
headers versions much too painful. Unlike the previous poster, I saw the
errors coming out after posix_types.h instead of assert.h -- but then,
he's using th
Public bug reported:
Binary package hint: linux-image-2.6.20-16-generic
My D-link DWL-G120 card under ndiswrapper works correctly under
2.6.20-15, but fails to connect via nm-applet under 2.6.20-16. The
device exists, but in syslog I receive:
nm_device_802_11_wireless_set_essid (): error setting
Oh I forgot to add. This is under feisty with the standard repositories
on a new installation. All packages are updated to 8/13/07, obviously
exception the kernel which I had to downgrade to 15.
--
2.6.20-16 kernel image and nm-applet fail with DWL-G120
https://bugs.launchpad.net/bugs/132285
You
And finally, it's not a device recognition issue. The device is
recognized, I get a reasonable ifconfig wlan0, and ap scanning appears
to work correctly - all local ap's are shown under nm-applet.
--
2.6.20-16 kernel image and nm-applet fail with DWL-G120
https://bugs.launchpad.net/bugs/132285
Yo
Further investigation reveals that this is an ndiswrapper bug, or a bug
in the way ndiswrapper gets loaded. It's intermittent under 15 - I just
got "lucky" a few times with that kernel. But if I modprobe -r
ndiswrapper and then modprobe ndiswrapper, everything works again. I
would try to debug with
The one currently in karmic -- apparently this one, builds empty lib and
lib-dev versions, and mpich2 itself lacks all libraries.
It's pretty much useless for anything but running hostname on 20 machines.
The version that apparently is wending it's way through debian is the same -- I
guess it's
I'm getting this (or similar) X crash on lucid amd64:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6d) [0x48672d]
1: /lib/libc.so.6 [0x2ad1d63337d0]
2: /usr/bin/X(xf86_reload_cursors+0x75) [0x4b6a75]
3: /usr/lib/xorg/modules/drivers//intel_drv.so [0x2ad1d7c91f08]
4: /usr/bin/X(xf86CrtcSetMode+0x25c)
Ignore that -- it was an old crash log. My crash could be anything,
since it didn't update the log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/491672
Title:
[i945gm] X server crash (SIGSEGV) in l
