Registered Member
|
I'm running Plasma 5 (5.5.5) on Fedora 23 (kernel 4.4.6-300).
My kf5-plasma version is 5.19.0. A few days ago, my primary display suddenly decided to wander to a different monitor. I assume it came along with some update, but I couldn't say what the update contained. I have attemped to set the primary display that I want, but it simply refuses to move. I have 3 monitors. One is HDMI (HDMI-0), the other two are DisplayPort (DP-3 and DP-5). (If that matters at all.) I would like for my center monitor, DP-3, to be the primary, but it has been forced to HDMI-0, regardless of the setting in the Display Configuration tool. Any thoughts how I might un-stick it? Thanks, Dave |
Registered Member
|
This is still an ongoing problem. It seems like every time I reboot my system, KDE forgets some of my settings when I login, again. Most notable are my screen configuration, primary display, and power control settings.
With respect to screen configurations, I have three displays connected to my system. When I reboot, I find that KDE returns to a "Unified Outputs" state, showing the same information on all three screens. I am forced to go separate the screens, again, and put them into the proper order. At the same time, I have to reset my default display, and it's not always the proper name of the display that works for me. I have HDMI-0 on the left, and then DP-3, DP-5 moving to the right. The monitor labeled DP-3 is my primary, but in the settings I had to select HDMI-0 for it to show up that way. Current Software: KDE Plasma Version 5.6.4 KDE Framework Version 5.21.0 Qt Version 5.6.0 Kernel Version 4.4.9-300.fc23.x86_64 What else can I provide that would be helpful to debug this problem? I'm truly trying to like Plasma 5, but I have to admit that I miss Plasma 4. Things worked just fine, and I could get on with doing whatever I needed to do. Thanks, Dave |
Registered Member
|
I really love KDE, is still my favorite DE despite all the issues.
But right now is a multi-monitor nightmare. |
Registered Member
|
I can confirm this. Setting the primary screen is hit or miss at the best. Often the primary screen is just the other one than is set; sometimes the primay screen (and therefore its panels) just sticks and the settings have no effect.
Even worse, if you deactivate one screen it happens that the panel(s) disappear(s) completely. (I guess, they move to the turned off screen, then, accordingly.) See also: https://www.kubuntuforums.net/showthrea ... sappearing Too sad, as KDE is such a great software. Hope the developers do read this. |
Registered Member
|
Yes, it is sad. This functionality worked in Plasma/KDE 4. It seems that the baby got thrown out with the bathwater, in this and perhaps a few other cases. At least, I know now htat I'm not the only one who is experiencing this particular category of trouble.
I agree that KDE is the desktop environment of choice, but I'm tempted to retreat to KDE4. There is a copr project that provides such a path. |
KDE Developer
|
A bug has been opened. I don't know the priority but I think it should be high:
https://bugs.kde.org/show_bug.cgi?id=363004 |
Registered Member
|
Thanks for the reply. As I said before, if there is any information I can provide that might be helpful, I will be more than happy.
I am a developer, myself, but I figure that I would just take away from someone else's time to get me up to speed. I can best be of service testing and providing debugging information. Thanks again, Dave |
Registered Member
|
This is great news! By the way, let me thank you for the great work you are doing! I hope for a quite high priority in this issue as it can make KDE kompletely unusable, depending on the use case. Think of a professional environment, e.g. where you have to switch a projector on and off in meetings or classes (which is, as you might guess, the case for me). Can I help testing? Please feel welcome to contact me.
I don’t believe this leads to solutions, at least in the long term. In fact, the old display management tool was buggy too – but you’re right, it didn’t have these issues as here. My criticism towards the development of KDE (and, by the way, other projects as well) is indeed that old versions tend to get dropped before the respective new one is really finalized. |
Registered Member
|
To be fair, the decision to move to KDE5 was made by the Fedora project, at least, in my case. KDE4 is certainly still out there, which is why it was possible for someone to put together a copr project for it. I do not hold these guys responsible for that decision at all. Fedora is notorious for living on the "bleading edge" of development. In this case, and in my opinion, they made a bad call. |
KDE Developer
|
Just to tell you: don't lose faith, Plasma people are working on the issue.
|
Registered Member
|
Thanks to all of you for your hard work. KDE is, hands down, the best desktop platform around!
|
Registered Member
|
Thank you for your kind reply! I want to tell you, that, besides this issue, I’m having a good experience with Plasma 5! (Upgraded from Ubuntu 14.04 to 16.04 a few weeks ago.) Hopefully, a fix will make it into the Updates of Ubuntu 16.04 LTS, too … |
Administrator
|
In order for this to be fixed properly, one would need Qt 5.6.1 (not 5.6.0, because there's a critical bug that will break Plasma). As far as I can tell, Ubuntu 16.04 ships 5.5.x.
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
Fedora 23 currently is pushing Qt 5.6.0, as well. Is 5.6.1 set for production release? Fedora is normally super quick about sending out new updates. They like to live on the bleeding edge. Maybe, I need to contact them to see about getting it updated in their repo.
|
Administrator
|
Fedora likely ships a patch to prevent the Plasma issue. 5.6.1 is supposedly slated to be out this week. Rergardless, there's a definite improvement with it (and Plasma 5.7 will bring further enhancements to that).
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar