Created attachment 1547426 [details]
Issue using and image and image viewer
Description of problem:
Spinner will not terminate unless window titlebar grabbed and window moved
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install fedora rawhide or f30 pre beta drop 1.7.
2. Open terminal.
3. cp -f /usr/share/backgrounds/f30/default/standard/f30.png Pictures/ or echo "Roses are red, violets are blue." > Documents/roses.txt
4 Open nautilus (Files). Navigate to either in . Right click and open with default application offered.
Move mouse away from window or perform other actions and spinner is still going.
See attached videos.
Spinner to terminate on file loading completion.
Affects rawhide and f30 pre beta ISO compose 1.7.
Created attachment 1547427 [details]
Issue using generated text file.
Further testing. Changed from component 'gnome-shell' to 'wayland' for now.
- Issue is on rawhide wayland
- Issue is not on rawhide xorg
- Issue is on f30 pre beta 1.7 wayland
- Issue is not on f30 pre beta 1.7 xorg
- Issue is not on f29 wayland
- Issue is not on f29 xorg
All testing with VMs and not on bare metal as not available to me.
Created attachment 1547876 [details]
All apps closed and spinner still active
Proposed as a Blocker for 30-beta by Fedora user kathenas using the blocker tracking app because:
Alters and interferes with normal default desktop functionality and usability. Violation: final.
Still present on f30 pre beta ISO compose 1.8.
You were right the first time - 'wayland' is almost never the right component for a bug. Something in the GNOME stack is much more appropriate (possibly mutter or GTK+ or something rather than gnome-shell, but gnome-shell is close enough that the right people should see the bug).
I can't reproduce this bug here, though. Just tried on both my desktop and a test box I just installed Beta-1.8 on and, nope, not happening...
I can reproduce this on Fedora 30, GNOME on Wayland. I've seen this off and on since upgrading from Fedora 29 also GNOME on Wayland. But I don't think it's a blocker. Beta or final.
Created attachment 1548361 [details]
strace of gnome shell while spinner is active (mostly). When I move the cursor away from the desktop area, spinner doesn't happen and gnome-shell uses ~1% CPU and then when over the desktop gnome-shell process uses ~25% CPU with spinner.
cmurf, what version of F30 are you running when you see this? Also, are you in a VM or baremetal?
I am -1 blocker based on the given criteria and my inability to reproduce this bug (baremetal). I believe the following might be a more appropriate criteria to present this as a blocker though, as I searched the F30 Basic and Beta criteria for one that officially would fit this bug:
"No part of any release-blocking desktop's panel (or equivalent) configuration may crash on startup or be entirely non-functional."
However, in either scenario, I do not believe this bug to violate either of the above, so -1 blocker from me.
this has nothing to do with the panel, though, really.
(In reply to Geoffrey Marr from comment #9)
> cmurf, what version of F30 are you running when you see this?
Latest from updates-testing. It was a F29 to F30 upgrade using gnome-software.
o Also, are you
> in a VM or baremetal?
Baremetal. i915 graphics.
The spinner doesn't block anything from working, or require me to alter my interaction. But while it does increase my carbon footprint from time to time, we don't block on minor performance issues.
Discussed in the F30 Beta Go/No-Go meeting today. We voted to reject this as a blocker because it does not violate any release criteria.
Was present on IRC for the meeting. Put forward the bug brought eyes upon it.
Would the bug rate mentioning in the release notes, even though not a blocker?
Changed component to mutter.
Duplicate of: https://gitlab.gnome.org/GNOME/mutter/issues/501
Patch associated with bug report upstream fixes issue for me.
Created attachment 1550381 [details]
Patch from upstream, will submit as fedora PR
Duplicate of: https://gitlab.gnome.org/GNOME/gtk/issues/1754
*** Bug 1696987 has been marked as a duplicate of this bug. ***
*** Bug 1697140 has been marked as a duplicate of this bug. ***
FYI: Fix due in mutter 3.32.1 due in this coming week.
Backport patch to fix timeout of application startup sequences (rhbz#1692135)
Not a blocker, so would like it in before freeze hits.
This is second submission of same patch, but was closed as advised 3.32.1 was imminent. That release of mutter has not happened.
The freeze already happened. This would need a freeze exception to go in before Final. Proposing.
Phil: both your PRs seem broken. I'll just do it myself.
Adam: Something gone sideways this morning and I should not do things when I am tired. Was fine, will try harder next time.
=) It seems like you started from an older checkout before my changes yesterday and that's what probably sent things sideways.
gnome-shell-3.32.1-1.fc30 gnome-shell-extensions-3.32.1-1.fc30 mutter-3.32.1-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-2d456e35ff
gnome-shell-3.32.1-1.fc30, gnome-shell-extensions-3.32.1-1.fc30, mutter-3.32.1-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-2d456e35ff
gnome-shell-3.32.1-1.fc30, gnome-shell-extensions-3.32.1-1.fc30, mutter-3.32.1-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.