Page MenuHomeSolus

Certain updates enable disable-lock-screen conf setting
Open, Needs More InfoPublic

Description

This has been happening for a while, I believe a total of 3 times, and is consistent across two of my machines. It most recently happened with the update of systemd to 244, along with the other packages that had updates this morning.

When relevant updates are installed, and the system is rebooted, the org.gnome.desktop.lockdown.disable-lock-screen dconf setting is automatically enabled. This disables locking on suspend. Only the update itself appears to change the setting, as it persists when changed back to off.

I am on Solus Budgie on both affected systems, with the latest package updates.

The package update that changed this setting was as follows (sourced from eopkg history):

* json-c is upgraded from 0.13.1-10-1-x86_64 to 0.13.1-11-1-x86_64 with delta.
* cryptsetup is upgraded from 1.7.5-7-1-x86_64 to 2.2.2-9-1-x86_64.
* systemd is upgraded from 239-77-1-x86_64 to 244-78-1-x86_64 with delta.
* pam is upgraded from 1.3.1-17-1-x86_64 to 1.3.1-18-1-x86_64 with delta.
* volume_key is upgraded from 0.3.9-3-1-x86_64 to 0.3.12-4-1-x86_64 with delta.
* libblockdev is upgraded from 2.22-5-1-x86_64 to 2.23-6-1-x86_64 with delta.
* udisks is upgraded from 2.7.6-18-1-x86_64 to 2.8.4-19-1-x86_64 with delta.
* systemd-devel is upgraded from 239-77-1-x86_64 to 244-78-1-x86_64.
* systemd-32bit is upgraded from 239-77-1-x86_64 to 244-78-1-x86_64 with delta.
* json-c-32bit is upgraded from 0.13.1-10-1-x86_64 to 0.13.1-11-1-x86_64 with delta.
* php is upgraded from 7.3.12-78-1-x86_64 to 7.3.13-79-1-x86_64 with delta.
* pam-devel is upgraded from 1.3.1-17-1-x86_64 to 1.3.1-18-1-x86_64 with delta.

Event Timeline

serebit created this task.Jan 14 2020, 12:04 AM
serebit updated the task description. (Show Details)
serebit updated the task description. (Show Details)
DataDrake triaged this task as Needs More Info priority.Feb 5 2020, 5:37 AM
DataDrake added a subscriber: DataDrake.

I think this will probably be gschema related. Can you grep for that key in /usr/share/glib-2.0/schemas? Thanks.

Result was:

Binary file /usr/share/glib-2.0/schemas/gschemas.compiled matches
/usr/share/glib-2.0/schemas/org.gnome.desktop.lockdown.gschema.xml:    <key name="disable-lock-screen" type="b">
serebit added a comment.EditedFeb 10 2020, 8:15 PM

Just happened again. I'm using takeback to see what caused it.

Edit: Couldn't reproduce it using takeback, it might be unrelated to eopkg, although I don't have many guesses as to what it could be.

It happened again after updating the GNOME components in unstable. @JoshStrobl, do you have any idea what could be causing this?

serebit added a comment.EditedApr 15 2020, 12:34 AM

It seems to only be happening when I'm on the unstable repository, as it stopped happening on my laptop after I switched to stable, but it still happens on my desktop. Don't know what that means, though.

@serebit is this still happening?

Seems so. An update on my (shannon) laptop disabled it again a week or two ago.