Version: 1.0.2 (using KDE KDE 1.2) Installed from: RedHat RPMs OS: Linux Restored konsole windows set DISPLAY to ":0", new konsole windows set DISPLAY to ":0.0". Normally I wouldn't be very picky about this, but we're faced with a situation where software in use at our site requires the DISPLAY variable to be EXACTLY the same (along with username and hostname) to be considered the "same user" for licensing purposes. Can anyone tell me how/why this difference arises and how I might change it?
I don't know what causes it. Why not simply check for "DISPLAY=:0" and set it to "DISPLAY=0.0" in your shell initializiation?
Well, yeah, we can always add yet another hack to .cshrc to get around another strange software inconsistancy. For once, I thought I'd try to delve a little deeper. FYI - I appears that changing :0 to :0.0 in /etc/X11/xdm/Xservers (I'm running an older kdm which still uses this file) appears to make the restored konsoles use ":0.0" as their DISPLAY, providing consistency. This isn't the "correct" thing to do, as we are starting servers here, not screens. But kdm loads struct display->name from that text which serves as the source for DISPLAY from the get go. I haven't figured out where in the KDE the .0 is added to the display name. But it seems like it should be added sooner rather than later.
I've been messing with this. I don't think it is a Konsole bug. 1. xterm has the correct $DISPLAY=0.0 when started by session manager and user. 2. Not related to kdm; using 'startx' also shows this issue. I would say it is a kinit problem, but I don't know enough to follow it.
Is this report still valid on KDE 3.x?
Still happens with 3.5.8 in Fedora 8.
In my machine running KDE-4.7.0, both restored konsole and new konsole have DISPLAY as ":0".