[Bug 82279] Re: displayconfig resolution change bug

Andreas Wenning awen at awen.dk
Thu Jun 5 14:53:07 UTC 2008


This is an SRU request for the fix of this an two other bugs. Changelog
from the SRU i'm requesting:

kde-guidance (0.8.0svn20080103-0ubuntu16.1) hardy-proposed; urgency=low

  [ Anthony Fok ]
  * kubuntu_32_displayconfig_update_refresh_rate.patch:
    - The refresh rate was not updated for the selected resolution, so
      resolution change could fail. (LP: #82279)
  * kubuntu_33_displayconfig_add_new_video_cards.patch:
    - Added 8086:29b2 for "Intel Q35";
  * debian/copyright: s/FDL/GFDL/;

  [ Andreas Wenning ]
  * kubuntu_34_kde-powermanager_no_lid_special_behaviour_disable.patch:
    - No need to call power plugged/unplugged in init if no lid is
      found; this just make us crash. (LP: #231163)
  * Edited kubuntu_23_kde-powermanager_gpmhelper.patch to prevent
    multiple brightness- or hibernate-calls happening on certain
    machines. Already implemented for sleep-calls. (LP: #207473)

 -- Andreas Wenning <awen at awen.dk>  Thu, 05 Jun 2008 16:24:38 +0200

=== Testcase for the individual bugs: ===
#82279:
In the displaymanager choose a new resolution. The new resolution should support a lower refresh rate than the one you are currently using. If you do not touch the refrash-rate field, your current refresh rate will be used; in some cases resulting in garbage on screen / empty screen. After the update a correct refresh rate will be used.

#231163:
On affected laptops guidance no longer crashes upon starting.

#207473:
On affected laptops brightness should now stop making multiple steps; or at least it should reduce the number of steps (this bug either originates in kde-guidance or in hal or in both; this of course only fixes the kde-guidance part).

** Attachment added: "kde-guidance_0.8.0svn20080103-0ubuntu16.1.debdiff"
   http://launchpadlibrarian.net/15059440/kde-guidance_0.8.0svn20080103-0ubuntu16.1.debdiff

-- 
displayconfig resolution change bug
https://bugs.launchpad.net/bugs/82279
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.




More information about the kubuntu-bugs mailing list