Page MenuHomeSolus

Running phoronix-test-suite enables disable-lock-screen conf setting
Closed, ResolvedPublic

Description

When running phoronix-test-suite on either my desktop or laptop, both of which use Solus, the disable-lock-screen key in dconf is immediately set to enabled.

GitHub issue that covers this: https://github.com/phoronix-test-suite/phoronix-test-suite/issues/291

Event Timeline

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">

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?

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.

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

serebit renamed this task from Certain updates enable disable-lock-screen conf setting to Running phoronix-test-suite enables disable-lock-screen conf setting.Jan 3 2021, 7:07 PM
serebit updated the task description. (Show Details)

@DataDrake Finally figured out what it is. Updated task accordingly.