Issue metadata
Sign in to add a comment
|
Chromium doesn't respect $DISPLAY
Reported by
ingo.bu...@googlemail.com,
Oct 11 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36 Steps to reproduce the problem: 1. Start X on VT1 and open a Chrome session. 2. Start another X on VT2 and try to open a Chrome session. This doesn't work even when using --user-data-dir without value to force a new session. What is the expected behavior? Chromium opens on the X running on VT2. What went wrong? Chromium opens on the X running on VT1. Did this work before? N/A Chrome version: 53.0.2785.143 Channel: stable OS Version: 4.7 Flash Version: Shockwave Flash 23.0 r0 This requires weird workarouns like [1]. Respecting the $DISPLAY variable is part of complying with the X specification and Chromium violates this. [1] https://productforums.google.com/forum/#!msg/chrome/NGs-B3sPiX8/3aBj7VPn9AUJ |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by thomasanderson@chromium.org
, Oct 11 2016Status: Duplicate (was: Unconfirmed)