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

Issue 650403 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 652326
Owner: ----
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Getting bash warning messages after opening crosh and shell in VT1

Project Member Reported by son...@google.com, Sep 26 2016

Issue description

Version: 8838.0.0
OS: chromeOS

What steps will reproduce the problem?
(1) Sign in to the device.
(2) Open crosh (Ctrl + Alt + t) and run shell.


What is the expected output?
Should not get any warning messages.


What do you see instead?
Getting bash warning messages after opening crosh and shell in VT1
=============================================
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
Loading extra module: /usr/share/crosh/dev.d/50-crosh.sh
Welcome to crosh, the Chrome OS developer shell.

If you got here by mistake, don't panic!  Just close this tab and carry on.

Type 'help' for a list of commands.

crosh> shell
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
chronos@localhost / $ 
================================================


Please use labels and text to provide additional information.



Note: able to reproduce this issue in VT2.

 

Comment 1 by son...@google.com, Sep 26 2016

Screenshot and logs are present at https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cros/650403/?debugUI=CLOUD


Note: Not able to reproduce this issue from VT2
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 27 2016

Labels: Hotlist-Google

Comment 3 by ka...@chromium.org, Sep 27 2016

Components: -OS>Kernel Platform>Apps>Shell Platform>Apps>Default
Labels: crosh
Mergedinto: 652326
Status: Duplicate (was: Untriaged)
Better info in the newer bug. Plus,  bug 652326  actually can occur in verified mode, so it's probably a bigger deal.
^^ My comment about verified mode doesn't really make a lot of sense. And in fact, the details here are relevant; the issues is NOT seen from shells not launched via Chrome. Anyway, solution is forthcoming in the dup'd bug.

Sign in to add a comment