Should I reinstall Arch?

cryptearth · 2025-06-23 06:13:46

In reference to https://bbs.archlinux.org/viewtopic.php?id=299721 I noticed that my current install from October 2022 start to get some "it's an old windows install"-ish vibes: As I keep dragging along old versions of dependencies (although I try to clean them regular) as well as system-wide default-configs some applications started to develope a "that doesn't seem to be right" kind of feeling, most noticeable the ICAClient for Citrix.
My first idea "user specific configs" was ruled out as the same issues still persist even on a new user profile. So it seems the issue is caused by something system wide. For fun I setup a VM, did a fresh install and the issue was gone. I haven't tried to do a clean install bare metal and mount my existing /home yet, but given the issue was not present on a clean install in a vm leads me to they either caused by some old stuff or its config I keep dragging along or maybe even something hardware related so even a new bare metal install won't fix it.
Point is: Although I myself see it's to be the simplest solution "just throw it away and start from scratch" like the "windows sledgehammer method" I question if this is really necessary on Arch or are there better ways to somewhat "clean" the current install from old stuff?
As for foreign packages there aren't many

amd-vulkan-prefixes 2-1
heroic-games-launcher-bin 2.17.2-1
icaclient 25.05.0.44-1
lib32-libva-vdpau-driver 0.7.4-8
libva-vdpau-driver 0.7.4-7
minecraft-launcher 1:2.1.3-3
obs-vaapi 0.4.2-1
protontricks 1.12.1-1
protonup-qt 2.12.0-1
python-inputs 0.5-4
python-libusb-package 1.0.26.2-1
python-steam 1.6.1-1
python-vdf 4.0-2
steamcmd latest-5
vkd3d-proton-bin 2.14.1-1
wol-systemd 20240304-1
yay 12.5.0-1
zfs-linux 2.3.3_6.15.3.arch1.1-1
zfs-utils 2.3.3-1

The rest is from official repos and up-to-date.
As the install is from before KDE6 was released there're also still some KDE5 packages I'm unable to remove because they would break dependencies for even some simple stuff like VLC - so I wonder even if I start from scratch installing VLC on a new system would still pull in all this old stuff because it depends on it.
I'm a bit puzzled - some users here run thier systems for over a decade and I can only guess how bloated thier systems might be - on the other hand I see that even a "just 2 1/2 year old system" already starts to show issues I only know back from my windows days when doing a fresh install at least once a year was pretty much a must-do.

Anyway - feel free to ask and reply - in the meantime I'll try to get some space on my boot drive do to a clean install and see if the issues persist.

seth · 2025-06-23 06:46:20

https://wiki.archlinux.org/title/Pacman … _(orphans)

Typically re-installation achieves jack shit, because dependencies will remain the same and files are just lying on the disk and then the same files will be lying on the disk. pacman (no packaging system, appsnapflatdockimage aside, is fucked up in a way the windows update service is)
As for isolated tools misbehaving, I'd simply test them on a fresh user account to see whether it's your users configuration (because then even if you re-install, if you keep your $HOME you'll also keep your problems)
VLC still depends on Qt5, but KDE related deps (kwallet) seem to be strictly optional?

users here run thier systems for over a decade and I can only guess how bloated thier systems might be

Ignoring several TB of stale porn: "not"
The only real "problem" is to clean up undesired config files and caches etc. programs you no longer use might have created in your $HOME - but again: those are then just a bunch of tiny files you're never opening.

Lone_Wolf · 2025-06-23 09:19:22

https://wiki.archlinux.org/title/System … filesystem may also be helpful.

cryptearth · 2025-06-23 15:14:32

Thanks for the replies, but none were able to fix the Citrix issue in particular.
As mentioned: I already tried a fresh user account but the issue persists - so if it's caused by some config it's by a system wide config - not a local user one.

pacman -Qdt currently doesn't return anything so I have at least no non-explicit orphan depencies. I also tried to slim down the system by removing packages I haven't installed on purpose but which came along. Some were held by meta-only depencies like meta packages or package groups and easy to remove.

I also don't seem to have any orphan config or not-yet-checked pacnew.

Guess the only real test would be to just do a clean install with existing /home and check wether the issue still persists.

Million Dollar question: If the issue is cleared on the new system with existing /home how do I figure out what's causing the issue on the current system?

Whoracle · 2025-06-23 15:23:04

cryptearth wrote:

Million Dollar question: If the issue is cleared on the new system with existing /home how do I figure out what's causing the issue on the current system?

By creating another fresh user, copying your "broken" home over, chmod'ing it to the new user, and see if the issue crops up again.
If yes: strace and see which files get used, and checking those for permissions and content.
If no: compare installed packages and versions, go from there.

seth · 2025-06-23 16:01:24

If we're focussing on some citrix issue specifically, maybe elaborate on its nature.
If it's not tied to your $HOME and works in a VM, you might easily face a problem that's related to some HW specifics (graphics driver issue) - or maybe the client doesn't like zfs

cryptearth · 2025-06-23 16:14:27

I'll give a clean install on a different drive a try - could very well be something hardware or driver related
unfortunatly I can't narrow down a specific time window as I just can't remember when was the last time it worked and can only roughly estimate when it broke - so it could be just some minor patches but also some major updates of any of kernel, mesa, icaclient and others

as for zfs: unlikely as I tried it in the same VM I use to build and test zfs - but I will not install it just for the sake of testing and ruling it out

Last edited by cryptearth (2025-06-23 16:14:50)

seth · 2025-06-23 16:17:20

https://bbs.archlinux.org/viewtopic.php?id=57855
*how* does it not work?

cryptearth · 2025-06-23 19:32:38

due to how the citrix client works I'm not able to share actual screenshots - so the following mockup has to suffice
I have a three monitor setup - stretching the client window accross all three screens and then switch to full screens sets up the session with three virtual screens - so far so good
but: instead of having each virtual display shown on each screen I see all three screens in a thin stripe - somewhat like this:

+------------------------------------------------------------------++------------------------------------------------------------------++------------------------------------------------------------------+
|                                                                  ||                                                                  ||                                                                  |
|                        PHYSICAL SCREEN 1                         ||                        PHYSICAL SCREEN 2                         ||                        PHYSICAL SCREEN 3                         |
|                                                                  ||                                                                  ||                                                                  |
|+--------------------++--------------------++--------------------+||+--------------------++--------------------++--------------------+||+--------------------++--------------------++--------------------+|
||                    ||                    ||                    ||||                    ||                    ||                    ||||                    ||                    ||                    ||
||    VIRTUAL         ||    VIRTUAL         ||    VIRTUAL         ||||    VIRTUAL         ||    VIRTUAL         ||    VIRTUAL         ||||    VIRTUAL         ||    VIRTUAL         ||    VIRTUAL         ||
||    SCREEN 1        ||    SCREEN 2        ||    SCREEN 3        ||||    SCREEN 1        ||    SCREEN 2        ||    SCREEN 3        ||||    SCREEN 1        ||    SCREEN 2        ||    SCREEN 3        ||
||                    ||                    ||                    ||||                    ||                    ||                    ||||                    ||                    ||                    ||
||                    ||                    ||                    ||||                    ||                    ||                    ||||                    ||                    ||                    ||
|+--------------------++--------------------++--------------------+||+--------------------++--------------------++--------------------+||+--------------------++--------------------++--------------------+|
|                                                                  ||                                                                  ||                                                                  |
|                                                                  ||                                                                  ||                                                                  |
|                                                                  ||                                                                  ||                                                                  |
+------------------------------------------------------------------++------------------------------------------------------------------++------------------------------------------------------------------+

fun fact: the mouse gets translated correctly - so if I want to click the start menu button in the lower left corner I have to move my mouse not to that position at the virtual screen location but to the bottom of the physical screen while the display is in this weird cropped status
if I span only two screens the issue is pretty much the same but with two virtual screens "mirrored" across two physical screens while the 3rd screen is either blanked or just shows my regular desktop (according to our IT guys when citrix is in full screen it's meant to blank any not occupied additional screens)
I also tried to not go full screen but only maximized window - but this messes with the virtual desktop as it will get stretched to a virtual triple-wide screen as if I had a (3x16):9 ultra-wide monitor (some of our IT guys have 32:9 double-wide screens on which it works as intented)

again: I created a new user - issue persists - so next option: clean install with only base, plasma and ICAClient (+depencies) with new /home - and if this works mounting existing /home
question remains: how to troubleshoot if it works on new system with existing /home - which would rule out anything /home related

gonna do the clean install now - report back in about an hour or so

cryptearth · 2025-06-23 20:57:14

so here's the result:
- clean system, new user: no issue
- clean system, existing /home: no issue
- old system, clean user: issue as above
- old system, main account (which just worked on the new system): issue as above
so from this I can rule out:
- it's not an issue with my existing /home
- it's not an issue with my hardware or anything driver related (both standard kernel 6.15.3)
- it's not an issue with plasma6 itself, but maybe with some old system config
- it could be any other system wide config in any way related to the graphical system
- on my old system the issue also occurs when starting an X11 session - same as for wayland
- ZFS doesn't matter
as a side note I also noticed slight improvements in the few games I currently play - most noteworthy is satisfactory: when I join my server it takes a few seconds from click on the button for the game to actual start loading - on the clean install it was instant (yes, very minor but still a detail noteworthy because it seems not the game but some external factor causing this different behaviour)

so overall a clean install does improve things overall no matter if I bring along my existing /home
and although it would be only a few minutes to reinstall the few packages I have installed (I have a rather slim system) I rather would preserve my current install but rather fix what's "wrong"(/different) to fix those issues I encounter

sure - I'm still in favor of the windows sledgehammer method I'm used to for the past two decades - and looking over at my servers how often a minor distribution upgrade (official support since suse 10) failed and required to setuo from scratch anyway I guess it's the best option anyway - but just for the sake of the spirit of linux and in respect to others not have setup a new system in 10 years - where to even start?

seth · 2025-06-23 21:16:38

As the install is from before KDE6 was released there're also still some KDE5 packages

https://archlinux.org/news/plasma-640-w … re-on-x11/ ?

Edit:, F5

- on my old system the issue also occurs when starting an X11 session - same as for wayland

"nope"

Still, do you have an X11 log from both systems (assuming that citrix will run on xwayland anyway)

Last edited by seth (2025-06-23 21:20:49)

cryptearth · 2025-06-24 06:09:05

old system: http://0x0.st/8lP6.txt
new install: http://0x0.st/8lPI.txt
both are wayland sessions
the only difference I can see is that my regular install has the locale and keyboard layout properly set while the clean install lacks it - but otherwise I didn't noticed anything different (except for maybe some of the order of the detected devices due to the nature of usb)

Last edited by cryptearth (2025-06-24 06:13:25)

seth · 2025-06-24 06:30:11

Also all three are attached to the same GPU and randr loads (and not eg. xinerama) in both cases.

printenv

You might have setup a global environment variable to steer toolkits between wayland and X11?

I also see no monitor config, ie. w/o randr runtime intervention they'll operated as clones (pretty much what you see)
https://wiki.archlinux.org/title/Waylan … plications - make sure citrix actually uses xrandr and then compare "xrandr -q" about how the outputs are actually laid out on xwayland.
In doubt help yourself out w/ an X11 config to arrange the outputs: https://wiki.archlinux.org/title/Multih … _xorg.conf

cryptearth · 2025-06-24 14:35:58

physical connection: "dumb" passive DP-to-DVI cables
as for monitor config: since I setup the system back in 2022 I configured the layout via kde settings only once to match the physical layout
fun fact: the clean install has correctly detected the physical layout without any manual config - could be due to by coincidence I have connected my display in exact the right order to just tge right ports
I also can't recall to have ever actively started an X11 session - even back then the first session I started after SDDM came up was a wayland session - so I'm unaware about any variable or config to mannual setup my layout (I don't know what config the kde system settings might have set but if any it doesn't seem to reflect in the log)
also my screens don't appear mirrored - it's only what citrix displays - and it also only affects the output - the input, e.g. mouse, is tracked correctly accross the screens

as for printenv: this will have to wait for later - today is a department event in my company which will go for at last 10pm - with my alarm will go off at 5am ... I'm so screwed

seth · 2025-06-24 15:35:21

the clean install has correctly detected the physical layout without any manual config

Ftr, that's not possible. The monitors do not hint gps data to the system or so… you'll have picked this up from your old $HOME, somehow.

Assuming citrix runs on xwayland (please check) post the "xrandr -q" output and attempt to configure the monitors via xorg configlet.
There's also https://wiki.archlinux.org/title/KDE#Un … lution_set - no idea whether that plays into your situation.

And then there's oc a chance that citrix itself is somehow misconfigured…

cryptearth · 2025-06-24 17:43:28

seth wrote:

you'll have picked this up from your old $HOME, somehow.

givn that my existing home was not mounted until way later I don't see any chance how this could have happened
I can't tell how but it actually worked fine out of the box when I started sddm on the new install for the first time
it even correctly detected that my left-most screen is my primary and that the the other two screens are positioned both physical and logical to the right of it with the display connected to DP-3 being the middle screen at +1920 and the one connected to DP-4 is the right-most screen at +3840
I had not have to set this on my own - and I have not given any attention when I connected my screens
so from what I can tell it's just how my gpu, its vbios or the driver enumerates the connections some time at early modesetting to coincidently matching the physical layout
I can't tell you what black voodoo magic is at work here - but it just works

anyway - I'll report back the requested information when I'm home and maybe get a chance to boot up my system before fallibg asleep infront of it

cryptearth · 2025-06-25 17:18:56

printenv from "old" system:

[main@main ~]$ printenv
SHELL=/bin/bash
SESSION_MANAGER=local/main:@/tmp/.ICE-unix/1667,unix/main:/tmp/.ICE-unix/1667
WINDOWID=94011559244544
COLORTERM=truecolor
XDG_CONFIG_DIRS=/home/main/.config/kdedefaults:/etc/xdg
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
XDG_MENU_PREFIX=plasma-
ICEAUTHORITY=/run/user/1000/iceauth_jsfOiK
LANGUAGE=
SHELL_SESSION_ID=c5b5792dcb034f83aa0d91e2385165a8
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
DESKTOP_SESSION=plasma
GTK_RC_FILES=/etc/gtk/gtkrc:/home/main/.gtkrc:/home/main/.config/gtkrc
XDG_SEAT=seat0
PWD=/home/main
XDG_SESSION_DESKTOP=KDE
LOGNAME=main
XDG_SESSION_TYPE=wayland
SYSTEMD_EXEC_PID=2091
XAUTHORITY=/run/user/1000/xauth_SKlNFh
MOTD_SHOWN=pam
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/main/.gtkrc-2.0:/home/main/.config/gtkrc-2.0
HOME=/home/main
LANG=de_DE.UTF-8
XDG_CURRENT_DESKTOP=KDE
KONSOLE_DBUS_SERVICE=:1.47
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/background.slice/plasma-krunner.service/memory.pressure
WAYLAND_DISPLAY=wayland-0
KONSOLE_DBUS_SESSION=/Sessions/1
PROFILEHOME=
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
INVOCATION_ID=b96b8423f140445e9ab410ff0eb64a39
KONSOLE_VERSION=250402
MANAGERPID=1478
KDE_SESSION_UID=1000
XKB_DEFAULT_LAYOUT=de
XDG_SESSION_CLASS=user
TERM=xterm-256color
USER=main
COLORFGBG=15;0
QT_WAYLAND_RECONNECT=1
KDE_SESSION_VERSION=6
PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket
DISPLAY=:1
SHLVL=1
XDG_VTNR=1
XDG_SESSION_ID=2
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
XKB_DEFAULT_VARIANT=nodeadkeys
JOURNAL_STREAM=9:16586
KDE_FULL_SESSION=true
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
KDE_APPLICATIONS_AS_SCOPE=1
MAIL=/var/spool/mail/main
KONSOLE_DBUS_WINDOW=/Windows/1
_=/usr/bin/printenv

content of /etc/X11

[main@main ~]$ for i in $(find /etc/X11); do echo $i; cat $i; echo "-EOF-"; done
/etc/X11
cat: /etc/X11: Ist ein Verzeichnis
-EOF-
/etc/X11/xorg.conf.d
cat: /etc/X11/xorg.conf.d: Ist ein Verzeichnis
-EOF-
/etc/X11/xorg.conf.d/00-keyboard.conf
# Written by systemd-localed(8), read by systemd-localed and Xorg. It's
# probably wise not to edit this file manually. Use localectl(1) to
# update this file.
Section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option "XkbLayout" "de"
        Option "XkbVariant" "nodeadkeys"
EndSection
-EOF-
/etc/X11/xinit
cat: /etc/X11/xinit: Ist ein Verzeichnis
-EOF-
/etc/X11/xinit/xinitrc.d
cat: /etc/X11/xinit/xinitrc.d: Ist ein Verzeichnis
-EOF-
/etc/X11/xinit/xinitrc.d/90xbrlapi
# startup script for /etc/X11/Xsession.d

prefix="/usr"
exec_prefix="${prefix}"
drivers_directory="${exec_prefix}/lib/brltty"
program_directory="${exec_prefix}/bin"
xbrlapi="$program_directory/xbrlapi"
brltty="$program_directory/brltty"

if [ -x "${xbrlapi}" ]; then
  if "${xbrlapi}" 2>/dev/null ; then
    # xbrlapi could connect to BrlAPI, try to start brltty with AtSpi2 driver.
    if [ -x "${brltty}" -a \
         -e "$drivers_directory/libbrlttybba.so" -a \
         -e "$drivers_directory/libbrlttyxa2.so" ]; then
      "${brltty}" -b ba -s no -x a2 -N 2>/dev/null
    fi
  fi
fi
-EOF-
/etc/X11/xinit/xinitrc.d/40-libcanberra-gtk-module.sh
#!/bin/sh

case "${DESKTOP_SESSION-}" in
  gnome*) # Done by gnome-settings-daemon
  ;;
  *)
    # Extra check in case DESKTOP_SESSION is not set correctly
    if [ -z "${GNOME_DESKTOP_SESSION_ID-}" ]; then
      GTK_MODULES="${GTK_MODULES:+$GTK_MODULES:}canberra-gtk-module"
      export GTK_MODULES
    fi
  ;;
esac
-EOF-
/etc/X11/xinit/xinitrc.d/50-systemd-user.sh
#!/bin/sh
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

systemctl --user import-environment DISPLAY XAUTHORITY

if command -v dbus-update-activation-environment >/dev/null 2>&1; then
    dbus-update-activation-environment DISPLAY XAUTHORITY
fi
-EOF-
/etc/X11/xinit/xinitrc.d/80-appmenu-gtk-module.sh
#!/bin/sh

if [ -n "$GTK_MODULES" ]; then
    GTK_MODULES="${GTK_MODULES}:appmenu-gtk-module"
else
    GTK_MODULES="appmenu-gtk-module"
fi

if [ -z "$UBUNTU_MENUPROXY" ]; then
    UBUNTU_MENUPROXY=1
fi

export GTK_MODULES
export UBUNTU_MENUPROXY
-EOF-

[main@main ~]$ xrandr -q
Screen 0: minimum 16 x 16, current 5760 x 1080, maximum 32767 x 32767
DP-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm
   1920x1080     59.96*+
   1440x1080     59.99  
   1400x1050     59.98  
   1280x1024     59.89  
   1280x960      59.94  
   1152x864      59.96  
   1024x768      59.92  
   800x600       59.86  
   640x480       59.38  
   320x240       59.29  
   1680x1050     59.95  
   1440x900      59.89  
   1280x800      59.81  
   1152x720      59.97  
   960x600       59.63  
   928x580       59.88  
   800x500       59.50  
   768x480       59.90  
   720x480       59.71  
   640x400       59.95  
   320x200       58.14  
   1600x900      59.95  
   1368x768      59.88  
   1280x720      59.86  
   1024x576      59.90  
   864x486       59.92  
   720x400       59.27  
   640x350       59.28  
DP-3 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 531mm x 299mm
   1920x1080     59.96*+
   1440x1080     59.99  
   1400x1050     59.98  
   1280x1024     59.89  
   1280x960      59.94  
   1152x864      59.96  
   1024x768      59.92  
   800x600       59.86  
   640x480       59.38  
   320x240       59.29  
   1680x1050     59.95  
   1440x900      59.89  
   1280x800      59.81  
   1152x720      59.97  
   960x600       59.63  
   928x580       59.88  
   800x500       59.50  
   768x480       59.90  
   720x480       59.71  
   640x400       59.95  
   320x200       58.14  
   1600x900      59.95  
   1368x768      59.88  
   1280x720      59.86  
   1024x576      59.90  
   864x486       59.92  
   720x400       59.27  
   640x350       59.28  
DP-4 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 531mm x 299mm
   1920x1080     59.96*+
   1440x1080     59.99  
   1400x1050     59.98  
   1280x1024     59.89  
   1280x960      59.94  
   1152x864      59.96  
   1024x768      59.92  
   800x600       59.86  
   640x480       59.38  
   320x240       59.29  
   1680x1050     59.95  
   1440x900      59.89  
   1280x800      59.81  
   1152x720      59.97  
   960x600       59.63  
   928x580       59.88  
   800x500       59.50  
   768x480       59.90  
   720x480       59.71  
   640x400       59.95  
   320x200       58.14  
   1600x900      59.95  
   1368x768      59.88  
   1280x720      59.86  
   1024x576      59.90  
   864x486       59.92  
   720x400       59.27  
   640x350       59.28

---
printenv from clean install (w/o existing /home)

[main@main ~]$ printenv
SHELL=/bin/bash
SESSION_MANAGER=local/main:@/tmp/.ICE-unix/1070,unix/main:/tmp/.ICE-unix/1070
WINDOWID=94577527968960
COLORTERM=truecolor
XDG_CONFIG_DIRS=/home/main/.config/kdedefaults:/etc/xdg
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
XDG_MENU_PREFIX=plasma-
ICEAUTHORITY=/run/user/1000/iceauth_kVGzDi
LANGUAGE=
SHELL_SESSION_ID=933b4b877f7a4cbc930ae0f5f7e85887
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
DESKTOP_SESSION=plasma
GTK_RC_FILES=/etc/gtk/gtkrc:/home/main/.gtkrc:/home/main/.config/gtkrc
XDG_SEAT=seat0
PWD=/home/main
XDG_SESSION_DESKTOP=KDE
LOGNAME=main
XDG_SESSION_TYPE=wayland
SYSTEMD_EXEC_PID=1548
XAUTHORITY=/run/user/1000/xauth_iPgbIf
MOTD_SHOWN=pam
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/main/.gtkrc-2.0:/home/main/.config/gtkrc-2.0
HOME=/home/main
LANG=de_DE.UTF-8
XDG_CURRENT_DESKTOP=KDE
KONSOLE_DBUS_SERVICE=:1.51
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/background.slice/plasma-krunner.service/memory.pressure
WAYLAND_DISPLAY=wayland-0
KONSOLE_DBUS_SESSION=/Sessions/1
PROFILEHOME=
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
INVOCATION_ID=9bf5e177af12426da76b96cc0260daf8
KONSOLE_VERSION=250402
MANAGERPID=804
KDE_SESSION_UID=1000
XDG_SESSION_CLASS=user
TERM=xterm-256color
USER=main
COLORFGBG=15;0
QT_WAYLAND_RECONNECT=1
KDE_SESSION_VERSION=6
PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket
DISPLAY=:1
SHLVL=1
XDG_VTNR=1
XDG_SESSION_ID=2
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
JOURNAL_STREAM=9:11054
XDG_DATA_DIRS=/home/main/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
KDE_FULL_SESSION=true
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
KDE_APPLICATIONS_AS_SCOPE=1
MAIL=/var/spool/mail/main
KONSOLE_DBUS_WINDOW=/Windows/1
_=/usr/bin/printenv

[main@main ~]$ for i in $(find /etc/X11); do echo $i; cat $i; echo "-EOF-"; done
/etc/X11
cat: /etc/X11: Ist ein Verzeichnis
-EOF-
/etc/X11/xorg.conf.d
cat: /etc/X11/xorg.conf.d: Ist ein Verzeichnis
-EOF-
/etc/X11/xinit
cat: /etc/X11/xinit: Ist ein Verzeichnis
-EOF-
/etc/X11/xinit/xinitrc.d
cat: /etc/X11/xinit/xinitrc.d: Ist ein Verzeichnis
-EOF-
/etc/X11/xinit/xinitrc.d/40-libcanberra-gtk-module.sh
#!/bin/sh

case "${DESKTOP_SESSION-}" in
  gnome*) # Done by gnome-settings-daemon
  ;;
  *)
    # Extra check in case DESKTOP_SESSION is not set correctly
    if [ -z "${GNOME_DESKTOP_SESSION_ID-}" ]; then
      GTK_MODULES="${GTK_MODULES:+$GTK_MODULES:}canberra-gtk-module"
      export GTK_MODULES
    fi
  ;;
esac
-EOF-
/etc/X11/xinit/xinitrc.d/50-systemd-user.sh
#!/bin/sh
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

systemctl --user import-environment DISPLAY XAUTHORITY

if command -v dbus-update-activation-environment >/dev/null 2>&1; then
    dbus-update-activation-environment DISPLAY XAUTHORITY
fi
-EOF-

xrandr not installed

as for citrix: I did a binary diff and except from some timestamps both the install in /opt as well as the configs in ~/.ICAClient come back binary identical

so - although I keep repeating myself: it is NOT the ica-client and obvious neither my hardware nor some driver - and neither my /home - but, at least to my observation, some old system-config (or package) I drag along since somewhen between it last worked (which I can't remember) and when it broke - I'm not able to figure out which seem to causes this

I'm actually quite lost on this one and I doubt trying any other distro just for the giggles would bring any additional info as they would all be new installs and none an old 2022 install kept alive
sure - I could "clone" my regular system over and start tearing it apart - kinda like when Linus tried Pop! and killed its DE by this "yes, I know what I do" prompt - but quite honestly: going down THAT rabbit hole I'm not sure if it's even worse without ANY lead and just bring the new install back to my current just by installing about one to two dozen packages along thier dependencies is as easy as to just get a list via

yay -Qe

which returns 248 lines and import that on the new install

who knows - maybe it's exactly THAT which will cause the new install to also act up - then it's only 248 packages + dependencies to dig through

Last edited by cryptearth (2025-06-25 17:46:44)

seth · 2025-06-25 22:50:40

keyboard layout aside, the main difference is

XDG_DATA_DIRS=/home/main/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share

some old system-config (or package) I drag along since somewhen between it last worked (which I can't remember) and when it broke

You could strace the citrix client for openat

strace -f --trace=openat /opt/Citrix/ICAClient/selfservice --icaroot /opt/Citrix/ICAClient

to see what it parses…
But w/ gtk2 on wayland and weird window arrangement my money remains there - can/have you tried the behavior on X11 on the old system?

Arch Linux

#1 2025-06-23 06:13:46

Should I reinstall Arch?

#2 2025-06-23 06:46:20

Re: Should I reinstall Arch?

#3 2025-06-23 09:19:22

Re: Should I reinstall Arch?

#4 2025-06-23 15:14:32

Re: Should I reinstall Arch?

#5 2025-06-23 15:23:04

Re: Should I reinstall Arch?

#6 2025-06-23 16:01:24

Re: Should I reinstall Arch?

#7 2025-06-23 16:14:27

Re: Should I reinstall Arch?

#8 2025-06-23 16:17:20

Re: Should I reinstall Arch?

#9 2025-06-23 19:32:38

Re: Should I reinstall Arch?

#10 2025-06-23 20:57:14

Re: Should I reinstall Arch?

#11 2025-06-23 21:16:38

Re: Should I reinstall Arch?

#12 2025-06-24 06:09:05

Re: Should I reinstall Arch?

#13 2025-06-24 06:30:11

Re: Should I reinstall Arch?

#14 2025-06-24 14:35:58

Re: Should I reinstall Arch?

#15 2025-06-24 15:35:21

Re: Should I reinstall Arch?

#16 2025-06-24 17:43:28

Re: Should I reinstall Arch?

#17 2025-06-25 17:18:56

Re: Should I reinstall Arch?

#18 2025-06-25 22:50:40

Re: Should I reinstall Arch?

Board footer