[Kevin/Cyan] By default crash reporting is disabled. |
|||||
Issue description
Chrome Version: M59-9449.0.0
OS: Chrome
Devices: Kevin and Cyan
What steps will reproduce the problem?
(1) sign in to the device.
(2) Trigger any crash. (Kernel/Process/Browser)
"sudo pkill -SEGV powerd"
or
"chrome://crash"
What is the expected result?
Kernel and process Crashes should create crash dmp files at /var/spool/crash directory .
Browser crashes should create crash dmp files at /home/chronos/user/crash directory.
What happens instead?
Crash dmps are not generated.
Please use labels and text to provide additional information.
For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
,
Apr 10 2017
,
Apr 10 2017
> By default crash reporting is disabled on these devices. err, what ? there is no board-specific logic wrt enabling of crash reports. the log message indicates everything is WAI: 2017-04-10T15:21:07.248102-07:00 WARNING crash_reporter[4261]: [user] Received crash notification for powerd[1343] sig 11, user 228 (ignoring - no consent) if you didn't agree to send crashes at OOBE time, then crashes aren't going to be sent ...
,
Apr 13 2017
Observed the same on Daisy with version 9457.0.0/59.0.3068.1.
,
Apr 14 2017
,
Apr 14 2017
@Comment 4 On OOBE we did not change the send crashes option. But after login we noticed send crashes option is disabled in settings. We are facing this issue randomly. Not able to reproduce this issue after re-imaging the device.
,
Apr 14 2017
what setting ? "Automatically send diagnostic and usage data to Google" ? if the device is enrolled, you probably can't toggle it. it's also not available in guest mode. please provide concrete details. this report is still too vague.
,
Jul 20 2017
,
Aug 4 2017
Not able to reproduce this issue on 9807.0.0 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by son...@google.com
, Apr 10 2017