Plasma autostart ignores Special Settings

English Applications
1

I want to have xosview(1) in the lower right corner of my desktop.
I started it and placed it in the lower right corner. I also arranged for proper size.
Then I edited “Application-Specific Settings” for xosview.
I set “Position Apply initialy xxx,yyy” and “Size Apply Initialy xx,yy”.
Killing xosview and restarting it makes it appear always at the correct location.
BUT
Starting it via autostart (System Settings -> Workspace -> Startup and Shutdown -> Autostart -> Add Program/Script) places xosview in the upper left corner.

Workaround:
Autostarting xosview with a delay of ~5sec (sh -c “sleep 5 && exec xosview”) solves that misbehavior.

What is the correct way to start e.g. xosview and have it controlled by the Settings attributes?
The shown workaround can’t be the official solution.

Any hint for me?
Regards

2

Unfortunately, your solution may well be the only feasible one:

  • When applications are auto-started, the only choices are “Before session startup
    ” and “Startup” (and, also “Shutdown” – not relevant here); - The problem with “Startup” is, there’s no guarantee that, Plasma will be full initialised before the application is started;
  • “xosview” is a pure
    X11 application; - Therefore, your solution is correct – all the Plasma resources which an X11 application will use, have to be correctly initialised before, the X11 application is started.
3

@ dcurtisfra
Isn’t it an issue or even a bug if it is not the same result whether I start an app with autostart or via launcher?
I for myself expect the identical result.

@all
Where should I report/discuss this issue with the goal to change the behavior of autostart?
To play with “sleep …” is not a high sophisticated solution.
It depends too much on the power of the computer.

regards

4

I guess you could open a bug report at bugs.kde.org.

5

I disagree.

  • Please take a look at the C system library section related to time keeping.
  • There are mechanisms in the Linux and UNIX® kernels related to time-keeping and timers.
  • Bash “Sleeping” actually relies on a timer function within the Linux and UNIX[SUB]®[/SUB] kernels …
  • “Real-Time” applications rely on accurate time-keeping and timer functions (“sleeping”) to ensure reliable operation …
  • “Sleeping” as such «at a program level», doesn’t continually consume CPU cycles. – Programs which continuously loop rather than using a systems time-keeping functionality do continually consume CPU cycles …