X never sees brightness key release events on Dell laptops

[William Grant]

Binary package hint: gnome-power-manager

Pressing either of the brightness keys brings up the g-p-m brightness OSD. This has changed recently such that it now steals keyboard focus. It eventually disappears, leaving corruption on the screen, giving my caret back. However, I can't type again until I switch to another VT and back.

It also sometimes doesn't appear at all, or just appears with some uninitialized texture (but still steals focus).
--

This is caused by X invoking autorepeat on the brightness keys, as it never appears to see a release event.

--

This is caused by a bug in the kernel that requires a Dell specific quirk. It has been fixed in -proposed.

[Andrew Bennetts (spiv)]

Something similar is happening to me. I've filed bug 282963 about it. It's probably related, maybe even a duplicate?

[William Grant (wgrant)]

The keypress events are actually repeating; X appears to never receive a release event, so invokes autorepeat.

We believe it's a kernel bug, but I've no idea where to look.

[Dimitrios Symeonidis (azimout)]

i cannot confirm this. latest intrepid, intel 945gm graphics, 2.24.0-0ubuntu4 g-p-m, 2.6.27-7-generic kernel

[Joakim Andersson (jocke)]

I can confirm it on my Dell XPS M1330. The keys worked fine out of the box in Hardy but in Intrepid all my Fn+* keys are repeating.

The keyboard lockup problem only occurs for me when gnome-power-manager is running, and the problem can be removed by reverting the patch from bug 280646 (I.E. by changing "AnyModifier" to "0" on line 118 in gnome-power-manager's src/gpm-button.c).

[Mario Limonciello (superm1)]

The root of the problem though is that the kernel is not showing keyreleases for these keys. g-p-m might stack onto it with additional problems, but this root problem needs to be fixed first.

[Joakim Andersson (jocke)]

showkeys(1) run in console doesn't see Fn+* key releases either (not even when run with -s, as far as I can see).

[kreggz (jasonkregting)]

I can confirm this bug on a Dell M90

My bug report is a duplicate #285795

1. I installed Ubuntu Intrepid (8.10) on a Dell Precision M90
2. When Gnome starts up, off power, it will automatically change the brightness. When you move the mouse the brightness increases
3. If you manually change the brightness without moving the mouse, Gnome will stop being responsive and you can no longer use any menus or type anything.
4. I can reproduce this problem at any time by following the same steps
5. I am using the Nvidia 177 restricted driver

[Ben Trusty (ben-trusty)]

same problem on dell inspiron 1150
i have full range of brightness control
but the pop-up dialog only shows either no brightness or full brightness and does not update with brightness change

afterword the keyboard does not for any application (or gui), as well as clicking on 'applications / places / system' and most other items on the panels does not do anything.

[Joakim Andersson (jocke)]

I think I've found the solution for this problem (I've successfully fixed it on my laptop anyway).
Because of bug 207473 (or another one of the similar ones), I added "blacklist video" to a file in my /etc/modprobe.d/. I accidentally(?) removed it the other day and suddenly both showkey and X was getting Fn+* key release events (too many though, see bug 207473, but the same amount as the press events anyway).

When I add the blacklisting back, the problem reappears. I tried switching back and forth a few times, only changing the blacklisting between reboots, so this bug was (for me) _definitely_ caused by "blacklist video".

(I think kreggz problem is a totally different one, because my laptop doesn't care at all about the mouse regarding this problem. Also, he installed intrepid directly, while I upgraded from hardy, where the "blacklist video" fix was working just fine.)

[Joakim Andersson (jocke)]

An update to my last comment:

My brightness keys still work fine, and don't break X. However, my other Fn-keys (Suspend and battery state) are still broken (only triggers press events). Strange thing is, the battery state button definitely worked at least once when I wrote my last comment... I can't think of any reasonable cause for this re-breakage...

[David O'Callaghan (david-ocallaghan)]

I'd like to confirm of this bug with gnome-power-manager 2.24.0-0ubuntu8 on kernel 2.6.27-7 on a Dell XPS M1330. I've tested this in a guest account and both with and without "visual effects" (compiz). Killing gnome-power-manager makes the brightness controls work correctly but is not optimal.

Like Joakim Andersson above I had previously added "blacklist video" to /etc/modprobe.d/blacklist and removing this solves the immediate problem of losing keyboard focus (but removes a workaround for bug 207473).

[Graham Whelan (gawhelan)]

Same issue with a Zepto Znote 6625wd except it affects the volume up/down media keys. showkey is recognizing press and release events for the other media keys, but only press events for the volume keys. All keys worked fine with Hardy.

[Justin J Stark (justinjstark)]

I have a Dell 1535 and have this problem. Pressing FN+up or FN+down causes the screen to change brightness but just pressing once seems to cause the key to "stick" and the brightness continues to change after I let go. When I finally get the brightness dialog to go away, X is unresponsive. The menus highlight but will not open and I cannot type anything.

[insertnewsn (insertnewsn)]

Same issue with Dell E1705.

Fn+Up or Fn+Down increases/decreases brightness as necessary, but then makes X unresponsive. Currently the only problem I have with Intrepid Ibex!

[AaronMT (aaron-train)]

Confirming same issue with Inspiron 1501

Fn+UP or Fn+Down increase and decrease brightness but lock up X afterwards, well at the same time my volume also changes not sure why.

[Stephen Gibson (stevieg-livejournal)]

Confirming as well for Dell Latitude D610

Fn+Up/fn+Down will trigger the BIOS to change the brightness, but it locks up X to all keyboard input and some mouse events.

[Troy R. (dsm-iv-tr)]

Confirming on Dell Vostro 1000: Fn+up/down 'steals' keyboard input.

The "fix" for me was to use the magic SysRq key to reset the keyboard from a virtual terminal - alt+prtscr+r - I don't know if it's the VT switching or the magic keycombo that fixes it, but this is clearly an input layer bug.

$ apt-cache policy gnome-power-manager
gnome-power-manager:
  Installed: 2.24.0-0ubuntu8
  Candidate: 2.24.0-0ubuntu8
  Version table:
 *** 2.24.0-0ubuntu8 0
        500 http://ca.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

$ apt-cache policy linux-image
linux-image:
  Installed: (none)
  Candidate: 2.6.27.7.11
  Version table:
     2.6.27.7.11 0
        500 http://ca.archive.ubuntu.com intrepid/main Packages

[Renaud Muller (imagine2)]

I also have the same problem on a dell inspiron 640m. Do I have to download a file using apt get? (I was not sure to understand the message following yours). Happy anyway to see that the bug has been noticed and discussed.

[Troy R. (dsm-iv-tr)]

@Renaud Muller:
I apologize for the confusing comment. The apt-cache lines I pasted indicate the versions of the packages I was referring to.

[michote (michote)]

same problem as gawhelan on Zepto 6615WD
see also bug 291612

[Stephen Gibson (stevieg-livejournal)]

Following up on my comment: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/261721/comments/16

After upgrading my image to 2.6.27-7-generic I am no longer experiencing the lock-up issues. As I type at this moment I have gone through the whole brightness range (FnUp/Down) and am still able to type and use menus. I had to manually change my menu.lst to use 2.6.27-7 as the installer for 8.10 by default keeps the current GRUB configuration and I had not realized until I ran a uname -r and saw 2.6.24. Here's my output from apt-cache and uname -r.

apt-cache policy gnome-power-manager
gnome-power-manager:
Installed: 2.24.0-0ubuntu8
Candidate: 2.24.0-0ubuntu8
Version table:
 *** 2.24.0-0ubuntu8 0
500 http://us.archive.ubuntu.com intrepid/main Packages
100 /var/lib/dpkg/status

apt-cache policy linux-image
linux-image:
Installed: (none)
Candidate: 2.6.27.7.11
Version table:
2.6.27.7.11 0
500 http://us.archive.ubuntu.com intrepid/main Packages

uname -r
2.6.27-7-generic

I'm assuming that most people commenting to this bug have checked which image they are running, however, it's something that can be overlooked when freaking out about a finger-memory keystroke that render X useless.

[Andrew Bennetts (spiv)]

Stephen Gibson wrote:
> I'm assuming that most people commenting to this bug have checked which
> image they are running, however, it's something that can be overlooked
> when freaking out about a finger-memory keystroke that render X useless.

It is worth checking. :)

Just to confirm, I still see the problem, and my system is as up to date as
yours:

$ apt-cache policy linux-image
linux-image:
  Installed: (none)
  Candidate: 2.6.27.7.11
  Version table:
     2.6.27.7.11 0
        500 http://au.archive.ubuntu.com intrepid/main Packages

$ uname -r
2.6.27-7-generic

My system is a Dell Inspiron 630m.

[Paul (pmac-7)]

Confirming- same problem on my Dell Inspiron 600m. Just updated to Intrepid from Hardy.

[Toco (toco8804)]

Pretty sure i fixed the problem with my laptop. (i have a 2 year old e1505)

To make a long and relatively painful story short on how I fixed it for my laptop i'll just say i uninstalled laptop-power-tools and everything associated with it in synaptic and i havn't lost keyboard functionality yet.

Should probably include that i uninstalled gnome-power-manager first and that didn't work so i uninstalled laptop-power-tools and that fixed it. I reinstalled gnome-power-manager and it still works.

I really don't know if this will help me or if you guys want to try it because i basically just went in blind and just started uninstalling things without knowing what they do.

[Edmundo VN (edmundo-vn)]

For me it doesn't happens with the brightness key but when I change the volume, Im using a Toshiba U305, as already reported switching to a virtual terminal, pressing alt+prtscr+r and returning to X make the keyboard and right click work again. Its really anoying.

[Mario Limonciello (superm1)]

I think that you need to look a little closer at what's actually
happening for these "Release" events possibly. Try starting a Failsafe
Terminal at your login screen. If you run xev over there, you'll see
that a KeyRelease event is somehow generated, however it is *followed*
by the KeyPress event. The two being out of order may be confusing
gnome's keyboard handler and gnome power manager.

Edmundo Valle Neto wrote:
> For me it doesn't happens with the brightness key but when I change the
> volume, Im using a Toshiba U305, as already reported switching to a
> virtual terminal, pressing alt+prtscr+r and returning to X make the
> keyboard and right click work again. Its really anoying.
>
>

--
Mario Limonciello
*Dell | Linux Engineering*
<email address hidden>

[Graham Whelan (gawhelan)]

Mario Limonciello wrote:
> I think that you need to look a little closer at what's actually
> happening for these "Release" events possibly. Try starting a Failsafe
> Terminal at your login screen. If you run xev over there, you'll see
> that a KeyRelease event is somehow generated, however it is *followed*
> by the KeyPress event. The two being out of order may be confusing
> gnome's keyboard handler and gnome power manager.

I can confirm this. Running xev from a failsafe terminal shows a KeyRelease event being generated before the KeyPress. Both are generated when the key is pressed down and no event is generated when the key is physically released.

$ xev

...

MotionNotify event, serial 23, synthetic NO, window 0x400001,
    root 0x13b, subw 0x0, time 1128533, (120,116), root:(122,118),
    state 0x0, is_hint 0, same_screen YES

KeyRelease event, serial 23, synthetic NO, window 0x400001,
    root 0x13b, subw 0x0, time 1129930, (120,116), root:(122,118),
    state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 23, synthetic NO, window 0x400001,
    root 0x13b, subw 0x0, time 1129930, (120,116), root:(122,118),
    state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

MotionNotify event, serial 26, synthetic NO, window 0x400001,
    root 0x13b, subw 0x0, time 1132703, (136,128), root:(138,130),
    state 0x0, is_hint 0, same_screen YES

...

[Michal Dubiel (majkijin-deactivatedaccount)]

I have the same problem on my Dell Inspiron 6000 as stated in bug description but I don't lose only a keyboard focus but also a part of the mouse functionality. For example I can't move windows, maximize or minimize it. Also I can't use my menu bar - clicking on Places or Applications do not unroll a menu. Everything back to work after switching to other VT and back.

[Tim Gardner (timg-tpi)]

I think this bug is related to #284066. Once that kernel version is in -proposed, please mark this report as a duplicate (if it is indeed the correct fix).

[Brenden Bain (brendenbain)]

Works for me after the upgrade to 2.6.27-8 in -proposed.

While the backlight setting seems to work, the dialog that used to come up in 8.04 showing the adjustment is no longer showing at all in 8.10.

[Michal Dubiel (majkijin-deactivatedaccount)]

Exactly the same on my system. Backlight setting works after upgrade to 2.6.27-8, but the dialogue doesn't show since 8.10.

[Dimitrios Symeonidis (azimout)]

can everyone who reported this problem please upgrade to 2.6.27-8 (from the -proposed repository) and confirm that the issue is fixed for them?

thank you

[kreggz (jasonkregting)]

I can confirm this has fixed the problem.

This is great!!! Thanks everyone!

[Essence (bryanmcconkey)]

This bug seems similar (identical?) to this one
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/294791

[stryderjzw (stryderjzw-gmail)]

Upgrading to 2.6.27-8 (in proposed) has fixed the problem for me! thanks.

[Ben Trusty (ben-trusty)]

"can everyone who reported this problem please upgrade to 2.6.27-8 (from the -proposed repository)"

it does NOT work for me
there is no change in the results from using fn+up/down for brightness up/down

the pop-up shows, though the horizontal meter does not move the brightness does adjust
this STILL does cause the keyboard and responsive failure.
no menus, no moving windows with mouse.

suggestions?

[mbeach (mbeaches)]

upgrading to 2.6.27-8 today has fixed this issue for me on a Dell Studio 1735. Fn+Up/Down works as expected.

[Cory (cory-northwinddesign)]

I can confirm that upgrading to 2.6.27-8 fixed the brightness issue.

[Essence (bryanmcconkey)]

I have upgraded to 2.6.27-8 and the steps I used to take to reproduce this problem no longer work, so far it seems fixed from that change. (Dell Inspiron 6400)

[Edmundo VN (edmundo-vn)]

For me it didn't worked, but my problem is a little different (the same problem with the function key that controls the volume), any suggestion?

[Graham Whelan (gawhelan)]

No change for me with the 2.6.27-8 kernel. Volume keys still don't work on a Zepto 6625wd.

[Kostas Chatzikokolakis (kostas-chatzi)]

On an xps 1330, I had previously solved the problem by removing "blacklist video" from /etc/modprobe.d/blacklist (as suggested by a previous comment).

After upgrading to 2.6.27-8, the problem does not appear, even when I put back "blacklist video".

[Justin J Stark (justinjstark)]

I have a Dell 1535 Studio and 2.6.27-8 fixes the problem for me. I get the brightness dialog that pops up when I push the buttons and everything works like it should.

[Dimitrios Symeonidis (azimout)]

according to several user reports, this issue was fixed in kernel 2.6.27-8. marking as such. thanks go out to everyone for helping triage and confirm the fix of this bug.

[Mario Limonciello (superm1)]

That kernel is still in proposed. Don't mark it fix released until it's in updates.

[Graham Whelan (gawhelan)]

Dimitrios Symeonidis wrote:
> according to several user reports, this issue was fixed in kernel 2.6.27-8.
> marking as such. thanks go out to everyone for helping triage and confirm
> the fix of this bug.

The 2.6.27-8 kernel hasn't fixed this issue for everyone.

Edmundo Valle Neto wrote:
> For me it didn't worked, but my problem is a little different (the same problem
> with the function key that controls the volume), any suggestion?

gawhelan wrote:
> No change for me with the 2.6.27-8 kernel. Volume keys still don't work on a
> Zepto 6625wd.

I realize that our problem is slightly different than the original bug report as it involves the volume rather than the brightness keys. But https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/291612 is marked as a duplicate of this bug and it involves volume keys on a zepto .

If this bug is to be marked fixed then #291612 should be removed as a duplicate and left open as I don't believe the 2.6.27-8 kernel contains a fix.

[Dimitrios Symeonidis (azimout)]

ok, gawhelan, #291612 has been removed from the duplicate list
please follow that report

[Michal Dubiel (majkijin-deactivatedaccount)]

Dimitrios Symeonidis: "according to several user reports, this issue was fixed in kernel 2.6.27-8. marking as such. thanks go out to everyone for helping triage and confirm the fix of this bug."

According to several user reports, kernel 2.6.27-8 fixes only a part of the problem. For instance on my system, keyboard is not locked after changing brightness but the dialogue still doesn't appear.
Is it good to mark issue fixed when it is fully fixed only for several users? Shouldn't we mark it after it is fully fixed for every user?

[gurrett86 (gurrett86)]

The kernel update seems to fix the keyboard not working. The pop-up dialog still only shows either no brightness or full brightness and does not update with changes.

[Essence (bryanmcconkey)]

Although updating to 2.6.27-8 did fix my main problem of loosing the keyboard when adjusting brightness, I do no longer have the pop up indicating brightness levels. If I anyone needs some more information, I will gladly provide whatever I can

[Dimitrios Symeonidis (azimout)]

edmundo, essence, gurrett86 and majkijin, can you post the output of your lspci -nn? we should find out what is different on your systems from all the other people above, for whom 2.6.27-8 fully fixed the problem.

[Michal Dubiel (majkijin-deactivatedaccount)]

On Dimitrios Symeonidis's request. My lspci -nn output:

00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
00:01.0 PCI bridge [0604]: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port [8086:2591] (rev 03)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 03)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 03)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 03)
00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 03)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 03)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev d3)
00:1e.2 Multimedia audio controller [0401]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller [8086:266e] (rev 03)
00:1e.3 Modem [0703]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller [8086:266d] (rev 03)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge [8086:2641] (rev 03)
00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) SATA Controller [8086:2653] (rev 03)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M22 [Mobility Radeon X300] [1002:5460]
03:00.0 Ethernet controller [0200]: Broadcom Corporation BCM4401-B0 100Base-TX [14e4:170c] (rev 02)
03:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b3)
03:01.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] (rev 08)
03:01.2 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 17)
03:03.0 Network controller [0280]: Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection [8086:4223] (rev 05)

[gurrett86 (gurrett86)]

00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 03)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 03)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 03)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 03)
00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 03)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 03)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev d3)
00:1e.2 Multimedia audio controller [0401]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller [8086:266e] (rev 03)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge [8086:2641] (rev 03)
00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) SATA Controller [8086:2653] (rev 03)
03:00.0 Ethernet controller [0200]: Broadcom Corporation BCM4401-B0 100Base-TX [14e4:170c] (rev 02)
03:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b3)
03:01.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] (rev 08)
03:01.2 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 17)
03:03.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05)

[Oxid (oxid22)]

For me, the kernel update don`t fix this bug, too. On a Sony Vaio VGN-FS215 with Intel 915 graphics.
My lspci -nn output:

00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 03)
00:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 03)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 03)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 03)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 03)
00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 03)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 03)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev d3)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge [8086:2641] (rev 03)
00:1f.1 IDE interface [0101]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller [8086:266f] (rev 03)
00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller [8086:266a] (rev 03)
06:03.0 CardBus bridge [0607]: Texas Instruments PCI7420 CardBus Controller [104c:ac8e]
06:03.2 FireWire (IEEE 1394) [0c00]: Texas Instruments PCI7x20 1394a-2000 OHCI Two-Port PHY/Link-Layer Controller [104c:802e]
06:03.3 Mass storage controller [0180]: Texas Instruments PCI7420/7620 Combo CardBus, 1394a-2000 OHCI and SD/MS-Pro Controller [104c:ac8f]
06:04.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG Network Connection [8086:4220] (rev 05)
06:08.0 Ethernet controller [0200]: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller Mobile [8086:1068] (rev 03)

[Edmundo VN (edmundo-vn)]

Follows the output of lspci -nn on my Toshiba Satellite U305-S2804:

edmundo@toshibau305:~$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 03)
00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03)
00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 03)
00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 03)
00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 03)
00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 03)
00:1c.2 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 [8086:2843] (rev 03)
00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 [8086:2845] (rev 03)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 03)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 [8086:2831] (rev 03)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 [8086:2832] (rev 03)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 [8086:2836] (rev 03)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f3)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller [8086:2815] (rev 03)
00:1f.1 IDE interface [0101]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller [8086:2850] (rev 03)
00:1f.2 SATA controller [0106]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller [8086:2829] (rev 03)
00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family) SMBus Controller [8086:283e] (rev 03)
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 01)
04:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] (rev 02)
0a:01.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 05)
0a:01.1 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 22)
0a:01.2 System peripheral [0880]: Ricoh Co Ltd R5C843 MMC Host Controller [1180:0843] (rev 12)
0a:01.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 12)
0a:01.4 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev ff)

[Ben Trusty (ben-trusty)]

dell inspiron 1150 / pentium 4 2.8ghz mobile / intel 855 mobile chipset

00:00.0 Host bridge [0600]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3580] (rev 02)
00:00.1 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3584] (rev 02)
00:00.3 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3585] (rev 02)
00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02)
00:02.1 Display controller [0380]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 81)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge [8086:24cc] (rev 01)
00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE Controller [8086:24ca] (rev 01)
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 01)
02:01.0 Ethernet controller [0200]: Broadcom Corporation BCM4401 100Base-T [14e4:4401] (rev 01)
02:02.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)
02:04.0 CardBus bridge [0607]: Texas Instruments PCI1510 PC card Cardbus Controller [104c:ac56]

[Essence (bryanmcconkey)]

Dell Inspiron 6400

00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
00:01.0 PCI bridge [0604]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port [8086:27a1] (rev 03)
00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 01)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [8086:27d0] (rev 01)
00:1c.3 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 [8086:27d6] (rev 01)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 [8086:27c8] (rev 01)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 [8086:27c9] (rev 01)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 [8086:27ca] (rev 01)
00:1d.3 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 [8086:27cb] (rev 01)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller [8086:27cc] (rev 01)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 01)
00:1f.2 IDE interface [0101]: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller [8086:27c4] (rev 01)
00:1f.3 SMBus [0c05]: Intel Corporation 82801G (ICH7 Family) SMBus Controller [8086:27da] (rev 01)
01:00.0 VGA compatible controller [0300]: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] [10de:01d7] (rev a1)
03:00.0 Ethernet controller [0200]: Broadcom Corporation BCM4401-B0 100Base-TX [14e4:170c] (rev 02)
03:01.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832]
03:01.1 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 19)
03:01.2 System peripheral [0880]: Ricoh Co Ltd R5C843 MMC Host Controller [1180:0843] (rev 0a)
03:01.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 05)
03:01.4 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev ff)
0b:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] (rev 02)

[Marius Kjeldahl (marius-kjeldahl)]

I've got a Dell 6400 hundred as well, and just want to add that in my case when the keyboard stops working, no switching to VT and back gets the keyboard working again in X/Kwin (I'm using Kubuntu 8.10). Mouse works fine, but keyboard just stops working. It works on the VTs, but not in X.

[Jaroslav Šmíd (jardasmid-gmail)]

I had the same problem on Dell Studio 1535. Upgrading to 2.6.27-8 from proposed solved it.

[Cory (cory-northwinddesign)]

I previously thought the upgrade to 2.6.27-8 solved the problem, but I just had my keyboard disabled again when trying to change brightness. I've attached my lspci -nn output.

[Andy Whitcroft (apw)]

On Fri, Nov 28, 2008 at 04:47:03PM -0000, Cory wrote:
> I previously thought the upgrade to 2.6.27-8 solved the problem, but I
> just had my keyboard disabled again when trying to change brightness.
> I've attached my lspci -nn output.

Could you try the 2.6.27-10.20 release currently in -proposed.
This has some specific fixes for brightness control. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!

[Ben Trusty (ben-trusty)]

i still have the problem with this
Linux rook 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686
GNU/Linux

so i am using the purposed via synaptic
it is nice that i know i can just hit ctrl+alt+f2 to fix it (rather than
having to reboot, like i used to. but it seems that this is a major problem
that needs to be fixed for most laptop systems.

On Fri, Nov 28, 2008 at 1:17 PM, Andy Whitcroft <email address hidden> wrote:

> On Fri, Nov 28, 2008 at 04:47:03PM -0000, Cory wrote:
> > I previously thought the upgrade to 2.6.27-8 solved the problem, but I
> > just had my keyboard disabled again when trying to change brightness.
> > I've attached my lspci -nn output.
>
> Could you try the 2.6.27-10.20 release currently in -proposed.
> This has some specific fixes for brightness control. Please see
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed. Thank you in advance!
>
> --
> X never sees brightness key release events
> https://bugs.launchpad.net/bugs/261721
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: Fix Committed
> Status in "xorg-server" source package in Ubuntu: Invalid
>
> Bug description:
> Binary package hint: gnome-power-manager
>
> Pressing either of the brightness keys brings up the g-p-m brightness OSD.
> This has changed recently such that it now steals keyboard focus. It
> eventually disappears, leaving corruption on the screen, giving my caret
> back. However, I can't type again until I switch to another VT and back.
>
> It also sometimes doesn't appear at all, or just appears with some
> uninitialized texture (but still steals focus).
> --
>
> This is caused by X invoking autorepeat on the brightness keys, as it never
> appears to see a release event.
>

[Kostas Chatzikokolakis (kostas-chatzi)]

Testing the new kernels on a Dell XPS 1330:
- linux-image-2.6.27-9 in -updates still has the problem
- linux-image-2.6.27-10 in -proposed does NOT have the problem (like 2.6.27-8, also in proposed)

[Essence (bryanmcconkey)]

The updating of the linux-image to the one from proposed fixed the main issue, however it took away the on screen brightness indication for many.

[Mario Limonciello (superm1)]

Hi Essence:

Can you open another bug on that issue against the gnome-power-manager package, and subscribe dell-team to it? I'm aware of the issue myself, but it would be good to track it while the gnome power manager maintainers triage it.

-----Original Message-----
From: <email address hidden> on behalf of Essence
Sent: Mon 12/1/2008 8:07 AM
To: <email address hidden>
Subject: [Bug 261721] Re: X never sees brightness key release events

The updating of the linux-image to the one from proposed fixed the main
issue, however it took away the on screen brightness indication for
many.

--
X never sees brightness key release events
https://bugs.launchpad.net/bugs/261721
You received this bug notification because you are a member of The Dell
Team, which is a direct subscriber.

[Essence (bryanmcconkey)]

I was about to do as you asked and open a new bug for the updated linux-image breaking the brightness indicator for some of us dell users, but it appears that the last update i received has fixed this problem!

So for reference I am running a Dell Inspirion 6400
gnome-power-manager 2.24.0-0ubuntu8.1
linux-image-2.6.27-10.20

Hopefully the other's users problems are fixed as well.

[Mario Limonciello (superm1)]

Hi Essence:

Please add this comment to bug 304187 which is tracking the behavior of the popup indicator. You are using the testing version (2.24.0-0ubuntu8.1) which should be the cause of this resolution.

[Kostas Chatzikokolakis (kostas-chatzi)]

I confirm that gnome-power-manager 2.24.0-0ubuntu8.1 from -proposed fixes the brightness indicator on a Dell xps 1330. Good job guys :)

[Jakub Skopal (kubacz)]

I have a Dell 1535 Studio and 2.6.27-9 has the same problem. Going up to 2.6.27-10 fixes the issue. gr8 job!!

[Stan Couix (s-couix)]

Hi everybody,

Recent update fix the issue of the brightness indicator (it moves now!) but the indicator is still here, I can't click on menus, etc. (fortunately switching VT workaround still works)

I have a Dell inspiron 510m with an intel 825/855 GM graphic card.

Ubuntu interpid ibex

uname -a :
Linux stan-laptop 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

gnome-power-management : 2.24.0-0ubuntu8.1

[Ben Trusty (ben-trusty)]

I concur, the slider now actually updates, but I still have to ctrl + alt +
f2 to fix keyboard problem (cant click on menus, cant type, etc)

dell inspiron 1150, 852/855gm

On Sun, Dec 28, 2008 at 5:09 AM, Stan Couix <email address hidden> wrote:

> Hi everybody,
>
> Recent update fix the issue of the brightness indicator (it moves now!)
> but the indicator is still here, I can't click on menus, etc.
> (fortunately switching VT workaround still works)
>
> I have a Dell inspiron 510m with an intel 825/855 GM graphic card.
>
> Ubuntu interpid ibex
>
> uname -a :
> Linux stan-laptop 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686
> GNU/Linux
>
> gnome-power-management : 2.24.0-0ubuntu8.1
>
> --
> X never sees brightness key release events
> https://bugs.launchpad.net/bugs/261721
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: Fix Committed
> Status in "xorg-server" source package in Ubuntu: Invalid
>
> Bug description:
> Binary package hint: gnome-power-manager
>
> Pressing either of the brightness keys brings up the g-p-m brightness OSD.
> This has changed recently such that it now steals keyboard focus. It
> eventually disappears, leaving corruption on the screen, giving my caret
> back. However, I can't type again until I switch to another VT and back.
>
> It also sometimes doesn't appear at all, or just appears with some
> uninitialized texture (but still steals focus).
> --
>
> This is caused by X invoking autorepeat on the brightness keys, as it never
> appears to see a release event.
>

[Andy Whitcroft (apw)]

On Sun, Dec 28, 2008 at 10:09:13AM -0000, Stan Couix wrote:
> Hi everybody,
>
> Recent update fix the issue of the brightness indicator (it moves now!)
> but the indicator is still here, I can't click on menus, etc.
> (fortunately switching VT workaround still works)
>
> I have a Dell inspiron 510m with an intel 825/855 GM graphic card.

Could you test the -11 kernel from -proposed for us and report back here.
Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation
how to enable and use -proposed.

[Patrick Kilgore (patrick-kilgore)]

I can confirm -11 fixes the problem for me. Good job guys!

[Stan Couix (s-couix)]

The problem is fixed now ! thank you guys !

[Mario Limonciello (superm1)]

The fix is in the *kernel* package. You need the kernel package from
-proposed until it gets released to -updates.

Ben Trusty wrote:
>
> I concur, the slider now actually updates, but I still have to ctrl +
> alt +
> f2 to fix keyboard problem (cant click on menus, cant type, etc)
>
> dell inspiron 1150, 852/855gm
>
> On Sun, Dec 28, 2008 at 5:09 AM, Stan Couix <email address hidden> wrote:
>
> > Hi everybody,
> >
> > Recent update fix the issue of the brightness indicator (it moves now!)
> > but the indicator is still here, I can't click on menus, etc.
> > (fortunately switching VT workaround still works)
> >
> > I have a Dell inspiron 510m with an intel 825/855 GM graphic card.
> >
> > Ubuntu interpid ibex
> >
> > uname -a :
> > Linux stan-laptop 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC
> 2008 i686
> > GNU/Linux
> >
> > gnome-power-management : 2.24.0-0ubuntu8.1
> >
> > --
> > X never sees brightness key release events
> > https://bugs.launchpad.net/bugs/261721
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in "linux" source package in Ubuntu: Fix Committed
> > Status in "xorg-server" source package in Ubuntu: Invalid
> >
> > Bug description:
> > Binary package hint: gnome-power-manager
> >
> > Pressing either of the brightness keys brings up the g-p-m
> brightness OSD.
> > This has changed recently such that it now steals keyboard focus. It
> > eventually disappears, leaving corruption on the screen, giving my caret
> > back. However, I can't type again until I switch to another VT and back.
> >
> > It also sometimes doesn't appear at all, or just appears with some
> > uninitialized texture (but still steals focus).
> > --
> >
> > This is caused by X invoking autorepeat on the brightness keys, as
> it never
> > appears to see a release event.
> >
>
> --
> X never sees brightness key release events
> https://bugs.launchpad.net/bugs/261721
> You received this bug notification because you are a member of The Dell
> Team, which is a direct subscriber.
>

--
Mario Limonciello
*Dell | Linux Engineering*
<email address hidden>

[Kashi Gorton (flash87)]

Is this a duplicate of bug 285323? William, are you on a Dell laptop of some description?

[klerfayt (klerfayt-deactivatedaccount)]

I would argue that bug #271706 should be marked duplicate of this because symptoms are identical and the cause same:

https://bugs.launchpad.net/ubuntu/+bug/278781/comments/7

"...issue is that on certain systems' PS/2 keyboards, the volume control keys (and certain media keys) report a KEY_DOWN when they're pressed, but not a KEY_UP when they're released..."

only difference are non-Dell laptops (Compaq, HP, Toshiba among others) and Fn volume keys

[Mario Limonciello (superm1)]

The exact fix used in this bug is pertinent *only* to Dell laptops. That bug refers to other brands, and henceforth is not a duplicate.

[klerfayt (klerfayt-deactivatedaccount)]

However the fix used to get around "most Fn keys on Dell laptops do not generate release event" would be similar if not exactly same for other brands of laptops:
"generate release events ourselves"

[Mario Limonciello (superm1)]

No, this fix is a dmidecode fix that matches on Dell strings. Something different will be needed for that bug, probably similar to this:

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=blobdiff;f=drivers/input/keyboard/atkbd.c;h=1aa2eaf59458ed1d4fc619f2ea575e1e170b3ac7;hp=c694eaae79869e364055c732dbdef44476c9a912;hb=aa085ec46c542ebcb952c41409a23ceb72d92664;hpb=0feccfbc02792f9555bd77aa611b863f82974214

It will have to match on the particular brands and models found in different bugs, which is why these should be treated as separate bugs.

[Andy Whitcroft (apw)]

On Mon, Jan 19, 2009 at 05:32:01PM -0000, klerfayt wrote:
> However the fix used to get around "most Fn keys on Dell laptops do not generate release event" would be similar if not exactly same for other brands of laptops:
> "generate release events ourselves"

Generally quirk based fixes such as these are very specific to the machine
that they apply to, they change specific keys with specific numbers.
We therefore try and maintain that single machine focus for each bug.
If the bug is not focused very tightly then the general bug would never
get completed and that would make it hard for any one laptop owner to
know if their laptop was supposed to be fixed or not.

[Kashi Gorton (flash87)]

So what's the status of this bug? I understand that a previous kernel release fixed the bug for the vendor id = "Dell Inc." case, but the vendor id = "Dell Computer Cooperation" case has not (yet?) made it into proposed: verified on my Inspiron 1100, the latest proposed does not fix the bug.

[Kashi Gorton (flash87)]

this guy https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285323/comments/88 states it clearly,

my output for sudo dmidecode | grep Vendor:
Vendor: Dell Computer Corporation
(sorry... misspelling in last comment)

So extending the fix has been suggested a few times:
http://marc.info/?l=linux-kernel&m=122650907006352&w=2
http://marc.info/?l=linux-kernel&m=123055061901679&w=2
http://marc.info/?l=linux-kernel&m=123056100215208&w=2

so it's queued for .29, when is this going to appear in -proposed?

[Rafac24 (cabanas86)]

Dell Inspiron B130

I upgraded to kernel 27-11 using the -proposed (all 'generic') and it did fix the issue with the Fn/Brightness.
But, it created another issue in that all networking capabilities were lost. It would not register my Wireless card and I tried plugging into eth0 and it wouldnt register that either.

I had to revert back to kernel 27-9 on startup.

I've only had Ubuntu for a month now. Should i have updated other files besides 'generic' ones?

Thanks.

[Robert (robrwo)]

I'm having a similar problem with a Lenovo ThinkPad R61i.

[Mario Limonciello (superm1)]

This bug has been fixed by intrepid-updates. If you continue to have problems with a non Dell laptop, please open a NEW bug.

[Kashi Gorton (flash87)]

The problem has only been partially fixed by released updates, as I said in my previous post the bug has been fixed for the vendor string "Dell Inc." but not for "Dell Computer Corporation". This is exactly the same bug, it's just older Dells with the same bug have a different vendor ID for some reason. The latest kernell (2.6.27-11.27) does not fix the issue on my Inspiron 1100.

[Alexander Lampret (alamp4kf)]

I have this bug too, on my "FUJITSU SIEMENS PA1510" !!! Not a Dell Laptop

[Kashi Gorton (flash87)]

If it isn't a Dell laptop, it isn't the same bug, file a new bug report. If it's exactly the same cause, i.e. brightness function keys reporting a down but not an up, then the solution will be similar but laptop vendor, possibly even laptop model, specific. This bug is treating Dell laptops with this issue. If yours is not a Dell laptop, then file a separate bug report.

https://help.ubuntu.com/community/ReportingBugs

[Connor Imes (ckimes)]

Agreed, this is not fixed for Vendor string "Dell Computer Corporation" in Intrepid kernel 2.6.27-11.27-generic, or in Jaunty on the latest kernel 2.6.28-6.16-generic. My laptop is a Dell 600m, I have a duplicate bug filed.

Setting back to Triaged, but if more information is still needed, please ask and we shall provide. Thank you.

[Jordan Armstrong (jordan-armstrong)]

The fix for this is to update 'drivers/input/keyboard/atkbd.c' to widen the Dell DMI signatures:

The fix for this is commit 2a3ec3265741c3b2a7ebbd1b33f538e5a5583c48 in Linus' tree:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2a3ec3265741c3b2a7ebbd1b33f538e5a5583c48

[Tim Gardner (timg-tpi)]

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-jaunty.git;a=commit;h=bf9b51b29cab40295dfc5d79289bd389f24b7b06

[Ben Trusty (ben-trusty)]

most recent ubuntu 8.10 proposed update (last night)
2.6.27-11-generic

still broken

On Sat, Jan 31, 2009 at 2:37 PM, Tim Gardner <email address hidden>wrote:

> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
> jaunty.git;a=commit;h=bf9b51b29cab40295dfc5d79289bd389f24b7b06
>
> ** Changed in: linux (Ubuntu Jaunty)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Tim Gardner (timg-tpi)
> Status: Invalid => Fix Committed
> Target: None => jaunty-alpha-5
>
> ** Changed in: linux (Ubuntu Intrepid)
> Assignee: Tim Gardner (timg-tpi) => Stefan Bader
> (stefan-bader-canonical)
>
> --
> X never sees brightness key release events on Dell laptops
> https://bugs.launchpad.net/bugs/261721
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "acpid" source package in Ubuntu: Invalid
> Status in "linux" source package in Ubuntu: Fix Committed
> Status in "xorg-server" source package in Ubuntu: Invalid
> Status in acpid in Ubuntu Intrepid: Invalid
> Status in linux in Ubuntu Intrepid: Triaged
> Status in xorg-server in Ubuntu Intrepid: Invalid
> Status in acpid in Ubuntu Jaunty: Invalid
> Status in linux in Ubuntu Jaunty: Fix Committed
> Status in xorg-server in Ubuntu Jaunty: Invalid
>
> Bug description:
> Binary package hint: gnome-power-manager
>
> Pressing either of the brightness keys brings up the g-p-m brightness OSD.
> This has changed recently such that it now steals keyboard focus. It
> eventually disappears, leaving corruption on the screen, giving my caret
> back. However, I can't type again until I switch to another VT and back.
>
> It also sometimes doesn't appear at all, or just appears with some
> uninitialized texture (but still steals focus).
> --
>
> This is caused by X invoking autorepeat on the brightness keys, as it never
> appears to see a release event.
>
> --
>
> This is caused by a bug in the kernel that requires a Dell specific quirk.
> It has been fixed in -proposed.
>

[Nicklas W Bjurman (lordmetroid)]

On my Dell Inspiron 5100 laptop(bought 5 years ago), brightness keys and any other function kets works fine.

[Nicklas W Bjurman (lordmetroid)]

DOH, Forgot to tell you that I am rinning Ubuntu 8.10 2.6.27-9-generic i686

[nanotube (nanotube)]

Problem still persists with the latest intrepid kernel update (2.6.27-11-generic) here on Dell Inspiron 5150.

dmidecode says manufacturer is "Dell Computer Corporation"

[Andy Whitcroft (apw)]

On Sun, Feb 01, 2009 at 02:41:13PM -0000, nanotube wrote:
> Problem still persists with the latest intrepid kernel update
> (2.6.27-11-generic) here on Dell Inspiron 5150.
>
> dmidecode says manufacturer is "Dell Computer Corporation"

The fix as committed will be in the next Jaunty kernel, it is not yet
released so that is probabally expected.

[Nicklas W Bjurman (lordmetroid)]

I actually never had any problem with brightness and sound keys on Ubuntu, other distributions I have had problems oddly enough including Debian.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 2.6.28-7.18

---------------
linux (2.6.28-7.18) jaunty; urgency=low

  [ Alok Kataria ]

  * SAUCE: (drop after 2.6.29) x86: add a synthetic TSC_RELIABLE feature
    bit
    - LP: #319945
  * SAUCE: (drop after 2.6.29) x86: add X86_FEATURE_HYPERVISOR feature bit
    - LP: #319945
  * SAUCE: (drop after 2.6.29) x86: Hypervisor detection and get tsc_freq
    from hypervisor
    - LP: #319945
  * SAUCE: (drop after 2.6.29) x86: Add a synthetic TSC_RELIABLE feature
    bit.
    - LP: #319945
  * SAUCE: (drop after 2.6.29) x86: Skip verification by the watchdog for
    TSC clocksource.
    - LP: #319945
  * SAUCE: (drop after 2.6.29) x86: VMware: Fix vmware_get_tsc code
    - LP: #319945
  * SAUCE: (drop after 2.6.29) x86: vmware: look for DMI string in the
    product serial key
    - LP: #319945

  [ Andy Whitcroft ]

  * SAUCE: toshiba_acpi -- pull in current -dev version of driver
    - LP: #269831
  * SAUCE: toshiba_acpi -- add acpi hotkey kernel thread
    - LP: #269831
  * move toshiba laptops back from tlsup to toshiba_acpi
    - LP: #269831

  [ Aneesh Kumar K.V ]

  * SAUCE: (revert before 2.6.28.y update) ext4: Fix the delalloc
    writepages to allocate blocks at the right offset.
  * SAUCE: (revert before 2.6.28.y update) ext4: avoid ext4_error when
    mounting a fs with a single bg
  * SAUCE: (revert before 2.6.28.y update) ext4: Don't overwrite
    allocation_context ac_status
  * SAUCE: (revert before 2.6.28.y update) ext4: Add blocks added during
    resize to bitmap
  * SAUCE: (revert before 2.6.28.y update) ext4: Use
    EXT4_GROUP_INFO_NEED_INIT_BIT during resize
  * SAUCE: (revert before 2.6.28.y update) ext4: cleanup mballoc header
    files
  * SAUCE: (revert before 2.6.28.y update) ext4: don't use blocks freed but
    not yet committed in buddy cache init
  * SAUCE: (revert before 2.6.28.y update) ext4: Fix race between
    read_block_bitmap() and mark_diskspace_used()
  * SAUCE: (revert before 2.6.28.y update) ext4: Fix the race between
    read_inode_bitmap() and ext4_new_inode()
  * SAUCE: (revert before 2.6.28.y update) ext4: Use new buffer_head flag
    to check uninit group bitmaps initialization
  * SAUCE: (revert before 2.6.28.y update) ext4: mark the blocks/inode
    bitmap beyond end of group as used
  * SAUCE: (revert before 2.6.28.y update) ext4: Don't allow new groups to
    be added during block allocation
  * SAUCE: (revert before 2.6.28.y update) ext4: Init the complete page
    while building buddy cache
  * SAUCE: (revert before 2.6.28.y update) ext4: Fix s_dirty_blocks_counter
    if block allocation failed with nodelalloc

  [ Hannes Eder ]

  * SAUCE: (drop after 2.6.29) x86: vmware - fix sparse warnings
    - LP: #319945

  [ Luke Yelavich ]

  * hid modules have hyphens instead of underscores in their names

  [ Mark Fasheh ]

  * SAUCE: (revert before 2.6.28.y update) jbd2: Add BH_JBDPrivateStart

  [ Theodore Ts'o ]

  * SAUCE: (revert before 2.6.28.y update) ext4: Add support for non-native
    signed/unsigned htree hash algorithms
  * SAUCE: (revert before 2.6.28.y update) ext4: tone down
    ext4_da_writepages warnings
  * SAUCE: (revert before 2.6.28.y...

[nanotube (nanotube)]

will this latest kernel be released for intrepid? or is it jaunty-only?

[Andy Whitcroft (apw)]

On Thu, Feb 05, 2009 at 05:18:43PM -0000, nanotube wrote:
> will this latest kernel be released for intrepid? or is it jaunty-only?

This is a Jaunty kernel only. Intrepid is carrying the 2.6.27 series of
kernels.

[Tim Abell (tim-abell)]

I'm a bit confused, having read all the comments.
I have an inspiron 8500, which reports "Dell Computer Corporation" in dmidecode. So I don't appear to benefit from the fix in 2.6.27-11.

Does the above comment
> This is a Jaunty kernel only.
 mean that I won't get this fix until I upgrade to Jaunty in April? ( https://wiki.ubuntu.com/JauntyReleaseSchedule ).

If so, should I use the blacklist workaround mentioned, and what are the side effects? (Seeing as I have no idea doing that actually means.)

[wolfie2x (wolfie2x)]

2.6.27-11 fixed about 90% of the problem for me on Intrepid. (Dell Inspiron 9400; Vendor Str="Dell Inc.". g-p-m 2.24.0-0ubuntu8.2; system fully up-to-date)

The problem now is:
The OSD is displayed but progress bar increment/decrement is in small steps (min brightness at 50% mark). If the progress bar is brought down to 0% mark, brightness doesn't change there after at all (At this point progress bar will move in larger steps though). Brightness works again after killing g-p-m and starting again.

Looks like the kernel bug is fixed but there's still a g-p-m bug. Should I update https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/304187, report a new bug or just continue here?

[Stefan Bader (smb)]

The patch "Input: atkbd - broaden the Dell DMI signatures" has been applied to Intrepid by the update to 2.6.27.15 (see LP bug #328652)

[Ben Trusty (ben-trusty)]

2.6.27-12-generic (latest proposed update)
still broken on dell inspiron 1150

On Fri, Feb 20, 2009 at 11:15 AM, Stefan Bader
<email address hidden>wrote:

> The patch "Input: atkbd - broaden the Dell DMI signatures" has been
> applied to Intrepid by the update to 2.6.27.15 (see LP bug #328652)
>
> ** Changed in: linux (Ubuntu Intrepid)
> Status: Triaged => Fix Committed
>
> --
> X never sees brightness key release events on Dell laptops
> https://bugs.launchpad.net/bugs/261721
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "acpid" source package in Ubuntu: Invalid
> Status in "linux" source package in Ubuntu: Fix Released
> Status in "xorg-server" source package in Ubuntu: Invalid
> Status in acpid in Ubuntu Intrepid: Invalid
> Status in linux in Ubuntu Intrepid: Fix Committed
> Status in xorg-server in Ubuntu Intrepid: Invalid
> Status in acpid in Ubuntu Jaunty: Invalid
> Status in linux in Ubuntu Jaunty: Fix Released
> Status in xorg-server in Ubuntu Jaunty: Invalid
>
> Bug description:
> Binary package hint: gnome-power-manager
>
> Pressing either of the brightness keys brings up the g-p-m brightness OSD.
> This has changed recently such that it now steals keyboard focus. It
> eventually disappears, leaving corruption on the screen, giving my caret
> back. However, I can't type again until I switch to another VT and back.
>
> It also sometimes doesn't appear at all, or just appears with some
> uninitialized texture (but still steals focus).
> --
>
> This is caused by X invoking autorepeat on the brightness keys, as it never
> appears to see a release event.
>
> --
>
> This is caused by a bug in the kernel that requires a Dell specific quirk.
> It has been fixed in -proposed.
>

[Martin Pitt (pitti)]

Accepted linux into intrepid-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[maraja (ugo-grandolini)]

Problem still persists with the latest intrepid kernel update (2.6.27-11-generic) here on Dell XPS 1330, Bios A15.
Ubuntu 8.10
Attached my dmidecode.

Also (maybe there is another report?) using the OSD buttons to increase/decrease volume show on the screen the indicator that the volume is changed but, actually, the volume on Volume Applet/Alsa mixer does not change.
Used to work on Ubuntu 8.04.

[Bryan Quigley (bryanquigley)]

My dmidecode | grep Vendor is Vendor: Dell Computer Corporation

I'm using the latest proposed - 2.6.27-13-generic.

It's fixed for me! Thank you.

[Kashi Gorton (flash87)]

Bryan: the linux that appeared in proposed for me was 2.6.27-12. What's going on?

The bug still persists for me, by the way...

[Kashi Gorton (flash87)]

/proc/version:
Linux version 2.6.27-12-generic (buildd@palmer) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu12) ) #1 SMP Thu Feb 5 09:26:35 UTC 2009

sudo dmidecode | grep Vendor:
Vendor: Dell Computer Corporation

[Bryan Quigley (bryanquigley)]

It won't auto update you to it yet, it's waiting for external drivers to
build perhaps?
I manually installed it, cause my laptop doesn't require any.

If you do a search for 2.6.27-13 it should come up and you could give it a
try (but it might break prop. drivers until they get built). Alternatively
you could just wait for them to finish building.

[Dimitrios Symeonidis (azimout)]

The reason 2.6.27-13 isn't automatically installed is that, for some strange reason, linux-image-generic wasn't updated, and still points to -12...

To see this for yourself, run "aptitude why linux-image-2.6.27-12-generic", and it will tell you that it's automatically installed because you have installed linux-image-generic. Then do "aptitude show linux-image-generic, and it will tell you it depends on 2.6.27-12

[Kashi Gorton (flash87)]

/proc/version:
Linux version 2.6.27-13-generic (buildd@palmer) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu12) ) #1 SMP Thu Feb 26 07:26:43 UTC 2009

... and it's fixed and working like a dream :) thanks guys! Mucho appreciatoed. Proposed now points at the right files, and my brightness is adjustable again, all is right in the world.

[Martin Pitt (pitti)]

Dimitrios Symeonidis [2009-03-01 21:00 -0000]:
> The reason 2.6.27-13 isn't automatically installed is that, for some
> strange reason, linux-image-generic wasn't updated, and still points to
> -12...

It is updated now.

Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

[Ben Trusty (ben-trusty)]

latest kernel update fixed mine
dell inspiron 1150
2.6.27-13-generic

On Tue, Mar 3, 2009 at 3:30 AM, Martin Pitt <email address hidden> wrote:

> Dimitrios Symeonidis [2009-03-01 21:00 -0000]:
> > The reason 2.6.27-13 isn't automatically installed is that, for some
> > strange reason, linux-image-generic wasn't updated, and still points to
> > -12...
>
> It is updated now.
>
> Martin
> --
> Martin Pitt | http://www.piware.de
> Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
>
> --
> X never sees brightness key release events on Dell laptops
> https://bugs.launchpad.net/bugs/261721
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “acpid” source package in Ubuntu: Invalid
> Status in “linux” source package in Ubuntu: Fix Released
> Status in “xorg-server” source package in Ubuntu: Invalid
> Status in acpid in Ubuntu Intrepid: Invalid
> Status in linux in Ubuntu Intrepid: Fix Committed
> Status in xorg-server in Ubuntu Intrepid: Invalid
> Status in acpid in Ubuntu Jaunty: Invalid
> Status in linux in Ubuntu Jaunty: Fix Released
> Status in xorg-server in Ubuntu Jaunty: Invalid
>
> Bug description:
> Binary package hint: gnome-power-manager
>
> Pressing either of the brightness keys brings up the g-p-m brightness OSD.
> This has changed recently such that it now steals keyboard focus. It
> eventually disappears, leaving corruption on the screen, giving my caret
> back. However, I can't type again until I switch to another VT and back.
>
> It also sometimes doesn't appear at all, or just appears with some
> uninitialized texture (but still steals focus).
> --
>
> This is caused by X invoking autorepeat on the brightness keys, as it never
> appears to see a release event.
>
> --
>
> This is caused by a bug in the kernel that requires a Dell specific quirk.
> It has been fixed in -proposed.
>

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 2.6.27-14.33

---------------
linux (2.6.27-14.33) intrepid-proposed; urgency=low

  [Stefan Bader]

  * Fix FTBS due to a mysteriously missing ABI directory.

linux (2.6.27-14.32) intrepid-proposed; urgency=low

  [Stefan Bader]

  * Rebuild of 2.6.27-14.30 with 2.6.27-11.31 security patches applied

linux (2.6.27-14.30) intrepid-proposed; urgency=low

  [ Alexey Starikovskiy ]

  * SAUCE: ACPI: EC: Limit workaround for ASUS notebooks even more
    - LP: #288385

  [ Huaxu Wan ]

  * SAUCE: report rfkill changes event if interface is down
    - LP: #193970

  [ Scott James Remnant ]

  * SAUCE: floppy: Provide a PnP device table in the module.
    - LP: #255651

  [ Steve Beattie ]

  * fix apparmor memory leak on deleted file ops
    - LP: #329489

  [ Stefan Bader ]

  * Revert "ACPI: Fix compiler warnings introduced by 32 to 64 bit acpi
    conversions"
    - LP: #337019
  * Revert "ACPI: Change acpi_evaluate_integer to support 64-bit on 32-bit
    kernels"
    - LP: #337019

  [ Upstream Kernel Changes ]

  * KVM: MMU: Add locking around kvm_mmu_slot_remove_write_access()
    - LP: #335097, #333409
  * ricoh_mmc: Handle newer models of Ricoh controllers
    - LP: #311932

linux (2.6.27-13.29) intrepid-proposed; urgency=low

  [ Colin Ian King ]

  * SAUCE: Bluetooth USB: fix kernel panic during suspend while streaming
    audio to bluetooth headset
    - LP: #331106, #322082

  [ Stefan Bader ]

  * Revert "SAUCE: Work around ACPI corruption upon suspend on some Dell
    machines." (replaced by stable update)
    - LP: #330200
  * Revert "SAUCE: Add back in lost commit for Apple BT Wireless Keyboard"
    (replaced by stable update)
    - LP: #330902

  [ Upstream Kernel Changes ]

  * Revert "vt: fix background color on line feed"
    - LP: #330200
  * ti_usb_3410_5052: support alternate firmware
    - LP: #231276
  * fuse: destroy bdi on umount
    - LP: #324921
  * fuse: fix missing fput on error
    - LP: #324921
  * fuse: fix NULL deref in fuse_file_alloc()
    - LP: #324921
  * inotify: clean up inotify_read and fix locking problems
    - LP: #324921
  * mac80211: decrement ref count to netdev after launching mesh discovery
    - LP: #324921
  * sysfs: fix problems with binary files
    - LP: #324921
  * x86, mm: fix pte_free()
    - LP: #324921
  * alpha: nautilus - fix compile failure with gcc-4.3
    - LP: #324921
  * it821x: Add ultra_mask quirk for Vortex86SX
    - LP: #324921
  * libata: pata_via: support VX855, future chips whose IDE controller use
    0x0571
    - LP: #324921
  * rtl8187: Add termination packet to prevent stall
    - LP: #324921
  * serial_8250: support for Sealevel Systems Model 7803 COMM+8
    - LP: #324921
  * SUNRPC: Fix a memory leak in rpcb_getport_async
    - LP: #324921
  * SUNRPC: Fix autobind on cloned rpc clients
    - LP: #324921
  * USB: fix char-device disconnect handling
    - LP: #324921
  * USB: storage: add unusual devs entry
    - LP: #324921
  * USB: usbmon: Implement compat_ioctl
    - LP: #324921
  * ALSA: hda - add another MacBook Pro 4, 1 subsystem ID
    - LP: #324921
  * ALSA: hda - Add quirk for HP DV6700 laptop
    - LP: #324921
  * ALSA: ...

[cenoura (maggico89)]

I'm experiencing the same problem on a Samsung r60+ laptop, on both Jaunty and Karmic alpha2.
The problem is the same as described in this duplicate: <a href="https://bugs.launchpad.net/bugs/282963">bug 282963</a>. The keyboard becomes unresponsive as well as most of the applets in the gnome-panel. Only way to get back to normal is to ctrl-alt-backspace (which I have activated back).

[Saivann Carignan (oxmosys)]

cenoura : This bug is fixed, therefore the problem you get is a different bug (even the symptoms might look very similar), can you copy and launch this line in a terminal to report a brand new detailed bug report for linux? :

ubuntu-bug -p linux