#1014153 libqt5gui5: cannot mouse over "grouped window" set to select -- lxqt panel task manager #1014153
- Package:
- lxqt-panel
- Source:
- lxqt-panel
- Description:
- LXQt desktop panel
- Submitter:
- proctor
- Date:
- 2022-07-01 18:27:03 UTC
- Severity:
- normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
panel crashed after clicking on okular grouped set of windows.
after panel reloaded the issue manifested.
i believe the crash/reload reloaded a new version (5.15.4+dfsg-3) and
that is where i think the problem may lie.
* What exactly did you do (or not do) that was effective (or
ineffective)?
tried rebooting. (not work)
tried creating new user and logging in as them. (not work)
tried using lxde desktop environment (this works)
tried reinstalling lxqt. (not work)
* What was the outcome of this action?
none of the troubleshooting produced a postitive result.
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
this appears to be the exact same issue as reported here
https://github.com/lxqt/lxqt-panel/issues/1600
which also seems to have a patch available.
thank you very much.
Hi! Right, but that patch is for lxqt-panel, not for Qt. So reassigning the bug. The patch is https://github.com/lxqt/lxqt-panel/commit/4c674608aaaac73d and it is present in versions ≥ 0.17.0. Debian currently has 0.16.1.
thank you for your response, and sorry for the poor quality info. i wonder how i might have searched for that patch being applied to debian. i would like to add a piece of info that had originally bolstered my idea that it was libqt5gui5: at the time of the panel crash this line was written in the logs kernel: traps: *lxqt-panel*[27936] general protection fault ip:7f0c3f93f300 sp:7ffd43edba18 error:0 in* libQt5Gui.so.5.15.2* (deleted)[7f0c3f8e2000+4d0000] i believe at that time *libQt5Gui.so.5.15.2* was switched to libQt5Gui.so.5.15.4 (my guess) -- and that is also when the problem began. since qt 5.15.2 version was also referenced in the bug that i found i thought there was a reasonable chance it was related. let me know if there is anything more i can provide. i am more or less an advanced user.