[SOLVED] TERM env var and other issues after fixing borked arch update

archlinuznoobb · 2024-05-28 13:48:47

I have a arch system dual booted with windows running KDE alongside Hyprland.

I ran a usual yay command to update but while installing the linux package the system went into kernel panic.

So I shut it down and naturally arch wouldn't boot. So I booted using a live usb and chroot was failing. Had to reinstall ncurses and lib32-ncurses and then I was able to chroot (This could be causing my current issue). Then I reinstalled linux and was able to boot normally into arch.

When I switch to tty3 and login, I get this:

warning: Could not set up terminal.
warning: TERM environment variable set to 'linux'.
warning: Check that this terminal type is supported on this system.
warning: Could not set up terminal using the fallback. terminal type 'xterm-256color'.
warning: Could not set up terminal using the fallback. terminal type 'xterm'.
warning: Could not set up terminal using the fallback. terminal type 'ansi'.
warning: Could not set up terminal using the fallback. terminal type 'dumb'.

Also logging into KDE has missing toolbar, Hyprland also has missing waybar, some apps like spotify wont open and is all around pretty broken.

If it helps I had setup Hyprland with fish and that was my primary terminal.

Last edited by archlinuznoobb (2024-05-28 17:29:37)

seth · 2024-05-28 15:06:46

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'

Everything that shows up w/ a broken or missing mtree needs to be re-installed "--dbonly" first and then, together w/ everything that has a suspicious amount of deviating files, proper.

PSA: 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Do you use the binary nvidia (550xx) driver?

archlinuznoobb · 2024-05-28 15:22:08

I ran the command you mentioned and I think a lot of stuff is broken. Here is the output: https://0x0.st/XNZr.txt

Will I need to install every package listed in that txt file one by one manually?
Also yes, I do use the nvidia proprietary binary driver.
Also disabled windows fastboot a long long time ago.

seth · 2024-05-28 15:59:08

adwaita-cursors: no mtree file
adwaita-icon-theme: no mtree file
adwaita-icon-theme-legacy: no mtree file
alsa-card-profiles: no mtree file
archlinux-appstream-data: no mtree file
e2fsprogs: no mtree file
glfw: no mtree file
gst-plugin-pipewire: no mtree file
kitty: no mtree file
kitty-shell-integration: no mtree file
kitty-terminfo: no mtree file
libcamera: no mtree file
libcamera-ipa: no mtree file
libcups: no mtree file
libpipewire: no mtree file
linux-headers: no mtree file
luajit: no mtree file
mangohud: no mtree file
ncurses: no mtree file
pcsclite: no mtree file
pipewire: no mtree file
pipewire-alsa: no mtree file
pipewire-audio: no mtree file
pipewire-jack: no mtree file
pipewire-pulse: no mtree file
python-fonttools: no mtree file
qbittorrent: no mtree file
vulkan-validation-layers: no mtree file
xorg-xinput: no mtree file

are broken for sure, re-install them first w/ then again w/o "--dbonly"

https://bbs.archlinux.org/viewtopic.php?id=293400
https://aur.archlinux.org/packages/nvidia-535xx-dkms

archlinuznoobb · 2024-05-28 17:05:33

Just reinstalled all there with --dbonly first and then without and almost everything seems to be fixed. Thanks a lot!

Btw during boot there a quick splash screen that says fsck failed for...UUID... something. Its there only for a short while though and it wasn't there before. Should I be worried?

seth · 2024-05-28 17:07:57

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

You want to check the system journal for the fsck message and in doubt open a new thread for it (and/or try top repair it w/ a manual fsck)

Arch Linux

#1 2024-05-28 13:48:47

[SOLVED] TERM env var and other issues after fixing borked arch update

#2 2024-05-28 15:06:46

Re: [SOLVED] TERM env var and other issues after fixing borked arch update

#3 2024-05-28 15:22:08

Re: [SOLVED] TERM env var and other issues after fixing borked arch update

#4 2024-05-28 15:59:08

Re: [SOLVED] TERM env var and other issues after fixing borked arch update

#5 2024-05-28 17:05:33

Re: [SOLVED] TERM env var and other issues after fixing borked arch update

#6 2024-05-28 17:07:57

Re: [SOLVED] TERM env var and other issues after fixing borked arch update

Board footer