https://bugs.kde.org/show_bug.cgi?id=413645
--- Comment #35 from Duncan <1i5t5.dun...@cox.net> --- (In reply to Aaron Rainbolt from comment #34) > I can also resolve the problem by entirely removing the "ItemGeometries" > line and leaving the "ItemGeometriesHorizontal" line. However, again, this > line is recreated at login, and if left at logout, the widget will again > "wander" and then snap. So something about the two entries coexisting is > causing things to go wrong. Those floating-point values look suspect. Does manually setting them to integer values (767 and 688) help? If not or if it doesn't stick, try the following... This bug has been around awhile, but there was a workaround I initially described in https://bugs.kde.org/show_bug.cgi?id=389141 that (with a bit of updating) presumably still works (see below): With the plasmoids in the desired location (either with the ItemGeometries lines deleted or with them set as desired, not sure which), set plasma-org.kde.plasma.desktop-appletsrc (normally found in ~/.config unless you set $XDG_CONFIG_HOME) read-only. This should prevent it from being overwritten with the bad config but unfortunately you'll still need to manually restart the initially started mixed-up plasmashell (plasmashell --replace, unfortunately at each login, tho it can be scripted as described below) in ordered to get it to take, since that initial start is what goes haywire. You can try the --replace from krunner. If that works as I expect it will, automate it with a script set to autostart (see the autostart kcontrol/systemsettings module), with a few seconds sleep to let the system stabilize before the --replace command. Of course with the desktop-appletsrc file set readonly reconfiguring things will work only for that plasmshell session so you'll have to remember to toggle it back read-writable if you want to reconfigure... (I believe the bug trigger here was a multi-monitor setup with different resolutions for each monitor, one full-HD one 4K. When I upgraded to matching-resolution 4Ks it stopped triggering for me so I've not seen the bug in awhile. Thus the "presumably still works" qualification above.) -- You are receiving this mail because: You are watching all bug changes.
