Bug 485578

Summary: /etc/xdg/autostart/klipper.desktop is obsolete or refers to wrong command
Product: [KDE Neon] neon Reporter: Malte S. Stretz <mss>
Component: Packages User EditionAssignee: Neon Bugs <neon-bugs-null>
Status: RESOLVED FIXED    
Severity: minor CC: jr, neon-bugs-null
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Malte S. Stretz 2024-04-15 08:41:13 UTC
SUMMARY
I am not sure if this is a packaging bug so I file it against Neon. Feel free to move it to the proper product.

When I looked at some other issue I found these lines in my journal:
> Apr 15 09:12:48 slpn-nb-mss systemd-xdg-autostart-generator[1178]: Exec binary 'klipper' does not exist: No such file or directory
> Apr 15 09:12:48 slpn-nb-mss systemd-xdg-autostart-generator[1178]: Not generating service for XDG autostart app-klipper@autostart.service, error parsing Exec= line: No such file or directory

The file /etc/xdg/autostart/klipper.desktop is provided by the plasma-workspace package which sounds wrong. Maybe a leftover from Plasma 5?

I do have a working clipboard management icon in the tray area or whatever it is called nowadays. But sounds like that one is not called Klipper anymore? At least there is no klipper binary to be found and no package called klipper available.

STEPS TO REPRODUCE
1. journalctl --user | grep klipper

OBSERVED RESULT
Error about an invalid klipper autostart entry.

EXPECTED RESULT
No such error.


SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-27-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz
Memory: 19,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: LENOVO
Product Name: 20F9CTO1WW
System Version: ThinkPad T460s

ADDITIONAL INFORMATION
Comment 1 Malte S. Stretz 2024-06-30 17:18:19 UTC
This seems to be fixed in the current packages.