Bug 468608 - Autostart programs do not launch on login
Summary: Autostart programs do not launch on login
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Startup process (other bugs)
Version First Reported In: 5.27.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-17 11:22 UTC by armoire.mountable405
Modified: 2023-04-24 17:09 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description armoire.mountable405 2023-04-17 11:22:48 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Add any program to Autostart.
2. Restart the session.

OBSERVED RESULT
The program doesn't launch.

EXPECTED RESULT
Program launches.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230414
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.8
Kernel Version: 6.2.9-1-default (64-bit)
Graphics Platform: Wayland
Comment 1 Nate Graham 2023-04-17 18:38:46 UTC
Can you run `kreadconfig5 --file startkderc --group General --key systemdBoot` in a terminal window and see what it says? If it says "true", then try the following:

1. Run `kwriteconfig5 --file startkderc --group General --key systemdBoot false` in a terminal window
2. reboot

If that fixes the issue, we know it's a problem with the systemd autostart stuff. Then please re-enable systemd boot by deleting the file ~/.config/startkderc, and then reboot again.

After the reboot, please run `/usr/lib/systemd/user-generators/systemd-xdg-autostart-generator` in a terminal and and paste the text that appears, if anything.

Thanks!
Comment 2 armoire.mountable405 2023-04-18 10:49:13 UTC
(In reply to Nate Graham from comment #1)
> Can you run `kreadconfig5 --file startkderc --group General --key
> systemdBoot` in a terminal window and see what it says? If it says "true",
> then try the following:
> 
> 1. Run `kwriteconfig5 --file startkderc --group General --key systemdBoot
> false` in a terminal window
> 2. reboot
> 
> If that fixes the issue, we know it's a problem with the systemd autostart
> stuff. Then please re-enable systemd boot by deleting the file
> ~/.config/startkderc, and then reboot again.
> 
> After the reboot, please run
> `/usr/lib/systemd/user-generators/systemd-xdg-autostart-generator` in a
> terminal and and paste the text that appears, if anything.
> 
> Thanks!

`kreadconfig5 --file startkderc --group General --key systemdBoot` says nothing.
Comment 3 Nate Graham 2023-04-18 15:21:42 UTC
Ok cool, that also means it's turned on, which is what I suspected, but I wanted to make sure. Can you go through the steps I indicated?
Comment 4 armoire.mountable405 2023-04-19 16:37:21 UTC
(In reply to Nate Graham from comment #3)
> Ok cool, that also means it's turned on, which is what I suspected, but I
> wanted to make sure. Can you go through the steps I indicated?

Thank you. `kwriteconfig5 --file startkderc --group General --key systemdBoot false` made the system not start plasma shell after login. 

`/usr/lib/systemd/user-generators/systemd-xdg-autostart-generator` says `This program takes one or three arguments.`
Comment 5 Nate Graham 2023-04-20 15:40:18 UTC
(In reply to armoire.mountable405 from comment #4)
> (In reply to Nate Graham from comment #3)
> > Ok cool, that also means it's turned on, which is what I suspected, but I
> > wanted to make sure. Can you go through the steps I indicated?
> 
> Thank you. `kwriteconfig5 --file startkderc --group General --key
> systemdBoot false` made the system not start plasma shell after login. 
Heh ok then let's not go down that path anymore. :) I'm pretty sure this is an issue that only appears with the systemd boot anyway.

> `/usr/lib/systemd/user-generators/systemd-xdg-autostart-generator` says
> `This program takes one or three arguments.`
Hmm, that's odd. Can you paste the entire contents of the terminal window?
Comment 6 armoire.mountable405 2023-04-23 09:50:24 UTC
(In reply to Nate Graham from comment #5)
> Hmm, that's odd. Can you paste the entire contents of the terminal window?

AUDIODRIVER pulseaudio
BUN_INSTALL /home/user/.bun
COLORFGBG '15;0'
COLORTERM truecolor
CONFIG_SITE /usr/share/site/x86_64-pc-linux-gnu
CPU x86_64
CSHEDIT emacs
DBUS_SESSION_BUS_ADDRESS unix:path=/run/user/1000/bus
DEBUGINFOD_URLS https://debuginfod.opensuse.org/
DESKTOP_SESSION /usr/share/wayland-sessions/plasmawayland
DISPLAY :1
FROM_HEADER
GPG_TTY
GUESTFISH_INIT \\e\[1\;34m
GUESTFISH_OUTPUT \\e\[0m
GUESTFISH_PS1 \\\[\\e\[1\;32m\\\]\>\<fs\>\\\[\\e\[0\;31m\\\]
GUESTFISH_RESTORE \\e\[0m
G_BROKEN_FILENAMES 1
G_FILENAME_ENCODING @locale,UTF-8,ISO-8859-15,CP1252
HISTSIZE 1000
HOME /home/user
HOST localhost.localdomain
HOSTNAME localhost.localdomain
HOSTTYPE x86_64
INVOCATION_ID e7c51e9cad54422e9e1c32e8086cef1f
JAVA_BINDIR /usr/lib64/jvm/jre-openjdk/bin
JAVA_HOME /usr/lib64/jvm/jre-openjdk
JAVA_ROOT /usr/lib64/jvm/jre-openjdk
JOURNAL_STREAM 8:167052
JRE_HOME /usr/lib64/jvm/java-11-openjdk-11
KDE_APPLICATIONS_AS_SCOPE 1
KDE_FULL_SESSION true
KDE_SESSION_UID 1000
KDE_SESSION_VERSION 5
KGLOBALACCELD_PLATFORM org.kde.kwin
KONSOLE_DBUS_SERVICE :1.256
KONSOLE_DBUS_SESSION /Sessions/1
KONSOLE_DBUS_WINDOW /Windows/1
KONSOLE_VERSION 230400
KWIN_RESTART_COUNT 1
LANG en_BW.UTF-8
LANGUAGE en_GB:en_GB
LC_TIME en_GB.UTF-8
LESS '-M -I -R'
LESSCLOSE 'lessclose.sh %s %s'
LESSKEY /usr/etc/lesskey.bin
LESSOPEN 'lessopen.sh %s'
LESS_ADVANCED_PREPROCESSOR no
LOGNAME user
MACHTYPE x86_64-suse-linux
MAIL /var/mail/user
MANAGERPID 2102
MANPATH '/usr/local/man'  '/usr/local/share/man'  '/usr/share/man'
MANPATHISSET yes
MINICOM '-c on'
MORE -sl
MOZ_GMP_PATH /usr/lib64/mozilla/plugins/gmp-gmpopenh264/system-installed
OMF_CONFIG /home/user/.config/omf
OMF_PATH /home/user/.local/share/omf
OSTYPE linux
PAGER less
PAM_KWALLET5_LOGIN /run/user/1000/kwallet5.socket
PATH '/home/user/.local/share/fnm'  '/home/user/.bun/bin'  '/home…
PLASMA_USE_QT_SCALING 1
PROFILEHOME
PROFILEREAD true
PWD /home/user
PYTHONSTARTUP /etc/pythonstart
QEMU_AUDIO_DRV pa
QSG_RENDER_LOOP basic
QT_AUTO_SCREEN_SCALE_FACTOR 0
QT_QPA_PLATFORMTHEME qt6ct
QT_WAYLAND_FORCE_DPI 96
SHELL /bin/bash
SHELL_SESSION_ID 3c81584a7e6948a3a6a7981cde6664ab
SHLVL 1
SYSTEMD_EXEC_PID 6783
TERM xterm-256color
USER user
VENDOR suse
WAYLAND_DISPLAY wayland-0
WINDOWID 1
WINDOWMANAGER /usr/bin/startplasma-x11
XAUTHLOCALHOSTNAME localhost.localdomain
XAUTHORITY /run/user/1000/xauth_zlIRvu
XCURSOR_SIZE 24
XCURSOR_THEME Tela-dark
XDG_ACTIVATION_TOKEN kwin-10
XDG_CONFIG_DIRS /home/user/.config/kdedefaults:/etc/xdg:/usr/local/etc/xdg:/…
XDG_CURRENT_DESKTOP KDE
XDG_DATA_DIRS '/home/user/.local/share/flatpak/exports/share'  '/var/lib/f…
XDG_RUNTIME_DIR /run/user/1000
XDG_SEAT seat0
XDG_SEAT_PATH /org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS user
XDG_SESSION_DESKTOP KDE
XDG_SESSION_ID 9
XDG_SESSION_PATH /org/freedesktop/DisplayManager/Session2
XDG_SESSION_TYPE wayland
XDG_VTNR 2
XKB_DEFAULT_LAYOUT gb
XKB_DEFAULT_MODEL microsoftpro
XKB_DEFAULT_OPTIONS terminate:ctrl_alt_bksp
XKB_DEFAULT_VARIANT ,winkeys
XKEYSYMDB /usr/X11R6/lib/X11/XKeysymDB
XNLSPATH /usr/share/X11/nls
user@localhost ~ 
❯ /usr/lib/systemd/user-generators/systemd-xdg-autostart-generator                          11:48:18
This program takes one or three arguments.
user@localhost ~ [234]
❯                                                                                           11:48:20
Comment 7 armoire.mountable405 2023-04-24 10:18:54 UTC
It appears that the problem is within kded5. For some reason, it doesn't start automatically, but I can type `kded 5` into the terminal and it would run fine.
Comment 8 armoire.mountable405 2023-04-24 10:36:02 UTC
The logs for kded5.service:

Apr 24 12:14:19 localhost.localdomain systemd[1]: Started KDE Daemon.
Apr 24 12:14:19 localhost.localdomain kded5[6541]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Apr 24 12:14:19 localhost.localdomain kded5[6541]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                                   
                                                   Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Apr 24 12:14:19 localhost.localdomain systemd[1]: kded5.service: Main process exited, code=exited, status=1/FAILURE
Apr 24 12:14:19 localhost.localdomain systemd[1]: kded5.service: Failed with result 'exit-code'.
Apr 24 12:33:54 localhost.localdomain systemd[1]: Started KDE Daemon.
Apr 24 12:33:54 localhost.localdomain kded5[9662]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Apr 24 12:33:54 localhost.localdomain kded5[9662]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Comment 9 Nate Graham 2023-04-24 17:09:22 UTC
Aha, it all makes sense now.

This will be most likely caused by a distro packaging or setup issue rather than a code bug. I would recommend following up upstream with your distro, either in an openSUSE forum or a bug report at https://bugzilla.opensuse.org.