Bug 22824

Summary:	Black areas appear on screen momentarily in Falkon browser
Product:	Mageia	Reporter:	aguador <waterbearer54>
Component:	RPM Packages	Assignee:	David GEIGER <geiger.david68210>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	kde, marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	falkon-3.0.0-2.mga7.src.rpm	CVE:
Status comment:

Description aguador 2018-03-24 13:04:00 CET

Irregularly-shaped portions of the screen, most frequently at the top, go black momentarily. This happens mostly with some cursor movements or when playing a video.

To reproduce:
  Start Falkon
  Play a video on a website (e.g., from youtube)

System details:
  E22.2
  X11
  Optimus hardware
  Proprietary nVidia driver

Variations tested without solving the problem:
  Changing rendering in Elementary (vSync/no vSync; hardware/software rendering)
  New profile/profile imported from Qupzilla

This did not happen with prior versions of Qupzilla on this system.

No similar bug report upstream has been found.

Comment 1 Marja Van Waes 2018-03-25 17:52:09 CEST

Assigning to the registered maintainer.

Assignee: bugsquad => geiger.david68210
CC: (none) => kde, marja11

Comment 2 aguador 2018-05-12 18:22:37 CEST

This problem persists even after recent Qt5 and webkit updates.

The problem is, however, not Falkon-specific. Otter Browser has the same problem on this system.

Comment 3 aguador 2018-05-12 18:24:14 CEST

Oops, I should have noted the Falkon update itself:

Versión de la aplicación 3.0.1
Versión de QtWebEngine: 5.10.1

Comment 4 aguador 2019-02-24 11:24:25 CET

This problem appears with all the QtWebEngines on my Magiea 7 machine (an Optimus laptop) with E22. Given the lack of other reports and some other rendering issues on this system, this likely independent of Falkon. I am changing this to "unconfirmed".

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Comment 5 aguador 2019-02-24 11:35:16 CET

Oops, I should have changed this to "invalid" as I suspect the issue lies with mesa-Enlightenment conflicts.

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => INVALID