Bug 379489

Summary: [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen
Product: [Applications] dolphin Reporter: Manfred Knick <Manfred.Knick>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: normal CC: mail
Priority: NOR    
Version: 17.04.0   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: emerge --info dolphin >> 0_emerge--info-dolphin.txt
emerge --info dbus >> 0_emerge--info-dbus.txt

Description Manfred Knick 2017-05-03 20:57:38 UTC
Created attachment 105331 [details]
emerge --info dolphin >> 0_emerge--info-dolphin.txt

Apps started via file-entries' context menu pop up on a wrong X11 screen.

The real pursuit may well reside inside klauncher or dbus.

In case, please be so kind to re-locate (I am not a QT/KDE expert).

Overview:
https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298620529

Description of Startup Procedure:
https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298611832

Observation of Patterns:
https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298374308

Please, let me know which further information would be helpful.
Comment 1 Manfred Knick 2017-05-03 20:58:42 UTC
Created attachment 105332 [details]
emerge --info dbus >> 0_emerge--info-dbus.txt
Comment 2 Manfred Knick 2017-06-07 16:30:16 UTC
Meanwhile also verified on ctwm with 4 screens.
Comment 3 Manfred Knick 2017-06-07 16:30:57 UTC
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".
Comment 4 Julian Steinmann 2018-05-19 14:17:24 UTC
Hello @Manfred & sorry that no developer ever responded to your question. After reading up on the issues you linked, I think the main problem is that not a single developer of Dolphin uses Zaphod mode, so fixing such a bug would be very hard. We are of course open to accept a patch from you or anybody else who also encountered this issue, but it's very unlikely that a developer could even reproduce the bug without completely changing their system... 

I propose to close this bug as RESOLVED WONTFIX even though this is a valid bug :( But it appears to me that you are really the only person affected by it + the developer of awesome does not intend to bring back Zaphod mode either. Would that be okay for you?
Comment 5 Manfred Knick 2018-05-19 17:05:19 UTC
> Would that be okay for you?
Certainly,
as already proposed at the end of comment 3 above.

Julian, I'm sorry but I have given up on KDE in scenarios 
where I necessarily have to combine multiple different HW adapters,
ensuring that special applications definitely run on their desired monitor ...

Thanks for looking into the issue 
and for your polite, friendly statement.