Xfce Problems still persist with Mesa

Support Graphics & Display
1

I thought a clean install with the latest iso xfce-23.1.3-240113 would help but no.
manjaro-downgrade
DOWNGRADE_FROM_ALA=1 sudo downgrade mesa
Down grade to mesa 1:23.1.9-1
Now I am on …9-1 everything is working fine. Is there a better workaround than this?
What time period do you think before this bug is fixed.
inxi -Fazy

System:
  Kernel: 6.6.10-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=7de2947a-a4ff-40b0-baf2-cbbbcb88cc0c rw quiet splash apparmor=1
    security=apparmor resume=UUID=2262e34b-9c31-4649-b2c1-2ca2ae1abadf
    udev.log_priority=3
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 wm: xfwm4 v: 4.18.0
    with: xfce4-panel tools: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: K73TA v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: K73TA v: 1.0 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends v: 214 date: 04/06/2012
Battery:
  ID-1: BAT1 charge: 20.8 Wh (100.0%) condition: 20.8/48.8 Wh (42.6%)
    volts: 12.4 min: 11.1 model: ASUS PA3533U type: Li-ion serial: <filter>
    status: full
CPU:
  Info: model: AMD A6-3400M APU with Radeon HD Graphics bits: 64 type: MCP
    arch: K12 Fusion level: v1 built: 2011 process: GF 32nm family: 0x12 (18)
    model-id: 1 stepping: 0 microcode: 0x3000027
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 512 KiB
    desc: d-4x64 KiB; i-4x64 KiB L2: 4 MiB desc: 4x1024 KiB
  Speed (MHz): avg: 849 high: 1000 min/max: 800/1400 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 800 2: 799 3: 800 4: 1000
    bogomips: 11185
  Flags: ht lm nx pae sse sse2 sse3 sse4a svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Sumo [Radeon HD 6520G] vendor: ASUSTeK driver: radeon v: kernel
    alternate: amdgpu arch: TeraScale-2 code: Evergreen process: TSMC 32-40nm
    built: 2009-15 ports: active: LVDS-1 empty: HDMI-A-1,VGA-1 bus-ID: 00:01.0
    chip-ID: 1002:9647 class-ID: 0300
  Device-2: AMD Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M]
    vendor: ASUSTeK driver: radeon v: kernel alternate: amdgpu arch: TeraScale-2
    code: Evergreen process: TSMC 32-40nm built: 2009-15 pcie: gen: 1
    speed: 2.5 GT/s lanes: 8 link-max: gen: 2 speed: 5 GT/s lanes: 16
    bus-ID: 01:00.0 chip-ID: 1002:6741 class-ID: 0300 temp: 50.5 C
  Display: x11 server: X.org v: 1.21.1.10 compositor: xfwm4 v: 4.18.0 driver:
    X: loaded: radeon unloaded: modesetting alternate: fbdev,vesa dri: r600
    gpu: radeon display-ID: :0.0 note: <missing: xdpyinfo/xrandr>
  Monitor-1: LVDS-1 model: Chi Mei Opto 0x1721 built: 2009 res: 1600x900
    dpi: 104 gamma: 1.2 size: 382x215mm (15.04x8.46") diag: 448mm (17.6")
    ratio: 16:9 modes: max: 1600x900 min: 640x480
  API: EGL v: 1.5 hw: drv: amd r600 platforms: device: 0 drv: r600 device: 1
    drv: r600 device: 2 drv: swrast gbm: drv: kms_swrast surfaceless: drv: r600
    x11: drv: r600 inactive: wayland
  API: OpenGL v: 4.5 vendor: mesa v: 23.1.9-manjaro1.1 glx-v: 1.4
    direct-render: yes renderer: AMD SUMO (DRM 2.50.0 / 6.6.10-1-MANJARO LLVM
    16.0.6) device-ID: 1002:9647 memory: 500 MiB unified: no
Audio:
  Device-1: AMD BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G series]
    vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:01.1
    chip-ID: 1002:1714 class-ID: 0403
  Device-2: AMD FCH Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 00:14.2 chip-ID: 1022:780d class-ID: 0403
  API: ALSA v: k6.6.10-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-2: MediaTek Wireless_Device driver: mt7921u type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:2 chip-ID: 0e8d:7961
    class-ID: 0000 serial: <filter>
  IF: wlp0s16f0u2 state: up mac: <filter>
Drives:
  Local Storage: total: 2.93 TiB used: 212.43 GiB (7.1%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Netac model: SSD 120GB MX
    size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 17O4 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: ST1000LM024 HN-M101MBB
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
    tech: HDD rpm: 5400 serial: <filter> fw-rev: 0001 scheme: GPT
  ID-3: /dev/sdd maj-min: 8:48 model: USB 3.0 Disk 3.0 size: 1.91 TiB
    block-size: physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s
    lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 2.00 scheme: MBR
Partition:
  ID-1: / raw-size: 102.69 GiB size: 100.52 GiB (97.89%)
    used: 25.85 GiB (25.7%) fs: ext4 dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 296 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 931.51 GiB size: 915.82 GiB (98.32%)
    used: 185.18 GiB (20.2%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda3 maj-min: 8:3
Sensors:
  System Temperatures: cpu: 6280.4 C mobo: N/A
  Fan Speeds (rpm): N/A
  GPU: device: radeon temp: 51.0 C device: radeon temp: 51.0 C
Info:
  Memory: total: 16 GiB note: est. available: 15.11 GiB used: 2.23 GiB (14.8%)
  Processes: 228 Power: uptime: 3h 11m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform
    avail: shutdown,reboot,suspend,test_resume image: 6.02 GiB
    daemons: xfce4-power-manager,upowerd Init: systemd v: 255
    default: graphical tool: systemctl
  Packages: 1096 pm: pacman pkgs: 1091 libs: 350 tools: pamac pm: flatpak
    pkgs: 5 Compilers: clang: 16.0.6 gcc: 13.2.1 Shell: Bash v: 5.2.21
    running-in: xfce4-terminal inxi: 3.3.32

All thoughts welcome.

2

Can you please describe what kind of problems that you are having with mesa/xfce?

That is one hot machine:

3

Ok, if I log onto a site like ebay, all the images do not display correctly. If I move over the images some of them come into focus but others overlap one another.
Here on the forum, if I move the mouse over the box at the bottom of the posts, where all the icons of the posters are shown, I get an colour rectangle.
For example if I hover over @jrichard326, I would get an orange rectangle.

4

I would look at the compositor settings for the system, with xfce it is also the window manager.

Perhaps disable xfce compositor and try with picom or xcompmgr compositor.

1 Like
5

Did you upgrade mesa package to latest 23.3.3?

6

Yes, and the problem still exists. I am a bit vague on the time line because I had a medical emergency and everything will time to get back to normal.
I have been chasing this problem for a while and it appears when “google-chrome hardware set off” the bug stops. Now updated mesa to current version. I do not know the reason for the bug but this work-around has let me update my system.

7

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.