New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mouse clicking freezes when loading QSynth #2
Comments
Thanks for the report. I've been thinking about dbus and the owner of qsynth (sometimes, it seems, extra instances of dbus are spawned when the owner is not set correctly). Did you remember to replace vaughan with your username in line 10 of Linux.lua? Otherwise if you run qsynth as root (like LilyQuick runs) it might make dbus' job easier. Another possibility is it's connected somehow to this bug https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1387219 The Colemak keyboard is probably the source of weird note names. You could make an exceptions list in Auxillary_Stuff.lua (see line 191ff). I probably should document this bit better... let me know if you need help. |
If it helps, I did remember to replace Thanks. |
I replaced "vaughan" by my username. It took me a while to figure out that I have to change the input device if I want to use the Lgitech keyboard I usually connect to my Laptop when I'm at home, lily-q intercepts only one keyboard. |
Thanks for writing and sharing LilyQuick. I've installed it on Debian Stretch and I'm using XFCE and xfce4-terminal.
When I run
sudo ./lq
, I get the usual printout of note lengths. However, if Qsynth is not running I am then unable to click successfully e.g. move my terminal window or switch to another application. I can move my mouse pointer normally, however. In order to regain proper control of the mouse, I have to press Ctrl-Alt-F1 to open a terminal, useps aux
to determine the pid ofdbus-launch
and kill this process. At this point, everything seems to work as it should.(I'm getting some weird note names but I think this is a separate issue caused by the fact that I use the Colemak keyboard layout. I'll look into this.)
The text was updated successfully, but these errors were encountered: