[plasmashell] [Bug 408250] Job progress not displayed in pop-up notification when something other than plasmashell has registered kuiserver first
https://bugs.kde.org/show_bug.cgi?id=408250 --- Comment #23 from Jeffery Patton --- I changed some things to specify that this affects the stable 5.16 itself and it is for everyone running 5.16.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408250] Job progress not displayed in pop-up notification when something other than plasmashell has registered kuiserver first
https://bugs.kde.org/show_bug.cgi?id=408250 Jeffery Patton changed: What|Removed |Added Platform|openSUSE RPMs |unspecified Version|5.15.90 |5.16.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408250] Job progress not displayed in pop-up notification when something other than plasmashell has registered kuiserver first
https://bugs.kde.org/show_bug.cgi?id=408250 Jeffery Patton changed: What|Removed |Added CC||roundduckm...@gmail.com --- Comment #22 from Jeffery Patton --- I suffer the same as well, but at least I get a progress circle from my Latte dock. I think. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #77 from Jeffery Patton --- (In reply to Erik Kurzinger from comment #76) > The Qt patch has been submitted for review, sorry about the delay. That's great! Nice to see that this patch will be considered by the Qt devs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #72 from Jeffery Patton --- (In reply to John A from comment #71) > (In reply to Drake from comment #69) > > (In reply to Jeffery Patton from comment #68) > > > (In reply to John A from comment #67) > > > > (In reply to hugues31100 from comment #66) > > > > > (In reply to Luca Carlon from comment #65) > > > > > > What distro? > > > > > > > > > > I use Manjaro > > > > > > > > Download the KWin sources from > > > > https://download.kde.org/stable/plasma/$pkgver/$pkgname-$pkgver.tar.xz, > > > > edit > > > > the file main_x11.cpp (apply the patch > > > > https://phabricator.kde.org/file/data/telix5fjwmcuir3v5yxs/PHID-FILE- > > > > dldsuycendhh6yyimgsp/Masterwork_From_Distant_Lands) and compress the > > > > sources > > > > to a tar.xz. > > > > Edit the PKGBUILD from > > > > https://git.archlinux.org/svntogit/packages.git/tree/trunk/ > > > > PKGBUILD?h=packages/kwin with your own source tar.xz (compute the > > > > sha256sum > > > > for it and replace the field sha256sums in your PKGBUILD). > > > > Then, use the edited PKGBUILD to build and install the package. > > > > You have to repeat the process for qtbase , look at > > > > https://git.archlinux.org/svntogit/packages.git/tree/trunk/ > > > > PKGBUILD?h=packages/qt5-base. > > > > The patch for qtbase is: > > > > diff --git > > > > a/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > > > > b/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > > > > index 4adf662152..434ea60bfb 100644 > > > > --- > > > > a/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > > > > +++ > > > > b/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > > > > @@ -601,6 +601,7 @@ void QGLXContext::doneCurrent() > > > > else > > > > glXMakeCurrent(m_display, 0, 0); > > > > m_isPBufferCurrent = false; > > > > +m_swapInterval = -1; > > > > } > > > > > > > > void QGLXContext::swapBuffers(QPlatformSurface *surface) > > > > > > > > If for whatever reason you cannot apply the patches, just edit theses > > > > two > > > > files since the patches are pretty small in size. > > > > > > How about for Debian/Ubuntu/KDE Neon? > > > > > > I use KDE Neon (well, not as of late partly due to this bug) and I guess > > > many of the steps are similar, except for the fact I'm dealing with Debian > > > packages. Do I like, build KWin, then use checkinstall to create a package > > > and install the package, or what? :/ > > > > > > I suggest to wait for an official fix, else you have to repeat the build > > process with each kwin update. > > > > If you still want to apply the patch, you need to know at least some basic > > stuff how to build a package from source. Because this is different to every > > distro, i cant cover every distro here, but usually every distro has a good > > documentation how to build a package from source. I will show you today how > > to do that in Kubuntu. > > > > Lets assume you have Kubuntu Disco Dingo, in that case you need to obtain > > the sources for kwin Disco Dingo first. > > > > You can fetch them via web: > > https://packages.ubuntu.com/disco/kde/kwin-x11 > > > > Or via apt-get(recommended) > > apt-get source kwin-x11 > > > > > > After you downloaded the sources you can apply the patch to main_x11.cpp. If > > you aren't able to apply the patch for whatever reason, you can, like > > Jeffery already mentioned, just edit the files manually because the patch > > files are very small. After you have done that you need to install a few > > required build-tools: > > > > sudo apt-get install build-essential fakeroot dpkg-dev > > > > Now the only step left, before we can start the build, is to get the > > dependencies for the build itself. You can download and install them with: > > > > sudo apt-get build-dep kwin-x11 > > > > now we can start to create the build file > > we can do this with cmake ./ > > > > And then we can start the build with the com
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #68 from Jeffery Patton --- (In reply to John A from comment #67) > (In reply to hugues31100 from comment #66) > > (In reply to Luca Carlon from comment #65) > > > What distro? > > > > I use Manjaro > > Download the KWin sources from > https://download.kde.org/stable/plasma/$pkgver/$pkgname-$pkgver.tar.xz, edit > the file main_x11.cpp (apply the patch > https://phabricator.kde.org/file/data/telix5fjwmcuir3v5yxs/PHID-FILE- > dldsuycendhh6yyimgsp/Masterwork_From_Distant_Lands) and compress the sources > to a tar.xz. > Edit the PKGBUILD from > https://git.archlinux.org/svntogit/packages.git/tree/trunk/ > PKGBUILD?h=packages/kwin with your own source tar.xz (compute the sha256sum > for it and replace the field sha256sums in your PKGBUILD). > Then, use the edited PKGBUILD to build and install the package. > You have to repeat the process for qtbase , look at > https://git.archlinux.org/svntogit/packages.git/tree/trunk/ > PKGBUILD?h=packages/qt5-base. > The patch for qtbase is: > diff --git > a/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > b/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > index 4adf662152..434ea60bfb 100644 > --- a/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > +++ b/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp > @@ -601,6 +601,7 @@ void QGLXContext::doneCurrent() > else > glXMakeCurrent(m_display, 0, 0); > m_isPBufferCurrent = false; > +m_swapInterval = -1; > } > > void QGLXContext::swapBuffers(QPlatformSurface *surface) > > If for whatever reason you cannot apply the patches, just edit theses two > files since the patches are pretty small in size. How about for Debian/Ubuntu/KDE Neon? I use KDE Neon (well, not as of late partly due to this bug) and I guess many of the steps are similar, except for the fact I'm dealing with Debian packages. Do I like, build KWin, then use checkinstall to create a package and install the package, or what? :/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #62 from Jeffery Patton --- (In reply to John A from comment #55) > (In reply to John A from comment #54) > > (In reply to Jeffery Patton from comment #51) > > > (In reply to John A from comment #50) > > > > I can confirm that the regression appears in Kubuntu 19.04 with kwin > > > > 5.15.90, an NVIDIA Optimus setup (NVIDIA is selected as the primary > > > > GPU), > > > > OpenGL 3.1 used as the rendering backend and options nvidia_drm > > > > modeset=1 > > > > set(to enable PRIME Synchronization and eliminate horizontal screen > > > > tearing). > > > > > > > > KWin hangs when using active screen edges (Present Windows), > > > > Alt-tabbing and > > > > sometimes when maximizing or moving a window. > > > > > > > > Switching the rendering backend to XRender resolves the issue. > > > > > > XRender doesn't resolve the issue, it's an ugly workaround that forces > > > software rendering. It's just about as bad as disabling Prime Sync. > > > > > > Thanks for confirming this affects the upcoming 5.16 as well though. > > > > Oh I agree that XRender is an ugly workaround. I was just pointing out that > > KWin does not hang when XRender is used as the rendering backend. > > > > In addition, the aforementioned fork (kwin-lowlatency) exhibits the same > > behaviour. > > > > I will apply the patches mentioned in this thread and report back. > > Just to be clear, when I wrote that kwin-lowlatency exhibits the same > behaviour, I meant it hangs, it does not resolve the issue. Well, that isn't good then. I wonder how you would apply the patch on KDE Neon, so I can test it out. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #52 from Jeffery Patton --- (In reply to Guilherme Almeida from comment #49) > (In reply to Erik Kurzinger from comment #48) > > (In reply to Guilherme Almeida from comment #47) > > > (In reply to Luca Carlon from comment #22) > > > > Hello, I'm also affected by this issue. It is so severe that the system > > > > was > > > > hardly usable. I just noticed one thing: I suspect the issue appears > > > > for me > > > > only when drm is enabled with nvidia-drm.modeset=1. By default this was > > > > not > > > > set in Kubuntu 18.10 and 19.04 (may explain why Peter Eszlari could not > > > > reproduce?). Unfortunately drm is the only way I found to prevent > > > > horizontal > > > > tearing. > > > > No idea if this info is already known or of any help to you. > > > > > > I can confirm that, Luca. Using PRIME on Manjaro 18.0.4, I changed > > > /etc/modprobe.d/nvidia-drm.conf, setting like this options nvidia_drm > > > modeset=0 and the the frezze has stoped. I haven't noticed tearing so far, > > > but if happens I will edit this reply. > > > > Note that the reason this resolves the issue is that is disables PRIME > > synchronization entirely (see > > https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime- > > synchronization/ for details). So tearing would be expected, since this is > > how the NVIDIA driver is made aware of each vblank by the Intel driver. > > > > Only disabling vsync for the QtQuick pop-ups would definitely be a > > preferable solution, I think. > > Yeah, I've noticed... Is strange that this problem affects users from > differents ways? I mean... One user reported > (https://forum.manjaro.org/t/kde-plasma-freeze-when-i-use-screen-edges-kwin- > hang-regression/88897/31?u=fvguilherme) that simple install kwin-lowlatency > from AUR instead of kwin has solved the problem. > > and yes, I've noticed a little horizontal tearing. I choose keep the freeze. The reason that fork doesn't seem to suffer a problem is that it's focused on a whole bunch of fixes for rendering as a whole, like the bugs that makes KWin hard to run at 144Hz, and either these fixes also counteract the freezing regression to Nvidia Optimus, or it never had the code added to it in the first place, since it's a fork that predated 5.14.4. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #51 from Jeffery Patton --- (In reply to John A from comment #50) > I can confirm that the regression appears in Kubuntu 19.04 with kwin > 5.15.90, an NVIDIA Optimus setup (NVIDIA is selected as the primary GPU), > OpenGL 3.1 used as the rendering backend and options nvidia_drm modeset=1 > set(to enable PRIME Synchronization and eliminate horizontal screen tearing). > > KWin hangs when using active screen edges (Present Windows), Alt-tabbing and > sometimes when maximizing or moving a window. > > Switching the rendering backend to XRender resolves the issue. XRender doesn't resolve the issue, it's an ugly workaround that forces software rendering. It's just about as bad as disabling Prime Sync. Thanks for confirming this affects the upcoming 5.16 as well though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #45 from Jeffery Patton --- (In reply to Luca Carlon from comment #39) > Tried hard to reproduce but I couldn't. These two patches seem to fix > properly for me on nVidia. I wonder how I'd apply a patch to a KDE Neon package, so I can test it out myself. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #44 from Jeffery Patton --- (In reply to Jeffery Patton from comment #43) > (In reply to David Edmundson from comment #35) > > The problem is the horrible world of Linux distributions means releases are > > way out. A fix in Qt can take ages (easily a year or more) to hit a distro > > which might get the latest kwin. > > This is a problem KDE has to deal with too, but this is why distributions > should either roll, or use an LTS version of KDE. Fragmentation I feel too > doesn't really cause this, especially considering that KDE is more of a > system program that's more tied to the OS, and shouldn't be updated like a > typical program on a stable distribution anyways. That's why I feel any > stable distribution should use LTS KDE unless they're going to only last a > short amount of time like Fedora or non-LTS Ubuntu releases. Forgot the same for Qt as well. I love how Kubuntu 18.04 uses LTS KDE and Qt, bugs are still being fixed for its desktop. :D -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #43 from Jeffery Patton --- (In reply to David Edmundson from comment #35) > The problem is the horrible world of Linux distributions means releases are > way out. A fix in Qt can take ages (easily a year or more) to hit a distro > which might get the latest kwin. This is a problem KDE has to deal with too, but this is why distributions should either roll, or use an LTS version of KDE. Fragmentation I feel too doesn't really cause this, especially considering that KDE is more of a system program that's more tied to the OS, and shouldn't be updated like a typical program on a stable distribution anyways. That's why I feel any stable distribution should use LTS KDE unless they're going to only last a short amount of time like Fedora or non-LTS Ubuntu releases. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #33 from Jeffery Patton --- I changed the title to signify that this still affects 5.14.5, besides 5.14.4. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #32 from Jeffery Patton --- (In reply to David Edmundson from comment #28) > From Erik: > > "Alright, I think I see what the issue is. For context, on PRIME systems, > since there isn't actually a display connected to the NVIDIA GPU, we rely on > xf86-video-modeset, which drives the Intel GPU, to call to our driver after > each vblank. However, it will actually only do so if there has been damage > to the screen. So what I think we have here is QtQuick's thread waiting on > this vblank signal before swapping buffers (since we set MaxFramesAllowed to > 1), and KWin's main compositing thread waiting on the QtQuick thread. Since > KWin isn't rendering to the screen while it waits, no damage occurs and > hence this vblank signal is never sent. I think some timeout is what > eventually gets things going again (after about 30 seconds). Does that make > sense?" > > A possible patch is here: https://phabricator.kde.org/P385 could someone try > it? Nice to see that a patch's development is at least being kicked off. Dealing with this bug for more than a month now has been quite annoying. :P Too bad I don't know C++ (I'm learning software development in college though, so that's something I may learn in the future), because I could've helped with this problem as well. :( -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 Jeffery Patton changed: What|Removed |Added Summary|KWin 5.15.4 hang regression |KWin 5.15.4+ hang |on Nvidia Optimus |regression on Nvidia ||Optimus -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 Jeffery Patton changed: What|Removed |Added Flags||X11+, NVIDIA+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #21 from Jeffery Patton --- I changed some details to describe the bug better. This doesn't affect all Nvidia systems, doesn't only affect Arch Linux, and isn't only caused by alt-tab. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 Jeffery Patton changed: What|Removed |Added Summary|KWin 5.15.4 alt-tab hang|KWin 5.15.4 hang regression |regression on nvidia|on Nvidia Optimus Platform|Archlinux Packages |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 alt-tab hang regression on nvidia
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #20 from Jeffery Patton --- (In reply to Peter Eszlari from comment #18) > (In reply to Pieter-Jan Briers from comment #17) > > Could it be that the issue is exclusive to people using PRIME on laptops? > > My tests are based on a discrete graphics card (GTX 960). I can confirm that when doing alt-tab and window snapping while my laptop is plugged into a TV, that there is none of the freezing I've seen when doing things directly on the laptop screen, except maybe a tiny lag typical with doing laptop things on this TV anyways. This bug seems to only affect laptops with Optimus then. Crap. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 alt-tab hang regression on nvidia
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #19 from Jeffery Patton --- (In reply to Peter Eszlari from comment #16) > (In reply to Jeffery Patton from comment #14) > > (In reply to Peter Eszlari from comment #13) > > > I cannot reproduce this: > > > > > > kwin 5.15.4 > > > Qt 5.11.1 > > > nvidia 390.116 > > > > Could it be the Nvidia driver version as well? > > > > I have 418.x, maybe if I went back to the default Ubuntu drivers on my Neon > > system I could have the freezings stop? > > Now I also tested this on Kubuntu 19.04 (with nvidia 418.56) and I cannot > reproduce it there either. Huh. I'll see if this bug is persistent on laptops then, as Pieter has said about. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 alt-tab hang regression on nvidia
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #14 from Jeffery Patton --- (In reply to Peter Eszlari from comment #13) > I cannot reproduce this: > > kwin 5.15.4 > Qt 5.11.1 > nvidia 390.116 Could it be the Nvidia driver version as well? I have 418.x, maybe if I went back to the default Ubuntu drivers on my Neon system I could have the freezings stop? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 alt-tab hang regression on nvidia
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #9 from Jeffery Patton --- (In reply to Jeffery Patton from comment #8) > I have this problem too. It happens every time when I do window snapping > with my mouse. I tested Pieter-Jan Brier's step to reproduce this bug by > using alt-tab, and I get that problem too. > > I have a post about it on KDE's subreddit here: > https://old.reddit.com/r/kde/comments/bb1bot/ > anybody_having_freezing_problems_in_kde_neon/ > > ABOUT MY SYSTEM: > Operating System: KDE neon 5.15 > KDE Plasma Version: 5.15.4 > KDE Frameworks Version: 5.56.0 > Qt Version: 5.12.0 > Kernel Version: 4.18.0-17-generic > OS Type: 64-bit > Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz > Memory: 11.6 GiB of RAM > GPU: Nvidia GTX 1050 Ti I need to add too that I wonder if this bug is because of the Nvidia-caused CPU usage bug fix that I think was added in 5.15.4. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 alt-tab hang regression on nvidia
https://bugs.kde.org/show_bug.cgi?id=406180 Jeffery Patton changed: What|Removed |Added CC||roundduckm...@gmail.com --- Comment #8 from Jeffery Patton --- I have this problem too. It happens every time when I do window snapping with my mouse. I tested Pieter-Jan Brier's step to reproduce this bug by using alt-tab, and I get that problem too. I have a post about it on KDE's subreddit here: https://old.reddit.com/r/kde/comments/bb1bot/anybody_having_freezing_problems_in_kde_neon/ ABOUT MY SYSTEM: Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 Kernel Version: 4.18.0-17-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 11.6 GiB of RAM GPU: Nvidia GTX 1050 Ti -- You are receiving this mail because: You are watching all bug changes.
