New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 754863 link

Starred by 1 user
Status: Fixed
Owner:
rjkroege@chromium.org
Closed: Oct 24
Cc:
rjkroege@chromium.org
█ dongseon...@intel.com
mustash-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Update documentation at https://www.chromium.org/developers/mus-ash

Project Member Reported by joone....@intel.com, Aug 11 2017 
Chrome Version: 62.0.3182.0
OS: (ChromeOS.)

What steps will reproduce the problem?
(1) Build CrOS(#493528) with mash:all
(2) Boot CrOS on Chromebook(ASUS C302)
(3) Run ./mash --service=mash_session --window-manager=simple_wm using sshfs and ssh

What is the expected result?
There is quick_launch on Mash desktop and we can type a text into the input field in quick_launch. 

What happens instead?
There is only a cursor in black screen.

Without --window-manager, quick_launch is shown, but typing doesn't work.

Here are logs:

chronos@localhost /opt/google/chrome/out $ ./mash --service=mash_session  --window-manager=simple_wm                                             
[12711:12713:0811/142412.617429:5761956882:INFO:service_process_launcher.cc(196)] Launched child process pid=12714, instance=, name=mash_session, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84
[12711:12721:0811/142412.639681:5761978969:INFO:service_process_launcher.cc(196)] Launched child process pid=12722, instance=, name=quick_launch, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84
[12711:12713:0811/142412.640071:5761979360:INFO:service_process_launcher.cc(196)] Launched child process pid=12723, instance=, name=simple_wm, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84
[12711:12721:0811/142412.661141:5762000421:INFO:service_process_launcher.cc(196)] Launched child process pid=12739, instance=, name=ui, user_id=02373fa3-04aa-4e67-b84a-18ea59da8a6d
[12711:12713:0811/142412.696559:5762035844:INFO:service_process_launcher.cc(196)] Launched child process pid=12747, instance=, name=font_service, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84 ./mash --service=mash_session  --window-manager=simple_wm 
device-enumerator: scan all dirs
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
[12739:12758:0811/142413.084513:5762423812:ERROR:vaapi_wrapper.cc(1197)] Could not get a valid VA display
[12739:12739:0811/142413.488620:5762827900:ERROR:screen_manager_ozone_internal.cc(302)] Not implemented reached in virtual void display::ScreenManagerOzoneInternal::CloseMirroringDisplayIfNotNecessary()
[12723:12723:0811/142413.490461:5762829836:ERROR:screen_base.cc(44)] Not implemented reached in virtual display::Display display::ScreenBase::GetDisplayNearestWindow(gfx::NativeWindow) const
device-enumerator: scan all dirs ./mash --service=mash_session  --window-manager=simple_wm 
  device-enumerator: scanning /sys/bus
  device-enumerator: scanning /sys/class
[12739:12739:0811/142413.518899:5762858176:ERROR:screen_manager_ozone_internal.cc(302)] Not implemented reached in virtual void display::ScreenManagerOzoneInternal::CloseMirroringDisplayIfNotNecessary()
[12723:12723:0811/142413.525192:5762864468:ERROR:layer_tree_host_impl.cc(2415)] Forcing zero-copy tile initialization as worker context is missing
[12723:12723:0811/142413.566939:5762906217:ERROR:screen_base.cc(20)] Not implemented reached in virtual gfx::Point display::ScreenBase::GetCursorScreenPoint()
[12722:12722:0811/142413.575663:5762914980:ERROR:layer_tree_host_impl.cc(2415)] Forcing zero-copy tile initialization as worker context is missing

Comment 1 by joone....@intel.com, Aug 11 2017

Cc: rjkroege@chromium.org

Comment 2 by joone....@intel.com, Aug 11 2017

Description: Show this description

Comment 3 by joone....@intel.com, Aug 11 2017

Cc: dongseon...@intel.com

Comment 4 by rjkroege@chromium.org, Aug 11 2017

Status: WontFix (was: Untriaged)
AFAIK, this isn't a supported config.

On your Chromebook, 

sudo -u chronos ./chrome --mash --user-data-dir=/home/chronos --homedir=/ --login-manager

will run Chrome in mash mode. Or any ChromeOS build of Chrome (for ozone x11 or ozone wayland) should run with --mash or --mus on your desktop (x11 or wayland respectively)

I'm marking WontFix based on this. Please re-open if you think that I'm confused.

Comment 5 by joone....@intel.com, Aug 12 2017 

I just followed the instructions in https://www.chromium.org/developers/mus-ash.
Is this only for a testing purpose in desktop? or was this way of launching Mash apps using mash executable file deprecated?

Comment 6 by rjkroege@chromium.org, Aug 14 2017

Components: -MUS Internals>MUS
Owner: rjkroege@chromium.org
Status: Assigned (was: WontFix)
Summary: Update documentation at https://www.chromium.org/developers/mus-ash (was: No UI when running ./mash --service=mash_session --window-manager=simple_wm on Chromebook)
The page you reference is obsolete. I think it's fair to re-open this bug as "freshen the doc s at https://www.chromium.org/developers/mus-ash"

Comment 7 by lafo...@chromium.org, Feb 26 2018

Components: -Internals>MUS Internals>Services>WindowService

Comment 8 by rjkroege@chromium.org, Oct 24

Status: Fixed (was: Assigned)
fixed. website has been updated.
►

Sign in to add a comment