F32, Automatic suspend isn't working.
by Chris Murphy
cross-posting test@ and desktop@
Fedora Workstation 32 (upgraded from f31)
Laptop on battery power set aside, 12 hours later it's dead instead of
sleeping. On F31 it reliably would sleep after 20 minutes.
Sleep still happens when pressing the power button and closing the
lid. It seems to be a GNOME automatic suspend timer problem.
Using dconf editor, I changed the
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout
Custom value 30 and the problem doesn't happen. Is there a way to
increase debug messages somehow to find out whether this timeout is
being reached? And what process or policy is causing it to be reset?
With the available information I can't figure out what's preventing
sleep.
--
Chris Murphy
1 year
any shell extensions preferences can't be opened unless
"gnome-extensions-app" is installed first
by Kamil Paral
Hello,
in F32, if you install gnome-shell extension through a web browser or dnf
and then want to display its configuration (a wrench icon next to it at
https://extensions.gnome.org/local/ ), or if you want to configure some of
the pre-installed extensions like background-logo, nothing happens after
you click on the button. No configuration is displayed. You need to install
gnome-extensions-app [1], which fixes the configuration dialogs, and you
can finally display them (even from a web browser). Or you can install
gnome-tweaks, which pulls gnome-extensions-app as a dependency. In the
out-of-the-box state, though, you can't display configuration and it's not
clear why.
This seems like a use case that was not considered, and it looks broken
from user PoV. I can see the following fixes:
a) Include the ability to show extension dialogs directly to gnome-shell
(that was the case in F31), and only distribute the application file in
gnome-extensions-app. It seems that all that needs to happen is to move
/usr/bin/gnome-shell-extension-prefs from gnome-extensions-app package to
gnome-shell package.
b) Install gnome-extensions-app by default (not ideal, people can uninstall
it and it breaks the dialogs, that is obscure behavior)
c) Make chrome-gnome-shell require gnome-extensions-app. This will fix the
web browser use case. Note, chrome-gnome-shell is installed by default, so
this would make gnome-extensions-app also installed by default.
Only a) fixes all use cases, I believe. Because extensions themselves can
have a button to show their configuration, I believe. If I remove
gnome-extensions-app, which looks to be a *manager* for extensions, I
wouldn't expect it to break the ability to show extensions preferences. But
it will, unless a) is done.
Which of the options is preferable? Or some other option? I'll file a bug
according to your recommendation. It would be really great if you could fix
this before F32 Final release.
Kamil
[1] I don't see "Extensions" app in gnome-software in a clean installation,
only in an upgraded one. Why, I don't know - but this brokenness is very
regular in gnome-software. A new user can't install it easily, though,
that's the point.
3 years, 8 months
f32 beta and volume beeps
by Matthew Miller
Hi everyone! In previous Fedora Workstation / GNOME, pressing the volume
up or down keys would cause a beep at the new level. This doesn't seem to
happen for me after an upgrade. I'm pretty sure it previously happened even
with "System Sounds" set to off, but in any case, I've now turned those on
and still get no beeps. (The buttons still work, and I get the visual
indicator, but no audible one.)
Is this an intentional change?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
3 years, 8 months
Call for testing: 4K displays and/or resolution scaling on X11
(especially AMD adapters)
by Adam Williamson
Hi folks!
We have a proposed F32 blocker bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1809717
which reports issues with 4K displays when using X11 (not Wayland).
Initial indications suggest this may be specific to AMD graphics
adapters: the reporter has an AMD adapter, and a couple of our team in
Brno have been able to reproduce issues on an AMD adapter but not an
Intel adapter. It's also suggested that the issue might actually be in
display scaling (which is used on small high-resolution displays by
default, hence the association with 4K, but can be enabled on any
display for testing).
So, to help us figure out the shape of this bug, can we ask folks to
test on whatever hardware you have available? The actual bug is that
only 1/2 or 1/4 of the display is lit up, the rest of it is black, like
in this image:
https://bugzilla.redhat.com/attachment.cgi?id=1667282
1. Run a GNOME-on-Wayland session, and see if the bug happens:
1. a) out-of-the-box
1. b) with display scaling manually enabled if it was not auto-enabled
(go to 'Displays' and change the 'Scale' setting to 200% if it is at
100% by default; you may have to log out and back in after changing the
setting, not sure)
2. Run a GNOME-on-X11 session, and see if the bug happens:
2. a) out-of-the-box
2. b) with display scaling manually enabled if it was not auto-enabled
(go to 'Displays' and change the 'Scale' setting to 200% if it is at
100% by default; you may have to log out and back in after changing the
setting, not sure)
3. Run a KDE-on-X11 session, and see if the bug happens:
3. a) out-of-the-box
3. b) with display scaling manually enabled if it was not auto-
enabled (go to 'Display Configuration' and change 'Global scale' to
200% , then log out and back in)
Please report back your results with info on the graphics card and
display used for testing. If you do hit the bug, you can also add a
comment to the bug report noting which configuration(s) produced the
bug and including the same info on the graphics card and display used.
Thanks very much!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
3 years, 8 months
fedora-workstation-repositories package not part of workstation
livecd
by Hans de Goede
Hi All,
With all the WFH stuff going on I set up a new fresh installed
laptop for my wife.
She needs google-chrome on there because for some reason MS-teams
does not want to allow video-conferencing in Firefox.
After doing a fresh F32 beta install from the workstation livecd
I wanted to edit /etc/yum.repos.d/google-chrome.repo to enable
that repo, but it was not there.
AFAIK the intention is for the fedora-workstation-repositories
to be there, so I think we might have a bug in comps here somewhere?
Regards,
Hans
p.s.
I have the feeling from some older installs on older machines that
the same issue is present in Fedora 31, but not much we can do
about that.
3 years, 8 months