As of the release of Dapper, this works for me now too. Using the
bcm43xx driver (i.e. not ndiswrapper). Thanks for fixing this! :)
--
Cannot associate with unencrypted networks using bcm43xx
https://launchpad.net/bugs/42504
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
Public bug reported:
There are numerous bug reports on the xserver-xorg-input-synaptics
package about missing functionality, and one that I opened about the
/dev/input/event? device node jumping around across reboots.
Most of these missing functionality bugs are probably due to people
using the /
Crap, I thought I reported this on udev, not on xserver-xorg-input-
synaptics. Can someone move it to that package? Or should I just open a
new one on udev? Sorry about that...
--
add a /dev/input/touchpad symlink in 60-symlinks.rules
https://launchpad.net/bugs/50968
--
ubuntu-bugs mailing list
When I tried before, using /dev/psaux as the device left me with very
basic functionality (i.e. no control over speed, tap-to-click, no scroll
areas, etc.), but using the event device instead worked.
I'll try it again and update the bug.
--
add a /dev/input/touchpad symlink in 60-symlinks.rules
I see that udev 093-0ubuntu2 has a new 65-persistent-input.rules file
which should be a fix for this. However, on my system it doesn't create
the by-id and by-path directories under /dev/input, nor any other
symlinks to the event device(s) that I can see.
--
add a /dev/input/touchpad symlink in 6
It works now w/ /dev/psaux and the auto-dev protocol. Thanks Scott.
Wes
On 6/28/06, Scott James Remnant <[EMAIL PROTECTED]> wrote:
>
> Attach your Xorg.0.log
>
> --
> add a /dev/input/touchpad symlink in 60-symlinks.rules
> https://launchpad.net/bugs/50968
>
--
"Small acts of humanity amid the
This is fixed by using the "auto-dev" protocol and /dev/psaux as the
device. This causes the driver to automatically use the correct event
device node. This bug should be closed.
--
/dev/input/event? device node changes across reboots
https://launchpad.net/bugs/44768
--
ubuntu-bugs mailing list
I can confirm this exact same behavior on my Dell Inspiron 6000 (also w/
ipw2200 hardware). NM can't create or connect to ad-hoc networks (the
association "ball" never goes green, so it doesn't even get to the DHCP
step). Associating and acquiring an address using command line tools
(iwconfig and d
Sorry, I forgot to mention that in my case at least, the ad-hoc network
in question had no encryption and was created by an XP SP2 machine using
the network creation wizard and the Internet connection sharing service.
--
ad-hoc networks don't work with ipw2200
https://launchpad.net/bugs/75358
--
I can confirm this bug. Any update on a fix?
--
Export to PicasaWeb fails with error
https://launchpad.net/bugs/76891
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
On new installs of 12.04 with the latest packages as of Oct. 29, 2012,
22:50 UTC, the /usr/lib/jvm/default-java does not get created. After
installing openjdk-6-jdk, my /usr/lib/jvm/ dir looks like this:
ls -la /usr/lib/jvm
total 24
drwxr-xr-x 5 root root 4096 Oct 29 22:12 .
11 matches
Mail list logo
