ROSA Linux Bugzilla – Bug 1140
kde4-firstsetup.sh runs every time I boot
Last modified: 2014-09-04 11:23:34 MSD
Description of problem:
I suppose that kde4-firstsetup.sh script should be run only 1 time, after that I suppose that it should be removed or disabled. Maybe it is one of the several factors because of which KDE starts so long.
Steps to Reproduce:
1. Open folder XDG_DOWNLOADS_DIR. See a PDF file "Welcome.pdf". Remove it.
2. Log out and login and open folder XDG_DOWNLOADS_DIR again. You will see
a link to Welcome.pdf, because it will be created by kde4-firstsetup.sh again.
I suppose this is a blocker?
Not sure if this is a blocker, since it may be an expected behaviour. The fact that we did not know about it does not change it )
Feel free to change severity of this bug if you think different. But, because we creating a link in the XDG_DOWNLOADS_DIR to a PDF document now, it may annoying users. :)
I've added FirstRun parameter to the global KDE config file ($HOME/.kde/share/config/kdeglobals) in the Mandriva group. Now script checks this parameter and creates link to StackFolder documentation only once.
You can use this parameter for checking another actions of script.
I suggest to use this parameter not only for our sub-script in kde4-firstrun, but for this script.
This script reset XDG environments. It's need not only in first run, but every time for set properly path. If we drop it, works in parallel session in other DE may broke KDE4 XDG settings.
Script works quickly and not able increase boot time (0.5 sec max).
So, please rename it for understanding in a future.
This should be fixed but only after all stuff from this sh script that *must* be executed each time is moved to another package.
Well, I tried to remove this script and my system works perfectly without this script. So....
i guess you are right, but noone else tested it =) Are we ready to take risk and remove it ?
No, but I suggest to test this variant widely. If we'll find that everything will work (and I practically sure that everything will work) we can fix this bug in RP1.