https://bugs.kde.org/show_bug.cgi?id=382604
--- Comment #27 from [email protected] --- Experimenting with environment variable XCURSOR_THEME. - Log into KDE Plasma, start Konsole - `echo $XCURSOR_THEME` shows me `KDE_Classic` (which was my cursor theme when I started) - From that konsole, `konsole &` and in that (new) konsole, `echo $XCURSOR_THEME` shows `KDE_Classic` (this is expected, environment passed on from the shell in konsole). Notice that mousing over the new konsole shows the KDE Classic cursor theme. - From that konsole, `XCURSOR_THEME=redglass konsole &` and in that konsole notice it shows redglass. Together this shows that starting Konsole from the command-line makes it obey the XCURSOR_THEME environment variable. - Use dbus to get KLauncher to launch a new konsole: `qdbus-qt5 org.kde.klauncher5 /KLauncher exec_blind konsole ""` .. notice that Konsole has XCURSOR_THEME set to `KDE_Classic` (because that's what I had when I logged in) - Use dbus to tell Klauncher to use a different environment: `qdbus-qt5 org.kde.klauncher5 /KLauncher setLaunchEnv XCURSOR_THEME Oxygen_Yellow` - Then use dbus to launch a new konsole again (same command) and notice it comes up with Oxygen Yellow as cursor theme and has XCURSOR_THEME set as expected. - Then use KRunner to start Konsole, e.g. alt-space, type "konsole". Notice it has KDE_Classic. - Then use the K-Menu to start Konsole. It too has KDE_Classic. So far, we've seen that Konsole follows the XCURSOR_THEME set in the environment when it is started. Also that KLauncher can modify the environment it uses to launch applications. Also that KRunner is not KLauncher, and uses some **other** notion of environment. (This can be similarly demonstrated by starting kwrite, changing the theme, then starting another kwrite which gets the old theme). -- You are receiving this mail because: You are watching all bug changes.
