Tnanks for your response! Glad to hear that my problem is not only mine. About the issue. I have several physical boxes with different proc/mem/etc but all running Kubuntu 20.04 (with KDE atop, minimal install). All of them behave in the same manner.
I do always install pyenv, recent python (3.9 in this case) and leo from git. So I first encountered the issue on this setup. Then I took system python's pip (3.9.5) and installed 6.5 - same issue. Then 6.4 - no changes. And only 6.3 gave my usable setup. So now I am on 6.3 from pip with py-395. I am not sure whether pip re-installs PyQT. Hope this would help. Thanks. вт, 8 мар. 2022 г. в 00:33, [email protected] <[email protected]>: > I was posting about it around April 13, 2021: > > https://groups.google.com/g/leo-editor/c/Pf4Wh0IT6H4/m/EHJFY86VAQAJ > On Monday, March 7, 2022 at 4:24:50 PM UTC-5 [email protected] wrote: > >> It will be fixed after @Edward, myself, or someone else can reliably >> reproduce the problem. It happened to me last year - I'm sure it was the >> exact same problem since the weird symbols were the same - but for the CTRL >> key instead. That went away so I thought that it had been fixed. I know >> that it was not purely a Qt problem because I wrote a little pyqt test >> program - not running in Leo - and did not get the bad symbols. >> >> I sympathize because the program is totally unusable this way, but we've >> got to find something different about your machine/installation. >> >> I don't recall your history with this now, but are you able to install it >> without pip and try that? The best way would be to clone the git repo and >> run that. In the worst case, you could also either install a different >> version of Python, or at least create a new virtual environment to get a >> clean an install as possible. If I were doing this, I would pip-install >> some earlier version of Leo (like 6.3, maybe?) so as to get the >> dependencies installed. Then I would run the git-repo clone version. >> >> If you don't know what any of this means, someone here can walk you >> through it, I'm sure. I can tell you that I'd feel crippled if I couldn't >> use Leo any more, so I have some idea how you feel! >> >> >> On Monday, March 7, 2022 at 2:06:16 PM UTC-5 gar wrote: >> >>> Hello, the team! >>> >>> Can you please tell me what is the status of this issue? Is it going to >>> be investigated? Or you failed to reproduce it and threw it away? >>> Actually my work with leo is absolutely paralyzed. I use the win-key >>> intensively, even for a kind of alt-tab. Leo outlines become dirty even >>> when I think that I don't use it. >>> Leo's recent master suffers from it, pip's 6.5 and 6.4 too. The latest >>> version where it doesnt is 6.3. >>> >>> Maybe the best solution is to downgrade to some version where it is >>> absent and never upgrade. I agree with that too - in case this issue is not >>> going to be fixed. >>> User pbg at Dec'18 reported that he succeeded to reproduce it and >>> provided you with the trace. Is anything else needed? >>> >>> Thanks. >>> >> -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/de6cf53c-f660-4a44-9083-faac311b5553n%40googlegroups.com > <https://groups.google.com/d/msgid/leo-editor/de6cf53c-f660-4a44-9083-faac311b5553n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAC%2B8SVzW7xR%3DjQNsuPG6sc4tiPJuavNzAj3jWrYAr-jKLjRsSg%40mail.gmail.com.
