[Desktop-packages] [Bug 1887396] Re: chromium-browser doesn't start
Hi Olivier,
Thank you, haven't tried that. At this point I gave up on the chromium snap
altogether, using instead Firefox and WebKit-based browsers other than
chromium. Too many issues with snap packages in general make it not worth the
trouble.
--
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:
Invalid
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=
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes:
ID Status Spawn Ready Summary
113 Done2020-07-12T23:38:16+01:00 2020-07-12T23:38:37+01:00 Install
"chromium" snap
114 Done2020-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
[Desktop-packages] [Bug 1891235] [NEW] Upon resume from sleep the mouse is down upon moving it, selecting text and dragging icons
Public bug reported: In this Thinkpax X1 Yoga, the touchscreen is managed by this wacom driver. After a few sleep/resume cycles (maybe 4 or 5), the mouse starts acting up: upon moving the mouse, it acts as if it was also down, selecting text or dragging icons in nautilus. It is as if upon click and then move, the mouse is never released, even if it has been. To work around the issue, do: sudo modprobe -r wacom sudo modprobe wacom ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-wacom 1:0.39.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 11 21:30:06 2020 DistUpgraded: 2020-05-20 10:21:28,278 DEBUG 'libsignon-glib1' scheduled for remove but not safe to remove, skipping DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1508 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FQCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=972ac4f9-34e5-4cf0-a6ba-2fa4322fd70a ro quiet splash vt.handoff=7 SourcePackage: xf86-input-wacom UpgradeStatus: Upgraded to focal on 2020-05-20 (83 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FQCTO1WW dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue May 19 16:22:47 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 38562 vendor MEI xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xf86-input-wacom (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1891235 Title: Upon resume from sleep the mouse is down upon moving it, selecting text and dragging icons Status in xf86-input-wacom package in Ubuntu: New Bug description: In this Thinkpax X1 Yoga, the touchscreen is managed by this wacom driver. After a few sleep/resume cycles (maybe 4 or 5), the mouse starts acting up: upon moving the mouse, it acts as if it was also down, selecting text or dragging icons in nautilus. It is as if upon click and then move, the mouse is never released, even if it has been. To work around the issue, do: sudo modprobe -r wacom sudo modprobe wacom ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-wacom 1:0.39.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 11 21:30:06 2020 DistUpgraded: 2020-05-20 10:21:28,278 DEBUG 'libsignon-glib1' scheduled for remove but not safe to remove, skipping DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1508 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:705a Lite-On Tech
[Desktop-packages] [Bug 1888674] Re: chromium doesn't launch when using --user-data-dir
More:
$ ls ~/snap/chromium
total 24
drwxr-xr-x 5 albert albert 4096 Jul 23 14:49 .
drwxr-xr-x 7 albert albert 4096 Jul 13 15:30 ..
drwxr-xr-x 5 albert albert 4096 Jul 13 21:43 1213
drwxr-xr-x 5 albert albert 4096 Jul 23 14:49 1229
drwxr-xr-x 4 albert albert 4096 Jul 13 15:30 common
lrwxrwxrwx 1 albert albert4 Jul 23 14:49 current -> 1229
# cd ~/snap/chromium/
$ rm -rf 1229
$ rm current
$ ln -s 1213 current
Then launch google chrome from the menus. Result? 1229 is recreated, and
current points to it again. That's unexpected.
--
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/1888674
Title:
chromium doesn't launch when using --user-data-dir
Status in chromium-browser package in Ubuntu:
New
Bug description:
The command to launch:
chromium-browser --user-data-
dir=/home/albert/snap/chromium/1213/.config/google-chrome 2>&1 >>
/dev/null
The error:
Gtk-Message: 14:38:15.136: Failed to load module "canberra-gtk-module"
Gtk-Message: 14:38:15.138: Failed to load module "canberra-gtk-module"
[24822:24822:0723/143815.159408:ERROR:process_singleton_posix.cc(280)] Failed
to create /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
Permission denied (13)
[24822:24822:0723/143815.159485:ERROR:chrome_browser_main.cc(1246)] 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.
[24822:25016:0723/143815.163146:ERROR:disk_cache.cc(184)] Unable to create
cache
[24822:25016:0723/143815.163207:ERROR:shader_disk_cache.cc(606)] Shader Cache
Creation failed: -2
Some background: was able to use a similar command for years. Then recently
when chromium was packed into a snap, I had to move my user directory inside
the ~/snap/ folder or it wouldn't launch. After the latest update, I can't
launch chromium at all.
Please advice. Thank you.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 83.0.4103.97-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 23 14:36:34 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-06-24 (1489 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium']
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 84.0.4147.89
(19abfe7bcba9318a0b2a6bc6634a67fc834aa592-refs/branch-heads/4147@{#852})
Snap.ChromiumVersion: Chromium 84.0.4147.89 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-05-20 (64 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1888674/+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
[Desktop-packages] [Bug 1888674] Re: chromium doesn't launch when using --user-data-dir
More info: if I change permissions from 700 to 755 with chmod 755 the
~/snap/chromium/1213/.config/ folder, then the error changes, which
makes no sense: it's my user who is launching this process in any case.
Now the error message is a bit different, still a "permission denied"
for SingletonLock:
Gtk-Message: 14:45:01.519: Failed to load module "canberra-gtk-module"
Gtk-Message: 14:45:01.521: Failed to load module "canberra-gtk-module"
[26613:26804:0723/144501.541534:ERROR:disk_cache.cc(184)] Unable to create cache
[26613:26804:0723/144501.541676:ERROR:shader_disk_cache.cc(606)] Shader Cache
Creation failed: -2
[26613:26613:0723/144501.539783:ERROR:process_singleton_posix.cc(280)] Failed
to create /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
Permission denied (13)
[26613:26613:0723/144501.543529:ERROR:chrome_browser_main.cc(1246)] 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.
--
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/1888674
Title:
chromium doesn't launch when using --user-data-dir
Status in chromium-browser package in Ubuntu:
New
Bug description:
The command to launch:
chromium-browser --user-data-
dir=/home/albert/snap/chromium/1213/.config/google-chrome 2>&1 >>
/dev/null
The error:
Gtk-Message: 14:38:15.136: Failed to load module "canberra-gtk-module"
Gtk-Message: 14:38:15.138: Failed to load module "canberra-gtk-module"
[24822:24822:0723/143815.159408:ERROR:process_singleton_posix.cc(280)] Failed
to create /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
Permission denied (13)
[24822:24822:0723/143815.159485:ERROR:chrome_browser_main.cc(1246)] 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.
[24822:25016:0723/143815.163146:ERROR:disk_cache.cc(184)] Unable to create
cache
[24822:25016:0723/143815.163207:ERROR:shader_disk_cache.cc(606)] Shader Cache
Creation failed: -2
Some background: was able to use a similar command for years. Then recently
when chromium was packed into a snap, I had to move my user directory inside
the ~/snap/ folder or it wouldn't launch. After the latest update, I can't
launch chromium at all.
Please advice. Thank you.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 83.0.4103.97-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 23 14:36:34 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-06-24 (1489 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium']
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 84.0.4147.89
(19abfe7bcba9318a0b2a6bc6634a67fc834aa592-refs/branch-heads/4147@{#852})
Snap.ChromiumVersion: Chromium 84.0.4147.89 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-05-20 (64 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1888674/+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
[Desktop-packages] [Bug 1888674] [NEW] chromium doesn't launch when using --user-data-dir
Public bug reported:
The command to launch:
chromium-browser --user-data-dir=/home/albert/snap/chromium/1213/.config
/google-chrome 2>&1 >> /dev/null
The error:
Gtk-Message: 14:38:15.136: Failed to load module "canberra-gtk-module"
Gtk-Message: 14:38:15.138: Failed to load module "canberra-gtk-module"
[24822:24822:0723/143815.159408:ERROR:process_singleton_posix.cc(280)] Failed
to create /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
Permission denied (13)
[24822:24822:0723/143815.159485:ERROR:chrome_browser_main.cc(1246)] 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.
[24822:25016:0723/143815.163146:ERROR:disk_cache.cc(184)] Unable to create cache
[24822:25016:0723/143815.163207:ERROR:shader_disk_cache.cc(606)] Shader Cache
Creation failed: -2
Some background: was able to use a similar command for years. Then recently
when chromium was packed into a snap, I had to move my user directory inside
the ~/snap/ folder or it wouldn't launch. After the latest update, I can't
launch chromium at all.
Please advice. Thank you.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 83.0.4103.97-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 23 14:36:34 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-06-24 (1489 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium']
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 84.0.4147.89
(19abfe7bcba9318a0b2a6bc6634a67fc834aa592-refs/branch-heads/4147@{#852})
Snap.ChromiumVersion: Chromium 84.0.4147.89 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-05-20 (64 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/1888674
Title:
chromium doesn't launch when using --user-data-dir
Status in chromium-browser package in Ubuntu:
New
Bug description:
The command to launch:
chromium-browser --user-data-
dir=/home/albert/snap/chromium/1213/.config/google-chrome 2>&1 >>
/dev/null
The error:
Gtk-Message: 14:38:15.136: Failed to load module "canberra-gtk-module"
Gtk-Message: 14:38:15.138: Failed to load module "canberra-gtk-module"
[24822:24822:0723/143815.159408:ERROR:process_singleton_posix.cc(280)] Failed
to create /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
Permission denied (13)
[24822:24822:0723/143815.159485:ERROR:chrome_browser_main.cc(1246)] 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.
[24822:25016:0723/143815.163146:ERROR:disk_cache.cc(184)] Unable to create
cache
[24822:25016:0723/143815.163207:ERROR:shader_disk_cache.cc(606)] Shader Cache
Creation failed: -2
Some background: was able to use a similar command for years. Then recently
when chromium was packed into a snap, I had to move my user directory inside
the ~/snap/ folder or it wouldn't launch. After the latest update, I can't
launch chromium at all.
Please advice. Thank you.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 83.0.4103.97-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 23 14:36:34 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-06-24 (1489 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium']
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 84.0.4147.89
(19abfe7bcba9318a0b2a6bc6634a67fc834aa592-refs/branch-heads/4147@{#852})
Snap.ChromiumVersion: Chromium 84.0.4147.89 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal o
[Desktop-packages] [Bug 1887396] Re: chromium-browser doesn't start
As of July 2nd, again I can't start chromium after having rebooted
Ubuntu without having quitted chromium first. This time, the error
indicates a lack of removal of temporary symlinks named SingletonLock
and related Singleton*. E.g.:
```
Gtk-Message: 00:39:49.309: Failed to load module "canberra-gtk-module"
Gtk-Message: 00:39:49.311: Failed to load module "canberra-gtk-module"
[11356:11356:0723/003949.329173:ERROR:process_singleton_posix.cc(265)] Failed
to unlink /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
Permission denied (13)
[11356:11356:0723/003949.329289:ERROR:process_singleton_posix.cc(280)] Failed
to create /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
File exists (17)
[11356:11356:0723/003949.329363:ERROR:process_singleton_posix.cc(265)] Failed
to unlink /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
Permission denied (13)
[11356:11356:0723/003949.329412:ERROR:chrome_browser_main.cc(1246)] 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.
[11356:11547:0723/003949.337100:ERROR:browser_gpu_channel_host_factory.cc(153)]
Failed to launch GPU process.
[11564:11564:0723/003949.384057:ERROR:broker_posix.cc(43)] Invalid node channel
message
```
Upon removing of the 3 symlinks within the profile folder, still an
error:
```
Gtk-Message: 01:00:08.609: Failed to load module "canberra-gtk-module"
Gtk-Message: 01:00:08.610: Failed to load module "canberra-gtk-module"
[13997:13997:0723/010008.630073:ERROR:process_singleton_posix.cc(280)] Failed
to create /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
Permission denied (13)
[13997:13997:0723/010008.630170:ERROR:chrome_browser_main.cc(1246)] 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.
[13997:14191:0723/010008.637081:ERROR:browser_gpu_channel_host_factory.cc(153)]
Failed to launch GPU process.
```
Any ideas? Thank you!
--
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:
Invalid
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=
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes:
ID Status Spawn Ready Summary
113 Done2020-07-12T23:38:16+01:00 2020-07-12T23:38:37+01:00 Install
"chromium" snap
114 Done2020-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
[Desktop-packages] [Bug 1887396] Re: chromium-browser doesn't start
Thank you, this was helpful. It's up and running.
--
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:
Invalid
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=
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes:
ID Status Spawn Ready Summary
113 Done2020-07-12T23:38:16+01:00 2020-07-12T23:38:37+01:00 Install
"chromium" snap
114 Done2020-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
[Desktop-packages] [Bug 1887396] [NEW] chromium-browser doesn't start
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=
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes:
ID Status Spawn Ready Summary
113 Done2020-07-12T23:38:16+01:00 2020-07-12T23:38:37+01:00 Install
"chromium" snap
114 Done2020-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=
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes:
ID Status Spawn Ready Summary
113 Done2020-07-12T23:38:16+01:00 2020-07-12T23:38:37+01:00 Install
"chromium" snap
114 Done2020-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.ChromiumV
[Desktop-packages] [Bug 1882376] [NEW] Can't connect to external audio TaoTronics TT-BA07
Public bug reported: >From my iphone and chromebook I can see the external speakers plugged to a TaoTronics TT-BA07 bluetooth device. But from Ubuntu 20.04, the device doesn't appear listed in the settings. There is listed a deviced named "1" that, when connecting to, appears to be a sound device, but from the sound settings "test" buttons I can't get any sound to play. Any hints as to how I could triage this issue and collect more details? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 17:22:16 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1442 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera Bus 001 Device 006: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FQCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=972ac4f9-34e5-4cf0-a6ba-2fa4322fd70a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-20 (17 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FQCTO1WW dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: E4:B3:18:78:A6:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:43684 acl:117 sco:0 events:3823 errors:0 TX bytes:705943 acl:202 sco:0 commands:2991 errors:0 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1882376 Title: Can't connect to external audio TaoTronics TT-BA07 Status in bluez package in Ubuntu: New Bug description: From my iphone and chromebook I can see the external speakers plugged to a TaoTronics TT-BA07 bluetooth device. But from Ubuntu 20.04, the device doesn't appear listed in the settings. There is listed a deviced named "1" that, when connecting to, appears to be a sound device, but from the sound settings "test" buttons I can't get any sound to play. Any hints as to how I could triage this issue and collect more details? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 17:22:16 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1442 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera Bus 001 Device 006: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FQCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=972ac4f9-34e5-4cf0-a6ba-2fa4322fd70a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-20 (17 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information
[Desktop-packages] [Bug 1881199] Re: [SoundCore mini, playback] No sound at all from Rhythmbox
Thank you very much, your suggestion solved the issue: rhythmbox can now play via bluetooth. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881199 Title: [SoundCore mini, playback] No sound at all from Rhythmbox Status in pulseaudio package in Ubuntu: Incomplete Bug description: After connecting via bluetooth the Soundcore Mini, I can get sound to play through it just fine from e.g. the Chromium browser, but not from Rhythmbox, which instead always plays from the laptop's internal speakrs. In the bluetooth settings, Soundcore Mini is connected. In the sound settings, Soundcore Mini is selected, and the "Test" button opens an UI that lets me play test sounds, and it works. And indeed it works for e.g. Google Chrome for a youtube video. But Rhythmbox plays through the internal speakers no matter what. I've tried restarting Rhythmbox, removing the ~/.pulse_secure/pulse/ folder with settings and then running "pulseaudio -k", and then restarting Rhythmbox, to no avail. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 22:00:38 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1434 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SoundCore mini Symptom_DevicesInUse: Cannot stat file /proc/43906/fd/6: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio Symptom_Type: No sound at all Title: [SoundCore mini, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-20 (8 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FQCTO1WW dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881199/+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
[Desktop-packages] [Bug 1881199] [NEW] [SoundCore mini, playback] No sound at all from Rhythmbox
Public bug reported: After connecting via bluetooth the Soundcore Mini, I can get sound to play through it just fine from e.g. the Chromium browser, but not from Rhythmbox, which instead always plays from the laptop's internal speakrs. In the bluetooth settings, Soundcore Mini is connected. In the sound settings, Soundcore Mini is selected, and the "Test" button opens an UI that lets me play test sounds, and it works. And indeed it works for e.g. Google Chrome for a youtube video. But Rhythmbox plays through the internal speakers no matter what. I've tried restarting Rhythmbox, removing the ~/.pulse_secure/pulse/ folder with settings and then running "pulseaudio -k", and then restarting Rhythmbox, to no avail. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 22:00:38 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1434 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SoundCore mini Symptom_DevicesInUse: Cannot stat file /proc/43906/fd/6: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio Symptom_Type: No sound at all Title: [SoundCore mini, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-20 (8 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FQCTO1WW dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881199 Title: [SoundCore mini, playback] No sound at all from Rhythmbox Status in pulseaudio package in Ubuntu: New Bug description: After connecting via bluetooth the Soundcore Mini, I can get sound to play through it just fine from e.g. the Chromium browser, but not from Rhythmbox, which instead always plays from the laptop's internal speakrs. In the bluetooth settings, Soundcore Mini is connected. In the sound settings, Soundcore Mini is selected, and the "Test" button opens an UI that lets me play test sounds, and it works. And indeed it works for e.g. Google Chrome for a youtube video. But Rhythmbox plays through the internal speakers no matter what. I've tried restarting Rhythmbox, removing the ~/.pulse_secure/pulse/ folder with settings and then running "pulseaudio -k", and then restarting Rhythmbox, to no avail. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 22:00:38 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1434 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SoundCore mini Symptom_DevicesInUse: Cannot stat file /proc/43906/fd/6: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio Symptom_Type: No sound at all Title: [SoundCore mini, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-20 (8 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW dmi.board.vendor: LENOVO dmi.board.version
[Desktop-packages] [Bug 1880243] Re: can't hide desktop icons neither with dconf-editor nor with gnome-shell-extension-desktop-icons
Thanks @vanvugt, so there are 3 UI ways of hiding the desktop icons, but only one works: $ gnome-shell-extension-prefs ... then switch off the desktop-icons extension. (Nevermind that gnome tweaks, under "Extensions", listed the desktop- icons gnome shell extension as disabled.) The bugs are then the mere existence of the other two UI ways of hiding desktop icons. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1880243 Title: can't hide desktop icons neither with dconf-editor nor with gnome- shell-extension-desktop-icons Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Bug description: In attempting to hide all desktop icons, I can't. 1. With dconf-editor, org/gnome/desktop/background/show-desktop-icons , I set the value to False, and yet the icons show. 2. With gnome-shell-extension-desktop-icons, despite disabling it, it still doesn't work (can change the size of the icons, but can't hide all icons when deactivating the extension). What's the appropriate approach to disable desktop icons? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 20.04.0-1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 22 22:24:44 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1428 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to focal on 2020-05-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1880243/+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
[Desktop-packages] [Bug 1880243] [NEW] can't hide desktop icons neither with dconf-editor nor with gnome-shell-extension-desktop-icons
Public bug reported: In attempting to hide all desktop icons, I can't. 1. With dconf-editor, org/gnome/desktop/background/show-desktop-icons , I set the value to False, and yet the icons show. 2. With gnome-shell-extension-desktop-icons, despite disabling it, it still doesn't work (can change the size of the icons, but can't hide all icons when deactivating the extension). What's the appropriate approach to disable desktop icons? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 20.04.0-1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 22 22:24:44 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1428 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to focal on 2020-05-20 (2 days ago) ** Affects: gnome-shell-extension-desktop-icons (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 gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1880243 Title: can't hide desktop icons neither with dconf-editor nor with gnome- shell-extension-desktop-icons Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: In attempting to hide all desktop icons, I can't. 1. With dconf-editor, org/gnome/desktop/background/show-desktop-icons , I set the value to False, and yet the icons show. 2. With gnome-shell-extension-desktop-icons, despite disabling it, it still doesn't work (can change the size of the icons, but can't hide all icons when deactivating the extension). What's the appropriate approach to disable desktop icons? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 20.04.0-1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 22 22:24:44 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1428 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to focal on 2020-05-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1880243/+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
[Desktop-packages] [Bug 979613] Re: Module rtl8192ce must sometimes be reloaded after suspend
*** This bug is a duplicate of bug 902557 *** https://bugs.launchpad.net/bugs/902557 Same is true for module b43. After resuming from suspend, wireless only works after doing: $ sudo modprobe -r b43 $ sudo modprobe b43 Hope that helps someone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/979613 Title: Module rtl8192ce must sometimes be reloaded after suspend Status in “network-manager” package in Ubuntu: Confirmed Bug description: Now and then wifi will not work after suspend. It attempts again and again, but times out. rmmod rtl8192ce and modprobe rtl8192ce fixes the problem. From syslog: [ 6651.918095] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin [ 6653.129184] wlan0: direct probe to 74:44:01:36:c7:12 (try 1/3) [ 6653.172141] wlan0: direct probe responded [ 6653.213025] wlan0: authenticate with 74:44:01:36:c7:12 (try 1) [ 6653.412782] wlan0: authenticate with 74:44:01:36:c7:12 (try 2) [ 6653.612560] wlan0: authenticate with 74:44:01:36:c7:12 (try 3) [ 6653.812348] wlan0: authentication with 74:44:01:36:c7:12 timed out [ 6658.897264] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin [ 6660.099766] wlan0: direct probe to 74:44:01:36:c7:12 (try 1/3) [ 6660.104844] wlan0: direct probe responded [ 6660.165951] wlan0: authenticate with 74:44:01:36:c7:12 (try 1) [ 6660.365148] wlan0: authenticate with 74:44:01:36:c7:12 (try 2) [ 6660.564934] wlan0: authenticate with 74:44:01:36:c7:12 (try 3) [ 6660.764757] wlan0: authentication with 74:44:01:36:c7:12 timed out [ 6665.798760] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin [ 6671.999652] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin [ 6673.205455] wlan0: direct probe to 74:44:01:36:c7:12 (try 1/3) [ 6673.209982] wlan0: direct probe responded [ 6673.271136] wlan0: authenticate with 74:44:01:36:c7:12 (try 1) [ 6673.470749] wlan0: authenticate with 74:44:01:36:c7:12 (try 2) [ 6673.670526] wlan0: authenticate with 74:44:01:36:c7:12 (try 3) [ 6673.870305] wlan0: authentication with 74:44:01:36:c7:12 timed out ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu1 Architecture: amd64 CRDA: country EC: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 20), (3, 17) (5250 - 5330 @ 20), (3, 23), DFS (5735 - 5835 @ 20), (3, 30) CheckboxSubmission: 621f51bbb855f2649d500c28b87f4a5e CheckboxSystem: 86f6fcdd6850a813cd5c77b7959e6176 Date: Thu Apr 12 09:10:29 2012 IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.3 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/979613/+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
