Arch Linux

Kamion008

Member

Registered: 2025-01-02

Posts: 3

KDE connect, systemsettings, discover crash immediately when launched

Since I began configuring qt, systemsettings, KDE connect, discover crash immediately when launched, however KDE connect launches if I launch KDE connect settings and discover if I look for the details of an app.
This does not happen to dolphin, which instead does not get themed and the files don't have any applications to be opened into, and KDE iso image writer, which works as intended.
Any other qt application has no issues.
Plasma itself takes now around 1m to start after I had tried to reinstall the plasma packages to see if that would resolve the problem.
Using a different user shows the same issues.
Hardware that I am using:
CPU: AMD Ryzen 5 7600X
GPU0: AMD Radeon Graphics
GPU1: NVIDIA GeForce RTX 4070

journal of me starting plasma wayland and opening systemsettimgs: https://0x0.st/8zwz.txt

P.S.: English is not my native language; please excuse typing errors.
P.P.S.: This is the first time I have written here, please suggest me how to post issues better

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,076

Re: KDE connect, systemsettings, discover crash immediately when launched

What exactly did you try to do that lead to those issues? You mention they started when you "began configuring qt" what exactly did you do when trying this? What output do you get from

printenv

Kamion008

Member

Registered: 2025-01-02

Posts: 3

Re: KDE connect, systemsettings, discover crash immediately when launched

I can't exactly remember, but I installed adwaita-qt and put it as the default in the qt5 and qt6 settings and it happened after that.
printenv output:

HOME=/home/kamion008
LANG=C.UTF-8
LOGNAME=kamion008
MAIL=/var/spool/mail/kamion008
PATH=/opt/devkitpro/tools/bin:/opt/devkitpro/tools/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/android-sdk/platform-tools:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/lib/rustup/bin:/opt/android-sdk/platform-tools
SHELL=/usr/bin/zsh
USER=kamion008
XDG_DATA_DIRS=/home/kamion008/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
XDG_RUNTIME_DIR=/run/user/1000
ORIENTATION=left
ADAPTIVE_SYNC=0
PANEL_TYPE=external
OUTPUT_CONNECTOR=*,DSI-1
CUSTOM_REFRESH_RATES=40,50,60
DRM_MODE=fixed
ENABLE_GAMESCOPE_HDR=0
GAMESCOPE_HDR_NITS=400
CLIENTCMD=steam -steamos -pipewire-dmabuf -gamepadui
GAMESCOPECMD=gamescope -H 1440 -e -f
QT_QPA_PLATFORMTHEME=qt6ct
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
DESKTOP_SESSION=gnome
DEVKITARM=/opt/devkitpro/devkitARM
DEVKITPPC=/opt/devkitpro/devkitPPC
DEVKITPRO=/opt/devkitpro
MOTD_SHOWN=pam
OLDPWD=/home/kamion008
PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket
PWD=/home/kamion008
SESSION_MANAGER=local/boh:@/tmp/.ICE-unix/1264,unix/boh:/tmp/.ICE-unix/1264
SHLVL=1
XDG_CURRENT_DESKTOP=GNOME
XDG_MENU_PREFIX=gnome-
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=GNOME
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
XDG_SESSION_TYPE=wayland
MANAGERPID=1160
INVOCATION_ID=74f32f8d56cf4b1da868ebcb442a7938
JOURNAL_STREAM=9:18454
SYSTEMD_EXEC_PID=1287
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service/memory.pressure
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
GJS_DEBUG_OUTPUT=stderr
GJS_DEBUG_TOPICS=JS ERROR;JS LOG
GNOME_SETUP_DISPLAY=:1
DISPLAY=:0
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.SAPKZ2
WAYLAND_DISPLAY=wayland-0
GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/kitty.desktop
DESKTOP_STARTUP_ID=a85bbb6d-fbc2-4252-9fff-4a144dc183d9
GIO_LAUNCHED_DESKTOP_FILE_PID=2799
KITTY_WINDOW_ID=1
TERM=xterm-kitty
COLORTERM=truecolor
KITTY_PID=2799
KITTY_PUBLIC_KEY=1:R9&@7Fl^0L@ZV^l8JecVLz_K4>)#w93iJ5Tz9tv~
TERMINFO=/usr/lib/kitty/terminfo
KITTY_INSTALLATION_DIR=/usr/lib/kitty
ZSH=/home/kamion008/.oh-my-zsh
PAGER=less
LESS=-R
LSCOLORS=Gxfxcxdxbxegedabagacad
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.7z=01;31:*.ace=01;31:*.alz=01;31:*.apk=01;31:*.arc=01;31:*.arj=01;31:*.bz=01;31:*.bz2=01;31:*.cab=01;31:*.cpio=01;31:*.crate=01;31:*.deb=01;31:*.drpm=01;31:*.dwm=01;31:*.dz=01;31:*.ear=01;31:*.egg=01;31:*.esd=01;31:*.gz=01;31:*.jar=01;31:*.lha=01;31:*.lrz=01;31:*.lz=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.lzo=01;31:*.pyz=01;31:*.rar=01;31:*.rpm=01;31:*.rz=01;31:*.sar=01;31:*.swm=01;31:*.t7z=01;31:*.tar=01;31:*.taz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tgz=01;31:*.tlz=01;31:*.txz=01;31:*.tz=01;31:*.tzo=01;31:*.tzst=01;31:*.udeb=01;31:*.war=01;31:*.whl=01;31:*.wim=01;31:*.xz=01;31:*.z=01;31:*.zip=01;31:*.zoo=01;31:*.zst=01;31:*.avif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:*~=00;90:*#=00;90:*.bak=00;90:*.crdownload=00;90:*.dpkg-dist=00;90:*.dpkg-new=00;90:*.dpkg-old=00;90:*.dpkg-tmp=00;90:*.old=00;90:*.orig=00;90:*.part=00;90:*.rej=00;90:*.rpmnew=00;90:*.rpmorig=00;90:*.rpmsave=00;90:*.swp=00;90:*.tmp=00;90:*.ucf-dist=00;90:*.ucf-new=00;90:*.ucf-old=00;90:
_=/usr/bin/printenv

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,076

Re: KDE connect, systemsettings, discover crash immediately when launched

You don't want to and should not be using qt6ct as your platform provider on KDE. Get rid of QT_QPA_PLATFORMTHEME=qt6ct and use KDE's own system settings to set a different Qt theme (and/or if you're actually using GNOME then make sure you make that environment dependent on the environment your in), and why is your XDG_SESSION_DESKTOP=GNOME when you're actually running KDE? or is that from a gnome session..

In general a lot of very random seeming environments here that I'm less then sure why they are there and where you might've picked them up to be a good idea.

Side note, but you most likely don't want C.UTF-8 as your primary language. If you "just" want english, generate the en_us locale and make it your main locale properly: https://wiki.archlinux.org/title/Locale

Kamion008

Member

Registered: 2025-01-02

Posts: 3

Re: KDE connect, systemsettings, discover crash immediately when launched

I have unset QT_QPA_PLATFORMTHEME and set english as my main language correctly, and yes, I'm using gnome right now. Still, is there a way to fix those plasma applications or I would have to reinstall arch (which I'd rather not to) to fix them?