This appears to be quite an old issue with Optimus graphics. For me the
workaround was to pass specific kernel parameters at boot time to inhibit acpi
control of the backlight but allow intel_backlight control
I followed the instructions at
https://nisheetlall.wordpress.com/2016/07/12/solved-bri
I found that the brightness controls (via function key or sliders in power
management) were changing the values in
/sys/class/backlight/acpi_videos0/brightness, but nothing changed in
/sys/class/backlight/intel_backlight/brightness.
When I edited the value in /sys/class/backlight/intel_backlight
I can confirm that /sys/device/platform/dock.0 does not exist on my
system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1574120
Title:
Notebook doesn't suspend when lid
Behaviour is not correct, nor was anything in my post #52 intended to
suggest that it is.
See the next couple of posts by Sebastian Bacher and myself for a full
and accurate description of the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
On my HP255G1 I have six inhibitors listed, the two blocks being;
Who: neilw (UID 1000/neilw, PID 1669/unity-settings-)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
Why: GNOME handling keypresses
Mode: block
Who: neilw (UID 1000/neilw, PID 1669/unity-sett
The problem persists after sorting the oddity with the unity-settings-
daemon, which appears to have been a one-off problem. (See bug #1577906
for more detail.)
Now I find that suspend only works if "HandleLidSwitchDocked=suspend" is
in logind.conf.
Without that I return to the bug condition.
In
Ok.
Commented out the HandleLidSwitchDocked=suspend line and restarted
systemd-logind.
Closed lid, waited a minute, the bug showed itself, the system did not
suspend.
neilw@NWPS-LAP:/etc/systemd$ systemd-inhibit
Who: Unity (UID 1000/neilw, PID 1463/compiz)
What: sleep
Why: Unity n
I've reinstated the workaround and run the requested commands again.
As far as I can see, the output of all three is exactly the same as in
the bug condition, apart from the items in the inhibitors list being
shown in a different order.
--
You received this bug notification because you are a mem
neilw@NWPS-LAP:/etc/systemd$ sleep 10; systemd-inhibit
//Lid closed, count to ten and open again to find...
Who: Telepathy (UID 1000/neilw, PID 1729/mission-control)
What: shutdown:sleep
Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay
Who: neilw (UID
System left in buggy state, debug enabled in system.conf, system
rebooted.
neilw@NWPS-LAP:~$ ls /sys/class/drm/
card0 card0-LVDS-1 controlD64 ttm
card0-HDMI-A-1 card0-VGA-1 renderD128 version
neilw@NWPS-LAP:~$ cat /sys/class/drm/*/enabled
disabled
enabled
disabled
neilw@NWPS-LAP:~$
Ok, I tried;
journalctl |grep systemd > somekindoflog.log
The result is attached.
** Attachment added: "Result of "journalctl |grep systemd > somekindoflog.log""
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+attachment/4660832/+files/somekindoflog.log
--
You received this
@pitti
neilw@NWPS-LAP:~$ ls /sys/class/drm/
card0 card0-LVDS-1 controlD64 ttm
card0-HDMI-A-1 card0-VGA-1 renderD128 version
neilw@NWPS-LAP:~$ grep -r . /sys/class/drm/*/enabled
/sys/class/drm/card0-HDMI-A-1/enabled:disabled
/sys/class/drm/card0-LVDS-1/enabled:enabled
/sys/class/d
@seb128
Yes, the bug is present with the default configuration file, but lid
close to suspend (from unity) works fine if I change the configuration.
In both the bug and functioning conditions the backlight turns off when
the lid is closed.
I will test behaviour from a console log-in later today.
@seb128
"You have a laptop not connected to an external display and configured
in settings to suspend on lid close (battery/ac) but it doesn't suspend
when you close the lid? Suspending through the menu works though and
settings HandleLidSwitchDocked=suspend makes it suspend on lid close"
Yes, th
14 matches
Mail list logo
