Thanks for your explanations. If GNOME has stopped aiming for compatibility, with other applications, then that’s really a shame for the other reasons you mentioned (full desktop environment that works out of the box). For me, one of the base principles of Linux has always been the ability to combine different tools of choice to get the best results for your specific situation. An application that veers away from this principle is really veering away from user self-determination and thus everything that has made Linux great.
I’ll keep my fingers crossed that Antergos will find a way to implement a fully working default Desktop nontheless in the near future. Except for this issue of one of the basic settings not working (which, simple as the issue itself may be and easily as it’s workaround solution may be applied, does constitute the difference between a fully matured distro and an enthusiast effort to me) I continue to be absolutely delighted by this distro and will definitely continue to use it!
Thanks also for merging my suggestions with the wiki article.
Works like a charm, thank you! :)
Well, that’s embarrassing: It’s not like I didn’t look for solutions quite some time before asking. Guess I should have used forum and wiki search rather than search engines :/
One small change to the wiki article I would suggest: If I’m not mistaken, then KDE doesn’t actually use the GNOME powersettings daemon and
OnlyShowIn=KDE;is just used so that GNOME doesn’t see the desktop entry. The key for completely hiding a desktop entry is
Hidden(see Desktop Entry Specification). Therefore, instead of editing, you can simply attach the new key to the desktop file with
echo "Hidden=true" | sudo tee -a /etc/xdg/autostart/org.gnome.SettingsDaemon.Power.desktop
And one addition: If like me you prefer not to interfere with global files that may be subject to update changes, you can enable the changes on a per-user basis by copying the file to the
.config/autostartdirectory in your home dir and then add the key by doing
$ cp /etc/xdg/autostart/org.gnome.SettingsDaemon.Power.desktop ~/.config/autostart/ $ echo "Hidden=true" >> .config/autostart/org.gnome.SettingsDaemon.Power.desktop
Both tested and working.
This has resolved the issue for me, so I’ve marked the thread as SOLVED.
I still have a few questions though:
- Since this seems to be a general problem with GNOME/Lightdm and the wiki solution works, why not make it a default for GNOME installations on Antergos? I saw that you already suggested this a while ago here last july . Have there been any objections to taking this path?
- If GNOME is unfriendly to customizations and doesn’t play nice with other applications, even to the point of breaking basic functionality, then why is it the default desktop environment on a fresh Antergos install, which is arguably a customized system and intended to be open for customizations? (I’ve personally enjoyed using GNOME for a long time when I’m not using Openbox, but I’ve never actually tried it out in mixed environments before, so this downside is new to me)
Please don’t get me wrong: I don’t mean to be annoying, I’m just trying to understand how things work.
Hi! Long time Debian user here but new to Antergos/arch. I’m on a default Antergos install (with Lightdm and Gnome) on a Thinkpad T520. It’s been a truly promising love affair so far, but now a seemingly straightforward issue is giving me headaches: Blanking the screen when idle will not work.
My aim: I want the screen to go into standby/poweroff after 60 seconds of idle time, and lock to be applied either 30 seconds after the screen has gone blank or immediately.
Relevant settings are these (those directly related are highlighted) :
Settings -> Privacy -> Screen Lock
- Automatic Screen Lock: On
- Lock screen after blank for: 30 seconds (alternative: “Screen turns off”)
- Show Notifications: On
Settings -> Power
- Blank Screen: 1 minute
- Automatic suspend: On
- On Battery Power: On
- Delay: 15 minutes
- Plugged In: On
- Delay: 30 minutes
No changes to light-locker settings
Expected behavior: Screen should be switched off after 60 seconds (and be locked after another 30 seconds)
Actual behavior: Absolutely nothing. :(
The problem is, I don’t even know where to start debugging this, since there are no related events registered via
What does work:
xset dpms force off
Things that also work (though not directly part of the root problem):
- The lock button in the GNOME system menu (top right corner)
- The keyboard shortcut for locking:
- Suspend on AC and on Battery
Since I can reproduce this in a completely fresh VM installation, I’m wondering whether it is a general bug/problem after a fresh default installation?
I very much Hope someone can help me fix this. I often work in crowded environments where I’m easily distracted, so this basic feature is very important to me.