Brightness hotkeys only work after suspending/resuming system.

Bug #697959 reported by Rick Ucker
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

All hotkeys except brightness work normally. Brightness hotkeys (fn+f6/f7) only begin to work after I suspend & resume once. After that, they work perfectly until the next reboot. Before I suspend & resume, xev and acpi_listen report no keypress when I press the hotkeys, which are fn+f6/f7.

The affected system is a Toshiba Satellite a305-s6857 running 10.10.

I created a new user account, logged in after booting up, and the issue was unchanged. So, this doesn't appear to be a config issue with my dot files.

Once it starts working (after I suspend & resume), the outputs are this:

acpi_listen: fn+f6, then fn+f7:
video DD03 00000087 00000000
video DD03 00000086 00000000

xev: fn+f6:
MappingNotify event, serial 36, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 36, synthetic NO, window 0x5e00001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 36, synthetic NO, window 0x5e00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 36, synthetic NO, window 0x0,
    keys: 4294967232 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

I am reporting this against the linux package as per https://wiki.ubuntu.com/Hotkeys/Troubleshooting (I got all the way to step 6-2 with no success).

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-24-generic 2.6.35-24.42
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rick 2055 F.... pulseaudio
 /dev/snd/pcmC0D0p: rick 2055 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd6500000 irq 47'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,1179ff1c,00100003'
   Controls : 13
   Simple ctrls : 10
Date: Wed Jan 5 22:31:54 2011
HibernationDevice: RESUME=UUID=5a618996-6b13-4b2a-8f8f-de14c76a07b0
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: TOSHIBA Satellite A305
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic root=UUID=723cef00-ee95-4943-ad9f-fc6730ee97bf ro vga=792 splash quiet quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 02/13/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.80
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr1.80:bd02/13/2009:svnTOSHIBA:pnSatelliteA305:pvrPSAG0U-02701V:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: Satellite A305
dmi.product.version: PSAG0U-02701V
dmi.sys.vendor: TOSHIBA

Revision history for this message
Rick Ucker (rick-ucker) wrote :
Rick Ucker (rick-ucker)
description: updated
Revision history for this message
Chase Douglas (chasedouglas) wrote :

Kind of sounds like a bios bug to me :(.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Rick,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kernel-suspend
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Rick Ucker (rick-ucker) wrote : Re: [Bug 697959] Re: Brightness hotkeys only work after suspending/resuming system.
Download full text (5.8 KiB)

Hi Jeremy, I tried two things:

   1. At the recommendation of Chase (also subscribed to this bug) I
   installed the backported 2.6.37-12-generic-26~lucid1-ubuntu kernel from
   here.<http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu/pool/main/l/linux-lts-backport-natty/>No
change in behavior.
   2. At your recommendation, I installed 2.6.37-999-generic #201101190911.
   With this kernel, I actually suffered a regression: I can't change
   brightness at all (even after suspend/resume), either via the hotkeys or via
   the Gnome Power Manager Brightness Applet. The latter used to work no matter
   what (no suspend/resume needed), but now I see a red slash with a circle
   around it at the center of the Brightness Applet icon. It also has a tooltip
   that reads: "Cannot get laptop panel brightness."

Rick

On Thu, Jan 13, 2011 at 4:36 PM, Jeremy Foshee <email address hidden>wrote:

> Hi Rick,
>
> If you could also please test the latest upstream kernel available that
> would be great. It will allow additional upstream developers to examine the
> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once
> you've tested the upstream kernel, please remove the
> 'needs-upstream-testing' tag. This can be done by clicking on the yellow
> pencil icon next to the tag located at the bottom of the bug description and
> deleting the 'needs-upstream-testing' text. Please let us know your
> results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: kernel-suspend
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/697959
>
> Title:
> Brightness hotkeys only work after suspending/resuming system.
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> All hotkeys except brightness work normally. Brightness hotkeys
> (fn+f6/f7) only begin to work after I suspend & resume once. After
> that, they work perfectly until the next reboot. Before I suspend &
> resume, xev and acpi_listen report no keypress when I press the
> hotkeys, which are fn+f6/f7.
>
> The affected system is a Toshiba Satellite a305-s6857 running 10.10.
>
> I created a new user account, logged in after booting up, and the
> issue was unchanged. So, this doesn't appear to be a config issue with
> my dot files.
>
> Once it starts working (after I suspend & resume), the outputs are
> this:
>
> acpi_listen: fn+f6, then fn+f7:
> video DD03 00000087 00000000
> video DD03 00000086 00000000
>
> xev: fn+f6:
> MappingNotify event, serial 36, synthetic NO, window 0x0,
> request MappingKeyboard, first_keycode 8, count 248
>
> FocusOut event, serial 36, synthetic NO, window 0x5e00001,
> mode NotifyGrab, detail NotifyAncestor
>
> FocusIn event, serial 36, synthetic NO, window 0x5e00001,
> mode NotifyUngrab, detail NotifyAncestor
>
> KeymapNotify event, serial 36, synthetic NO, window 0x0,
> keys: 4294967232 0 0 0 0 ...

Read more...

tags: removed: needs-upstream-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.