Hide Forgot
Description of problem: I think that line 163 in the startkde script is sourcing the .../env/ scripts in the incorrect order. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: Actual results: Expected results: Additional info: Line 163 currently reads: qtpaths --paths ConfigLocation | tr ':' '\n' | sed 's,$,/plasma-workspace,g' The paths so generate are source in a loop: for prefix in `echo $scriptpath`; do for file in "$prefix"/env/*.sh; do test -r "$file" && . "$file" || true done done But, on my system, the line at 163 produces: $ qtpaths --paths ConfigLocation | tr ':' '\n' | sed 's,$,/plasma-workspace,g' /home/Peter/.config/plasma-workspace /etc/xdg/plasma-workspace Thus any default setting in the /etc/xdg/ file will override any setting in my local configuration file. If the order in which the qtpaths command returns the files is fixed, then changing line 163 to read: qtpaths --paths ConfigLocation | tr ':' '\n' | tac - | sed 's,$,/plasma-workspace,g' would, I believe, fix the problem.
Yes, that's by design, NOTABUG If you want different behavior, write your source'd env files to accomodate it.
Or more specifically, if you want to get upstream involved to convince them to change behavior (@bugs.kde.org or mailing lists or whatever0, that's fine too, but we won't change it downstream in fedora only.