Ted Gould <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-10-10 at 16:17 +, Marc Jauvin wrote:
>> Hi Matt, since I did this upgrade, keyboard and mouse don't work after
>> I rebooted... not sure if this is caused by your updated package (or
>> one of their dependency like xinput).
>
> This is likely
On Fri, 2008-10-10 at 16:17 +, Marc Jauvin wrote:
> Hi Matt, since I did this upgrade, keyboard and mouse don't work after
> I rebooted... not sure if this is caused by your updated package (or
> one of their dependency like xinput).
This is likely to be the same as this bug:
https://b
I have filed bug 281669 about the sticky num lock key (Bryce's issue #2
in
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/280646/comments/41)
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you a
Closing out the linux task; this is not a kernel bug.
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Bugs, which
I've confirmed the fix on my T61 with gnome-power-manager
2.24.0-0ubuntu4 in Intrepid.
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
On Fri, Oct 10, 2008 at 04:17:00PM -, Marc Jauvin wrote:
> Hi Matt, since I did this upgrade, keyboard and mouse don't work after
> I rebooted... not sure if this is caused by your updated package (or
> one of their dependency like xinput).
>
> I'm currently writing this from Hardy since m
Hi Matt, since I did this upgrade, keyboard and mouse don't work after
I rebooted... not sure if this is caused by your updated package (or
one of their dependency like xinput).
I'm currently writing this from Hardy since my Intrepid install is
unusable... ;)
Matt Zimmerman <[EMAIL PROTECTE
This bug was fixed in the package gnome-power-manager - 2.24.0-0ubuntu4
---
gnome-power-manager (2.24.0-0ubuntu4) intrepid; urgency=low
* src/gpm-button.c:gpm_button_grab_keystring: use AnyModifier modmask with
XGrabKey so that hotkeys being handled through gpm-button still work
** Changed in: gnome-power-manager (Ubuntu)
Target: None => ubuntu-8.10
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
There is a package in my PPA with this patch:
https://edge.launchpad.net/~mdz/+archive
deb http://ppa.launchpad.net/mdz/ubuntu intrepid main
deb-src http://ppa.launchpad.net/mdz/ubuntu intrepid main
I haven't been able to test it on the T61 yet, but would appreciate
regression testing nonetheles
On Fri, Oct 10, 2008 at 01:50:49AM -, Bryce Harrington wrote:
> 1. The problem with g-p-m not handling the brightness key when numlock
> is set is in fact an issue local to gnome-power-manager. It's simply
> neglects to grab the modifiers for the keys.
>
> The first line of the attached patc
** Attachment added: "debdiff using AnyModifier"
http://launchpadlibrarian.net/18390848/gnome-power-manager-280646.debdiff
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Matt Zimmerman (mdz)
Status: New => Triaged
--
ACPI
Brightness up/down works for me on Lenovo X60s with intrepid beta - OSD stops
working after NumLock.
Brightness changes are very slow (1 second).
Most Hotkeys work - still no OSD for the volume control keys ...
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/
With -verbose=4
** Attachment added: "xmond"
http://launchpadlibrarian.net/18383939/xmond
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1. The problem with g-p-m not handling the brightness key when numlock
is set is in fact an issue local to gnome-power-manager. It's simply
neglects to grab the modifiers for the keys.
The first line of the attached patch makes the issue go away (the rest
of the patch is just instrumentation).
In the first case, it printed a whole slew of output (including all the opcode
152 stuff), in the second cases it only printed a few lines (the opcode 95
stuff).
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification b
Here is output from xmond sitting between the X server and gnome-power-
manager. I did brightness-down, numlock, brightness-down.
** Attachment added: "xmond"
http://launchpadlibrarian.net/18383759/xmond
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bug
Weird, here's my xev output:
keycode 36 = (keysym 0xff0d, Return)
Brightness down:
keycode 8 =
keycode 8 =
keycode 8 =
keycode 8 =
keycode 8 =
keycode 8 =
(OCD displays)
Numlock:
keycode 77 = (keysym 0xff7f, Num_Lock)
keycode 77 = (keysym 0xff7f, Num_Lock)
Brightness down:
keycode 232 = (
-evdev sees the same output regardless of whether numlock is on or off:
Brightness key down:
(II) [bwh] Posting keyboard event code=232, value=1...
(II) [bwh] Posting keyboard event code=232, value=1...
(II) [bwh] Posting keyboard event code=232, value=0...
(II) [bwh] Posting keyboard event code=2
Backtrace from gnome-power-manager on gpm_button_filter_x_events with
numlock off:
#0 gpm_button_filter_x_events (xevent=0xbf9ce898, event=0x81774f8,
data=0x81ac5b8)
at gpm-button.c:79
#1 0xb7702679 in gdk_event_translate (display=0x8175000, event=0x81774f8,
xevent=0xbf9ce898, return_e
** Description changed:
Binary package hint: gnome-power-manager
+ Problem:
+ The state of the numlock key affects how the brightness switching keys work.
The OCD display does not display. On some systems (e.g. Thinkpad 61's), it
also prevents brightness from changing. This seems to be a
I've made a few packages/patches for debugging purposes:
http://bryceharrington.org/ubuntu/EvdevBug280646/
x11-xkb-utils-xkbwatch-dbg.patch - modifies xkbwatch to print
changes to stdout
*~instrumented* - Instruments -evdev to print out the keys
(code=) and the action value (0=
Fwiw, this is what I see in my /var/log/Xorg.0.log with the instrumented
package:
Tap num_lock:
(II) [bwh] Posting keyboard event code=77, value=1...
(II) [bwh] Posting keyboard event code=77, value=0...
Fn+ARROWUP (brightness up):
(II) [bwh] Posting keyboard event code=233, value=1...
(II) [bwh]
Bryce has reproduced the problem on a different laptop, where (although
his brightness is handled in hardware) when numlock is on, gnome-power-
manager doesn't receive the appropriate events, and the OSD doesn't
display
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchp
Andreas reports that, on 8.04 (where everything works correctly), he
sees events in hal:
[EMAIL PROTECTED]:~$ lshal -m
Start monitoring devicelist:
-
15:38:53.978: computer_logicaldev_input_2 condition ButtonPressed =
brightness-down
15:38:53.983:
I've noticed that gnome-settings-daemon seems to propagate the numlock
state from the gconf key to X via XkbLockModifiers. This explains why
toggling the gconf key changes the behaviour even though nothing is
actually looking at the gconf key.
--
ACPI brightness events no longer work on ThinkPad
Notably, I don't see anything in "lshal -m" when I press the brightness
keys, regardless of whether numlock_on=false (works) or numlock_on=true
(doesn't work)
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because
Since the num lock bug is old, I'm trying to work out why the brightness
keys don't work when that gconf key is set.
When numlock_on is false, gnome-power-manager sees KeyPress events for
the brightness keys in gpm_button_filter_x_events and responds.
When numlock_on is true, gpm_button_filter_x_
I rebooted into 2.6.24 and confirmed (via input-events) that I see a num
lock event on the first press and not on the second, so that issue is
older.
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are
Andreas Hasenack pointed out on IRC that, on Ubuntu 8.04, his brightness
keys do work (as I reported as well), but he is also able to reproduce
the num_lock misbehaviour. So it appears that the num lock / gconf
issue may be old, but that something new has caused the brightness keys
to stop working
This is what I see in xev when toggling then NumLock key on and then
off:
[Toggle ON]
KeyPress event, serial 33, synthetic NO, window 0x401,
root 0x7b, subw 0x0, time 67170208, (104,59), root:(175,141),
state 0x0, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
XLookupString
Further debugging on #ubuntu-devel has revealed that gnome-settings-
daemon listens for numlock keypresses (by listening for every key event)
and sets the gconf key.
I have also discovered that, snooping with xev, I see a KeyPress event
for num lock when the state is off (i.e. when turning num loc
I can reproduce the problem on the console, using "sudo input-events 1":
/dev/input/event1
bustype : BUS_I8042
vendor : 0x1
product : 0x1
version : 43860
name: "AT Translated Set 2 keyboard"
phys: "isa0060/serio0/input0"
bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP
I
Unsetting /desktop/gnome/peripherals/keyboard/remember_numlock_state
doesn't seem to help...
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Part of the problem appears to be that this gconf key gets set to true
when num lock is turned on, and then never set back to false when num
lock is turned off.
perseus:[~] gconftool-2 --get
/desktop/gnome/peripherals/keyboard/host-perseus/0/numlock_on
false
perseus:[~] # press num lock
perseus:[
Confirmed, deleting .gconf/desktop/gnome/peripherals/keyboard/host-
perseus/0/%gconf.xml and starting a new session got it working again.
Thanks for that data point.
Now to find out why that setting affects it...
** Description changed:
Binary package hint: gnome-power-manager
[regression
On Thu, Oct 09, 2008 at 04:30:48PM -, Marc Jauvin wrote:
> OK, but try deleting the file I mention in ~/.gconf along with
> ~/.gconfd/saved_state and do a logout/login. If you've got the same
> behavior as I do, this should restore your hotkeys (until you enable
Oh, thanks for clarifying
OK, but try deleting the file I mention in ~/.gconf along with
~/.gconfd/saved_state and do a logout/login. If you've got the same
behavior as I do, this should restore your hotkeys (until you enable
Numlock again).
Matt Zimmerman <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 09, 2008 at 12:28:
On Thu, Oct 09, 2008 at 12:28:02PM -, Marc Jauvin wrote:
> Please, see this bug report and check if you have the same behavior:
>
>https://bugs.launchpad.net/ubuntu/+bug/279766
That doesn't seem related; my num lock is off and turning it on doesn't
change my symptoms.
--
- mdz
--
ACP
Please, see this bug report and check if you have the same behavior:
https://bugs.launchpad.net/ubuntu/+bug/279766
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Bugs, which
Writing to acpi_video0/brightness does nothing, but writing to
acpi_video1 successfully changes the brightness. is this the interface
which hal should be using?
** Changed in: hal (Ubuntu)
Importance: Undecided => Medium
Status: New => Triaged
** Tags added: regression
--
ACPI bright
I can see
/sys/devices/virtual/backlight/acpi_video[01]/actual_brightness change
when I press the keys, just as /proc/acpi/video/VID/LCD0/brightness
does. However there doesn't seem to be anything in sysfs corresponding
to /proc/acpi/video/VID1/LCD0/brightness (the one which works).
Looking like
I can see the events being received by hald-addon-acpi (using strace),
but there's nothing in lshal -m
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Starting to look like a hal issue, moving there...
** Changed in: hal (Ubuntu)
Sourcepackagename: gnome-power-manager => hal
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Bugs,
The gpm brightness applet does work, so gpm's logic for setting the
brightness (and whatever it calls out to...xrandr?) is working.
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
perseus:[~] cat /proc/acpi/ibm/hotkey
status: enabled
mask: 0x008c7fff
commands: enable, disable, reset,
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
gnome-power-manager --verbose says that it is grabbing the right
keycodes:
TI:11:55:04 TH:0x650a00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
- Grabbed modmask=0, keycode=233
TI:11:55:04 TH:0x650a00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
- Grabbed modmask=0, keyco
I rebooted into 2.6.24 and the problem persists, so I don't think this
is strictly a kernel issue. Looking at g-p-m now.
** Changed in: gnome-power-manager (Ubuntu)
Sourcepackagename: linux => gnome-power-manager
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.ne
This looks relevant:
http://osdir.com/ml/linux.acpi.ibm-acpi.devel/2007-10/msg00102.html
Recent Lenovo ThinkPads define a dummy grahpics device, find it and
ignore it
Those laptops define one grahpics device on a PCI Express (e.g. Internal Intel
965 card) and one on a separate PCI bus (via a PCI
Aha...when I press the hotkeys, I can see the value in
/proc/acpi/VID/LCD0/brightness change (the one which does nothing). So
it's twiddling the wrong one (or there's an extra one when there
shouldn't be).
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/2
Writing values to /proc/acpi/VID1/LCD0/brightness works (though
VID/LCD0/brightness seems to do nothing...why are there two?)
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Bugs,
http://www.mail-archive.com/ibm-acpi-
[EMAIL PROTECTED]/msg00657.html
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Documentation/laptops/thinkpad-acpi.txt says:
0x1010 0x0FFN+HOME Brightness up. This key is
always handled by the firmware
in IBM ThinkPads, even when
unmasked. Just leave it alone.
Some external references:
http://www.justlinux.com/forum/showthread.php?p=883138
http://www.nabble.com/T61-Brightness-keys-with-2.6.26-not-working-(NVIDIA)-td18577619.html
--
ACPI brightness events no longer work on ThinkPad T61
https://bugs.launchpad.net/bugs/280646
You received this bug notifi
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/18362434/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/18362435/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/18362436/Dependencies.txt
** A
55 matches
Mail list logo
