Gräßlin: Multi-screen woes in Plasma 5.7
Gräßlin: Multi-screen woes in Plasma 5.7
Posted Jul 12, 2016 2:23 UTC (Tue) by torquay (guest, #92428)Parent article: Gräßlin: Multi-screen woes in Plasma 5.7
Martin's entire blog post is a litany of excuses. Take this gem for example:
-
It’s affecting all Qt applications on X11 and has nothing to do with Plasma. Just because Plasma is also using Qt does not mean that Plasma developers have to fix it.
Apparently nothing is the fault of Plasma. It's either upstream's fault (Qt, drivers, etc), or the application themselves are to blame (dodgy window hints). Except that Plasma is the desktop environment providing the user interface. One of its core functions is to provide window management, and yet it fails to do that reliably. This makes it unfit for purpose.
If Plasma is to serve as a provider of a user interface, then it must take into account the limitations of the software stack it's using. In other words, it must provide workarounds for the underlying problems in the stack, or create its own parts of the stack (no need to use Qt for everything). Anything less than that is evading responsibility to the end users.
Furthermore, a lot of the issues described in the blog post could have been detected with a modicum of testing, prior to releasing Plasma. Instead, users are yet again treated as guinea pigs (ie. file bugs, because KDE developers couldn't be bothered to do thorough testing themselves). How many times have we been here before?
Posted Jul 12, 2016 3:08 UTC (Tue)
by ReallyNiceGuy (guest, #60085)
[Link] (3 responses)
Posted Jul 12, 2016 6:31 UTC (Tue)
by phocean (guest, #108185)
[Link]
Posted Jul 12, 2016 19:52 UTC (Tue)
by pbonzini (subscriber, #60935)
[Link]
Posted Jul 12, 2016 21:30 UTC (Tue)
by mm7323 (subscriber, #87386)
[Link]
I filled some bugs with as much info as I could, and these collected lots of me-too responses, more info and suggestions. The bugs seemed to snowball, but there was never any progress or dev involvement so the energy was wasted.
I moved to LXDE, but then with HiDPI the whole thing got just too bad again. A new laptop later and I actually use Win10 with Linux in VirtualBox. It works well enough, and I can get Vbox to do screen scaling too if needed.
The sad thing is that I remember multi screen working really well in KDE on fedora 13 or something around then. I remember undocking, all the windows coming onto the panel, then docking again and them going back to their original multi-screen layout. Hopefully we will get back to that sort of thing one day again.
Posted Jul 12, 2016 5:50 UTC (Tue)
by mgraesslin (guest, #78959)
[Link] (21 responses)
Posted Jul 12, 2016 6:29 UTC (Tue)
by phocean (guest, #108185)
[Link] (2 responses)
1) Why was it released to users without testing? It always take me 20 sec on any KDE fresh install to make it crash very badly, with multi-screen.
2) Ok, the underlying stack is rotten. But why is it working with Gnome? If you haven't yet, you should test this environment and pick some idea. At least they respected their users in finding a workaround.
So, yes, pointing out the weaknesses is good, but coming with a solution is better.
Because, even though I like Plasma, it is useless to me as is, so I am using Gnome.
Posted Jul 12, 2016 7:08 UTC (Tue)
by warrax (subscriber, #103205)
[Link] (1 responses)
The fact that it fails in 20s on your setup has no bearing on whether it regularly fails for anyone else. Testing resources are limited.
(Btw, do you have any idea how unbelievably entitled you sound/read to others?)
> Ok, the underlying stack is rotten. But why is it working with Gnome? If you haven't yet, you should test this environment and pick some idea. At least they respected their users in finding a workaround.
Well, GNOME has a different set of workarounds that fail in other circumstances.
Posted Jul 12, 2016 7:26 UTC (Tue)
by phocean (guest, #108185)
[Link]
Nothing exotic, I do have a simple Thinkpad with Intel graphics, and I reported the bug a while ago.
> (Btw, do you have any idea how unbelievably entitled you sound/read to others?)
No, sorry if you feel so. Of course, I am not. But neither your, nor me, are native English speaker or have the same culture.
> Well, GNOME has a different set of workarounds that fail in other circumstances.
In my extensive experience, very, very much less. Bugs are minor and in more serious circumstances, Gnome manages to reload himself, preserving windows positions and everything else.
Posted Jul 12, 2016 7:04 UTC (Tue)
by h2 (guest, #27965)
[Link] (17 responses)
1. ignored comment, did not publish it, because it pointed out a series of core problems with your approach to software development and bug reporting, using specific examples of massive bugs and failures from the 5x release to highlight the points, I assume that's why anyway.
My conclusion was this: kde is broken internally as a project and is currently unable to ship quality software that can be trusted. I moved to xfce, which thank god still appears to be run by responsible competent adults. If you're confused about how to properly integrate a new toolkit, look how xfce is doing it with gtk3. Slowly, bit by bit, probably waiting for issues to be resolved in gtk3 (and believe me, I'm NOT a gtk fan), then rolling out support for the new toolkit, once it's stable. Not breaking it all then making excuses, which seems to be the too big and pointlessly bloated to succeed model that gnome and kde are both following.
I further concluded that the kde project itself is the problem at this point, not a specific issue or bug, certainly I couldn't trust kde to deliver a desktop I'd want to use, even when working, it was like you guys never even try to stress your desktops, so the stuff is incredibly slow, particularly when you load it with lots of programs and virtual desktops (something it appears you guys don't even use as developers anymore given how incredibly poorly these things ran in 5.x and 4.x to a lesser but still quite poor degree), I had accepted this slowness in kde 4.x, but when I went to xfce, I suddenly saw how bad kde had gotten, switching virtual desktops now works just the same as it used on kde 3.5, when it was fast, like a desktop should be.
It seems like you guys have gotten lost in all your glitzy details, and actually believe that a desktop is something more than what runs your applications in a smooth, fast, clean way. it's sad, because a theoretically good and working kde would still be the best out there, but kde hasn't been good and fast for years, and 5.x isn't even working, though there's lots of excuses given.
I don't blame you for being defensive, that's certainly the easier option, rather than actually looking at the kde project and trying to figure out how things can have gotten so distorted that basic functionality is left to rot and die while you do all kinds of exciting things like adding support for wayland, something that barely even exists out here in the real world yet.
My conclusion is that there was never enough developer mindshare to maintain two distinct full featured desktops, and there still isn't, and there certainly isn't enough to maintain massively bloated stuff like kde 4-5x have become, or gnome, or whatever. Incremental development would have been the key, with well planned gradual integration of new toolkits, but that would probably require a mindset your project no longer has access too, which is too bad.
And I speak as someone who spent years doing heavy duty active support for a kde based distro, and really wanted to like kde but in the end I had to wave the white flag and give up, it simply was not practical to deal with software from a group that simply seems unable to do anything remotely close to good programming. kids, lol, what can you say, you can only get what you get out of college.
I'd tentatively suggest that a few simple tests be used to check design concepts:
1. the virtual desktops are not an afterthought, which means, you can do simple things that all your users wanted, like putting a different image on each desktop, by design, not a crude tacked on hack added late in the release series, like happened with 4.x. Again, being unable to do this I believe is a design flaw, not a small thing that doesn't matter.
2. switching between heavily loaded virtual desktops happens almost instantly. 4x would take up to 15 seconds on a very heavily loaded desktop switch, it was really getting silly. xfce of course manages this, magically, as it should, instantly. So did kde 3.5.
3. multiple monitor support is a core feature, face up to it, only power users as a rule use gnu/linux, it will never crack the windows market, this is particularly true because the one thing regular users not only hate, but won't tolerate, is incomprehensible failures of their desktops. I was a significant kde distro guy, and I lost 1 week on the various failures of 4.x to 5x, and I am patient, and able to debug, and try to resolve issues, heck, I'll even file bug reports to devs who are competent enough to take them, but certainly not if they react with defensiveness (always the hallmark of the mediocre I find).
So there's little point in pretending that gnu/linux desktop marketshare is more than the roughly 1.8, and apparently falling, that it is now, which means, get real, stop doing stupid over the top graphics junk and focus on what matters to users, the desktop working, being fast, stable, and reliable. If you can't figure that out, then just stop pretending kde is more than a hobbiest project.
I loved the entire concept behind kde, but it's failing seriously now. I'd say xfce is only a few core features/weaknesses away from being almost everything kde 3.5 was, which is more than 4.x and 5x ever will be given how slow they are. xfce of course has to deal with the radical gtk 3x instability, so I guess they will wait for gtk 3.x stable to be released, then build on that, incrementally moving along, slowly, conservatively.
Posted Jul 12, 2016 7:49 UTC (Tue)
by mgraesslin (guest, #78959)
[Link] (8 responses)
Posted Jul 12, 2016 11:09 UTC (Tue)
by nix (subscriber, #2304)
[Link] (7 responses)
Look, I get that wm development is hard and drives people to insanity in record time, and I get that crucial parts of the stack are broken, but the fact remains that if your software depends on a broken stack of components you replace or repair the broken pieces until you get something that works (e.g. perhaps getting and using an ATI video card, on which multi-monitor support works perfectly; or finding out what LXDE-Qt are doing to make multi-monitor support work). You don't post blog posts containing a litany of excuses: that just makes you look like you're whining and does nothing but reassure your users that you are not actually trying to fix the problem in any meaningful sense: you're trying to fob the problem off on other people.
After all, all the pieces here are free software and with the exception of the Intel portion none requires specialized hardware knowledge. At no point did you say why you couldn't fix any of the Qt bugs: you just took it as read that of course you wouldn't because that was in a different silo!
Posted Jul 12, 2016 16:01 UTC (Tue)
by einar (guest, #98134)
[Link]
For the record, many of the glaring issues with QScreen were fixed by KDE developers.
Posted Jul 12, 2016 18:01 UTC (Tue)
by mgraesslin (guest, #78959)
[Link] (5 responses)
git shortlog -- src/plugins/platforms/xcb/qxcbscreen.*:
Martin Gräßlin (2):
with 3 more changes by KDE devs. Overall in the xcb plugin I just counted 53 commits by KDE devs. Many of them being screen related.
So I think we do our job there.
Posted Jul 13, 2016 14:57 UTC (Wed)
by nix (subscriber, #2304)
[Link] (4 responses)
Posted Jul 13, 2016 15:29 UTC (Wed)
by mgraesslin (guest, #78959)
[Link] (3 responses)
Posted Jul 13, 2016 17:10 UTC (Wed)
by tuna (guest, #44480)
[Link] (2 responses)
Posted Jul 13, 2016 19:05 UTC (Wed)
by mgraesslin (guest, #78959)
[Link] (1 responses)
Posted Jul 12, 2016 9:00 UTC (Tue)
by distances (guest, #103785)
[Link]
I'm not affiliated with KDE, but do you really expect to be taken seriously after commenting like this? I for sure didn't bother to read the rest of your comment, and I would just straight away delete posts like this from my own blog. This is simply not constructive, and you know it.
Sorry for derailing the discussion. Martin, thanks for insights and your hard work, it's really appreciated. I recently updated to 5.7 and things seem very stable this far.
Posted Jul 12, 2016 17:07 UTC (Tue)
by krake (guest, #55996)
[Link]
Isn't that exactly how this is being done?
Krita had its first Qt5 based release only recently, I think Okular has not released its Qt5 variant yet, etc.
Posted Jul 12, 2016 17:57 UTC (Tue)
by rsidd (subscriber, #2582)
[Link] (2 responses)
I'm a long-time, but not quite "power", user. My current, and likely long-term, desktop environment is a mix of i3 and xfce. But I only went this route because of frustrations with the "friendly", "Windows-like" alternatives. I installed KDE 1.0 on a bunch of linux machines at my grad school in the late 1990s, and many people were relieved at not having to battle with fvwm or whatever the previous desktop was. I used KDE, primarily, up until 4.0, and struggled with 4.x for a while after before quitting. I used Gnome 2 and Ubuntu Unity for a while. In a way I am thankful that all of these were so sub-optimal (or evolved in such sub-optimal directions) that I was forced to find a better setup for myself.
Now, my reading of the current situation is the "desktop" market for Linux, such as it is, is dominated by Ubuntu (Unity) and Fedora (Gnome 3). I'm not sure if there is a single widely-used distro that uses KDE by default any more. Doesn't mean KDE developers should just quit and do something else, but it does mean they should worry a little about what Linux desktop users (who are likely to be power users with multiple monitors etc) are experiencing, and how their offering compares to other desktops on Linux.
Posted Jul 12, 2016 18:19 UTC (Tue)
by einar (guest, #98134)
[Link]
openSUSE uses Plasma as the default desktop selection.
Posted Jul 15, 2016 19:31 UTC (Fri)
by thoeme (subscriber, #2871)
[Link]
Posted Jul 13, 2016 5:42 UTC (Wed)
by jackb (guest, #41909)
[Link] (2 responses)
I tried it intermittently in the late 90s, and then used it pretty much continuously since the 3.x days.
This means I've running KDE for about half my lifetime.
Half of the time I've been using KDE has been waiting for the 4.x and higher series to regain the stability of the 3.5 releases.
Have I really wasted a quarter of my life limping along with almost-but-not-quite functional desktop? I guess once you adapt to it the limitations and workarounds feel natural and you stop noticing them.
Posted Jul 16, 2016 15:30 UTC (Sat)
by jospoortvliet (guest, #33164)
[Link] (1 responses)
Posted Jul 19, 2016 19:43 UTC (Tue)
by Wol (subscriber, #4433)
[Link]
When I had my trouble with early KDE4, I ended up with Xfce and/or KDE. I can't remember whether I looked at Gnome, but when I do I almost always end up running away screaming - Gnome and I just don't get on ...
Cheers,
Gräßlin: Multi-screen woes in Plasma 5.7
The straw for me was the window manager crashing every time my secondary monitor was turned on. I found a bug filled for this exact issue, added my report to it, but, more than a year after that, I still receive "me too" updates on that bug.
I have no problems using XFCE at all. It is simple enough, does the job, it is quick and lightweight.
I wonder if all the bells and whistles are really worth the trouble.
I agree with your view about testing, but I feel that the problem is deeper than that. It seems to me that much that is changed is just done for the sake of the change itself.
Gräßlin: Multi-screen woes in Plasma 5.7
Gräßlin: Multi-screen woes in Plasma 5.7
Gräßlin: Multi-screen woes in Plasma 5.7
Gräßlin: Multi-screen woes in Plasma 5.7
Gräßlin: Multi-screen woes in Plasma 5.7
Gräßlin: Multi-screen woes in Plasma 5.7
Gräßlin: Multi-screen woes in Plasma 5.7
Anyway, I could reproduce it on any hardware : login, place the external monitor on the top of the main, apply and... it is over: main screen get black, panel is on the secondary, and plasma gets unresponsive.
Believe me, I am honest, as I do prefer Plasma as a DE. I have tried using it for months and tried all possible workarounds, but for my work I need stability.
don't make me laugh
2. locked thread for further comments
3. ignored another comment I put on another posting, same story.
don't make me laugh
don't make me laugh
don't make me laugh
don't make me laugh
Enable XSync extension also for KWin
Do not overwrite existing event mask of root window
don't make me laugh
don't make me laugh
don't make me laugh
don't make me laugh
don't make me laugh
> xfce [..] still appears to be run by responsible competent adults
don't make me laugh
don't make me laugh
don't make me laugh
don't make me laugh
Seens YMMV all over...
don't make me laugh
don't make me laugh
don't make me laugh
Wol