SUMMARY Very long plasma start STEPS TO REPRODUCE Add to application startup https://imgur.com/a/obIqWpw OBSERVED RESULT https://youtu.be/OZnBPURtHAc EXPECTED RESULT That's how the plasma starts without applications in autorun https://youtu.be/BpeSP01JiAw SOFTWARE/OS VERSIONS KDENeon Plasma Version: 5.17.5 ADDITIONAL INFORMATION It seems to me a long autostart of plasma is an unacceptable behavior. She seems to be waiting when all applications from startup are launched. I think she should not do this and should start immediately.
>She seems to be waiting when all applications from startup are launched. It is deliberately. I would suggest you find out which one is slow and report it to them, it probably is a sign that they don't have X Startup ID correctly. As a workaround you can probably also disable that in the autostart .desktop file once you have identified which one is at fault.
I do not want to disable anything. I want the plasma to start first, and then the rest of the applications from autorun. This is a very simple desire.
I am happy to help you find a workaround if you find which process is responsible and upload the relevant .desktop file.
I'll try. But I have little time for such experiments.
(In reply to David Edmundson from comment #3) > I am happy to help you find a workaround if you find which process is > responsible and upload the relevant .desktop file. I did an experiment. I downloaded the applications in autorun one at a time and recorded the start time. Launch time without applications 32 seconds. Radiotray-NG 32 seconds Gxneur 32 seconds Flameshot 32 seconds Yandex.Disk indicator 32 seconds If you run these four applications together, the download will still be 32 seconds Now the following applications: MEGAsync 34 seconds Geary 37 seconds qBittorrent 44 seconds Telegram 58 seconds Download with all applications 1:57
Any ideas?
Is there anyone there?
Please include the .desktop files qBittorrent and Telegram They'll be in /etc/xdg/autostart/ or .config/autostart
While I was waiting for an answer, I added a couple more applications to autorun: syspeek 40 seconds psensor 45 seconds The total plasma start-up time is now 2 minutes. All .desktop files are located .config / autostart and only syspeek in / etc / xdg / autostart /
Created attachment 125322 [details] Telegram
Created attachment 125323 [details] qbittorrent
Created attachment 125324 [details] psensor
Created attachment 125325 [details] syspeek
What's next?
If you remove StartupNotify=true from those desktop files it shouldn't block
(In reply to David Edmundson from comment #16) > If you remove > > StartupNotify=true > > > from those desktop files it shouldn't block There is no such line in the syspeek file. And it does not work. The launch time has not changed at all, exactly 2 minutes. Do you have any other ideas?
Still relevant. Opensuse Tumbleweed, Plasma 5.25.3.
You can maybe try adding StartupNotify=false to those files to see if David's suggestion works.
(In reply to Nate Graham from comment #22) > You can maybe try adding StartupNotify=false to those files to see if > David's suggestion works. I didn't quite understand what to do. Explain in more detail please. I am still experiencing this issue.
Open those .desktop files in a text editor like Kate that can modify root-owned files, add "StartupNotify=false" on a new line, save the files, and reboot.
(In reply to Nate Graham from comment #24) > Open those .desktop files in a text editor like Kate that can modify > root-owned files, add "StartupNotify=false" on a new line, save the files, > and reboot. Should this be done with all applications in startup? Or should this be done with the applications themselves in the menu?
Let's start with just the ones David mentioned (qBittorrent and Telegram) and see what happens.
(In reply to Nate Graham from comment #26) > Let's start with just the ones David mentioned (qBittorrent and Telegram) > and see what happens. I still didn't understand. Should this be done at startup? Or in the general menu? By the way, I removed qbittorrent from startup a long time ago. In general, the composition of autoload has changed slightly. The problem is still the same.
You would modify those apps' .desktop files now, and then reboot. The changes you made will (well, should) change how they auto-start.
(In reply to Nate Graham from comment #22) > You can maybe try adding StartupNotify=false to those files to see if > David's suggestion works. Я изменил файл appimagekit_fba9ad8d4057184072014e350c91a589-Telegram_Desktop.desktop в директории /home/kot/.config/autostart/ и ничего не изменилось при запуске системы. Проблема та же. Что я ещё должен сделать? Qbittorrent давно отключён в автозапуске.
(In reply to KOT040188 from comment #25) > (In reply to Nate Graham from comment #24) > > Open those .desktop files in a text editor like Kate that can modify > > root-owned files, add "StartupNotify=false" on a new line, save the files, > > and reboot. > > Should this be done with all applications in startup? Or should this be > done with the applications themselves in the menu? I changed the appimagekit_fba9ad8d4057184072014e350c91a589-Telegram_Desktop.desktop file in the /home/kot/.config/autostart/ directory and nothing changed when the system started. The problem is the same. What else should I do? Qbittorrent has long been disabled in autorun.
Oh it's an AppImage, interesting. I wonder if that's relevant. If you remove all AppImage-based autostart entries, does the problem go away?
(In reply to Nate Graham from comment #31) > Oh it's an AppImage, interesting. I wonder if that's relevant. If you remove > all AppImage-based autostart entries, does the problem go away? Good version, but no. In fact, when adding applications to autorun, the plasma starts slower, when removing applications, the plasma starts faster.
Plasma waits for all applications to launch and this is a problem. This should not be.