[Pkg-xfce-devel] Bug#715313: Bug#715313: xfce4-appfinder: Always displays on :0.0 (does not honor $DISPLAY)
corsac at debian.org
Mon Jul 8 05:45:14 UTC 2013
On dim., 2013-07-07 at 16:02 -0400, Mark Kamichoff wrote:
> Package: xfce4-appfinder
> Version: 4.10.1-1
> Severity: important
> It appears that xfce4-appfinder does not correctly honor the $DISPLAY
> variable and and always displays on :0.0. The --display= switch on the
> command line that is documented in xfce4-appfinder(1) is also ignored.
> For example, if the $DISPLAY variable is set to be :0.1, the
> xfce4-appfinder appears on :0.0. I have tried all of the following and
> xfce4-appfinder always displays on the :0.0 screen:
> % xfce4-appfinder --display=":0.1"
> % env DISPLAY=:0.1 xfce4-appfinder
> % export DISPLAY=:0.1
> % xfce4-appfinder
> This also happens when xfce4-appfinder is run as xfrun4.
> This makes it difficult to start applications on an X screen other than
> :0.0. No prior versions of xfce4-appfinder (xfrun4) exhibited this
> >From what I can tell no other Xfce4 utilities exhibit this problem.
I think the same thing will happen with xfce4-terminal once the first
window is opened (see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710002 for example).
xfce4-appfinder is actually run (as xfrun) as part of the session
startup in order to start fast when you call xfrun. That also means the
window will inherit settings of that process, for example the $DISPLAY.
I'm not too sure there are ways to workaround that. I'll forward the bug
upstream but in any case, you have to know that multiple $DISPLAY is not
usually something really supported when it comes to dbus-activated
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 490 bytes
Desc: This is a digitally signed message part
More information about the Pkg-xfce-devel