Issue metadata
Sign in to add a comment
|
Eve UI won't start up after flashing Chrome |
||||||||||||||||||||||
Issue descriptionCrOS Version: 9956.0.0 I'm trying to flash Chrome from ToT onto my Eve using deploy_chrome. Whenever I try, the UI will not start up. Logs attached. Relevant logs seem to be these: 2017-09-19T16:06:49.853175-07:00 INFO session_manager[8018]: [INFO:browser_job.cc(140)] Running child /opt/google/chrome/chrome --ui-prioritize-in-gpu-process --use-gl=egl --enable-native-gpu-memory-buffers --enable-drm-atomic --enable-hardware-overlays=single-fullscreen,single-on-top --enable-webgl-image-chromium --enable-features=Pepper3DImageChromium,PointerEvent,EnableBackgroundBlur --gpu-sandbox-failures-fatal=yes --enable-logging --log-level=1 --use-cras --enable-wayland-server --user-data-dir=/home/chronos --max-unused-resource-memory-usage-percentage=5 --system-developer-mode --force-clamshell-power-button --login-profile=user --has-chromeos-keyboard --enable-touchview --enable-voice-interaction --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/oem_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/oem_small.jpg --default-wallpaper-is-oem --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --arc-availability=officially-supported --enable-arc-oobe-optin --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --enable-logging=stderr --log-level=1 --login-manager --policy-switches-begin --enable-features=InstantTethering --policy-switches-end --vmodule=*arc/*=1,tablet_power_button_controller=1,*chromeos/login/*=1,auto_enrollment_controller=1,*plugin*=2,*zygote*=1,*/ui/ozone/*=1,*/ui/display/manager/chromeos/*=1,power_button_observer=2,webui_login_view=2,lock_state_controller=2,webui_screen_locker=2,screen_locker=2,*blue*=3 --vmodule=device_event_log*=3 2017-09-19T16:06:50.296162-07:00 WARNING crash_reporter[8440]: [user] Received crash notification for chrome[8365] sig 6, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly) 2017-09-19T16:06:50.299189-07:00 INFO session_manager[8018]: [INFO:child_exit_handler.cc(77)] Handling 8365 exit. 2017-09-19T16:06:50.299757-07:00 ERR session_manager[8018]: [ERROR:child_exit_handler.cc(85)] Exited with signal 6 2017-09-19T16:06:50.299790-07:00 INFO session_manager[8018]: [INFO:session_manager_service.cc(301)] Exiting process is chrome. 2017-09-19T16:06:50.299807-07:00 INFO session_manager[8018]: [INFO:browser_job.cc(149)] Terminating process group: Ensuring browser processes are gone. 2017-09-19T16:06:50.299824-07:00 INFO session_manager[8018]: [INFO:system_utils_impl.cc(95)] Sending 9 to -8365 as 1000 2017-09-19T16:06:50.301465-07:00 WARNING session_manager[8018]: [WARNING:session_manager_service.cc(325)] Child stopped, shutting down 2017-09-19T16:06:50.301572-07:00 INFO session_manager[8018]: [INFO:session_manager_service.cc(498)] SessionManagerService quitting run loop 2017-09-19T16:06:50.301613-07:00 INFO session_manager[8018]: [INFO:session_manager_service.cc(202)] SessionManagerService exiting 2017-09-19T16:06:50.302562-07:00 WARNING session_manager[8018]: [WARNING:session_manager_main.cc(227)] session_manager exiting with code 2 2017-09-19T16:06:50.304163-07:00 WARNING kernel: [ 70.372831] init: ui main process (8018) terminated with status 2 2017-09-19T16:06:50.324126-07:00 NOTICE ui-respawn[8527]: Rebooted too much; running respawn logic. 2017-09-19T16:06:50.326311-07:00 NOTICE ui-respawn[8532]: ui failed with exit status 2. 2017-09-19T16:06:50.330688-07:00 NOTICE ui-respawn[8547]: Reached respawn limit for ui.
,
Sep 20 2017
I remember seeing a similar issue on Kevin yesterday with certain build. I will try to this tomorrow.
,
Sep 20 2017
+xdai/vadimt, the current gardeners.
,
Sep 20 2017
As discussed over chat with Kyle, this appears to be a chrome crash on startup in TOT that needs to be bisected
,
Sep 20 2017
This regression is caused by https://chromium-review.googlesource.com/c/chromium/src/+/668739. This CL causes Chrome to crash when loading up on CrOS.
,
Sep 20 2017
Xiaochu is reverting: https://chromium-review.googlesource.com/c/chromium/src/+/674040
,
Sep 20 2017
CL has been reverted. Xiaochu, please test your change on Eve before re-submitting - thanks!
,
Sep 20 2017
What was the exact cause of the crash? Did Chrome log the reason it was aborting?
,
Sep 20 2017
derat@: See the logs on my original post on this issue. I didn't see any specific reason for the crash - not sure.
,
Sep 20 2017
[8061:8155:0919/160648.719767:ERROR:bus.cc(552)] Failed to get the ownership of org.chromium.ComponentUpdaterService: Connection ":1.109" is not allowed to own the service "org.chromium.ComponentUpdaterService" due to security policies in the configuration file ... [8061:8061:0919/160648.900252:FATAL:cros_dbus_service.cc(76)] Failed to own: org.chromium.ComponentUpdaterService I think that deploy_chrome should've rebooted your device to pick up the updated D-Bus configuration. Do you remember if that happened? Did you try rebooting manually?
,
Sep 20 2017
Yes, it did reboot my machine, and I also did try rebooting manually. I also tried flashing to different CrOS versions (from Goldeneye), but none of these things fixed this issue.
,
Sep 20 2017
Do you (or did you) have a /opt/google/chrome/dbus/org.chromium.ComponentUpdaterService.conf file? For what it's worth, I have it on an eve system that I'd deployed Chrome to while I think this change was in, and I didn't experience any problems with Chrome failing to take ownership of the service name. Not sure what the reason is for the difference. We've had problems around mysterious D-Bus permission failures in the past, but I don't know that the cause was ever found.
,
Sep 20 2017
I've attached the org.chromium.ComponentUpdaterService.conf that is currently on my machine (note that I've flashed and rebooted it a few times since I experienced this bug, so it may have changed).
,
Sep 20 2017
I'm hitting this same issue on cyan with org.chromium.VirtualFileRequestService from: https://chromium-review.googlesource.com/c/chromium/src/+/662088 [25718:25718:0920/132305.061223:FATAL:cros_dbus_service.cc(76)] Failed to own: org.chromium.VirtualFileRequestService #0 0x5edce00eb4dc base::debug::StackTrace::StackTrace() #1 0x5edce01013ce logging::LogMessage::~LogMessage() #2 0x5edce0ac4006 chromeos::CrosDBusServiceImpl::OnOwnership() #3 0x5edcdf43091d _ZN4base8internal7InvokerINS0_9BindStateINS_17RepeatingCallbackIFvRKNS_8FilePathEbEEEJS4_bEEEFvvEE3RunEPNS0_13BindStateBaseE #4 0x5edce00ebcd9 base::debug::TaskAnnotator::RunTask() #5 0x5edce0107017 base::MessageLoop::RunTask() #6 0x5edce0107816 base::MessageLoop::DoWork() #7 0x5edce0109199 base::MessagePumpLibevent::Run() #8 0x5edce0129d3a base::RunLoop::Run() #9 0x5edcdfdf8d28 ChromeBrowserMainParts::MainMessageLoopRun() #10 0x5edcde9f7fe4 content::BrowserMainLoop::RunMainMessageLoopParts() #11 0x5edcde9fa792 content::BrowserMainRunnerImpl::Run() #12 0x5edcde9f37bc content::BrowserMain() #13 0x5edcdfdcc64c content::ContentMainRunnerImpl::Run() #14 0x5edcdfdee87f service_manager::Main() #15 0x5edcdfdcb511 content::ContentMain() #16 0x5edcde352b35 ChromeMain #17 0x75358ebcd736 __libc_start_main #18 0x5edcde352919 _start Dan is taking a look at my device; fingers crossed we find a fix/workaround.
,
Sep 20 2017
msw/hashimoto: There's another with similar symptoms today - see issue 767107 .
,
Sep 20 2017
Possible workaround: "killall -HUP dbus-daemon". (This seems to be doing something that rebooting the system doesn't!)
,
Sep 20 2017
I found an eve and chrome-deploy prompts me to reboot due to dbus change. Then after reboot, UI works fine and my new API works as well. my chrome os is 63.0.3221.0
,
Sep 20 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by abodenha@chromium.org
, Sep 19 2017Status: Assigned (was: Untriaged)