** Changed in: linux (Ubuntu)
Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)
--
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/1686268
Title:
Backlight brightness level not rest
On Fri, May 26, 2017 at 19:55 Mario Limonciello
wrote:
> But so we're talking about the slider in the bios that adjusts keyboard
> backlight right? That's not tied to display backlight.
> No, the "Video" tab in BIOS has two sliders, one is for AC and another one
is for battery. Both of them are
But so we're talking about the slider in the bios that adjusts keyboard
backlight right? That's not tied to display backlight.
On Fri, May 26, 2017, 00:31 Kai-Heng Feng
wrote:
> It can't be reproduced once you changed the brightness via slider in
> BIOS.
>
> It should be reproduceable if the bri
It can't be reproduced once you changed the brightness via slider in
BIOS.
It should be reproduceable if the brightness was *never* touched in
BIOS.
Once the brightness is changed in BIOS, the issue can no longer be
reproduced regardless the brightness value.
--
You received this bug notificati
Mine was about half in the battery slider and 0 in the AC slider.
On Fri, May 26, 2017, 12:11 PM Mario Limonciello
wrote:
> That sounds a little crazy that it can't reproduce in my opinion. When it
> "did" reproduce was the brightness at one of the extremes? Eg full high on
> shutdown or full lo
That sounds a little crazy that it can't reproduce in my opinion. When it
"did" reproduce was the brightness at one of the extremes? Eg full high on
shutdown or full low on shutdown?
On Thu, May 25, 2017, 03:21 Kai-Heng Feng
wrote:
> Mario, can you take a look?
>
> A quick summary:
> 1. Boot the
Mario, can you take a look?
A quick summary:
1. Boot the system.
2. The value systemd-backlight read from intel backlight is 0.
3. systemd-backlight restore the value it from /var/lib/systemd/backlight.
4. Brightness value being overwritten to maximum value, 1500.
After I changed the brightness s
Changing the brightness in the BIOS video tab got rid of the problem!
Great!!!
I am glad that you stumble upon that only AFTER you could confirm that
the problem existed. :)
Thank you for your time and assistance!
--
You received this bug notification because you are a member of Kernel
Packages
Also, try to upgrade to the latest BIOS, that may help:
$ sudo fwupdmgr refresh
$ sudo fwupdmgr update
$ sudo reboot
--
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/1686268
Title:
Backlig
The issue's gone after I changed brightness in BIOS video tab.
So I cannot dig this anymore =(
But try if this solves your issue.
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
I now have Precision 5520 and I can reproduce the issue. I'll take a
deeper look on this issue.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification b
About the reading in #20, it was the situation at that given time, not
after a reboot. Since the
/sys/class/backlight/intel_backlight/brightness was not 1500 (full
brightness after reboot) I obviously changed it.
The dynamic of what happens is shown in the "example" section of #23.
After every reb
> 1. the grep . /var/lib/systemd/backlight/* shows the value of the
brightness that was right before the last reboot. That doesn't change
real-time when I change the brightness with the slider. The value appear
to get stored right before the reboot.
Yes, the service will restore brightness value a
Just discovered that the value returned by grep .
/var/lib/systemd/backlight/* is ALWAYS the value of cat
/sys/class/backlight/intel_backlight/brightness BEFORE reboot.
So to summarize:
1. the grep . /var/lib/systemd/backlight/* shows the value of the
brightness that was right before the last reb
Setting the multi-user.target causes a timeout error at boot,
complaining that it cannot connet lumetad (?).
BTW, as another possibly useful detail. After reboot the cat
/sys/class/backlight/intel_backlight/brightness and the grep .
/var/lib/systemd/backlight/* give both 1500 (the maximum). AS soo
Seems like there are two possibility:
1. systemd-backlight didn't restore the value successfully.
2. It did, but something else changed the value.
Let's try this:
$ sudo systemctl set-default multi-user.target
Reboot and check if this happens.
Use
$ sudo systemctl set-default graphical.target
To
$ cat /sys/class/backlight/intel_backlight/brightness
451
$ grep . /var/lib/systemd/backlight/*
75
--
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/1686268
Title:
Backlight brightness lev
Hmm, I think I am still not pretty sure I fully understand the situation
here.
So, right after reboot,
What's the value of `cat
/sys/class/backlight/intel_backlight/brightness`?
And the output of `grep . /var/lib/systemd/backlight/*`?
--
You received this bug notification because you are a mem
1. The real value of the current brightness (e.g. 75)
2. As I said: after the reboot that value is the same (e.g. 75)
3. As soon as I move the slicer in the Gnome Shell Panel, the new value gets
saved into the file (e.g. 150)
To explain you better: it looks like the value in that file is kept in
Ok, I think I should ask more explicitly:
1. What's the value of '/sys/class/backlight/intel_backlight/brightness' before
reboot?
2. What's the value after reboot?
3. What do you mean "that value is saved as soon as I change the brightness"?
--
You received this bug notification because you are
Yes, that value is saved as soon as I change the brightness. After
reboot the brightness value is not restored (indeed the back-light is
actually full brightness), although the value in that file is still the
saved one.
However running the `sudo /lib/systemd/systemd-backlight load
backlight:intel_
So is the value of '/sys/class/backlight/intel_backlight/brightness' the
stored/restored value?
--
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/1686268
Title:
Backlight brightness level n
I forgot to say that the above output comes after commenting out the
@reboot cron entry workaround and restarting, so it is exactly what it
does without any workaround.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
The exact command you wrote:
$ systemctl status systemd-backlight@intel_backlight.service
systemd-backlight@intel_backlight.service - Load/Save Screen Backlight
Brightness of intel_backlight
Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static;
vendor preset: enabled)
Act
What's the output of `systemctl status systemd-
backlight@intel_backlight.service`?
--
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/1686268
Title:
Backlight brightness level not restored
Apparently, it was working with 16.10 (4.8.0-46), although I had a
different setup (GNOME desktop added on an official UBUNTU installation
from DELL).
The problem started with Ubuntu Gnome 17.04 (4.10.0-19) and persisted
with 4.10.0-20.
About testing the upstream kernel, I am willing to try. I ju
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[
apport information
** Tags added: apport-collected zesty
** Description changed:
I am not sure if this is the right place to report this, so feel free to
move it elsewhere.
It looks like the systemd-backlight service (/lib/systemd/system
/systemd-backlight@.service) does not restore t
28 matches
Mail list logo
