Bug 1960737

Summary:	openbox locks up unexpectedly quickly
Product:	[Fedora] Fedora	Reporter:	joern
Component:	openbox	Assignee:	Miroslav Lichvar <mlichvar>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	34	CC:	christoph.wickert, joern, mlichvar
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-08 00:06:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description joern 2021-05-14 17:32:40 UTC

Description of problem:

When using the openbox window manager / environment, I notice it locks up relatively quickly, i.e. the screen goes blank and I have to enter my password to unlock.

In the settings (right click on background / preferences / settings / privacy / screen lock), I tried to set set the blank screen delay to 15 minutes and the automatic
screen lock delay to one hour, but to no avail.  Even disabling automatic screen lock altogther in that menue has no effect.

I tried to time it by typing 'date' in an xterm, leaving the inputs untouched for a while, and typing 'date' again after the screen blanked and I unlocked it.
The time difference was 5 minutes and 15 seconds, so apparently the effective
delay is 5 minutes.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. install openbox (if not installed already), set a long delay for blank screen delay and screen lock
2. log into openbox
3. wait 5 minutes

Actual results:

screen goes blank, need to enter password to log unlock


Expected results:

session stays active with switched-on screen and ordinary keybopard / mouse controls for longer.


Additional info:

Comment 1 Miroslav Lichvar 2021-05-17 07:05:17 UTC

Do you use openbox alone, or in some desktop environment like XFCE?

openbox doesn't provide a lock screen program. Maybe you have xscreensaver installed? I'm not sure what is the default timeout.

Comment 2 joern 2021-05-17 23:44:21 UTC

I've been using openbox alone, but with the KDE system settings menue to set the display orientation (the standard one doesn't do anything).

openbox also shows crashes now and then I haven't been able to properly reproduce yet, which is why I'm temporarily using gnome classic right now (xfce and KDE seem defunct too) to get a bit of work done and to check if the hardware appears stable otherwise.  34 hours with loads between 0 and 45 seems good so far in that aspect.

Comment 3 Ben Cotton 2022-05-12 16:15:31 UTC

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-06-08 00:06:38 UTC

Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.