| Summary: | No open animation with google-chrome in CSD mode | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | MrNekit <Balykin_nikita> |
| Component: | effects-window-management | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | minor | CC: | bizyaev, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.24.5 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Demonstration
CSD mode (no window open animation) system titlebar and borders enabled (animation plays) |
||
Looks like KWin's Scale effect is not activating when the window is opened and closed. I can half reproduce with Chromium (not Chrome). If I disable the system titlebar and borders and use the app in CSD mode, then the Scale effect triggers when the app is launched, but not when its window is closed. If I make it use the system titlebar and borders, then the effect plays for both. Can you reproduce that? (In reply to Nate Graham from comment #1) > Can you reproduce that? Yes, I can. In CSD mode no window open animation, but when I enable system titlebar and borders the effect plays. Created attachment 149512 [details]
CSD mode (no window open animation)
Created attachment 149513 [details]
system titlebar and borders enabled (animation plays)
But there is little bug when I enable system titlebar and borders. For a while the window is empty. Very interesting. It could be a bug in Chromium/Chrome itself, or an issue in KWin. I don't see the issue in other CSD-using apps though. (In reply to MrNekit from comment #5) > But there is little bug when I enable system titlebar and borders. For a > while the window is empty. There are possibly two things that could happen: either chrome is transparent in first N frames or kwin fails to get window pixmap because geometry changes, etc. Can you run kwin with QT_LOGGING_RULES="kwin_scene_opengl.debug=true" and see if kwin prints anything when opening google chrome? QT_LOGGING_RULES="kwin*.debug=true" `env QT_LOGGING_RULES="kwin*.debug=true" kwin_x11 --replace` in konsole > qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 18923, resource id: 69206021, major code: 18 (ChangeProperty), minor code: 0
> qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 19028, resource id: 69206021, major code: 18 (ChangeProperty), minor code: 0
> kwin_core: User timestamp, ASN: 10891832
> kwin_core: User timestamp, final: KWin::X11Client(0x55fcacff1960, windowId=0x1000003, caption="Новая вкладка - Google Chrome") : 10891832
> kwin_core: Activation, compared: KWin::X11Client(0x55fcacff1960, windowId=0x1000003, caption="Новая вкладка - Google Chrome") : 10891832 : 10889335 : true
> qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5386, resource id: 69206021, major code: 18 (ChangeProperty), minor code: 0
> qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5473, resource id: 69206021, major code: 18 (ChangeProperty), minor code: 0
> kwin_core: User timestamp, ASN: 11025203
> kwin_core: User timestamp, final: KWin::X11Client(0x561d07a67880, windowId=0x1000003, caption="Новая вкладка - Google Chrome") : 11025203
> kwin_core: Activation: No client active, allowing
> qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6076, resource id: 73400706, major code: 3 (GetWindowAttributes), minor code: 0
> AppMenuModel::onActiveWindowChanged 16777219 ( == QVariant(int, -1) )
> AppMenuModel::onActiveWindowChanged 16777219 ( == QVariant(qulonglong, 16777219) )
system titlebar and borders enabled (previous post in csd mode)
This seems to work for me now: Operating System: openSUSE Tumbleweed 20240503 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-1-default (64-bit) Graphics Platform: Wayland Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
Created attachment 149422 [details] Demonstration Check attach SOFTWARE/OS VERSIONS: Chrome ver: 102.0.5005.61 Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.15.41-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × AMD Ryzen 3 PRO 2200G with Radeon Vega Graphics Memory: 21.5 ГиБ of RAM Graphics Processor: AMD Radeon Vega 8 Graphics