#596357 chromium-browser: Still fails to honour $DISPLAY properly.

Package:
src:chromium
Source:
chromium
Submitter:
Cyril Brulebois
Date:
2018-12-04 12:57:13 UTC
Severity:
minor
#596357#5
Date:
2010-09-10 16:44:49 UTC
From:
To:
Hi,

even though #587398 was kind of addressed, chromium is still not
honouring DISPLAY (or --display as the manpage claims it does) properly.
Indeed, if chromium is started on :0, and then one tries one of those:
  DISPLAY=:1 chromium-browser
  chromium-browser --display :1

a new browser window is opened on :0.

A trivial way to reproduce this is to start an :1 display through:
  Xephyr :1

And sorry, no, I'm not opening a Google Account just to report the bug
upstream (which is what I'm prompted for if I click “New issue” or if I
follow the link in presubj).

Mraw,
KiBi.
#596357#10
Date:
2010-11-09 01:45:01 UTC
From:
To:
unarchive 587398
notfixed 587398 chromium-browser/6.0.472.36~r55963-1
notfixed 587398 chromium-browser/6.0.472.53~r57914-3
forcemerge 596357 587398
tags 596357 + upstream
forwarded 596357 http://crbug.com/15781
quit

Hi,

Cyril Brulebois wrote:

Actually I don't think #587398 was addressed at all.
#596357#29
Date:
2016-04-25 21:16:40 UTC
From:
To:
If you open second one with different profile, it should work.