Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1637751 - Display gets messed up when routing panel is active
Display gets messed up when routing panel is active
Status: NEW
Product: Fedora
Classification: Fedora
Component: gnome-maps (Show other bugs)
29
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Kalev Lember
Fedora Extras Quality Assurance
AcceptedFreezeException https://fedor...
: CommonBugs
Depends On:
Blocks: F29FinalFreezeException
  Show dependency treegraph
 
Reported: 2018-10-09 19:20 EDT by Adam Williamson
Modified: 2018-10-26 11:07 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
video of the bug occurring (1.11 MB, application/octet-stream)
2018-10-09 19:22 EDT, Adam Williamson
no flags Details
backtrace of the crasher that can be triggered after triggering this bug (184.81 KB, text/plain)
2018-10-10 13:41 EDT, Adam Williamson
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Gitlab GNOME/gnome-maps/issues/131 None None None 2018-10-12 16:15 EDT

  None (edit)
Description Adam Williamson 2018-10-09 19:20:39 EDT
To reproduce, just run Maps, right-click somewhere, and select 'Route from here'. The routing panel to the right of the map opens, but half of it is not visible, seemingly covered in some sort of odd white...layer. If you then resize the window, the whole routing panel disappears behind the white layer, and the window stops being square (the right hand side of the window sort of bleeds past the X button, is the best way I can describe it).

Will attach a video.

Proposing as a 29 Final blocker, per criterion "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test."
Comment 1 Adam Williamson 2018-10-09 19:22 EDT
Created attachment 1492297 [details]
video of the bug occurring
Comment 2 Adam Williamson 2018-10-10 13:41:16 EDT
Additionally, if you right click and select "What's Here?" *after* triggering this bug, gnome-maps crashes. If you do "What's Here?" *before* triggering this bug, it works. I'll attach a traceback from that crash.
Comment 3 Adam Williamson 2018-10-10 13:41 EDT
Created attachment 1492639 [details]
backtrace of the crasher that can be triggered after triggering this bug
Comment 4 Lukas Ruzicka 2018-10-11 08:14:11 EDT
I was able to reproduce this bug.
Comment 5 Kalev Lember 2018-10-11 08:21:39 EDT
We sadly don't have anyone working on gnome-maps anymore in Fedora, and I am (as the ticket is assigned to me) right now occupied with fixing various gnome-software regressions in F29 that are all much higher priority. I wouldn't recommend blocking the release on this.
Comment 6 Adam Williamson 2018-10-11 13:03:00 EDT
Remember that one way to address a release blocker is to remove the app...
Comment 7 Zbigniew Jędrzejewski-Szmek 2018-10-15 03:37:18 EDT
@adamw: gnome-maps version?

I can't reproduce this with gnome-maps-3.30.0-1.fc29.x86_64.
Comment 8 Adam Williamson 2018-10-15 11:13:29 EDT
3.30.1-1.fc29. Dunno why you're on 3.30.0.
Comment 9 Zbigniew Jędrzejewski-Szmek 2018-10-15 11:38:32 EDT
I can't reproduce with gnome-maps-3.30.1-1.fc29.x86_64 either.

Actually those two recent versions of gnome-maps work great here — display is snappy and the routing seems quite good.
Comment 10 Chris Murphy 2018-10-15 12:51:13 EDT
I can't reproduce the bug in the description and video. I can reproduce the crash in comment 2.
Comment 11 Geoffrey Marr 2018-10-15 15:17:06 EDT
Discussed during the 2018-10-15 blocker review meeting: [1]

The decision to classify this bug as an "AcceptedBlocker" was made as it violates the following criteria:

"All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test". 

We note that dropping the app from Workstation is acceptable if a fix is not available.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2018-10-15/f29-blocker-review.2018-10-15-16.00.txt
Comment 12 Kalev Lember 2018-10-16 06:21:37 EDT
I can't reproduce it here either. Can one of the people who is able to reproduce it report it upstream at https://gitlab.gnome.org/GNOME/gnome-maps please? Thanks!
Comment 13 Kalev Lember 2018-10-16 06:22:25 EDT
Ahh sorry never mind, I see it's already reported at https://gitlab.gnome.org/GNOME/gnome-maps/issues/131
Comment 14 Geoffrey Marr 2018-10-16 21:55:54 EDT
I also cannot reproduce this bug. Will send this out to the list to request more testing.
Comment 15 Paul W. Frields 2018-10-22 10:05:04 EDT
The Workstation WG discussed this bug and was against holding the release up for this bug. However, upstream are looking at it so we can winnow down the cases where it does reproduce. Some users report this working fine under intel + Wayland, so it doesn't seem to be universal. It should be possible to fix in an update.

This link may be useful: https://gitlab.gnome.org/GNOME/gnome-maps/issues/131#note_348400
Comment 16 Kamil Páral 2018-10-22 13:32:10 EDT
Discussed during today's blocker review [1]:
#agreed 1637751 – RejectedBlocker AcceptedFreezeException – After much deliberation and hearing from stickster as representative from the Workstation WG, we have unanimously decided to not block the release on this bug, based on the fact that 1) the bug is not universal, 2) the fix may destabilize other things, and 3) it seems overly-zealous to block the release on this bug. We accept it as a Freeze Exception in case a fix comes about soon.

https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2018-10-22/

Note You need to log in before you can comment on or make changes to this bug.