kernel-packages team mailing list archive

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

gagzou, thank you for your comment. If you have a bug with your backlight, please feel free to file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

-- 
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