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

Issue 593013 link

Starred by 4 users
Status: WontFix
Owner: ----
Closed: Dec 2016
Cc:
ew...@chromium.org
pucchakayala@chromium.org
msarda@chromium.org
█ bzanotti@chromium.org
█ brajkumar@chromium.org
█ samueltan@chromium.org
songsuk@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

chrome is unable to open profile correctly

Reported by ba...@hasdemir.com, Mar 8 2016 
UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0

Steps to reproduce the problem:
1. exit chrome
2. kill all chrome processes
3. opened chrome without having the error in title
4. created a user and changed to the new user
5. deleted all users, 
6. exited chrome
7. killed all chrome processes
8. sudo apt-get remove --purge google-chrome-*
9. rm -rf ~/.config/google-chrome*
10. sudo gdebi /tmp/google-chrome-stable_current_amd64.deb
11. Problem is back after first exit.

What is the expected behavior?
Chrome should be able to read user profile correctly. 

What went wrong?
Receive a dialog window with an error copied below:

Your profile could not be opened correctly. 

Some features may be unavailable. Please check that the profile exists and you have eprmission to read and write its contents. 

Did this work before? Yes previous version. see 344358

Chrome version: 49.0.2623.75-1  Channel: stable
OS Version: Debian 7.4
Flash Version: not sure

https://bugs.chromium.org/p/chromium/issues/detail?id=344358

Comment 1 by brajkumar@chromium.org, Mar 10 2016

Cc: brajkumar@chromium.org
Components: UI>Browser>Profiles
Labels: Needs-Feedback
Unable to reproduce the issue on Ubuntu 14.04 using chrome latest stable M49-49.0.2623.87 by following steps mentioned in the above comment. Observed chrome is able to open the profile without any error as expected.

Please follow the below steps to repair this issue, In case if issue is still seen let us know.
1.Quit Google Chrome.
2.Open terminal and Change directory (cd) to ~/.config/google-chrome/Default
3.Delete the file named “Web Data”:  rm -rf Web\ Data;
4.Start Google Chrome and the error should be gone.

Comment 2 by ba...@hasdemir.com, Mar 10 2016 

Issue is still present after repair steps.

1. quit Google Chrome
2. killed all Chrome processes
3. Open terminal and Change directory (cd) to ~/.config/google-chrome/Default
4. Delete the file named “Web Data”:  rm -rf Web\ Data;
5. Start Google Chrome and the error is gone
6. quit Google Chrome
7. Start Google Chrome and the error is still present


This issue is reproducible constantly on my machine. Happy to help if I can.
Project Member

Comment 3 by sheriffbot@chromium.org, Mar 10 2016

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Status: Assigned (was: Unconfirmed)
Thank you for providing more feedback. Assigning to requester "brajkumar@chromium.org" for another review.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by ba...@hasdemir.com, Mar 29 2016 

This is issue is still persistent with version 49.0.2623.110

Comment 5 by samueltan@chromium.org, Mar 29 2016

Cc: samueltan@chromium.org
I have been running into this problem on my corp account with samus since the end of 2015. This is reproducible on my device, everytime I log into my corp account.

Comment 6 by ligim...@chromium.org, Apr 29 2016

Cc: songsuk@chromium.org pucchakayala@chromium.org
Labels: -Needs-Review Arch-MIPS M-52 OS-Chrome
Owner: ----
Status: Unconfirmed (was: Assigned)
Routing for further triage to Geetha/Song.
Project Member

Comment 7 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

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

Comment 8 by abodenha@chromium.org, Jun 2 2016

Labels: -OS-Chrome
Project Member

Comment 9 by sheriffbot@chromium.org, Jul 15 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

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

Comment 10 by sheriffbot@chromium.org, Dec 19 2016

Cc: ew...@chromium.org bzanotti@chromium.org msarda@chromium.org
Status: WontFix (was: Unconfirmed)
--Chrome Identity automated triaging--

This bug is Unconfirmed and has gone two weeks without any activity, so it is being closed as WontFix. Please re-open if this is still a valid and reproducible bug or feature request and mark it as Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

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

Sign in to add a comment