Interesting on my ancient Dell Laptop the Mastodon Instance seems to trigger a bug in falkon-qt6 on GhostBSD.

Scrolling the page locks the box up and after short while screen turns black for a second or two and gets back responsible back then, so you can click on the close button to close falkon. If you don't it turns black again, rinse and repeat.

falkon-qt6 does work fine on another machine with GhostBSD and it wasn't nothing like that before, so it must have been a recent deprecation.

Tried downgrading drm-kmod but to no avail, geckobased and blinkbased works, so switching now to ungoogled-chromium now.

---
/e1: FYI, tested with xlibre, same bug

/e2: turning on/off hw accell, same bug

/e3: dooble (also qtwebengine) triggers the same bug... It is a bit more verbose and utters something about "context lost via EXT_robustness. Reset status = GL_GUILTY_CONTEXT_RESET_KHR" and later "context lost during make current" in all sorts of parts of chromium.

/e4: et tu "qutebrowser" and qutebrowser-qt5: Same bug, same error msgs in qtwebengine as dooble.

/workaround: export "QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" enviroment variable
---

Wait.. I *did* disable hw accel tick box in the browser. Oh, let me guess: "it's just the browser that doesn't use hw accel now, nobody spoke of mOdErN qtwebengine, eh!?!"

Anyway, this fixed it for me.
Now, off to work... later shift.

#runbsd #browser #webengine #gpu #oldhardware #drm #freebsd #ghostbsd #qt #falkon #kde

I was working on updating a #cpp project to a newer #Qt version, but wanted to keep comparing to a #git tag from some time ago. The problem is that checking out a different commit changes all the files as far as #CMake is concerned, and everything builds from scratch. If only there was a way to have another copy of the same repo without cloning...

find . -name '*.qml' | xargs sed -i 's/\(import [A-Za-z0-9.]*\)[ ]*[0-9.]*/\1/g'

Which translates to "please remove all versions from import statements in my #Qt QML files"