KDE Multi-Monitor Control Getting An Overhaul
Multi-monitor support on Free systems has always been a pain (even after RANDR made it a lot less of a pain). GNOME2 had a great feature: you only had to configure a given pair of displays once and it would do-the-right-thing and remember their configuration. But if you wanted to mirror displays of different resolutions, you were out of luck. KDE handled the latter case, but infuriatingly enough doesn't remember or restore configurations like GNOME2 did, and worse yet requires manual intervention before disconnecting a display. But, now that's all changing: "As some of you might have noticed, display management in KDE is not really something we could be proud of. It does not work as expected, it lacks some features and it’s not really maintained. Time to change it, don’t you think? ... Alex has written the libkscreen library that provides information about available/connected/enabled outputs and notifications about their changes. He also intends to write a KDED daemon that would listen for these events and depending on connected monitors (every monitor can be uniquely identified by it’s EDID) it would load specific configuration. For example, docking your notebook into a docking station at work would automatically turn on a second monitor and place it left of the notebook screen (or whatever you configure the first time you do it). Undocking the notebook and connecting a data projector in a meeting room would automatically set clone mode etc. etc."
Additionally, the dock applet and monitor configuration UI have been overhauled allowing for quickly setting common configurations ("extend display to the {right,left,top,bottom}" / "clone") directly from the desktop, and direct manipulation of the monitor positions if you do end up needing to use the configuration program (article has a video and screenshots).
In other news, readers demand to know when Slashdot is getting getting an editor.
True story.
Finally! I use KDE at work every day and this is the one major thing that makes me hesitate always when I need to disconnect my computer from a dock. Especially when there are three use cases that are always encountered: desktop monitor, projector, and just the plain laptop screen without any external monitors.
Is the medi medi cation cation taking effect effect yet yet?
Proverbs 21:19
Honestly.
You're supposed to know how to hack your xconfig with vi. Setting up two displays is supposed to hurt.
:wq
I'd like to see more vanilla versions of this software. Open Source Software has become almost as bad as the commercial counter parts in wanting to wrap everything up as one big GUI package. I don't want a bunch of bologna to download and run to configure dual monitors if I want to use a very lightweight window manager, or setup an embedded solution such as a kiosk.
/optional/ GUI front end over this junk any day.
One of the original and cool ideas of open source was to allow hackers to dive into the utilities and do really cool things with them that they aren't meant to achieve. A multi monitor control system that is tied into a blob of libraries doesn't sound appealing to me. I'll take a 32KB application that has an
Sig: I stole this sig.
I don't think Windows handles multiple monitors very well either. It's not just free operating systems, it's all operating systems. 3rd party utilities are the only thing that come close to making multiple monitors behave well.
Yes it's an anecdote! Were you expecting original research in a Slashdot comment?
geez, someone remind me why linux hasn't taken off yet? oh yeah, because every bit of setup and configuration is a pain in the ass.
And here Windows 7 handles five monitors using three different resolutions flawlessly. Thanks to Ultramon, they line up seamlessly in spite of also being different sizes and being at different physical elevations. It's one of the more major things that has kept me on Windows - I look forward to Linux being able to do the same.
When I disconnect the external monitor, it automagically moves APP windows and panes to laptop monitor, that is configured as secondary screen. When I replug the monitor, APP windows that previously where on it, return to it, as do the panes...
They waste all these time mucking with icons, reorganizing menu accesses, and other such superfluous "human interaction" nonsense, but never got around to supporting something as basic as multiple displays.
It's why you're better off to wait for jesus to return than the mythical "year of linux desktop".
Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
to..
KDE Getting Multi-Monitor Control
I run LMDE with three monitors driven by two ATI/AMD Radeon cards. I use the fglrx proprietary catalyst driver largely because I have difficulty getting all three monitors going without it.
Unfortunately, I am now quite familiar with my xorg.conf file.
My point: Linux multi-monitor support is one area where it has dragged behind Windows and it's about time somebody started seriously working on it.
nvidia-settings
Detect Displays
Click on newly-detected display and select "TwinView" and "Clone Displays".
Click apply.
Done, works with all window managers.
Finally, the last piece needed to get Linux onto the desktop!
Considering that Macintoshes have had these features for over a quarter century, this is great news.
Really glad to see this fixed up. It will be a great day when my external screen is the way it should be when I fire up and dock my laptop in the morning. Long over-due.
Mike
Good multihead support should be on kernel level. This allows multihead not needing the X-server.
...the original Mac had the basis for this designed in from the beginning. The Mac had a graphics region (65k x 65k pixels) larger than the display region. The window was a display port on this region.
If it supported Opencl that would be a start.
While is nice to have better control over this features we need to first get them working reliably, I still can't get KDE to start with max the laptop monitor max resolution, it will always go back to a 1280x768 and I have to change it manually.
In the end we get back to the same old problem with Linux graphics, driver support. I remember back a couple of years having a nvidia card with the binary blob, most stuff worked as I wanted but screen adjusting and multimonitor had to be done via nvidia tools, but in the end of the day it works. Now I have an ATI card and I cannot get multimonitor working properly even with its own tools, on a more powerful card with more memory.
For quite a while I think there has been no real interest on doing this overhaul as most of those features would not work releably on most systems.
C-x C-c
Where can I get the source code to libkscreen? I can't find it on github. Link?
In all these years of Linux usage I still have not been able to do clone a display while having different resolutions. Is this actually possible?
I want to present slides on a presentation monitor, which is connected to my Thinkpad (nvidia, binary driver) via VGA cable. At the same time, I want to see the slides on the notebook screen during the presentation. So the screen has to be cloned.
However, the native resolution of the notebook and second (big) monitor differs. For instance, the notebook is 1600x900, the external presentation monitor is 1920x1080. Is there a way to produce the signal in 1920x1080 on the second monitor, and at the same time clone the screen on the notebook screen in another resolution?
Been using multi-monitor for many many years.
Setup xorg.conf or xfree86.conf and done. What the hell is so hard about that.
Now you windows noobs who think you are l33t since you installed dual boot linux, and are running gnome or kde, fuck you, if you can't figure out something as fucking simple as a couple lines in your xorg.conf file.
And shit, you can whip up a little shell script that auto adds and removes monitors, as it detects they are connected and disconnected with xrandr in a couple minutes-- fucking simple.
Different resolutions-- so? Always has worked for me.
Well, I'm using KDE with two monitors right now. (left/right configuration). However, I configured these with the Radeon tool which works well with little fuss. Ditto with multiple monitors on Nvidia (the vendor tool works nicely).
My biggest complaint about multiple displays on KDE is what happens if you have a transient display (not always connected). When I have my laptop at my work-desk, I connect to a bigger monitor and have dual-head. However, if I don't disable the dual-head before using the laptop without a secondary display, baaaad things happen and I usually end up with a desktop that's stuffing new windows onto a monitor that doesn't exist.
Mind you, I think this might be at least partially problem with the vendor driver, but the WM should be smart enough to figure out that a monitor no longer exists as well.
Filed a few bugs in my time, nice of them to take notice.
TFS mentions only GNOME2. How is the multi-monitor status on other DEs nowadays? XFCE, GNOME3, MATE etc.? Cinnamon would still be the same as GNOME2, right?
10 years too late?
"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety."
My work machine has four (yes) monitors, two on a Radeon 7000 series and two on the Intel IGP. Win7 works mostly[1] flawlessly, but Mint will only see the two Intel-powered monitors by default. I'm given to understand that I can get all four going, but it'd involve writing a custon xorg.conf and I can't be bothered since I'm usually in Win7 because that's what I have to support.
[1] fairly often the Intel driver will crash and be automatically restarted on resume from sleep.
Hail Eris, full of mischief...
E pluribus sanguinem
Macs have supported multiple monitors since what, 1988 or so? That just work/easily configurable/reconfigurable..
That "feature" was a trap just waiting for people to play with it and end up with a blank display on login
If a user used that tool to set a resolution that was not available to the hardware the only ways around it were to create a new user account for them and copy the files over or to log in remotely and fuck about with the braindead registry clone (only worse) that is gconf - think a MS Windows registry only without regedit and without any man pages for the obscure registry key manipulating software. Think of that and think of how you would talk someone through it on a poor quality phone line with no chance of remote login and you'll get some idea of how pissed off I was at this "feature".
Changing stuff in xorg settings like any sane application (nvidia-settings etc) does gives you a way back if the configuration is messed up. Hiding it in a registry key that is inaccessable without undocumented tools that are not even on the system by default is a failure of design. Whatever gnome idiot did that (and I know it was not Miguel) and then wandered off leaving unsupported shit behind should never have forced their stupid idea into the mainsteam and should have just left it all to xorg until they had a fully working implemention instead of just an incomplete and undocumented demo.
... that my taskbar will finally start up on a deterministic screen, and no longer the crapshoot of Left-only, Right-only, or spanned-across-both every single time I log on?
"Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
EOM
Ubuntu is an African word meaning 'I can't configure Debian'
Newsflash: the "desktop" isn't even going to matter to people like you (consumers) in a few short years. Desktops will be used only by content producers, and everyone else (content consumers) will prefer tablets, where (ironically) linux already dominates.
That is one "feature" that is about as brain dead as it comes. White space is supposed to be a delimiter between words. I can see how on one level it seems more cool and "generalized" to be able to have arbitrary chars in file names, and indeed software should handle these cases correctly, but it is really an ugly hack. It breaks the clean, simple, and intuitively obvious way of telling when one identifier ends and another begins.
Writing software that correctly recognizes file names with spaces in them is an admirable adaptation to poor naming by users.
Actually putting white space into file names is a bad idea, and putting it into the names of main program directories is utterly stupid.