I have had success with acpi_backlight=native.
The superfluous listeners for backlight really should be muted...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527157
Title:
Brightness controls
The bug is still present in Ubuntu 15.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527157
Title:
Brightness controls skips Levels.
To manage notifications about this bug go to:
Seems odd to me that this bug is a low priority. The results are pretty
poor UX.
There are 3 interesting solutions here.
http://askubuntu.com/questions/208331/brightness-control-increments-brightness-by-4-instead-of-1
Fix 1 is a partial fix that worked for me right away. Still looking into
the
This bug needs more attention.
There are still big amount of laptops where the brightness is
incorrectly adjusted by 2 or 3 steps per one brightness key press.
Some affected machines:
* Dell E4300
* Asus F200CA
* Fujitsu E751
--
You received this bug notification because you are a member of
This bug seems to have gone stale (again?), but I'd like to report that
it affects me with:
* 13.10, fully updated
* Thinkpad T440p (FHD panel, if that matters)
Using the slider in Settings Brightness Lock, it seems that there is
~15 brightness levels (it's hard to get an exact count, since
Hello,
I have this exact same issue on 12.04 32bits on Dell VOSTRO 3450.
I am a bit confused of all the posts above... is there a patch for 12.04 at the
end?
Short instruction on how to apply the patch will be highly appreciated
(or a link to a wiki or something about applying patches in
Just popped in to check on this bug. I don't have the hardware I filed
this against anymore, and I'm still happy on OS X and my Macbook Air,
but I feel a responsibility to the users still stuck with this problem.
Why are you guys marking the g-p-m bug invalid? The switch to g-s-d
doesn't
Why are you guys marking the g-p-m bug invalid?
Because see previous comments.
g-s-d handles media keys. This bug is appeared, because we have a case, when
g-s-d should handle brightness keys differently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
gsd-media-keys-manager.c.rej :
--- plugins/media-keys/gsd-media-keys-manager.c 2012-04-14 11:13:20.0
+0400
+++ plugins/media-keys/gsd-media-keys-manager.c 2012-04-14 11:20:07.772836587
+0400
@@ -142,6 +144,8 @@
NotifyNotification *volume_notification;
In order for this patch to apply properly, it should be applied last,
after all ubuntu patches. In you case you don't have any of them
applied.
If you got package from packages.ubuntu.com, there are 2 source files:
one http://archive.ubuntu.com/ubuntu/pool/main/g/gnome-settings-daemon
Patch 16_use_synchronous_notifications.patch -- is the one, that my patch
heavily depends on.
Also, as far, as I understand, it's incompatible with debian.
To make patch for debian, I need to understand, where to get correct
params for update_screen_cb(), to call it from
Hmm... really strange.
I made patch ubuntu 11.10, g-s-d 3.2.2-0ubuntu2.1. May be you upgraded to 12.04
already?
Actually, I should make patch for 12.04, as it's latest stable now. Will do
this bit later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, I didn't write instruction:
- put the file into debian/patches/ dir
- add line 52_brightness_in_hardware.patch to 'series' file in that dir (not
sure if this step is required)
- build package as usual
This patch should be applied last, after all ubuntu/debian patches.
That's why it fails.
I'm using Debian Wheezy, but I tried it on Ubuntu's 3.2.2 source package
and it failed with the same error.
I tried unpacking the package and using patch -p1
52_brightness_in_hardware.patch, and that didn't work.
I tried putting it in the debian/patches directory and using dpkg-buildpackage,
Patch didn't work for me. What gnome-settings-daemon version did you
work on? (3.2.2 here)
$ patch -p1 ../52_brightness_in_hardware.patch
patching file data/org.gnome.settings-daemon.plugins.power.gschema.xml.in.in
patching file plugins/media-keys/gsd-media-keys-manager.c
Hunk #1 succeeded at
Thanks. I'll test this out as soon as I find time to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527157
Title:
Brightness controls skips Levels.
To manage notifications about this bug go to:
Here is the patch. Please review it.
** Patch added: 52_brightness_in_hardware.patch
https://bugs.launchpad.net/archlinux/+source/gnome-power-manager/+bug/527157/+attachment/3063911/+files/52_brightness_in_hardware.patch
--
You received this bug notification because you are a member of
My patch is similar to one in comment #15.
Differences are:
- it uses gsettings api (commonly used by g-s-d now)
- it doesn't break StepUp/StepDown dbus methods
- it's smaller
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
James: no, there is no need to touch kernel. You should have noticed,
that brightness control works as expected, before you login (during boot
or even on login screen).
Problem is in user-level process running during user session. We have to
find that process, than fix will be pretty simple.
See
Oh, that was about g-s-d source!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527157
Title:
Brightness controls skips Levels.
To manage notifications about this bug go to:
** Changed in: gnome-power-manager (Ubuntu)
Status: Triaged = Invalid
** Also affects: gnome-settings-daemon
Importance: Undecided
Status: New
** Changed in: gnome-settings-daemon
Assignee: (unassigned) = Dmitriy Geels (dmig)
--
You received this bug notification because
Fix itself is pretty simple, but all that g/dconf mess confuses me.
Need to understand, how to create new key in dconf...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527157
Title:
Brightness
Oh yeah! #24 is really dirty one!
But it gave me a clue, how this bug should be fixed:
Patching StepUp/StepDown handlers is very bad practice, because these methods
may be called by some other applications. We need to prevent calls to these
methods depending on some parameter.
The problem
I would change status on g-p-m to 'Invalid' and assign bug to other
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527157
Title:
Brightness controls skips Levels.
To manage notifications
Dmitriy: Yes it is a dirty hack :) I don't know of any other
applications that would increment the backlight up and down, and GNOME's
ability to set the brightness to a specific percentage (without going
through steps inbetween) *should* still be functional with it...although
even the unpatched
This patch is for GNOME 3.2 that permanently disables gnome-settings-
deamon's ability to step-up and step-down the backlight. For those who
still can't get the correct brightness steps, this is a workaround. It
works perfectly on my Lenovo Thinkpad x220.
I'm not usually a code hacker or
Please note that the above patch is ONLY for those encountering this
problem and should definitely be used ONLY on an individual basis. It
will break backlight control for everyone else using GNOME 3.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.3 kernel[1] (Not a kernel in the daily directory). Once you've
tested the upstream kernel, please remove the 'needs-upstream-testing'
tag(Only that
Happy Birthday Bug 527157! Gee, has it been two years already? It
feels like just yesterday I was wondering why I couldn't get more than
5-7 brightness levels! Three Ubuntu releases later, and I've had to find
two different solutions to the same problem. Maybe it's a g-p-m bug!
Maybe it's a
Here's a thread in the linux-thinkpad mailing list about this issue (it affects
XFCE as well as GNOME):
http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2012-February/050576.html
The thinkpad-acpi kernel module maintainer says:
This typically means broken crap that reacts to
I have better with my Thinkpad X100e : 4 levels of brightness per keypress !
This reduces from 16 to 5, which is quite annoying.
I didn’t have the problem up to natty…
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is still a problem in Oneric.The version of Gnome Power Manager
is completely different (3.1.3). Is there a fix possible for this? The
bug is exactly the same. Two brightness levels when only one is needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Tested Konstantin Lavrov's patch (Comment #15) in Natty (11.04). worked
like a charm. With the patch, double brightness events are now gone in
my Alienware M11xR2 as well. Please commit ASAP!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
A patched GPM is available from my PPA:
https://launchpad.net/~baudm/+archive/backports
The packages incorporate the original patch that I've posted here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks everyone, i've fixed my backlight problem with following steps:
1) set options video brightness_switch_enabled=0
to /etc/modprobe.d/video.conf
2) compile and install patched gnome-power-manager
Hope this changes will go to upstream. The only minor problem is that
gnome-power-manager is not
** Patch added: patch for GNOME Power Manager 2.32.0
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/527157/+attachment/1716645/+files/14-brightness-in-hardware.patch
--
Brightness controls skips Levels.
https://bugs.launchpad.net/bugs/527157
You received this bug
I made the modification to apply to gnome-power-manager-2.32.0 tarball
in Maverick.
Please, test it.
For me it solve everything with brightness
* Adding /apps/gnome-power-manager/backlight/brightness_in_hardware key.
It is just workaround to prevent g-p-m from adjusting brightness,
if Fn +
** Patch removed: 14-brightness-in-hardware.patch
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/527157/+attachment/1716368/+files/14-brightness-in-hardware.patch
--
Brightness controls skips Levels.
https://bugs.launchpad.net/bugs/527157
You received this bug
I solved this problem by adding a gconf key, named
brightness_in_hardware (reminiscent of HAL), for setting whether or not
to use xrandr for stepping the brightness up/down. Please test my patch
(agaist gpm 2.30.1) and see if it works for you.
** Patch added: 14-brightness-in-hardware.patch
Here's the updated patch.
** Patch removed: 14-brightness-in-hardware.patch
http://launchpadlibrarian.net/52070036/14-brightness-in-hardware.patch
** Patch added: 14-brightness-in-hardware.patch
http://launchpadlibrarian.net/52071575/14-brightness-in-hardware.patch
--
Brightness controls
** Tags added: patch
--
Brightness controls skips Levels.
https://bugs.launchpad.net/bugs/527157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Patch updated:
- Honor brightness_in_hardware setting regardless of the backend used (xrandr,
HAL, or whatever future backend; for consistent behavior)
- Set default value of brightness_in_hardware to 'true' (most people would
probably set this to 'true' anyway)
** Patch added:
** Also affects: gnome-power-manager (Arch Linux)
Importance: Undecided
Status: New
--
Brightness controls skips Levels.
https://bugs.launchpad.net/bugs/527157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I tested this in Arch, and it affects Arch's current version as well.
Every version of GPM I've seen seems to have this issue. Kubuntu's
power manager does not have this problem. I looked into the code for
GPM, and noticed that xrandr is used to adjust the brightness. The HAL
code has an option
It being set to Triaged means we have everything that we need. It is
unlikely with this issue there is a workaround at this moment you will
have to wait for a fix. If you know anything about programing you might
want to look into a possibility of you making a patch yourself.
--
Brightness
Is there any other information that I can provide to help out? I
understand this is low priority, but I'm hoping someone will have a
Eureka! moment and find a workaround/fix.
--
Brightness controls skips Levels.
https://bugs.launchpad.net/bugs/527157
You received this bug notification because
** Summary changed:
- Brightness controls create triple brightness changes on Dell Mini 1012 -
TEST CASE
+ Brightness controls skips Levels.
--
Brightness controls skips Levels.
https://bugs.launchpad.net/bugs/527157
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Confirmed
--
Brightness controls skips Levels.
https://bugs.launchpad.net/bugs/527157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
set to triaged/low as per Anzenketh's request.
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Low
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Triaged
--
Brightness controls skips Levels.
https://bugs.launchpad.net/bugs/527157
You received this
49 matches
Mail list logo
