Bug 451846 - [nvidia] Subsurface problem
Summary: [nvidia] Subsurface problem
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.24.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-24 08:51 UTC by ad1rie3
Modified: 2022-03-25 15:01 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
wayland log (515.58 KB, text/plain)
2022-03-24 08:55 UTC, ad1rie3
Details
Wayland log on INTEL machine (working) (222.90 KB, text/plain)
2022-03-24 08:59 UTC, ad1rie3
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ad1rie3 2022-03-24 08:51:52 UTC
SUMMARY
I run the test weston-subsurface for testing nvidia hardware i run the test in MODE 0, in this mode the red circle and the triangle always turn. 

https://photos.app.goo.gl/jRzxwRSCqWRdtux2A

STEPS TO REPRODUCE
1.  Lunch weston-subsurfaces no param

OBSERVED RESULT
the red circle and triangle not turn, except when i move my cursor or resize the windows

EXPECTED RESULT
In mode 0, the green turn only when we resize the windows, the red and triangle alway turn and never stop

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.15-201.fc35.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor
Memory: 15.6 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1660/PCIe/SSE2
Comment 1 ad1rie3 2022-03-24 08:55:01 UTC
Created attachment 147695 [details]
wayland log
Comment 2 ad1rie3 2022-03-24 08:59:12 UTC
Created attachment 147696 [details]
Wayland log on INTEL machine (working)

On intel, it's working fine, so i joint the same log, for diff with the log of problem
Comment 3 ad1rie3 2022-03-24 14:17:04 UTC
After some test, it stuck on 
[3535557.686]  -> wl_surface@24.attach(wl_buffer@51, 0, 0)
[3535557.705]  -> wl_surface@24.damage(0, 0, 101, 102)
[3535557.719]  -> wl_surface@24.commit()
[3535557.781] wl_display@1.delete_id(41)
[3535570.280] wl_display@1.delete_id(49)
[3535570.449] wl_display@1.delete_id(36)
[3535570.476] wl_buffer@44.release()

juste before callback.done
[4244776.086] wl_callback@51.done(2406061[4244776.069] 
[4244776.097] wl_buffer@42.release()
)
[4244776.105] wl_callback@36.done(2406061)
Comment 4 ad1rie3 2022-03-25 12:48:17 UTC
Ok, driver bug, it happens on Weston too.