https://bugs.kde.org/show_bug.cgi?id=360430
--- Comment #5 from Bernd Steinhauser <li...@bernd-steinhauser.de> --- As I don't see this every time, I guess there is a race going on. To me, it looks like kscreen tries to look for a config, when some daemon or backend is sometimes not available to retrieve the config (e.g. kded or kdeinit). Then it tries a best guess at the screen config and writes that config to disk (at that time, the backend/daemon/whatever would be available, because it happens a bit later). Since I'm not good at understanding c++ and since I don't know kscreen in detail, that's just speculation. However, I remember from times where loading a config was successful, that there are lines in the log telling you that it found a config and tries to apply that. When the config gets rewritten, I can't find such lines in the log, but there aren't logs about something failing either. Other than the lines about some xrandr, but iirc that's normal (since there are multiple ones). -- You are receiving this mail because: You are watching all bug changes.
