[Konsole-devel] [Bug 297224] Command-line options ignored when stdout redirected to /dev/null

Jekyll Wu adaptee at gmail.com
Wed Apr 25 12:10:43 UTC 2012


https://bugs.kde.org/show_bug.cgi?id=297224

--- Comment #4 from Jekyll Wu <adaptee at gmail.com> ---
Thanks for your feedback and sorry for the delay of the reply.

> The way I understand your explanation, one of my observations is not
> explained:
>     session-on-display 0 $ konsole --display 1:0
> new konsole session opens on display 1:0
>     session-on-display 1 $ konsole
> another new konsole session opens on display 1:0, as expected
>     session-on-display 1 $ konsole > /dev/null
> a new konsole session opens on display 0, whereas it is obviously expected
> on display 1.
> 

I don't have or use that two display enviroment, so I can only do some
guessing. 

This line "session-on-display 0 $ konsole --display 1:0" is important. Is it
executed in an existing Konsole window opened through icon/menu/shortcut, or is
it executed in a xterm and no konsole is running at all?. If it is the first
case, then the last invocation can be explained. The selection of reusable
konsole process is dbus-based(That is how KUniqueApplication works), so display
does not make difference here. If the first reusable konsole process shows on
display 0, then all following reusing attempt will open konsole window on
display 0.

And I think that DBUS_SESSION_BUS_ADDRESS is the right behavior. You are using
two displays in the same user session, right? Then DBUS_SESSION_BUS_ADDRESS
should be same regardless of display if I understand it correctly.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the konsole-devel mailing list