kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

camden lindsay, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606547/comments/22
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: linux (Ubuntu)
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/606547

Title:
  toshiba_acpi no control of display backlight after suspend to ram

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  Hello-
  toshiba portege r705

  After boot, display backlight control works fine.
  After suspend to ram (any number of times), backlight control does not work
  After suspend to ram, wake, suspend to disk, wake backlight control returns to working state.

  When control is not working, on screen display does work -- indicating backlight changing brightness (even though its not)
  /proc/acpi/toshiba/lcd changes with button pushes, as expected
  /sys/devices/platform/toshiba_acpi/backlight/toshiba/actual_brightness changes with button pushes, as expected
  however--
  /sys/devices/platform/toshiba_acpi/backlight/toshiba/brightness never changes from 0, even from a fresh boot.

  Additionally, the max_brightness=7 and the count starts at 0, but there are only 5 levels when adjusting using control buttons.  And even more oddly, when increasing from 0, display_brightness goes like this:
  0,2,4,6,7
  And when decreasing from 7, it goes like this:
  7,5,3,1,0.

  Although i think this needs to be filed against a different component,
  (suggestions?) i thought it might be valid here as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606547/+subscriptions