| Summary: | The composer breaks down after you unlock the pc | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | s1r51ckb01 |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | asturm, kde, plasma-bugs-null, polynomial-c |
| Priority: | NOR | ||
| Version First Reported In: | 5.18.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
kwinrrc_config_file
kwinrc_2 Qdbus_log kwinrc_3_2020.03.18 Qdbus_kwin_2.20180318 Dbus-monitor GLXInfo |
||
Does KWin crash? i.e. do you see a sad face in the system tray that says kwin_x11 has crashed? No, unfortunately, I don't have any crash symptoms. I am aware of this situation because in the notifications I am indicated what is written in the first comment (composer disable it, to enable it use the dedicated shotcut) If you need logs and additional information are at your disposal. Could you please lock and unlock your screen so compositing gets disabled and post your ~/.config/kwinrc here? Created attachment 126845 [details]
kwinrrc_config_file
Yes sure.
> Enabled=true
> OpenGLIsUnsafe=false
These seem to be fine.
Could you please also post output of `qdbus org.kde.KWin /KWin supportInformation` after unlocking computer?
Created attachment 126849 [details]
kwinrc_2
I enclose again kwinrc (kwinrc_2) and qdbus
Created attachment 126850 [details]
Qdbus_log
Could you please check whether this bug still occurs when "Allow applications to block compositing" in the compositor settings is unchecked? Of course, today I'll be working with the setting disabled and I see the behavior First update of the day: by disabling that option for now I have not had any problems (no composition notification disabled) I enclose kwinrrc + qdbus after unlocking (kwinrc_3 + qdbus_kwin_2) Created attachment 126864 [details]
kwinrc_3_2020.03.18
Created attachment 126865 [details]
Qdbus_kwin_2.20180318
Okay, so it seems like compositing is blocked by some application. Just to be sure, could you please create a new user account and check whether this bug is reproducible with the new user account? Unfortunately, I celebrated too quickly. After about an hour or so of not using the login the problem reappeared. Being the pc I use for work I have some problems in creating a new user. It appears like somebody is trying to block compositing via d-bus, e.g.
qdbus org.kde.KWin /Compositor suspend
Can I ask you what I can verify (log/conf/etc.) (In reply to s1r51ckb01 from comment #16) > Can I ask you what I can verify (log/conf/etc.) Run bustle to record activity on the session bus, lock screen, unlock screen, stop recording, save the log, and post it here. Please make sure that compositing is disabled before stopping recording activity on the session bus. I started `dbus-monitor` before going on lunch break and on the way back I found the composer disabled. I enclose the product log Created attachment 126887 [details]
Dbus-monitor
Hmm, nobody attempts to suspend compositing via d-bus. :( Another potential reason why compositing gets disabled is that driver reports garbage GL_MAX_VIEWPORT_DIMS. Can you please post output of `glxinfo -l`? Created attachment 126888 [details]
GLXInfo
Sure!!!!
Git commit 348e72c56ec7e157cec15d8e27065e4194490d89 by Vlad Zahorodnii. Committed on 19/03/2020 at 14:40. Pushed by vladz into branch 'Plasma/5.18'. [scenes/opengl] Print a debug message when viewport limits aren't met Summary: This may help with debugging why compositing is suspended. Test Plan: Compiles. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D28139 M +3 -2 plugins/scenes/opengl/scene_opengl.cpp https://commits.kde.org/kwin/348e72c56ec7e157cec15d8e27065e4194490d89 The provided glxinfo log contains MAX_VIEWPORT_DIMS with normal values. I'm still pretty sure that the driver provides garbage GL_MAX_VIEWPORT_DIMS when we call viewportLimitsMatched(). Is there any chance you could build kwin with 348e72c56ec? I'm afraid not. Being a machine dedicated to work use, I would avoid doing trials of this kind. At this point I resign myself and I will wait for the next release of updates to see if the problem is solved. Okay, FYI, 5.18.4 will be released on 2020-03-31. Veeery good I have a little update: in this day i work only with one monitor (plugged in hdmi) I usually work with two connected monitors (one connected with hdmi and the other with mini display port). These days, it seems that the problem hasn't arisen... I have the same problem on an up-to-date Gentoo system. The issue started after upgrading to plasma-5.18 Girls and boys, I have a little update: today I disabled the screen saver after X minutes (in settings -> energy saving) and it seems that the composer no longer hangs up. I will continue to monitor the situation in the coming days This bug was reported against an outdated version of KWin. We have made many changes since the. If the issue persists in newer versions can you reopen the bug report updating the version number. |
Info System: -` .o+` `ooo/ OS: Arch Linux `+oooo: Kernel: x86_64 Linux 5.4.23-1-lts `+oooooo: Uptime: 37m -+oooooo+: Packages: 1376 `/:-:++oooo+: Shell: zsh 5.8 `/++++/+++++++: Resolution: 3840x1080 `/++++++++++++++: DE: KDE 5.67.0 / Plasma 5.18.2 `/+++ooooooooooooo/` WM: KWin ./ooosssso++osssssso+` GTK Theme: Breeze [GTK2/3] .oossssso-````/ossssss+` Icon Theme: breeze -osssssso. :ssssssso. Disk: 109G / 238G (49%) :osssssss/ osssso+++. CPU: Intel Core i7-4600U @ 4x 3.3GHz /ossssssss/ +ssssooo/- GPU: Mesa DRI Intel(R) Haswell Mobile `/ossssso+/:- -:/+osssso+- RAM: 3619MiB / 7839MiB I would like to apologize from the outset for the confusing information I am about to write. I will try to explain myself as best I can. Since I have done the 5.18 plasma update (5.18.2 included) I have noticed that when I move away from the PC and the screen lock is activated, once the unlock password is entered the composer stops working. As proof of this, the system notifies me of this and advises me to use the ALT+SHIFT+F12 shortcut to rehabilitate the composer. The strange thing is that in the settings (screen and video -> composer) the item "Enable desktop effects at startup" is active My configuration is as follows (I use X11 as a graphical server): Scaling method: Automatic Rendering Engine: OpenGL 2.0 Noise Prevention (vsync): Automatic Keep the window thumbnails: Only for visible windows [v] Allow applications to block the composition As always I thank you for everything you do for the community!