You are not logged in.
Hi everyone,
I've been using Arch for a while with GNOME 3.6 and locking my session left the lockscreen visible until the configured screen timeout. Now, with GNOME 3.8, each time I lock my session, my monitors get shut down ("no signal"). I can get it to display again by pressing a key, but it timeouts and shuts them down again rather quickly if I just let it sitting there.
Does anyone know if there is any way to get the old behavior back? I checked the screen timeout configuration on the control panel and I didn't find anything relevant or obviously misconfigured. I'm running a dual monitor setup on Intel HD4000 in case it makes any difference.
Thanks!
Offline
Same here, its a really stupid default. my laptop is not tablet gnome.
Offline
For me it is even worse. Not only does it automatically try to shut down the monitors. It also fails. My screen just stays black but with my monitors turned on. Once I press a key to make GDM show again and wait for it to disable the monitors again, suddenly it works.
Offline
Same problem here, there are a lot of configurations been changed and no way to customize.
Offline
I see the same basic operation here. If I click on lock from the user panel it seems to take a couple of seconds to kick in and I then see a flash of the lockscreen and my monitor is immediately soft off. I only have to move my mouse (or press a key) to get the lockscreen back, but the monitor goes off again in a short while, totally ignoring my power settings of never blanking the monitor. I guess the devs interest was mainly in battery powered devices, but user preferences should prevail over defaults, even if you're battery powered. I'm currently using a custom theme along with custom gdm theme, but I believe it was the same with the standard themes.
Last edited by sidneyk (2013-04-25 17:00:56)
Offline
I have the opposite problem. I'm on a laptop and I want the display to blank after a short time, but it doesn't. I locked it and walked away but the screen stayed on the whole time.
Offline
I guess that the problem is gnome-power-manager:
without it, "lock" works fine; with it, this strange behaviour occurs.
*edit* = if you lock your screen and push 'canc' while it is blank, then it returns "locked" as it was supposed to be.
By the way, i can not suspend my computer: if I do so, then it does not wake up, it simply reboots. Any help? Thanks
Last edited by and-bnk (2013-04-28 19:29:58)
Offline
I guess that the problem is gnome-power-manager:
without it, "lock" works fine; with it, this strange behaviour occurs.
*edit* = if you lock your screen and push 'canc' while it is blank, then it returns "locked" as it was supposed to be.By the way, i can not suspend my computer: if I do so, then it does not wake up, it simply reboots. Any help? Thanks
You may want to check this part of the systemd wiki and see if you need to configure or enable something for proper operation:
Offline
You may want to check this part of the systemd wiki and see if you need to configure or enable something for proper operation:
thank you, but it did not help
still having problem with the suspend thing...
Offline
Any success on this topic guys?
Offline