Bug #11489

Graphics artifacts cover parts of the web page content with Tor Browser 6.x on libvirt/QXL

Added by intrigeri 2016-05-25 17:32:27 . Updated 2016-08-02 09:29:48 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Start date:
2016-05-25
Due date:
% Done:

100%

Feature Branch:
bugfix/11500-slow-qxl
Type of work:
Test
Blueprint:

Starter:
Affected tool:
Browser
Deliverable for:

Description

tails-i386-feature_11403-tor-browser-6.x-2.4-20160525T1414Z-04b3e43.iso, host system = current sid, VM has QXL graphics:

      <model type='qxl' ram='524288' vram='262144' vgamem='262144' heads='1' primary='yes'/>

Seen it both in the Tor Browser and Unsafe Browser. Can’t reproduce in the very same VM with Tails 2.3.


Files


Subtasks


Related issues

Related to Tails - Feature #11403: Migrate to Tor Browser 6.0.x based on Firefox 45.2 Resolved 2016-05-09
Related to Tails - Bug #11500: Poor graphics performance in KVM guest with QXL driver Resolved 2016-05-30

History

#1 Updated by intrigeri 2016-05-25 17:32:40

  • related to Feature #11403: Migrate to Tor Browser 6.0.x based on Firefox 45.2 added

#2 Updated by intrigeri 2016-05-25 17:34:01

  • Assignee set to intrigeri
  • Type of work changed from Research to Test

Next step: try with different (virtual and/or bare metal) graphics adapters, try without the Mesa backport, try on current devel (i.e. with the Mesa backport and Tor Browser 5.x).

#3 Updated by intrigeri 2016-05-25 17:40:20

  • Assignee changed from intrigeri to anonym
  • Type of work changed from Test to Research

Can’t reproduce on:

  • tails-i386-devel-2.4-20160521T1819Z-66ffb1b.iso (Mesa backports, Tor Browser 5.x) in the same VM
  • tails-i386-feature_11403-tor-browser-6.x-2.4-20160525T1414Z-04b3e43.iso with a VGA graphics adapter

So it seems to be the combination of QXL with Tor Browser 6.x that is a problem.

#4 Updated by intrigeri 2016-05-25 17:43:46

  • Assignee changed from anonym to intrigeri
  • Target version set to Tails_2.4
  • Type of work changed from Research to Test

anonym can’t reproduce, so I’ll retry after rebooting (got some important host system upgrades today, didn’t reboot yet).

#5 Updated by intrigeri 2016-05-26 15:08:48

  • Category set to Hardware support
  • Assignee changed from intrigeri to goupille
  • QA Check set to Info Needed

I can still reproduce this after a reboot. I don’t know what to do about it, so adding frontdesk to the watch list, so they’re aware of this potential problem, and can let us know if anyone reports any such regression in 2.4~rc1 or later. goupille: please reassign to whoever is on duty during next week, and this one should ideally then report back and reassign to whoever is on duty from June 6 to June 12.

#6 Updated by intrigeri 2016-05-30 09:43:36

  • related to Bug #11500: Poor graphics performance in KVM guest with QXL driver added

#7 Updated by intrigeri 2016-05-30 09:43:53

  • Status changed from Confirmed to In Progress
  • Assignee changed from goupille to anonym
  • % Done changed from 0 to 50
  • QA Check changed from Info Needed to Ready for QA
  • Feature Branch set to bugfix/11500-slow-qxl

#8 Updated by anonym 2016-05-31 14:37:50

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

I cannot reproduce even without this branch merged, but trust that it fixes your problem. I do see significant improvements for Bug #11500.

Merged!

#9 Updated by intrigeri 2016-06-06 06:02:52

  • Status changed from Fix committed to In Progress
  • Target version changed from Tails_2.4 to Tails_2.5
  • % Done changed from 100 to 50
  • QA Check deleted (Pass)

See Bug #11514.

#10 Updated by intrigeri 2016-06-07 02:31:17

  • Assignee set to anonym
  • % Done changed from 50 to 60
  • QA Check set to Ready for QA

#11 Updated by anonym 2016-06-08 04:10:13

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 60 to 100
  • QA Check changed from Ready for QA to Pass

#12 Updated by intrigeri 2016-08-02 09:29:48

  • Status changed from Fix committed to Resolved