Looks like nobody is interested, so I did a dirty hack to make upower
ignoring Apple Wireless Keyboard. The patch is attached.
** Patch added: upower.patch
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1245287/+attachment/3906593/+files/upower.patch
--
You received this bug
Posting the pre-compiled package for patch testing and for everybody
else interested.
** Attachment added: upower_0.9.22-1ubuntu3_amd64.deb
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1245287/+attachment/3906594/+files/upower_0.9.22-1ubuntu3_amd64.deb
--
You received this bug
I have 13.04 and have power indicator reporting 0% per Apple Wireless Keyboard.
Upower daemon said no valid voltage value found for device.
Is there any chance to ask upower to ignore keyboard or detect voltage
correctly?
--
You received this bug notification because you are a member of Ubuntu
Had the same issue with my HP EliteBook 2170p having next version of
AR9462 with ID 0cf3:311e in Rarian. Fixed by blacklisting it in the
btusb and ath3k drivers. The ready deb package is attached
** Attachment added: ar9462-dkms_1.5_all.deb
Thanks to m0sia for the patched package.
Why not to add patch functionality as an option to the official package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527267
Title:
Application Indicators
Commenting 4 lines in /etc/pulse/default.pa as mentioned before helped
me too. But hardware tab is still empty (HP Mini 2140). No slmodemd is
here.
--
[Karmic] processes holding /dev/dsp* or /dev/snd/pcm* cause pulseaudio: card
not found - Null Output / Dummy Output
The same for me using HP/Compaq 6720s laptop with Ubuntu Hardy, which is
up to date
--
mplayer and vlc causes backlight to go to full brightness
https://bugs.launchpad.net/bugs/204805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The same for me.
--
Laptop TFT monitor - brightness level is not saved
https://bugs.launchpad.net/bugs/35223
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I got SIGSEGV using gnome-screensaver-dialog.
** Changed in: gnome-screensaver (Ubuntu)
Status: Invalid = New
** Attachment added: New backtrace file
http://launchpadlibrarian.net/14045230/gnome-screensaver-dialog.txt
** Summary changed:
- gnome-screensaver-dialog crashed with
