Graphical interface is broken - Brave: Icons are no longer visible

Support Graphics & Display
,
1

After yesterday’s update, my desktop background is barely recognizable. The desktop wallpaper has broken up into vertical lines. In Brave, no characters were visible at all. I’ve managed to get the problem in Brave under control for now by launching Brave this way:

brave --disable-gpu

After that, Brave was readable again, so I turned off hardware acceleration. The rest (Desktop) looks terrible. What can I do?

❯ inxi -Fxxyc0
System:
  Host: tom-manjaro-notebook Kernel: 7.0.10-1-MANJARO arch: x86_64 bits: 64
    compiler: gcc v: 16.1.1
  Desktop: GNOME v: 50.1 tk: GTK v: 3.24.52 wm: gnome-shell dm: GDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: X55C v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: X55C v: 1.0 serial: <superuser required>
    part-nu: ASUS-NotebookSKU Firmware: UEFI vendor: American Megatrends
    v: X55C.409 date: 01/09/2013
Battery:
  ID-1: BAT0 charge: 38.8 Wh (98.8%) condition: 39.2/47.5 Wh (82.5%)
    volts: 10.8 min: 10.8 model: ASUSTeK K55--52 serial: N/A charging:
    status: not charging cycles: N/A
CPU:
  Info: dual core model: Intel Core i3-2328M bits: 64 type: MT MCP
    arch: Sandy Bridge rev: 7 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 798 min/max: 800/2200 cores: 1: 798 2: 798 3: 798 4: 798
    bogomips: 17560
  Flags-basic: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
    vendor: ASUSTeK driver: i915 v: kernel arch: Gen-6 ports: active: LVDS-1
    empty: DP-1,HDMI-A-1,VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0116
  Device-2: Sunplus Innovation Asus Webcam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 4-1.3:3 chip-ID: 1bcf:2883
  Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
    compositor: gnome-shell driver: gpu: i915 display-ID: 0
  Monitor-1: LVDS-1 model: AU Optronics 0x22ec res: 1366x768 dpi: 101
    diag: 394mm (15.5")
  API: EGL v: 1.5 platforms: device: 0 drv: crocus device: 1 drv: swrast gbm:
    drv: crocus surfaceless: drv: crocus wayland: drv: crocus x11: drv: crocus
  API: OpenGL v: 4.6 compat-v: 3.3 vendor: intel mesa v: 26.1.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 3000 (SNB GT2)
    device-ID: 8086:0116 display-ID: :0.0
  Info: Tools: api: eglinfo,glxinfo x11: xprop
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20
  API: ALSA v: k7.0.10-1-MANJARO status: kernel-api
  Server-1: sndiod v: N/A status: off
  Server-2: JACK v: 1.9.22 status: off
  Server-3: PipeWire v: 1.6.5 status: off
  Server-4: PulseAudio v: 17.0-98-gb096 status: active with: pulseaudio-alsa
    type: plugin
Network:
  Device-1: Ralink RT5390 Wireless 802.11n 1T/1R PCIe vendor: Foxconn
    driver: rt2800pci v: 2.3.0 pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0
    chip-ID: 1814:5390
  IF: wlp2s0 state: up mac: f4:b7:e2:9d:27:9e
  Device-2: Qualcomm Atheros AR8161 Gigabit Ethernet vendor: ASUSTeK
    driver: alx v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000
    bus-ID: 03:00.0 chip-ID: 1969:1091
  IF: enp3s0 state: down mac: 60:a4:4c:75:cc:d4
Drives:
  Local Storage: total: 465.76 GiB used: 191.82 GiB (41.2%)
  ID-1: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB
    speed: 6.0 Gb/s serial: 2329E6EF3F81
Partition:
  ID-1: / size: 95.56 GiB used: 75.93 GiB (79.5%) fs: ext4 dev: /dev/sda2
  ID-2: /boot/efi size: 998 MiB used: 288 KiB (0.0%) fs: vfat dev: /dev/sda1
  ID-3: /home size: 350.69 GiB used: 115.88 GiB (33.0%) fs: ext4
    dev: /dev/sda4
Swap:
  ID-1: swap-1 type: partition size: 9.77 GiB used: 0 KiB (0.0%) priority: -1
    dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 2100
Info:
  Memory: total: 8 GiB note: est. available: 7.2 GiB used: 3.34 GiB (46.4%)
  Processes: 253 Power: uptime: 21m wakeups: 0 Init: systemd v: 260
    default: graphical
  Packages: 1696 pm: pacman pkgs: 1686 pm: flatpak pkgs: 10 Compilers:
    clang: 22.1.5 gcc: 16.1.1 Shell: Zsh v: 5.9 running-in: gnome-terminal
    inxi: 3.3.40
[Stable Update] 2026-05-27 - Kernels, NVIDIA, Firefox, Thunderbird, Mesa, Blender
Video problems after last upgrades
2

Ahm, you answered yourself in the title - downgrade mesa!?
Or do you need help with the exact commands?

3

The exact command would be great. Will this version stick, or will we have to start over with the next update?

4

Just downgrading mesa is a bad idea, you end up in a partial syc’d package situation as many packages depend on mesa and mesa depends on many others. If you have no timeshift backup you could use to revert to an older stage, better wait for the fix, if it’s really mesa linked.

2 Likes
5

There was some info in a post of the update thread: [Stable Update] 2026-05-27 - Kernels, NVIDIA, Firefox, Thunderbird, Mesa, Blender - #48 by emerson.cavalcanti

But you can directly execute for example this:

sudo pacman -U https://archive.archlinux.org/packages/m/mesa/mesa-1%3A26.0.6-1-x86_64.pkg.tar.zst
6

Since this is about the 5-6-7 user with pre 2011 intel gpu, and there is an official bug report in the mesa github i think we are pretty sure at this point :slight_smile:
I have written a recommendation to wait with the update in the “known problems” but for those who didn’t wait…of course restoring a backup will be better. Compromise, whit all the negatives as you correctly pointed out - downgrading mesa.
The ultimate solution would be to fast track the new version as soon as ready for all branches, but last time i checked several days ago upstream still hadn’t released a fixed version. Gotta check again.

Alternative command:
manjaro-downgrade mesa
And you select the previous newest version. Might need to install manjaro-downgrade first.

Please note that the point of partial downgrade is valid - if you have a snapshot of the entire root pre-update it will be better to use that.

3 Likes
7

This is a well-known issue with older Intel graphics and mesa.

@Teo 's workaround works and worked well for me for over a month, despite @Wollie 's concerns. And yes, manjaro-downgrade offers the option to add mesa to the ignore list for future updates. However, I suggest you avoid doing so. Why?

On 2026-06-03 a new version of mesa which fixes the problem entered Arch Extra-Testing. On 2026-06-04 (earlier today) it was moved out of testing into Arch Extra. Manjaro will pick up the update in due course.

8

Then lets ping @philm to fast track the new fixed mesa to all branches, so that people with pre 2011 intel gpus can use their computers withouth the need to downgrade or restore snapshots.

3 Likes
9

Bug fixes
ANV: dEQP ASTC tests crash w/ FPE_INTDIV on Xe3

intel/blorp: VK_ANDROID_external_format regression on buildtype=debug

the new mesa 26.1.0-1 is causing mutliple graphical issues on intel i5-2400 and higher (integrated graphics)

Remark Teo: meant is actually lower, every intel gpu released pre 2011.

1 Like
10

When will the update be available? Or do I have to install them manually?

11

Speaking only as an ordinary user, it showed up on my Unstable Branch machine the other day. Not yet on my Testing Branch one, as of noontime US Eastern 2026-06-06.

The version to look for is mesa 1:26.1.2-1. Keep an eye on it here: Branch compare for Manjaro

In the meanwhile, sudo manjaro-downgrade mesa works. If you choose “no” when asked if you want to add it to your Ignore List, when the update comes, you’ll get updated.

3 Likes
12

Pinging @philm @Yochanan to fasttrack the new mesa to all branches so that people having pre-2011 Intels can use manjaro stable again in a supported way.

In case that takes unreasonable amount of time, just as downgrading, alternate solution will be to manually install those packages from unstable branch. Again, that will put you in unsupported state. Also keep in mind some other packages are closely connected to the mesa version, like vulkan.

13

But that’s why fast-tracking the new mesa may not be a good idea. :thinking:

14

That is why it has to be done from someone with deep understanding of the system and only if safe. If not safe a note saying it will also be helpful.

2 Likes
15

There is mesa-amber for older hardware. That worked for me.

2 Likes