https://bugs.kde.org/show_bug.cgi?id=490685
--- Comment #4 from Adam Fontenot <adam.m.fontenot+...@gmail.com> --- Okay, so I've further narrowed down the issue to a specific environment variable that triggers it. A shell started with a clean environment via `sudo -u $USER /bin/bash` didn't show the issue, but as soon as I add back the following environment variable from my real environment, it happens again. XDG_CONFIG_HOME=/home/$USER/.config/ dolphin . Vice versa, I also was able to work around the problem by starting Dolphin with a blank XDG_CONFIG_HOME variable in my normal environment. In addition, I was able to partially reproduce the issue on a different system that didn't exhibit the compositor hang by adding this environment variable. While the compositor does not clearly hang as it does on my system, I was able to reproduce the syscall spam issue. Without this specific environment variable, Dolphin issues no syscalls when its window is in the background. With it, activity from Dolphin is constant. It is very surprising to me that this can make a difference, because I would normally expect most programs to treat this directory as the configuration root by default anyway. -- You are receiving this mail because: You are watching all bug changes.
