I'm working x11-wm/awesome-4.1:0 exploiting Multiple separate X11 screens as described in awesome issue #598 [ https://github.com/awesomeWM/awesome/issues/598 ] . At least since upgrade of QT -> 5.7.1 and KDE-Apps -> 17.04 (but I think to remember that with 16.12 already), running dolphin on any X11 screen > 0, starting okular from clicking a PDF file entry, . . . it always pops up on X11 screen # 0 regardless from which other screen it was started. Please, let me know which additional information would be helpful.
Created attachment 471288 [details] emerge --info dolphin >> emerge--info--dolphin.txt
Created attachment 471290 [details] emerge --info okular >> emerge--info--okular.txt
SAME starting kate or kwrite. SAME with gvim. WORKS : opens a running LibreOffice Application on the correct screen.
So, this is actually an awesmomewm issue, right? Because how would it be the applications' business to influence what screen they should appear on.
*** This bug has been marked as a duplicate of bug 616964 ***
(In reply to Andreas Sturmlechner from comment #4) > So, this is actually an awesmomewm issue, right? > Because how would it be the > applications' business to influence what screen they should appear on. O.k. - let me speculate once: Because _Dolphin_ starts those applications ? FACT: Starting those applications from awesome background menu _directly_ works perfectly.
I deeply disagree. And reject speculations instead of fixing. Thus, until _proven_, I request to keep this open. Thanks.
How big are chances that "Application X starts on wrong screen" consists of two different bugs? Right. So keep it at one single bug, the one you opened first. Especially since the only place where you can possibly fix this is upstream. *** This bug has been marked as a duplicate of bug 616964 ***
@ Andreas, you insisted to hi-jack : so both are _yours_ now, I'm out. Go forward and make sure for a resolution, whatever it may imply. Thanks.
No reason to act sour. Make your gentoo bug a tracker bug for upstreams if you want to have any solution found there enter gentoo quickly.
(In reply to Andreas Sturmlechner from comment #10) > No reason to act sour. Being with Gentoo since v1,2 , I _am_ used to cross-reference and mark as Dup as needed - as soon as being _proven_ or at least given verificating evidence, but not on "speculative probability". A) One case was about "app kate always starts on tag 6, _same_ X11 screen" B) Other case was "Dolphin starts apps always on active tag of X11 screen 0" In between, I have done the work to provide an example of A) (kate) _also_ behaving like B). _NOW_ I agree to merge the two bug reports because there is an indication of both being effected by the same cause. > Make your gentoo bug a tracker bug for upstreams if > you want to have any solution found there enter gentoo quickly. Thanks for your "beginner's lesson" - very much appreciated, indeed. P.S.: -> https://bugs.gentoo.org/show_bug.cgi?id=616964#c6 "Go forth and test!" (Linus Torvalds)
(In reply to Manfred Knick from comment #11) > Being with Gentoo since v1,2 That's all nice and well. Please note that I am purposefully not responding in your current open bug to not derail it further - you are solely responsible for how it looks. (In reply to Manfred Knick from comment #11) > I _am_ used to cross-reference and mark as Dup as needed - > as soon as being _proven_ or at least given verificating evidence, > but not on "speculative probability". So you didn't open your second bug based on "speculative probability" before you had even established at whom to direct the first one? If you like it or not, someone's got to process your bugs, and if you begin to spawn multiple bugs before you have made your case this is bound to end up in a fragmented mess. It does not improve the chance of success for your bug, although the real place to fix it is upstream anyway. Based on your information given at the time it was perfectly reasonable to close this as duplicate. "If it quacks like a duck..." (In reply to Manfred Knick from comment #11) > _NOW_ I agree to merge the two bug reports > because there is an indication of both being effected by the same cause. And in between you've wasted unnecessary time with cross-referencing and bickering. Work on your temper, use less capitals, and you will find people to be more likely to chime in and help, hitting less walls.
More detailed findings described in awesome issue #598 [ https://github.com/awesomeWM/awesome/issues/598 ], comment 2017-05-01 19:01 Finally I could identify the **patterns**: AWESOME: A) _Dolphin_ spawns the apps (including Kate) from file context - onto that (wrong) X11 screen where (after starting X env) the _first_ instance of Dolphin had been started - (regardless if this _first_ instance has been closed in between) - into the currently active "tag" of that (wrong) X11 screen. TWM: FVWM: FLUXBOX: XFCE: A) Dito:
dolphin doesn't start applications, klauncher does. Using dbus. https://userbase.kde.org/KDE_System_Administration/Startup#klauncher:_Service_Activation Imo still the same/similar bug as your other one.
Upstream: KDE_Bug 379489 - [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen [ https://bugs.kde.org/show_bug.cgi?id=379489 ]
Meanwhile also verified on ctwm with 4 screens.
Although confirmed as working stable multiple times, unfortunately, Elv13 stated that nobody @ Awesome would care about independent X11 screens ("ZaphoMode") any more; c.f. https://github.com/awesomeWM/awesome/issues/598#issuecomment-305114301 ff. Same disinterest stated by leading upstream (=KDE) developers. If really nobody cares besides me, I do not mind to close as "WONTFIX".
