Summary: | [Multiple separate X11 screens] x11-wm/awesome :: kde-apps/kate-17.04.0 :: starts on wrong tag of current active X11 screen | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Manfred Knick <Manfred.Knick> |
Component: | Current packages | Assignee: | Maxim Koltsov (RETIRED) <maksbotan> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Manfred Knick
2017-04-29 09:38:05 UTC
CROSS-REFERENCE: awesome issue #1759 [ https://github.com/awesomeWM/awesome/issues/1759 ] *** Bug 617004 has been marked as a duplicate of this bug. *** CROSS-REFERENCE: -> https://bugs.gentoo.org/show_bug.cgi?id=617004 -> https://bugs.gentoo.org/show_bug.cgi?id=617004#c4 -> https://bugs.gentoo.org/show_bug.cgi?id=617004#c7 *** Bug 617004 has been marked as a duplicate of this bug. *** As stated in -> https://github.com/awesomeWM/awesome/issues/1759 . in between, <cite> Worth the effort, I built fvwm-crystal (which provides 8 virtual screens per X11 screen). It suffers the _same_ problems, starting applications on wrong screens. Unfortunately, I could not identify any correlation at all yet. </cite> So it's _not_ proven awesome to be the cause ! @ Andreas: Now, I am really fed up with all your speculations again and again. DO WORK ! Or keep out interfering, PLEASE! That does _not_ meet "Gentoo Dev Quality" at all. If needed, we might take this to the board - as one example ... Deeply sorry for my edit mistakes and the noise ... 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: B) Starting _Kate_ from awesome background menu, it opens - onto the current active X11 screen - but onto that (wrong) "tag" - which is the active one on X11 screen 0. - Above behaviour does not apply to KWrite, GVim, LibreOffice and Okular, - but seems to be specific to Kate and Awesome only afaics. TWM: FVWM: FLUXBOX: XFCE: B) = as to be expected: The tests have been executed with [-P-] [ ] x11-wm/awesome-4.0-r1:0 and [IP-] [ ] x11-wm/awesome-9999:0 at last. kate uses dbus at startup to detect existing instances. Start with --startanon to possibly modify behaviour. Upstream: KDE Bug 379488 - [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen [ https://bugs.kde.org/show_bug.cgi?id=379488 ] 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. Thus closing as "WONTFIX". POSTSCRIPTUM: Meanwhile also verified on ctwm with 4 screens. |