[SOLVED] Last Week's Update Killed Fullscreen in Plasma(X11) Now This Weeks and No Regression Fix This Time

chrisretusn · 10-09-2021, 08:59 AM

Quote:

Originally Posted by enorbet

I suppose I wasn't quite clear. I can go fullscreen with a parent app, like Firefox, but if I try to launch a sub as fullscreen as well and from the parent, like a YouTube video, screen goes black... BUT if I keep Firefox smaller than full, clicking the video's full screen icon works as it should. The same goes for other apps and subs like Gwenview.... works fine as long as Gwenview isn't full when I select a photo to go full.

I view YouTube a lot, I full screen most videos I watch, as I mentioned earlier I keep Firefox maximized. I even tried going full screen with Firefox and clicking the full screen a YouTube video. All is workings.

I fired up Gwenview which I also use maximized. Going full screen with a picture from Browse or View (clicking the full screen icon on image) works.

I tried going full screen of from embedded videos on web sites. also on facebook from a videos displayed in my feed, no issues.

Quote:

Thanks again chrisretusn, it would be some helpful to know if driver version is having any effect. I've tried 460.x drivers and 470.x drivers and those all exhibit the same problem. The only changes that work have been KWin version for a time (regression no longer works for some elusive reason) or keeping the parent app less than full when launching a sub as full.

I'm stuck with the 390.x drivers. I use most of my programs maximized, keeping it less than full would not be cool.

I wish I could do more. I know what it's like to have a unique problem. I made a couple of post in a couple of related thread about an issue I am having with logging out of Plasma, no one else seems to have it. I plan on making my own thread on this once I get some other testing done to see if can find a reason. So far I have been very frustrated with this issue.

enorbet · 10-09-2021, 02:40 PM

Thanks again chrisretusn, that helps narrow the field a bit. At the very least it appears the action is interactive between nvidia drivers and KWin. Now if I only hear from someone else using 460 or 470 drivers. It's difficult to know how much is or could be KDE Plasma since few distros are as current as Slackware Current. The latest OpenSuse is still on LTS (5.18).

enorbet · 10-10-2021, 03:32 PM

I figured I should reiterate that in the quest to discover whether fault is with nvidia driver version or KDE, it is probably important that the problem occurred with KDE updates, which for a time was solved with a KWin regression. So my money is on KDE being to blame. What complicates things is something in addition to KWin is now also involved. At least it seems that way since regression no longer fixes it.

FWIW I realize this is hardly an important issue since, at least for now, there is a fairly easy workaround. It does smack of a compatibility issue though, since it only happens in KDE with KWin enabled. If the dev team was set to make some fundamental change one would think they'd make driver builders aware.

chrisretusn · 10-11-2021, 03:54 AM

Out curiosity do you normally boot to runlevel 3 and use startx (what I do) or runlevel 4? I think you answered this in Post #1.

I agree that it seems to be a KWin issue.

enorbet · 10-11-2021, 02:39 PM

I always boot to runlevel 3 but do not "startx". I login as root and execute "sddm" from where I choose WM/DE and User login. The problem does not occur in Fluxbox or Xfce... or KDE if I disable KWin.

chrisretusn · 10-12-2021, 02:54 AM

Quote:

Originally Posted by enorbet

I always boot to runlevel 3 but do not "startx". I login as root and execute "sddm" from where I choose WM/DE and User login. The problem does not occur in Fluxbox or Xfce... or KDE if I disable KWin.

Thanks!
Hmm... I never thought of that option before. Come to think of it, I do believe somewhere on this forum you have said that before, says one of mu brain cell. I think I will try this today after I update.

0XBF · 10-13-2021, 02:24 PM

Hi,

I noticed that I am getting a black screen when going fullscreen in a youtube video as well. This is on a slackware64-current box that is a couple weeks behind the latest slackware-current updates (been running windows on it lately for work purposes).

Some notes:
- Graphics card is a nvidia 1660 super, using the 470.63.01 drivers (the nouveau driver crashes).
- I have two monitors plugged in, one into HDMI, the other in a DisplayPort.
- The black screen only occurs with youtube in full screen on the DisplayPort monitor (HP E223), the HDMI monitor is fine with full screen.
- This only occurs in kde plasma 5, xfce is fine with both monitors in full screen.

Disabling compositing stops the problem.

After some web searching I found a reddit thread about disabling "full screen animations" and that also fixes the issue, while still allowing compositing to be used. To disable "full screen animations", open the system settings control panel, click "Workspace Behavior", then "Desktop Effects", uncheck "Full Screen" (it says "Animation for a window going to and leaving full screen mode" underneath the option).

Hope that helps your issue enorbet

0XBF · 10-13-2021, 02:45 PM

Well that was short lived lol. It was working for a bit and stopped again. I also noticed that just toggling the compositor checkbox "Allow applications to block compositing" off and back on again will make the fullscreen video work until the next time I re-open a full screen video. Perhaps disabling that "full screen" animation did something similar.

Sorry for the false hopes. I'll poke around some more and see if I learn anything else

0XBF · 10-13-2021, 05:29 PM

Well so far the only things that work consistently are either disabling compositing or switching from OpenGL to the XRender backend. The problem occurs with either of the OpenGL options enabled. This bug report on kde's webpage describes the problem exactly the same as I have it: https://bugs.kde.org/show_bug.cgi?id=441904 Guess I'll be running XRender for a while and keeping an eye on the progress with this one.

enorbet · 10-13-2021, 07:26 PM

Thanks very much 0XBE, I have similar results - failure. The easiest workaround (but still a pita) is don't go Fullscreen from a maximized window. Example: if I'm viewing a YouTube video in Firefox on KDE Plasma and wish to go Fullscreen on the video, I have to first resize Firefox down some. Then the video doesn't go blackout.

0XBF · 10-13-2021, 08:14 PM

In the meanwhile I tried patching kwin to revert the code from the commit that was pointed out in that bug report. I can confirm that it fixes the fullscreen problem with kwin-5.22.5 so I added my case to that report.

If you're feeling up to it you can try patching it yourself with the following patch:

kwin_surfaceitem_revert_f432ba78.patch

Code:

--- ./src/surfaceitem.cpp       2021-10-13 18:33:12.240973977 -0500
+++ ./src/surfaceitem.cpp.new   2021-10-13 18:33:38.319972955 -0500
@@ -92,9 +92,7 @@
     } else {
         m_windowPixmap->create();
         if (m_windowPixmap->isValid()) {
-            if (m_referencePixmapCounter == 0) {
-                m_previousWindowPixmap.reset();
-            }
+            m_previousWindowPixmap.reset();
             discardQuads();
         }
     }

To use it you would need a copy of the kde.Slackbuild and source files from a slackware-current mirror. Make a 'kwin' directory inside the patch directory and drop that file in there. Then in the patch directory, create a kwin.patch file with the following:

Code:

cat $CWD/patch/kwin/kwin_surfaceitem_revert_f432ba78.patch | patch -p1 --verbose || { touch ${SLACK_KDE_BUILD_DIR}/${PKGNAME}.failed ; continue ; }

Then you can run the kde slackbuild just for kwin and it will pick up the patch:

Code:

# ./kde.SlackBuild plasma:kwin

Note that the last command will upgrade the package automatically too (its coded into the kde.SlackBuild). To just build the modified package without automatically upgrading to it you'd have to disable it with something like:

Code:

UPGRADE=no ./kde.SlackBuild plasma:kwin

But then you will have to manually 'upgradepkg' it after.

Hopefully the kde devs can provide a proper fix and correct the problem upstream sometime in the near future.

0XBF · 10-14-2021, 06:14 PM

Nice timing with the plasma 5.23.0 release today. I was looking at the changes and saw they had addressed this bug with kwin. Pat also now added it to the slackware-current repos and after upgrading to it, I see that fullscreen is working again here.

Hopefully you see similar results!

enorbet · 10-15-2021, 03:31 PM

Thank you 0XBE
Thank you KDE
Thank you Patrick

all is right with Fullscreen now

chrisretusn · 10-16-2021, 03:37 AM

Quote:

Originally Posted by enorbet

all is right with Fullscreen now

Awesome!

enorbet · 10-16-2021, 09:04 PM

My apologies chrisretusn if it felt like I slighted you. I am also indebted to you for your concerm, support, ideas, and helping to kep the thread alive. If I hadn't been clear on that, well... I just have