Bug 328276

Summary:	KDE is autostarting programs that have no findable entry in any autostart location.
Product:	[Applications] systemsettings	Reporter:	SaburoutaMishima
Component:	kcm_autostart	Assignee:	Laurent Montel <montel>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kde
Priority:	NOR
Version:	4.11.3
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description SaburoutaMishima 2013-12-01 12:39:54 UTC

SMPlayer starts at login, but there is no entry for SMPlayer in KCMAutostart, and there are no SMPlayer desktop files in any of the (frankly super-numerous) startup locations, either for the user or the system.

I would really, really like to know how this is happening. KDEInit4 is listed as the parent process, so this seems to be happening inside KDE. If that is somehow not the case, this bug can be closed, but I would still appreciate any insight into how this is possible. There is also no service for smplayer in systemd.

Reproducible: Sometimes

Steps to Reproduce:
1. Install smplayer
2. Restart and observe smplayer starting at system startup
3. Observe that there is not dekstop file in an autostart locations, no entry in kcm autostart
Actual Results:  
SMPlayer starts at login.

Expected Results:  
Only programs listed in the autostart panel, or with desktop files in autostart locations, start at login.

I've looked through every installed unit file, and I can't find one that seems related to SMPlayer. Given that the parent process of SMPlayer (when it appears at system startup) is KDEInit4, those two facts together suggest to me that KDE is somehow starting it.

I also have KDE configured to start a new sessions, not restore old sessions, so that doesn't seem to be the problem.

Comment 1 David Edmundson 2015-09-26 14:17:20 UTC

can you find a reference to smplayer in any of these locations:
http://blog.davidedmundson.co.uk/node/8

if so this is a duplicate of 274920.

Otherwise reopen this, and we'll take another look.

Also can you see if it autolaunches in openbox?
If you've added this manually to .xinitrc (for example) there's not a lot we can do.

*** This bug has been marked as a duplicate of bug 274920 ***