What could prevent from screen blanking / DPMS
by Lukas Zapletal
Hey,
I have pretty minimal i3wm install and I recently tried to set up blanking and DPMS, but
the thing is it does not work:
$ xset s blank s 10 dpms 10 15 20
$ xset q
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000002
XKB indicators:
00: Caps Lock: off 01: Num Lock: on 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 660 repeat rate: 25
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 0 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 2/1 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 10 cycle: 600
Colors:
default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
catalogue:/etc/X11/fontpath.d,built-ins
DPMS (Energy Star):
Standby: 10 Suspend: 15 Off: 20
DPMS is Enabled
Monitor is On
What could prevent blanking and suspend from happening and how to debug this? I don't
have any screensaver installed, could this be an issue?
Thanks
3 years, 12 months
Re: Blocking on user switching: redux
by Kamil Paral
On Thu, Apr 16, 2020 at 5:50 PM Patrick O'Callaghan <pocallaghan(a)gmail.com>
wrote:
> My use case is slightly different. I like to be able to log into a
> basic user configuration to test something, without logging out of my
> current session. That second desktop might even be running Gnome rather
> than KDE. Would that also count as a blocker?
>
Hello Patrick. Our criteria are mostly concerned with a default Fedora
installation (Workstation, KDE, Server, etc). We might even state it
explicitly in this criterion. So no, switching users between different
desktop environments is unlikely to be release blocking.
4 years
F32 flatpak runtime and app rebuilds coming
by Kalev Lember
Hi all,
I've pushed out an initial F32 flatpak runtime/SDK and a few apps built
against it. Would be awesome if people could give them a try:
flatpak remote-modify --enable fedora-testing
flatpak install fedora-testing org.gnome.Maps (or anything else from the
Bodhi update)
The Bodhi update is at
https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2020-dfd7272b06
and if things seem to roughly work, please leave karma there.
More F32 based flatpaks are coming, this here is just an initial test
batch. I'll work on rebuilding all of the flatpaks against F32 runtime
if this looks good.
There's also a new gnome-extensions-app flatpak in the fedora-testing
flatpak remote -- please give this a try as well (and then leave karma
at
https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2020-e4b1cea63b)
if it works. Thanks Florian for all the hard work with this!
Thanks!
--
Kalev
4 years
Re: Blocking on user switching: redux
by Adam Williamson
On Tue, 2020-04-14 at 21:20 +0200, Iñaki Ucar wrote:
> On Tue, 14 Apr 2020 at 20:14, Adam Williamson
> <adamwill(a)fedoraproject.org> wrote:
> > Hi folks!
> >
> > So, during Fedora 32 Final blocker review, a bug relating to "user
> > switching" came up for review:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1817708
> >
> > I dug into the question of whether we have tended to consider the "log
> > in / log out / shut down / reboot" criterion as covering user
> > switching, and found that this issue is actually kinda outstanding and
> > unresolved for a long time.
>
> This is about the KillUserProcesses yes/no debate [1], right?
No.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
4 years
