Version: 4.6.1 (using KDE 4.6.1) OS: Linux Nvidia -- Option "Xinerama" "0" Dual displays, running panels on both displays with task manager etc. in each pannel. (Basically two independent displays) When Konsole is launched from the application menu or from an icon the first konsole is launched onto the correct display containing the pointer. All subsequent launches are launched to the same display and virtual desktop as the initial Konsole. No other applications appear to suffer from this problem. If all konsoles are terminated the launching will again be correct for the first new konsole. Of interest: The passive busy icon appears on both displays while launch is pending. Reproducible: Always Steps to Reproduce: launch konsole on display 0 then launch second konsole on display 1 Actual Results: 1st konsole launches onto display 0 2nd konsole launches onto display 0 Expected Results: 1st konsole launches onto display 0 2nd konsole launches onto display 1
Does "Basically two independent displays" mean different $DISPLAY environment variable? I'm terribly unfamiliar with those setups. This might be another side effect of Konsole using KUniqueApplication. That is, Konsole tries to use only one process for all the Konsole windows launched from menu or Krunner. You can use "ps aux | grep konsole" to check that. What if you launch Konsole by typing 'konsole' manually in a xterm in the given stpes? That would force konsole to use new process.
(In reply to comment #1) Yes DISPLAY is :0.0 and :0.1 However I have just tried again and now everything is broken, I fear that KDE4 will never be able to support proper multiple displays. Now even adding a panel no longer works. The only way this will ever work again is if some of the developers use NVidia without Xinerama and choose "separate displays" While many people might just wash this away, to me that is the same as a windows user saying that virtual desktops are a waste of time. If you do have multiple monitors and you work with lots of open windows its _really_ nice to be able to have separate virtual desktops on each monitor. Of note is that while KDE3 did not allow you to move windows between monitors Gnome did have that option.
Thanks for your feedback about $DISPLAY However, the other information is a little off topic. I know little about dual monitors, multiple displays, etc. So clearly I can't help much here. It is better to open another report for your genenal problem against kwin developers. The only thing I can help here is to confirm this specific problem of Konsole is related with Konsole using KUniqueApplication. So please, try launching Konsole from xterm in each display, and see whether the results are different from the original report. Or, you have done that but I failed to notice it in your last comment? Thanks in advance.
[pasting here the reply sent directly to me with the approval from the reporter] Hi Sorry I did not make myself clearer, its quite a while since I posted that report, and at that time it was still possible to use separate multiple displays. However since I have updated KDE to 4.6 this is no longer possible as the desktop wallpaper appears to be raised above all windows. But I have forced it closed and tried as you requested, and if I run konsole from a terminal with the correct DISPLAY environment it works fine. Also if I use "File-New Window" the new windows are correctly shown on the displays as would be expected. When running under Gnome, the problem with konsole is present as described, again If I open a Gnome terminal it opens on the correct display, and any Konsole's opened from within the gnome terminals then appear on the correct display. Hope this is clearer. Regards Ross
Hi Ross Thanks for your valuable feedback, again. Now I'm sure this specific problem is due to konsole using KUniqueApplication. In other words, in most cases there will be only one konsole process no matter how many Konsole windows are launched from icon/menu/krunner. That implies all those Konsole windows will have the same $DISPLAY, so they all show up in the same display. The obvious fix is to stop using KUniqueApplication. However, that is a big change in design and is unlikely to happen in the near future. So the best thing that can be done at the moment is to acknowledge the existence of this issue.
Ross/Jekyll I'd first like to acknowledge that this issue has seen a few years. :) Is this still an issue with current konsole? I'm not 100% familiar with having alternate display exports.
Created attachment 132996 [details] attachment-18262-0.html Hi Justin I am sorry I can no longer confirm if this is the case as I gave up using separate displays and learnt to live with the limitation and advantage of having a unified display. However I will try reconfigure this weekend if I have some spare time and report back. Regards Ross On 2020/11/03 08:16, Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=269338 > > Justin Zobel <justin.zobel@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|CONFIRMED |NEEDSINFO > CC| |justin.zobel@gmail.com > > --- Comment #6 from Justin Zobel <justin.zobel@gmail.com> --- > Ross/Jekyll I'd first like to acknowledge that this issue has seen a few years. > :) > > Is this still an issue with current konsole? I'm not 100% familiar with having > alternate display exports. >
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!