Public bug reported:
Upon launching chromium-browser from the terminal with the command:
$ chromium-browser --user-data-dir=/home/albert/.config/google-chrome
2>&1 >> /dev/null
I get this error:
Gtk-Message: 15:31:01.011: Failed to load module "canberra-gtk-module"
[5823:6010:0713/153101.029812:ERROR:disk_cache.cc(184)] Unable to create cache
[5823:6010:0713/153101.029862:ERROR:shader_disk_cache.cc(606)] Shader Cache
Creation failed: -2
[5823:5823:0713/153101.030904:ERROR:process_singleton_posix.cc(280)] Failed to
create /home/albert/.config/google-chrome/SingletonLock: Permission denied (13)
[5823:5823:0713/153101.030977:ERROR:chrome_browser_main.cc(1258)] Failed to
create a ProcessSingleton for your profile directory. This means that running
multiple instances would start multiple browser processes rather than opening a
new window in the existing process. Aborting now to avoid profile corruption.
... and chromium remains closed.
The chromium-browser and the command above worked fine until before the
snap-ization of chromium-browser in Ubuntu 20.04, which came about
yesterday when I run the updater.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 83.0.4103.97-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 13 15:33:56 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-06-24 (1479 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes:
ID Status Spawn Ready Summary
113 Done 2020-07-12T23:38:16+01:00 2020-07-12T23:38:37+01:00 Install
"chromium" snap
114 Done 2020-07-12T23:38:38+01:00 2020-07-12T23:38:39+01:00 Connect
chromium:password-manager-service to core:password-manager-service
Snap.ChromeDriverVersion: ChromeDriver 83.0.4103.116
(8f0c18b4dca9b6699eb629be0f51810c24fb6428-refs/branch-heads/4103@{#716})
Snap.ChromiumVersion: Chromium 83.0.4103.116 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-05-20 (54 days ago)
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1887396
Title:
chromium-browser doesn't start
Status in chromium-browser package in Ubuntu:
New
Bug description:
Upon launching chromium-browser from the terminal with the command:
$ chromium-browser --user-data-dir=/home/albert/.config/google-chrome
2>&1 >> /dev/null
I get this error:
Gtk-Message: 15:31:01.011: Failed to load module "canberra-gtk-module"
[5823:6010:0713/153101.029812:ERROR:disk_cache.cc(184)] Unable to create cache
[5823:6010:0713/153101.029862:ERROR:shader_disk_cache.cc(606)] Shader Cache
Creation failed: -2
[5823:5823:0713/153101.030904:ERROR:process_singleton_posix.cc(280)] Failed
to create /home/albert/.config/google-chrome/SingletonLock: Permission denied
(13)
[5823:5823:0713/153101.030977:ERROR:chrome_browser_main.cc(1258)] Failed to
create a ProcessSingleton for your profile directory. This means that running
multiple instances would start multiple browser processes rather than opening a
new window in the existing process. Aborting now to avoid profile corruption.
... and chromium remains closed.
The chromium-browser and the command above worked fine until before
the snap-ization of chromium-browser in Ubuntu 20.04, which came about
yesterday when I run the updater.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 83.0.4103.97-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 13 15:33:56 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-06-24 (1479 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes:
ID Status Spawn Ready Summary
113 Done 2020-07-12T23:38:16+01:00 2020-07-12T23:38:37+01:00 Install
"chromium" snap
114 Done 2020-07-12T23:38:38+01:00 2020-07-12T23:38:39+01:00 Connect
chromium:password-manager-service to core:password-manager-service
Snap.ChromeDriverVersion: ChromeDriver 83.0.4103.116
(8f0c18b4dca9b6699eb629be0f51810c24fb6428-refs/branch-heads/4103@{#716})
Snap.ChromiumVersion: Chromium 83.0.4103.116 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-05-20 (54 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887396/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
