[Desktop-packages] [Bug 2064118] Re: Latest Chrome update breaks and froze interfaze in Ubuntu and wont open
Sorry, we don't support Google Chrome. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- 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/2064118 Title: Latest Chrome update breaks and froze interfaze in Ubuntu and wont open Status in chromium-browser package in Ubuntu: Invalid Bug description: Latest Chrome Update has broken Chrome for Ubuntu 22.04.4 LTS Release: 22.04 When I click on the Chrome Icon it just indicates a loading Icon and break functionality of the whole interface, I need to Quit Chrome to be able to use any app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2064118/+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 2062173] Re: Apparmor denies updating namespace with ecryptfs
Possible duplicate of LP:2062330.
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
--
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/2062173
Title:
Apparmor denies updating namespace with ecryptfs
Status in chromium-browser package in Ubuntu:
New
Status in snapd package in Ubuntu:
New
Bug description:
Noticed on Ubuntu 23.10. Started misbehaving on April 17th 2024.
$ snap info chromium
...
snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/stable
refresh-date: today at 08:58 CEST
channels:
latest/stable:123.0.6312.122 2024-04-15 (2821) 168MB -
...
When running chromium, it complains about not being able to open my home dir:
cannot update snap namespace: cannot expand mount entry (none
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0
0): cannot use invalid home directory "/home/tannerli": permission denied
snap-update-ns failed with code 1
AppArmor log shows that access to ecryptfs private folder was denied:
Apr 18 13:13:21 hostname kernel: audit: type=1400
audit(1713438801.579:437): apparmor="DENIED" operation="open"
class="file" profile="snap-update-ns.chromium"
name="/home/.ecryptfs/tannerli/.Private/" pid=32412 comm="5"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
I found out, that, under /var/lib/snapd/apparmor/profiles, while
snap.chromium.chromium has the line
owner @{HOMEDIRS}/.ecryptfs/*/.Private/ r,
the file snap-update-ns.chromium does _not_ have the line. Adding it
and reloading the profile allows chromium to start again.
I'm nowhere near experienced enough to tell whether this line should
be added by default or something else went wrong on my machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2062173/+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 2062330] Re: Chromium fails to start with "invalid home directory"
I think the same fix[1] that was committed to address the related bug will apply here. Quoting from there: > Please re-test on snapd edge tomorrow [1] https://github.com/snapcore/snapd/pull/13853 -- 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/2062330 Title: Chromium fails to start with "invalid home directory" Status in chromium-browser package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: As of this morning chromium failed to launch, a problem which I've never had before. When I run from command line, I get this: $ chromium ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored. cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 0): cannot use invalid home directory "/home/macho": permission denied snap-update-ns failed with code 1 Here is some more info: $ ls -la /home | grep macho drwx-- 34 macho macho 12288 Apr 18 08:55 macho $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 2 days ago, at 01:07 EDT channels: latest/stable:123.0.6312.122 2024-04-15 (2821) 168MB - latest/candidate: 124.0.6367.60 2024-04-17 (2828) 169MB - latest/beta: 124.0.6367.60 2024-04-16 (2827) 169MB - latest/edge: 125.0.6420.3 2024-04-17 (2829) 170MB - installed: 123.0.6312.122(2821) 168MB - $ dpkg -l libgtk3-nocsd0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++----> ii libgtk3-nocsd0:amd64 3-1ubuntu2 amd64Library to disable Gtk+ 3 cl Happy to provide any further info needed. This is on ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2062330/+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 2062330] Re: Chromium fails to start apparently citing issue with nocsd
Great! Just a question, does > ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored. still show when launching Chromium? I'm assuming the following "cannot update snap namespace" line went away. ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Chromium fails to start apparently citing issue with nocsd + Chromium fails to start with "invalid home directory" ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Changed in: snapd (Ubuntu) Importance: Undecided => High -- 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/2062330 Title: Chromium fails to start with "invalid home directory" Status in chromium-browser package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: As of this morning chromium failed to launch, a problem which I've never had before. When I run from command line, I get this: $ chromium ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored. cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 0): cannot use invalid home directory "/home/macho": permission denied snap-update-ns failed with code 1 Here is some more info: $ ls -la /home | grep macho drwx-- 34 macho macho 12288 Apr 18 08:55 macho $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 2 days ago, at 01:07 EDT channels: latest/stable:123.0.6312.122 2024-04-15 (2821) 168MB - latest/candidate: 124.0.6367.60 2024-04-17 (2828) 169MB - latest/beta: 124.0.6367.60 2024-04-16 (2827) 169MB - latest/edge: 125.0.6420.3 2024-04-17 (2829) 170MB - installed: 123.0.6312.122(2821) 168MB - $ dpkg -l libgtk3-nocsd0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++----> ii libgtk3-nocsd0:amd64 3-1ubuntu2 amd64Library to disable Gtk+ 3 cl Happy to provide any further info needed. This is on ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2062330/+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 2062330] Re: Chromium fails to start apparently citing issue with nocsd
Hi, this looks strikingly similar to LP:2061981, but here you have a standard /home layout. Can you please do snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons and report back? -- 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/2062330 Title: Chromium fails to start apparently citing issue with nocsd Status in chromium-browser package in Ubuntu: New Bug description: As of this morning chromium failed to launch, a problem which I've never had before. When I run from command line, I get this: $ chromium ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored. cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 0): cannot use invalid home directory "/home/macho": permission denied snap-update-ns failed with code 1 Here is some more info: $ ls -la /home | grep macho drwx-- 34 macho macho 12288 Apr 18 08:55 macho $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 2 days ago, at 01:07 EDT channels: latest/stable:123.0.6312.122 2024-04-15 (2821) 168MB - latest/candidate: 124.0.6367.60 2024-04-17 (2828) 169MB - latest/beta: 124.0.6367.60 2024-04-16 (2827) 169MB - latest/edge: 125.0.6420.3 2024-04-17 (2829) 170MB - installed: 123.0.6312.122(2821) 168MB - $ dpkg -l libgtk3-nocsd0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++----> ii libgtk3-nocsd0:amd64 3-1ubuntu2 amd64Library to disable Gtk+ 3 cl Happy to provide any further info needed. This is on ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2062330/+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 2061981] Re: chromium fails to start with non-standard home directory
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Invalid ** Changed in: snapd (Ubuntu) Status: Confirmed => Triaged -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: Triaged Bug description: CURRENT WORKAROUND -- snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons Those are just "quality of life" interfaces (c.f. LP:1732482) that most users probably do not even use, disconnecting them will cause no breakage. (Of course, a proper diagnosis and fix is due.) ORIGINAL REPORT --- cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] Re: chromium fails to start with non-standard home directory
Thanks!
As a note for self, I diffed snapd 2.61.2 and 2.62 and found in
cmd/snap-update-ns/user.go:
--->
+func isPlausibleHome(path string) error {
+ if path == "" {
+ return fmt.Errorf("cannot allow empty path")
+ }
+ if path != filepath.Clean(path) {
+ return fmt.Errorf("cannot allow unclean path")
+ }
+ if !filepath.IsAbs(path) {
+ return fmt.Errorf("cannot allow relative path")
+ }
+ const openFlags = syscall.O_NOFOLLOW | syscall.O_CLOEXEC |
syscall.O_DIRECTORY
+ fd, err := sysOpen(path, openFlags, 0)
+ if err != nil {
+ return err
+ }
+ sysClose(fd)
+ return nil
+}
<---
--->
+ if err := isPlausibleHome(realHome); err != nil {
+ realHomeError = fmt.Errorf("cannot use invalid home directory
%q: %v", realHome, err)
<---
It remains to be ascertained whether this lack of permission always
existed but didn't cause the launch of the snap to fail.
--
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/2061981
Title:
chromium fails to start with non-standard home directory
Status in chromium-browser package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Confirmed
Bug description:
CURRENT WORKAROUND
--
snap disconnect chromium:dot-local-share-applications
snap disconnect chromium:dot-local-share-icons
Those are just "quality of life" interfaces (c.f. LP:1732482) that
most users probably do not even use, disconnecting them will cause no
breakage. (Of course, a proper diagnosis and fix is due.)
ORIGINAL REPORT
---
cannot update snap namespace: cannot expand mount entry (none
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-
dir=$HOME 0 0): cannot use invalid home directory
"/home/department/user_name": permission denied
Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory
/home/department/user_name
Used to work fine up to last week.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Apr 17 10:32:18 2024
InstallationDate: Installed on 2017-03-24 (2580 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
Snap.Changes:
ID Status Spawn Ready Summary
206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove
"chromium" snap
207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove
"chromium" snap
208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install
"chromium" snap
209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect
chromium:password-manager-service to snapd:password-manager-service
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] Re: chromium fails to start with non-standard home directory
Thank you very much for testing that, having the input of the directly affected user is always highly valuable for debugging. ** Description changed: - chromium 123.0.6312.122 2821 latest/stablecanonical + CURRENT WORKAROUND + -- + + snap disconnect chromium:dot-local-share-applications + snap disconnect chromium:dot-local-share-icons + + Those are just "quality of life" interfaces (c.f. LP:1732482) that most + users probably do not even use, disconnecting them will cause no + breakage. (Of course, a proper diagnosis and fix is due.) + + ORIGINAL REPORT + --- cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: - ID Status Spawn Ready Summary - 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap - 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap - 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap - 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service + ID Status Spawn Ready Summary + 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap + 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap + 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap + 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: CURRENT WORKAROUND -- snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons Those are just "quality of life" interfaces (c.f. LP:1732482) that most users probably do not even use, disconnecting them will cause no breakage. (Of course, a proper diagnosis and fix is due.) ORIGINAL REPORT --- cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
Thank you for the additional information. enaira05, you can disconnect them with snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons wouterd, glad to hear that solves your problem. The interface has been present for a long time. The Chromium update I released yesterday was just a new upstream release and as such introduces nothing that would trigger such an error. On my side I can see in 'snap changes' 1618 Donetoday at 12:40 CEST today at 12:43 CEST Auto-refresh snap "snapd" So I'm placing my bets on that change. Are you able to 'snap revert snapd' for a test? If yes, please remember to reconnect the interfaces for the test. -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] Re: chromium fails to start with non-standard home directory
** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] Re: chromium fails to start with non-standard home directory
What is 'snap connections chromium | grep personal-files'? If you disconnect the dot-local-share ones, does Chromium start? -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061981] Re: chromium fails to start with non-standard home directory
Thanks, I'll look into the issue, for now you can use `snap revert chromium` to use the previous version. ** This bug is no longer a duplicate of bug 1620771 when /home is somewhere else, snaps don't work -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061985] [NEW] Other users are also highlighted although unselected
Public bug reported: If there is more than one user available, both are highlighted in gray, although only one is highlighted with a orange border. Ubuntu 24.04, gdm 46.0-2ubuntu1. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gdm3-user.jpg" https://bugs.launchpad.net/bugs/2061985/+attachment/5766750/+files/gdm3-user.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2061985 Title: Other users are also highlighted although unselected Status in gdm3 package in Ubuntu: New Bug description: If there is more than one user available, both are highlighted in gray, although only one is highlighted with a orange border. Ubuntu 24.04, gdm 46.0-2ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2061985/+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 2061981] Re: chromium fails to start with non-standard home directory
*** This bug is a duplicate of bug 1620771 *** https://bugs.launchpad.net/bugs/1620771 ** This bug has been marked a duplicate of bug 1620771 when /home is somewhere else, snaps don't work -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+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 2061978] [NEW] Pressing enter on close button of out-of-date cache dialog still triggers the reload button
Public bug reported: Start software-properties-gtk, make any change in the sources configuration, e.g. by just toggling universe check button, enter your password and click close. A dialog appears saying that > To install software and updates from newly added or changed sources, you have to reload the information about available software. with a reload and a close button. Press the right arrow key and close will be selected in the interface, evidenced by a faint border around that button. Press the enter key. - Expected: The close button becomes dark for a brief moment, indicating that it has been pressed, and the program exits immediately. - Observed: The reload button becomes dark for a brief moment, indicating that it has been pressed, and the program starts updating the cache. ** Affects: software-properties (Ubuntu) Importance: Low Assignee: Nathan Teodosio (nteodosio) Status: Triaged ** Tags: ui -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061978 Title: Pressing enter on close button of out-of-date cache dialog still triggers the reload button Status in software-properties package in Ubuntu: Triaged Bug description: Start software-properties-gtk, make any change in the sources configuration, e.g. by just toggling universe check button, enter your password and click close. A dialog appears saying that > To install software and updates from newly added or changed sources, you have to reload the information about available software. with a reload and a close button. Press the right arrow key and close will be selected in the interface, evidenced by a faint border around that button. Press the enter key. - Expected: The close button becomes dark for a brief moment, indicating that it has been pressed, and the program exits immediately. - Observed: The reload button becomes dark for a brief moment, indicating that it has been pressed, and the program starts updating the cache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061978/+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 2061936] Re: Chrome starts, but runs wild in the bg (never gets to the screen). chromium works fine.
Hi, thanks for opening a report. > chrome started failing > chromium launches fine Ubuntu only maintains Chromium. Chrome is proprietary software provided directly by Google so you need to file a report with them. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- 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/2061936 Title: Chrome starts, but runs wild in the bg (never gets to the screen). chromium works fine. Status in chromium-browser package in Ubuntu: Invalid Bug description: This started today. The chrome snap was automatically updated (updates to chrome have been arriving fast). After the update, chrome started failing: * Clocking on the launcher succeeds, but nothing pops up to the screen. The UI freezes (can't even updated htop on a term). * Right clicking on the launcher icon, followed by choosing Quit restores responsiveness, but there is no chrome. * chromium launches fine. Both images come from the same snap. ProblemType: Bug DistroRelease: Ubuntu 23.10 ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 18:48:10 2024 ProcEnviron: LANG=en_US.UTF-8 LC_TIME=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color Snap: chromium 123.0.6312.122 (latest/stable) SnapChanges: ID Status Spawn Ready Summary 612 Done2024-04-16T18:04:21-07:00 2024-04-16T18:04:40-07:00 Revert "chromium" snap 613 Done2024-04-16T18:11:03-07:00 2024-04-16T18:11:16-07:00 Refresh "chromium" snap SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061936/+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 2061850] [NEW] Can't authenticate in TTY after installing authd, but sudo works
Public bug reported: In Ubuntu Noble, I install authd 0.2.1, switch to a different TTY and try to log in. I enter my user name and I am asked > Select your provider > > 1: local I click and am asked for the password. After entering it I expect to eventually get a shell, but after installing Authd I can wait minutes and end up with nothing (as if it were validating the password). If I enter wrong credentials I get "login incorrect" and a new user name prompt, which is the correct behavior. I get the same question asked when using 'sudo' but there it works. ** Affects: authd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to authd in Ubuntu. https://bugs.launchpad.net/bugs/2061850 Title: Can't authenticate in TTY after installing authd, but sudo works Status in authd package in Ubuntu: New Bug description: In Ubuntu Noble, I install authd 0.2.1, switch to a different TTY and try to log in. I enter my user name and I am asked > Select your provider > > 1: local I click and am asked for the password. After entering it I expect to eventually get a shell, but after installing Authd I can wait minutes and end up with nothing (as if it were validating the password). If I enter wrong credentials I get "login incorrect" and a new user name prompt, which is the correct behavior. I get the same question asked when using 'sudo' but there it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2061850/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
This is unlikely to be a problem in Gnome Keyring, as SDDM has no problem unlocking in on log-in. I'm therefore adding here GDM3. ** Also affects: gdm (Ubuntu) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** No longer affects: gdm (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gdm3 package in Ubuntu: New Status in gnome-keyring package in Ubuntu: Triaged Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+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 2060730] Re: totem cannot install codecs via packagekit
OK, I was also missing gstreamer1.0-packagekit. Summary is: For reproducing that exact error, have neither gstreamer1.0-libav nor gstreamer-1.0-plugins-bad nor gstreamer-1.0-packagekit. To fix the error, one needs both gstreamer1.0-packagekit and gnome- software, then hitting "Find in Software" will open gnome-software with suggestions (as attached). ** Attachment added: "Screenshot from 2024-04-12 11-46-48.png" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2060730/+attachment/5764166/+files/Screenshot%20from%202024-04-12%2011-46-48.png ** Also affects: app-center Importance: Undecided Status: New ** Changed in: totem (Ubuntu) Status: Triaged => Invalid ** Changed in: packagekit (Ubuntu) Status: New => Invalid ** Changed in: app-center Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2060730 Title: totem cannot install codecs via packagekit Status in App Center: Triaged Status in packagekit package in Ubuntu: Invalid Status in totem package in Ubuntu: Invalid Bug description: While attempting to play a video on Ubuntu noble desktop for raspberry pi, totem attempts to locate a package for the H.264 codec but cannot find a service providing org.freedesktop.PackageKit. This is strange given that packagekit is installed, provides packagekit.service, which declares that it provides that name over DBus. Specifically, the following is output by totem: ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder) ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder) ** Message: 21:13:39.414: PackageKit: xid = 0 ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit) ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit) ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files ** Message: 21:13:39.441: No installation candidate for missing plugins found. The packagekit.service is defined as: $ systemctl cat packagekit.service # /usr/lib/systemd/system/packagekit.service [Unit] Description=PackageKit Daemon # PK doesn't know how to do anything on ostree-managed systems; # currently the design is to have dedicated daemons like # eos-updater and rpm-ostree, and gnome-software talks to those. ConditionPathExists=!/run/ostree-booted Wants=network-online.target [Service] Type=dbus BusName=org.freedesktop.PackageKit User=root ExecStart=/usr/libexec/packagekitd And just to demonstrate packagekit is actually running: $ systemctl status packagekit.service ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static) Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s ago Main PID: 1565 (packagekitd) Tasks: 4 (limit: 3864) Memory: 6.2M (peak: 6.7M) CPU: 180ms CGroup: /system.slice/packagekit.service └─1565 /usr/libexec/packagekitd Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - PackageKit Daemon... Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - PackageKit Daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/app-center/+bug/2060730/+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 2060730] Re: totem cannot install codecs via packagekit
If I install gnome-software and try again, I get a prompt: > Unable to play the file > > MPEG-4 AAC decoder, H.264 (High Profile) decoder are required to play the > file, but are not installed With a button to "Find in Software". Clicking it does nothing though. And even before clicking anything on the prompt, '/usr/bin/gnome- software --gapplication-service' is registered in ps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2060730 Title: totem cannot install codecs via packagekit Status in packagekit package in Ubuntu: New Status in totem package in Ubuntu: Triaged Bug description: While attempting to play a video on Ubuntu noble desktop for raspberry pi, totem attempts to locate a package for the H.264 codec but cannot find a service providing org.freedesktop.PackageKit. This is strange given that packagekit is installed, provides packagekit.service, which declares that it provides that name over DBus. Specifically, the following is output by totem: ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder) ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder) ** Message: 21:13:39.414: PackageKit: xid = 0 ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit) ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit) ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files ** Message: 21:13:39.441: No installation candidate for missing plugins found. The packagekit.service is defined as: $ systemctl cat packagekit.service # /usr/lib/systemd/system/packagekit.service [Unit] Description=PackageKit Daemon # PK doesn't know how to do anything on ostree-managed systems; # currently the design is to have dedicated daemons like # eos-updater and rpm-ostree, and gnome-software talks to those. ConditionPathExists=!/run/ostree-booted Wants=network-online.target [Service] Type=dbus BusName=org.freedesktop.PackageKit User=root ExecStart=/usr/libexec/packagekitd And just to demonstrate packagekit is actually running: $ systemctl status packagekit.service ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static) Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s ago Main PID: 1565 (packagekitd) Tasks: 4 (limit: 3864) Memory: 6.2M (peak: 6.7M) CPU: 180ms CGroup: /system.slice/packagekit.service └─1565 /usr/libexec/packagekitd Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - PackageKit Daemon... Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - PackageKit Daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2060730/+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 2060730] Re: totem cannot install codecs via packagekit
Aha, had to remove gstreamer1.0-libav as well, then: ---> ** (totem:195768): WARNING **: 11:00:53.910: atk-bridge: GetRegisteredEvents returned message with unknown signature ** Message: 11:00:53.953: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc, channel-mask=(bitmask)0x (MPEG-4 AAC decoder) ** Message: 11:00:53.953: Missing plugin: gstreamer|1.0|totem|H.264 (High Profile) decoder|decoder-video/x-h264, level=(string)4, profile=(string)high (H.264 (High Profile) decoder) <--- ** Changed in: totem (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2060730 Title: totem cannot install codecs via packagekit Status in packagekit package in Ubuntu: New Status in totem package in Ubuntu: Triaged Bug description: While attempting to play a video on Ubuntu noble desktop for raspberry pi, totem attempts to locate a package for the H.264 codec but cannot find a service providing org.freedesktop.PackageKit. This is strange given that packagekit is installed, provides packagekit.service, which declares that it provides that name over DBus. Specifically, the following is output by totem: ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder) ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder) ** Message: 21:13:39.414: PackageKit: xid = 0 ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit) ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit) ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files ** Message: 21:13:39.441: No installation candidate for missing plugins found. The packagekit.service is defined as: $ systemctl cat packagekit.service # /usr/lib/systemd/system/packagekit.service [Unit] Description=PackageKit Daemon # PK doesn't know how to do anything on ostree-managed systems; # currently the design is to have dedicated daemons like # eos-updater and rpm-ostree, and gnome-software talks to those. ConditionPathExists=!/run/ostree-booted Wants=network-online.target [Service] Type=dbus BusName=org.freedesktop.PackageKit User=root ExecStart=/usr/libexec/packagekitd And just to demonstrate packagekit is actually running: $ systemctl status packagekit.service ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static) Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s ago Main PID: 1565 (packagekitd) Tasks: 4 (limit: 3864) Memory: 6.2M (peak: 6.7M) CPU: 180ms CGroup: /system.slice/packagekit.service └─1565 /usr/libexec/packagekitd Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - PackageKit Daemon... Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - PackageKit Daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2060730/+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 2060730] Re: totem cannot install codecs via packagekit
Cannot reproduce it here, but despite no gstreamer-bad the video plays normally. Maybe I have another package that satisfies that, I'll investigate further. ---> % systemctl status packagekit.service ○ packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static) Active: inactive (dead) abr 12 10:32:34 canonical systemd[1]: Starting packagekit.service - PackageKit Daemon... abr 12 10:32:34 canonical PackageKit[162838]: daemon start abr 12 10:32:35 canonical systemd[1]: Started packagekit.service - PackageKit Daemon. abr 12 10:37:40 canonical PackageKit[162838]: daemon quit abr 12 10:37:40 canonical systemd[1]: packagekit.service: Deactivated successfully. abr 12 10:42:35 canonical systemd[1]: Starting packagekit.service - PackageKit Daemon... abr 12 10:42:35 canonical PackageKit[182154]: daemon start abr 12 10:42:35 canonical systemd[1]: Started packagekit.service - PackageKit Daemon. abr 12 10:48:36 canonical PackageKit[182154]: daemon quit abr 12 10:48:36 canonical systemd[1]: packagekit.service: Deactivated successfully. % dpkg -l | grep gstream ii gir1.2-gstreamer-1.0:amd64 1.24.1-1build1 amd64GObject introspection data for the GStreamer library ii gstreamer1.0-alsa:amd64 1.24.1-1build1 amd64GStreamer plugin for ALSA ii gstreamer1.0-clutter-3.0:amd64 3.0.27-4build1 amd64Clutter PLugin for GStreamer 1.0 ii gstreamer1.0-gl:amd641.24.1-1build1 amd64GStreamer plugins for GL ii gstreamer1.0-gtk3:amd64 1.24.1-2ubuntu1 amd64GStreamer plugin for GTK+3 ii gstreamer1.0-libav:amd64 1.24.1-1build1 amd64ffmpeg plugin for GStreamer ri gstreamer1.0-nice:amd64 0.1.21-2build3 amd64ICE library (GStreamer plugin) ii gstreamer1.0-pipewire:amd64 1.0.4-2ubuntu4 amd64GStreamer 1.0 plugin for the PipeWire multimedia server ii gstreamer1.0-plugins-base:amd64 1.24.1-1build1 amd64GStreamer plugins from the "base" set ii gstreamer1.0-plugins-base-apps 1.24.1-1build1 amd64GStreamer helper programs from the "base" set ii gstreamer1.0-plugins-good:amd64 1.22.9-1ubuntu1 amd64GStreamer plugins from the "good" set ii gstreamer1.0-plugins-ugly:amd64 1.22.10-1 amd64GStreamer plugins from the "ugly" set ii gstreamer1.0-pulseaudio:amd641.22.9-1ubuntu1 amd64GStreamer plugin for PulseAudio (transitional package) ii gstreamer1.0-qt5:amd64 1.22.9-1ubuntu1 amd64GStreamer plugin for Qt5 ii gstreamer1.0-tools 1.24.1-1build1 amd64Tools for use with GStreamer ii gstreamer1.0-x:amd64 1.24.1-1build1 amd64GStreamer plugins for X11 and Pango ii libgstreamer-gl1.0-0:amd64 1.24.1-1build1 amd64GStreamer GL libraries ii libgstreamer-plugins-base1.0-0:amd64 1.24.1-1build1 amd64GStreamer libraries from the "base" set ii libgstreamer-plugins-base1.0-dev 1.24.1-1build1 amd64GStreamer development files for libraries from the "base" set ii libgstreamer-plugins-good1.0-0:amd64 1.22.9-1ubuntu1 amd64GStreamer development files for libraries from the "good" set ii libgstreamer-plugins-good1.0-dev 1.22.9-1ubuntu1 amd64GStreamer development files for libraries from the "good" set ii libgstreamer1.0-0:amd64 1.24.1-1build1 amd64Core GStreamer libraries and elements ii libgstreamer1.0-dev:amd641.24.1-1build1 amd64GStreamer core development files ii libgtk-4-media-gstreamer 4.14.1+ds-0ubuntu2 amd64GStreamer media backend for the GTK graphical user interface library <--- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2060730 Title: totem cannot install codecs via packagekit
[Desktop-packages] [Bug 2061075] Re: firefox, chromium-browser are not merely a transitional packages
** Patch added: "chr.diff" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061075/+attachment/5764073/+files/chr.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2061075 Title: firefox, chromium-browser are not merely a transitional packages Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: New Bug description: They not only install the corresponding snap but also at least have some hooks to update-alternatives and also provide www-browser, x-www- browser, gnome-www-browser. As such, removing the package might result in installation of something preposterous such as wslu to satisfy such a meta-package dependency, as reported in LP:2060898. The packages' description might lead one to remove them expecting no side effects: > Description-en: Transitional package - firefox -> firefox snap > This is a transitional dummy package. It can safely be removed. > . > firefox is now replaced by the firefox snap. So I suggest we change it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061075/+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 2060898] Re: Trying to install gimp-help-en threatens to install wslu
We will change the browsers' deb description so as to not invite a removal. LP:2061075. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2060898 Title: Trying to install gimp-help-en threatens to install wslu Status in edubuntu-meta package in Ubuntu: Fix Committed Status in kubuntu-meta package in Ubuntu: Triaged Status in lubuntu-meta package in Ubuntu: Fix Committed Status in ubuntu-budgie-meta package in Ubuntu: Fix Committed Status in ubuntu-mate-meta package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Invalid Status in ubuntustudio-meta package in Ubuntu: Fix Committed Status in wslu package in Ubuntu: Invalid Status in edubuntu-meta source package in Noble: Fix Committed Status in kubuntu-meta source package in Noble: Triaged Status in lubuntu-meta source package in Noble: Fix Committed Status in ubuntu-budgie-meta source package in Noble: Fix Committed Status in ubuntu-mate-meta source package in Noble: Triaged Status in ubuntu-meta source package in Noble: Invalid Status in ubuntustudio-meta source package in Noble: Fix Committed Status in wslu source package in Noble: Invalid Bug description: Filing this against ubuntu-meta since I believe this is a seed problem that potentially affects all variants of Ubuntu (flavors or otherwise). wslu is "a collection of utilities for the Windows 10 Linux Subsystem, such as for converting Linux paths to a Windows paths or creating Linux application shortcuts on the Windows 10 Desktop." Obviously this package should *never* be installed on a desktop or even on most VMs, but only within WSL instances. However... wslu provides the virtual package www-browser, as one of its features is to open links in Windows 10 using the default browser set there. This means that if a package depends or recommends www-browser, it may attempt to pull in one of several packages, wslu included. In the past, this hasn't been a problem because Firefox was present on all flavor images, and Firefox provides www-browser as well. However, now that Firefox is a Snap, it is possible for Firefox to be installed without the firefox transitional apt package being installed. (This is the case in a default installation of Kubuntu Noble Beta.) As it turns out, Kubuntu Noble Beta ships with *no* packages that provide www- browser, meaning that any package that depends on it will have to install a new browser. Due to some stroke of misfortune, apt is picking wslu out of all packages as the package for this use case. Installing gimp-help-en will also install www-browser, which results in wslu becoming installed. wslu causes quite a few problems when installed on a desktop system - among them, the syslog is spammed with errors due to the system not in fact being a WSL VM, audio breaks in weird ways, and application launchers sometimes fail. Why this happens is unclear, but the issues appear to resolve once wslu is removed from the system. It is therefore probably a good idea to avoid wslu becoming installed on accident in this way. Probably the best way to resolve this is to ensure that some package that provides www-browser is available on every Ubuntu image. This could be done via seeding or by adding a package to ubuntu-minimal. Alternatively, wslu could be set to no longer provide www-browser, though it's unclear if that would break its functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+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 2061075] [NEW] firefox, chromium-browser are not merely a transitional packages
Public bug reported: They not only install the corresponding snap but also at least have some hooks to update-alternatives and also provide www-browser, x-www- browser, gnome-www-browser. As such, removing the package might result in installation of something preposterous such as wslu to satisfy such a meta-package dependency, as reported in LP:2060898. The packages' description might lead one to remove them expecting no side effects: > Description-en: Transitional package - firefox -> firefox snap > This is a transitional dummy package. It can safely be removed. > . > firefox is now replaced by the firefox snap. So I suggest we change it. ** Affects: chromium-browser (Ubuntu) Importance: Low Assignee: Nathan Teodosio (nteodosio) Status: Triaged ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Description changed: They not only install the corresponding snap but also at least have some hooks to update-alternatives and also provide www-browser, x-www- browser, gnome-www-browser. As such, removing the package might result in installation of something preposterous such as wslu to satisfy such a meta-package dependency, as reported in LP:2060898. + + The packages' description might lead one to remove them expecting no + side effects: + + > Description-en: Transitional package - firefox -> firefox snap + > This is a transitional dummy package. It can safely be removed. + > . + > firefox is now replaced by the firefox snap. + + So I suggest we change it. -- 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/2061075 Title: firefox, chromium-browser are not merely a transitional packages Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: New Bug description: They not only install the corresponding snap but also at least have some hooks to update-alternatives and also provide www-browser, x-www- browser, gnome-www-browser. As such, removing the package might result in installation of something preposterous such as wslu to satisfy such a meta-package dependency, as reported in LP:2060898. The packages' description might lead one to remove them expecting no side effects: > Description-en: Transitional package - firefox -> firefox snap > This is a transitional dummy package. It can safely be removed. > . > firefox is now replaced by the firefox snap. So I suggest we change it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061075/+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 1901077] Re: Chromium Browser (snap) Does Not Delete Cookies and Web Site Data When Being Closed
MikeV, can you describe more precisely what you mean with "not working" in the duplicate bug report? How did you ascertain this? Were all or only a handful of cookies still present after restarting Chromium? Can you start Chromium in the command line with 'chromium --enable- logging=stderr &> chr.log', close it as you normally do and then attach the result here? -- 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/1901077 Title: Chromium Browser (snap) Does Not Delete Cookies and Web Site Data When Being Closed Status in chromium-browser package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 $ uname -a Linux Zweiblum 5.4.0-51-generic #56-Ubuntu SMP Mon Oct 5 14:28:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: gestern um 18:33 CEST channels: latest/stable:86.0.4240.111 2020-10-21 (1362) 170MB - latest/candidate: 86.0.4240.111 2020-10-21 (1362) 170MB - latest/beta: 87.0.4280.20 2020-10-16 (1357) 172MB - latest/edge: 88.0.4292.2 2020-10-16 (1358) 173MB - installed: 86.0.4240.111(1362) 170MB - I enabled "Cookies und Websitedaten beim Beenden von Chromium löschen" (Delete Cookies and Web Site Data when exiting Chromium). Still, after quitting and restarting Chromium, the list of sites with stored Cookies and other information under "Alle Cookies und Websitedaten anzeigen" (Show all Cookies and Web Site Data) is huge. I expect it to be empty after a restart, except for maybe some specific white-listed Cookies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1901077/+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 2060976] Re: Create autopkgtest
** Patch added: "freerdp2.diff" https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/2060976/+attachment/5763791/+files/freerdp2.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/2060976 Title: Create autopkgtest Status in freerdp2 package in Ubuntu: New Bug description: Ran successfully with autopkgtest -B . -- schroot noble-amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/2060976/+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 2060976] [NEW] Create autopkgtest
Public bug reported: Ran successfully with autopkgtest -B . -- schroot noble-amd64. ** Affects: freerdp2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/2060976 Title: Create autopkgtest Status in freerdp2 package in Ubuntu: New Bug description: Ran successfully with autopkgtest -B . -- schroot noble-amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/2060976/+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 2057842] Re: FFe: [MIR] freedp2 -> freerdp3 in main
** Patch removed: "freerdp3.diff"
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2057842/+attachment/5759842/+files/freerdp3.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2057842
Title:
FFe: [MIR] freedp2 -> freerdp3 in main
Status in freerdp3 package in Ubuntu:
Fix Released
Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in remmina package in Ubuntu:
Fix Released
Bug description:
Feature Freeze Exception Request
--
There are only 2 packages in Ubuntu main that use freerdp2: remmina and
gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore
only one version of freerdp will be in main. freerdp2 will be demoted to
universe since many universe packages use it and are not prepared to switch to
freerdp3.
This also requests updating gnome-control-center to fully enable the
features of gnome-remote-desktop 46.
Impact
--
A headline feature of GNOME 46 is support as a Remote Desktop server without
requiring someone to already be logged in locally ("headless" mode). This
feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires
freerdp3.
Impact if this does not happen
--
- We would need to patch gnome-control-center to use the older Remote Desktop
panel (or at least hide the new tab for Remote Login)
- We would need to keep using gnome-remote-desktop 45 instead of 46. The
gnome-remote-desktop upstream maintainers would be unhappy with this decision.
gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may
require changes in gnome-remote-desktop for things to work well although a
simple test showed that basic remote desktop seems to work ok with the
mismatch. (See comment #1 from upstream developer.)
Why this did not land sooner
---
It required the packaging of a new source package freerdp3. And we had to do
this sooner than Debian. Sorry too many things to do before Feature Freeze and
this did not make it.
Affected Packages
-
- gnome-remote-desktop 45 -> 46
- gnome-control-center (to update the Remote Desktop settings page)
- remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not
work with freerdp 3.3 in my testing
- gnome-connections (build-dependency swap): Not required by other changes
and not in Main but makes sense to switch it also
Affected Flavors
Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center,
gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships
gnome-control-center but this appears to be a bug since they ship
cinnamon-control-center and is likely already fixed in noble-proposed)
Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.
gnome-connections has no reverse dependencies or recommends.
Upstream Changes
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS
https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md
gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature
Freeze. It will be updated to 46.0. The relevant part here is whether we use
the 46~beta version of the Remote Desktop page or the 46.0 version.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS
Build Logs
--
I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA.
The PPA currently has noble-proposed disabled so that it is easily possible to
try this set of packages without dealing with the incomplete 32-bit time
transition in noble-proposed. In addition, the PPA has the affected packages
from this FFe.
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages
Testing Done
---
1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect
to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46
RC. Remote control worked.
2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with
freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control
worked.
3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built
with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote
control worked.
4. I added a new Remote Login test case to
https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop and
verified that remote login worked. Notably, enabling this changes the
port for the older service, now called "Desktop Sharing" to 3390.
Since 3389 is the default port, users would then need to manually
specific port 3390 for Desktop Sharing in their remote connection app
(Remmina, GNOME Connections, etc.).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp3/+bug/2057842/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 2060915] [NEW] Comments in source files flood "other software"
Public bug reported: Reproduction case: Add the attached source file to /etc/apt/sources.list.d/. You don't need to 'apt update' for this test. Open software-properties-gtk. Issue: All the comments at the top of the file are displayed, flooding the interface. Limiting the number of comment lines displayed and only displaying the full comments in a tool tip (GTK.Tree has a couple of set_tooltip functions) may result in a better user interface. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "foo-bar.sources" https://bugs.launchpad.net/bugs/2060915/+attachment/5763609/+files/foo-bar.sources ** Merge proposal linked: https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/463886 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2060915 Title: Comments in source files flood "other software" Status in software-properties package in Ubuntu: New Bug description: Reproduction case: Add the attached source file to /etc/apt/sources.list.d/. You don't need to 'apt update' for this test. Open software-properties-gtk. Issue: All the comments at the top of the file are displayed, flooding the interface. Limiting the number of comment lines displayed and only displaying the full comments in a tool tip (GTK.Tree has a couple of set_tooltip functions) may result in a better user interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060915/+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 2050884] Re: Ubuntu Metrics server is not accepting reports
Corrado, the released fix was only for the consumer (gnome-initial- setup). I think that, if you chose to send system information to Canonical and it failed, which is at the moment guaranteed to happen because the service is not up yet, ubuntu-report schedules a new attempt to send the report. If that is ad infinitum or spams your system logs, please file a new bug against ubuntu-report[1]. [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+filebug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2050884 Title: Ubuntu Metrics server is not accepting reports Status in gnome-initial-setup package in Ubuntu: Fix Released Status in ubuntu-report package in Ubuntu: Triaged Bug description: gnome-initial-setup now prompts to send a report immediately, and when it does, it fails, I'll attach a screenshot in the comments. Even when I clicked "Don't send to ubuntu" or however it's phrased, I still encountered the error message pop up in the comments. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-initial-setup 46~alpha-2ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 10:38:31 2024 InstallationDate: Installed on 2024-01-23 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2050884/+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 2050884] Re: Ubuntu Metrics server is not accepting reports
** Changed in: gnome-initial-setup (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2050884 Title: Ubuntu Metrics server is not accepting reports Status in gnome-initial-setup package in Ubuntu: Fix Released Status in ubuntu-report package in Ubuntu: Triaged Bug description: gnome-initial-setup now prompts to send a report immediately, and when it does, it fails, I'll attach a screenshot in the comments. Even when I clicked "Don't send to ubuntu" or however it's phrased, I still encountered the error message pop up in the comments. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-initial-setup 46~alpha-2ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 10:38:31 2024 InstallationDate: Installed on 2024-01-23 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2050884/+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 2049670] Re: noble: gnome-initial-setup 20 second delay & error popup
** Changed in: gnome-initial-setup (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2049670 Title: noble: gnome-initial-setup 20 second delay & error popup Status in gnome-initial-setup package in Ubuntu: Fix Released Bug description: When GNOME Initial Setup is run in Ubuntu 24.04 LTS (the current development release), when clicking Next on the "Help improve Ubuntu" screen, the Initial Setup pauses for 20 seconds then shows a popup dialog (screenshot attached). This happens regardless of whether Yes or No is chosen on that screen. Sometimes, the app might go to the next screen and close the popup dialog itself. Logs GNOME Initial Setup can be run from the command line by running /usr/libexec/gnome-initial-setup --existing-user When run from the command line, these warnings are emitted: InitialSetup-Message: Starting gnome-initial-setup InitialSetup-Message: Production mode: changes will be saved to disk INFO[0003] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: open /var/lib/ubuntu_dist_channel: no such file or directory (gnome-initial-setup): InitialSetup-WARNING **: Failed to send report information: data were not delivered successfully to metrics server, saving for a later automated report: couldn't send post http request: Post "https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline exceeded (Client.Timeout exceeded while awaiting headers) INFO[0107] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: open /var/lib/ubuntu_dist_channel: no such file or directory Logs 2 == If No is selected, the command-line warning is slightly different. Failed to send report decline: data were not delivered successfully to metrics server, saving for a later automated report: couldn't send post http request: Post "https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Other Info == Perhaps the metrics server is not set up for Ubuntu 24.04 LTS yet? This bug is related to bug 1761742 and I agree with comment #3 there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2049670/+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 2060094] Re: Packaging: Provide chromium
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/2060094 Title: Packaging: Provide chromium Status in chromium-browser package in Ubuntu: Fix Released Bug description: Debian provides the Chromium browser in the chromium package; we, in chromium-browser package. A package that depends on 'chromium' was autosynced. So this provides for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2060094/+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 1719572] Re: chromedriver can't click links outside of the window with Chromium 61
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released -- 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/1719572 Title: chromedriver can't click links outside of the window with Chromium 61 Status in chromium-browser package in Ubuntu: Fix Released Bug description: The latest version of chromium (61) introduces a change that breaks the ability of clicking to links outside of the current view using chromedriver. It seems that there is a fix for it in chromedriver 2.32: > Fixes a bug where Chromedriver fails to click due to page scrolling changes in Chrome 61+. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1719572/+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 2049493] Re: rustc 1.71 version needed in jammy to build chromium updates for ARM
** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Released ** Changed in: rustc (Ubuntu) Status: New => Incomplete ** Changed in: rustc (Ubuntu) Status: Incomplete => Fix Released -- 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/2049493 Title: rustc 1.71 version needed in jammy to build chromium updates for ARM Status in chromium-browser package in Ubuntu: Fix Released Status in rustc package in Ubuntu: Fix Released Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+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 2060282] [NEW] Giflib 5.2.2-1 fails to build
Public bug reported: https://launchpadlibrarian.net/721167206/buildlog_ubuntu-noble- amd64.giflib_5.2.2-1_BUILDING.txt.gz Upstream bug: https://sourceforge.net/p/giflib/bugs/170/ ** Affects: giflib (Ubuntu) Importance: Undecided Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to giflib in Ubuntu. https://bugs.launchpad.net/bugs/2060282 Title: Giflib 5.2.2-1 fails to build Status in giflib package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/721167206/buildlog_ubuntu-noble- amd64.giflib_5.2.2-1_BUILDING.txt.gz Upstream bug: https://sourceforge.net/p/giflib/bugs/170/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/2060282/+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 2060282] Re: Giflib 5.2.2-1 fails to build
** Patch added: "giflib.diff" https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/2060282/+attachment/5761636/+files/giflib.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to giflib in Ubuntu. https://bugs.launchpad.net/bugs/2060282 Title: Giflib 5.2.2-1 fails to build Status in giflib package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/721167206/buildlog_ubuntu-noble- amd64.giflib_5.2.2-1_BUILDING.txt.gz Upstream bug: https://sourceforge.net/p/giflib/bugs/170/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/2060282/+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 2060282] Re: Giflib 5.2.2-1 fails to build
** Bug watch added: Debian Bug tracker #1068438 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068438 ** Also affects: giflib (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068438 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to giflib in Ubuntu. https://bugs.launchpad.net/bugs/2060282 Title: Giflib 5.2.2-1 fails to build Status in giflib package in Ubuntu: Fix Committed Status in giflib package in Debian: Unknown Bug description: https://launchpadlibrarian.net/721167206/buildlog_ubuntu-noble- amd64.giflib_5.2.2-1_BUILDING.txt.gz Upstream bug: https://sourceforge.net/p/giflib/bugs/170/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/2060282/+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 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
This seems not to be an issue any more. Feel free to reset the status if otherwise. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released -- 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/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Fix Released Bug description: I upgraded from Focal to Groovy, and now the first launch of the Chromium snap after a reboot is taking much longer than before. On my main home laptop it takes over 30 seconds, while under Focal I don't remember it taking more than 10 seconds. I tried another computer I could erase. On Groovy that computer takes nearly a minute to launch the Chromium snap after rebooting. Then I clean installed Focal on the same machine, and the Chromium snap takes just under 10 seconds to launch after a reboot. For both I installed all updates, and I let the computer sit idle for a few minutes after rebooting to try to rule out other activity. I haven’t noticed the change for any other snap, although I don’t use any that I ever noticed as much of a launch delay as Chromium. (VS Code for one doesn’t seem slower — certainly not taking nearly a minute — but I haven't done a real comparison like for Chromium.) ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 21:29:20 2020 InstallationDate: Installed on 2020-04-01 (202 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Snap: chromium 87.0.4280.20 (latest/beta) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+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 2058840] Re: Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Committed
--
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/2058840
Title:
Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Status in chromium-browser package in Ubuntu:
Fix Committed
Bug description:
Ubuntu 22.04 LTS Jammy x64
I hope this is the correct package to assign this request to:
In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to
decrypt its password store.
This makes all stored passwords unavailable as soon as the system is
upgraded from Plasma 5 to Plasma 6.
Chromium writes the following error messages to the console:
-
[5362:5362:0324/103716.837413:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="isEnabled" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.837451:ERROR:kwallet_dbus.cc(112)] Error contacting
kwalletd6 (isEnabled)
[5362:5362:0324/103716.838022:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KLauncher.start_service_by_desktop_name: object_path=
/KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.kde.klauncher was not provided by any .service files
[5362:5362:0324/103716.838042:ERROR:kwallet_dbus.cc(81)] Error contacting
klauncher to start kwalletd6
[5362:5362:0324/103716.838264:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.close: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="close" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.838295:ERROR:kwallet_dbus.cc(503)] Error contacting
kwalletd6 (close)
-
Followed by hundreds of messages as the following:
-
ERROR:login_database.cc(1046) Password decryption failed, encryption_result
is 2
-
It appears to work to "just" whitelist the new kwalletd module name in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium (and maybe
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver ?)
followed by
$ systemctl restart apparmor
$ systemctl restart snapd.apparmor
$ systemctl restart apparmor
(Not sure if both of these are necessary, and if so, in what order.)
and completely restart Chromium.
The new KWallet section looks as follows - I only added the ",6" to
the patterns:
-
# KWallet's client API is still in use in KDE/Plasma. It's DBus API relies
upon
# member data for access to its 'folders' and 'entries' and it therefore does
# not allow for application isolation via AppArmor. For details, see:
# - https://cgit.kde.org/kdelibs.git/tree/kdeui/util/kwallet.h?h=v4.14.33
#
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.freedesktop.DBus.*
peer=(label=unconfined),
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.kde.KWallet
peer=(label=unconfined),
-
I hope that at least this report may be found by other people running
into the same trouble I just did...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058840/+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 2017011] Re: [snap] unable to read /proc/pressure/{cpu, io, memory}
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
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/2017011
Title:
[snap] unable to read /proc/pressure/{cpu,io,memory}
Status in chromium-browser package in Ubuntu:
Fix Released
Bug description:
During normal operation, chromium wants to read
/proc/pressure/{cpu,io,memory} but is denied by the Apparmor policy:
$ journalctl -b0 -k --grep 'chromium.chromium' | grep -F
'name="/proc/pressure/'
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:817): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:818): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:819): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Note that simply starting the browser doesn't prompt it try and read
those files, you need to do something more involving like watching
Youtube for example.
Additional information:
$ snap list chromium core20
Name VersionRev Tracking Publisher Notes
chromium 112.0.5615.49 2424 latest/stable canonical✓ -
core2020230308 1852 latest/stable canonical✓ base
$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
$ uname -a
Linux sdeziel-lemur 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017011/+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 2017011] Re: [snap] unable to read /proc/pressure/{cpu, io, memory}
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
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/2017011
Title:
[snap] unable to read /proc/pressure/{cpu,io,memory}
Status in chromium-browser package in Ubuntu:
Fix Committed
Bug description:
During normal operation, chromium wants to read
/proc/pressure/{cpu,io,memory} but is denied by the Apparmor policy:
$ journalctl -b0 -k --grep 'chromium.chromium' | grep -F
'name="/proc/pressure/'
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:817): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:818): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:819): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Note that simply starting the browser doesn't prompt it try and read
those files, you need to do something more involving like watching
Youtube for example.
Additional information:
$ snap list chromium core20
Name VersionRev Tracking Publisher Notes
chromium 112.0.5615.49 2424 latest/stable canonical✓ -
core2020230308 1852 latest/stable canonical✓ base
$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
$ uname -a
Linux sdeziel-lemur 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017011/+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 2060094] Re: Packaging: Provide chromium
** Patch added: "chr.diff" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2060094/+attachment/5761408/+files/chr.diff -- 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/2060094 Title: Packaging: Provide chromium Status in chromium-browser package in Ubuntu: Triaged Bug description: Debian provides the Chromium browser in the chromium package; we, in chromium-browser package. A package that depends on 'chromium' was autosynced. So this provides for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2060094/+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 2060094] [NEW] Packaging: Provide chromium
Public bug reported: Debian provides the Chromium browser in the chromium package; we, in chromium-browser package. A package that depends on 'chromium' was autosynced. So this provides for it. ** Affects: chromium-browser (Ubuntu) Importance: Low Assignee: Nathan Teodosio (nteodosio) Status: Triaged -- 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/2060094 Title: Packaging: Provide chromium Status in chromium-browser package in Ubuntu: Triaged Bug description: Debian provides the Chromium browser in the chromium package; we, in chromium-browser package. A package that depends on 'chromium' was autosynced. So this provides for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2060094/+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 2017011] Re: [snap] unable to read /proc/pressure/{cpu, io, memory}
I'm changing the logging period from 10 minutes to 10 days, as in this
case it's better not to suppress the error entirely as the information
in those files might be used for something more substantial in the
future.
I pushed the changes to beta and edge, the latter of which is currently
building. Once the change is confirmed I'll push it to stable too.
--
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/2017011
Title:
[snap] unable to read /proc/pressure/{cpu,io,memory}
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
During normal operation, chromium wants to read
/proc/pressure/{cpu,io,memory} but is denied by the Apparmor policy:
$ journalctl -b0 -k --grep 'chromium.chromium' | grep -F
'name="/proc/pressure/'
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:817): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:818): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:819): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Note that simply starting the browser doesn't prompt it try and read
those files, you need to do something more involving like watching
Youtube for example.
Additional information:
$ snap list chromium core20
Name VersionRev Tracking Publisher Notes
chromium 112.0.5615.49 2424 latest/stable canonical✓ -
core2020230308 1852 latest/stable canonical✓ base
$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
$ uname -a
Linux sdeziel-lemur 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017011/+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 2017011] Re: [snap] unable to read /proc/pressure/{cpu, io, memory}
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
--
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/2017011
Title:
[snap] unable to read /proc/pressure/{cpu,io,memory}
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
During normal operation, chromium wants to read
/proc/pressure/{cpu,io,memory} but is denied by the Apparmor policy:
$ journalctl -b0 -k --grep 'chromium.chromium' | grep -F
'name="/proc/pressure/'
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:817): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:818): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:819): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Note that simply starting the browser doesn't prompt it try and read
those files, you need to do something more involving like watching
Youtube for example.
Additional information:
$ snap list chromium core20
Name VersionRev Tracking Publisher Notes
chromium 112.0.5615.49 2424 latest/stable canonical✓ -
core2020230308 1852 latest/stable canonical✓ base
$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
$ uname -a
Linux sdeziel-lemur 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017011/+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 2058881] Re: [snap] Allow chromium snap to access Pressure Stall Information (PSI)
*** This bug is a duplicate of bug 2017011 ***
https://bugs.launchpad.net/bugs/2017011
** Changed in: chromium-browser (Ubuntu)
Importance: Wishlist => Low
** Tags added: log-noise
** This bug has been marked a duplicate of bug 2017011
[snap] unable to read /proc/pressure/{cpu,io,memory}
--
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/2058881
Title:
[snap] Allow chromium snap to access Pressure Stall Information (PSI)
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Hi,
Currently seeing this:
| Mar 25 16:12:23 dharkan.local kernel: audit: type=1400
audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
| Mar 25 16:12:23 dharkan.local kernel: audit: type=1400
audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0
| Mar 25 16:12:23 dharkan.local kernel: audit: type=1400
audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid>
It seems the AppAmor profile should be updated to allow Chromium
access to the pressure stall information for it to monitor and manage
it's processes?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058881/+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 2059412] [NEW] SyntaxWarning: invalid escape sequence '\.'
Public bug reported:
Installing software-properties gives
--->
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197:
SyntaxWarning: invalid escape sequence '\.'
elif
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
uri) == None:
<---
Marked as "wishlist" importance because Python still passes that to
re.match as '\.' instead of '.', so the behavior is correct, as can be
confirmed with
--->
% python3 -c 'print("\.")'
:1: SyntaxWarning: invalid escape sequence '\.'
\.
<---
** Affects: software-properties (Ubuntu)
Importance: Wishlist
Assignee: Nathan Teodosio (nteodosio)
Status: Triaged
** Description changed:
Installing software-properties gives
--->
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197:
SyntaxWarning: invalid escape sequence '\.'
- elif
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
uri) == None:
+ elif
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
uri) == None:
<---
+
+ Marked as "wishlist" importance because Python still passes that to
+ re.match as '\.' instead of '.', so the behavior is correct, as can be
+ confirmed with
+
+ --->
+ % python3 -c 'print("\.")'
+ :1: SyntaxWarning: invalid escape sequence '\.'
+ \.
+ <---
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/2059412
Title:
SyntaxWarning: invalid escape sequence '\.'
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Installing software-properties gives
--->
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197:
SyntaxWarning: invalid escape sequence '\.'
elif
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
uri) == None:
<---
Marked as "wishlist" importance because Python still passes that to
re.match as '\.' instead of '.', so the behavior is correct, as can be
confirmed with
--->
% python3 -c 'print("\.")'
:1: SyntaxWarning: invalid escape sequence '\.'
\.
<---
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059412/+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 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript
The fix is in Snapd beta and should be in stable in the next month or so. ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Released ** Changed in: firefox (Ubuntu) Status: In Progress => Fix Released -- 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/2032992 Title: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1) Install chromium snap snap install chromium 2) Install openjdk-21 documentation sudo apt install openjdk-21-doc 3) Browse API documentation chromium /usr/share/doc/openjdk-21-doc/api/index.html The search bar is inactive and dev console contains: jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND $ls -l /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js lrwxrwxrwx 1 root root 43 Mar 17 13:31 /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js -> ../../../../javascript/jquery/jquery.min.js cat /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js prints the file contents Downloaded version of chrome opens documentation with active search bar and no javascript errors /tmp/chrome/chrome /usr/share/doc/openjdk-21-doc/api/index.html Expected results: Chromium snap should be able to follow symlink into /usr/share/javascript and correctly load OpenJDK API documentation. Note: this probably should be a specific exclusion for Debian-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/2032992/+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 2050884] Re: Ubuntu Metrics server is not accepting reports
https://salsa.debian.org/gnome-team/gnome-initial- setup/-/merge_requests/23 ** Changed in: gnome-initial-setup (Ubuntu) Status: Triaged => In Progress ** Changed in: gnome-initial-setup (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2050884 Title: Ubuntu Metrics server is not accepting reports Status in gnome-initial-setup package in Ubuntu: In Progress Status in ubuntu-report package in Ubuntu: Triaged Bug description: gnome-initial-setup now prompts to send a report immediately, and when it does, it fails, I'll attach a screenshot in the comments. Even when I clicked "Don't send to ubuntu" or however it's phrased, I still encountered the error message pop up in the comments. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-initial-setup 46~alpha-2ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 10:38:31 2024 InstallationDate: Installed on 2024-01-23 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2050884/+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 2059267] [NEW] Ubuntu patch reverting another Ubuntu patch
Public bug reported:
Downstream Update-style-to-the-same-than-flutter-installer.patch[1] is
reverting a great deal of gis-apps-page.{c,ui} that are introduced by
(also downstream controlled) 0001-Add-Ubuntu-mode-with-special-
pages.patch[2].
I think that makes maintaining those patches more complex than necessary
and suggest to merge them together.
[1]
https://git.launchpad.net/ubuntu/+source/gnome-initial-setup/tree/debian/patches/Update-style-to-the-same-than-flutter-installer.patch
[2]
https://git.launchpad.net/ubuntu/+source/gnome-initial-setup/tree/debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch#n399
** Affects: gnome-initial-setup (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-initial-setup in Ubuntu.
https://bugs.launchpad.net/bugs/2059267
Title:
Ubuntu patch reverting another Ubuntu patch
Status in gnome-initial-setup package in Ubuntu:
New
Bug description:
Downstream Update-style-to-the-same-than-flutter-installer.patch[1] is
reverting a great deal of gis-apps-page.{c,ui} that are introduced by
(also downstream controlled) 0001-Add-Ubuntu-mode-with-special-
pages.patch[2].
I think that makes maintaining those patches more complex than
necessary and suggest to merge them together.
[1]
https://git.launchpad.net/ubuntu/+source/gnome-initial-setup/tree/debian/patches/Update-style-to-the-same-than-flutter-installer.patch
[2]
https://git.launchpad.net/ubuntu/+source/gnome-initial-setup/tree/debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch#n399
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2059267/+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 2057842] Re: FFe: [MIR] freedp2 -> freerdp3 in main
Actually please hold that for a moment, I had forgotten to enable other
architectures in the PPA and a test is failing in Armhf.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2057842
Title:
FFe: [MIR] freedp2 -> freerdp3 in main
Status in freerdp3 package in Ubuntu:
Fix Released
Status in gnome-remote-desktop package in Ubuntu:
Fix Committed
Status in remmina package in Ubuntu:
Fix Committed
Bug description:
Feature Freeze Exception Request
--
There are only 2 packages in Ubuntu main that use freerdp2: remmina and
gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore
only one version of freerdp will be in main. freerdp2 will be demoted to
universe since many universe packages use it and are not prepared to switch to
freerdp3.
This also requests updating gnome-control-center to fully enable the
features of gnome-remote-desktop 46.
Impact
--
A headline feature of GNOME 46 is support as a Remote Desktop server without
requiring someone to already be logged in locally ("headless" mode). This
feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires
freerdp3.
Impact if this does not happen
--
- We would need to patch gnome-control-center to use the older Remote Desktop
panel (or at least hide the new tab for Remote Login)
- We would need to keep using gnome-remote-desktop 45 instead of 46. The
gnome-remote-desktop upstream maintainers would be unhappy with this decision.
gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may
require changes in gnome-remote-desktop for things to work well although a
simple test showed that basic remote desktop seems to work ok with the
mismatch. (See comment #1 from upstream developer.)
Why this did not land sooner
---
It required the packaging of a new source package freerdp3. And we had to do
this sooner than Debian. Sorry too many things to do before Feature Freeze and
this did not make it.
Affected Packages
-
- gnome-remote-desktop 45 -> 46
- gnome-control-center (to update the Remote Desktop settings page)
- remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not
work with freerdp 3.3 in my testing
- gnome-connections (build-dependency swap): Not required by other changes
and not in Main but makes sense to switch it also
Affected Flavors
Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center,
gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships
gnome-control-center but this appears to be a bug since they ship
cinnamon-control-center and is likely already fixed in noble-proposed)
Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.
gnome-connections has no reverse dependencies or recommends.
Upstream Changes
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS
https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md
gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature
Freeze. It will be updated to 46.0. The relevant part here is whether we use
the 46~beta version of the Remote Desktop page or the 46.0 version.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS
Build Logs
--
I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA.
The PPA currently has noble-proposed disabled so that it is easily possible to
try this set of packages without dealing with the incomplete 32-bit time
transition in noble-proposed. In addition, the PPA has the affected packages
from this FFe.
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages
Testing Done
---
1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect
to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46
RC. Remote control worked.
2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with
freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control
worked.
3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built
with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote
control worked.
4. I added a new Remote Login test case to
https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop and
verified that remote login worked. Notably, enabling this changes the
port for the older service, now called "Desktop Sharing" to 3390.
Since 3389 is the default port, users would then need to manually
specific port 3390 for Desktop Sharing in their remote connection app
(Remmina, GNOME Connections, etc.).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp3/+bug/2057842/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 2057842] Re: FFe: [MIR] freedp2 -> freerdp3 in main
The following debdiff enables the build tests and runs them as
autopkgtests, which as per [1] run successfully.
[1] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-nteodosio-
rebuilds/noble/amd64/f/freerdp3/20240326_213622_91f66@/log.gz
** Patch added: "freerdp3.diff"
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2057842/+attachment/5759842/+files/freerdp3.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2057842
Title:
FFe: [MIR] freedp2 -> freerdp3 in main
Status in freerdp3 package in Ubuntu:
Fix Released
Status in gnome-remote-desktop package in Ubuntu:
Fix Committed
Status in remmina package in Ubuntu:
Fix Committed
Bug description:
Feature Freeze Exception Request
--
There are only 2 packages in Ubuntu main that use freerdp2: remmina and
gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore
only one version of freerdp will be in main. freerdp2 will be demoted to
universe since many universe packages use it and are not prepared to switch to
freerdp3.
This also requests updating gnome-control-center to fully enable the
features of gnome-remote-desktop 46.
Impact
--
A headline feature of GNOME 46 is support as a Remote Desktop server without
requiring someone to already be logged in locally ("headless" mode). This
feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires
freerdp3.
Impact if this does not happen
--
- We would need to patch gnome-control-center to use the older Remote Desktop
panel (or at least hide the new tab for Remote Login)
- We would need to keep using gnome-remote-desktop 45 instead of 46. The
gnome-remote-desktop upstream maintainers would be unhappy with this decision.
gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may
require changes in gnome-remote-desktop for things to work well although a
simple test showed that basic remote desktop seems to work ok with the
mismatch. (See comment #1 from upstream developer.)
Why this did not land sooner
---
It required the packaging of a new source package freerdp3. And we had to do
this sooner than Debian. Sorry too many things to do before Feature Freeze and
this did not make it.
Affected Packages
-
- gnome-remote-desktop 45 -> 46
- gnome-control-center (to update the Remote Desktop settings page)
- remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not
work with freerdp 3.3 in my testing
- gnome-connections (build-dependency swap): Not required by other changes
and not in Main but makes sense to switch it also
Affected Flavors
Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center,
gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships
gnome-control-center but this appears to be a bug since they ship
cinnamon-control-center and is likely already fixed in noble-proposed)
Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.
gnome-connections has no reverse dependencies or recommends.
Upstream Changes
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS
https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md
gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature
Freeze. It will be updated to 46.0. The relevant part here is whether we use
the 46~beta version of the Remote Desktop page or the 46.0 version.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS
Build Logs
--
I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA.
The PPA currently has noble-proposed disabled so that it is easily possible to
try this set of packages without dealing with the incomplete 32-bit time
transition in noble-proposed. In addition, the PPA has the affected packages
from this FFe.
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages
Testing Done
---
1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect
to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46
RC. Remote control worked.
2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with
freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control
worked.
3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built
with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote
control worked.
4. I added a new Remote Login test case to
https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop and
verified that remote login worked. Notably, enabling this changes the
port for the older service, now called "Desktop Sharing" to 3390.
Since 3389 is the default port, users would then need to manually
[Desktop-packages] [Bug 2058840] Re: Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Opened merge request for Snapd:
https://github.com/snapcore/snapd/pull/13757.
--
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/2058840
Title:
Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
Ubuntu 22.04 LTS Jammy x64
I hope this is the correct package to assign this request to:
In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to
decrypt its password store.
This makes all stored passwords unavailable as soon as the system is
upgraded from Plasma 5 to Plasma 6.
Chromium writes the following error messages to the console:
-
[5362:5362:0324/103716.837413:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="isEnabled" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.837451:ERROR:kwallet_dbus.cc(112)] Error contacting
kwalletd6 (isEnabled)
[5362:5362:0324/103716.838022:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KLauncher.start_service_by_desktop_name: object_path=
/KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.kde.klauncher was not provided by any .service files
[5362:5362:0324/103716.838042:ERROR:kwallet_dbus.cc(81)] Error contacting
klauncher to start kwalletd6
[5362:5362:0324/103716.838264:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.close: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="close" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.838295:ERROR:kwallet_dbus.cc(503)] Error contacting
kwalletd6 (close)
-
Followed by hundreds of messages as the following:
-
ERROR:login_database.cc(1046) Password decryption failed, encryption_result
is 2
-
It appears to work to "just" whitelist the new kwalletd module name in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium (and maybe
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver ?)
followed by
$ systemctl restart apparmor
$ systemctl restart snapd.apparmor
$ systemctl restart apparmor
(Not sure if both of these are necessary, and if so, in what order.)
and completely restart Chromium.
The new KWallet section looks as follows - I only added the ",6" to
the patterns:
-
# KWallet's client API is still in use in KDE/Plasma. It's DBus API relies
upon
# member data for access to its 'folders' and 'entries' and it therefore does
# not allow for application isolation via AppArmor. For details, see:
# - https://cgit.kde.org/kdelibs.git/tree/kdeui/util/kwallet.h?h=v4.14.33
#
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.freedesktop.DBus.*
peer=(label=unconfined),
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.kde.KWallet
peer=(label=unconfined),
-
I hope that at least this report may be found by other people running
into the same trouble I just did...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058840/+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 2058840] Re: Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
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/2058840
Title:
Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
Ubuntu 22.04 LTS Jammy x64
I hope this is the correct package to assign this request to:
In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to
decrypt its password store.
This makes all stored passwords unavailable as soon as the system is
upgraded from Plasma 5 to Plasma 6.
Chromium writes the following error messages to the console:
-
[5362:5362:0324/103716.837413:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="isEnabled" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.837451:ERROR:kwallet_dbus.cc(112)] Error contacting
kwalletd6 (isEnabled)
[5362:5362:0324/103716.838022:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KLauncher.start_service_by_desktop_name: object_path=
/KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.kde.klauncher was not provided by any .service files
[5362:5362:0324/103716.838042:ERROR:kwallet_dbus.cc(81)] Error contacting
klauncher to start kwalletd6
[5362:5362:0324/103716.838264:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.close: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="close" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.838295:ERROR:kwallet_dbus.cc(503)] Error contacting
kwalletd6 (close)
-
Followed by hundreds of messages as the following:
-
ERROR:login_database.cc(1046) Password decryption failed, encryption_result
is 2
-
It appears to work to "just" whitelist the new kwalletd module name in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium (and maybe
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver ?)
followed by
$ systemctl restart apparmor
$ systemctl restart snapd.apparmor
$ systemctl restart apparmor
(Not sure if both of these are necessary, and if so, in what order.)
and completely restart Chromium.
The new KWallet section looks as follows - I only added the ",6" to
the patterns:
-
# KWallet's client API is still in use in KDE/Plasma. It's DBus API relies
upon
# member data for access to its 'folders' and 'entries' and it therefore does
# not allow for application isolation via AppArmor. For details, see:
# - https://cgit.kde.org/kdelibs.git/tree/kdeui/util/kwallet.h?h=v4.14.33
#
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.freedesktop.DBus.*
peer=(label=unconfined),
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.kde.KWallet
peer=(label=unconfined),
-
I hope that at least this report may be found by other people running
into the same trouble I just did...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058840/+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 2058881] Re: [snap] Allow chromium snap to access Pressure Stall Information (PSI)
I reproduced that now. Do you observe any problem or hindrance as a result of those denials? I had a look at the source code and it seems that it doesn't actually use that information for load balancing or anything of the sorts, but actually only for informational purposes, namely for assembling histograms and reporting the results to the so called UMA, User Metrics Analysis according to the developer's glossary, for instance if the user chooses to report a session crash back to Google. ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Wishlist -- 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/2058881 Title: [snap] Allow chromium snap to access Pressure Stall Information (PSI) Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi, Currently seeing this: | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid> It seems the AppAmor profile should be updated to allow Chromium access to the pressure stall information for it to monitor and manage it's processes? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058881/+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 2058840] Re: Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Hi Gunter, thanks for the report. From what I understand Plasma 6 is not
(and will not be) available in Ubuntu 24.04, did you get it in by
building it from source or by using some PPA? I ask because it would be
nice to reproduce your observations before incorporating a fix.
Many thanks for raising this way before Plasma 6 is released to Ubuntu,
this way we can assure this bug is gone by the time Plasma 6 becomes
officially supported in Ubuntu.
--
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/2058840
Title:
Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Status in chromium-browser package in Ubuntu:
New
Bug description:
Ubuntu 22.04 LTS Jammy x64
I hope this is the correct package to assign this request to:
In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to
decrypt its password store.
This makes all stored passwords unavailable as soon as the system is
upgraded from Plasma 5 to Plasma 6.
Chromium writes the following error messages to the console:
-
[5362:5362:0324/103716.837413:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="isEnabled" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.837451:ERROR:kwallet_dbus.cc(112)] Error contacting
kwalletd6 (isEnabled)
[5362:5362:0324/103716.838022:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KLauncher.start_service_by_desktop_name: object_path=
/KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.kde.klauncher was not provided by any .service files
[5362:5362:0324/103716.838042:ERROR:kwallet_dbus.cc(81)] Error contacting
klauncher to start kwalletd6
[5362:5362:0324/103716.838264:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.close: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="close" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.838295:ERROR:kwallet_dbus.cc(503)] Error contacting
kwalletd6 (close)
-
Followed by hundreds of messages as the following:
-
ERROR:login_database.cc(1046) Password decryption failed, encryption_result
is 2
-
It appears to work to "just" whitelist the new kwalletd module name in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium (and maybe
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver ?)
followed by
$ systemctl restart apparmor
$ systemctl restart snapd.apparmor
$ systemctl restart apparmor
(Not sure if both of these are necessary, and if so, in what order.)
and completely restart Chromium.
The new KWallet section looks as follows - I only added the ",6" to
the patterns:
-
# KWallet's client API is still in use in KDE/Plasma. It's DBus API relies
upon
# member data for access to its 'folders' and 'entries' and it therefore does
# not allow for application isolation via AppArmor. For details, see:
# - https://cgit.kde.org/kdelibs.git/tree/kdeui/util/kwallet.h?h=v4.14.33
#
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.freedesktop.DBus.*
peer=(label=unconfined),
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.kde.KWallet
peer=(label=unconfined),
-
I hope that at least this report may be found by other people running
into the same trouble I just did...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058840/+subscriptions
--
Mailing list:
Re: [Desktop-packages] [Bug 2058881] [NEW] [snap] Allow chromium snap to access Pressure Stall Information (PSI)
Hello, do you have a reproduction case? I don't get this when I launch Chromium, does it try that when on heavy load? -- 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/2058881 Title: [snap] Allow chromium snap to access Pressure Stall Information (PSI) Status in chromium-browser package in Ubuntu: New Bug description: Hi, Currently seeing this: | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid> It seems the AppAmor profile should be updated to allow Chromium access to the pressure stall information for it to monitor and manage it's processes? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058881/+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 2054887] Re: Grahpical bugs caused by unable to access libdrm
> the issue is still present Then I'm marking this as fixed and restricting its scope to just the missing amdgpu.ids. The actual rendering issue is already tracked in LP:2004532. > with the below errors Those are expected warnings, they don't relate to the reported issue. > The following command says that "chromium is already installed Ah, when you already have the snap installed you use 'snap refresh ...' instead. > I am starting to wonder if it is a bug not present in Chromium but in snap itself. I decided to try Firefox and the issue is present there too. Thanks for your proactivity with regards to investigating this bug. The lack of amdgpu.ids in the snap was indeed caused by snap confinement, but judging by the stderr we now have all files and libraries reachable, so a system library such as Mesa could also be playing a role in the bug. ** Summary changed: - Grahpical bugs caused by unable to access libdrm + Unable to access libdrm ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/2054887 Title: Unable to access libdrm Status in chromium-browser package in Ubuntu: Fix Released Bug description: Related: LP:2004532. The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 2058035] [NEW] [SRU] Create directories for apt configuration files if they are absent
Public bug reported: Impact -- The autopkgtest for 0.96.20.12, which introduces Ubuntu Pro in Xenial's software-properties, failed on Dbus tests[1]. The failure is because, at some point in time, the .keep file were removed from the otherwise empty tests/aptroot/etc/apt/apt.conf.d/. This caused the Git repository to drop tests/aptroot/etc/apt/apt.conf.d/ and also its parent, which also became empty, and the tests try to directly create files in those directories, raising the error. It seems that previous uploaders did not use the Git checkout, as the offending commit was introduced in Jun 2019 and there were subsequent uploads that did contain those empty directories. Test case - Trigger an autopkgtest against the proposed package version. It must succeed. Regression Potential Although the introduced change is idempotent, there could be other part of the code assuming the directories didn't exist and trying to create them with a "fail if already exists" approach, causing a runtime regression. [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- xenial/xenial/amd64/s/software-properties/20240301_100314_9e242@/log.gz ** Affects: software-properties (Ubuntu) Importance: Low Assignee: Nathan Teodosio (nteodosio) Status: In Progress ** Affects: software-properties (Ubuntu Xenial) Importance: High Assignee: Nathan Teodosio (nteodosio) Status: New ** Also affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Xenial) Importance: Undecided => High ** Changed in: software-properties (Ubuntu Xenial) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Merge proposal linked: https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/461724 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2058035 Title: [SRU] Create directories for apt configuration files if they are absent Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Xenial: New Bug description: Impact -- The autopkgtest for 0.96.20.12, which introduces Ubuntu Pro in Xenial's software-properties, failed on Dbus tests[1]. The failure is because, at some point in time, the .keep file were removed from the otherwise empty tests/aptroot/etc/apt/apt.conf.d/. This caused the Git repository to drop tests/aptroot/etc/apt/apt.conf.d/ and also its parent, which also became empty, and the tests try to directly create files in those directories, raising the error. It seems that previous uploaders did not use the Git checkout, as the offending commit was introduced in Jun 2019 and there were subsequent uploads that did contain those empty directories. Test case - Trigger an autopkgtest against the proposed package version. It must succeed. Regression Potential Although the introduced change is idempotent, there could be other part of the code assuming the directories didn't exist and trying to create them with a "fail if already exists" approach, causing a runtime regression. [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- xenial/xenial/amd64/s/software- properties/20240301_100314_9e242@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058035/+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 2017447] Re: chromium installs cupsd snap
You raise very valid concerns. However, at this point in time a maintainer of the snap can choose either to not install the Cups snap and have half of its users frustrated that printing does not work or to install the snap with no questions asked and frustrate a tiny fraction of that number. So as for Chromium, who we ought to frustrate is a opinion matter. A better dependency handling system or a prompt (to whether or not install Cups) would fit us here, but needs to be requested to Snapd. > canonical-published snaps can trigger installation of 3rd-party- published snaps The snap at hand is published by Open Printing[1], which is led by Till Kamppeter, who is also in Canonical. I underline that lest a less informed reader thinks that we just on a whim install whatever random third party snap. > despite specifically disabling the system-wide "APT::Install- Recommends" setting Yes, it would be nice if there were a way to honour this or a similar setting in Snapd too, unfortunately there is not one. [1] https://openprinting.github.io/about-us/ ** Changed in: chromium-browser (Ubuntu) Status: New => Opinion -- 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/2017447 Title: chromium installs cupsd snap Status in chromium-browser package in Ubuntu: Opinion Bug description: at some point, chromium has installed cupsd : cupsd isn't listed as installed in aptitude but it *is* listed under snap list if i wanted cups installed and printer support i would have installed it myself this shouldn't be installing itself through the backdoor via autoupdate there also doesn't seem to be anywhere in settings to turn it off Version 112.0.5615.49 (Official Build) snap (64-bit) (updated via snap refresh) ubuntu: 20.04 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Uname: Linux 6.0.7-gnulibre-squashfix x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 23 13:58:18 2023 InstallationDate: Installed on 2017-04-18 (2196 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 112.0.5615.49 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2020-04-25 (1093 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017447/+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 2056644] Re: Error from chromium-browser when doing do-release-upgrade from ubuntu 22 to 24
The log still says > Unable to reach the snap store Can you please try again once you can reach it? ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- 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/2056644 Title: Error from chromium-browser when doing do-release-upgrade from ubuntu 22 to 24 Status in chromium-browser package in Ubuntu: Invalid Bug description: I'm upgrading my odroid xu4 from ubuntu 22 to 24 because it wanted so when I logged in via ssh. I'm doing do-release-upgrade. It tried to migrate chromium to snap but couldn't contact the snap store. It seemed like some DNS resolution was broken (pinging anything gave Temporary failure in name resolution). I added 1.1.1.1 to /etc/resolv.conf and then do-release-upgrade could contact the snap store, but it printed some random error messages and suggested opening this bug report ProblemType: Package DistroRelease: Ubuntu 24.04 Package: chromium-browser 1:101.0.4951.15-0ubuntu1~ppa1~22.04.1ubuntu1 [modified: usr/lib/chromium-browser/libEGL.so usr/lib/chromium-browser/libGLESv2.so] ProcVersionSignature: Ubuntu 5.4.268-431 5.4.268-431 Uname: Linux 5.4.268-431 armv7l ApportVersion: 2.28.0-0ubuntu1 Architecture: armhf CasperMD5CheckResult: unknown Date: Sat Mar 9 15:53:18 2024 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.4ubuntu5 apt 2.7.12 SourcePackage: chromium-browser Title: package chromium-browser 1:101.0.4951.15-0ubuntu1~ppa1~22.04.1ubuntu1 [modified: usr/lib/chromium-browser/libEGL.so usr/lib/chromium-browser/libGLESv2.so] failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-03-09 (0 days ago) modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.default.apport: 2020-08-18T19:12:02.115260 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2056644/+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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
For Chromium users: Can you verify if either of snap remove chromium snap install --beta chromium or snap remove chromium snap install --channel internal-libdrm chromium fixes the issue? Note: A refresh will *not* work for the first case, it really needs to be removed and installed back (looks like there is a bug in Snapd). -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in ubuntu-spotify-app: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet
[Desktop-packages] [Bug 2054887] Re: Grahpical bugs caused by unable to access libdrm
** Description changed: + Related: LP:2004532. + The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy -- 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/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Related: LP:2004532. The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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
Re: [Desktop-packages] [Bug 2054887] Re: Grahpical bugs caused by unable to access libdrm
I can reproduce the issue if I refresh instead of really reinstalling the snap, so a bug in Snapd. Please try snap remove chromium snap install --beta chromium Does the amdgpu.ids error go away now? If that still doesn't solve the graphical bugs and you have time, it would also be very useful whether snap install --channel beta/internal-libdrm chromium works. -- 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/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Related: LP:2004532. The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Confirmed
--
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/2004532
Title:
Hardware acceleration broken for amdgpu/mesa in snap
Status in ubuntu-spotify-app:
New
Status in chromium-browser package in Ubuntu:
Confirmed
Status in firefox package in Ubuntu:
Fix Released
Bug description:
Snap packages which use hardware accelerated graphics are broken after
the last routine system upgrade via apt. My system is using AMD Radeon
RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers.
Two snap packages which are now unusable are Mozilla Firefox and
Chromium browsers. Both display animated speckled color garbage inside
their windows, overlayed with the correct image. Disabling hardware
acceleration in the settings for the snap version of Firefox fixed it.
Also, Firefox version installed from the original Mozilla tarball into
/opt/ works just fine with the acceleration enabled on the same
system, as well as glmark2 benchmark. Looks like the issue is only
affecting snap packages.
$ snap list firefox chromium
Name Version Rev Tracking Publisher Notes
chromium 109.0.5414.119 2295 latest/stable canonical✓ -
firefox 109.0.1-1 2311 latest/stable mozilla✓-
$ dpkg -l snapd|grep ^ii
ii snapd 2.58+22.10 amd64Daemon and tooling that enable
snap packages
$ dpkg -l mesa\* | grep ^ii
ii mesa-utils8.5.0-1 amd64Miscellaneous
Mesa utilities -- symlinks
ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous
Mesa utilities -- native applications
ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API
video acceleration drivers
ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video
acceleration drivers
ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan
graphics drivers
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.10
Release:22.10
Codename: kinetic
$ uname -a
Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4
12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: snap (not installed)
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Feb 1 22:55:48 2023
InstallationDate: Installed on 2020-08-02 (913 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: snap
UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago)
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900
1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480
640x480 640x480 640x480
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p2 ext4 916G 222G 648G 26% /
tmpfs tmpfs 16G 0 16G 0% /dev/shm
/dev/nvme0n1p2 ext4 916G 222G 648G 26% /
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2020-08-02 (914 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUS System Product Name
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic
root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
(772095164c7d5d4e73160f858efed3b5e87eca83-refs/branch-heads/5414@{#1458})
[Desktop-packages] [Bug 2054887] Re: Grahpical bugs caused by unable to access libdrm
> I still have the issue after switching to the beta version 123.0.6312.22 Hum... Do you still get the error about the missing file in stderr? Can you confirm snap run --shell chromium ls -l /usr/share/libdrm lists amdgpu.ids now? I also built the snap with Libdrm provided by Chromium's source itself, so I'm curious if that would resolve the issue for you: snap refresh --channel beta/internal-libdrm chromium > Here is the output All is correct there indeed. -- 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/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
** Description changed:
- Possible, proposed solutions
-
-
- Option 1: Please install from these channels and report back with
- success or failure.
-
- snap refresh --channel candidate/core22 firefox
-
- Option 2:
-
- chromium --ozone-platform=wayland
- MOZ_ENABLE_WAYLAND=1 firefox
-
- If nothing works, it is possible around the issue by disabling hardware
- acceleration.
-
- Original bug report
- ---
-
Snap packages which use hardware accelerated graphics are broken after
the last routine system upgrade via apt. My system is using AMD Radeon
RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers.
Two snap packages which are now unusable are Mozilla Firefox and
Chromium browsers. Both display animated speckled color garbage inside
their windows, overlayed with the correct image. Disabling hardware
acceleration in the settings for the snap version of Firefox fixed it.
Also, Firefox version installed from the original Mozilla tarball into
/opt/ works just fine with the acceleration enabled on the same system,
as well as glmark2 benchmark. Looks like the issue is only affecting
snap packages.
$ snap list firefox chromium
Name Version Rev Tracking Publisher Notes
chromium 109.0.5414.119 2295 latest/stable canonical✓ -
firefox 109.0.1-1 2311 latest/stable mozilla✓-
$ dpkg -l snapd|grep ^ii
ii snapd 2.58+22.10 amd64Daemon and tooling that enable
snap packages
$ dpkg -l mesa\* | grep ^ii
ii mesa-utils8.5.0-1 amd64Miscellaneous
Mesa utilities -- symlinks
ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous
Mesa utilities -- native applications
ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API
video acceleration drivers
ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video
acceleration drivers
ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan
graphics drivers
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.10
Release:22.10
Codename: kinetic
$ uname -a
Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4
12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: snap (not installed)
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Feb 1 22:55:48 2023
InstallationDate: Installed on 2020-08-02 (913 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: snap
UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago)
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900
1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480
640x480 640x480 640x480
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p2 ext4 916G 222G 648G 26% /
tmpfs tmpfs 16G 0 16G 0% /dev/shm
/dev/nvme0n1p2 ext4 916G 222G 648G 26% /
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2020-08-02 (914 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUS System Product Name
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic
root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
(772095164c7d5d4e73160f858efed3b5e87eca83-refs/branch-heads/5414@{#1458})
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
It looks like this regressed in Chromium (probably when Chromium switched to core22) judging by LP:2054887. The fix for the lack of /usr/share/libdrm/amdgpu.ids is currently released on beta and will be soon in other channels too. ** Changed in: chromium-browser (Ubuntu) Status: Fix Released => Fix Committed -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in ubuntu-spotify-app: New Status in chromium-browser package in Ubuntu: Fix Committed Status in firefox package in Ubuntu: Fix Released Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash
[Desktop-packages] [Bug 2054887] Re: Grahpical bugs caused by unable to access libdrm
Maybe it was perception error, because today I can confirm /usr/share/libdrm/amdgpu.ids is present in the beta snap. Could you please confirm the bug (or at least the error message) goes away by switching to it? sudo snap refresh --beta chromium ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- 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/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 2054887] Re: Grahpical bugs caused by unable to access libdrm
Either the workaround[1] didn't work for Chromium or I managed to botch my copy of it[2], for /usr/share/libdrm is still empty in the Chromium beta snap. [1] https://git.launchpad.net/~mozilla-snaps/firefox-snap/+git/firefox-snap/commit/?id=00059b6a9aea8e4ce5a239bd9e649f60736dd947 [2] https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=beta#n303 -- 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/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: In Progress Bug description: The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 2054887] Re: Grahpical bugs caused by unable to access libdrm
And Firefox has a work around, which I'm copying to Chromium beta. Once the fix is confirmed, will be released to other chnnaels. ** Changed in: chromium-browser (Ubuntu) Status: New => In Progress ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High -- 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/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: In Progress Bug description: The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 2054887] Re: Grahpical bugs caused by unable to access libdrm
This might be a bug in Snapd: LP:2055273. -- 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/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: New Bug description: The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 2055040] Re: Software rendering under Wayland mode
Happy to hear that! Would you mind confirming if the log from 3 no longer has references to crashed GPU process? Because if it still does, then I know for future debugging that that could be a red herring. ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: Fix Released Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2055040] Re: Software rendering under Wayland mode
2. Thank you for the willingness to test that! Unfortunately, the snap store makes snap branches expire after 30 days of their publication (LP:2019554). So if you try installing that snap, you'll end with the normal, stable snap. I just edited the comment there. 3. It has repeated instances of ---> [495611:495611:0226/163727.476117:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_code=133 [495611:495611:0226/163727.476173:WARNING:gpu_process_host.cc(1424)] The GPU process has crashed 1 time(s) [495913:495913:0226/163727.536126:WARNING:angle_platform_impl.cc(49)] renderergl_utils.cpp:2087 (GenerateCaps): Disabling GL_EXT_clip_cull_distance because only 8 clip distances, 0 cull distances and 0 combined clip/cull distances are supported by the driver. <--- You have some extensions there, so can you please make sure this problem is also present in a clean browser? An easy way to do this is to rename $HOME/snap/chromium and then once done testing you can rename it back. -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2055040] Re: Software rendering under Wayland mode
Correction: Command in 3 should be 'chromium --enable-logging=stderr --v=1 >chr.log 2>&1'. -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2055040] Re: Software rendering under Wayland mode
Thanks for clarifying. > If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script) 1. Just to confirm, this means that if you just launch the Chromium snap normally, the described behavior happens? Because, as you pointed out, --ozone-platform-hint=auto is a default flag in the launcher, so passing it via command line shouldn't affect the observed behavior. 2. Is the issue something new or was it this way ever since you started using the edge Chromium snap? 3. Can you attach the log generated from running 'chromium --enable- logging=stderr --v=1 2&>1 >chr.log'? ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New ** Tags added: kivu ** Description changed: - Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the - --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as + Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) + with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2055040] Re: Software rendering under Wayland mode
** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: Incomplete Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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
Re: [Desktop-packages] [Bug 2055040] [NEW] Software rendering under Wayland mode
What is 'snap info chromium|grep tracking'? > When omitting the parameter or setting it to "X11", HW rendering gets > correctly detected and activated. How did you determine that, was it in about:gpu? -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2054887] Re: Grahpical bugs caused by unable to access libdrm
Looks like GPU indeed, can you confirm with --disable-gpu? What is 'snap list|grep ^gnome' and 'snap connections chromium'? -- 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/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: New Bug description: The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 2054941] Re: Chromium does not print out, although printer is visible
** Also affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2054941 Title: Chromium does not print out, although printer is visible Status in chromium-browser package in Ubuntu: New Status in cups package in Ubuntu: New Bug description: Firefox from snap prints OK, but not Chromium. Interesting thing is that printer is visible, but printout is never coming out from the printer, if it is printed from Chromium. I have this problem for longer time, maybe half a year or more. Here are some outputs which could be useful: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy $ uname -v #107-Ubuntu SMP Wed Feb 7 13:26:48 UTC 2024 $ cups.lpstat -p printer HP_LaserJet_Professional_M1132_MFP is idle. enabled since Sun Feb 25 21:20:34 2024 Could not create job on the system's CUPS daemon - No such file or directory $ lpstat -v device for HP_LaserJet_Professional_M1132_MFP: hp:/usb/HP_LaserJet_Professional_M1132_MFP?serial=0XXX $ cups.lpstat -p printer HP_LaserJet_Professional_M1132_MFP is idle. enabled since Sun Feb 25 21:23:45 2024 Could not create job on the system's CUPS daemon - No such file or directory $ snap list | grep cups cups 2.4.7-3 1024 latest/stable openprinting** - $ snap connections cups InterfacePlug Slot Notes avahi-controlcups:avahi-control:avahi-control - cups chromium:cups cups:cups - cups-control - cups:cups-control - cups-control cups:cups-host:cups-control - home cups:home :home - network cups:network :network - network-bind cups:network-bind :network-bind - network-manager-observe cups:network-manager-observe :network-manager-observe - raw-usb cups:raw-usb :raw-usb - system-files cups:etc-cups :system-files - $ ps aux | grep cups-proxyd root7618 0.0 0.1 241736 3300 ?Sl 19:59 0:01 cups-proxyd /var/snap/cups/common/run/cups.sock /var/run/cups/cups.sock -l --logdir /var/snap/cups/1024/var/log This is interesting part of log from /var/log/cups/error_log: E [25/Feb/2024:19:52:33 +0100] [Client 168] Returning IPP client-error-not-possible for CUPS-Create-Local-Printer (ipp://localhost/) from localhost. W [25/Feb/2024:20:55:05 +0100] Notifier for subscription 502 (dbus://) went away, retrying! W [25/Feb/2024:20:55:05 +0100] Notifier for subscription 503 (dbus://) went away, retrying! W [25/Feb/2024:20:55:05 +0100] Notifier for subscription 505 (dbus://) went away, retrying! W [25/Feb/2024:20:55:05 +0100] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054941/+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 2054627] Re: Chromium fails to launch/startup up
Thanks for the report, glad to know it's not an issue any more. If it comes back, feel free to open the bug again. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/2054627 Title: Chromium fails to launch/startup up Status in chromium-browser package in Ubuntu: Incomplete Bug description: Chromium fails to start up from the KDE interface. I click the icon and nothing happen. When I launch Chromium from the terminal it launches but I get the following output in the terminal: (chrome:55656): Gtk-WARNING **: 20:39:23.626: Theme parsing error: gtk.css:1:21: Failed to import: Error opening file /home/user/snap/chromium/2757/.config/gtk-3.0/colors.css: No such file or directory Gtk-Message: 20:39:23.666: Failed to load module "colorreload-gtk-module" Gtk-Message: 20:39:23.666: Failed to load module "window-decorations-gtk-module" [55656:55656:0221/203923.708230:ERROR:policy_logger.cc(156)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build. (chrome:55656): IBUS-WARNING **: 20:39:24.041: Failed to mkdir /home/user/snap/chromium/2757/.config/ibus/bus: Not a directory ProblemType: Bug DistroRelease: Ubuntu 24.04 Uname: Linux 6.7.5-060705-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 21 20:40:07 2024 InstallationDate: Installed on 2024-02-17 (5 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240213) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Snap: chromium 121.0.6167.184 (stable) SnapChanges: ID Status Spawn Ready Summary 4Done2024-02-21T19:35:25-06:00 2024-02-21T19:35:59-06:00 Install "chromium" snap SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054627/+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 2053229] Re: Gnome Calendar stuck with old Gmail account appointments
** Description changed: For about one month my Google Calendar won't synchronize any more with Google, despite I having my account set up. As such it won't alert me of new events and will keep me alerting of deleted recurring events. + + "Synchronize calendars" does nothing. + + The log with --debug says: + + ---> + 11:47:04.656226 GcalManager: [1;33mWARNING[0m: source_credentials_required_cb: Failed to authenticate 'nathan.teodo...@canonical.com': Failed to obtain an access token for “nathan.teodo...@canonical.com”: No credentials found in the keyring + <--- + + But I didn't delete any entry in the keyring since, and in the keyring I + do see "GOA Google credentials for identity account_*". ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-calendar 45.1-1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 11:37:53 2024 InstallationDate: Installed on 2022-05-16 (640 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to noble on 2023-01-17 (394 days ago) ** Description changed: For about one month my Google Calendar won't synchronize any more with Google, despite I having my account set up. As such it won't alert me of new events and will keep me alerting of deleted recurring events. "Synchronize calendars" does nothing. The log with --debug says: ---> - 11:47:04.656226 GcalManager: [1;33mWARNING[0m: source_credentials_required_cb: Failed to authenticate 'nathan.teodo...@canonical.com': Failed to obtain an access token for “nathan.teodo...@canonical.com”: No credentials found in the keyring + 11:47:04.656226 GcalManager: [1;33mWARNING[0m: source_credentials_required_cb: Failed to authenticate 'nathan.teodosio _at_ canonical.com': Failed to obtain an access token for “nathan.teodosio _ at_ canonical.com”: No credentials found in the keyring <--- But I didn't delete any entry in the keyring since, and in the keyring I do see "GOA Google credentials for identity account_*". ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-calendar 45.1-1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 11:37:53 2024 InstallationDate: Installed on 2022-05-16 (640 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to noble on 2023-01-17 (394 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2053229 Title: Gnome Calendar stuck with old Gmail account appointments Status in gnome-calendar package in Ubuntu: New Bug description: For about one month my Google Calendar won't synchronize any more with Google, despite I having my account set up. As such it won't alert me of new events and will keep me alerting of deleted recurring events. "Synchronize calendars" does nothing. The log with --debug says: ---> 11:47:04.656226 GcalManager: [1;33mWARNING[0m: source_credentials_required_cb: Failed to authenticate 'nathan.teodosio _at_ canonical.com': Failed to obtain an access token for “nathan.teodosio _ at_ canonical.com”: No credentials found in the keyring <--- But I didn't delete any entry in the keyring since, and in the keyring I do see "GOA Google credentials for identity account_*". ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-calendar 45.1-1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 11:37:53 2024 InstallationDate: Installed on 2022-05-16 (640 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to noble on 2023-01-17 (394 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2053229/+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 2053229] [NEW] Gnome Calendar stuck with old Gmail account appointments
Public bug reported: For about one month my Google Calendar won't synchronize any more with Google, despite I having my account set up. As such it won't alert me of new events and will keep me alerting of deleted recurring events. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-calendar 45.1-1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 11:37:53 2024 InstallationDate: Installed on 2022-05-16 (640 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to noble on 2023-01-17 (394 days ago) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2053229 Title: Gnome Calendar stuck with old Gmail account appointments Status in gnome-calendar package in Ubuntu: New Bug description: For about one month my Google Calendar won't synchronize any more with Google, despite I having my account set up. As such it won't alert me of new events and will keep me alerting of deleted recurring events. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-calendar 45.1-1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 11:37:53 2024 InstallationDate: Installed on 2022-05-16 (640 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to noble on 2023-01-17 (394 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2053229/+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 2049625] Re: CVE-2024-0519: Out of bounds memory access in V8
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released -- 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/2049625 Title: CVE-2024-0519: Out of bounds memory access in V8 Status in chromium-browser package in Ubuntu: Fix Released Bug description: https://thehackernews.com/2024/01/zero-day-alert-update-chrome-now-to- fix.html Stable was fixed in 120.0.6099.224 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049625/+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 2052624] Re: Stop using --video-capture-use-gpu-memory-buffer flag in beta/edge builds
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released ** Tags added: hwacc ** Tags removed: hwacc ** Tags added: kivu -- 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/2052624 Title: Stop using --video-capture-use-gpu-memory-buffer flag in beta/edge builds Status in chromium-browser package in Ubuntu: Fix Released Bug description: Looking at https://discourse.ubuntu.com/t/an-overview-of-hardware- acceleration-in-chromium/36672, a couple of flags are added for beta and edge channel builds of Chromium to enable VAAPI. You may want to remove the flag --video-capture-use-gpu-memory-buffer from the builds, as it completely breaks webcam input: ERROR:video_capture_impl.cc(501)] Failed to open GpuMemoryBuffer handle It can be worked around by creating ~/.chromium-browser.init and adding CHROMIUM_FLAGS="--disable-video-capture-use-gpu-memory-buffer" to it, but that is not exactly user friendly (and rather redundant). Upstream the Chromium developers say that the --video-capture-use-gpu- memory-buffer flag is broken and that packagers should no longer be using it. https://issues.chromium.org/issues/40279468 >> Do the packagers need to be advised to remove this, or should the flags work as intended? > Yes. If you could inform them, please do so. On Chrome M116 that flag got broken, unfortunately. The flag had absolutely no effect before that, actually. In the future it will be enabled automatically when supported. So it's a good idea to remove that flag from the config for all versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2052624/+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
Re: [Desktop-packages] [Bug 2052624] Re: Stop using --video-capture-use-gpu-memory-buffer flag in beta/edge builds
Sure. And in case you are interested, you can always test "after-build time" changes such as this using snap try[1]. Chromium's launcher script would be in bin/chromium.launcher. [1] https://snapcraft.io/docs/snap-try Am 07/02/2024 um 17:53 schrieb Kevin Keijzer: > Sure, no problem. > > Could you by any chance do a new build for the beta channel with this > fix included? Then I can test if the webcam still works in the default > configuration, without the ~/.chromium-browser.init file. > -- 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/2052624 Title: Stop using --video-capture-use-gpu-memory-buffer flag in beta/edge builds Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Looking at https://discourse.ubuntu.com/t/an-overview-of-hardware- acceleration-in-chromium/36672, a couple of flags are added for beta and edge channel builds of Chromium to enable VAAPI. You may want to remove the flag --video-capture-use-gpu-memory-buffer from the builds, as it completely breaks webcam input: ERROR:video_capture_impl.cc(501)] Failed to open GpuMemoryBuffer handle It can be worked around by creating ~/.chromium-browser.init and adding CHROMIUM_FLAGS="--disable-video-capture-use-gpu-memory-buffer" to it, but that is not exactly user friendly (and rather redundant). Upstream the Chromium developers say that the --video-capture-use-gpu- memory-buffer flag is broken and that packagers should no longer be using it. https://issues.chromium.org/issues/40279468 >> Do the packagers need to be advised to remove this, or should the flags work as intended? > Yes. If you could inform them, please do so. On Chrome M116 that flag got broken, unfortunately. The flag had absolutely no effect before that, actually. In the future it will be enabled automatically when supported. So it's a good idea to remove that flag from the config for all versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2052624/+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 2052624] Re: Stop using --video-capture-use-gpu-memory-buffer flag in beta/edge builds
Thanks for bringing that to our attention. ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Committed -- 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/2052624 Title: Stop using --video-capture-use-gpu-memory-buffer flag in beta/edge builds Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Looking at https://discourse.ubuntu.com/t/an-overview-of-hardware- acceleration-in-chromium/36672, a couple of flags are added for beta and edge channel builds of Chromium to enable VAAPI. You may want to remove the flag --video-capture-use-gpu-memory-buffer from the builds, as it completely breaks webcam input: ERROR:video_capture_impl.cc(501)] Failed to open GpuMemoryBuffer handle It can be worked around by creating ~/.chromium-browser.init and adding CHROMIUM_FLAGS="--disable-video-capture-use-gpu-memory-buffer" to it, but that is not exactly user friendly (and rather redundant). Upstream the Chromium developers say that the --video-capture-use-gpu- memory-buffer flag is broken and that packagers should no longer be using it. https://issues.chromium.org/issues/40279468 >> Do the packagers need to be advised to remove this, or should the flags work as intended? > Yes. If you could inform them, please do so. On Chrome M116 that flag got broken, unfortunately. The flag had absolutely no effect before that, actually. In the future it will be enabled automatically when supported. So it's a good idea to remove that flag from the config for all versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2052624/+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 2052343] Re: Native Messaging is not working with Snap version of Chromium
** Changed in: chromium-browser (Ubuntu) Status: New => Triaged ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium -- 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/2052343 Title: Native Messaging is not working with Snap version of Chromium Status in chromium-browser package in Ubuntu: Triaged Bug description: Native Messaging is not working with Snap version of Chromium. Snap Firefox, Native Firefox and Native Chrome, work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2052343/+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 2049493] Re: rustc 1.71 version needed in jammy to build chromium updates for ARM
Assigning critical importance as 121 reached stable. ** Summary changed: - Newer rustc version needed in jammy to build chromium updates + rustc 1.71 version needed in jammy to build chromium updates for ARM ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Critical ** Changed in: chromium-browser (Ubuntu) Status: New => Triaged -- 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/2049493 Title: rustc 1.71 version needed in jammy to build chromium updates for ARM Status in chromium-browser package in Ubuntu: Triaged Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+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 2049493] Re: Newer rustc version needed in jammy to build chromium updates
Just for completeness: > I still do not understand why manually removing the -Z flags failed. Actually that had failed on the 32-bit ARMv7. ARMv8 had failed because of connection and I didn't care to trigger it again so I assumed it would fail for the same reason. Turns out that is not the case: ARMv7 just failed again[1] (after 88 h building...) with the same error with the RUSTC_BOOTSTRAP strategy, while ARMv8, as said in last comment, succeeds. So that is a separate issue. [1] https://launchpadlibrarian.net/710577930/buildlog_snap_ubuntu_jammy_armhf_chromium- rust_BUILDING.txt.gz -- 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/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+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 2049493] ARM builds
ARMv8 built alright with your proposed RUSTC_BOOTSTRAP strategy. I still do not understand why manually removing the -Z flags failed. Could it be that those undefined references were to unstable functions? But that is just out of curiosity. For the purposes of this report, please kindly continue with the Jammy backport of Rustc 1.7.1 as it solves the issue at hand. -- 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/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+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 2049493] Re: Newer rustc version needed in jammy to build chromium updates
The build with the manual removal of the -Z flags failed[1] with multiple undefined references such as ---> obj/third_party/rust/cxx/v1/lib/libcxx_lib.rlib(libcxx_lib.cxx.fbfe687f763ab24e-cgu.0.rcgu.o):cxx.fbfe687f763ab24e-cgu.0:function < as core::fmt::Debug>::fmt: error: undefined reference to '::fmt' obj/third_party/rust/cxx/v1/lib/libcxx_lib.rlib(libcxx_lib.cxx.fbfe687f763ab24e-cgu.0.rcgu.o):cxx.fbfe687f763ab24e-cgu.0:function < as core::fmt::Display>::fmt: error: undefined reference to '::fmt' obj/third_party/rust/cxx/v1/lib/libcxx_lib.rlib(libcxx_lib.cxx.fbfe687f763ab24e-cgu.0.rcgu.o):cxx.fbfe687f763ab24e-cgu.0:function < as core::fmt::LowerHex>::fmt: error: undefined reference to 'core::fmt::numfmt' <--- The builds with RUSTC_BOOTSTRAP=1 were silently reset after hours of progress (an old mysterious bug) and therefore we'll find out their actual result only on Monday. [1] https://launchpadlibrarian.net/710066046/buildlog_snap_ubuntu_jammy_armhf_chromium- rust_BUILDING.txt.gz -- 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/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+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
Re: [Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates
> Normally, it is not. Rust compilers, even in the stable channel, include > the complete logic of a nightly compiler. The logic is disabled by > default during the runtime when the compiler is in the stable channel. It is reassuring to learn that. > I hope my explanation makes sense. It does, and thanks again. -- 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/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+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
Re: [Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates
Thanks for that suggestion, looks like just what I needed. I looked it up and found this: > The build system sets RUSTC_BOOTSTRAP=1. This special variable means to break the stability guarantees of rust: Allow using #![feature(...)] with a compiler that's not nightly. This should never be used except when bootstrapping the compiler. Is it reasonable to dismiss that foreboding statament on the premise that we, as downstream, are not the ones introducing the usage of those unstable features and as such trust upstream to know what they are doing? I.e., is there an increased risk in using RUSTC_BOOTSTRAP in a non-nightly compiler (the proposed case for us downstream) in comparison to using the unstable options in a nightly compiler (what upstream does)? -- 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/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+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 2049236] Re: Chromium queuing my application requests
OK, feel free to reset the bug if the problem re-appears. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/2049236 Title: Chromium queuing my application requests Status in chromium-browser package in Ubuntu: Incomplete Bug description: I have web application with frontend and backend served behind nginx proxy with HTTP 2 enabled. My application is loading very slow, because some requests are put into queue for 1s. This only happening with chromium. I tested with Newest Edge, Firefox and Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049236/+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 2049493] Re: Newer rustc version needed in jammy to build chromium updates
The build failed[1] with
error: the option `Z` is only accepted on the nightly compiler
In the ideal world that nightly Rustc would be used, but given the
nature of deb packaging I suppose it is not doable.
Since I encountered the same error before and was able to overcome it by
manually removing all instances of that unstable option from the build
files, I'll try that strategy again. It is in general a boring process
because those options are generated during build and I couldn't track
down their originators; they are not to be found literally in the source
files, and so I removed them iteratively with a ad-hoc (and rather
embarrassing :p)
--->
find / -type f -name '*.ninja' -exec grep -Fq Zmacro-backtrace {} \; \
-exec sed -i \
's/-Zdep-info-omit-d-target//g;s/-Zmacro-backtrace//g;s/-Zremap-cwd-prefix=.//g'
\
{} +
<---
Additionally, near the end of the build (the one with the old Rustc to
be clear) things there were multiple undefined references[2], but I
reckon that was because the libprofiler_builtins.rlib was not available
and not because of the removal of the -Z options.
I'm submitting another build with the -Z options again removed and will
report back with the results once available.
[1]
https://launchpadlibrarian.net/709883798/buildlog_snap_ubuntu_jammy_arm64_chromium-rust_BUILDING.txt.gz
[2]
https://launchpadlibrarian.net/708915623/buildlog_snap_ubuntu_jammy_armhf_chromium-rust_BUILDING.txt.gz
--
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/2049493
Title:
Newer rustc version needed in jammy to build chromium updates
Status in chromium-browser package in Ubuntu:
New
Status in rustc package in Ubuntu:
New
Bug description:
The next chromium version is making rustc mandatory to build. Chromium
is a snap built from core22 so using the jammy packages, the build is
currently failing because it needs libprofiler_builtins.rlib which
isn't available.
Upstream provides toolchain builds that can be used but only for amd64 so
currently the snap is failing to build on arm
https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta
The version upstream is using is 1.75 but it's possible that a lower
version would be enough for now if libprofiler was enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+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 2049493] Re: Newer rustc version needed in jammy to build chromium updates
Thanks for the backport. I launched builds in https://launchpad.net/~nteodosio/+snap/chromium-rust and will report back with the results once available. ** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- 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/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+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
Re: [Desktop-packages] [Bug 2049236] [NEW] Chromium queuing my application requests
Thanks for the report, do you have a reproduction recipe? -- 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/2049236 Title: Chromium queuing my application requests Status in chromium-browser package in Ubuntu: New Bug description: I have web application with frontend and backend served behind nginx proxy with HTTP 2 enabled. My application is loading very slow, because some requests are put into queue for 1s. This only happening with chromium. I tested with Newest Edge, Firefox and Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049236/+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
