SUMMARY At login skype does not start STEPS TO REPRODUCE 1. ask for Skype to autostart at login 2. go to kde settings autostart 3. check that skype is well added in autostart 4. Restart the PC then login OBSERVED RESULT Skype does not start EXPECTED RESULT Skype starts SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20221111 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 KDE GEARS 22.08.3 ADDITIONAL INFORMATION No problem till yesterday
About some months ago, I got a similar problem with the scripts.
Can you run `/usr/lib/systemd/user-generators/systemd-xdg-autostart-generator` in a terminal window and paste the output here?
x@y:~> /usr/lib/systemd/user-generators/systemd-xdg-autostart-generator x@y:~>
Ok, that seems fine. Can you paste the contents of the desktop file for Skype's autostart entry?
Created attachment 153771 [details] desktop file for Skype's autostart entry
Sounds like https://bugs.kde.org/show_bug.cgi?id=433299
That was traced to https://github.com/systemd/systemd/pull/18782 which was merged, though. The desktop file looks sane to me. It does have "X-GNOME-Autostart-enabled" in it, but that's not quite the same as "X-GNOME-Autostart-Phase" which systemd is known to have issues with (see https://github.com/systemd/systemd/issues/18791). Out of curiosity though, does it start working if you edit the file to remove the "X-GNOME-Autostart-enabled=true" line?
>> Out of curiosity though, does it start working if you edit the file to remove the "X-GNOME-Autostart-enabled=true" line? It fails. There was no problem for many years. Suddenly it fails.
Created attachment 153791 [details] packges updated at 2022/11/15 1
Created attachment 153792 [details] packges updated at 2022/11/15 2
Created attachment 153793 [details] packges updated at 2022/11/15 3
Created attachment 153794 [details] packges updated at 2022/11/15 4
Created attachment 153795 [details] packges updated at 2022/11/15 5
Created attachment 153796 [details] packges updated at 2022/11/15 6
Today 2022/11/16, no more problem ! See the list of the packages updated at 2022/11/15
Cool, thanks. Seems like it wasn't a KDE bug.
Yesterday 2022-11-16 there was an update to KDE frameworks 5.100.0. The problem reappeared this morning.
Created attachment 153825 [details] packages updated at 202-11-16 1
Created attachment 153826 [details] packages updated at 202-11-16 2
Created attachment 153827 [details] packages updated at 202-11-16 3
Created attachment 153828 [details] packages updated at 202-11-16 4
Created attachment 153829 [details] packages updated at 202-11-16 5
Created attachment 153830 [details] packages updated at 202-11-16 6
Created attachment 153831 [details] packages updated at 202-11-16 7
It's extremely unlikely that the frameworks update changed anything here
Ok, but there were also other packages. xembedsniproxy 5.26.3 gmenudbusmenuproxy 5.26.3 plasma5-workspace-libs 5.26.3 plasma5-workspace 5.26.3 plasma5-workspace-lang 5.26.3 plasma5-session 5.26.3 plasma5-session-wayland 5.26.3 gtk4-schema 4.8.2 libgtk-4.1 4.8.2 gtk4tools 4.8.2 gtk4-lang 4.8.2 libLLVM15 15.0.4 libLLVM15-32bit 15.0.4 libavif15 0.11.1 libavif15-32bit 0.11.1 libexiv2-27 0.27.5 libtiff5 4.4.0 libtiff5-32bit 4.4.0 libtiff-devel 4.4.0 python310-setuptools 65.5.1 wireless-regdb 20221012
Can you run this command: kwriteconfig5 --file startkderc --group General --key systemdBoot false Then reboot, and see if Skype autostarts as expected.
I didn't use "kwriteconfig5 --file startkderc --group General --key systemdBoot false" I just waited. Result : one week without any problem. Hypothesis: some process launched by sytemd or kde login disturbs skype launching. If I encounter a problem I will use "kwriteconfig5 --file startkderc --group General --key systemdBoot false"
Also randomly a script launching fails. Script is well launching but does not finish its starting. I must kill it, then launch it again. Here is the script ************************************************************************************************ #!/bin/bash sleep 10s bash -c '/usr/bin/google-chrome-stable --profile-directory=Default --app-id=celnaknmndcdcjcagffhbhciignkeokb &' while [ true ] do sleep 5 status=$(wmctrl -l | grep "Facebook") if [ "$status" != "" ] ; then break fi done WID="$(wmctrl -lx | grep "Facebook")"; kdocker -qtw "${WID%% *}" -i ~/.local/share/icons/hicolor/32x32/apps/chrome-celnaknmndcdcjcagffhbhciignkeokb-Default.png & ********************************************************************************************************
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
i supplied the requested info.
First we need the name of the generated service. Pleas run `ls $XDG_RUNTIME_DIR/systemd/generator.late/*skype*` in a terminal window, which will tell you the name of the systemd service for Skype's autostart entry. Then run `systemctl status --user [service name]` and paste the contents here. Also can you paste the output of `cat $XDG_RUNTIME_DIR/systemd/generator.late/*skype*`? It might help to see the generated systemd service's contents too.
:~> ls $XDG_RUNTIME_DIR/systemd/generator.late/*skype* /run/user/1001/systemd/generator.late/app-skypeforlinux@autostart.service :~> systemctl status --user app-skypeforlinux@autostart.serviceWarning: The unit file, source configuration file or drop-ins of app-skypeforli> ● app-skypeforlinux@autostart.service - Skype for Linux Loaded: loaded (/home/roubach/.config/autostart/skypeforlinux.desktop; gen> Active: active (running) since Thu 2022-12-15 07:47:31 CET; 20min ago Docs: man:systemd-xdg-autostart-generator(8) Process: 2555 ExecStart=/usr/bin/skypeforlinux (code=exited, status=0/SUCCE> Main PID: 2555 (code=exited, status=0/SUCCESS) Tasks: 72 (limit: 4915) Memory: 481.0M CPU: 13.257s CGroup: /user.slice/user-1001.slice/user@1001.service/app.slice/app-skypef> ├─2577 "/usr/share/skypeforlinux/skypeforlinux --executed-from=/ho> ├─2606 "/usr/share/skypeforlinux/skypeforlinux --type=zygote --no-> ├─2607 "/usr/share/skypeforlinux/skypeforlinux --type=zygote --ena> ├─2609 "/usr/share/skypeforlinux/skypeforlinux --type=zygote --ena> ├─2656 /usr/share/skypeforlinux/chrome_crashpad_handler --monitor-> ├─2727 "/usr/share/skypeforlinux/skypeforlinux --type=gpu-process > ├─2739 "/usr/share/skypeforlinux/skypeforlinux --type=utility --ut> └─2796 "/usr/share/skypeforlinux/skypeforlinux --type=renderer --e>
That's odd. It definitely looks like it's running. what does `ps -e | grep -i skype` show?
:~> ps -e | grep -i skype 2577 ? 00:01:08 skypeforlinux 2606 ? 00:00:00 skypeforlinux 2607 ? 00:00:00 skypeforlinux 2609 ? 00:00:00 skypeforlinux 2727 ? 00:03:58 skypeforlinux 2739 ? 00:00:37 skypeforlinux 2796 ? 00:21:39 skypeforlinux 21585 ? 00:00:01 skypeforlinux
Ok, so Skype is fact running. What exactly is the problem?
Skype randomly does not autostart.
When you ran the `ps` command I asked for, Skype was running and you could interact with it? Or it was running, but it showed no interactive UI?
Randomly Skype is not launched. Skype is not running. Skype is not in the process list.
(In reply to Nate Graham from comment #38) > When you ran the `ps` command I asked for, Skype was running and you could > interact with it? Or it was running, but it showed no interactive UI? I need an answer to this question that I just asked, please.
If you execute "ps -e | grep -i skype" then you get nothing.
But in comment 35, you showed the opposite. I'm very confused now.
Today, Skype is launched with succes by the kde autostart function. Randomly, it is not autostarted.
Ok. I think this is beyond by debugging ability at this point.
> Can you run `/usr/lib/systemd/user-generators/systemd-xdg-autostart-generator` in a terminal window and paste the output here? Problem is that it's output goes straight to the journal (at least on my system). SYSTEMD_LOG_LEVEL=debug might also be useful. See also https://www.freedesktop.org/software/systemd/man/systemd.generator.html example 3 At first I suspected X-GNOME-Autostart-enabled=true interfering but that isn't the case.
In the past I sent a report about, with openSUSE Argon 19.3, suddenly all apps [*] and my 4 scripts fails to autostart, definitively. Nobody found any solution, then I switched to openSUSE tumbleweed to get a kde autostart running well. [*] I checked with other app than Skype like VLC, etc.
>then I switched to openSUSE tumbleweed to get a kde autostart running well. and there it worked?
And in particular, do they disable the systemd boot feature by default? That could explain the differences.
(In reply to Nate Graham from comment #48) > And in particular, do they disable the systemd boot feature by default? That > could explain the differences. No, systemd boot is enabled.
(In reply to David Edmundson from comment #47) > >then I switched to openSUSE tumbleweed to get a kde autostart running well. > > > and there it worked? it works better but not well. that's why i sent this report
Sounds like maybe Tumbleweed ships a newer Systemd version which fixed this issue?
the systemd update date is 2023/01/30 and version is 252.5. i don't know of the issue is fixed.
(In reply to Philippe ROUBACH from comment #53) > the systemd update date is 2023/01/30 and version is 252.5. Thanks. > i don't know of the issue is fixed. Well is it still happening or not? :)
>> Well is it still happening or not? It's a random issue.
So sometimes when you boot up the system Skype autostarts, and sometimes it doesn't?
(In reply to Nate Graham from comment #56) > So sometimes when you boot up the system Skype autostarts, and sometimes it > doesn't? Yes, skype or a script.
I get 2 times the problem. Problem not solved.
On my side, any custom .sh script added to "Startup and Shutdown > Autostart" doesn't work either. It happens all the time, but I found this issue and didn't want to create another one. For example, if one creates a custom .sh script with content: #!/bin/sh # Run Terminal /usr/bin/konsole & the console will appear and close immediately. The issue appeared a couple of months ago for the first time. Before that everything worked correctly for years.
MitraX, that's something else. The fact that Konsole runs at all means that it *is* autostarting, it's just not doing what you expect it to do once it launches. Maybe it's crashing, maybe something else is happening. But it's not related to the issue described in this bug report, so please submit a new bug report for it if you suspect that there's a KDE code bug involved.
(In reply to MitraX from comment #59) > On my side, any custom .sh script added to "Startup and Shutdown > > Autostart" doesn't work either. It happens all the time, but I found this > issue and didn't want to create another one. > > For example, if one creates a custom .sh script with content: > > #!/bin/sh > # Run Terminal > /usr/bin/konsole & > > the console will appear and close immediately. > > The issue appeared a couple of months ago for the first time. Before that > everything worked correctly for years. That means your systemd is too old and kills background processes of autostarted applications. You need https://github.com/systemd/systemd/pull/20813
I forget to indicate that I sent a report to openSUSE team. https://bugzilla.opensuse.org/show_bug.cgi?id=1200141
randomly also kontact does not start ! kontact is not in "autostart" in the contrary of skype and scripts.
Unfortunately nobody has been able to reproduce the issue, and we haven't gotten any other reports of this happening, so I'm afraid there isn't much we can do about it, sorry. I'd recommend following up with your distro for further support.