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

Issue 914492 link

Starred by 1 user

Issue metadata

Status: Closed
Owner:
Closed: Dec 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Settings UI: "Open Settings" button seems broken?

Project Member Reported by dpa...@chromium.org, Dec 12

Issue description

See screencast where the "Open settings" button seems to forward the user to some subpage that does not exist? Which leads to the user being forwarded back to the top level chrome://settings page?

I am a bit confused about what is happening, but it definitely seems broken.

@tangltom: Can you take a look?
 
open_settings_button.mp4
854 KB View Download
Labels: -Pri-3 OS-Linux OS-Mac OS-Windows Pri-2
Status: Started (was: Assigned)
I see, the button should probably be hidden when unity is off.

One question: The sync link below works just fine?
Status: Assigned (was: Started)
Okay, I just had the exact same error with my test account and the button worked perfectly fine (when unity is disabled).

Is the account you are using a special account? (i.e. sync not allowed, managed, ...?)
stub-user@example.com is a weird account that appears if you first launch 
ChromeOS (on Linux) with a certain profile folder (say /tmp/test_profile), and then launch Chrome on Linux with the same profile folder.
Okay, so this is the ChromeOS standard test profile then?
Is this really a bug or did this just happen because you accidentally used the same profile folder for ChromeOS and Chrome?
> Is this really a bug

I don't know if this is a state where a regular user can get into. Filed this bug hoping that you (or someone else) could tell whether this is a real bug.

> accidentally used the same profile folder for ChromeOS and Chrome?

That is indeed how I ended up in this situation.
Status: Closed (was: Assigned)
From my understanding this is not a real bug :)
Especially since I ended up in the exact same state and everything worked as intended.
Hence closing it.

If your problem should occur again in a real scenario, which I don't think it will, please reopen.

Sign in to add a comment