[Desktop-packages] [Bug 1998409] Re: [snap] chromium fails to start: unsupported version 0 of Verneed record
** Changed in: chromium-browser (Ubuntu) Status: Incomplete => 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/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: New Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record dirname: error while loading shared libraries:
[Desktop-packages] [Bug 1998641] [NEW] Sync xserver-xorg-video-vmware 1:13.3.0-3.1 from Debian unstable
Public bug reported: The delta between 1:13.3.0-3 and 1:13.3.0-3ubuntu1 was introduced in LP: #1991117 to fix a failure to build from source with GCC 12, as noted in its change log: * d/p/fix-missing-array-notation.patch: - cherry pick an upstream change to fix the build with the new gcc (LP: #1991117). This cherry-pick has been incorporated in Debian (bug 1021182[1]), and since that was the only delta, we can sync it. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021182 ** Affects: xserver-xorg-video-vmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/1998641 Title: Sync xserver-xorg-video-vmware 1:13.3.0-3.1 from Debian unstable Status in xserver-xorg-video-vmware package in Ubuntu: New Bug description: The delta between 1:13.3.0-3 and 1:13.3.0-3ubuntu1 was introduced in LP: #1991117 to fix a failure to build from source with GCC 12, as noted in its change log: * d/p/fix-missing-array-notation.patch: - cherry pick an upstream change to fix the build with the new gcc (LP: #1991117). This cherry-pick has been incorporated in Debian (bug 1021182[1]), and since that was the only delta, we can sync it. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021182 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1998641/+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 1989455] Re: [snap] No keyring for Chromium in Seahorse
*** This bug is a duplicate of bug 1997168 *** https://bugs.launchpad.net/bugs/1997168 ** This bug has been marked a duplicate of bug 1997168 [snap] Passwords are saved but not loaded with gnome keyring -- 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/1989455 Title: [snap] No keyring for Chromium in Seahorse Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The password storage test[1] says > Open seahorse (the default system keyring application), and under the Connexion keyring verify that there's an entry called "Chromium Safe Storage". I reproduce it in the .deb package, but fail to be reproduce it in the snap, even though password storage still works. [1]: https://wiki.ubuntu.com/Process/Merges/TestPlans/chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989455/+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 1998591] [NEW] Misbehavior in login keys
Public bug reported: These are the steps that I used to reproduce the issue: Open Seahorse and click the entry below the passwords tab (in my system it's called "Login"). Now, snap install --stable chromium snap connect chromium:password-manager-service snap run chromium Nothing new showed up in Seahorse, but it should have, since Chromium stored a password there via the desktop portal. Now close Seahorse and launch it again, and you will see one of two things: 1. A new entry (corresponding to Chromium) shows up; or 2. The password tab is entirely gone. In case 2, the ways I found to bring it back was to either log out or gnome-keyring-daemon -r. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: seahorse 42.0-2 ProcVersionSignature: Ubuntu 5.19.0-18.18-generic 5.19.7 Uname: Linux 5.19.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 08:14:07 2022 InstallationDate: Installed on 2022-05-16 (199 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-11-21T16:23:39.969270 ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1998591 Title: Misbehavior in login keys Status in seahorse package in Ubuntu: New Bug description: These are the steps that I used to reproduce the issue: Open Seahorse and click the entry below the passwords tab (in my system it's called "Login"). Now, snap install --stable chromium snap connect chromium:password-manager-service snap run chromium Nothing new showed up in Seahorse, but it should have, since Chromium stored a password there via the desktop portal. Now close Seahorse and launch it again, and you will see one of two things: 1. A new entry (corresponding to Chromium) shows up; or 2. The password tab is entirely gone. In case 2, the ways I found to bring it back was to either log out or gnome-keyring-daemon -r. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: seahorse 42.0-2 ProcVersionSignature: Ubuntu 5.19.0-18.18-generic 5.19.7 Uname: Linux 5.19.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 2 08:14:07 2022 InstallationDate: Installed on 2022-05-16 (199 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-11-21T16:23:39.969270 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1998591/+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 1989455] Re: [snap] No keyring for Chromium in Seahorse
** 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/1989455 Title: [snap] No keyring for Chromium in Seahorse Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The password storage test[1] says > Open seahorse (the default system keyring application), and under the Connexion keyring verify that there's an entry called "Chromium Safe Storage". I reproduce it in the .deb package, but fail to be reproduce it in the snap, even though password storage still works. [1]: https://wiki.ubuntu.com/Process/Merges/TestPlans/chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989455/+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 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
** 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/1997168
Title:
[snap] Passwords are saved but not loaded with gnome keyring
Status in chromium-browser package in Ubuntu:
Fix Committed
Bug description:
Steps to reproduce:
* System: Fresh (minimal, desktop) installation of Ubuntu 22.04 LTS in
VirtualBox to rule out any side-effects from preexisting configurations
* Install latest updates: `sudo apt update && sudo apt upgrade -y && sudo apt
dist-upgrade -y && sudo snap refresh`
* Install chromium from snap (`sudo snap install chromium`)
* Connect chromium to password manager service (`sudo snap connect
chromium:password-manager-service`) -> now chromium should be able to use gnome
keyring to store its master password
* Launch chromium, navigate to "chrome://settings/passwords"
* Add a new password ("Saved Passwords" -> "Add")
* Password shows up under "Saved Passwords" as expected.
* Close chromium and open it again, navigate to "chrome://settings/passwords"
* Expected: Password should show up. Instead: The list is empty.
* Add another password: List stays empty.
What I found out so far:
* Despite of the list showing up as empty in chromium, both passwords have
been stored in "~/snap/chromium/common/chromium/Default/Login Data" (to
confirm, grep for the username of the saved login, as the password itself will
be encrypted)
* It seems that the snap version of chromium does not create the entries
"Chrome Safe Storage" and "Chrome Safe Storage Control" in the gnome keyring,
which seems to be necessary at the moment (see http://crbug.com/660005). If a
non-snap version of chromium (e.g. from
https://launchpad.net/~savoury1/+archive/ubuntu/chromium) is installed first,
which is used to bootstrap the user's chromium config folder and which creates
the aforementioned entries in the gnome keyring, things are working fine, even
after transitioning to the snap version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997168/+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 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
I released the (possible) fix in stable/password branch. You can install
it with
snap install --channel stable/password chromium
Please make sure to connect the interface as in the bug description,
snap connect chromium:password-manager-service
It might also be a good idea to delete the Chromium entries from
Seahorse before 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/1997168
Title:
[snap] Passwords are saved but not loaded with gnome keyring
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
Steps to reproduce:
* System: Fresh (minimal, desktop) installation of Ubuntu 22.04 LTS in
VirtualBox to rule out any side-effects from preexisting configurations
* Install latest updates: `sudo apt update && sudo apt upgrade -y && sudo apt
dist-upgrade -y && sudo snap refresh`
* Install chromium from snap (`sudo snap install chromium`)
* Connect chromium to password manager service (`sudo snap connect
chromium:password-manager-service`) -> now chromium should be able to use gnome
keyring to store its master password
* Launch chromium, navigate to "chrome://settings/passwords"
* Add a new password ("Saved Passwords" -> "Add")
* Password shows up under "Saved Passwords" as expected.
* Close chromium and open it again, navigate to "chrome://settings/passwords"
* Expected: Password should show up. Instead: The list is empty.
* Add another password: List stays empty.
What I found out so far:
* Despite of the list showing up as empty in chromium, both passwords have
been stored in "~/snap/chromium/common/chromium/Default/Login Data" (to
confirm, grep for the username of the saved login, as the password itself will
be encrypted)
* It seems that the snap version of chromium does not create the entries
"Chrome Safe Storage" and "Chrome Safe Storage Control" in the gnome keyring,
which seems to be necessary at the moment (see http://crbug.com/660005). If a
non-snap version of chromium (e.g. from
https://launchpad.net/~savoury1/+archive/ubuntu/chromium) is installed first,
which is used to bootstrap the user's chromium config folder and which creates
the aforementioned entries in the gnome keyring, things are working fine, even
after transitioning to the snap version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997168/+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 1998497] [NEW] "Always on top" window prevents new windows from taking focus
Public bug reported: 1. Launch a terminal 2. Launch something from it, say 'xlogo &' 3. Put xlogo always on top by right clicking its title bar and selecting that option. 4. Back to the terminal, open a new window, preferentially something whose lack of input focus is evident, e.g. 'zenity --password'. Expected: New window has focus (you can type right away into zenity). Observed: Old window has focus. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libglib2.0-0 2.74.0-3 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:58:34 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998497 Title: "Always on top" window prevents new windows from taking focus Status in glib2.0 package in Ubuntu: New Bug description: 1. Launch a terminal 2. Launch something from it, say 'xlogo &' 3. Put xlogo always on top by right clicking its title bar and selecting that option. 4. Back to the terminal, open a new window, preferentially something whose lack of input focus is evident, e.g. 'zenity --password'. Expected: New window has focus (you can type right away into zenity). Observed: Old window has focus. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libglib2.0-0 2.74.0-3 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:58:34 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998497/+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 1996267] Re: [snap] Doesn't store encrypted passwords unless interface is connected
** 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/1996267 Title: [snap] Doesn't store encrypted passwords unless interface is connected Status in chromium-browser package in Ubuntu: Confirmed Bug description: In the Snap package of Chromium, Chromium is not protecting passwords with gnome-keyring (or KWallet). As a result, copying the Chromium profile directory from the snap directory gives access to all stored passwords. This is a HIGH security risk. Regular users who are used to storing their passwords in browsers are probably unaware of this. Note that Chromium is started with the command line option “--password-store=basic”. This hack should never have been released to the public. The Chromium documentation states: > --password-store=basic (to use the plain text store) https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996267/+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 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
** 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/1997168
Title:
[snap] Passwords are saved but not loaded with gnome keyring
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
Steps to reproduce:
* System: Fresh (minimal, desktop) installation of Ubuntu 22.04 LTS in
VirtualBox to rule out any side-effects from preexisting configurations
* Install latest updates: `sudo apt update && sudo apt upgrade -y && sudo apt
dist-upgrade -y && sudo snap refresh`
* Install chromium from snap (`sudo snap install chromium`)
* Connect chromium to password manager service (`sudo snap connect
chromium:password-manager-service`) -> now chromium should be able to use gnome
keyring to store its master password
* Launch chromium, navigate to "chrome://settings/passwords"
* Add a new password ("Saved Passwords" -> "Add")
* Password shows up under "Saved Passwords" as expected.
* Close chromium and open it again, navigate to "chrome://settings/passwords"
* Expected: Password should show up. Instead: The list is empty.
* Add another password: List stays empty.
What I found out so far:
* Despite of the list showing up as empty in chromium, both passwords have
been stored in "~/snap/chromium/common/chromium/Default/Login Data" (to
confirm, grep for the username of the saved login, as the password itself will
be encrypted)
* It seems that the snap version of chromium does not create the entries
"Chrome Safe Storage" and "Chrome Safe Storage Control" in the gnome keyring,
which seems to be necessary at the moment (see http://crbug.com/660005). If a
non-snap version of chromium (e.g. from
https://launchpad.net/~savoury1/+archive/ubuntu/chromium) is installed first,
which is used to bootstrap the user's chromium config folder and which creates
the aforementioned entries in the gnome keyring, things are working fine, even
after transitioning to the snap version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997168/+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 1998484] Re: Segmentation fault during window resize
** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1998484/+attachment/5633735/+files/journalctl.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1998484 Title: Segmentation fault during window resize Status in seahorse package in Ubuntu: New Bug description: I was just resizing Seahorse's window in a clean Kinetic VM and it segfaulted. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: seahorse 42.0-2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:30:16 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1998484/+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 1998484] [NEW] Segmentation fault during window resize
Public bug reported: I was just resizing Seahorse's window in a clean Kinetic VM and it segfaulted. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: seahorse 42.0-2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:30:16 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1998484 Title: Segmentation fault during window resize Status in seahorse package in Ubuntu: New Bug description: I was just resizing Seahorse's window in a clean Kinetic VM and it segfaulted. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: seahorse 42.0-2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:30:16 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1998484/+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 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10
** 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 xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in pipewire package in Ubuntu: Invalid Status in xdg-desktop-portal package in Ubuntu: Invalid Status in xdg-desktop-portal-gtk package in Ubuntu: Fix Released Bug description: Freshly installed Ubuntu 21.10, screen sharing does not work with any browser, tested the following options: - Firefox snap - Firefox deb - Chromium snap - Chromium flatpak Steps to reproduce: 1. Go to https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006 2. Select to share the whole desktop in the xdg-desktop-portal 3. Notice the orange screen share indicator in Gnome-Shell but actually nothing is shared in the browser. This should be handled high priority since this is a critical feature during the pandemic. Filed against ubuntu-meta since I don't know exactly which package to blame, whether it's pipewire, xdg-desktop portal or some problem directely with mutter / gnome-shell, please reassign accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+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 1998409] Re: chromium fails to start: unsupported version 0 of Verneed record
Hey Dmitriy, indeed reboots should not be necessary to launch updated snaps. So yes please run that apport-collect command and see if you can collect the lines from "journalctl -r" around the time of the crash you experienced some hours ago. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Tags added: snap ** Summary changed: - chromium fails to start: unsupported version 0 of Verneed record + [snap] chromium fails to start: unsupported version 0 of Verneed record -- 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/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record
[Desktop-packages] [Bug 1997907] Re: [Bug 1997596] Re: Chromium crashes without any apparent reason
** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New ** Summary changed: - [Bug 1997596] Re: Chromium crashes without any apparent reason + [snap] trap invalid opcode -- 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/1997907 Title: [snap] trap invalid opcode Status in chromium-browser package in Ubuntu: New Bug description: Chromium shuts down and when restarted, says it didn't shut down properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 24 16:34:50 2022 InstallationDate: Installed on 2022-03-19 (250 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 107.0.5304.110 (latest/stable) 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/1997907/+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 1997907] Re: [Bug 1997596] Re: Chromium crashes without any apparent reason
Weird. That is a documented option in man journalctl. But anyway, -n1000 is just to show 1000 lines, the idea being we don't want to upload the whole journal, a thousand lines should suffice. You can do journalctl -r | head -n 1000 > /tmp/journal.log instead. -- 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/1997907 Title: [Bug 1997596] Re: Chromium crashes without any apparent reason Status in chromium-browser package in Ubuntu: Incomplete Bug description: Chromium shuts down and when restarted, says it didn't shut down properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 24 16:34:50 2022 InstallationDate: Installed on 2022-03-19 (250 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 107.0.5304.110 (latest/stable) 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/1997907/+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 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly
I don't think Chromium is misbehaving here, at least not the snap, I tested with a deb I got from upstream and it's the same. At any rate, and correct me if mistaken, when terminal emulators are terminated, they send HUP to their jobs. So when Xorg or Wayland dies, it may kill the terminal before Chromium, and then the terminal HUPs Chromium. Now try "pkill -HUP chrom" and it will say the same thing, "didn't shut down correctly". I consider that more as a chance for the user to easily restore his pages — Firefox does the same and I guess many users appreciate 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/1952557 Title: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly Status in chromium-browser package in Ubuntu: Invalid Bug description: In Jammy when I have Chrome running and I log out of a Wayland session and then log back in and restart Chrome it says it wasn't shut down correctly. I'm pretty sure in earlier releases Chrome was given the opportunity to shut down cleanly when I logged out, but :shrug: I could be remembering this incorrectly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 28 11:17:25 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (834 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 40.5-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1952557/+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 1997979] Re: Merge grilo-plugins 0.3.15-1 from Debian unstable
** Patch added: "debian-to-ubuntu.diff" https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1997979/+attachment/5632803/+files/debian-to-ubuntu.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1997979 Title: Merge grilo-plugins 0.3.15-1 from Debian unstable Status in grilo-plugins package in Ubuntu: Confirmed Bug description: Built successfully locally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1997979/+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 1997979] [NEW] Merge grilo-plugins 0.3.15-1 from Debian unstable
Public bug reported: Built successfully locally. ** Affects: grilo-plugins (Ubuntu) Importance: Wishlist Assignee: Nathan Teodosio (nteodosio) Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1997979 Title: Merge grilo-plugins 0.3.15-1 from Debian unstable Status in grilo-plugins package in Ubuntu: Confirmed Bug description: Built successfully locally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1997979/+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 1997907] Re: [Bug 1997596] Re: Chromium crashes without any apparent reason
Sorry, Apport definitely did not report enough information for us. There are two independent things you can do. I recommend at least doing item 2, but doing both is better. 1. If you can, start chromium this way snap run chromium --enable-logging=stderr --v=1 &> /tmp/chromium.log and attach /tmp/chromium.log to this bug report once you get a crash. 2. Once you get a crash, please run journalctl -rn1000 > /tmp/journal.log and attach journal.log to this bug report. ** 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/1997907 Title: [Bug 1997596] Re: Chromium crashes without any apparent reason Status in chromium-browser package in Ubuntu: Incomplete Bug description: Chromium shuts down and when restarted, says it didn't shut down properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 24 16:34:50 2022 InstallationDate: Installed on 2022-03-19 (250 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 107.0.5304.110 (latest/stable) 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/1997907/+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 1997596] Re: Chromium crashes without any apparent reason
*** This bug is a duplicate of bug 1997907 *** https://bugs.launchpad.net/bugs/1997907 ** This bug has been marked a duplicate of bug 1997907 [Bug 1997596] Re: Chromium crashes without any apparent reason -- 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/1997596 Title: Chromium crashes without any apparent reason Status in chromium-browser package in Ubuntu: Incomplete Bug description: Version 107.0.5304.110 (Official Build) snap (64-bit) Ubuntu 20.04.5 LTS +/- 6 tabs open at any given time. Browser shuts down randomly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997596/+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 1989455] Re: [snap] No keyring for Chromium in Seahorse
** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium ** 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/1989455 Title: [snap] No keyring for Chromium in Seahorse Status in chromium-browser package in Ubuntu: In Progress Bug description: The password storage test[1] says > Open seahorse (the default system keyring application), and under the Connexion keyring verify that there's an entry called "Chromium Safe Storage". I reproduce it in the .deb package, but fail to be reproduce it in the snap, even though password storage still works. [1]: https://wiki.ubuntu.com/Process/Merges/TestPlans/chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989455/+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 1997596] Re: Chromium crashes without any apparent reason
Thanks for filing a report, but there is almost no information that will help us debugging it. Please use ubuntu-bug chromium apport-collect 1997596 Also, if the crashes occur often, then run Chromium this way: snap run chromium --enable-logging=stderr --v=1 &> /tmp/chromium.log and once the crash occurs, attach /tmp/chromium.log to this report. ** 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/1997596 Title: Chromium crashes without any apparent reason Status in chromium-browser package in Ubuntu: Incomplete Bug description: Version 107.0.5304.110 (Official Build) snap (64-bit) Ubuntu 20.04.5 LTS +/- 6 tabs open at any given time. Browser shuts down randomly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997596/+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 1997569] Re: Merge alsa-utils 1.2.7 from Debian unstable
** Patch added: "ubuntu-to-ubuntu.diff" https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1997569/+attachment/5632336/+files/ubuntu-to-ubuntu.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1997569 Title: Merge alsa-utils 1.2.7 from Debian unstable Status in alsa-utils package in Ubuntu: Confirmed Bug description: Please merge alsa-utils 1.2.7 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1997569/+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 1997569] Re: Merge alsa-utils 1.2.7 from Debian unstable
** Patch added: "debian-to-ubuntu.diff" https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1997569/+attachment/5632335/+files/debian-to-ubuntu.diff ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1997569 Title: Merge alsa-utils 1.2.7 from Debian unstable Status in alsa-utils package in Ubuntu: Confirmed Bug description: Please merge alsa-utils 1.2.7 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1997569/+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 1997569] [NEW] Merge alsa-utils 1.2.7 from Debian unstable
Public bug reported: Please merge alsa-utils 1.2.7 from Debian unstable. ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1997569 Title: Merge alsa-utils 1.2.7 from Debian unstable Status in alsa-utils package in Ubuntu: Confirmed Bug description: Please merge alsa-utils 1.2.7 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1997569/+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 1997530] Re: package chromium-browser 107.0.5304.87-0ubuntu11.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab d
For the record, the error is ==> Installing the chromium snap 2022-11-23T08:29:33+01:00 INFO Waiting for automatic snapd restart... error: cannot perform the following tasks: - Run configure hook of "chromium" snap if present (run hook "configure": cannot perform operation: mount --bind -o ro /mnt/usr/lib/snapd /tmp/snap.rootfs_3sGUSK/usr/lib/snapd: No such file or directory) dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-BFutJd/00-chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_arm64.deb (--unpack): »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück How did you get that kernel? It doesn't seem to be supported in Ubuntu. Can you try again with a supported kernel? ** 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/1997530 Title: package chromium-browser 107.0.5304.87-0ubuntu11.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in chromium-browser package in Ubuntu: Incomplete Bug description: it crashes on systemupgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 107.0.5304.87-0ubuntu11.18.04.1 Uname: Linux 4.9.140+ aarch64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: arm64 Date: Wed Nov 23 08:32:22 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstalledPlugins: Load-Avg-1min: 2.46 Load-Processes-Running-Percent: 0.4% Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcKernelCmdLine: root=/dev/mmcblk0p2 rootfstype=ext4 rw firmware_class.path=/lib/firmware/ access=m2 rootlabel_retries=1 swr_dir=/switchroot/ubuntu/ boot_m=1 boot_p=1 pmc_reboot2payload.enabled=1 pmc_reboot2payload.reboot_action=bootloader pmc_reboot2payload.default_payload=reboot_payload.bin pmc_reboot2payload.hekate_config_id=SWR-UBU fbcon=primary:1 consoleblank=0 nvdec_enabled=0 vpr_resize tegra_fbmem=0x40@0xf5a0 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 107.0.5304.87-0ubuntu11.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2022-11-23 (0 days ago) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997530/+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 1993581] Re: [snap] posix_spawn: No such file or directory
Fix released in amd64 beta. Marking as committed because it's still not released for other architectures nor for edge. Can you please confirm it works for you? ** 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/1993581 Title: [snap] posix_spawn: No such file or directory Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium from the edge channel fails to launch with % chromium [17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] posix_spawn: No such file or directory (2) % snap info chromium channels: latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB - latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB - latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB - latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB - installed: 108.0.5355.0 (2146) 153MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] Re: [snap] posix_spawn: No such file or directory
For reference, It's not entirely clear whether this is an upstream or downstream issue, but I'm leaning on the former. The source seems to indicate that chrome_crash_handler is meant only for an official (branded) Chromium build [3][4]; This is backed up by [5], which however has much obsolete stuff. Relevant upstream reports: [1] Issue 1377365: Chromium dev fails to launch: "posix_spawn: No such file or directory". [2] Issue 1176772: Land Crashpad for Chromium-Linux. As a matter of fact, if I manually copy chrome_crash_handler (from somewhere else) into the snap, Chromium launches normally. Unfortunately simply disabling posix_spawn for chrome_crash_handler doesn't work, as already detected here. There is some IPC[6] involved and the other end — the client process in the diagram, I reckon — aborts. [1]: https://bugs.chromium.org/p/chromium/issues/detail?id=1377365 [2]: https://bugs.chromium.org/p/chromium/issues/detail?id=1176772 [3]: https://source.chromium.org/chromium/chromium/src/+/main:BUILD.gn;drc=45940cd0c24186a35012d06d0aa0302e98830ab4;l=510 [4]: https://source.chromium.org/chromium/chromium/src/+/main:chrome/BUILD.gn;drc=45940cd0c24186a35012d06d0aa0302e98830ab4;l=1712 [5]: https://source.chromium.org/chromium/chromium/src/+/main:docs/website/site/developers/crash-reports/index.md [6]: https://chromium.googlesource.com/crashpad/crashpad/+/refs/heads/main/doc/overview_design.md -- 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/1993581 Title: [snap] posix_spawn: No such file or directory Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium from the edge channel fails to launch with % chromium [17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] posix_spawn: No such file or directory (2) % snap info chromium channels: latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB - latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB - latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB - latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB - installed: 108.0.5355.0 (2146) 153MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] Re: [snap] posix_spawn: No such file or directory
You were faster than me on #6, Alexander. :) > And just to confirm, Google builds from https://download- chromium.appspot.com (now version 109.0.5396.0) open without issue. Yes, it is a downstream issue related to the crash pad, which serves no purpose in our context. -- 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/1993581 Title: [snap] posix_spawn: No such file or directory Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium from the edge channel fails to launch with % chromium [17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] posix_spawn: No such file or directory (2) % snap info chromium channels: latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB - latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB - latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB - latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB - installed: 108.0.5355.0 (2146) 153MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] Re: [snap] posix_spawn: No such file or directory
I am aware that my tentative fix (submitted to beta) failed to solve the issue. But we are getting closer. -- 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/1993581 Title: [snap] posix_spawn: No such file or directory Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium from the edge channel fails to launch with % chromium [17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] posix_spawn: No such file or directory (2) % snap info chromium channels: latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB - latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB - latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB - latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB - installed: 108.0.5355.0 (2146) 153MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1814936] Re: chromium-browser fails to start, with message [...:ERROR:data_store_impl.cc(131)] Failed to open Data Reduction Proxy DB: 3
** 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/1814936 Title: chromium-browser fails to start, with message [...:ERROR:data_store_impl.cc(131)] Failed to open Data Reduction Proxy DB: 3 Status in chromium-browser package in Ubuntu: Incomplete Status in chromium-browser package in Debian: New Bug description: EDIT: upstream report at https://bugs.chromium.org/p/chromium/issues/detail?id=944295 ps shows chromium-browser processes are running, but no windows appear. I've been able to correlate the message "[...:ERROR:data_store_impl.cc(131)] Failed to open Data Reduction Proxy DB: 3" with this failure mode. Users are frustrated when it happens to them, and advice online is to delete your profile and reboot, which is suboptimal, because it removes all bookmarks, history, settings, etc. I have one user that gets this error almost daily, even after workstation swap, so I'm guessing there's a behavioral component as well. I have confirmed that killing all chromium-browser processes and rolling back just $HOME/.config/chromium/Default/Preferences to the state it was before a prior successful start is enough to fix the issue when it happens to me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 71.0.3578.98-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGs6EyAQEBAQgcAQOARid46g8lqFRDliIaUFS/74BxT4GAgQCzAIFAlQCpQNHAVl4AoKCgKVAwIDUAuokhAAAS/QAySx5aGAAKICAgICAg/ABWQTMyQVEKICAgICAg/wBKMkxNQVMwMDExOTQKARECAyXxSpAEAwEUEgUfBxMjCQcHgwEAAG0DDAAQADgxAjqAGHE4LUBYLEUAuokhAAAfVl4AoKCgKVAwIDUAuokhAAAeAR0AclHQHiBuKFUAuokhAAAf1QmAoCDgLRAIYCIAuokhCAgY9A== modes: 2560x1440 2560x1440 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Wed Feb 6 08:45:01 2019 Desktop-Session: 'mate' '/etc/xdg/xdg-mate:/etc/xdg' '/usr/share/mate:/usr/share/mate:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: Load-Avg-1min: 3.04 Load-Processes-Running-Percent: 0.1% MachineType: Shuttle Inc. DX30D ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=dc6e336f-c022-11e8-b65f-80ee73d362fb ro SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FDX30 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd02/15/2017:svnShuttleInc.:pnDX30D:pvrV1.0:rvnShuttleInc.:rnFDX30:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: D dmi.product.name: DX30D dmi.product.version: V1.0 dmi.sys.vendor: Shuttle Inc. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1814936/+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 1809105] Re: Broken setting custom flags in /usr/bin/chromium-browser script
*** This bug is a duplicate of bug 1514484 ***
https://bugs.launchpad.net/bugs/1514484
Please let me know if I misunderstood and this isn't a duplicate.
** This bug has been marked a duplicate of bug 1514484
Chromium start-up script doesn't accept argument values with spaces in
$CHROMIUM_FLAGS, cause is lack of quotes
--
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/1809105
Title:
Broken setting custom flags in /usr/bin/chromium-browser script
Status in chromium-browser package in Ubuntu:
New
Bug description:
To workaround LP#1808853 (https://bugs.launchpad.net/bugs/1808853) I
tried to make the following script (/etc/chromium-
browser/customizations/20-chromium-useragent-fix):
https://gitlab.com/mikhailnov/nastr/blob/master/chromium-useragent-
fix.sh
But it does not work due to probably an error in /usr/bin/chromium-
browser
If use an unmodified /usr/bin/chromium-browser, then my scripts leads
to openning multiple tabs, because --useagent=VALUE is passed as
multiple arguements, not one.
I've made a patch:
--- ./chromium-browser 2018-12-17 04:53:00.0 +0300
+++ /tmp/chromium-browser 2018-12-19 14:16:29.186960503 +0300
@@ -207,16 +207,16 @@
echo "$GDB $LIBDIR/$APPNAME -x $tmpfile"
$GDB "$LIBDIR/$APPNAME" -x $tmpfile
if [ $want_temp_profile -eq 1 ] ; then
-rm -rf $TEMP_PROFILE
+rm -rf ${TEMP_PROFILE:?}/*
fi
exit $?
else
if [ $want_temp_profile -eq 0 ] ; then
-exec $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@"
+exec "$LIBDIR/$APPNAME" "$CHROMIUM_FLAGS" "$@"
else
# we can't exec here as we need to clean-up the temporary profile
-$LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@"
-rm -rf $TEMP_PROFILE
+"$LIBDIR/$APPNAME" "$CHROMIUM_FLAGS" "$@"
+rm -rf ${TEMP_PROFILE:?}/*
fi
fi
After this multiple pages are not openned, but, if we run
$ bash -x /usr/bin/chromium-browser
we see:
+ exec /usr/lib/chromium-browser/chromium-browser '
--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so
--ppapi-flash-version=32.0.0.101 --user-agent=Mozilla/5.0 (X11; Linux x86_64)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36
--enable-pinch' https://yandex.ru/internet
the problem is in ' ', new user-agent is not applied
If to run manually
$ /usr/lib/chromium-browser/chromium-browser
--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so
--ppapi-flash-version=32.0.0.101 --user-agent=Mozilla/5.0 (X11; Linux x86_64)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36
--enable-pinch https://yandex.ru/internet
then setting a custom useragent does work.
What can be done?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1809105/+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 1794354] Re: [snap] emoji show as black and white if fonts-symbola is installed
Still an issue? Cannot reproduce in current stable 107.0.5304.87. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => 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/1794354 Title: [snap] emoji show as black and white if fonts-symbola is installed Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm using the Chromium Snap from the Beta channel. Test Case = 0. Be sure you don't have the Chromium deb running. 1. Visit https://launchpad.net/bugs/1779569 The rainbow emoji should show in color 2. sudo apt install fonts-symbola 3. Close Chromium. Wait a few moments to make sure it closes then open it and repeat step 1 4. The rainbow emoji shows in black and white Other Info == Firefox and GTK apps like gedit correctly show in color as long as fonts-noto-color-emoji is installed, regardless of whether fonts-symbola is also installed. I also was unable to duplicate this bug with the Firefox Snap [edge channel 63.0b9-1 (134)]. System Info === Ubuntu 18.10 fonts-noto-color-emoji 0~20180810-1 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ contact: https://forum.snapcraft.io/ 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 snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refresh-date: 8 days ago, at 13:41 EDT channels: stable:69.0.3497.100 (494) 141MB - candidate: 69.0.3497.100 (494) 141MB - beta: 70.0.3538.16 (487) 142MB - edge: 70.0.3538.9 (472) 142MB - installed: 70.0.3538.16 (487) 142MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1794354/+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 1764648] Re: Read pixels broken in Chrome/Chromium on 18.04 using the NVIDIA driver
** 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/1764648 Title: Read pixels broken in Chrome/Chromium on 18.04 using the NVIDIA driver Status in chromium-browser package in Ubuntu: Fix Released Bug description: 2 ways to reproduce: 1) Go to https://www.khronos.org/registry/webgl/sdk/tests/webgl-conformance-tests.html and run the all/conformance/reading tests. 2) Go to photoeditor.polarr.co. Select the Pro workspace. Skip the tutorial. Press F to open the filters panel (or click the 3 circle icon on the left). All of the filter previews will be garbled or black for any image that you edit. I've tried this on 2 computers, one with a 980, and one with a 1070. They both fail on Ubuntu 18.04 but work correctly on 16.04 and 17.10. Firefox works correctly. I attempted to use the Noveau driver, but I got a max resolution of 640p and WebGL didn't work at all so far as I could tell. I've tried running my Polarr photo editor (an Electron app) on 18.04, and it also doesn't work correctly any more. This is what I get in the terminal for chromium-browser when I run the WebGL conformance tests for reading pixels: amiller@amiller-All-Series:~$ chromium-browser [4775:4775:0417/30.985800:ERROR:gles2_cmd_decoder.cc(12024)] [.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : glReadPixels: format and type incompatible with the current read framebuffer [4775:4775:0417/30.986559:ERROR:gles2_cmd_decoder.cc(12024)] [.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : glReadPixels: format and type incompatible with the current read framebuffer [4775:4775:0417/30.987074:ERROR:gles2_cmd_decoder.cc(12024)] [.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : glReadPixels: format and type incompatible with the current read framebuffer [4775:4775:0417/30.987630:ERROR:gles2_cmd_decoder.cc(12024)] [.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : glReadPixels: format and type incompatible with the current read framebuffer ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 65.0.3325.181-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Tue Apr 17 00:06:03 2018 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2018-04-10 (6 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) InstalledPlugins: /usr/lib/mozilla/plugins: => libgnome-shell-browser-plugin.so (size: 18856 bytes, mtime: Sat Apr 7 06:58:00 2018) Load-Avg-1min: 0.29 Load-Processes-Running-Percent: 0.1% MachineType: ASUS All Series ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=a9752952-f843-46f2-9206-e16c858d6d33 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-17 (0 days ago) dmi.bios.date: 12/10/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1203 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1203:bd12/10/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1764648/+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 1793738] Re: /usr/lib/chromium-browser/chromium-browser:11:vmw_svga_winsys_query_init:begin_query_vgpu10:svga_begin_query:svga_end_query:st_BeginQuery
** 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/1793738 Title: /usr/lib/chromium-browser/chromium- browser:11:vmw_svga_winsys_query_init:begin_query_vgpu10:svga_begin_query:svga_end_query:st_BeginQuery Status in chromium-browser package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 69.0.3497.81-0ubuntu0.18.04.1, the problem page at https://errors.ubuntu.com/problem/5b4b816028653b60b026daed26b5a6c379728625 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1793738/+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 1993809] Re: Update gnome-shell to 42.5
I verified the SRU by installing the gnome-shell from proposed, 42.5-0ubuntu1. The test succeeded. I followed the test cases in https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell. For the test case 1, I couldn't notice any problem in any of the 4 sessions, with moving windows, tiling, application panel etc. For the test case 2, I enabled all the extensions without error. To the best of my knowledge of their functionality, they behaved fine. I also installed Hexchat and confirmed that the tray icon showed up, so the Appindicator extension is working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1993809 Title: Update gnome-shell to 42.5 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS The version currently in Ubuntu 22.04.1 LTS is 42.4 Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- I also cherry-picked a fix from kinetic: gsettings org.gnome.settings-daemon.peripherals.mouse no longer exists in Ubuntu 22.04 LTS so I updated the apport script to stop trying to report customizations for that gsettings schema. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993809/+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 1993562] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor
** 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/1993562 Title: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor Status in chromium-browser package in Ubuntu: Fix Released Bug description: When starting chromium's snap, those messages are logged: $ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F snap.chromium.chromium audit: type=1400 audit(1666201583.608:610): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:611): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_name" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:612): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:613): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_version" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Chromium behaves OK but generates log pollution. Additional info: $ snap list chromium snapd Name Version RevTracking Publisher Notes chromium 106.0.5249.119 2136 latest/stable canonical✓ - snapd 2.57.4 17336 latest/stable canonical✓ snapd $ uname -rm 5.15.0-52-generic x86_64 $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993562/+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 1993562] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor
Thanks for the report, Simon, I pushed a fix to Chromium in a feature branch[1]. As per my tests, it solves the issue. Could you please confirm it by downloading it and installing it with snap install --dangerous ./chromium*.snap [1]: https://launchpad.net/~nteodosio/+snap/chromium-browser-beta-deny- metrics/+build/1917882 ** 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/1993562 Title: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor Status in chromium-browser package in Ubuntu: Fix Committed Bug description: When starting chromium's snap, those messages are logged: $ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F snap.chromium.chromium audit: type=1400 audit(1666201583.608:610): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:611): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_name" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:612): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:613): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_version" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Chromium behaves OK but generates log pollution. Additional info: $ snap list chromium snapd Name Version RevTracking Publisher Notes chromium 106.0.5249.119 2136 latest/stable canonical✓ - snapd 2.57.4 17336 latest/stable canonical✓ snapd $ uname -rm 5.15.0-52-generic x86_64 $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993562/+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 1993562] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor
** 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/1993562 Title: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor Status in chromium-browser package in Ubuntu: In Progress Bug description: When starting chromium's snap, those messages are logged: $ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F snap.chromium.chromium audit: type=1400 audit(1666201583.608:610): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:611): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_name" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:612): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:613): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_version" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Chromium behaves OK but generates log pollution. Additional info: $ snap list chromium snapd Name Version RevTracking Publisher Notes chromium 106.0.5249.119 2136 latest/stable canonical✓ - snapd 2.57.4 17336 latest/stable canonical✓ snapd $ uname -rm 5.15.0-52-generic x86_64 $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993562/+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 1692319] Re: Cannot activate "Google Docs Offline" extension
Thanks for trying to reproduce this, that's much appreciated! And glad to hear it (apparently) solved itself. -- 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/1692319 Title: Cannot activate "Google Docs Offline" extension Status in chromium-browser package in Ubuntu: Incomplete Bug description: ~ $ lsb_release -rd Description: Linux Mint 18.1 Serena Release: 18.1 ~ $ apt-cache policy chromium-browser chromium-browser: Installed: 58.0.3029.110-0ubuntu0.16.04.1281 Candidate: 58.0.3029.110-0ubuntu0.16.04.1281 Version table: *** 58.0.3029.110-0ubuntu0.16.04.1281 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://archive.ubuntu.com/ubuntu xenial/universe i386 Packages = Have tried this under both 32 and 64bit installs, slightly different behaviour. My concern is with the 32bit build, so I will focus on that, with a footnote on 64bit. On a 32bit netbook (Acer AspireOne) I have LinuxMint 18.1 (Ubuntu 16.04-based) with the Chromium browser installed. I have installed the https://chrome.google.com/webstore/detail/google-docs- offline/ghbmnnjooekpmoecnnnilnnbdlolhkhi"Google Docs Offline" extension into the browser, and restarted the browser (multiple tries installing & uninstalling, to make sure there wasn't a failure in the install). Extension is at https://chrome.google.com/webstore/detail/google-docs- offline/ghbmnnjooekpmoecnnnilnnbdlolhkhi According to directions I should make sure offline sync is enabled in Google Drive (which it is), and then make sure they are enabled in the settings for Google Docs. Once that is enabled I should have an option in each document's preferences to save offline. Expected: I should be able to enable the offline function in Google Docs by moving the switch to active. After that I should be able to mark a document for offline synchronization. What Happened: The setting in Google Drive is checked as enabled. However, when I go to the settings screen for Google Docs, the 'slider' to enable the option is stuck in a half-way position (neither off nor on). Consequentially the offline sync option will not be available for the document. - I had tried this with the 64bit version on another system (same Mint 18.1 on a 64bit system). Same chromium version as above. It actually enables the option and lets me sync a document, and I can do an offline edit (disabling the network to test). However, it will only work for a couple exits/restarts of the browser, at which point it will disable itself. Strange behaviour in itself; perhaps related or not, just put here in case it's relevant. I have tried this on the official Google Chrome (58.0.3029.96-1) on the same 64bit system and it works no problem. Obviously I cannot do the comparable test on 32bit (no 32bit Linux can be found anywhere, Google wiped out every copy in existence). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1692319/+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 1692319] Re: Cannot activate "Google Docs Offline" extension
Is this still an issue for the current Chromium stable? ** 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/1692319 Title: Cannot activate "Google Docs Offline" extension Status in chromium-browser package in Ubuntu: Incomplete Bug description: ~ $ lsb_release -rd Description: Linux Mint 18.1 Serena Release: 18.1 ~ $ apt-cache policy chromium-browser chromium-browser: Installed: 58.0.3029.110-0ubuntu0.16.04.1281 Candidate: 58.0.3029.110-0ubuntu0.16.04.1281 Version table: *** 58.0.3029.110-0ubuntu0.16.04.1281 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://archive.ubuntu.com/ubuntu xenial/universe i386 Packages = Have tried this under both 32 and 64bit installs, slightly different behaviour. My concern is with the 32bit build, so I will focus on that, with a footnote on 64bit. On a 32bit netbook (Acer AspireOne) I have LinuxMint 18.1 (Ubuntu 16.04-based) with the Chromium browser installed. I have installed the https://chrome.google.com/webstore/detail/google-docs- offline/ghbmnnjooekpmoecnnnilnnbdlolhkhi"Google Docs Offline" extension into the browser, and restarted the browser (multiple tries installing & uninstalling, to make sure there wasn't a failure in the install). Extension is at https://chrome.google.com/webstore/detail/google-docs- offline/ghbmnnjooekpmoecnnnilnnbdlolhkhi According to directions I should make sure offline sync is enabled in Google Drive (which it is), and then make sure they are enabled in the settings for Google Docs. Once that is enabled I should have an option in each document's preferences to save offline. Expected: I should be able to enable the offline function in Google Docs by moving the switch to active. After that I should be able to mark a document for offline synchronization. What Happened: The setting in Google Drive is checked as enabled. However, when I go to the settings screen for Google Docs, the 'slider' to enable the option is stuck in a half-way position (neither off nor on). Consequentially the offline sync option will not be available for the document. - I had tried this with the 64bit version on another system (same Mint 18.1 on a 64bit system). Same chromium version as above. It actually enables the option and lets me sync a document, and I can do an offline edit (disabling the network to test). However, it will only work for a couple exits/restarts of the browser, at which point it will disable itself. Strange behaviour in itself; perhaps related or not, just put here in case it's relevant. I have tried this on the official Google Chrome (58.0.3029.96-1) on the same 64bit system and it works no problem. Obviously I cannot do the comparable test on 32bit (no 32bit Linux can be found anywhere, Google wiped out every copy in existence). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1692319/+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 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes
** 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/1514484 Title: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes Status in chromium-browser package in Ubuntu: Fix Released Bug description: You can't have arguments with spaces inside CHROMIUM_FLAGS, whatever comes after the first space is going to be interpreted as an URL by the actual chromium binary. Easy repro: 1. Set user's CHROMIUM_FLAGS with an argument containing spaces, eg: $ echo 'CHROMIUM_FLAGS=--user-agent="A B C"' > .chromium-browser.init 2. Run chromium: $ /usr/bin/chromium-browser 3. See 2 extra open tabs, one trying to open URL 'B', the other 'C'. The cause for this funny behavior is the lack of quotes around $CHROMIUM_FLAGS in the script installed in /usr/bin/chromium-browser -- it calls $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@" by the end of the script. I've tried working around it but couldn't, no amount of escaping and extra quotes seems to help if it's called like that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1514484/+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 1697639] Re: Chromium window under GNOME Shell can't be moved with touch input
Is this still an issue with the current Chromium stable? ** Tags added: touch ** 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/1697639 Title: Chromium window under GNOME Shell can't be moved with touch input Status in chromium-browser package in Ubuntu: Incomplete Bug description: Running Chromium on Artful under GNOME Shell. I can move the window around with the mouse as normal, but it cannot be moved with touch input. Note that pinch to zoom does work, and scrolling the window up and down also work. Just that I can't move the window around on the screen, maximize it, etc. chromium-browser: Installed: 58.0.3029.110-0ubuntu1.1354 Candidate: 58.0.3029.110-0ubuntu1.1354 Version table: *** 58.0.3029.110-0ubuntu1.1354 500 500 http://gb.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1697639/+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 1577367] Re: Repeated flickers in chromium (with skylake)
Is this still a problem on the currently supported Chromium (106.0)? ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => 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/1577367 Title: Repeated flickers in chromium (with skylake) Status in chromium-browser package in Ubuntu: Incomplete Bug description: This affects chromium and chrome. As you click around inside or between tabs, you get repeated strobing which is disconcerting and borderline unusable. Disabling GPU altogether breaks rendering in many cases (for example, buttons become badly "torn"). The "solution" is to add the flags described here, i.e.: --disable- gpu-driver-bug-workarounds --enable-native-gpu-memory-buffers https://productforums.google.com/forum/#!msg/chrome/CtKF2BiskT8/Am_xdbtdAgAJ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 49.0.2623.108-0ubuntu1.1233 [modified: usr/share/applications/chromium-browser.desktop] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-DP-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-3: edid-base64: AP///wBaYyw6AQEBAQIXAQOAPCJ4Lu7Vo1ZQnyYQUFS/74CzAKlAlQCQQIGAgUBxTwEBAjqAGHE4LUBYLEUAVVAhAAAe/wBUQUYxMzAyMDY3MDcK/QAyTA9TEgAKICAgICAg/ABWWDI3NzAgU0VSSUVTAaICAyLxT5AFBAMCBwYfFBMSERYVASMJfweDAQAAZQMMABAAAjqAGHE4LUBYLEUAVVAhAAAeAR2AGHEcFiBYLCUAVVAhAACeAR0AclHQHiBuKFUAVVAhAAAejArQiiDgLRAQPpYAVVAhAAAYAjqA0HI4LUAQLEWAVVAhAAAeTQ== dpms: On modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1680x1050 1400x1050 1280x1024 1280x1024 1440x900 1280x960 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected Date: Mon May 2 07:44:21 2016 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2016-04-29 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Load-Avg-1min: 0.49 Load-Processes-Running-Percent: 0.3% MachineType: Shuttle Inc. SH170 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=4ead2e88-6c4e-4c28-88da-96b9b0338338 ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.12 dmi.board.asset.tag: Default string dmi.board.name: FH170 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.12:bd08/26/2015:svnShuttleInc.:pnSH170:pvr1.0:rvnShuttleInc.:rnFH170:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: SH170 dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1577367/+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 1690254] Re: Ubuntu browser builds can't select text on NYTimes articles
Is this still an issue in Chromium stable? Can't reproduce it on Firefox either. ** 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/1690254 Title: Ubuntu browser builds can't select text on NYTimes articles Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Incomplete Status in firefox package in Ubuntu: New Bug description: Note: this bug *may* affect touch screen devices only. Just a hunch. Load an NYTimes article such as https://www.nytimes.com/2017/05/10/science/trappist-earth-size- planets-orbits-music.html and attempt to select some text, either via click-and-drag or double/triple click. Using the official Mozilla Firefox 53.0.2 build, this works as expected. Using the Ubuntu Zesty Firefox 53.0+build6 build however, the user can't select any text. Instead, click-and-drag scrolls some links to other articles in from the sides, while double click resizes the article text (equivalent touchpad and touchscreen interactions have the same effect). Android-style tap-and-hold does nothing. Caret Browsing also doesn't work, as the arrow keys are overridden. Only + still works as expected. There doesn't seem to be an invisible layer above the text, since the mouse pointer changes between an arrow, finger, and I-beam cursor, and since clicking on links works. This inconsistency violates the Law of Least Astonishment. Affected browsers: * Ubuntu Gnome 17.04 64-bit touchscreen: Ubuntu Firefox 53.0+build6 with clean profile, Ubuntu Modifications add-on only * Ubuntu Gnome 17.04 64-bit touchscreen: Ubuntu Firefox 53.0+build6 with clean profile and no add-ons * Ubuntu Gnome 17.04 64-bit touchscreen: Ubuntu Chromium 58.0.3029.96 Not affected: * Ubuntu Gnome 17.04 64-bit touchscreen: Official Mozilla Firefox 53.0.2 with clean profile * Ubuntu 16.04 LTS 32-bit: Ubuntu Firefox 53.0+build6 on Ubuntu 16.04 LTS * Windows XP 32-bit: Mozilla 52.0.2 Bugzilla reference: https://bugzilla.mozilla.org/show_bug.cgi?id=1363936 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: firefox 53.0.2+build1-0ubuntu0.17.04.2 Uname: Linux 4.11.0-041100-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 BuildID: 20170509205512 CurrentDesktop: GNOME Date: Fri May 12 07:47:00 2017 InstallationDate: Installed on 2016-12-02 (159 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1690254/+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 1682799] Re: mouse pointer disappears on tabs/navbar when screen scaled
Is this still an issue now that Chromium 106.0 is the currently supported version? ** 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/1682799 Title: mouse pointer disappears on tabs/navbar when screen scaled Status in chromium-browser package in Ubuntu: Incomplete Bug description: Hi, running chromium 57.0.2987.98-0ubuntu1.1348 on zesty on a 2016 XPS 13. When using xrandr --scale to make my HiDPI screen usable with my lower DPI screen, moving the mouse over the navbar makes the mouse pointer disappear. I've took a video to demonstrate this: https://www.youtube.com/watch?v=x_YmsFbtcOA Steps to reproduce: 0. Connect additional, external display 1. run: xrandr --output DP-1 --right-of eDP-1 --output eDP-1 --auto --scale 0.75x0.75 2. hover mouse over navbar I don't know if this is an issue in chromium or xorg. I filled https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1580123 last year for another issue with scaling. Looks like xorg is pretty much dead. Also happy for any workarounds, chromium is not really usable like this. Fwiw, I'm running xorg 1:7.7+16ubuntu3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1682799/+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 1673636] Re: Chromium-browser 56.0.2924.76 displays "Aw, snap!" for every page
Being 56.0.2924.76, this is most likely expired; Bump this otherwise. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => 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/1673636 Title: Chromium-browser 56.0.2924.76 displays "Aw, snap!" for every page Status in chromium-browser package in Ubuntu: Incomplete Bug description: I have a Raspberry Pi 3 running Ubuntu Mate 16.04.2 LTS armhf, and the latest chromium-browser release (56.0.2924.76-0ubuntu0.16.04.1268) displays only the "Aw, snap!" error instead of opening the page. Here's what it outputs: chromium-browser --type=renderer --enable-pinch --primordial-pipe-token=2B6454B8FDD8B6DF81A0410F38661838 --lang=en-US --extension-process --enable-offline-auto-reload --enable-offline-auto-reload-visible-only --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553 --disable-accelerated-video-decode --service-request-channel-token=2B6454B8FDD8B 6DF81A0410F38661838 --renderer-client-id=3 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed. Received signal 4 723e23f6 #0 0x76eccdd2 base::debug::StackTrace::StackTrace() #1 0x76ecd10c #2 0x723e2270 #3 0x723e23f6 abort [end of stack trace] chromium-browser --type=renderer --enable-pinch --primordial-pipe-token=62B2952180A16AFBE460B81D4FF09B03 --lang=en-US --extension-process --enable-offline-auto-reload --enable-offline-auto-reload-visible-only --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553 --disable-accelerated-video-decode --service-request-channel-token=62B2952180A16 AFBE460B81D4FF09B03 --renderer-client-id=4 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed. Received signal 4 723e23f6 #0 0x76eccdd2 base::debug::StackTrace::StackTrace() #1 0x76ecd10c #2 0x723e2270 #3 0x723e23f6 abort [end of stack trace] [4913:4913:0316/193331.442163:ERROR:sandbox_linux.cc(343)] InitializeSandbox() called with multiple threads in process gpu-process. chromium-browser --type=renderer --enable-pinch --primordial-pipe-token=976299708D6398A9E2529F8A2B6E1493 --lang=en-US --instant-process --enable-offline-auto-reload --enable-offline-auto-reload-visible-only --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553 --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-comp ositing --service-request-channel-token=976299708D6398A9E2529F8A2B6E1493 --renderer-client-id=9 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed. Received signal 4 723e23f6 #0 0x76eccdd2 base::debug::StackTrace::StackTrace() #1
[Desktop-packages] [Bug 1668730] Re: Tweak .desktop Actions for more consistency
Merged, initially on the dev branch, commit 1bfc178[1]. Is it now a matter of simply mailing ubuntu-translators? [1]: https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from- source/commit/?id=1bfc17860b7ffdf33e5d1061d6772364daa9726d ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => 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/1668730 Title: Tweak .desktop Actions for more consistency Status in chromium-browser package in Ubuntu: Fix Committed Bug description: See the similar bugs for Firefox (LP: #1668664) and webbrowser-app (LP: #1668699) which give some more justification. The webbrowser-app change was approved by Design and will be in the next major update. I am attaching a patch: - Drop the "Open a " prefix from the .desktop actions. - Renames the NewWindow action to new-window to not have a duplicate entry in GNOME Shell - Consistently use Title Case (Early in Unity, sentence case was preferred but that's obsolete now for .desktop Actions) - Retitle "Open a New Window in incognito mode" to "New Incognito Window". This parallel's Firefox's "New Private Window" and better matches what you get in Chromium's "hamburger" menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1668730/+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 1629445] Re: Chromium tabs have micro-disconnections
Please bump this if still reproducible. ** Changed in: chromium-browser (Ubuntu) Status: Triaged => 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/1629445 Title: Chromium tabs have micro-disconnections Status in chromium-browser package in Ubuntu: Incomplete Bug description: From time to time Chromium tabs disconnects from the Internet, then the terminal echoes the following: Received signal 11 SEGV_MAPERR 0078 #0 0x7fdac25b8c5e base::debug::StackTrace::StackTrace() #1 0x7fdac25b904b #2 0x7fdaaae453d0 #3 0x7fdac1c60239 blink::KURL::~KURL() #4 0x7fdac1c6024a blink::KURL::~KURL() #5 0x7fdaa78321ad blink::ScriptSourceCode::~ScriptSourceCode() #6 0x7fdaa7829d50 #7 0x7fdac1c782f0 #8 0x7fdac1c78833 blink::BaseArena::sweepUnsweptPage() #9 0x7fdac1c788d0 blink::BaseArena::lazySweepWithDeadline() #10 0x7fdac1c7ed50 blink::ThreadState::performIdleLazySweep() #11 0x7fdaa4f11561 scheduler::WebSchedulerImpl::runIdleTask() #12 0x7fdaa4f11a58 #13 0x7fdaa4f10f97 #14 0x7fdaa4f10d8f #15 0x7fdac25ba879 base::debug::TaskAnnotator::RunTask() #16 0x7fdaa4f0ac81 scheduler::TaskQueueManager::ProcessTaskFromWorkQueue() #17 0x7fdaa4f0b274 scheduler::TaskQueueManager::DoWork() #18 0x7fdaa4f08cd7 #19 0x7fdac25ba879 base::debug::TaskAnnotator::RunTask() #20 0x7fdac25dd9f1 base::MessageLoop::RunTask() #21 0x7fdac25de49d base::MessageLoop::DeferOrRunPendingTask() #22 0x7fdac25de769 base::MessageLoop::DoWork() #23 0x7fdac25e01b9 base::MessagePumpDefault::Run() #24 0x7fdac25fd358 base::RunLoop::Run() #25 0x7fdac25dc835 base::MessageLoop::Run() #26 0x7fdabf22b400 #27 0x7fdabec2d861 #28 0x7fdabec2ddfd #29 0x7fdabec2cff1 content::ContentMain() #30 0x55bc8c97b92a ChromeMain #31 0x7fd8b830 __libc_start_main #32 0x55bc8c97b7d9 _start r8: r9: 32c185e094d0 r10: 32c185da1af0 r11: 0246 r12: 3710d4a27f10 r13: 3710d4a3f000 r14: 1630 r15: 17cc14280380 di: 0020 si: 3710d4a28b20 bp: 0020 bx: 0020 dx: 17cc18bb8000 ax: 7fdaa7829e40 cx: 3710d4a28b00 sp: 7ffe7207ad20 ip: 7fdac1c60239 efl: 00010202 cgf: 0033 erf: 0004 trp: 000e msk: cr2: 0078 [end of stack trace] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 52.0.2743.116-0ubuntu0.16.04.1.1250 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DRM.card0-DP-1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: AP///wBMLdoIODYxMAgXAQOANR54KrpBoVlVnSgNUFS/74BxT4HAgQCBgJUAqcCzAAEBAjqAGHE4LUBYLEUAEyshAAAeAR0AclHQHiBuKFUAEyshAAAe/QAySx5REQAKICAgICAg/ABTMjRCMzUwCiAgICAgAZsCAxGxRpAEHxMSA2UDDAAQAAEdALxS0B4guChVQBMrIQAAHowK0JAgQDEgDEBVABMrIQAAGIwK0Iog4C0QED6WABMrIQAAGAAAIQ== dpms: On modes: 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected Date: Fri Sep 30 21:46:10 2016 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' Env: 'None' 'None' InstallationDate: Installed on 2016-05-02 (151 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InstalledPlugins: Load-Avg-1min: 0.58 Load-Processes-Running-Percent: 0.1% MachineType: MEDIONPC MS-7358 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=c34225d3-c644-4d92-a8ea-00123e6255e1 ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7358 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Fab D dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM: dmi.product.name: MS-7358 dmi.product.version: OEM dmi.sys.vendor: MEDIONPC gconf-keys: /desktop/gnome/applications/browser/exec =
[Desktop-packages] [Bug 1631851] Re: Chromium taking 150% cpu after page load
Please bump this if still reproducible. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => 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/1631851 Title: Chromium taking 150% cpu after page load Status in chromium-browser package in Ubuntu: Incomplete Bug description: - Open https://www.facebook.com/U2 - Chromium continues to take 150% cpu after page finishes loading. Running Ubuntu 14.04 Mate desktop here. This happens with latest Chromium 53.0.2785 package and earlier versions as well. I can replicate the issue in Ubuntu Mate 14.04 and 16.04 LiveCDs: Just boot, apt-get update and apt-get install chromium-browser from it. Also happens in Lubuntu 16.04 but *not* in regular 14.04 / 16.04 Ubuntu LiveCDs, so could be Gnome / Unity related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1631851/+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 1604161] Re: Chromium does not honor DOM Javascript variable document.lastModified
1. Opened a local file in Chromium 107.0.5304.62 , file:///home/nteodosio/a.html. 2. Opened the Chromium console with Ctrl+Shift+i. 3. Entered document.lastModified and verified that the output was both correct and did not change with time. ** 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/1604161 Title: Chromium does not honor DOM Javascript variable document.lastModified Status in chromium-browser package in Ubuntu: Fix Released Bug description: It seems that the Chromium web browser Version 51.0.2704.79 Ubuntu 16.04 sets the JavaScript variable document.lastModified to the current date and time if the document is browsed with the file protocol, e.g. file:///media/OS/Users Firefox shows 2016-07-18 17:36:12 for my document whereas Chromium for the same document now shows 2016-07-18 17:46:36, a time that changes every time the page is loaded. Exactly the same JavaScript function works perfectly well for Chromium when provided by HTTP, see http://www.osttimorkommitten.se/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1604161/+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 1989131] Re: [snap] What about PDF MimeType in .desktop file?
** 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/1989131 Title: [snap] What about PDF MimeType in .desktop file? Status in chromium-browser package in Ubuntu: Fix Released Bug description: I see with a recent commit (https://git.launchpad.net/~chromium- team/chromium-browser/+git/snap-from- source/commit/?id=f96f95b0b511f0943320af8aed1a41599d921b2f) you've added more MimeType entries in the .desktop file. What about PDF, since Chromium has a pretty good built-in PDF viewer? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989131/+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 1993021] Re: Chromium displays form fields of a PDF different/wrong
Upstream endorses[1] the first hypothesis. The concatenated PDF is buggy. [1]: https://bugs.chromium.org/p/chromium/issues/detail?id=1376014#c5 ** 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/1993021 Title: Chromium displays form fields of a PDF different/wrong Status in chromium-browser package in Ubuntu: Invalid Bug description: With Evince-3.36.10-0ubuntu1, fill in US-IRS PDF Y2020 tax forms (f1040, f1040s1, f1040s2) and save. With PDF-Arranger 1.4.2-1: [+] t2210-f1040.pdf [+] t2210-1040s1.pdf [+] t2210-1040s2.pdf Export (down-arrow icon) t2210-tax-cat2.pdf - popped up warnings in dialog box: The metadata field /Accessibility with value 'structured; tagged' has no XMP equivalent, so it was discarded The metadata field /Form with value 'fillable' has no XMP equivalent, so it was discarded Display of t2210-tax-cat2.pdf page 3 (f1040 s1): * chromium-browser-106.0.5249.91: incorrectly displays form entry in lines 2b, 5, 7, 8-lhs, 11, 13, 16, 21. * evince-3.36.10-0ubuntu1: correct (lines 1, 3, 9, 14 only) * firefox-104: correct (lines 1, 3, 9, 14 only) * xpdf-3.04-7: correct (lines 1, 3, 9, 14 only) Display of t2210-tax-cat2.pdf page 4 (f1040 s2): * chromium-browser-106.0.5249.91: incorrectly displays form entry in lines 1, 3, 6, 7b, 8, 8c * evince-3.36.10-0ubuntu1: correctly blank except lines 4 & 10. * firefox-104: correctly blank except lines 4 & 10. * xpdf-3.04-7: correctly blank except lines 4 & 10. Ubuntu-20.04.5/Linux-5.4.0/amd64 ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195 Uname: Linux 5.4.0-125-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Oct 14 20:40:01 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2018-11-21 (1424 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Snap: chromium 106.0.5249.119 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2022-07-09 (97 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993021/+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 1991698] Re: package chromium-browser 105.0.5195.102-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error
>From DpkgTerminalLog.txt, > Download snap "chromium" (2117) from channel "stable" (received an unexpected http response code (503) when trying to download... This was just a transient server problem, so trying again later should solve it. Let me know otherwise. ** 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/1991698 Title: package chromium-browser 105.0.5195.102-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Invalid Bug description: This happened during the OS upgrade to 20.4. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 105.0.5195.102-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBMLYELTktLMDQYAQOAPSN4Kl+xoldPoigPUFS/74BxT4EAgcCBgJUAqcCzAAEBBHQAMPJwWoCwWIoAYFkhAAAe/QAYSx5aHgAKICAgICAg/ABVMjhENTkwCiAgICAg/wBIVFBGQzAwNzU5CiAgAakCAyPxSJAEHxMDEiAiIwkHB4MBAABtAwwAEACAPCAQYAECAwI6gBhxOC1AWCxFAGBZIQAAHgI6gNByOC1AECxFgGBZIQAAHgEdAHJR0B4gbihVAGBZIQAAHlZeAKCgoClQMCA1AGBZIQAAGgAARw== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGr+0mAAAcAQSlIhN4AsY1o1ZSnigKUFQBAQEBAQEBAQEBAQEBAQEBFDeAtHA4JkBsMKoAWMIQAAAaECyAtHA4JkBsMKoAWMIQAAAa/gBHSFcxS4BCMTU2SEFOAAADQQKeABoBCiAgAAI= modes: 1920x1080 1920x1080 Date: Tue Oct 4 12:22:48 2022 Desktop-Session: 'None' 'None' 'None' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00+beaver-+X00 Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-01-06 (635 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 InstalledPlugins: Load-Avg-1min: 2.18 Load-Processes-Running-Percent: 0.2% MachineType: Dell Inc. Precision 3550 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-126-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 105.0.5195.102-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-10-04 (0 days ago) dmi.bios.date: 09/07/2022 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.1 dmi.board.name: 0XK86F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: MTTESTPC dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.1:bd09/07/2022:svnDellInc.:pnPrecision3550:pvr:rvnDellInc.:rn0XK86F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3550 dmi.product.sku: 09A2 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1991698/+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 1993729] Re: failed to install
I missed the DpkgTerminalLog in my last comment. error: snap "chromium" has "install-snap" change in progress This most likely means you tried to `apt install chromium-browser` simultaneously to `snap install chromium`. Easiest is to `apt remove chromium-browser; snap remove chromium`, and then use only one command to install it. ** 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/1993729 Title: failed to install Status in chromium-browser package in Ubuntu: Incomplete Bug description: app failed to install first time froze half way through so tried dpkg --configure then tried reinstalling now comes up with error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 20 19:06:29 2022 Dependencies: ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-10-19 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: chromium-browser Title: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 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/1993729/+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 1993562] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor
** Changed in: chromium-browser (Ubuntu) Status: New => Triaged ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Low -- 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/1993562 Title: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor Status in chromium-browser package in Ubuntu: Triaged Bug description: When starting chromium's snap, those messages are logged: $ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F snap.chromium.chromium audit: type=1400 audit(1666201583.608:610): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:611): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_name" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:612): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_vendor" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 audit: type=1400 audit(1666201583.608:613): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_version" pid=320950 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Chromium behaves OK but generates log pollution. Additional info: $ snap list chromium snapd Name Version RevTracking Publisher Notes chromium 106.0.5249.119 2136 latest/stable canonical✓ - snapd 2.57.4 17336 latest/stable canonical✓ snapd $ uname -rm 5.15.0-52-generic x86_64 $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993562/+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 1993729] [NEW] failed to install
Hi Tristian, thanks for your bug report.
Let me see if I understand: You executed dpkg --configure -a, which
completed successfully.
You say you tried reinstalling. Did you try it in a terminal with
apt remove chromium-browser
apt install chromium-browser
? If not, can you try it and report its output?
If that doesn't solve the error, run
{ snap info chromium; chromium; } &> chr.log
and attach the chr.log file to this bug report.
Probably unrelated, but the last line of your dmesg has
> Please run fsck.
Might be a good idea to heed that.
--
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/1993729
Title:
failed to install
Status in chromium-browser package in Ubuntu:
New
Bug description:
app failed to install first time froze half way through so tried dpkg
--configure then tried reinstalling now comes up with error
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
AptOrdering:
chromium-browser:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Oct 20 19:06:29 2022
Dependencies:
ErrorMessage: new chromium-browser package pre-installation script subprocess
returned error exit status 10
InstallationDate: Installed on 2022-10-19 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal,
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.21.1ubuntu2.1
apt 2.4.8
SourcePackage: chromium-browser
Title: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 10
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/1993729/+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 1990010] 105.0.5195.19 .deb results
No dice here, FfmpegVideoDecoder ):
** Attachment added: "chr105.log"
https://bugs.launchpad.net/bugs/1990010/+attachment/5625585/+files/chr105.log
--
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/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+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 1993581] Re: [snap] posix_spawn: No such file or directory
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => 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/1993581 Title: [snap] posix_spawn: No such file or directory Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium from the edge channel fails to launch with % chromium [17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] posix_spawn: No such file or directory (2) % snap info chromium channels: latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB - latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB - latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB - latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB - installed: 108.0.5355.0 (2146) 153MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] [NEW] [snap] posix_spawn: No such file or directory
Public bug reported: Chromium from the edge channel fails to launch with % chromium [17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] posix_spawn: No such file or directory (2) % snap info chromium channels: latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB - latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB - latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB - latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB - installed: 108.0.5355.0 (2146) 153MB - ** Affects: chromium-browser (Ubuntu) Importance: Critical Assignee: Nathan Teodosio (nteodosio) 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/1993581 Title: [snap] posix_spawn: No such file or directory Status in chromium-browser package in Ubuntu: New Bug description: Chromium from the edge channel fails to launch with % chromium [17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] posix_spawn: No such file or directory (2) % snap info chromium channels: latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB - latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB - latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB - latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB - installed: 108.0.5355.0 (2146) 153MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1843392] Re: [snap] smart card reader no longer works
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Changed in: firefox (Ubuntu) Status: New => Confirmed ** Changed in: firefox (Ubuntu) Importance: Undecided => High ** Changed in: chromium-browser (Ubuntu) Assignee: Olivier Tilloy (osomon) => (unassigned) ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1734371 Importance: Unknown Status: Unknown -- 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/1843392 Title: [snap] smart card reader no longer works Status in Mozilla Firefox: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: chromium uses the Netscape Cryptographic Module to access smartcards for authentication purposes. This stopped working when switching to the snap version. Chromium would normally access the setup in ~/.pki/nssdb/pkcs11.txt That file would refer to a library used to access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc- pkcs11.so The problem can be bypassed by manually launching chromium via: /snap/chromium/current/usr/lib/chromium-browser/chrome To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1843392/+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 1993191] Diffs
Those would be the corresponding diffs I suppose, are them to be sponsored? I suppose a SRU will be needed for Jammy and Focal. ** Patch added: "focal.diff" https://bugs.launchpad.net/bugs/1993191/+attachment/5624840/+files/focal.diff ** Patch added: "jammy.diff" https://bugs.launchpad.net/bugs/1993191/+attachment/5624841/+files/jammy.diff ** Patch added: "kinetic.diff" https://bugs.launchpad.net/bugs/1993191/+attachment/5624842/+files/kinetic.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/1993191 Title: apport hook that collects snap's information is outdated Status in chromium-browser package in Ubuntu: In Progress Status in chromium-browser source package in Focal: In Progress Status in chromium-browser source package in Jammy: In Progress Status in chromium-browser source package in Kinetic: In Progress Bug description: See https://bazaar.launchpad.net/~chromium-team/chromium- browser/groovy-stable/view/head:/debian/apport/chromium- browser.py#L59. It collects information about core18, but the chromium snap was rebased on core20 almost a year ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+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 1993191] Re: apport hook that collects snap's information is outdated
** Changed in: chromium-browser (Ubuntu) Milestone: None => kinetic-updates ** Also affects: chromium-browser (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: chromium-browser (Ubuntu Kinetic) Importance: Medium Assignee: Olivier Tilloy (osomon) Status: In Progress ** Also affects: chromium-browser (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: chromium-browser (Ubuntu Kinetic) Milestone: kinetic-updates => None ** Changed in: chromium-browser (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: chromium-browser (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: chromium-browser (Ubuntu Jammy) Status: New => In Progress ** Changed in: chromium-browser (Ubuntu Focal) Status: New => 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/1993191 Title: apport hook that collects snap's information is outdated Status in chromium-browser package in Ubuntu: In Progress Status in chromium-browser source package in Focal: In Progress Status in chromium-browser source package in Jammy: In Progress Status in chromium-browser source package in Kinetic: In Progress Bug description: See https://bazaar.launchpad.net/~chromium-team/chromium- browser/groovy-stable/view/head:/debian/apport/chromium- browser.py#L59. It collects information about core18, but the chromium snap was rebased on core20 almost a year ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+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 1993021] Re: Chromium displays form fields of a PDF different/wrong
Reported upstream at https://bugs.chromium.org/p/chromium/issues/detail?id=1376014. -- 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/1993021 Title: Chromium displays form fields of a PDF different/wrong Status in chromium-browser package in Ubuntu: New Bug description: With Evince-3.36.10-0ubuntu1, fill in US-IRS PDF Y2020 tax forms (f1040, f1040s1, f1040s2) and save. With PDF-Arranger 1.4.2-1: [+] t2210-f1040.pdf [+] t2210-1040s1.pdf [+] t2210-1040s2.pdf Export (down-arrow icon) t2210-tax-cat2.pdf - popped up warnings in dialog box: The metadata field /Accessibility with value 'structured; tagged' has no XMP equivalent, so it was discarded The metadata field /Form with value 'fillable' has no XMP equivalent, so it was discarded Display of t2210-tax-cat2.pdf page 3 (f1040 s1): * chromium-browser-106.0.5249.91: incorrectly displays form entry in lines 2b, 5, 7, 8-lhs, 11, 13, 16, 21. * evince-3.36.10-0ubuntu1: correct (lines 1, 3, 9, 14 only) * firefox-104: correct (lines 1, 3, 9, 14 only) * xpdf-3.04-7: correct (lines 1, 3, 9, 14 only) Display of t2210-tax-cat2.pdf page 4 (f1040 s2): * chromium-browser-106.0.5249.91: incorrectly displays form entry in lines 1, 3, 6, 7b, 8, 8c * evince-3.36.10-0ubuntu1: correctly blank except lines 4 & 10. * firefox-104: correctly blank except lines 4 & 10. * xpdf-3.04-7: correctly blank except lines 4 & 10. Ubuntu-20.04.5/Linux-5.4.0/amd64 ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195 Uname: Linux 5.4.0-125-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Oct 14 20:40:01 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2018-11-21 (1424 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Snap: chromium 106.0.5249.119 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2022-07-09 (97 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993021/+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 1987137] Debian patch
I was just messing around and found this Debian patch[1]; Seems to be very much on point. [1]: https://sources.debian.org/src/chromium/106.0.5249.119-1/debian/patches/fixes/angle-wayland.patch/ -- 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/1987137 Title: Migrating chromium-browser to core22 has libwayland-client0 issues Status in chromium-browser package in Ubuntu: New Bug description: Following on an earlier bug report that related to simple core22 migration for chromium-browser, here is a blocker that I don't know how to deal with. After checking out the core22 branch from git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22 (which already contains the early, easy migration commits), doing a build eventually generates (snippet here): 2022-08-19 20:15:05.809 :: In file included from ../../third_party/wayland/src/src/wayland-client.h:40: 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct wl_proxy *) wl_display, 2022-08-19 20:15:05.809 ::^ 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct wl_proxy *) wl_display, 2022-08-19 20:15:05.810 ::^ 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct wl_proxy *) wl_registry, 2022-08-19 20:15:05.810 :: ^ 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared identifier 'wl_proxy_marshal_flags' 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct wl_proxy *) wl_compositor, and lots more of the same; it seems pretty clear that the relevant wayland library is simply not new enough, and I don't know what to add/modify to add core22 support to the mix, so I am open to suggestions. I do notice the file parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json, which contains package version manifests for various distros, but not Ubuntu 22.04, so I'm *guessing* that might need enhancement. But that's just a guess. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+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 1816497] AMD GPU
Thanks for the report, especially valuable as it is the first about AMD.
I just submitted a change and pushed the new build. Can you please give
it a try?
# snap refresh --channel beta/hwacc chromium
$ snap run chromium
The previous version did not include the radeonsi_drv_video.so driver
(the one in your system is not visible from snap confinement).
If it still doesn't work, please attach the outputs of env and lscpu.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel beta/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples.
4. Enter about:media-internals in the address bar, click the
corresponding box (if the video is playing, it will have the "(kPlay)"
identifier) and note what the page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
Currently it seems to work for all reporters on Xorg, but not for all
reporters on Wayland.
Just to situate ourselves, beta/hwacc is [1] and I plan to merge it in
the main snap via [2]. Comments before #176 refer to [3] and _should_
be roughly equivalent to [1], but I wouldn't be surprised if it turned
out not to be.
[1]:
https://launchpad.net/~nteodosio/+snap/chromium-browser-dev/+build/1875127
[2]:
https://code.launchpad.net/~nteodosio/chromium-browser/+git/chromium-browser/+merge/428038
[3]:
https://launchpad.net/~nteodosio/+snap/chromium-browser-hwacc/+build/1838168
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1993021] Re: Chromium displays form fields of a PDF different/wrong
I can verify that the *cat2*.pdf file matches your description, displaying incorrectly in Chromium 106.0.5249.119 and correctly on Evince and Zathura. However, if I generate it myself from pdfarranger t2210-f1040.pdf t2210-1040s1.pdf t2210-1040s2.pdf , with PDF-Arranger 1.8.2-1, the problem no longer occurs. I see two possible conclusions: - The concatenated file in your zip (and thus 1.4.2-1) has a bug such that its rendering relies undefined behavior — but I don't know if there is such a thing; or - Chromium has a bug and renders a fine PDF incorrectly. -- 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/1993021 Title: Chromium displays form fields of a PDF different/wrong Status in chromium-browser package in Ubuntu: New Bug description: With Evince-3.36.10-0ubuntu1, fill in US-IRS PDF Y2020 tax forms (f1040, f1040s1, f1040s2) and save. With PDF-Arranger 1.4.2-1: [+] t2210-f1040.pdf [+] t2210-1040s1.pdf [+] t2210-1040s2.pdf Export (down-arrow icon) t2210-tax-cat2.pdf - popped up warnings in dialog box: The metadata field /Accessibility with value 'structured; tagged' has no XMP equivalent, so it was discarded The metadata field /Form with value 'fillable' has no XMP equivalent, so it was discarded Display of t2210-tax-cat2.pdf page 3 (f1040 s1): * chromium-browser-106.0.5249.91: incorrectly displays form entry in lines 2b, 5, 7, 8-lhs, 11, 13, 16, 21. * evince-3.36.10-0ubuntu1: correct (lines 1, 3, 9, 14 only) * firefox-104: correct (lines 1, 3, 9, 14 only) * xpdf-3.04-7: correct (lines 1, 3, 9, 14 only) Display of t2210-tax-cat2.pdf page 4 (f1040 s2): * chromium-browser-106.0.5249.91: incorrectly displays form entry in lines 1, 3, 6, 7b, 8, 8c * evince-3.36.10-0ubuntu1: correctly blank except lines 4 & 10. * firefox-104: correctly blank except lines 4 & 10. * xpdf-3.04-7: correctly blank except lines 4 & 10. Ubuntu-20.04.5/Linux-5.4.0/amd64 ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195 Uname: Linux 5.4.0-125-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Oct 14 20:40:01 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2018-11-21 (1424 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Snap: chromium 106.0.5249.119 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2022-07-09 (97 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993021/+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 1992648] Possibly related
*** This bug is a duplicate of bug 1991691 *** https://bugs.launchpad.net/bugs/1991691 Possibly related to LP: #1991691, I also had font problems in the Firefox snap with kernel 5.19.0-19 which were solved by reverting to 5.19.0-18. The reporter of this issue confirmed[1] he was also on that kernel. [1]: https://irclogs.ubuntu.com/2022/10/14/%23ubuntu-next.html -- 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/1992648 Title: Japanese Text no longer shows Status in firefox package in Ubuntu: New Bug description: 1) Ubuntu 22.10 2) firefox 05.0.3-1 1943 latest/stablemozilla✓- 3) Text written in japanese no longer shows, instead, the unicode fallback font is used, for example https://ja.wikipedia.org/wiki/%E6%97%A5%E6%9C%AC%E3%81%AB%E3%81%8A%E3%81%91%E3%82%8B%E6%BC%A2%E5%AD%97 It shows up fine in a browser running in a 20.04 LXC, and it also shows correctly in the window title bar, but not inside the actual browser. 4) I expect japanese text to show up correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992648/+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 1625517] Re: Clicking inside address bar does not update PRIMARY buffer (middle-mouse clipboard)
https://bugs.chromium.org/p/chromium/issues/detail?id=951475 ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- 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/1625517 Title: Clicking inside address bar does not update PRIMARY buffer (middle- mouse clipboard) Status in chromium-browser package in Ubuntu: Won't Fix Status in firefox package in Ubuntu: Confirmed Bug description: When I click in the address bar once, the entire URL is selected. In most other applications, this is an indicator that my PRIMARY buffer [1] has been updated with the full URL. However, when I MMB-paste, the previous contents of the buffer appear. This has tripped me up on many occasions. Steps to reproduce: 1: Open a text editor, or any other recepticle for pasted text. 2: Select some text on a page. 3: Middle-click in the text editor, and verify that it's the text you selected in step 2. 4: Click the address bar in Chromium. The URL is highlighted. 5: Middle-click in the text editor again. 6: Hit Ctrl+z. Frustratedly go back to your browser. Click the address bar once, then again to deselect everything. Then drag or triple-click to select all. 7: Middle-click in the text editor again. Now it works. Expected results: In step 5, the full URL of the page you were visiting should have appeared. However, it's still the text you selected in step 2. I'm using Chromium version 52.0.2743.116 Built on Ubuntu , running on Ubuntu 16.04 (64-bit) [1]: I'm not shouting, this is what it's called. It's also known as the "middle-mouse clipboard". See also https://tronche.com/gui/x/icccm/sec-2.html#s-2.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1625517/+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 1991493] Patch v2
The last patch fails to build, I must have only tried to build the
source package with debuild -S, sorry.
This one was built successfully with debuild.
** Patch added: "nmo2.diff"
https://bugs.launchpad.net/bugs/1991493/+attachment/5621788/+files/nmo2.diff
** Changed in: network-manager-openvpn (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1991493
Title:
Data ciphers are not properly configured with openvpn 2.6
Status in NetworkManager-OpenVPN:
New
Status in network-manager-openvpn package in Ubuntu:
Triaged
Bug description:
OPTIONS ERROR: failed to negotiate cipher with server. Add the
server's cipher ('AES-256-CBC') to --data-ciphers (currently
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to
this server.
So basically some servers won't be supported anymore because
unsupported '--cipher' option is used instead of '--data-ciphers'
A fix is available at https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/merge_requests/46
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1991493/+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 1991493] Re: Data ciphers are not properly configured with openvpn 2.6
** Changed in: network-manager-openvpn (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1991493
Title:
Data ciphers are not properly configured with openvpn 2.6
Status in NetworkManager-OpenVPN:
New
Status in network-manager-openvpn package in Ubuntu:
In Progress
Bug description:
OPTIONS ERROR: failed to negotiate cipher with server. Add the
server's cipher ('AES-256-CBC') to --data-ciphers (currently
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to
this server.
So basically some servers won't be supported anymore because
unsupported '--cipher' option is used instead of '--data-ciphers'
A fix is available at https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/merge_requests/46
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1991493/+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 1991293] Re: sane-backends 1.1.1-5 FTBFS
Since the bug didn't affect the user base directly, only testing, we will wait for a sync with Debian. Thanks, Ralph! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1991293 Title: sane-backends 1.1.1-5 FTBFS Status in sane-backends: Fix Released Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends package in Debian: Fix Released Bug description: FTBFS[1]: ---> minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::Pixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::RawPixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::PixelFormat’) <--- Since this happens in testsuite/, my suggested workaround is to simply disable the offending call, responsible for a diagnostic message. [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic- amd64.sane-backends_1.1.1-5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/1991293/+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 1991493] Re: Data ciphers are not properly configured with openvpn 2.6
Cherry-pick of the commits mentioned by
https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/merge_requests/46#note_1566186.
** Patch added: "nmo.diff"
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1991493/+attachment/5621148/+files/nmo.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1991493
Title:
Data ciphers are not properly configured with openvpn 2.6
Status in NetworkManager-OpenVPN:
New
Status in network-manager-openvpn package in Ubuntu:
Triaged
Bug description:
OPTIONS ERROR: failed to negotiate cipher with server. Add the
server's cipher ('AES-256-CBC') to --data-ciphers (currently
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to
this server.
So basically some servers won't be supported anymore because
unsupported '--cipher' option is used instead of '--data-ciphers'
A fix is available at https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/merge_requests/46
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1991493/+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 1990010] Re: VA error: resource allocation failed
Makes sense (assuming the Libva etc. is the same), thanks for
investigating this further!
Since you are the one working on this it is more accurate to transfer
the assignment status to you. If you feel otherwise please let me know.
** Changed in: chromium-browser (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => Bram Stolk (b-stolk)
--
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/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+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 1991563] [NEW] download.default_directory inside /tmp/snap.chromium
Sorry, this is by design[1][2]:
> snaps aren’t allowed to share content in directories like /tmp,
/run/shm or /var/tmp. This is one reason why we use a mount namespace to
the snap has a snap-specific /tmp directory
[1]:
https://forum.snapcraft.io/t/tizonia-snap-apparmor-denied-suggestion-adjust-program-to-use-tmpdir-or-tmp/4951/2
[2]: https://forum.snapcraft.io/t/accessing-tmp-from-snaps/22384
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
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/1991563
Title:
download.default_directory inside /tmp/snap.chromium
Status in chromium-browser package in Ubuntu:
Won't Fix
Bug description:
While using a selenium test, I found out the download files are not
inside the download.default_directory the test is setting, but
prefixed by /tmp/snap.chromium/
Python example:
options = Options()
prefs = { "download.default_directory": "/tmp" }
options.add_experimental_option("prefs", prefs)
browser = webdriver.Chrome(options=options)
# click on a button that download a file.
This file would be in /tmp/snap.chromium/tmp instead of just /tmp/
I'm on Ubuntu 22.04.1 LTS and I use Chromium 105.0.5195.125 (Official
Build) snap (64-bit)
Any idea how to relocate where the files are saved during a selenium
test to be outside of /tmp/snap.chromium directory (which belongs to
root user)?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1991563/+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 1900167] Re: gnome-software Unable to install updates
I kept clicking the button and at some point it turned into Download, not sure if as a result of insisting or of a completed snap-store update that I had to do manually with snap-store --quit snap refresh snap-store -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1900167 Title: gnome-software Unable to install updates Status in gnome-software package in Ubuntu: Expired Bug description: Click on 'Updates' and then on 'Restart & Update' I have a message: Unable to install updates: GDBus.error... Prepared update not found:/var/lib/PackageKit/prepared-update corrado@corrado-x2-gg-1009:~$ apt policy gnome-software gnome-software: Installed: 3.38.0-2build1 Candidate: 3.38.0-2build1 Version table: *** 3.38.0-2build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-x2-gg-1009:~$ inxi -Fx System: Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 Sound Server: ALSA v: k5.8.0-23-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives: Local Storage: total: 2.05 TiB used: 9.42 GiB (0.4%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 9.41 GiB (30.1%) fs: ext4 dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 43.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash v: 5.0.17 inxi: 3.1.07 corrado@corrado-x2-gg-1009:~$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 18:20:00 2020 InstallationDate: Installed on 2020-10-10 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1900167/+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 1900167] Re: gnome-software Unable to install updates
I confirm this bug on Jammy. The error message in the notification box is Unable to install updates Prepared update not found: "/var/lib/PackageKit/prepared-update" and stderr says Snapd snapd_client_refresh_sync: assertion 'name != NULL' failed Gs snap did not set error for gs_plugin_update Gs not GsPlugin error pk-engine-error-quark:1: Prepared update not found: /var/lib/PackageKit/prepared-update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1900167 Title: gnome-software Unable to install updates Status in gnome-software package in Ubuntu: Expired Bug description: Click on 'Updates' and then on 'Restart & Update' I have a message: Unable to install updates: GDBus.error... Prepared update not found:/var/lib/PackageKit/prepared-update corrado@corrado-x2-gg-1009:~$ apt policy gnome-software gnome-software: Installed: 3.38.0-2build1 Candidate: 3.38.0-2build1 Version table: *** 3.38.0-2build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-x2-gg-1009:~$ inxi -Fx System: Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 Sound Server: ALSA v: k5.8.0-23-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives: Local Storage: total: 2.05 TiB used: 9.42 GiB (0.4%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 9.41 GiB (30.1%) fs: ext4 dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 43.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash v: 5.0.17 inxi: 3.1.07 corrado@corrado-x2-gg-1009:~$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 18:20:00 2020 InstallationDate: Installed on 2020-10-10 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1900167/+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 1990010] Re: VA error: resource allocation failed
FFMpeg decoder either way for me. `intel_gpu_top` reports Cofeelake and
confirms no video decoding.
--
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/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+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 1991022] Re: [FFe] Socket activation
> @Nathan, I've uploaded that one with some tweaks now, let me know if you > think it's right Absolutely! Thanks, Sebastien. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [FFe] Socket activation Status in speech-dispatcher package in Ubuntu: Fix Committed Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Rationale] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. And then, > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[2], but still not released. I have built and installed the package in Kinetic and verified that spd-say still causes the dispatcher spawn and emits sound. Upstream test can also confirm this. [1]: https://github.com/brailcom/speechd/issues/335 [2]: https://github.com/brailcom/speechd/pull/763 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+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 1990010] Re: VA error: resource allocation failed
> ** Attachment added: "chromium-browser-unstable_104.0.5112.101-1_amd64"
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620071/+files/chromium-browser-unstable_104.0.5112.101-1_amd64.deb
>
Thanks Qinling.
Playback is software accelerated as verified in about:media-internals
(kDecoderName is FfmpegVideoDecoder).
Tested on Wayland. Execution log is attached.
--->
% vainfo
libva info: VA-API version 1.15.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.15 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.4.3 ()
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileVP9Profile0: VAEntrypointVLD
VAProfileVP9Profile2: VAEntrypointVLD
<---
** Attachment added: "log"
https://bugs.launchpad.net/bugs/1990010/+attachment/5620076/+files/log
--
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/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug
[Desktop-packages] [Bug 1991293] [NEW] sane-backends 1.1.1-5 FTBFS
Public bug reported: FTBFS[1]: ---> minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::Pixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::RawPixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::PixelFormat’) <--- Since this happens in testsuite/, my suggested workaround is to simply disable the offending call, responsible for a diagnostic message. [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic- amd64.sane-backends_1.1.1-5_BUILDING.txt.gz ** Affects: sane-backends (Ubuntu) Importance: High Assignee: Nathan Teodosio (nteodosio) Status: New ** Tags: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1991293 Title: sane-backends 1.1.1-5 FTBFS Status in sane-backends package in Ubuntu: New Bug description: FTBFS[1]: ---> minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::Pixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::RawPixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::PixelFormat’) <--- Since this happens in testsuite/, my suggested workaround is to simply disable the offending call, responsible for a diagnostic message. [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic- amd64.sane-backends_1.1.1-5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1991293/+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 1991293] Re: sane-backends 1.1.1-5 FTBFS
To-do is to submit a proper fix upstream, which likely involves overloading the << operator for the offending types. ** Patch added: "sane-backends.diff" https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1991293/+attachment/5620060/+files/sane-backends.diff ** Changed in: sane-backends (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: sane-backends (Ubuntu) Importance: Undecided => High ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1991293 Title: sane-backends 1.1.1-5 FTBFS Status in sane-backends package in Ubuntu: New Bug description: FTBFS[1]: ---> minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::Pixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::RawPixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::PixelFormat’) <--- Since this happens in testsuite/, my suggested workaround is to simply disable the offending call, responsible for a diagnostic message. [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic- amd64.sane-backends_1.1.1-5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1991293/+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 1991253] [NEW] Fix test failure in abseil 0~20210324.2-4
Public bug reported: Abseil is failing to build in Kinetic because of a segmentation fault in test phase[1]. I'm forwarding a fix from upstream. [1]: https://launchpadlibrarian.net/625442454/buildlog_ubuntu-kinetic- amd64.abseil_0~20210324.2-4_BUILDING.txt.gz ** Affects: abseil (Ubuntu) Importance: High Assignee: Nathan Teodosio (nteodosio) Status: New ** Tags: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to abseil in Ubuntu. https://bugs.launchpad.net/bugs/1991253 Title: Fix test failure in abseil 0~20210324.2-4 Status in abseil package in Ubuntu: New Bug description: Abseil is failing to build in Kinetic because of a segmentation fault in test phase[1]. I'm forwarding a fix from upstream. [1]: https://launchpadlibrarian.net/625442454/buildlog_ubuntu-kinetic- amd64.abseil_0~20210324.2-4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/abseil/+bug/1991253/+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 1991117] Re: 13.3.0-3build1 fails to build from source
Thanks for your review, Sebastien.
I attach the patch with the cherry-pick.
> Also please tag the patches you add
Added more tags in this one, please do let me know if I still left a
relevant field out.
PS: I sent mail to this bug but it didn't arrive (at least yet). So
disregard echos of this message.
** Patch added: "xorg-vmware3.diff"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+attachment/5620009/+files/xorg-vmware3.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1991117
Title:
13.3.0-3build1 fails to build from source
Status in xserver-xorg-video-vmware package in Ubuntu:
Incomplete
Bug description:
[Log]
https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz
[Error]
../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’:
../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always
evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address]
240 |if (priv->yuv[i]) {
|^~~~
../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here
125 | struct xa_surface *yuv[2][3];
|^~~
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+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 1990010] Re: VA error: resource allocation failed
> Which build guide did you follow to build your chromium browser? Could
> you please provide us the version of your chromium browser and vainfo
> output information? Thank you!
Qinling, the snap against which we have been testing is built from [1].
(Please correct me, Bram, if you tested a different build.)
[1]: https://git.launchpad.net/~nteodosio/chromium-browser/tree/?h=dev
--
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/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+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 1991138] [NEW] 16.04.1+18.10.20180917-0ubuntu8 fails to build from source
Public bug reported: [Log] https://launchpadlibrarian.net/625439356/buildlog_ubuntu-kinetic-armhf.libdbusmenu_16.04.1+18.10.20180917-0ubuntu8_BUILDING.txt.gz ** Affects: libdbusmenu (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libdbusmenu in Ubuntu. https://bugs.launchpad.net/bugs/1991138 Title: 16.04.1+18.10.20180917-0ubuntu8 fails to build from source Status in libdbusmenu package in Ubuntu: New Bug description: [Log] https://launchpadlibrarian.net/625439356/buildlog_ubuntu-kinetic-armhf.libdbusmenu_16.04.1+18.10.20180917-0ubuntu8_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/1991138/+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 1991117] Re: 13.3.0-3build1 fails to build from source
** Patch added: "xorg-vmware.diff"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+attachment/5619810/+files/xorg-vmware.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1991117
Title:
13.3.0-3build1 fails to build from source
Status in xserver-xorg-video-vmware package in Ubuntu:
New
Bug description:
[Log]
https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz
[Error]
../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’:
../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always
evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address]
240 |if (priv->yuv[i]) {
|^~~~
../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here
125 | struct xa_surface *yuv[2][3];
|^~~
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+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 1991117] [NEW] 13.3.0-3build1 fails to build from source
Public bug reported:
[Log]
https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz
[Error]
../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’:
../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always
evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address]
240 |if (priv->yuv[i]) {
|^~~~
../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here
125 | struct xa_surface *yuv[2][3];
|^~~
** Affects: xserver-xorg-video-vmware (Ubuntu)
Importance: Undecided
Status: New
** Tags: patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1991117
Title:
13.3.0-3build1 fails to build from source
Status in xserver-xorg-video-vmware package in Ubuntu:
New
Bug description:
[Log]
https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz
[Error]
../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’:
../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always
evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address]
240 |if (priv->yuv[i]) {
|^~~~
../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here
125 | struct xa_surface *yuv[2][3];
|^~~
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+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 1991100] Re: 2.3.3.4+dfsg-1ubuntu5 fails to build from source
** Patch added: "clucene.diff" https://bugs.launchpad.net/ubuntu/+source/clucene-core/+bug/1991100/+attachment/5619789/+files/clucene.diff ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1991100 Title: 2.3.3.4+dfsg-1ubuntu5 fails to build from source Status in clucene-core package in Ubuntu: New Bug description: Log: https://launchpadlibrarian.net/625441502/buildlog_ubuntu-kinetic- amd64.clucene-core_2.3.3.4+dfsg-1ubuntu5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clucene-core/+bug/1991100/+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 1991100] [NEW] 2.3.3.4+dfsg-1ubuntu5 fails to build from source
Public bug reported: Log: https://launchpadlibrarian.net/625441502/buildlog_ubuntu-kinetic- amd64.clucene-core_2.3.3.4+dfsg-1ubuntu5_BUILDING.txt.gz ** Affects: clucene-core (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1991100 Title: 2.3.3.4+dfsg-1ubuntu5 fails to build from source Status in clucene-core package in Ubuntu: New Bug description: Log: https://launchpadlibrarian.net/625441502/buildlog_ubuntu-kinetic- amd64.clucene-core_2.3.3.4+dfsg-1ubuntu5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clucene-core/+bug/1991100/+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 1991022] Re: Feature freeze exception: Socket activation
** Description changed: [Description] Systemd socket activation for Speech Dispatcher. - - - Creates the speech-dispatcher.socket; - - Modifies the server so that it can detect it was automatically launched by that socket activation; and - - Modifies the Autotools files accordingly. + + - Creates the speech-dispatcher.socket; + - Modifies the server so that it can detect it was automatically launched by that socket activation; and + - Modifies the Autotools files accordingly. [Rationale] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. And then, > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] - The change was already proposed upstream[2], but it is on hold because - the build with undefined sanitizer CI failed two times out of four. In - the words of the maintainer, - - > That's not systematic, but that's often enough that it'll be a pain in - the CI, and is a sign of some subtle bug creeping in there. - - I then opened my own fork with debugging enabled[3] to track down the - problem, but the CI succeeded all the six times I executed it[4], so at - this point I'd assume it was a transient issue more than a subtle bug. + The changes are already merged upstream[2], but still not released. I have built and installed the package in Kinetic and verified that spd- say still causes the dispatcher spawn and emits sound. Upstream test can also confirm this. [1]: https://github.com/brailcom/speechd/issues/335 [2]: https://github.com/brailcom/speechd/pull/763 - [3]: https://github.com/brailcom/speechd/commit/a63a5f7fe187edd5bf60c12a9c8e078cd2234e73 - [4]: https://github.com/nteodosio/speechd/actions/runs/3129483607 ** Patch added: "0.11.3-1--0.11.3-1ubuntu1.diff" https://bugs.launchpad.net/bugs/1991022/+attachment/5619783/+files/0.11.3-1--0.11.3-1ubuntu1.diff ** Attachment added: "speechd-apt-install-log" https://bugs.launchpad.net/bugs/1991022/+attachment/5619784/+files/speechd-apt-install-log ** Tags removed: wip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: Feature freeze exception: Socket activation Status in speech-dispatcher package in Ubuntu: New Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Rationale] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. And then, > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[2], but still not released. I have built and installed the package in Kinetic and verified that spd-say still causes the dispatcher spawn and emits sound. Upstream test can also confirm this. [1]: https://github.com/brailcom/speechd/issues/335 [2]: https://github.com/brailcom/speechd/pull/763 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions --
[Desktop-packages] [Bug 1991022] [NEW] Feature freeze exception: Socket activation
Public bug reported: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Rationale] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it > inside of the sandbox, so that each application has its own "private" > instance of Speech Dispatcher running. This works more or less, but it has > the downside that speech dispatcher cannot coordinate simultaneous messages > from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the > same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps > access to the Speech Dispatcher instance of the host. And then, > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The change was already proposed upstream[2], but it is on hold because the build with undefined sanitizer CI failed two times out of four. In the words of the maintainer, > That's not systematic, but that's often enough that it'll be a pain in the CI, and is a sign of some subtle bug creeping in there. I then opened my own fork with debugging enabled[3] to track down the problem, but the CI succeeded all the six times I executed it[4], so at this point I'd assume it was a transient issue more than a subtle bug. I have built and installed the package in Kinetic and verified that spd- say still causes the dispatcher spawn and emits sound. Upstream test can also confirm this. [1]: https://github.com/brailcom/speechd/issues/335 [2]: https://github.com/brailcom/speechd/pull/763 [3]: https://github.com/brailcom/speechd/commit/a63a5f7fe187edd5bf60c12a9c8e078cd2234e73 [4]: https://github.com/nteodosio/speechd/actions/runs/3129483607 ** Affects: speech-dispatcher (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic wip ** Attachment added: "speechd-sbuild-log" https://bugs.launchpad.net/bugs/1991022/+attachment/5619593/+files/speechd-sbuild-log ** Tags added: wip ** Tags added: kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: Feature freeze exception: Socket activation Status in speech-dispatcher package in Ubuntu: New Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Rationale] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. And then, > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The change was already proposed upstream[2], but it is on hold because the build with undefined sanitizer CI failed two times out of four. In the words of the maintainer, > That's not systematic, but that's often enough that it'll be a pain in the CI, and is a sign of some subtle bug creeping in there. I then opened my own fork with debugging enabled[3] to track down the problem, but the CI succeeded all the six times I executed it[4], so at this point I'd assume it was a transient issue more than a subtle bug. I have built and installed the package in Kinetic and verified that spd-say still causes the dispatcher spawn and emits sound. Upstream test can also confirm this. [1]: https://github.com/brailcom/speechd/issues/335 [2]: https://github.com/brailcom/speechd/pull/763 [3]:
[Desktop-packages] [Bug 1983794] Test case from 1949200
I'm forwarding the program provided by
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/comments/26
as a useful minimal test case for the regression introduced by the
Libcanberra handle-display-closing patch.
** Attachment added: "test-gtk.c"
https://bugs.launchpad.net/bugs/1983794/+attachment/5619461/+files/test-gtk.c
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1990010] Re: VA error: resource allocation failed
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
** 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/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+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 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes
** 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/1514484 Title: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes Status in chromium-browser package in Ubuntu: Fix Committed Bug description: You can't have arguments with spaces inside CHROMIUM_FLAGS, whatever comes after the first space is going to be interpreted as an URL by the actual chromium binary. Easy repro: 1. Set user's CHROMIUM_FLAGS with an argument containing spaces, eg: $ echo 'CHROMIUM_FLAGS=--user-agent="A B C"' > .chromium-browser.init 2. Run chromium: $ /usr/bin/chromium-browser 3. See 2 extra open tabs, one trying to open URL 'B', the other 'C'. The cause for this funny behavior is the lack of quotes around $CHROMIUM_FLAGS in the script installed in /usr/bin/chromium-browser -- it calls $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@" by the end of the script. I've tried working around it but couldn't, no amount of escaping and extra quotes seems to help if it's called like that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1514484/+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 1989131] Re: [snap] What about PDF MimeType in .desktop file?
** 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/1989131 Title: [snap] What about PDF MimeType in .desktop file? Status in chromium-browser package in Ubuntu: Fix Committed Bug description: I see with a recent commit (https://git.launchpad.net/~chromium- team/chromium-browser/+git/snap-from- source/commit/?id=f96f95b0b511f0943320af8aed1a41599d921b2f) you've added more MimeType entries in the .desktop file. What about PDF, since Chromium has a pretty good built-in PDF viewer? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989131/+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 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes
** 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/1514484 Title: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes Status in chromium-browser package in Ubuntu: Fix Committed Bug description: You can't have arguments with spaces inside CHROMIUM_FLAGS, whatever comes after the first space is going to be interpreted as an URL by the actual chromium binary. Easy repro: 1. Set user's CHROMIUM_FLAGS with an argument containing spaces, eg: $ echo 'CHROMIUM_FLAGS=--user-agent="A B C"' > .chromium-browser.init 2. Run chromium: $ /usr/bin/chromium-browser 3. See 2 extra open tabs, one trying to open URL 'B', the other 'C'. The cause for this funny behavior is the lack of quotes around $CHROMIUM_FLAGS in the script installed in /usr/bin/chromium-browser -- it calls $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@" by the end of the script. I've tried working around it but couldn't, no amount of escaping and extra quotes seems to help if it's called like that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1514484/+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 1625517] Re: Clicking inside address bar does not update PRIMARY buffer (middle-mouse clipboard)
Reported upstream: https://bugs.chromium.org/p/chromium/issues/detail?id=1365943 -- 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/1625517 Title: Clicking inside address bar does not update PRIMARY buffer (middle- mouse clipboard) Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: When I click in the address bar once, the entire URL is selected. In most other applications, this is an indicator that my PRIMARY buffer [1] has been updated with the full URL. However, when I MMB-paste, the previous contents of the buffer appear. This has tripped me up on many occasions. Steps to reproduce: 1: Open a text editor, or any other recepticle for pasted text. 2: Select some text on a page. 3: Middle-click in the text editor, and verify that it's the text you selected in step 2. 4: Click the address bar in Chromium. The URL is highlighted. 5: Middle-click in the text editor again. 6: Hit Ctrl+z. Frustratedly go back to your browser. Click the address bar once, then again to deselect everything. Then drag or triple-click to select all. 7: Middle-click in the text editor again. Now it works. Expected results: In step 5, the full URL of the page you were visiting should have appeared. However, it's still the text you selected in step 2. I'm using Chromium version 52.0.2743.116 Built on Ubuntu , running on Ubuntu 16.04 (64-bit) [1]: I'm not shouting, this is what it's called. It's also known as the "middle-mouse clipboard". See also https://tronche.com/gui/x/icccm/sec-2.html#s-2.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1625517/+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 1625517] Re: Clicking inside address bar does not update PRIMARY buffer (middle-mouse clipboard)
** Changed in: firefox (Ubuntu) Status: New => Confirmed ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Low -- 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/1625517 Title: Clicking inside address bar does not update PRIMARY buffer (middle- mouse clipboard) Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: When I click in the address bar once, the entire URL is selected. In most other applications, this is an indicator that my PRIMARY buffer [1] has been updated with the full URL. However, when I MMB-paste, the previous contents of the buffer appear. This has tripped me up on many occasions. Steps to reproduce: 1: Open a text editor, or any other recepticle for pasted text. 2: Select some text on a page. 3: Middle-click in the text editor, and verify that it's the text you selected in step 2. 4: Click the address bar in Chromium. The URL is highlighted. 5: Middle-click in the text editor again. 6: Hit Ctrl+z. Frustratedly go back to your browser. Click the address bar once, then again to deselect everything. Then drag or triple-click to select all. 7: Middle-click in the text editor again. Now it works. Expected results: In step 5, the full URL of the page you were visiting should have appeared. However, it's still the text you selected in step 2. I'm using Chromium version 52.0.2743.116 Built on Ubuntu , running on Ubuntu 16.04 (64-bit) [1]: I'm not shouting, this is what it's called. It's also known as the "middle-mouse clipboard". See also https://tronche.com/gui/x/icccm/sec-2.html#s-2.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1625517/+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
