Version: 2.0 (using KDE 4.0.0) Installed from: Gentoo Packages Compiler: gcc version 4.1.2 (Gentoo 4.1.2 p1.0.2) OS: Linux konqueror --display :0.1 will open konqueror on my second display konsole --display :0.1 will open konsole on my first display export DISPLAY=:0.1 konqueror will now open on second display konsole will open on first display When now konsole has opened: $ env | grep DISPLAY DISPLAY=:0.0
I take it you are launching Konsole from within Konsole itself? In that case, this has the same cause as bug #155340 When running Konsole from an xterm with --display :0.1 (which doesn't exist on my system), kdelibs failed ungracefully: > /media/usbdisk/robert/kde4/src/kdelibs/kdeui/windowmanagement/kwindowsystem_x11.cpp:276 > sprintf( net_wm_cm_name, "_NET_WM_CM_S%d", DefaultScreen( dpy )); Called from: > /media/usbdisk/robert/kde4/src/kdebase/apps/konsole/src/main.cpp:81 > 81 if ( KWindowSystem::compositingActive()
On my system, no matter were I launch konsole from, it opens on :0.0 I now tried from an xterm running on :0.1 and I tried from the plasma application launcher which I've managed to get to show up on :0.1. The result is the same.
> On my system, no matter were I launch konsole from, it opens on :0.0 Do you already have Konsole running on :0.0 before trying to open it on :0.1? At present, once Konsole has been started on a particular display, any new instances will be part of the same process and will start on the same display.
I did, I closed all of them and started a konsole from :0.1 and from :0.0 with DISPLAY set to :0.1. And you were right, in both cases konsole opens on :0.1 as expected.
Should be fixed by SVN commit r795982. When Konsole is started from the terminal it always uses a new process so it should respect the value of $DISPLAY in the parent processes environment.
Marking as fixed as per comment #5