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

Issue 729843 link

Starred by 3 users
Status: Duplicate
Merged: issue 777490
Owner:
ka...@chromium.org
Closed: Aug 17
Cc:
█ rpattumani@chromium.org
ka...@chromium.org
sontis@chromium.org
dsunk...@chromium.org
█ josa...@chromium.org
harpreet@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

/var/spool/crash/ folder has lsb-release & os-release files

Project Member Reported by dsunk...@chromium.org, Jun 6 2017 
Chrome Version: M60-9592.8.0
OS: Chrome

What steps will reproduce the problem?
(1) Install M60 release on chromebook.
(2) Check /var/spool/crash directory
(3) lsb-release & os-release files are present.

What is the expected result?
lsb-release & os-release files should not be there in this folder.

What happens instead?
lsb-release & os-release files are present in /var/spool/crash directory

Comment 1 by ka...@chromium.org, Jun 6 2017

Labels: -Pri-3 Pri-2
Hi  dsunkara@, can you provide some more info?

What does 'install' mean? 
When are these files observed there? OOBE? User login?
Is this Enterprise enrolled device? CfM?
Can you find these files where they should be located?
How consistent is this?

Comment 2 by ka...@chromium.org, Jun 6 2017

Cc: josa...@chromium.org

Comment 3 by dsunk...@chromium.org, Jun 6 2017 

Hi Kalin,

Install means imaging chromebook either with test build or recovery image. 
These files are observed always on M60 release. At OOBE, user login etc. I have not observed yet when these are removed from the directory (may be after crash_sender task is complete, I still have to check). 
These files are observed in both enterprise enrolled devices and on chromebooks on both recovery builds and test image builds. 
Yes, I find these files in /etc/lsb-release too.

Comment 4 by ka...@chromium.org, Jun 6 2017

Labels: Stability-Crash
+ Stability-Crash, as to get input from anyone who might know more.

I can reproduce this just by recovering a device(cyan) and checking /var/spool/crash at OOBE stage.

Comment 5 by harpreet@chromium.org, Jun 30 2017

Cc: rpattumani@chromium.org

Comment 6 by dsunk...@chromium.org, Jul 7 2017

Labels: M-61
Same issue is observed on M61 as well. 
61 / 9718.0.0 / 61.0.3150.0

Comment 7 by harpreet@chromium.org, Jul 18 2017

Owner: ka...@chromium.org
kalin@ - could you please help route this as needed. Thanks

Comment 8 by dsunk...@chromium.org, Nov 8 2017

Labels: M-64 M-63

Comment 9 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Untriaged)

Comment 10 by vapier@chromium.org, Aug 17

Components: -OS>Installer -Internals>Installer OS>Systems>CrashReporting
Labels: -Restrict-View-Google
Mergedinto: 777490
Status: Duplicate (was: Assigned)
we addressed this in  crbug.com/777490  by moving the files to a /var/lib path
►

Sign in to add a comment