Yesterday I did an update (using yes | yay) for about 75 packages on my 6 year old EndeavourOS system. I do updates every 2 weeks in general. Rebooted, did some work and left the screen on, for an hour (I usually do this). Came back and saw my screen having weird doubling text glitch, [like this screenshot above]. This issue also visible on my firmware setting (BIOS) screen, which leads me to believe this might be a h/w issue, though not sure.

I want to know whether an arch update can break my display. One particular thing I noticed this morning was, when i adjusted my display brightness, the screen went back to normal for a minute or so.

Also recently I changed my battery about 2 months ago. This was my second battery replacement. After I did my first battery replacement (3 years ago), my laptop had similar display issues with Intel integrated graphics on Windows a month later. which forced me to switch. It was fine on Linux, up until now. So it got me thinking if there is any connection with battery replacements and display issues. I know it sounds weird. Earlier there were not display anomalies on the BIOS screen, but now there is.

Is there a way to fix this.

System info: HP Envy, EndeavourOS Linux 6.12.1-arch1-1, Intel® Core™ i7-8550U with Intel UHD Graphics 620

[Update 1]
I hooked up my laptop to an external monitor and everything looks fine on the monitor screen. So the issue is only with my Laptop’s screen I guess.

[Update 2]

Packages I upgraded yesterday

alsa-card-profiles alsa-ucm-conf alsa-utils sqlite npth systemd-libs libsysprof-capture gnupg file systemd pacman archlinux-keyring bash-completion btrfs-progs c-ares dav1d dkms edk2-ovmf ell eos-translations fastfetch spirv-tools glslang libpipewire pipewire pipewire-audio libwireplumber wireplumber pipewire-jack libjxl shaderc libplacebo pixman ffmpeg noto-fonts firefox flatpak fluidsynth fwupd gst-plugin-pipewire iwd js115 js128 less libbpf libsynctex libtool openal mpv noto-fonts-extra passt perl-image-exiftool pipewire-alsa pipewire-pulse pkgconf plocate pv qt6-translations qt6-base qt6-declarative qt6-multimedia-ffmpeg qt6-multimedia qt6-svg qt6-wayland sudo systemd-resolvconf systemd-sysvcompat ttf-nerd-fonts-symbols-common ttf-nerd-fonts-symbols virtiofsd webkit2gtk-4.1 webkitgtk-6.0 welcome xterm librewolf-bin librewolf-bin-deb

  • rtxn@lemmy.worldEnglish
    5·
    10 days ago

    using yes | yay

    Don’t do that. You don’t know what prompt you’re replying to with “y”. Use yay -Syu --noconfirm if you want to run it unattended.

    Could you list the packages that were updated? grep upgraded /var/log/pacman.log, then copy the lines that have the correct date.

    • overgrown@lemmings.worldOPEnglish
      1·
      10 days ago
      Package list

      alsa-card-profiles alsa-ucm-conf alsa-utils sqlite npth systemd-libs libsysprof-capture gnupg file systemd pacman archlinux-keyring bash-completion btrfs-progs c-ares dav1d dkms edk2-ovmf ell eos-translations fastfetch spirv-tools glslang libpipewire pipewire pipewire-audio libwireplumber wireplumber pipewire-jack libjxl shaderc libplacebo pixman ffmpeg noto-fonts firefox flatpak fluidsynth fwupd gst-plugin-pipewire iwd js115 js128 less libbpf libsynctex libtool openal mpv noto-fonts-extra passt perl-image-exiftool pipewire-alsa pipewire-pulse pkgconf plocate pv qt6-translations qt6-base qt6-declarative qt6-multimedia-ffmpeg qt6-multimedia qt6-svg qt6-wayland sudo systemd-resolvconf systemd-sysvcompat ttf-nerd-fonts-symbols-common ttf-nerd-fonts-symbols virtiofsd webkit2gtk-4.1 webkitgtk-6.0 welcome xterm librewolf-bin librewolf-bin-deb

      • lurch (he/him)@sh.itjust.worksEnglish
        1·
        10 days ago

        you got multiple font packages there, but I think they are for Wayland/X not for console. (my initial thought looking at the picture was “bad console font setting”)

      • rtxn@lemmy.worldEnglish
        1·
        10 days ago

        The one that stands out to me is fwupd. If it has a pacman hook, it’s possible that it might have borked some firmware on the computer. Try flashing a firmware update manually. You might be able to downgrade to the last working version or the factory default if the motherboard supports Flashback.