Screen corruption / blank tabs after system resumes from sleep

  • As reported in another thread, this can be 'fixed' by disabling hardware acceleration. However, the symptoms appear to be slightly different.

    On waking system from sleep, occasionally the screen will be glitched as in the attached image. At other times, there is no obvious glitching, but some tabs will show a white screen which remains white after shift-F5. If I click blindly on the white screen, links on the page will open normally. This only appears to affect some tabs, and it seems random which tabs will be affected.

    This issue persists with all extensions disabled (vivaldi --disable-extensions). Nvidia drivers have been updated without effect.

    On restarting Vivaldi, everything works perfectly until next resume from sleep.

    As far as I recall, this problem began after updating to 3.3.


    System:    Host: <filter> Kernel: 5.8.0-7.1-liquorix-amd64 x86_64 bits: 64 compiler: N/A 
               parameters: audit=0 intel_pstate=disable 
               root=UUID=<filter> ro quiet splash 
               Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: Compiz 0.8.18 
               dm: LightDM 1.26.0 Distro: MX-19.2_x64 patito feo October 15  2019 
               base: Debian GNU/Linux 10 (buster) 
    Machine:   Type: Desktop Mobo: MSI model: 760GA-P43(FX) (MS-7699) v: 1.0 serial: <filter> 
               BIOS: American Megatrends v: 1.3 date: 10/14/2014 
    CPU:       Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer 
               family: 15 (21) model-id: 2 stepping: N/A microcode: 6000852 L2 cache: 2048 KiB 
               flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 41997 
               Speed: 1399 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 1: 1398 
               2: 1399 3: 2093 4: 2929 5: 1399 6: 1399 
               Vulnerabilities: Type: itlb_multihit status: Not affected 
               Type: l1tf status: Not affected 
               Type: mds status: Not affected 
               Type: meltdown status: Not affected 
               Type: spec_store_bypass 
               mitigation: Speculative Store Bypass disabled via prctl and seccomp 
               Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
               Type: spectre_v2 
               mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
               Type: srbds status: Not affected 
               Type: tsx_async_abort status: Not affected 
    Graphics:  Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB] vendor: ZOTAC driver: nvidia v: 450.66 
               bus ID: 01:00.0 chip ID: 10de:1c02 
               Display: x11 server: X.Org 1.20.4 driver: nvidia 
               unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: compiz v: 0.8.18 
               resolution: 1920x1080~60Hz 
               OpenGL: renderer: GeForce GTX 1060 3GB/PCIe/SSE2 v: 4.6.0 NVIDIA 450.66 
               direct render: Yes 
    Audio:     Device-1: AMD SBx00 Azalia vendor: Micro-Star MSI driver: snd_hda_intel v: kernel 
               bus ID: 00:14.2 chip ID: 1002:4383 
               Device-2: NVIDIA GP106 High Definition Audio vendor: ZOTAC driver: snd_hda_intel 
               v: kernel bus ID: 01:00.1 chip ID: 10de:10f1 
               Sound Server: ALSA v: k5.8.0-7.1-liquorix-amd64 
    Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
               vendor: Micro-Star MSI driver: r8169 v: kernel port: c800 bus ID: 02:00.0 
               chip ID: 10ec:8168 
               IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
    Drives:    Local Storage: total: 1.49 TiB used: 590.03 GiB (38.6%) 
               ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB block size: 
               physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
               rev: CC45 scheme: MBR 
               ID-2: /dev/sdb vendor: Western Digital model: WD6400AAKS-22A7B2 size: 596.17 GiB 
               block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 3B01 
               scheme: MBR 
    Partition: ID-1: / raw size: 29.30 GiB size: 28.71 GiB (98.00%) used: 16.95 GiB (59.0%) fs: ext4 
               dev: /dev/sda5 
               ID-2: /home raw size: 900.78 GiB size: 885.64 GiB (98.32%) used: 573.08 GiB (64.7%) 
               fs: ext4 dev: /dev/sda7 
               ID-3: swap-1 size: 450.0 MiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
               cache pressure: 100 (default) dev: /dev/sda6 
    Sensors:   System Temperatures: cpu: 50.0 C mobo: 38.6 C gpu: nvidia temp: 38 C 
               Fan Speeds (RPM): cpu: 0 fan-1: 646 fan-3: 0 gpu: nvidia fan: 55% 
               Voltages: 12v: N/A 5v: N/A 3.3v: 3.38 vbat: 3.25 
    Repos:     No active apt repos in: /etc/apt/sources.list 
               Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
               1: deb buster-updates main contrib non-free
               Active apt repos in: /etc/apt/sources.list.d/debian.list 
               1: deb buster main contrib non-free
               2: deb buster/updates main contrib non-free
               Active apt repos in: /etc/apt/sources.list.d/mx.list 
               1: deb buster main non-free
               Active apt repos in: /etc/apt/sources.list.d/spotify.list 
               1: deb stable non-free
               No active apt repos in: /etc/apt/sources.list.d/various.list 
               Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
               1: deb stable main
    Info:      Processes: 290 Uptime: 1h 23m Memory: 15.63 GiB used: 2.83 GiB (18.1%) Init: SysVinit 
               v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
               running in: quick-system-in inxi: 3.0.36 

  • Similarly to the other thread have you tested if it happens with Chromium (85) as well? Could be many reasons, a Chromium bug, kernel-GPU driver incompatibility, a bugged powermanagement packet etc.

  • Ahh, I see what you mean. Problem reproducible in both Chromium 83 & 87.


  • Moderator

    @fossean As it happens in some Chromium versions for you, it is a issue you should report to your MX Linux bugtracker and Chromium bug tracker.

Log in to reply

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.