-
Notifications
You must be signed in to change notification settings - Fork 135
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
Panel spams system log in an infinite loop freezing the system #2044
Comments
Not reproducible, of course. Which WM do you use? |
DE: lxqt-session |
I also use kwin 6.0.2 but with git LXQt, which is based on Qt6. Did you experience the same issue before upgrading to KWin 6.0.2? |
Could you test with the default configuration |
Also this can't be the case because it means hundreds of times in a millisecond ;) |
Well my journalctl log had the same line printed over 100 000 times with the same second number, for every second, anyhow |
When I search "Container window visible, stack below" with google, I get only KDE bugs. You didn't answer my second question, BTW. |
I do not know as I installed lxqt-panel to try it out due to frequent crashes on xfce4-panel. I had been using mostly lxqt setup, except with kwin_x11 for WM and xfce4-panel until now. |
Many crashes and resets later and trying to open different sets of programs, almost at the root cause. For some reason, both lxqt-panel and lxqt-notificationd really do not like all sorts of applications that go into systray.
I also went ahead and tested this with both Some heavily cleaned up systemd journals as well. So something has gone wildly wrong with lxqt interacting with dbus to get information about systray icons/notifications. |
From the second log:
That looks like both plasma and LXQt notifications were running before. |
Referring to #2045 (comment) and the comment below it, I see problems with |
I noted that in the issue lxqt/lxqt#2509 all file handles were hogged and wanted to further specify that lxqt-notificationd gave me a graphical error about this when crashing. Wasn't aware that this was a significant error since linux doesn't log such events anywhere to my knowledge. |
Does it still happen with Qt6 and an upgraded system? |
It does. I have a lot of this in the output of journalctrl
Maybe this is related |
In the page from sway there is a reference to |
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Context
When lxqt-panel is running, it spawns the system journal with the message
lxqt-panel[1446]: Container window visible, stack below
Hundreds of thousands of times per second freezing the system until the panel is closed.
System Information
The text was updated successfully, but these errors were encountered: