[Desktop-packages] [Bug 1967632]
(In reply to Olivier Tilloy from comment #1) > (from > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1843392/comments/1) > > The proposed approach to solve this that was discussed with the Ubuntu > security team is: > - stage common PKCS modules in the snap > - add a layout for `/usr/lib/pkcs11` pointing to a writeable area of the > snap (e.g. `$SNAP_USER_DATA/.local/lib`) > - on first run, copy the common PKCS modules to that writeable area > - document that custom modules (and their dependencies?) should be manually > copied to that directory > - create a new interface (not auto-connected, that's okay) for access to > `/var/run/pcscd/pcscd.comm` > > I'm not familiar with how smart card readers work though, so feedback and > suggestions are welcome. Why can't the snap package be configured to just let access to /var/run/pcscd/pcscd.comm? The PKCS#11 libs are normally platform/distribution dependent, so you can't just include it in a snap package hoping this will works anywhere. Dependencies are more platform dependent, 1 over all: libpcsclite.so.1 library shall match the protocol version of his server, you can't just bring it in the snap packages and hope it works. It looks like Snap is by now very immature technology to run the default version of FF on Ubuntu. -- 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/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+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 1973306] Re: packages freezes on authentification with Wayland
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1973306 Title: packages freezes on authentification with Wayland Status in software-properties package in Ubuntu: Expired Bug description: I want to report an issue which might well have been reported already, although i could not find it. A few weeks ago I switched from Ubuntu LTS 20.04 towards the LTS 22.04 with Wayland as default. I discovered that there is a sort of incompatibility between the software-properties-package and the Wayland protocol, which occurs systematically and never occurs when switching back to Xorg. When one tries to add or change a rule in ‘other software’ the application always freezes when the user is asked to authenticate. As soon a one cancels the authentification procedure it unfreezes almost immediately, but freezes again when the user retries to complete the adding or alteration procedure. As said, this error never occurs if the user switches back to an Xorg session. See screenshot: the window with the communication 'software & updates does not respond' and with the choice to close or to wait is hidden behind the authentification window. I am not really sure whether this bug has to be reported as a security issue, but certainly the software-properties-package is of utmost importance for a stable and secure OS. My system: OS: Ubuntu 22.04 LTS x86_64 Kernel: 5.15.0-30-generic Uptime: 13 mins Packages: 1940 (dpkg), 17 (flatpak), Shell: bash 5.1.16 Resolution: 1920x1080 DE: GNOME 42.0 WM: Mutter WM Theme: Adwaita Theme: Adwaita [GTK2/3] Icons: Numix [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-10510U (8) @ 4.900GHz GPU: Intel CometLake-U GT2 [UHD Grap Memory: 2992MiB / 64007MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973306/+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 1989649] Re: GDM doesn't start after package updates
Also unassigning from gdm3 since that component has not changed in almost 5 months. ** Package changed: gdm3 (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1989649 Title: GDM doesn't start after package updates Status in Ubuntu: Incomplete Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1989649/+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 1973638] Re: gnome-shell 42 leaks tens of megabytes with every screenshot
** Changed in: gnome-shell (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: fixed-in-42.5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1973638 Title: gnome-shell 42 leaks tens of megabytes with every screenshot Status in GNOME Shell: Unknown Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Status in gjs source package in Jammy: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: [Impact] gnome-shell's memory usage grows by tens of megabytes with every screenshot. A few screenshots make it 100MB larger and a few dozen screenshots make it 1GB larger. [Test Plan for GNOME Shell Fix] TODO [Test Plan for GJS Fix] 1. Log into gnome-shell. 2. Measure its real memory usage: grep RSS /proc/`pidof gnome-shell`/status 3. Take 20 full screen screenshots by pressing PrtScn each time. No need to save them anywhere. 4. Measure the memory usage again. Expected: Memory usage grows a little but growth does not exceed a few hundred megabytes. It should level off after a while and sometimes even shrink due to garbage collection. Observed: Memory usage grows without bounds, easily exceeding 1GB after about 20 screenshots (depending on screen resolution). It never shrinks significantly. [Where problems could occur] Since the fix affects GJS, problems could occur in any part of gnome- shell. [Other Info] This leak requires multiple fixes to minimize the memory usage. For the moment we are only aiming to fix the main GJS portion of the bug that allows memory usage to exceed 1GB. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1973638/+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 1989649] [NEW] GDM doesn't start after package updates
Public bug reported: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1989649 Title: GDM doesn't start after package updates Status in gdm3 package in Ubuntu: New Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1989649/+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 1989582] Re: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1989582 Title: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze Status in GNOME Shell: New Status in mutter package in Ubuntu: In Progress Bug description: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989582/+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 1989590] Re: Can't click on Dash items if status drop-down is shown
I can't seem to reproduce the "nothing happens" part in kinetic. For me the active popover closes as expected. > Expected: > 1. the system status drop-down goes away <= Already works > 2. the clicked item is activated <= Matter of opinion, not true in > traditional GUI design. But it will work on the second click. Can you attach a video of the problem you see? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1989590 Title: Can't click on Dash items if status drop-down is shown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps: 1. open any of the system status drop-downs 2. click on any Dash item Expected: 1. the system status drop-down goes away 2. the clicked item is activated Current: 1. nothing happens ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 16:49:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989590/+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 1989632] [NEW] Ctrl+Home shortcut selects first tab instead of going to top of document
Public bug reported: In Gnome Text Editor, when there are several tabs, the Ctrl+Home (resp. Ctrl+End) shortcuts navigate to the first (resp. last) tab instead of going to the top (resp. bottom) of the current document. When only one document is open (no tabs), the shortcuts work as expected (and as documented in the shortcuts window). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-text-editor 42.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Sep 14 21:48:03 2022 InstallationDate: Installed on 2018-12-14 (1370 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-text-editor UpgradeStatus: Upgraded to kinetic on 2022-09-02 (12 days ago) ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/1989632 Title: Ctrl+Home shortcut selects first tab instead of going to top of document Status in gnome-text-editor package in Ubuntu: New Bug description: In Gnome Text Editor, when there are several tabs, the Ctrl+Home (resp. Ctrl+End) shortcuts navigate to the first (resp. last) tab instead of going to the top (resp. bottom) of the current document. When only one document is open (no tabs), the shortcuts work as expected (and as documented in the shortcuts window). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-text-editor 42.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Sep 14 21:48:03 2022 InstallationDate: Installed on 2018-12-14 (1370 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-text-editor UpgradeStatus: Upgraded to kinetic on 2022-09-02 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1989632/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
We're seeing the same behavior with Dell Precision 3600 series desktops and HID Global OMNIKEY 3x21 Smart Card Readers We did not encounter the issue with 18.04 or 20.04, only in 22.04. sudo systemctl enable pcscd.socket does not seem to resolve the issue for us sudo systemctl start pcscd.service must be run after every reboot, we haven't seen any solution that persists a reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1983794] Re: Evolution not deleting autosave files
This bug **is** the tracker bug for the issue we believe was triggered
by libcanberra.
--
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 1983794] Re: Evolution not deleting autosave files
Can you cite the bug report on the libcanberra package which relates to
this issue? There are LOTS of them.
FWIW, the only component of the several components of the evolution
suite which EXPLICITLY depends on libcanberra (ldd |grep canberra)
is /usr/libexec/evolution-data-server/evolution-alarm-notify. Disabling
the loading of this module by renaming it does NOT fix the problem, so
if the problem is indeed in libcanberra then it must be used implicitly
by some other part of the suite.
or else something much more esoteric is going on :)
--
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 1760849] Re: Login screen appears on only one monitor and it's not the one I want
The problem with the workaround/fix is that that fix can and will get overwritten by newer versions of GDM3. That just happened to me and I had a hard time figuring out how to fix it until I came across this again... -- 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/1760849 Title: Login screen appears on only one monitor and it's not the one I want Status in GNOME Shell: Unknown Status in gnome-control-center package in Ubuntu: Opinion Status in gnome-shell package in Ubuntu: Triaged Bug description: Upstream bugs: https://gitlab.gnome.org/GNOME/gdm/issues/168 https://gitlab.gnome.org/GNOME/gdm/issues/183 https://gitlab.gnome.org/GNOME/gdm/issues/195 https://gitlab.gnome.org/GNOME/gdm/issues/319 https://gitlab.gnome.org/GNOME/gdm/issues/372 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3867 The Ubuntu login screen is tiled on all displays, not mirrored, making it nearly impossible to login when using an external monitor if the laptop screen is not visible. There appears to be no available control to alter the display settings of the login screen. Prior to bionic, the controls followed the mouse onto different displays so you could login by giving the mouse a swipe to the right to get the controls to appear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 22:13:53 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1760849/+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 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
This bug was fixed in the package poppler - 0.62.0-2ubuntu2.14 --- poppler (0.62.0-2ubuntu2.14) bionic-security; urgency=medium * SECURITY REGRESSION: Adding missing install header - debian/patches/0001-Install-goo-GooCheckedOps.h.patch: this add goo/GooCheckedOps.h to the CMakeLists.txt in order to it be distributed in the libpoppler-private-dev that was missing in the previous fix for CVE-2022-38784. (LP: #1989515) -- Leonidas Da Silva Barbosa Wed, 14 Sep 2022 13:46:18 -0300 ** Changed in: poppler (Ubuntu) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-38784 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: Fix Released Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1989626] [NEW] UIFe: fonts-noto-color-emoji & other updates for Unicode 15
Public bug reported: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. We also need to update glib and pango for the new release so that new composite emoji like "pink heart" display correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There isn't an upstream pango merge request or issue but I think it will be needed. We also need new versions of unicode-data, node-unicode, and gucharmap. There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. ** Affects: fonts-noto-color-emoji (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic ** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. We also need to update glib and pango for the new release so that new composite emoji like "pink heart" display correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There isn't an upstream pango merge request or issue but I think it will be needed. We also need new versions of unicode-data, node-unicode, and gucharmap. There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. + I don't have packaging ready for these changes yet but I'm requesting + the UIFe early. + 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html Email to Docs List: not done yet I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. ** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. We also need to update glib and pango for the new release so that new composite emoji like "pink heart" display correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There isn't an upstream pango merge request or issue but I think it will be needed. We also need new versions
[Desktop-packages] [Bug 1982764] Re: Peek does not work under Wayland ?
** Also affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1982764 Title: Peek does not work under Wayland ? Status in Peek: New Status in gnome-screenshot package in Ubuntu: New Status in peek package in Ubuntu: New Bug description: Hi, Ubuntu 22.04 Jammy django@ASGARD:~$ sudo lshw -c video [sudo] Mot de passe de django : *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabricant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 nom logique: /dev/fb0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom fb configuration : depth=32 driver=i915 latency=0 resolution=1920,1080 ressources : irq:32 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d django@ASGARD:~$ using peek from repository ( 1.5.1+git20211214-1 amd64 ) I can't get it to work under Wayland session ( peek window opens but no recording at all ). Under Xorg session it almost works but does not "capture" mouse- cursor. To manage notifications about this bug go to: https://bugs.launchpad.net/peek/+bug/1982764/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
Oh, I DO have sound in the speakers, BT high def (A2DP) audio too... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GU_G731GU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+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 1989295] Re: Mouse cursor goes to 0, 0 coordinates on a full screen capture
** Also affects: peek (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1989295 Title: Mouse cursor goes to 0,0 coordinates on a full screen capture Status in gnome-screenshot package in Ubuntu: New Status in peek package in Ubuntu: New Bug description: Hi, Ubuntu 22.04 here. I've installed gnome-screenshot as the default capture tool does not offer delay when needing to capture secondary menus ( those under right click or coming from panels, or coming from application menu… ) My issue with gnome-screenshot is : it is unable to capture mouse-cursor ! Anytime I try a « full screen » capture with delay + mouse cursor, mouse cursor shows at 0,0 coordinate on the resulting picture. Be it on Xorg or Wayland. Always reproducible. ( Other applications are unable to « capture » mouse cursor, ie peek, so maybe not specific to gnome-screenshot ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1989295/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
$ lspci | grep -i audio 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1) *** Is there REALLY Realtek audio hardware in here too? *** or just a partly initialized driver due to the missing hardware? Looks as that driver(?) in linux-modules-extra-(uname -r)... $ apt-file find snd-hda-intel | grep $(uname -r) linux-modules-extra-5.13.0-52-generic: /lib/modules/5.13.0-52-generic/kernel/sound/pci/hda/snd-hda-intel.ko $ apt-file find snd-hda-intel | wc -l 576 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.6 dmi.modalias:
[Desktop-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
$ cat /sys/class/sound/hwC0D0/vendor_name Realtek -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GU_G731GU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
Hmm... $ cat /sys/class/sound/hwC0D0/chip_name ALC294 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GU_G731GU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+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] Re: [snap] vaapi chromium no video hardware decoding
Desktop: wayland
OS: Kinetic
CPU: i5-12600k
GPU: Intel Alderlake_s (Gen12)
I hit this error: vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode)
After which chromium seems to fall back to ffmpeg.
[135904:14:0913/135753.793304:INFO:decoder.cc(41)] DecryptingVideoDecoder
[135863:135986:0913/135753.794331:INFO:decoder.cc(65)] VDAVideoDecoder
[135904:14:0913/135753.795630:INFO:decoder.cc(65)] VDAVideoDecoder
[135904:14:0913/135753.795678:INFO:decoder.cc(65)] VDAVideoDecoder
[135863:135863:0913/135753.809617:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[135863:135863:0913/135753.809730:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[135863:135863:0913/135753.811544:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[135863:135863:0913/135753.811593:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[135904:14:0913/135753.811795:INFO:decoder.cc(32)] VpxVideoDecoder
[135904:14:0913/135753.811863:INFO:decoder.cc(44)] Dav1dVideoDecoder
[135904:14:0913/135753.812884:INFO:decoder.cc(29)] FFmpegVideoDecoder
[135904:14:0913/135753.812955:INFO:decoder.cc(29)] FFmpegVideoDecoder
[135744:135875:0913/135755.767907:ERROR:udev_watcher.cc(98)] Failed to begin
udev enumeration.
Launched with:
$ chromium --enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist --disable-
gpu-driver-bug-workaround --ozone-platform=wayland Downloads/big-buck-
bunny-1080p-60fps-30sec.mp4
--
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`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
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 candidate/hwacc,
which is [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 :
[Desktop-packages] [Bug 1973734] [pulseaudio/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1973734 Title: FTBFS on riscv64 in focal Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Bug description: [Impact] * FTBFS on riscv64 in focal in unittest of volume test * Disable that unit test, as later releases do not run unittests on riscv64, and it's better to have up to date pulseaudio on riscv64 (with many security fixes), even if it doesn't completely correctly work. [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * volume-test probably indicates that one can't set volume correctly on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1973734/+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 1750199] Re: Blurry Icons on HighDPI
** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=144583 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1750199 Title: Blurry Icons on HighDPI Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: In Progress Bug description: On bionic with libreoffice 6.0 from proposed new and subjectively better icons are shipped which is great. However, they still are rather blurry on a HighDPI screen. Can we patch the package to provide a higher resolution iconset? To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1750199/+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 1750199] Re: Blurry Icons on HighDPI
** Changed in: libreoffice (Ubuntu) Status: Confirmed => In Progress ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1750199 Title: Blurry Icons on HighDPI Status in libreoffice package in Ubuntu: In Progress Bug description: On bionic with libreoffice 6.0 from proposed new and subjectively better icons are shipped which is great. However, they still are rather blurry on a HighDPI screen. Can we patch the package to provide a higher resolution iconset? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750199/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
--- audio in the output of lshw --- *-multimedia description: Audio device product: TU116 High Definition Audio Controller vendor: NVIDIA Corporation physical id: 0.1 bus info: pci@:01:00.1 version: a1 width: 32 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:17 memory:a508-a5083fff --- *-multimedia description: Audio device product: Cannon Lake PCH cAVS vendor: Intel Corporation physical id: 1f.3 bus info: pci@:00:1f.3 version: 10 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=snd_hda_intel latency=32 resources: irq:150 memory:a5418000-a541bfff memory:a510-a51f --- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312
[Desktop-packages] [Bug 1871027] Re: xserver-xorg-video-amdgpu list firmware-amd-graphics as a suggested package
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1871027 Title: xserver-xorg-video-amdgpu list firmware-amd-graphics as a suggested package Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: In xserver-xorg-video-ati the suggested firmware-amd-graphics was dropped because the firmware is part of the linux-firmware package in Ubuntu and since I just ran up on it I thought I would report it so that people are not searching for firmware-amd-graphics for no reason at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1871027/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
--- seen in dmesg --- [5.815777] Bluetooth: hci0: Firmware revision 0.1 build 26 week 11 2020 [5.881465] NET: Registered protocol family 38 [9.328954] wlo1: authenticate with 94:18:65:08:59:ae [9.338666] wlo1: send auth to 94:18:65:08:59:ae (try 1/3) [9.382307] wlo1: authenticated [9.384831] wlo1: associate with 94:18:65:08:59:ae (try 1/3) [9.389564] wlo1: RX AssocResp from 94:18:65:08:59:ae (capab=0x431 status=0 aid=3) [9.392938] wlo1: associated [9.505267] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready [ 64.717314] snd_hda_intel :00:1f.3: couldn't bind with audio component [ 64.772851] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 64.772856] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 64.772858] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 64.772860] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 64.772862] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 64.772863] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [ 64.772865] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 65.227287] snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel HDMI/DP codec [ 65.231312] hdaudio hdaudioC0D2: Unable to configure, disabling [ 65.232125] input: HDA Intel PCH Headset Mic as /devices/pci:00/:00:1f.3/sound/card0/input21 [ 65.232353] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input22 [ 481.066720] kauditd_printk_skb: 22 callbacks suppressed [ 481.066723] audit: type=1400 audit(1663175820.795:34): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=2107 comm="cups-browsed" capability=23 capname="sys_nice" [ 482.476639] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 482.476642] usb usb3: root hub lost power or was reset [ 482.476643] usb usb4: root hub lost power or was reset [ 482.598315] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 482.687635] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 484.946351] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 485.054903] rfkill: input handler disabled [ 491.657064] Bluetooth: RFCOMM TTY layer initialized [ 491.657070] Bluetooth: RFCOMM socket layer initialized [ 491.657073] Bluetooth: RFCOMM ver 1.11 [ 491.886727] rfkill: input handler enabled [ 492.013259] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 493.174837] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 493.434596] rfkill: input handler disabled --- end of dmsg --- " autoconfig for ALC294" => $ sudo lshw | grep ALC294 | wc -l 0 $ --- https://www.google.com/search?q=ALC294+%2Bg731 -> notably "g731" doesn't seem to be present in the google-search for ALC294 https://www.google.com/search?q=%2BALC294+%2Bg731 => no match on g731 Why is there an attempt to initialize this non-existant hardware? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill:
[Desktop-packages] [Bug 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
Ok, i did find the issue -Thanks Security folks - and I'm issuing a security regression update. Thanks. ** Changed in: poppler (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: In Progress Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1989602] [NEW] Delay in updating charge status in Ubuntu 22.04 LTS
Public bug reported: I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS. When plugging in the charger, the current charge status in the top bar and Settings shows 'Not Charging' for a few minutes and then shows that the system is charging normally. When unplugging the charger the same happens; the charge status shows 'Not Charging' for a few minutes, and then shows the correct charge status. Normally, the change in power status should be instantaneous. In short, there is a delay in the OS in showing the current charge status. Upon further research, it was found that the 'upower' service is to blame; it polls every two minutes(i.e., it refreshes the charge status every two minutes); causing a delay in charge status. This is further compounded by the fact that restarting upower service, or the system as a whole makes the system to show the correct charge status. However, I did not have this problem on another system, a HP Pavilion x360 14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS. There, the power status behaves normally with no delays whatsoever. Please look into this issue and fix this bug as soon as possible. One suggestion would be to increase the polling frequency of upower from 2 mins. to something lesser, so that the charge status shows correctly. upower version: UPower client version 0.99.17 UPower daemon version 0.99.17 OS: Description:Ubuntu 22.04.1 LTS Release:22.04 Kernel: Linux 5.15.0-47-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: upower 0.99.17-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 20:41:16 2022 InstallationDate: Installed on 2022-09-12 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1989602 Title: Delay in updating charge status in Ubuntu 22.04 LTS Status in upower package in Ubuntu: New Bug description: I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS. When plugging in the charger, the current charge status in the top bar and Settings shows 'Not Charging' for a few minutes and then shows that the system is charging normally. When unplugging the charger the same happens; the charge status shows 'Not Charging' for a few minutes, and then shows the correct charge status. Normally, the change in power status should be instantaneous. In short, there is a delay in the OS in showing the current charge status. Upon further research, it was found that the 'upower' service is to blame; it polls every two minutes(i.e., it refreshes the charge status every two minutes); causing a delay in charge status. This is further compounded by the fact that restarting upower service, or the system as a whole makes the system to show the correct charge status. However, I did not have this problem on another system, a HP Pavilion x360 14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS. There, the power status behaves normally with no delays whatsoever. Please look into this issue and fix this bug as soon as possible. One suggestion would be to increase the polling frequency of upower from 2 mins. to something lesser, so that the charge status shows correctly. upower version: UPower client version 0.99.17 UPower daemon version 0.99.17 OS: Description: Ubuntu 22.04.1 LTS Release: 22.04 Kernel: Linux 5.15.0-47-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: upower 0.99.17-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 20:41:16 2022 InstallationDate: Installed on 2022-09-12 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1989602/+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 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
Hi, Could you please provide with any steps in how to reproduce it? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: New Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1972914] Re: frequent 15-sec guest freeze with ubuntu 22.04 host and guest
Confirming this report on: Ubuntu 22.04 Host with: Lenovo Server Dual 16 Core CPUs (with hyperthreading == 64 CPUS) 384GB RAM Ubuntu 22.04 Libvirt 8.0.0 QEMU API 8.0.0 Hyervisor QEMU 6.2.0 Ubuntu 22.04 Desktop Guest with: Q35 VM with OVMF 4 x CPU 8192MB RAM Trying to run "snap Eclipse". UI performance is so bad that it is unusable. I have testing the same software configuration with Ubuntu 20.04 Quest with only 2 CPU/4096MB RAM and performance is very snappy and no issues. On my 22.04 quest I also have a lot of qxl errors in my kern.log: sudo grep 'drm:qxl_alloc' kern.log Sep 11 21:08:36 graphit kernel: [ 103.590807] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO Sep 11 21:11:09 graphit kernel: [ 256.682227] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO Sep 11 21:11:42 graphit kernel: [ 289.705678] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO Sep 11 21:12:00 graphit kernel: [ 307.625499] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO Sep 11 21:12:18 graphit kernel: [ 325.801386] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO ... ... I updated libvert vgamem as per your finding and now have workable VM again. So while there is work around I believe there should be some fix in libvirt/qemu to ensure that VM is configured with vgamem value that results in working VM. I have posted my testing in details here: https://tips.graphica.com.au/ubuntu-eclipse-snap-is-broken/ Thank you for posting the bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1972914 Title: frequent 15-sec guest freeze with ubuntu 22.04 host and guest Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: I'm running a new installation of Ubuntu 22.04 Desktop on a Thinkpad T450s (core i5-5200, 2 cores / 4 vCPUs, 12 GB memory). Using the virt- manager GUI, I performed what I believe is a simple, plain-vanilla installation of an Ubuntu 22.04 guest running under qemu/kvm with 2 vCPUs and 4 GB memory. I'm seeing very frequent, 15-second freezes of the guest. When it happens, the guest is completely unresponsive. After about 15 seconds, it works normally again, until the next freeze. The duration of the freeze appears to be the same every time. The guest isn't doing much - just open the calculator app and click number buttons. The freeze doesn't happen if I don't interact with the guest (just leave the system monitor running in the guest, so I can see that it's not frozen). I observe the freeze when I have 2 of the 4 vCPUs dedicated to the guest. I do NOT observe it when I have only one vCPU dedicated to the guest. Both the host and guest are using only a small fraction of the memory available to them. When the problem happens, the host indicates that CPU usage is very low across all vCPUs. The host appears to be operating normally when the guest is frozen. I see the following pair of lines in the guest syslog every time the freeze occurs (and only when the freeze occurs): May 10 13:48:40 qemu-jammy kernel: [ 144.259799] qxl :00:01.0: object_init failed for (8298496, 0x0001) May 10 13:48:40 qemu-jammy kernel: [ 144.259819] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO I don't see anything in the host syslog that correlates with the freeze. If I choose "Virtio" in the Video drop-down in the virt-manager GUI, with "3D acceleration" UNchecked, the guest works fine, and the freeze never happens. Unfortunately, that loses fractional scaling, which is important to me. If I check "3D acceleration," the guest won't boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1972914/+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 1989590] [NEW] Can't click on Dash items if status drop-down is shown
Public bug reported: Steps: 1. open any of the system status drop-downs 2. click on any Dash item Expected: 1. the system status drop-down goes away 2. the clicked item is activated Current: 1. nothing happens ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 16:49:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1989590 Title: Can't click on Dash items if status drop-down is shown Status in gnome-shell package in Ubuntu: New Bug description: Steps: 1. open any of the system status drop-downs 2. click on any Dash item Expected: 1. the system status drop-down goes away 2. the clicked item is activated Current: 1. nothing happens ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 16:49:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989590/+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 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
** Changed in: poppler (Ubuntu) Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: New Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies
The description of the patch explains why the current behavior is buggy and not just different in a way users would be relying on the difference of behavior. It's not that it works differently, it is that it reports wrong information. The patch didn't apply directly so I've adapted it and verified that a build of the package with it matched the new expected behavior before uploading. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: Incomplete Bug description: = Impact = the ping statistics are incorrect when dealing with truncated packets = Test case = $ ping -c 1 -s 1200 8.8.8.8 should list truncated replies and received packets = Regression potential = the changes are limited to the ping source any regression would impact that utility, check that responses are correctly handled and statistics reflecting what is expected -- Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1989587] [NEW] Cannot print to autodiscovered printers
Public bug reported: I have issues when trying to print on autodiscovered printers. In some cases, cups reports a "permission denied". In other cases, the local queue is not created at all, so that it is impossible to print. However, these printers do appear in the kde print dialog for applications like okular, etc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups-browsed 1.28.15-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 14 15:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (941 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/VG_NVMe-root ro quiet splash zswap.enabled=1 vt.handoff=7 SourcePackage: cups-filters UpgradeStatus: Upgraded to jammy on 2022-06-03 (103 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER modified.conffile..etc.cups.cups-browsed.conf: [modified] mtime.conffile..etc.cups.cups-browsed.conf: 2022-09-14T15:52:48.888330 ** Affects: cups-filters (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 cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1989587 Title: Cannot print to autodiscovered printers Status in cups-filters package in Ubuntu: New Bug description: I have issues when trying to print on autodiscovered printers. In some cases, cups reports a "permission denied". In other cases, the local queue is not created at all, so that it is impossible to print. However, these printers do appear in the kde print dialog for applications like okular, etc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups-browsed 1.28.15-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 14 15:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (941 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/VG_NVMe-root ro quiet splash zswap.enabled=1 vt.handoff=7 SourcePackage: cups-filters UpgradeStatus: Upgraded to jammy on 2022-06-03 (103 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER modified.conffile..etc.cups.cups-browsed.conf: [modified] mtime.conffile..etc.cups.cups-browsed.conf: 2022-09-14T15:52:48.888330 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1989587/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies
I'm not doubting that the revert was correct for upstream. But we have a different context in a stable release, where users may be relying on behaviours that upstream are at liberty to change in their main development branch, but we are not in our stable releases. Further, we can't just assume that what is correct for them in their code base is correct for us to cherry-pick to our stable release that holds a previous version of the code base. Somebody needs to spend time to ensure this is safe. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: Incomplete Bug description: = Impact = the ping statistics are incorrect when dealing with truncated packets = Test case = $ ping -c 1 -s 1200 8.8.8.8 should list truncated replies and received packets = Regression potential = the changes are limited to the ping source any regression would impact that utility, check that responses are correctly handled and statistics reflecting what is expected -- Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1848210] Re: ghostscript: ensure update of cups-filter
It looks like this wasn't needed in practice; marking as Won't Fix. ** Changed in: ghostscript (Ubuntu Xenial) Status: In Progress => Won't Fix ** Changed in: ghostscript (Ubuntu Xenial) Importance: Medium => Undecided ** Changed in: ghostscript (Ubuntu Xenial) Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned) ** Changed in: ghostscript (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: ghostscript (Ubuntu Bionic) Importance: Medium => Undecided ** Changed in: ghostscript (Ubuntu Bionic) Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in cups-filters package in Ubuntu: Invalid Status in ghostscript package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: Invalid Status in ghostscript source package in Xenial: Won't Fix Status in cups-filters source package in Bionic: Invalid Status in ghostscript source package in Bionic: Won't Fix Bug description: [Impact] * After an update of ghostscript but not cups-filters users may hit errors printing PDF files (LP#1828401). * This is possible as Landscape does not consider the -security pocket (has both ghostscript/cups-filters) but rather USN notices and ghostscript had a notice [0]. The regression on cups-filters was identified later, and doesn't warrant a USN notice. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. Per Debian Policy [1]: """ Normally a Breaks entry will have an “earlier than” version clause; such a Breaks is introduced in the version ... [that] reveals a bug in earlier versions of the broken package ... This use of Breaks will inform higher-level package management tools that the broken package must be upgraded before the new one. """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. * This doesn't fix the current situation with Landscape and USNs so this same problem might still occur again, but at least it is already in place on future updates. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. [Other Info] * This is only required in Xenial and Bionic. * Trusty doesn't have the ghostscript update that causes the problem. * Disco/Eoan have the cups-filters fix that it requires (1.22.5+). [Links] [0] https://usn.ubuntu.com/3970-1/ [1] https://www.debian.org/doc/debian-policy/ch-relationships.html#packages-which-break-other-packages-breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1848210/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies
@Robie, the patch description has details on the change. The github report also discuss why the patch was broken and not just doing what is intended and why the revert is right. I'm not involved in iputils and will not be able to provide more information that was in there. Note that the revert is part of 22.04. I was mostly trying to help landing a fix we were getting request on. I'm fine updating the testcase if that's enough to unblock the SRU but otherwise please reject my upload, I'm not wanting to spend the time needed to prove that upstream can be trusted on that one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: Incomplete Bug description: = Impact = the ping statistics are incorrect when dealing with truncated packets = Test case = $ ping -c 1 -s 1200 8.8.8.8 should list truncated replies and received packets = Regression potential = the changes are limited to the ping source any regression would impact that utility, check that responses are correctly handled and statistics reflecting what is expected -- Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies
This is definitely a bug that we want to fix in Focal. But is this particular code change the correct way to do it? Won't reverting this commit regress the fix that was introduced by the commit in the first place? I think this needs a proper analysis of the possible implications for unaffected users, please, rather than just blindly cherry-picking the revert from upstream. I think maybe bug 1551020 would be reintroduced by this upload, for example? The test plan should also include verifying regular use cases that might be impacted by this code change are not regressed, not just that this particular bug is fixed. ** Changed in: iputils (Ubuntu Focal) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: Incomplete Bug description: = Impact = the ping statistics are incorrect when dealing with truncated packets = Test case = $ ping -c 1 -s 1200 8.8.8.8 should list truncated replies and received packets = Regression potential = the changes are limited to the ping source any regression would impact that utility, check that responses are correctly handled and statistics reflecting what is expected -- Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies
I checked that jammy and later indeed has the same commit reverted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: Incomplete Bug description: = Impact = the ping statistics are incorrect when dealing with truncated packets = Test case = $ ping -c 1 -s 1200 8.8.8.8 should list truncated replies and received packets = Regression potential = the changes are limited to the ping source any regression would impact that utility, check that responses are correctly handled and statistics reflecting what is expected -- Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1551020] Re: IpUtils Ping can be in wait forever
Upstream bug: https://github.com/iputils/iputils/pull/67 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1551020 Title: IpUtils Ping can be in wait forever Status in iputils package in Ubuntu: Expired Bug description: Ping is using round trip time from previous incoming echo response packet to determine max waittime for next packet, but the validation of the value read from incoming echo response packet is poor. It only checks for non-negative values. To reproduce the Bug: Step 1: Apply the following diff to the Ping command- (this simulates the condition that triptime value read from incoming echo response was some arbitrary large value)- diff -r iputils/ping_common.c iputils_ping_hang_repro/ping_common.c 709c709,711 < triptime = tv->tv_sec * 100 + tv->tv_usec; --- > /*SNAP: To repro Ping hang, set this value to some large long value. Since this is read from */ > /* incoming echo reply and not validated for 0 or too large, this will cause hang/long wait. > /* triptime = tv->tv_sec * 100 + tv->tv_usec; */ > triptime = 1000123456789; /tmp/diff.out (END) Step 2: Run the following ping command targeted at a host that is at first successfully replying to the Ping echo requests, but at some point during the execution (before the last ping echo request) take the target offline(to trigger the waittime). This will cause Ping to set the waittime to tmax which is 2 X the max RTT which we just set to a very large value. sudo ./ping -c 10 -i 0.5 $TARGET_IP > /tmp/out.log AS A RESULT, 1. The Ping will keep running for a few hundred years, no big deal. In strace there will be a periodic recvmsg to check for response every few ms, something like this- Process 11373 attached - interrupt to quit ... recvmsg(3, 0x7ffed06dc650, 0) = -1 EAGAIN (Resource temporarily unavailable) recvmsg(3, 0x7ffed06dc650, 0) = -1 EAGAIN (Resource temporarily unavailable) recvmsg(3, 0x7ffed06dc650, 0) = -1 EAGAIN (Resource temporarily unavailable) ... 2. In the /proc/timer_list file I see a large value for the process' timer- ... #14: <>, it_real_fn, S:01, hrtimer_start, ping/11373 # expires at 611433835413-611433835413 nsecs [in 2000179546163581 to 2000179546163581 nsecs] ... So we can see that when a large timeval is read from the echo response, it is not validated. Possible causes for invalid timeval values could be: Malicious destination, buggy OS, Malformed packets, interference with echo response belonging to "traceroute" command but had the same ID and Seq No. Impact- Ping runs forever. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1551020/+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 1987678] Re: Backport jansson 2.14 to jammy from kinetic
** Changed in: jansson (Ubuntu Jammy) Assignee: (unassigned) => Loïc Minier (lool) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jansson in Ubuntu. https://bugs.launchpad.net/bugs/1987678 Title: Backport jansson 2.14 to jammy from kinetic Status in jansson package in Ubuntu: Fix Released Status in jansson source package in Jammy: In Progress Bug description: [Impact] * jansson 2.13 has a symbol conflict with json-c library.(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 & https://github.com/akheron/jansson/issues/523). So an application is linking to both jansson and json-c, there will be 50% of chance that it reference to a wrong symbol, which need to SIGSEGV * In order to fix this issue, both json-c and jansson need to add symbol versioning. jansson library added this in 2.14(not yet in jammy) while json-c added in 0.15 (already in jammy) * And the affecting application should rebuild against the latest json-c and jansson libraries in order to have the correct symbol linked [Test Plan] * jansson is basically available in all of the cpu architecture. So the 1st test will be building in a personal ppa and see if it can be built in every platform. * Some of the library mentioned in the upstream issue checker can be used to verify the fix. But since I am working on a package in a private project which is hitting the issue. I am testing with my private packages(which is on arm64 platform) * Looking into the packages that depends on jansson. There are a large number of packages including network-manager. So I tried to pick 2 packages on my desktop to verify if there is regression 1. network-manager, since it is widely used in Ubuntu 2. emacs, since jansson is a JSON parser, so I pick an application that I can do some operation on JSON(e.g. formatting in emacs) [Where problems could occur] * jansson upstream is well maintained and there is also CI test job. jansson 2.14 is also packaged and maintained by Debian community. It is available for a few months already. So in general, the risk of regression is low in that perspective. * When looking into the changes between 2.13 and 2.14. There are changes in test coverage and some tidy up on the build scripts. The changes look safe but certainly there can be mistake and behaviour changes. But jansson do not depends on other packages and so this kind of regression on build script should be easily caught by test builds in different architecture and a simple integration test with package that depends on jansson. * On the library itself, it added symbol versioning to fix the bug and at the same time there are 3 new API added in 2.14. But these changes should be backward compatible. But since there is new symbols added, there can be new symbol conflict with other library but the impact should just be similar to the original bug that it is already conflict with json-c. There are alos misc fixes in like snprintf checking which looks to be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678/+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 1989582] Re: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1989582 Title: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze Status in GNOME Shell: New Status in mutter package in Ubuntu: Triaged Bug description: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989582/+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 1989582] [NEW] gnome-shell 43 (and mutter) Xorg sessions stutter and freeze
Public bug reported: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze. ** Affects: gnome-shell Importance: Unknown Status: New ** Affects: mutter (Ubuntu) Importance: Critical Status: Triaged ** Tags: kinetic performance ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5861 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5861 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5861 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1989582 Title: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze Status in GNOME Shell: New Status in mutter package in Ubuntu: Triaged Bug description: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989582/+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 1971602] Re: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: el subproceso nuevo paquete firefox script pre-installation devolvió el código de salida de error 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/1971602 Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: el subproceso nuevo paquete firefox script pre-installation devolvió el código de salida de error 1 Status in firefox package in Ubuntu: Confirmed Bug description: Updated from Ubuntu 21.10 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 29 13:08:39 2022 ErrorMessage: el subproceso nuevo paquete firefox script pre-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2018-05-25 (1440 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no se han encontrado cambios SourcePackage: firefox Title: package firefox 1:1snap1-0ubuntu2 failed to install/upgrade: el subproceso nuevo paquete firefox script pre-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to jammy on 2022-04-29 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971602/+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 1989572] Re: libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0
** Description changed: This maybe has to be reassigned to affect 'ddeb-retriever', but the web form doesn't allow setting it as package for reporting. 'libglib2.0-0' was updated in the bionic-updates repository, but 'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs repository: - # apt-cache policy libglib2.0-0 - libglib2.0-0: - Installed: 2.56.4-0ubuntu0.18.04.9 - Candidate: 2.56.4-0ubuntu0.18.04.9 - Version table: - *** 2.56.4-0ubuntu0.18.04.9 500 - 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2.56.1-2ubuntu1 500 - 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages + # apt-cache policy libglib2.0-0 + libglib2.0-0: + Installed: 2.56.4-0ubuntu0.18.04.9 + Candidate: 2.56.4-0ubuntu0.18.04.9 + Version table: + *** 2.56.4-0ubuntu0.18.04.9 500 + 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2.56.1-2ubuntu1 500 + 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages - # apt-cache policy libglib2.0-0-dbgsym - libglib2.0-0-dbgsym: - Installed: (none) - Candidate: 2.56.1-2ubuntu1 - Version table: - 2.56.1-2ubuntu1 500 - 500 http://ddebs.ubuntu.com bionic/main amd64 Packages + # apt-cache policy libglib2.0-0-dbgsym + libglib2.0-0-dbgsym: + Installed: (none) + Candidate: 2.56.1-2ubuntu1 + Version table: + 2.56.1-2ubuntu1 500 + 500 http://ddebs.ubuntu.com bionic/main amd64 Packages Due to this, the package 'libglib2.0-0-dbgsym' is not installable with apt-get: - # apt-get update && apt-get install libglib2.0-0-dbgsym - [...] - The following packages have unmet dependencies: - libglib2.0-0-dbgsym : Depends: libglib2.0-0 (= 2.56.1-2ubuntu1) but 2.56.4-0ubuntu0.18.04.9 is to be installed - E: Unable to correct problems, you have held broken packages. + # apt-get update && apt-get install libglib2.0-0-dbgsym + [...] + The following packages have unmet dependencies: + libglib2.0-0-dbgsym : Depends: libglib2.0-0 (= 2.56.1-2ubuntu1) but 2.56.4-0ubuntu0.18.04.9 is to be installed + E: Unable to correct problems, you have held broken packages. Using `--force-yes` or `--allow-downgrades` does not make any difference. These are the ddebs repositories in use: - # cat /etc/apt/sources.list.d/ddebs.list - deb http://ddebs.ubuntu.com bionic main restricted universe multiverse - deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse - deb http://ddebs.ubuntu.com bionic-proposed main restricted universe multiverse + # cat /etc/apt/sources.list.d/ddebs.list + deb http://ddebs.ubuntu.com bionic main restricted universe multiverse + deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse + deb http://ddebs.ubuntu.com bionic-proposed main restricted universe multiverse System is Ubuntu 18.04 Bionic: - # lsb_release -rd - Description:Ubuntu 18.04.6 LTS - Release:18.04 + # lsb_release -rd + Description:Ubuntu 18.04.6 LTS + Release:18.04 -- 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/1989572 Title: libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0 Status in glib2.0 package in Ubuntu: New Bug description: This maybe has to be reassigned to affect 'ddeb-retriever', but the web form doesn't allow setting it as package for reporting. 'libglib2.0-0' was updated in the bionic-updates repository, but 'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs repository: # apt-cache policy libglib2.0-0 libglib2.0-0: Installed: 2.56.4-0ubuntu0.18.04.9 Candidate: 2.56.4-0ubuntu0.18.04.9 Version table: *** 2.56.4-0ubuntu0.18.04.9 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.56.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages # apt-cache policy libglib2.0-0-dbgsym libglib2.0-0-dbgsym: Installed: (none) Candidate: 2.56.1-2ubuntu1 Version table: 2.56.1-2ubuntu1 500 500 http://ddebs.ubuntu.com bionic/main amd64 Packages Due to this, the package 'libglib2.0-0-dbgsym' is not installable with apt-get: # apt-get update && apt-get install libglib2.0-0-dbgsym [...] The following packages have unmet dependencies: libglib2.0-0-dbgsym : Depends: libglib2.0-0 (=
[Desktop-packages] [Bug 1989572] [NEW] libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0
Public bug reported: This maybe has to be reassigned to affect 'ddeb-retriever', but the web form doesn't allow setting it as package for reporting. 'libglib2.0-0' was updated in the bionic-updates repository, but 'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs repository: # apt-cache policy libglib2.0-0 libglib2.0-0: Installed: 2.56.4-0ubuntu0.18.04.9 Candidate: 2.56.4-0ubuntu0.18.04.9 Version table: *** 2.56.4-0ubuntu0.18.04.9 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.56.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages # apt-cache policy libglib2.0-0-dbgsym libglib2.0-0-dbgsym: Installed: (none) Candidate: 2.56.1-2ubuntu1 Version table: 2.56.1-2ubuntu1 500 500 http://ddebs.ubuntu.com bionic/main amd64 Packages Due to this, the package 'libglib2.0-0-dbgsym' is not installable with apt-get: # apt-get update && apt-get install libglib2.0-0-dbgsym [...] The following packages have unmet dependencies: libglib2.0-0-dbgsym : Depends: libglib2.0-0 (= 2.56.1-2ubuntu1) but 2.56.4-0ubuntu0.18.04.9 is to be installed E: Unable to correct problems, you have held broken packages. Using `--force-yes` or `--allow-downgrades` does not make any difference. These are the ddebs repositories in use: # cat /etc/apt/sources.list.d/ddebs.list deb http://ddebs.ubuntu.com bionic main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-proposed main restricted universe multiverse System is Ubuntu 18.04 Bionic: # lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1989572 Title: libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0 Status in glib2.0 package in Ubuntu: New Bug description: This maybe has to be reassigned to affect 'ddeb-retriever', but the web form doesn't allow setting it as package for reporting. 'libglib2.0-0' was updated in the bionic-updates repository, but 'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs repository: # apt-cache policy libglib2.0-0 libglib2.0-0: Installed: 2.56.4-0ubuntu0.18.04.9 Candidate: 2.56.4-0ubuntu0.18.04.9 Version table: *** 2.56.4-0ubuntu0.18.04.9 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.56.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages # apt-cache policy libglib2.0-0-dbgsym libglib2.0-0-dbgsym: Installed: (none) Candidate: 2.56.1-2ubuntu1 Version table: 2.56.1-2ubuntu1 500 500 http://ddebs.ubuntu.com bionic/main amd64 Packages Due to this, the package 'libglib2.0-0-dbgsym' is not installable with apt-get: # apt-get update && apt-get install libglib2.0-0-dbgsym [...] The following packages have unmet dependencies: libglib2.0-0-dbgsym : Depends: libglib2.0-0 (= 2.56.1-2ubuntu1) but 2.56.4-0ubuntu0.18.04.9 is to be installed E: Unable to correct problems, you have held broken packages. Using `--force-yes` or `--allow-downgrades` does not make any difference. These are the ddebs repositories in use: # cat /etc/apt/sources.list.d/ddebs.list deb http://ddebs.ubuntu.com bionic main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-proposed main restricted universe multiverse System is Ubuntu 18.04 Bionic: # lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1989572/+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 39136]
*** Bug 1787765 has been marked as a duplicate of this bug. *** -- 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/39136 Title: firefox should render unrecognized text/* as text/plain Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: The current program suggested to view certain filetypes (e.g. text/x-debian-source-package as send when visiting http://librarian.launchpad.net/1788684/usplash_0.1-33.dsc) is less. Perhaps gedit would be a more sensible choice? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/39136/+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 1989571] [NEW] Firefox apparmor profile : should allow python3.10 and further
Public bug reported: I'm using firefox package from https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ on ubuntu 22.04. In this release, python3 version is currently 3.10.4-0ubuntu2. But the profile only allow python3.0 to python3.9, and I have errors notifications the profile : grep python /etc/apparmor.d/usr.bin.firefox #include /usr/include/python2.[4567]/pyconfig.h r, /usr/local/lib/python3.[0-9]/dist-packages/ r, /usr/bin/python3.[0-9] mr, so I suggest the following patch (also attached) : --- usr.bin.firefox 2022-09-14 11:48:12.612062823 +0200 +++ usr.bin.firefox.new 2022-09-14 11:48:58.232329229 +0200 @@ -319,9 +319,9 @@ /usr/share/distro-info/*.csv r, /var/lib/dpkg/** r, -/usr/local/lib/python3.[0-9]/dist-packages/ r, +/usr/local/lib/python3.[0-9]*/dist-packages/ r, /usr/bin/ r, -/usr/bin/python3.[0-9] mr, +/usr/bin/python3.[0-9]* mr, # file_inherit deny /tmp/gtalkplugin.log w, ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "patch on apparmor firefox profile for python last releases" https://bugs.launchpad.net/bugs/1989571/+attachment/5615753/+files/usr.bin.firefox.patch -- 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/1989571 Title: Firefox apparmor profile : should allow python3.10 and further Status in firefox package in Ubuntu: New Bug description: I'm using firefox package from https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ on ubuntu 22.04. In this release, python3 version is currently 3.10.4-0ubuntu2. But the profile only allow python3.0 to python3.9, and I have errors notifications the profile : grep python /etc/apparmor.d/usr.bin.firefox #include /usr/include/python2.[4567]/pyconfig.h r, /usr/local/lib/python3.[0-9]/dist-packages/ r, /usr/bin/python3.[0-9] mr, so I suggest the following patch (also attached) : --- usr.bin.firefox 2022-09-14 11:48:12.612062823 +0200 +++ usr.bin.firefox.new 2022-09-14 11:48:58.232329229 +0200 @@ -319,9 +319,9 @@ /usr/share/distro-info/*.csv r, /var/lib/dpkg/** r, -/usr/local/lib/python3.[0-9]/dist-packages/ r, +/usr/local/lib/python3.[0-9]*/dist-packages/ r, /usr/bin/ r, -/usr/bin/python3.[0-9] mr, +/usr/bin/python3.[0-9]* mr, # file_inherit deny /tmp/gtalkplugin.log w, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1989571/+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 1895664] Re: evince can't start local installation of vivaldi browser
@seb128: Vivaldi is the spiritual successor of Opera. Opera _is_ included in /etc/apparmor.d/abstractions/ubuntu-browsers, so Vivaldi should be as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1895664 Title: evince can't start local installation of vivaldi browser Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Invalid Bug description: evince 3.28.4-0ubuntu1.2 running on bionic. I cannot call the vivaldi-browser by clicking on a link. Instead an error is shown "Failed to execute child process “/usr/bin/vivaldi-stable” (Permission denied)". Some lines from syslog: Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 audit(1600172908.761:241): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 audit(1600172909.393:242): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 audit(1600172909.585:243): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 audit(1600172909.617:244): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 audit(1600172933.841:256): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895664/+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 1895664] Re: evince can't start local installation of vivaldi browser
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1895664 Title: evince can't start local installation of vivaldi browser Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Invalid Bug description: evince 3.28.4-0ubuntu1.2 running on bionic. I cannot call the vivaldi-browser by clicking on a link. Instead an error is shown "Failed to execute child process “/usr/bin/vivaldi-stable” (Permission denied)". Some lines from syslog: Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 audit(1600172908.761:241): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 audit(1600172909.393:242): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 audit(1600172909.585:243): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 audit(1600172909.617:244): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 audit(1600172933.841:256): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895664/+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 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland
This is the debdiff for gnome-shell 42.4-0ubuntu0.22.04.1 from jammy. We would like this to be included in -proposed before next weekend (2022-09-23), so I am doing SRU in spite of Salsa merge request. ** Description changed: - Monitor switcher popup (Super-P) is not displayed on desktop with joined - display on GNOME 3 in Wayland mode + [Impact] + Users using desktop PC is not able to switch monitor mode between mirrored and joined mode using Super-P or keyboard shortcut. This SRU fixes the issue. - [Reproduce Steps] - 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) + [Test Plan] + 1. Use a desktop PC and start GNOME 3 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again - [Expected Result] - Display Switcher popup should appear + Expected: Display Switcher popup should appear - [Actual Result] - Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode + Actual: Display Switcher does not popup + + [Where problems could occur] + Although this change is minimal, the impact should be only on switching display mode using the shortcut. [Version] gnome-shell42.2-0ubuntu0.2 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Patch added: "gnome-shell_42.4-0ubuntu0.22.04.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1984147/+attachment/5615731/+files/gnome-shell_42.4-0ubuntu0.22.04.2.debdiff -- 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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Jammy: In Progress Status in gnome-shell source package in Kinetic: Fix Committed Bug description: [Impact] Users using desktop PC is not able to switch monitor mode between mirrored and joined mode using Super-P or keyboard shortcut. This SRU fixes the issue. [Test Plan] 1. Use a desktop PC and start GNOME 3 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again Expected: Display Switcher popup should appear Actual: Display Switcher does not popup [Where problems could occur] Although this change is minimal, the impact should be only on switching display mode using the shortcut. [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+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 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland
Update Jammy: https://salsa.debian.org/gnome-team/gnome- shell/-/merge_requests/64 ** Changed in: gnome-shell (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Jammy) Assignee: (unassigned) => Yao Wei (medicalwei) ** Changed in: oem-priority Assignee: (unassigned) => Yao Wei (medicalwei) ** Changed in: oem-priority Status: New => In Progress ** Patch removed: "lp1984147.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1984147/+attachment/5612602/+files/lp1984147.patch ** Tags added: fixed-upstream -- 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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Jammy: In Progress Status in gnome-shell source package in Kinetic: Fix Committed Bug description: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+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 1956885] Re: Incorrect verify implementation, unable to verify on one finger
Hi Loic, I built a new deb here, please also check on your side. I can verify with one finger. fpritd-verify also works from my testing. https://launchpad.net/~andch/+archive/ubuntu/staging-fprint ** No longer affects: libfprint (Ubuntu) ** Changed in: oem-priority Status: Confirmed => In Progress ** Changed in: libfprint-2-tod1-broadcom Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1956885 Title: Incorrect verify implementation, unable to verify on one finger Status in libfprint-2-tod1-broadcom: In Progress Status in OEM Priority Project: In Progress Bug description: The closed-source library blocks on synchronous USB transfers in its "verify" method (at least, there might be others with the same issue). The "identify" one is correct (asynchronous). As a result : $ fprintd-verify Using device /net/reactivated/Fprint/Device/0 Listing enrolled fingers: - #0: right-index-finger (finger pressed) Verify started! Verifying: right-index-finger (blocked) "Verify started!" should happen immediately, but the code libfprint code waits for fp_device_verify to return, which only happens when the finger is pressed with this driver. The verify success message is sent during the call, so it is ignored. "fprintd-verify -f any" and pam-fprintd use fp_device_identify, so they work correctly. But with https://gitlab.freedesktop.org/libfprint/fprintd/-/commit/fc65055279 (so I suppose on jammy), the "verify" method will be used instead if only one finger is enrolled. TL,DR: the fingerprint reader appears to mostly work on focal, but starting with jammy it won't unless at least two fingers are enrolled. Note that this is tested on a Dell Latitude 5521, but the issue should be the same with all Broadcom fingerprint readers using this library. Duplicate bug #1981974 To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1956885/+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
