As most of the underlying work is in QtWayland, I’d say: yes, it’s Wayland only (not being the author nor an expert on display technology, so take my words with some caution). The blog post talks about some stuff that is impossible to do in X11 (“impossible” as in “would require massive changes to X11 itself, which no one wants to do”).
@Sina@MartinR xorg supported exchanging the compositor before (kwin --replace). I believe xorg didn't support clients surviving a crash of xorg itself.
I wouldn’t say it’s a bad browser for regular web browsing if you just want a vanilla browsing experience. It integrates well with KDE Plasma theming and does come with an ad blocker built in and the ability to customize the browser through scripting. Past that it just doesn’t have a lot of the bells and whistles (such as variety in extensions) that other browsers have. I prefer having at least a few privacy extensions and a better ad blocker installed so it’s a deal breaker for me for daily driving. If you don’t mind something more minimal like that it works just fine.
I prefer having at least a few privacy extensions and a better ad blocker installed so it’s a deal breaker for me for daily driving.
Too bad KDE rather develop three(!) completely independent browsers than to just combine resources and all three are based on QtWebEngine. So there is Falkon which only has a desktop GUI. Then there is Angelfish that has a smartphone GUI, a tablet GUI, and also a desktop GUI. Recently they released a browser for TVs – why they did not just add a fourth GUI to Angelfish: Nobody knows. Why Angelfish wasn’t just developed as Falkon 3.0: Nobody knows.
When it was still based on QtWebKit (and named QupZilla), it had relatively little overhead, so it was a better choice for low end PCs than fully featured browsers. My guess is that those descriptions are a leftover.
@Yora@woelkchen most people do not look beyond the UI. Unfortunately writing a pretty UI is the easy part of writing a browser. Maintaining some browser engine is much harder.
So make sure to use a browser with an engine backed by as big an open source project as possible and one where the browser engine has as few downstream patches as possible.
Wrapping the entire engine in a new set of APIs not available upstream involves way too many downstream patches for my taste.
And yet, when Qt Company still made QtWebKit, instead of using the stable branches Apple used for Safari, they made releases from svn trunk and then tried to stabilize it with a small team. No idea when Qt Company keep trying to make a browser module for so long and keep failing all the time…
That killed the whole xorg session. It logs into a black screen with only the cursor. I’ve been messing with it for about 3 days. So, I just went ahead nuked my whole system, including my home drive and reinstalled from scratch. All good now. It was painful to restore all of my home files from server, but we are all good now.
I don’t think a reinstall should be necessary. I upgraded a Neon unstable machine from 5.x to 6 in place and it worked fine. The final release should work the same.
I wouldn’t say switching too much. I probably do it once every two weeks or so. Also, wouldn’t reinstalling the system fix the whole thing? This happens on a fresh install out of the box. Wayland is just out of the question for me now, as I can never keep the 175% scaling.
Try reinstalling the drivers and make sure the open source one is not installed. Also, what distro are you using, what card do you have, and what version of the drivers are you running?
I encountered this too. There is a way to disable this in the notification settings, but that way is disabling notifications for “special application behavior” or something like that outright. You can probably do this per app, I’m just not sure what kind of other notifications this disables (if any). But if you wanna try, just it the settings icon on the next popup.
Nothing is throttling my CPU unless it’s somehow defaulted on in OpenSuse, Manjaro, Debian, or Linux Mint. Also these same distros, I installed other DEs on and had it work just fine. It’s a AMD Ryzen 9 3900x 4 ghz 12 cores.
This is specifically a KDE problem. So question, if you do windows key -> term/kon -> enter. As quickly as you can, does it accept the enter input and immediately launch your terminal?
@MJBrune@Ashiette I tried doing it as quickly as I can and it didn't work the first time (result appeared what looks like about 0.1-0.2s later) but it did work in subsequent attempts (even when looking for other apps)
CPU: i5-1135G7
If you look for an app and then for a different app, does it find it quickly? I suspect it might be reading the .desktop files lazily (meaning it only reads them the first time you look for something)
Edit: nvm ksycoca is there to prevent that
Even if I look for the same app over and over again, it doesn’t speed up. Doesn’t seem like a caching issue to me. Perhaps the second time you were just .1-.2 seconds slower on the enter button?
This is far too late of a response, but I’m glad you found it! I haven’t logged in for a while, but I’m coming back now. Apologies for not getting back! Ditto menu really is great. <3
KDE
Top