https://bugs.kde.org/show_bug.cgi?id=490891
--- Comment #25 from René Paw Christensen <[email protected]> --- (In reply to zupnikszydlik from comment #24) > ~/.config/plasma-org.kde.plasma.desktop-appletsrc I connected to my computer with SSH, and saved "positionsB" and "positionsC" in `~/.config/plasma-org.kde.plasma.desktop-appletsrc`. They were saved/made like this: 1) Position icons, 2) Logoff, 3) From SSH copy the "positions" key/value to "positionsB/C". This was done to have the two "positionsB/C" key/value to revert back to. Now some testing: 1) * Position icons. * Logoff/on. * Turn monitor off/on. * Icons didn't move as expected. 2) * Move icons to right/bottom * Turn monitor off * Here I noticed on the SSH that the "positions" was updated. * Turn monitor on. * Icons was moved (our bug). 3) * Turn monitor off * Restore "positions" to the value when the icons were at the right/bottom (positionsB). * Turn monitor on. * Icons was moved. Here I hoped that they were moved to the right/bottom, but no such luck. 4) * Logoff * Restore "positions" to the value when the icons were at the right/bottom (positionsB). * Logon. * Icons was moved to the right/bottom. Why did 3) fail, when 4) didn't ? Probably because the configuration file is cached in memory, still saved to disk when updated in memory, but not reloaded into memory when updated on the disk. Then I thought that perhaps the issue is that the icon positions are saved when you logoff and when you turn off the monitor - and perhaps the code that saves the icon positions isn't the same - i.e. one has the bug. But no: 5) * Move icons to right/bottom * Turn monitor off * Save the "positions", which should be the buggy positions if my theory was right. * Turn monitor on, and icons was moved as expected. * Logoff. * Restore the "positions". * Logon. * Now the icons was in the right/bottom. So the positions saved when I turned off the monitor was correct - so the error must happen when the monitor is turned on. Perhaps the configuration file should be re-read into memory when changed on disk, but that is a minor "bug" (missing feature), and not the one we are chasing here. -- You are receiving this mail because: You are watching all bug changes.
