Bug 416265

Summary: Very long Plasma launch time when autostarting various apps
Product: [Plasma] plasmashell Reporter: KOT040188
Component: Startup processAssignee: David Edmundson <kde>
Status: REPORTED ---    
Severity: normal CC: kde, nate, plasma-bugs, postix
Priority: NOR    
Version: 5.17.5   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=473860
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Telegram
qbittorrent
psensor
syspeek

Description KOT040188 2020-01-14 21:05:30 UTC
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.
Comment 1 David Edmundson 2020-01-14 21:08:25 UTC
>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.
Comment 2 KOT040188 2020-01-14 21:14:35 UTC
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.
Comment 3 David Edmundson 2020-01-14 21:17:53 UTC
I am happy to help you find a workaround if you find which process is responsible and upload the relevant .desktop file.
Comment 4 KOT040188 2020-01-14 21:21:57 UTC
I'll try. But I have little time for such experiments.
Comment 5 KOT040188 2020-01-15 21:20:02 UTC
(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
Comment 6 KOT040188 2020-01-17 20:53:32 UTC
Any ideas?
Comment 7 KOT040188 2020-01-22 23:44:44 UTC
Is there anyone there?
Comment 8 David Edmundson 2020-01-23 00:28:20 UTC
Please include the .desktop files qBittorrent and Telegram 


They'll be in /etc/xdg/autostart/
or .config/autostart
Comment 9 KOT040188 2020-01-23 13:51:58 UTC
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 /
Comment 10 KOT040188 2020-01-23 13:53:52 UTC
Created attachment 125322 [details]
Telegram
Comment 11 KOT040188 2020-01-23 13:54:31 UTC
Created attachment 125323 [details]
qbittorrent
Comment 12 KOT040188 2020-01-23 13:55:00 UTC
Created attachment 125324 [details]
psensor
Comment 13 KOT040188 2020-01-23 13:56:08 UTC
Created attachment 125325 [details]
syspeek
Comment 14 KOT040188 2020-01-25 11:56:47 UTC
What's next?
Comment 15 KOT040188 2020-01-28 16:37:48 UTC
Is there anyone there?
Comment 16 David Edmundson 2020-01-28 16:39:36 UTC
If you remove

StartupNotify=true


from those desktop files it shouldn't block
Comment 17 KOT040188 2020-02-01 18:00:42 UTC
(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?
Comment 18 KOT040188 2020-02-06 18:51:37 UTC
What's next?
Comment 19 KOT040188 2020-02-08 20:05:00 UTC
Any ideas?
Comment 20 KOT040188 2020-02-15 12:27:39 UTC
Is there anyone there?
Comment 21 KOT040188 2022-07-27 18:41:11 UTC
Still relevant. Opensuse Tumbleweed, Plasma 5.25.3.
Comment 22 Nate Graham 2023-04-27 21:17:20 UTC
You can maybe try adding StartupNotify=false to those files to see if David's suggestion works.
Comment 23 KOT040188 2023-04-27 21:51:11 UTC
(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.
Comment 24 Nate Graham 2023-04-28 17:57:16 UTC
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.
Comment 25 KOT040188 2023-04-28 18:17:09 UTC
(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?
Comment 26 Nate Graham 2023-04-28 18:21:27 UTC
Let's start with just the ones David mentioned (qBittorrent and Telegram) and see what happens.
Comment 27 KOT040188 2023-04-28 18:27:58 UTC
(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.
Comment 28 Nate Graham 2023-04-28 18:31:06 UTC
You would modify those apps' .desktop files now, and then reboot. The changes you made will (well, should) change how they auto-start.
Comment 29 KOT040188 2023-04-28 19:06:29 UTC
(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 давно отключён в автозапуске.
Comment 30 KOT040188 2023-04-28 19:07:34 UTC
(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.
Comment 31 Nate Graham 2023-05-01 20:02:10 UTC
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?
Comment 32 KOT040188 2023-05-02 17:59:22 UTC
(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.
Comment 33 KOT040188 2023-05-02 18:01:01 UTC
Plasma waits for all applications to launch and this is a problem. This should not be.