Closed FrauH0lle closed 3 years ago
I have the same issue on kubuntu.
I think it tries to get some of the colors from the global theme.. And I don't think it has a fallback, if it can not be found..
A small update:
I was curious a and tested v.0.8 and indeed, it does work on openSUSE leap 15.2. Consequently, I did a git bisect and it appears that the last working commit is 71f090f8f331f2f12532fae7ed21a36f987e1891 and from c1c3d2ff889812137424dc2b4731aec1d563ebe3 onwards it does not work.
The above mentioned errors about the colors are still present even if the script is working and thus, I think they are not related to the issue here.
Same issue on Manjaro KDE using hotkey or screen edges (https://store.kde.org/p/1372470/).
KDE Plasma version: 5.20.4 KDE-Frameworks version: 5.77.0 Qt version: 5.15.2 Kernel version: 5.10.1-5-MANJARO
Thanks for the info, I'm looking for the solution.
some pseudocode:
myColor = rgb(1,2,3) // default fallback color
try { myColor = someColorFromGlobalTheme } catch{}
I guess it will fail safely
I'll insert your failsafe version for the color issue. But a user in reddit (https://www.reddit.com/r/kde/comments/kftis5/parachute_kwin_script_version_090/ggo7fzc?utm_source=share&utm_medium=web2x&context=3) fixed this temporarily and still Parachute didn't run.
Same issue on Manjaro KDE using hotkey or screen edges (https://store.kde.org/p/1372470/).
I am also running Manjaro in a VM. How strange is that?
Same issue on Manjaro KDE using hotkey or screen edges (https://store.kde.org/p/1372470/).
I am also running Manjaro in a VM. How strange is that?
I'm on the testing branch, maybe you're on stable? There's a difference in plasma versions (no difference in qt5-base):
plasma-desktop repository : extra Stable : 5.20.4-1 Testing : 5.20.4-2 Unstable : 5.20.4-2
plasma-framework repository : extra Stable : 5.76.0-1 Testing : 5.77.0-2 Unstable : 5.77.0-2
I'm on the testing branch, maybe you're on stable? There's a difference in plasma versions (no difference in qt5-base):
No, I'm also on testing.
Have you tried to correct the color issue? I'm thinking it's two different issues here.
Ok, I discovered what it was: I was using kwinft-beta
and kdisplay-beta
... I forgot about that. My apologies...
Switching back to kwin
and kscreen
, everything works fine now. :) Thanks for the script, it's much faster here than the previous version. :)
Sorry for the hassle.
Ok, I discovered what it was: I was using
kwinft-beta
andkdisplay-beta
... I forgot about that. My apologies...Switching back to
kwin
andkscreen
, everything works fine now. :) Thanks for the script, it's much faster here than the previous version. :)Sorry for the hassle.
No problem.
For those who still can't run the script, can you see if the milou package is installed? This is a dependency of version 0.9 that didn't exist in 0.8.
milou package - how to install?
Using the package manager of your distribution. For example, pacman -S milou
for Arch based distro.
Same here, kubuntu 20.10. I checked and milou is already installed. Tried qdbus org.kde.kglobalaccel /component/kwin invokeShortcut Parachute in terminal, nothing happens. Tried installing through command line, and through kde store (purging all parachute related files between installs).
Similar to #26 , invoking the script via hotkey or terminal does not have any effect. Also there is no output in the terminal which could give a hint.
This happens on Solus with
and on openSUSE Leap 15.2 (running in a Virtualbox VM)
However, the script does work Fedora 33 and openSUSE Tumbleweed (both tested in a VM). Tumbleweed and Fedora have the same or similar Qt and Plasma versions as Solus.
Installing via the KDE store or from Github with the given instructions does not make a difference.
Restarting kwin with
kwin_x11 --replace &
only gives a small error on openSUSE eventhough I think these are not related to the problem:Is there anything I could do to get more information on what is going wrong?