Bug 1838951 - freezes when using maps.google.com or dnf
Summary: freezes when using maps.google.com or dnf
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 32
Hardware: alphaev6
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-22 06:49 UTC by John Lutz
Modified: 2023-09-15 00:32 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-25 16:18:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg (92.05 KB, text/plain)
2020-05-22 06:49 UTC, John Lutz
no flags Details

Description John Lutz 2020-05-22 06:49:15 UTC
Created attachment 1690970 [details]
dmesg

Description of problem:
machine locks when using maps.google.com, clicking multiple browser tabs in firefox releases it. also locks sometimes with dnf. Also, windows in this current page's bugzilla report also hang sometimes.

Version-Release number of selected component (if applicable):
firefox 76.0.1

How reproducible:
maps.google.com, scroll around inside maps until freeze

Steps to Reproduce:
1.go to maps.google.com, 
2.scroll around inside maps. {freezes}
3.click firefow browser tabs {eventually releases}

Actual results:
interupted work.

Expected results:
uninterupted work.

Additional info:
latest gigaabyte bios 3/09/2018 of z170x-gaming-5
using onboard vga, portable external usb

Comment 1 John Lutz 2020-07-27 18:54:50 UTC
Switching OFF Wayland and Switching ON X solved the problem on the gigabyte motherboard. No issues at ALL anymore!



On my other computer, a laptop, this wasn't even an issue.

Comment 2 Martin Stransky 2020-07-31 10:22:48 UTC
Do you see the lag with Firefox only or is it present also with other Wayland based applications?
Also as a workaround you can install/use firefox-x11 package which is provided as a fallback.

Comment 3 Fedora Program Management 2021-04-29 16:27:11 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2021-05-25 16:18:38 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 Red Hat Bugzilla 2023-09-15 00:32:01 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


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