New issue
Advanced search Search tips

Issue 783308 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Files app doesnt show SD card on first login

Reported by urja...@gmail.com, Nov 9 2017

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS armv7l 10106.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3261.0 Safari/537.36
Platform: 10106.0.0 (Official Build) dev-channel veyron_speedy

Steps to reproduce the problem:
1. Boot with SD card inserted
2. Open Files app after login
3. SD card not listed

What is the expected behavior?
SD card is listed.(And is listed if you re-login with Ctrl-Shift-Q.)

What went wrong?
The log in /var/log/ui/ui.(relevant time) has these lines:

[1206:1206:1109/032808.815606:ERROR:object_proxy.cc(575)] Failed to call method: org.chromium.CrosDisks.EnumerateAutoMountableDevices: object_path= /org/chromium/CrosDisks: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.CrosDisks was not provided by any .service files
[1206:1206:1109/032808.815714:ERROR:volume_manager.cc(943)] Failed to refresh disk mount manager
[1206:1206:1109/032810.518813:ERROR:object_proxy.cc(575)] Failed to call method: org.chromium.UpdateEngineInterface.GetEolStatus: object_path= /org/chromium/UpdateEngine: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.UpdateEngine was not provided by any .service files
[1206:1206:1109/032810.518937:ERROR:update_engine_client.cc(425)] Failed to request getting eol status

So i guess the disks service didnt start early enough (or there is something else wrong...), but I dont know why.

Did this work before? N/A 

Chrome version: 64.0.3261.0  Channel: dev
OS Version: 10106.0.0
Flash Version: 27.0.0.183
 
Components: Platform>Apps>FileManager
Labels: CrOS-FilesApp
Status: Untriaged (was: Unconfirmed)
<files-triage>

Comment 3 by sashab@chromium.org, Feb 28 2018

Labels: -CrOS-FilesApp

Comment 4 by sashab@chromium.org, Mar 28 2018

Status: Unconfirmed (was: Untriaged)

Comment 5 by dats@chromium.org, Apr 6 2018

Labels: Needs-Feedback
Tried a few times - works fine for me. From what I see in the log your system got in some weird state when dbus is not configured properly, which explains why you wouldn't see removable media. As configuration for CrosDisks is in /etc which is read-only I'm not sure how that would happen though and what needs to be done to reproduce this. Is it still a problem?

Comment 6 by urja...@gmail.com, Apr 6 2018

I havent seen this in a while (it was reproducible enough back then in my very specific setup to get really annoying, but i guess it disappeared at some time).

I was assuming it was some kind of a race with the UI starting faster than CrosDisks (since it worked on the second try), but for now i guess this can be closed...
Project Member

Comment 7 by sheriffbot@chromium.org, Apr 6 2018

Cc: dats@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by dats@chromium.org, Apr 8 2018

Status: WontFix (was: Unconfirmed)
Thanks for the update!

Sign in to add a comment