Public bug reported:
Prior to installing the xorg-edgers ppa, as well as during earlier
versions from the ppa, the brightness settings panel/OSD would recognize
and display any brightness settings changes that were initiated by the
fn-keys of my Thinkpad Edge E220s. This has recently stopped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020435
Title:
[xorg-edgers] Libnotify/brightness settings no longer displays/change
with fn keys
To manage notifications about this bug go to:
Just recieved some inte/gmal specific updates and the bug is still
present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020435
Title:
[xorg-edgers] Libnotify/brightness settings no longer
Public bug reported:
Related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790755
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/882619
There is a fair bit unexpected behavior related with this bug so it's a
bit hard to tie down, but it most certianly does not seem fixed.
It's
** Attachment added: one of the brightness event handlers.
https://bugs.launchpad.net/bugs/990938/+attachment/3114532/+files/asus-brightness-down
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Ubuntu 12.04 AMD64, Lenovo Thinkpad Edge E220s. Hitting the Brightness Keys
Causes the System to Hang
+ Ubuntu 12.04 AMD64: [Lenovo Thinkpad Edge E220s] Hitting the Brightness Keys
Causes the System to Hang
** Summary changed:
- Ubuntu 12.04 AMD64: [Lenovo Thinkpad Edge
Grabbed 3.4.0-030400rc4-generic #201204230908 SMP Mon Apr 23 13:10:03 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux from the mainline PPA just to verify it was not
the result of an ubuntu specific patch(or that it had been fixed upstream).
The bug is still present.
--
You received this bug
More logging. This is from the 32Bit kernel. I switched over because it
happens way less frequently.
ThinkPad-Edge-E220s kernel: [ 36.773814] thinkpad_acpi: unhandled HKEY event
0x6050
Apr 29 02:14:11 ThinkPad-Edge-E220s kernel: [ 36.773816] thinkpad_acpi:
please report the conditions when
Public bug reported:
Some type of intial misdetect perhaps? The system loads, everything is
working well but for the first 5-10 seconds after the desktop/cursor
loads neither input device responds to any input.
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name=SynPS/2 Synaptics TouchPad
** Summary changed:
- [Lenovo Thinkpad E220s] Touchpad/Trackpoint Does Not Respond For 5-10 sec
After Startup
+ [Lenovo Thinkpad E220s] Touchpad/Trackpoint Does Not Respond To Input For
5-10 Seconds After Startup
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I went out and bought an external mouse (Logitech M305) to test out and
see if it was an issue with how X handled mice on this specific unit and
it most certainly is not a generic error. The external mouse is usable
even before the desktop starts loading(the purple ubuntu screen)
--
You received
I've been meaning too, but I can't seems to get the bug to take on x86
when working on the internal disk (as opposed to when I could do it off
the live image). This is my primary machine sadly and I can't just go
reinstalling x86-64 build just to file a but report.
--
You received this bug
I'm in no way trying to be rude or anything.
Honestly I am not, but I found this:
http://www.ubuntu.com/certification/hardware/201103-7427/
And considering this bug has not been marked as anything but triaged,
how can that be?
--
You received this bug notification because you are a member of
** Summary changed:
- Ubuntu 12.04 AMD64/x86: [Lenovo Thinkpad Edge E220s] Hitting the Brightness
Keys Causes the System to Hang
+ Ubuntu 12.04 AMD64: [Lenovo Thinkpad Edge E220s] Hitting the Brightness Keys
Causes the System to Hang
--
You received this bug notification because you are a
It looks like this bug is a dub if this one :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/78773
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994968
Title:
[Lenovo Thinkpad E220s]
Not that anyone seems to taking note of this bug, but for the sake of
postarity, I done some digging and it seems to be related to the 3.5
kernel update. A simple revert to 3.2 kernel will solve the bug, if you
are using 12.04 anyway.
--
You received this bug notification because you are a
I just took a look and my previous comment is obviously wrong its not a
dup of that bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994968
Title:
[Lenovo Thinkpad E220s] Touchpad/Trackpoint
The only thing that worked was the classic proto=bare modprobe
directive. But that is hardly a real solution. It makes the mouse
basically useless.
** Package changed: xserver-xorg-input-synaptics (Ubuntu) = xserver-
xorg-input-evdev (Ubuntu)
--
You received this bug notification because you
I've tried explicity specifiy one of the device as follows before all
others are loaded:
Section InputDevice
Identifier TPPS/2 IBM TrackPoint
Driver evdev
Option Device
/dev/input/by-path/platform-i8042-serio-1-event-mouse
Option GrabDevice False
I've jumped up to kernel 3.5, still no luck
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994968
Title:
[Lenovo Thinkpad E220s] Touchpad/Trackpoint Does Not Respond To Input
For 5-10 Seconds
Public bug reported:
While ubuntu can seemingly detect when I plug-in a pair of headphones or
a microphone (or a combination unit in this specific case) and correctly
reroute the audio input and output to the newly added points, it does
not expose a per jack volume control.
The upshot is that I
** Description changed:
While ubuntu can seemingly detect when I plug-in a pair of headphones or
a microphone (or a combination unit in this specific case) and correctly
reroute the audio input and output to the newly added points, it does
not expose a per jack volume control.
The
notice the analog-output: Analog Output (priority 9900, available:
unknown) below, that is what displays when the headphones are plugged
in or not plugged in, so perhaps my jack sensing borked?
1 sink(s) available.
* index: 0
name: alsa_output.pci-_00_1b.0.analog-stereo
23 matches
Mail list logo
