Me he encontrado alguna vez con que Chrome soltaba un error diciendo que no podía abrir correctamente mi perfil.
Error: no se ha podido abrir correctamente tu perfil
Resulta bastante molesto ya que te impide acceder a la base de datos de usuarios y contraseñas habituales.
Para verificar el error, podemos ejecutar Google Chrome desde el terminal y podremos ver el siguiente error:
javi@casa:~$ google-chrome [8721:8749:0208/071704:ERROR:connection.cc(1060)] Web sqlite error 5, errno 0: database is locked, sql: PRAGMA journal_mode = PERSIST ATTENTION: default value of option force_s3tc_enable overridden by environment. [8721:8721:0208/071704:ERROR:connection.cc(1060)] sqlite error 5, errno 0: database is locked, sql: PRAGMA journal_mode = PERSIST [8721:8749:0208/071705:ERROR:connection.cc(1060)] Web sqlite error 5, errno 0: database is locked, sql: PRAGMA cache_size=32 [8721:8749:0208/071705:ERROR:connection.cc(1060)] Web sqlite error 5, errno 0: database is locked, sql: CREATE TABLE meta(key LONGVARCHAR NOT NULL UNIQUE PRIMARY KEY, value LONGVARCHAR) [8721:8749:0208/071705:ERROR:web_data_service_backend.cc(54)] Cannot initialize the web database: 1 [8721:8721:0208/071705:ERROR:connection.cc(1060)] sqlite error 5, errno 0: database is locked, sql: PRAGMA cache_size=32 [8721:8721:0208/071705:ERROR:connection.cc(1060)] sqlite error 5, errno 0: database is locked, sql: CREATE TABLE meta(key LONGVARCHAR NOT NULL UNIQUE PRIMARY KEY, value LONGVARCHAR) [8721:8721:0208/071705:ERROR:password_store_factory.cc(136)] Could not initialize login database. [8721:8721:0208/071705:ERROR:desktop_window_tree_host_x11.cc(810)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType) [8721:8721:0208/071705:ERROR:desktop_window_tree_host_x11.cc(810)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType) [8721:8721:0208/071705:ERROR:desktop_window_tree_host_x11.cc(810)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType) [8721:8721:0208/071705:ERROR:desktop_window_tree_host_x11.cc(810)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType) [8721:8749:0208/071705:ERROR:connection.cc(1060)] Quota sqlite error 5, errno 0: database is locked, sql: UPDATE OriginInfoTable SET used_count = ?, last_access_time = ? WHERE origin = ? AND type = ? [8721:8721:0208/071705:ERROR:CONSOLE(0)] "Error in event handler for (unknown): TypeError: Cannot read property 'length' of undefined at setElemhideCSSRules (chrome-extension://cfhdojbkjhnklbpkdaibdccddilifddb/include.preload.js:175:18)", source: https://www.google.es/_/chrome/newtab?espv=2&ie=UTF-8 (0) [8721:8749:0208/071706:ERROR:connection.cc(1060)] Quota sqlite error 5, errno 0: database is locked, sql: UPDATE OriginInfoTable SET last_modified_time = ? WHERE origin = ? AND type = ? [8721:8749:0208/071706:ERROR:connection.cc(1060)] Quota sqlite error 5, errno 0: database is locked, sql: UPDATE OriginInfoTable SET last_modified_time = ? WHERE origin = ? AND type = ? [8721:8749:0208/071706:ERROR:connection.cc(1060)] Quota sqlite error 5, errno 0: database is locked, sql: UPDATE OriginInfoTable SET last_modified_time = ? WHERE origin = ? AND type = ? [8721:8749:0208/071706:ERROR:connection.cc(1060)] Quota sqlite error 5, errno 0: database is locked, sql: UPDATE OriginInfoTable SET last_modified_time = ? WHERE origin = ? AND type = ? [8721:8721:0208/071715:ERROR:desktop_window_tree_host_x11.cc(810)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType) [8721:8721:0208/071719:ERROR:desktop_window_tree_host_x11.cc(810)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType)
Lo que está ocurriendo es que alguna de las extensiones de Chrome se ha quedado bloqueando la base de datos sqlite que chrome utiliza para almacenar datos de tu perfil. Vamos a solucionarlo.
Entramos al directorio de configuración de google chrome
javi@casa:~$ cd .config/google-chrome/Default/
Ejecutamos el siguiente comando. Este va a identiicar los archivos sqlite almacenados por google en su directorio de configuración, y matar los procesos que estén bloqueando la base de datos.
javi@casa:~/.config/google-chrome/Default$ find . -type f -exec file {} ; | grep -i SQLite | cut -d: -f1 | while read FILE; do fuser -k -TERM "$FILE"; done
/home/javi/.config/google-chrome/Default/QuotaManager: 3964
/home/javi/.config/google-chrome/Default/Login Data: 3964
Tras esto, Chrome vuelve a abrir sin problemas ni errores de que no puede acceder a nuestro perfil.