Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1943571 - System freeze when selecting the "move" option on a picture in picture video (Wayland).
Summary: System freeze when selecting the "move" option on a picture in picture video ...
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 34
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ffwayland
TreeView+ depends on / blocked
Reported: 2021-03-26 13:36 UTC by Filippo Landi
Modified: 2022-06-07 21:49 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-06-07 21:49:22 UTC
Type: Bug

Attachments (Terms of Use)
Screencast of what happens (deleted)
2021-03-26 18:24 UTC, Filippo Landi
no flags Details

Description Filippo Landi 2021-03-26 13:36:08 UTC
Description of problem:
Fedora 34 beta clean install, updated and using default settings.
On Wayland (default setting) the system freeze when selecting the "move" option on a picture in picture video (I have tested it with YouTube videos).
It doesn't happen with Xorg where it will move the window just fine.

Additional info:
I have an Nvidia GTX1060 6GB using Nouveau driver as it is the default.

Comment 1 Martin Stransky 2021-03-26 17:07:37 UTC
Can you please a screencast of it?

Comment 2 Filippo Landi 2021-03-26 18:24:28 UTC
Created attachment 1766720 [details]
Screencast of what happens

The moment that the screencast stops is when I click "muovi" (italian for "move") and I see a black screen (video driver crashing?). 
However now the black screen doesn't show glitches and I have noticed that after a few seconds (I would say 5 seconds) it recovers but at the login screen, instead this afternoon I had glitches with the blackscreen and the PC seemed unrecoverable so I had to force shutdown.  
Maybe something has changed since I have used Xorg after I have experienced the bug and now I just switched to Wayland for doing the screencast.
I can make a video with my phone in case.

Comment 3 Martin Stransky 2021-03-29 14:05:24 UTC
I see, Thanks. It works for me on Fedora 33 - can it be a Fedora 34 regression? (btw. you can move the PIP button with pressed left mouse button).

Comment 4 Martin Stransky 2021-04-28 09:55:19 UTC
I updated my system to Fedora 34 but I can't reproduce it.

Comment 5 Ben Cotton 2022-05-12 15:24:34 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Ben Cotton 2022-06-07 21:49:22 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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.

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

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