New issue
Advanced search Search tips

Issue 706021 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Chromebook signs out when lid closed

Reported by kallie.j...@isd97.org, Mar 28 2017

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS armv7l 9202.56.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.123 Safari/537.36
Platform: 9202.56.1 (Official Build) stable-channel daisy

Steps to reproduce the problem:
1. Just close Samsung Chromebook
2. Open it
3. 

What is the expected behavior?
It is supposed to resume your session.

What went wrong?
I opened it and it restarts the computer. It doesn't even give a chance to restore opened tabs.

Did this work before? Yes (See other comments)

Chrome version: 57.0.2987.123  Channel: stable
OS Version: 9202.56.1
Flash Version: Shockwave Flash 25.0 r0

It worked two updates before.
 
Components: OS>Kernel>Power

Comment 2 by derat@chromium.org, Apr 19 2017

Labels: Needs-Feedback
Feedback report at http://feedback/#/Report/55208773484 -- thanks!

When I look at powerd.PREVIOUS from the report, it indicates that in the previous boot, the system shut down due to an explicit request from Chrome:

[0317/110732:INFO:suspend_delay_controller.cc(63)] Registering suspend delay 67305476 (chrome) of 5000 ms on behalf of :1.54
[0317/110732:INFO:suspend_delay_controller.cc(63)] Registering dark suspend delay 67338243 (chrome) of 5000 ms on behalf of :1.54
[0317/110732:INFO:daemon.cc(1065)] D-Bus org.chromium.LibCrosService ownership changed to :1.54
...
[0317/113353:INFO:daemon.cc(1145)] Got RequestShutdown message from :1.54
...
[0317/113353:INFO:daemon.cc(1503)] Shutting down, reason: user-request
[0317/113353:INFO:main.cc(240)] Launching "/usr/bin/powerd_setuid_helper --action=shut_down --shutdown_reason=user-request"

Can you file another feedback report with Alt+Shift+i immediately after reproducing the problem and logging back in?

Comment 3 by derat@chromium.org, May 1 2017

Status: WontFix (was: Unconfirmed)
Please file another feedback report immediately after you see the problem as described in #2 and then ping the bug so it can be reopened. Thanks!
How do I "ping" a bug?

Comment 5 by derat@chromium.org, May 1 2017

Components: Enterprise
Labels: -Needs-Feedback
Status: Unconfirmed (was: WontFix)
Summary: Chromebook signs out when lid closed (was: Chrome Book Shuts Off When Lid Shuts)
Sorry, I meant "comment on the bug to let us know that you've submitted a new feedback report." You just did. :-)

http://feedback/#/Report/58013059257

I don't think that the system is shutting down when you close the lid. Rather, it's signing you out, and it looks like this is happening because it's been configured to do that (presumably via enterprise policy, because that's the only way to request this):

----

...
[0419/082350:INFO:daemon.cc(1431)] Session state changed to started
[0419/082350:INFO:state_controller.cc(757)] Updated settings: dim=5m screen_off=6m lock=0s idle_warn=0s idle=10m (shutdown) lid_closed=shutdown use_audio=1 use_video=1
[0419/082352:INFO:daemon.cc(1359)] Received updated external policy: ac_dim=7m ac_screen_off=8m ac_lock=8m10s ac_idle_warn=0s ac_idle=30m battery_dim=5m battery_screen_off=6m battery_lock=6m10s battery_idle_warn=0s battery_idle=10m ac_idle=suspend battery_idle=suspend lid_closed=logout use_audio=1 use_video=1 presentation_factor=2.0 user_activity_factor=2.0 wait_for_initial_user_activity=0 force_nonzero_brightness_for_user_activity=1 (Prefs)
[0419/082352:INFO:state_controller.cc(757)] Updated settings: dim=5m screen_off=6m lock=6m10s idle_warn=0s idle=10m (suspend) lid_closed=logout use_audio=1 use_video=1
...
[0419/082501:INFO:daemon.cc(507)] Lid closed
...
[0419/082501:INFO:state_controller.cc(899)] Ready to perform lid-closed action (logout)
[0419/082503:INFO:daemon.cc(1431)] Session state changed to stopped

----

Can you confirm that this device is enrolled?
It's owned by a school.
Screenshot 2017-05-01 at 11.47.01.png
4.3 KB View Download

Comment 7 by derat@chromium.org, May 1 2017

Status: WontFix (was: Unconfirmed)
This behavior is configured by the device's administrator. If you'd like it to behave differently, you'll need to ask them to change the policy.
Is there a way to fix it for myself on my end? They probably did that for a reason, so I don't want to mess with the IT person.

Comment 9 by derat@chromium.org, May 1 2017

Nope, the administrator is the only person who can change this.
Okay! Thank you for your help through all of this. 

Sign in to add a comment