[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 fanzhuyi...@gmail.com changed: What|Removed |Added Summary|External Monitor stopped|External Monitor stopped |working after commit 120d14 |working after commit ||120d1415 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 --- Comment #3 from fanzhuyi...@gmail.com --- Commit 62873155 was still bad, in case people are wondering if this has been fixed by very recent commits. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 David Edmundson changed: What|Removed |Added Priority|NOR |VHI -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #4 from Zamundaaa --- https://invent.kde.org/plasma/kwin/-/merge_requests/4770 should work around the issue -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|CONFIRMED |ASSIGNED --- Comment #5 from Nate Graham --- FWIW I cannot reproduce the issue with only an Intel iGPU, and no NVIDIA GPU. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 --- Comment #6 from fanzhuyi...@gmail.com --- (In reply to Zamundaaa from comment #4) > https://invent.kde.org/plasma/kwin/-/merge_requests/4770 should work around > the issue This fixes the issue for me, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 --- Comment #7 from fanzhuyi...@gmail.com --- If this is a nvidia driver issue, should an upstream bugreport be filed to nvidia? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 --- Comment #8 from fanzhuyi...@gmail.com --- Just out of curiosity, are the autotests in the CI/CD pipelines capable of capturing regressions like this? Or can they not because currently there is no nvidia runner for the pipelines? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 --- Comment #9 from Zamundaaa --- > If this is a nvidia driver issue, should an upstream bugreport be filed to > nvidia? I already contacted NVidia about this and will follow up with them as needed. > Just out of curiosity, are the autotests in the CI/CD pipelines capable of > capturing regressions like this? No, the drm autotests that we already have, and the better ones that are still planned can't cover driver bugs as they're built against a virtual driver. Having tests be run on bare metal against a vast array of different hardware and drivers is far outside of the scope of things KDE can realistically do. Maybe eventually we can make some driver test farms also test KWin on those drivers, but even that would only run from time to time, and would not catch these issues before they're merged. So for the foreseeable future, the only way to catch regressions like this is to do manual testing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 --- Comment #10 from fanzhuyi...@gmail.com --- (In reply to Zamundaaa from comment #9) > > If this is a nvidia driver issue, should an upstream bugreport be filed to > > nvidia? > I already contacted NVidia about this and will follow up with them as needed. Thanks! > > Just out of curiosity, are the autotests in the CI/CD pipelines capable of > > capturing regressions like this? > No, the drm autotests that we already have, and the better ones that are > still planned can't cover driver bugs as they're built against a virtual > driver. Having tests be run on bare metal against a vast array of different > hardware and drivers is far outside of the scope of things KDE can > realistically do. > Maybe eventually we can make some driver test farms also test KWin on those > drivers, but even that would only run from time to time, and would not catch > these issues before they're merged. Totally understandable. What are the possibilities of getting nvidia to make some donations if they care about making KDE software run better on nvidia platforms? > So for the foreseeable future, the only > way to catch regressions like this is to do manual testing. Glad I could help in some way : ) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478246] External Monitor stopped working after commit 120d1415
https://bugs.kde.org/show_bug.cgi?id=478246 Zamundaaa changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/50899f3f34 ||bacb70c5fcdc0e6dea1803400d0 ||b60 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #11 from Zamundaaa --- Git commit 50899f3f34bacb70c5fcdc0e6dea1803400d0b60 by Xaver Hugl. Committed on 08/12/2023 at 16:27. Pushed by zamundaaa into branch 'master'. backends/drm: work around atomic commits failing with NVidia For some reason, when IN_FENCE_FD is set, the NVidia driver rejects the commit. Until that's fixed in the driver, don't set the property M +2-1src/backends/drm/drm_commit.cpp M +6-0src/backends/drm/drm_gpu.cpp M +1-0src/backends/drm/drm_gpu.h https://invent.kde.org/plasma/kwin/-/commit/50899f3f34bacb70c5fcdc0e6dea1803400d0b60 -- You are receiving this mail because: You are watching all bug changes.
