[Desktop-packages] [Bug 1998565] Re: DVT1_Tributo RPL_Ubuntu_SUT no sound output
** Attachment added: "os version.png" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1998565/+attachment/5633862/+files/os%20version.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1998565 Title: DVT1_Tributo RPL_Ubuntu_SUT no sound output Status in gvfs package in Ubuntu: New Bug description: [PIMS-185529]Play music and video,adjust volume to 0-100%.Find no sound output. Description Expect Behaviors: Test case: 100424.013 Steps:10/11 Play music and video and adjust volume to 0-100% function normal. Note: Ubuntu_22.04.1 LTS/dell-bto-jammy-jellyfish-tentacool-rpl-X74-20221124-1 BIOS:0.2.0 CPU:I5-1340P/I5-1350P/I7-1360P [Reproduce Steps] 1.Play music/video via Internet 2.Ajust the sound volume find no sound output [Results] Expected Result: - Play music and video, sound's output is work normally. Actual Result: - Play music and video,adjust volume to 0-100%.Find no sound output. [Additional Information] Test Vault ID: 100424.013 SKU: Tributo RPL BIOS Version: 0.2.0 Image/Manifest: dell-bto-jammy-jellyfish-tentacool-rpl-X74-20221124-1 CPU: CPU:I5-1340P/I5-1350P/I7-1360P GPU: intel gxf Failure rate: F/R:2/2U To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1998565/+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 1998565] [NEW] DVT1_Tributo RPL_Ubuntu_SUT no sound output
Public bug reported: [PIMS-185529]Play music and video,adjust volume to 0-100%.Find no sound output. Description Expect Behaviors: Test case: 100424.013 Steps:10/11 Play music and video and adjust volume to 0-100% function normal. Note: Ubuntu_22.04.1 LTS/dell-bto-jammy-jellyfish-tentacool-rpl-X74-20221124-1 BIOS:0.2.0 CPU:I5-1340P/I5-1350P/I7-1360P [Reproduce Steps] 1.Play music/video via Internet 2.Ajust the sound volume find no sound output [Results] Expected Result: - Play music and video, sound's output is work normally. Actual Result: - Play music and video,adjust volume to 0-100%.Find no sound output. [Additional Information] Test Vault ID: 100424.013 SKU: Tributo RPL BIOS Version: 0.2.0 Image/Manifest: dell-bto-jammy-jellyfish-tentacool-rpl-X74-20221124-1 CPU: CPU:I5-1340P/I5-1350P/I7-1360P GPU: intel gxf Failure rate: F/R:2/2U ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: jellyfish-tentacool-rpl jellyfish-tentacool-rpl-x74-20221124-1 ** Attachment added: "sosreport-marg-XPS-9320-146755-2022-12-01-immvjve.tar.xz" https://bugs.launchpad.net/bugs/1998565/+attachment/5633861/+files/sosreport-marg-XPS-9320-146755-2022-12-01-immvjve.tar.xz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1998565 Title: DVT1_Tributo RPL_Ubuntu_SUT no sound output Status in gvfs package in Ubuntu: New Bug description: [PIMS-185529]Play music and video,adjust volume to 0-100%.Find no sound output. Description Expect Behaviors: Test case: 100424.013 Steps:10/11 Play music and video and adjust volume to 0-100% function normal. Note: Ubuntu_22.04.1 LTS/dell-bto-jammy-jellyfish-tentacool-rpl-X74-20221124-1 BIOS:0.2.0 CPU:I5-1340P/I5-1350P/I7-1360P [Reproduce Steps] 1.Play music/video via Internet 2.Ajust the sound volume find no sound output [Results] Expected Result: - Play music and video, sound's output is work normally. Actual Result: - Play music and video,adjust volume to 0-100%.Find no sound output. [Additional Information] Test Vault ID: 100424.013 SKU: Tributo RPL BIOS Version: 0.2.0 Image/Manifest: dell-bto-jammy-jellyfish-tentacool-rpl-X74-20221124-1 CPU: CPU:I5-1340P/I5-1350P/I7-1360P GPU: intel gxf Failure rate: F/R:2/2U To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1998565/+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 1990030] Re: Webpage in Firefox crashes computer
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1990030 Title: Webpage in Firefox crashes computer Status in firefox package in Ubuntu: Expired Bug description: I could not reproduce this today, but the web page at https://celebratingsweets.com/big-chewy-ginger-molasses-cookies/ crashed my computer. This website has every advertisement, popup, and video known to man on it. I had a monitor connected to my laptop by an HDMI cable, and I had the Firefox browser (I have the latest version 104.0.2, 64-bit) open in the laptop screen to this web page. This was the only window I had open (the only other [user] program running was wallch, which rotates the desktop background image), when the screen went blank after a period of inactivity, and the screen wouldn't redraw when I moved my finger on the laptop touchpad or pressed the space bar to wake it up. It just stayed black, ctl-alt-del was not recognized, nor were any keys, and the only thing I could figure out to get it back was to press the power button until the computer shut off. Then reboot. This happened twice. The touchpad was hot, like something was overheating inside the laptop. This laptop was built by System76 and is some sort of generic Lenovo under the hood. No web site has ever crashed my computer before. I have Ubuntu, upgraded from version 20 to 22.04.1 LTS three weeks ago, and upgraded from DSL to fiber Internet two weeks ago. Maybe one of these is causing the problem. I'll try to also report it to the other components' producers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1990030/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Tags added: originate-from-1982919 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Confirmed Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1987631] Re: Screencast only records one second
Just a single bump in hopes that a maintainer will see my above comments. It would be wonderful if we could either cherry-pick that commit or get a merge of gstreamer 1.20.4 in jammy (similar to https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1980239 but unfortunately Jeremy Bicha did not respond to my inquiry about merging 1.20.4). Screen recording in jammy is still broken but I've tested this patch on two machines with success now. So, I'm hopeful it will be picked up. -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: Confirmed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1980781] Re: SRU of ubuntu-advantage-desktop-daemon to older series
This bug was fixed in the package ubuntu-advantage-desktop-daemon -
1.10~16.04.1
---
ubuntu-advantage-desktop-daemon (1.10~16.04.1) xenial; urgency=medium
* Backport the ubuntu-advantage-desktop-daemon service to 16.04
(lp: #1980781)
* debian/compat, debian/control, debian/rules:
- Lower dh level to 9, specify 'with systemd' which isn't default
* debian/control, debian/patches/build_without_meson.patch:
- build using autotools instead of meson since the xenial version
is outdated and lacks the required features
* debian/control:
- require an ubuntu-advantage-tools version recent enough
* debian/patches/older_systemd_options.patch:
- don't use systemd options which aren't available in xenial
-- Sebastien Bacher Tue, 20 Sep 2022 18:27:07
+0200
** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-advantage-desktop-daemon in
Ubuntu.
https://bugs.launchpad.net/bugs/1980781
Title:
SRU of ubuntu-advantage-desktop-daemon to older series
Status in ubuntu-advantage-desktop-daemon package in Ubuntu:
Fix Released
Status in ubuntu-advantage-desktop-daemon source package in Xenial:
Fix Released
Status in ubuntu-advantage-desktop-daemon source package in Bionic:
Fix Released
Status in ubuntu-advantage-desktop-daemon source package in Focal:
Fix Released
Bug description:
[Impact]
ubuntu-advantage-desktop-daemon is a service we added in 22.04 to let
desktop application interact easily with Ubuntu Advantage
adsys makes use of is to check if the system is connected to UA. This is
supported in 20.04 LTS but until now the daemon was not available there.
Installing the daemon enables advanced usages (scripts, privilege
delegation…) which require an Ubuntu Pro account
Ubuntu Pro integration is being added to software-properties which
also require the service to be available.
[Test Plan]
A. Verify the service
1. Install:
$ sudo apt install ubuntu-advantage-desktop-daemon
2. Check able to access daemon
$ gdbus call --system --dest com.canonical.UbuntuAdvantage --object-path
/com/canonical/UbuntuAdvantage/Manager --method
org.freedesktop.DBus.Properties.GetAll 'com.canonical.UbuntuAdvantage.Manager'
({'Attached': , 'DaemonVersion': <'1.8'>},)
B. Software-properties
Verify that the new 'Ubuntu Pro' page is working as expected, SRU bug
#, especially that it reflects the correct status and that
attaching/detaching a token and enabling/disabling services is working
C. Adsys (focal)
1. Ensure that you have an Ubuntu Advantage subcription enabled.
2. Setup some scripts under AD to be executed, one for machine scripts (on
startup), one for user scripts (on login). Those scripts can create some
temporary files under /tmp for instance.
3. Reboot and login on the Ubuntu laptop connected with AD by adsys.
4. Check that the scripts were executed by testing that the created file
under /tmp are present.
[Where problems could occur]
This is a code that has not previously been used on 20.04 and thus
could trigger new bugs. It has been used for since jammy though
without major issues.
A. The service itself
The service shouldn't be active unless it's needed. If you don't have ubuntu
advantage nor adsys configured check that the service is not loaded.
The service should low on resource usage, check that it's the case by
checking the RAM and CPU consumption.
B. Software-properties
The Ubuntu Pro tab didn't exist before so there should be no
regression possible there due to the service. The livepatch enablement
is handled through the service as part of UA now so check that
livepatch is correctly working still on upgraded systems
C. Adsys (focal)
The behaviour change in adsys should be limited to enabling features
which weren't available in focal before but we should ensure those are
correctly working and not providing a buggy user experience
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/1980781/+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 1988256] Re: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland
I'd been running into this issue on Ubuntu 22.04 with Google Chrome, GNOME Shell under Wayland, and multiple monitors - opening Chrome will frequently crash my whole GNOME session. I could also reliably reproduce it once Chrome is running by moving a Chrome window to another monitor from the GNOME activities overview. After I built & installed libmutter 42.6 (42.5 was previously installed), the problem went away. -- 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/1988256 Title: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland_seat_get_grab_info() from token_can_activate() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/6582f375d7b1e6bec0fdee2e9d2ec574844a8457 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1988256/+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 1998537] [NEW] Holding Cttrl+S generates too many 'save page' dialogues
Public bug reported: Opening any page and holding Ctrl+S on the firefox snap package begins to spam-generate save dialogues. These do not stop being generated for several seconds after Ctrl+S is released. These dialogues slow down the system to the point that interacting with both them, and the system as a whole, feels laggy. The compositor also attempts to assign them each shadows, and as a result, on Mutter with Wayland, a they are surrounded by a thick black halo (see attachment). I'm running Ubuntu 22.04.1 on Gnome 42.5 with Wayland. Firefox is version 107.0.1 although this bug has been present on every version of Firefox I've used on this system. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "The bug in action" https://bugs.launchpad.net/bugs/1998537/+attachment/5633826/+files/Screenshot%20from%202022-12-01%2021-24-35.png -- 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/1998537 Title: Holding Cttrl+S generates too many 'save page' dialogues Status in firefox package in Ubuntu: New Bug description: Opening any page and holding Ctrl+S on the firefox snap package begins to spam-generate save dialogues. These do not stop being generated for several seconds after Ctrl+S is released. These dialogues slow down the system to the point that interacting with both them, and the system as a whole, feels laggy. The compositor also attempts to assign them each shadows, and as a result, on Mutter with Wayland, a they are surrounded by a thick black halo (see attachment). I'm running Ubuntu 22.04.1 on Gnome 42.5 with Wayland. Firefox is version 107.0.1 although this bug has been present on every version of Firefox I've used on this system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1998537/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: modemmanager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Confirmed Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1998529] [NEW] Uninstalling extensions dereferences symlinks, risking data loss
Public bug reported: Uninstalling a gnome-shell extension removes its folder in ".local/share/gnome-shell/extensions", recursively as it should, but dereferencing symlinks!! Here is what happens and how to reproduce: Someone (me) installs an extension to try it out. While tweaking with its configuration, to try to customize it, I put a symlink within its extensions directory, pointing to somewhere else in my home folder. For example, in my case, a symlink to "~/Pictures/Icons", to be able to set it up with one of many custom icons I've created. Uninstall the extension later as it's not to my liking, extensions folder is gone, as well as my ~/Pictures/Icons folder's contents in my home directory. This could have been a lot worse, if the symlink was pointing higher up, since its doing a recursive delete. In this case, extension was installed as well as removed from the gnome- extensions website. Usually I install from website, but uninstall from extensions manager. Do not know if it happens with extensions manager as well. Please fix this, because I was frankly shocked that this happened, and could lead to very bad things (I've never seen a rm -rf follow symlinks, and wouldn't even want to know what flag would do that and why you would want that). What would expect to happen: A simple rm -rf recursive, non- dereferencing removal of extensions directory. What happened instead: A recursive removal, dereferencing symlinks, which can lead anywhere, and be very dangerous. Symlinks may have been placed in there if someone was working on or tweaking an extension. Description: Ubuntu 22.04.1 LTS Release: 22.04 gnome-shell42.5 chrome-gnome-shell 10.1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1998529 Title: Uninstalling extensions dereferences symlinks, risking data loss Status in gnome-shell package in Ubuntu: New Bug description: Uninstalling a gnome-shell extension removes its folder in ".local/share/gnome-shell/extensions", recursively as it should, but dereferencing symlinks!! Here is what happens and how to reproduce: Someone (me) installs an extension to try it out. While tweaking with its configuration, to try to customize it, I put a symlink within its extensions directory, pointing to somewhere else in my home folder. For example, in my case, a symlink to "~/Pictures/Icons", to be able to set it up with one of many custom icons I've created. Uninstall the extension later as it's not to my liking, extensions folder is gone, as well as my ~/Pictures/Icons folder's contents in my home directory. This could have been a lot worse, if the symlink was pointing higher up, since its doing a recursive delete. In this case, extension was installed as well as removed from the gnome-extensions website. Usually I install from website, but uninstall from extensions manager. Do not know if it happens with extensions manager as well. Please fix this, because I was frankly shocked that this happened, and could lead to very bad things (I've never seen a rm -rf follow symlinks, and wouldn't even want to know what flag would do that and why you would want that). What would expect to happen: A simple rm -rf recursive, non- dereferencing removal of extensions directory. What happened instead: A recursive removal, dereferencing symlinks, which can lead anywhere, and be very dangerous. Symlinks may have been placed in there if someone was working on or tweaking an extension. Description: Ubuntu 22.04.1 LTS Release: 22.04 gnome-shell42.5 chrome-gnome-shell 10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998529/+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 1997999] Re: The initial gnome screen shows the former Ubuntu release (22.04) - should show 22.10
Thanks, I think this is the unity-greeter package. ** Package changed: ubuntu-release-upgrader (Ubuntu) => unity-greeter (Ubuntu) ** Changed in: unity-greeter (Ubuntu) Status: Incomplete => New ** Changed in: unity-greeter (Ubuntu Kinetic) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1997999 Title: The initial gnome screen shows the former Ubuntu release (22.04) - should show 22.10 Status in unity-greeter package in Ubuntu: New Status in unity-greeter source package in Kinetic: New Bug description: Looks like the release is hard coded, or a screen did not get updated.. It shows the right logo for 22.10, but states Ubuntu version is 22.04. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:125:3162311:2022-11-25 07:01:12.63680 +1300:2022-11-25 07:01:12.104844419 +1300:/var/crash/_usr_libexec_xscreensaver_pinion.1000.crash CurrentDesktop: ubuntu:GNOME Date: Sat Nov 26 11:46:56 2022 InstallationDate: Installed on 2021-12-04 (356 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to kinetic on 2022-11-09 (16 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1997999/+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 1997999] [NEW] The initial gnome screen shows the former Ubuntu release (22.04) - should show 22.10
You have been subscribed to a public bug: Looks like the release is hard coded, or a screen did not get updated.. It shows the right logo for 22.10, but states Ubuntu version is 22.04. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:125:3162311:2022-11-25 07:01:12.63680 +1300:2022-11-25 07:01:12.104844419 +1300:/var/crash/_usr_libexec_xscreensaver_pinion.1000.crash CurrentDesktop: ubuntu:GNOME Date: Sat Nov 26 11:46:56 2022 InstallationDate: Installed on 2021-12-04 (356 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to kinetic on 2022-11-09 (16 days ago) VarLogDistupgradeTermlog: ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: unity-greeter (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug dist-upgrade kinetic third-party-packages -- The initial gnome screen shows the former Ubuntu release (22.04) - should show 22.10 https://bugs.launchpad.net/bugs/1997999 You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. -- 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 1993789] Re: Backport the webp gdk-pixbuf loader to the LTS
This bug was fixed in the package webp-pixbuf-loader - 0.0.5-5~22.04.1 --- webp-pixbuf-loader (0.0.5-5~22.04.1) jammy; urgency=medium * Backport gdk-pixbuf loader for the webp format (lp: #1993789) -- Sebastien Bacher Fri, 21 Oct 2022 10:43:09 +0200 ** Changed in: webp-pixbuf-loader (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webp-pixbuf-loader in Ubuntu. https://bugs.launchpad.net/bugs/1993789 Title: Backport the webp gdk-pixbuf loader to the LTS Status in webp-pixbuf-loader package in Ubuntu: Fix Released Status in webp-pixbuf-loader source package in Jammy: Fix Released Bug description: * Impact The webp format is getting more popular, having the gdk-pixbuf loader available in the archive would make easier for users to enable it (as a first step, we might also want to consider enable it by default) * Testcase 1. Install webp-pixbuf-loader 2. Use nautilus to browser a directory with webp images, they should be previewed 3. Start eog, select the open option and select a webp image, it should be displayed * Regression potential The package is new and not installed by default so it shouldn't have any impact. Install it then verify that it's not creating issues in nautilus, eog or other gtk based viewers loading icons. Other formats should keep working as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webp-pixbuf-loader/+bug/1993789/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
Hello everyone subscribed to this topic, I totally edited my previous comment because it was a misconception. Now I noticed, the problem depends on whether the printer is connected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1998444] Re: Backport security fix for CVE-2022-3970
The fix for CVE-2022-3970 has been released in the following versions: Ubuntu 22.10: 4.4.0-4ubuntu3.2 Ubuntu 22.04 LTS: 4.3.0-6ubuntu0.3 Ubuntu 20.04 LTS: 4.1.0+git191117-2ubuntu0.20.04.7 Ubuntu 18.04 LTS: 4.0.9-5ubuntu0.9 ** Changed in: tiff (Ubuntu) Status: In Progress => Fix Released ** Changed in: tiff (Ubuntu Bionic) Status: New => Fix Released ** Changed in: tiff (Ubuntu Focal) Status: New => Fix Released ** Changed in: tiff (Ubuntu Jammy) Status: New => Fix Released ** Changed in: tiff (Ubuntu Kinetic) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1998444 Title: Backport security fix for CVE-2022-3970 Status in tiff package in Ubuntu: Fix Released Status in tiff source package in Bionic: Fix Released Status in tiff source package in Focal: Fix Released Status in tiff source package in Jammy: Fix Released Status in tiff source package in Kinetic: Fix Released Bug description: This CVE patch is desperately needed to fix a build failure caused by a crash in the testsuite of the current libreoffice/kinetic SRU Testing load file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff: *** stack smashing detected ***: terminated Fatal exception: Signal 6 Stack: /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2] /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a] /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc] /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a] /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636] /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386] /lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc] /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1] /lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10] /<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6] /<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5] /<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c] /<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07] /<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f] /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9] /<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5] Aborted (core dumped) make[4]: ***
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
I released the (possible) fix in stable/password branch. You can install
it with
snap install --channel stable/password chromium
Please make sure to connect the interface as in the bug description,
snap connect chromium:password-manager-service
It might also be a good idea to delete the Chromium entries from
Seahorse before the test.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1997168
Title:
[snap] Passwords are saved but not loaded with gnome keyring
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
Steps to reproduce:
* System: Fresh (minimal, desktop) installation of Ubuntu 22.04 LTS in
VirtualBox to rule out any side-effects from preexisting configurations
* Install latest updates: `sudo apt update && sudo apt upgrade -y && sudo apt
dist-upgrade -y && sudo snap refresh`
* Install chromium from snap (`sudo snap install chromium`)
* Connect chromium to password manager service (`sudo snap connect
chromium:password-manager-service`) -> now chromium should be able to use gnome
keyring to store its master password
* Launch chromium, navigate to "chrome://settings/passwords"
* Add a new password ("Saved Passwords" -> "Add")
* Password shows up under "Saved Passwords" as expected.
* Close chromium and open it again, navigate to "chrome://settings/passwords"
* Expected: Password should show up. Instead: The list is empty.
* Add another password: List stays empty.
What I found out so far:
* Despite of the list showing up as empty in chromium, both passwords have
been stored in "~/snap/chromium/common/chromium/Default/Login Data" (to
confirm, grep for the username of the saved login, as the password itself will
be encrypted)
* It seems that the snap version of chromium does not create the entries
"Chrome Safe Storage" and "Chrome Safe Storage Control" in the gnome keyring,
which seems to be necessary at the moment (see http://crbug.com/660005). If a
non-snap version of chromium (e.g. from
https://launchpad.net/~savoury1/+archive/ubuntu/chromium) is installed first,
which is used to bootstrap the user's chromium config folder and which creates
the aforementioned entries in the gnome keyring, things are working fine, even
after transitioning to the snap version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997168/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken
** Also affects: fontforge (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Confirmed Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997907] Re: [snap] trap invalid opcode
Still doing the same thing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1997907 Title: [snap] trap invalid opcode Status in chromium-browser package in Ubuntu: New Bug description: Chromium shuts down and when restarted, says it didn't shut down properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 24 16:34:50 2022 InstallationDate: Installed on 2022-03-19 (250 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 107.0.5304.110 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997907] Re: [snap] trap invalid opcode
Just upgraded kernel from 5.15.0-52 to 5.15.0-56 & monitoring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1997907 Title: [snap] trap invalid opcode Status in chromium-browser package in Ubuntu: New Bug description: Chromium shuts down and when restarted, says it didn't shut down properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 24 16:34:50 2022 InstallationDate: Installed on 2022-03-19 (250 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 107.0.5304.110 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998497] [NEW] "Always on top" window prevents new windows from taking focus
Public bug reported: 1. Launch a terminal 2. Launch something from it, say 'xlogo &' 3. Put xlogo always on top by right clicking its title bar and selecting that option. 4. Back to the terminal, open a new window, preferentially something whose lack of input focus is evident, e.g. 'zenity --password'. Expected: New window has focus (you can type right away into zenity). Observed: Old window has focus. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libglib2.0-0 2.74.0-3 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:58:34 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998497 Title: "Always on top" window prevents new windows from taking focus Status in glib2.0 package in Ubuntu: New Bug description: 1. Launch a terminal 2. Launch something from it, say 'xlogo &' 3. Put xlogo always on top by right clicking its title bar and selecting that option. 4. Back to the terminal, open a new window, preferentially something whose lack of input focus is evident, e.g. 'zenity --password'. Expected: New window has focus (you can type right away into zenity). Observed: Old window has focus. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libglib2.0-0 2.74.0-3 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:58:34 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958019]
https://wiki.archlinux.org/title/DSDT#Using_modified_code: We should be able to override it. From here, using early patching should allow you to specify using a quirk to support CSC3551. From there's a question of using safe values in your override. Also, you won't have suspend/resume for the support for the amp chips with the Gen 6 unless you're using a 6.1 kernel. On 11/30/22 03:40, bugzilla-dae...@kernel.org wrote: > I wish the kernel guys weren't so dead set against loadable DSDTs. There's > still so many reasons why we need to be able to patch these ourselves and > there's no good reason to have to rebuild an entire kernel just to add > missing > table entries. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997907] Re: [snap] trap invalid opcode
Just updated to Version 108.0.5359.71 (Official Build) snap (64-bit), still doing the same thing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1997907 Title: [snap] trap invalid opcode Status in chromium-browser package in Ubuntu: New Bug description: Chromium shuts down and when restarted, says it didn't shut down properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 24 16:34:50 2022 InstallationDate: Installed on 2022-03-19 (250 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 107.0.5304.110 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973031] Re: [MIR] libwpe
** Also affects: libwpe (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwpe in Ubuntu. https://bugs.launchpad.net/bugs/1973031 Title: [MIR] libwpe Status in libwpe package in Ubuntu: Fix Released Status in libwpe source package in Jammy: New Bug description: [Availability] The package libwpe is already in Ubuntu universe. The package libwpe build for the architectures it is designed to work on. It currently builds and works for architectures: amd64 arm64 armhf i386 ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/libwpe [Rationale] The package libwpe is required in Ubuntu main as a dependency of webkit2gtk. The dependency is optional but the default upstream and in other distributions and the only one upstream is really testing (turned out some of the issues we had previous cycle are because we aren't using the default backend, which also made a lower priority for upstream to work on fixes). Upstream is also planning to deprecate the nonwpe codepath. - The package wpebackend-fdo is required in Ubuntu main no later than aug 25 due to feature freeze [Security] - No CVEs/security issues in this software in the past - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Ubuntu and Debian and has currently no reports - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libwpe/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libwpe [Quality assurance - testing] - The package does not run a test at build time because upstream doesn't have one. That's something we need to work on. BLOCKER ^ If webkit2gtk is built with it as it default backend then the webkitgtk autopkgtests are going to exercise wpe, is that enough? BLOCKER? ^ We need to work on the testing story, backup plan is to write some manual test plans. It's likely that the test plan for wpebackend-fdo will cover the library. [Quality assurance - packaging] - debian/watch is present and works -- There is only one lintian warning # lintian --pedantic P: libwpe source: package-uses-old-debhelper-compat-version 12 12 isn't that old but we will work on updating to 13 - Lintian overrides are not present - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf question - Packaging and build is easy, link to d/rules https://salsa.debian.org/webkit-team/libwpe/-/blob/master/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be desktop-packages - Team is not yet, but will subscribe to the package before promotion - This does not use static builds - This does not use vendored code - The package successfully built during the most recent test rebuild [Background information] The Package description explains the package well Upstream Name is libwpe Link to upstream project https://github.com/WebPlatformForEmbedded/libwpe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwpe/+bug/1973031/+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 1973033] Re: [MIR] wpebackend-fdo
** Also affects: wpebackend-fdo (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpebackend-fdo in Ubuntu. https://bugs.launchpad.net/bugs/1973033 Title: [MIR] wpebackend-fdo Status in wpebackend-fdo package in Ubuntu: Fix Released Status in wpebackend-fdo source package in Jammy: New Bug description: [Availability] The package wpebackend-fdo is already in Ubuntu universe. The package wpebackend-fdo build for the architectures it is designed to work on. It currently builds and works for architectures: amd64 arm64 armhf i386 ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/wpebackend-fdo [Rationale] - The package wpebackend-fdo is required in Ubuntu main as a dependency of webkit2gtk. The dependency is optional but the default upstream and in other distributions and the only one upstream is really testing (turned out some of the issues we had previous cycle are because we aren't using the default backend, which also made a lower priority for upstream to work on fixes). Upstream is also planning to deprecate the nonwpe codepath. We might also need to build with that backend on older series at some point due to the previous statement. - The package wpebackend-fdo is required in Ubuntu main no later than aug 25 due to feature freeze [Security] - No CVEs/security issues in this software in the past - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Ubuntu and Debian and has currently no reports - Ubuntu https://bugs.launchpad.net/ubuntu/+source/wpebackend-fdo/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=wpebackend-fdo - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because upstream doesn't have one. That's something we need to work on. BLOCKER ^ - The package does not run an autopkgtest because upstream has no test and Debian didn't have some either. If webkit2gtk is built with it as it default backend then the webkitgtk autopkgtests are going to exercise wpe, is that enough? BLOCKER? ^ We need to work on the testing story, backup plan is to write some manual test plans. [Quality assurance - packaging] - debian/watch is present and works -- There is only one lintian warning # lintian --pedantic P: wpebackend-fdo source: package-uses-old-debhelper-compat-version 12 12 isn't that old but we will work on updating to 13 - There is one lintian overrides for having the .so distributed in the library rather than the dev because browsers try to load the .so and it should be available. The change was added in Debian to https://salsa.debian.org/webkit-team/wpebackend-fdo/-/commit/07a67e57 - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions - Packaging and build is easy, link to d/rules https://salsa.debian.org/webkit-team/wpebackend- fdo/-/blob/master/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - There are further dependencies that are not yet in main, MIR for them is at https://bugs.launchpad.net/ubuntu/+source/libwpe/+bug/1973031 [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be desktop-packages - Team is not yet, but will subscribe to the package before promotion - This does not use static builds - This does not use vendored code - The package successfully built during the most recent test rebuild [Background information] The Package description explains the package well Upstream Name is wpebackend-fdo Link to upstream project https://github.com/Igalia/WPEBackend-fdo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpebackend-fdo/+bug/1973033/+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 1979121] Re: [MIR] webp-pixbuf-loader
Targetting 22.04 there now as we would like to have webp support enabled by default also in the LTS. @MIR team, could you review the request of promoting the package also in 22.04? The exact same version that was promoted in Kinetic has been SRUed to the LTS, https://launchpad.net/bugs/1993789 If/when the promotion is validated we will work on SRUing an eog update pulling webp-pixbuf-loader by default (depends or recommends) ** Also affects: webp-pixbuf-loader (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webp-pixbuf-loader in Ubuntu. https://bugs.launchpad.net/bugs/1979121 Title: [MIR] webp-pixbuf-loader Status in webp-pixbuf-loader package in Ubuntu: Fix Released Status in webp-pixbuf-loader source package in Jammy: New Bug description: [Availability] The package webp-pixbuf-loader is already in Ubuntu universe. The package webp-pixbuf-loader build for the architectures it is designed to work on. It currently builds and works for architetcures: amd64 arm64 armhf ppc64el riscv64 s390x is failing tests in which seems a big endian issue, reported upstream https://github.com/aruiz/webp-pixbuf-loader/issues/39 Link to package https://launchpad.net/ubuntu/+source/webp-pixbuf-loader [Rationale] - The package webp-pixbuf-loader is required in Ubuntu main to be able to open webp image from the standard viewer (eog) and get thumbnails in the filemanage - The package webp-pixbuf-loader will generally be useful for a large part of our user base - The package webp-pixbuf-loader is required in Ubuntu main no later than aug 25 due to feature freeze [Security] - No CVEs/security issues in this software in the past - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is new in Debian/Ubuntu and has currently no bug reported - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpadlibrarian.net/607631911/buildlog_ubuntu-kinetic-amd64.webp-pixbuf-loader_0.0.5-2_BUILDING.txt.gz - The package does not run an autopkgtest because image loaders aren't easy to verify in that setup, but we will open example webp files as a manual testcase before doing package updates. [Quality assurance - packaging] - debian/watch is present and works - the package is in sync with Debian and has a valid maintainer definition - The package displays no lintian warnings - Please link to a recent build log of the package https://launchpadlibrarian.net/607631911/buildlog_ubuntu-kinetic-amd64.webp-pixbuf-loader_0.0.5-2_BUILDING.txt.gz - Lintian overrides are not present [Maintenance/Owner] - Owning Team will be desktop-packages - Team is already subscribed to the package - This does not use static builds - This does not use vendored code - The package has been built in the archive more recently than the last test rebuild [Background information] The Package description explains the package well Upstream Name is webp-pixbuf-loader Link to upstream project https://github.com/aruiz/webp-pixbuf-loader/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webp-pixbuf-loader/+bug/1979121/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
Works for me too on 22.04 (for a Canon TS8350 on the network) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY 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.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY 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/cups/+bug/1973441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996267] Re: [snap] Doesn't store encrypted passwords unless interface is connected
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1996267 Title: [snap] Doesn't store encrypted passwords unless interface is connected Status in chromium-browser package in Ubuntu: Confirmed Bug description: In the Snap package of Chromium, Chromium is not protecting passwords with gnome-keyring (or KWallet). As a result, copying the Chromium profile directory from the snap directory gives access to all stored passwords. This is a HIGH security risk. Regular users who are used to storing their passwords in browsers are probably unaware of this. Note that Chromium is started with the command line option “--password-store=basic”. This hack should never have been released to the public. The Chromium documentation states: > --password-store=basic (to use the plain text store) https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1997168
Title:
[snap] Passwords are saved but not loaded with gnome keyring
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
Steps to reproduce:
* System: Fresh (minimal, desktop) installation of Ubuntu 22.04 LTS in
VirtualBox to rule out any side-effects from preexisting configurations
* Install latest updates: `sudo apt update && sudo apt upgrade -y && sudo apt
dist-upgrade -y && sudo snap refresh`
* Install chromium from snap (`sudo snap install chromium`)
* Connect chromium to password manager service (`sudo snap connect
chromium:password-manager-service`) -> now chromium should be able to use gnome
keyring to store its master password
* Launch chromium, navigate to "chrome://settings/passwords"
* Add a new password ("Saved Passwords" -> "Add")
* Password shows up under "Saved Passwords" as expected.
* Close chromium and open it again, navigate to "chrome://settings/passwords"
* Expected: Password should show up. Instead: The list is empty.
* Add another password: List stays empty.
What I found out so far:
* Despite of the list showing up as empty in chromium, both passwords have
been stored in "~/snap/chromium/common/chromium/Default/Login Data" (to
confirm, grep for the username of the saved login, as the password itself will
be encrypted)
* It seems that the snap version of chromium does not create the entries
"Chrome Safe Storage" and "Chrome Safe Storage Control" in the gnome keyring,
which seems to be necessary at the moment (see http://crbug.com/660005). If a
non-snap version of chromium (e.g. from
https://launchpad.net/~savoury1/+archive/ubuntu/chromium) is installed first,
which is used to bootstrap the user's chromium config folder and which creates
the aforementioned entries in the gnome keyring, things are working fine, even
after transitioning to the snap version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997168/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998484] Re: Segmentation fault during window resize
** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1998484/+attachment/5633735/+files/journalctl.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1998484 Title: Segmentation fault during window resize Status in seahorse package in Ubuntu: New Bug description: I was just resizing Seahorse's window in a clean Kinetic VM and it segfaulted. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: seahorse 42.0-2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:30:16 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1998484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998484] [NEW] Segmentation fault during window resize
Public bug reported: I was just resizing Seahorse's window in a clean Kinetic VM and it segfaulted. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: seahorse 42.0-2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:30:16 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1998484 Title: Segmentation fault during window resize Status in seahorse package in Ubuntu: New Bug description: I was just resizing Seahorse's window in a clean Kinetic VM and it segfaulted. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: seahorse 42.0-2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:30:16 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1998484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966911] Re: Cannot enroll finger on Jammy
** Changed in: libfprint-2-tod1-goodix Status: Fix Committed => Fix Released -- 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/1966911 Title: Cannot enroll finger on Jammy Status in libfprint-2-tod1-goodix: Fix Released Status in OEM Priority Project: Fix Released Status in fprintd package in Ubuntu: Won't Fix Status in libfprint package in Ubuntu: Fix Released Status in fprintd source package in Jammy: Invalid Status in libfprint source package in Jammy: Fix Released Bug description: [Impact] Cannot enroll finger on Jammy (goodix tod driver) [Test plan] 1. Install Jammy on XPS-9310 2. Open Gnome-control-center and select `User` 3. Enroll fingerprint 1. Find another Laptop with fingerprint device and test on Jammy [Where problems could occur] * This change will only affect fingerprint tod driver The changes are mostly in the wrapper for the goodix driver so the focus should be on testing if finger print enrollment and identification is working on those devices during both authentication and finger enrollment (especially when no other fingerprints have been already enrolled). The only possible regression may happen in goodix devices using the TOD driver that may not been able to enroll or log-in. To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in pipewire package in Ubuntu: Invalid Status in xdg-desktop-portal package in Ubuntu: Invalid Status in xdg-desktop-portal-gtk package in Ubuntu: Fix Released Bug description: Freshly installed Ubuntu 21.10, screen sharing does not work with any browser, tested the following options: - Firefox snap - Firefox deb - Chromium snap - Chromium flatpak Steps to reproduce: 1. Go to https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006 2. Select to share the whole desktop in the xdg-desktop-portal 3. Notice the orange screen share indicator in Gnome-Shell but actually nothing is shared in the browser. This should be handled high priority since this is a critical feature during the pandemic. Filed against ubuntu-meta since I don't know exactly which package to blame, whether it's pipewire, xdg-desktop portal or some problem directely with mutter / gnome-shell, please reassign accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998409] Re: chromium fails to start: unsupported version 0 of Verneed record
Hey Dmitriy, indeed reboots should not be necessary to launch updated snaps. So yes please run that apport-collect command and see if you can collect the lines from "journalctl -r" around the time of the crash you experienced some hours ago. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Tags added: snap ** Summary changed: - chromium fails to start: unsupported version 0 of Verneed record + [snap] chromium fails to start: unsupported version 0 of Verneed record -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record
[Desktop-packages] [Bug 1997907] Re: [Bug 1997596] Re: Chromium crashes without any apparent reason
** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New ** Summary changed: - [Bug 1997596] Re: Chromium crashes without any apparent reason + [snap] trap invalid opcode -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1997907 Title: [snap] trap invalid opcode Status in chromium-browser package in Ubuntu: New Bug description: Chromium shuts down and when restarted, says it didn't shut down properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 24 16:34:50 2022 InstallationDate: Installed on 2022-03-19 (250 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 107.0.5304.110 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998444] Re: Backport security fix for CVE-2022-3970
** Changed in: tiff (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1998444 Title: Backport security fix for CVE-2022-3970 Status in tiff package in Ubuntu: In Progress Status in tiff source package in Bionic: New Status in tiff source package in Focal: New Status in tiff source package in Jammy: New Status in tiff source package in Kinetic: New Bug description: This CVE patch is desperately needed to fix a build failure caused by a crash in the testsuite of the current libreoffice/kinetic SRU Testing load file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff: *** stack smashing detected ***: terminated Fatal exception: Signal 6 Stack: /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2] /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a] /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc] /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a] /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636] /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386] /lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc] /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1] /lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10] /<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6] /<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5] /<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c] /<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07] /<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f] /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9] /<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5] Aborted (core dumped) make[4]: *** [/<>/solenv/gbuild/CppunitTest.mk:121: /<>/workdir/CppunitTest/vcl_filters_test.test] Error 134 For the log of the failed amd64 kinetic archive build, see https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.3-0ubuntu0.22.10.1/+build/24883181 For the log of the successful amd64 kinetic PPA build with the updated tiff present, see https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+build/24886085 Lunar already includes this fix with the last merge from debian https://launchpad.net/ubuntu/+source/tiff/4.4.0-6ubuntu1
[Desktop-packages] [Bug 1971712] Re: Add support for Intel DG2
** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Confirmed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997979] Re: Merge grilo-plugins 0.3.15-1 from Debian unstable
This bug was fixed in the package grilo-plugins - 0.3.15-1ubuntu1 --- grilo-plugins (0.3.15-1ubuntu1) lunar; urgency=medium * Merge with Debian (LP: #1997979). Remaining change: - Split package into -base and -extra (Closes: #805609) grilo-plugins (0.3.15-1) unstable; urgency=medium [ Alberto Garcia ] * New upstream release. * debian/control: - Update debhelper-compat from 12 to 13 (Closes: #1003134). - Update Standards-Version to 4.6.1.0 (no changes). * debian/grilo-plugins-0.3.lintian-overrides: - Update format of hardening-no-fortify-functions. * debian/copyright: - Update copyright years. [ Debian Janitor ] * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on libgdata-dev, libglib2.0-dev, libgoa-1.0-dev and libtotem-plparser-dev. -- Nathan Pratta Teodosio Fri, 25 Nov 2022 11:31:46 -0300 ** Changed in: grilo-plugins (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1997979 Title: Merge grilo-plugins 0.3.15-1 from Debian unstable Status in grilo-plugins package in Ubuntu: Fix Released Bug description: Built successfully locally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1997979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978295] Update Released
The verification of the Stable Release Update for xdg-desktop-portal has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1978295 Title: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Focal: Fix Released Bug description: [Impact] * The OpenDirectory method of the OpenURI portal opens a file manager window showing the requested directory, but it doesn't select the passed file in that directory. This affects all users of this API, particularly the chromium and firefox snaps. * This is an upstream bug that was fixed in later versions of xdg- desktop-portal, this SRU backports the fix to the 1.6 series that's in focal. [Test Plan] * On a focal machine, install the chromium snap, launch it and download any file from a web page (from e.g. https://kernel.org/) * Once the download is complete, browse to chrome://downloads * Click the "Show in folder" link for the downloaded file, this opens a Nautilus window showing the contents of the default downloads directory (e.g. $HOME/Downloads) * Expected result: the downloaded file is selected in the Nautilus window * Actual result without the patch: no file is selected * Similarly for the firefox snap, downloading a file and clicking the "Show in Folder" button in the downloads panel should select the downloaded file * General functionality of all other portals (including the wallpaper portal) should be thoroughly tested to look out for regressions [Where problems could occur] * The backported patches potentially affect other portals (not just OpenURI), including the Wallpaper portal. * Therefore the functionality of all other portals should be thoroughly tested to ensure there are no functional regressions. [Other Info] * The firefox snap wasn't using this API before version 103.0, which at the time of writing this hasn't officially been released yet (it is due for release tomorrow, 2022-07-26). In the meantime it can be installed from the candidate channel. [Original Description] This is an upstream issue (https://github.com/flatpak/xdg-desktop- portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0. I'm proposing to SRU the corresponding patch to focal. This will be especially useful for browsers packaged as snaps (see bug #1887195 for chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978295/+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 1978295] Re: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file
This bug was fixed in the package xdg-desktop-portal - 1.6.0-1ubuntu2 --- xdg-desktop-portal (1.6.0-1ubuntu2) focal; urgency=medium * Cherry-pick an upstream commit and its prerequisites to highlight the selected file when invoking tho OpenDirectory method (LP: #1978295) - debian/patches/upstream-32da40b-unset-fd-from-requests.patch - debian/patches/upstream-9c81f44-real-path-for-doc-path.patch - debian/patches/upstream-8f3ab60-opendirectory-fixes.patch -- Olivier Tilloy Fri, 10 Jun 2022 11:10:25 +0200 ** Changed in: xdg-desktop-portal (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1978295 Title: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Focal: Fix Released Bug description: [Impact] * The OpenDirectory method of the OpenURI portal opens a file manager window showing the requested directory, but it doesn't select the passed file in that directory. This affects all users of this API, particularly the chromium and firefox snaps. * This is an upstream bug that was fixed in later versions of xdg- desktop-portal, this SRU backports the fix to the 1.6 series that's in focal. [Test Plan] * On a focal machine, install the chromium snap, launch it and download any file from a web page (from e.g. https://kernel.org/) * Once the download is complete, browse to chrome://downloads * Click the "Show in folder" link for the downloaded file, this opens a Nautilus window showing the contents of the default downloads directory (e.g. $HOME/Downloads) * Expected result: the downloaded file is selected in the Nautilus window * Actual result without the patch: no file is selected * Similarly for the firefox snap, downloading a file and clicking the "Show in Folder" button in the downloads panel should select the downloaded file * General functionality of all other portals (including the wallpaper portal) should be thoroughly tested to look out for regressions [Where problems could occur] * The backported patches potentially affect other portals (not just OpenURI), including the Wallpaper portal. * Therefore the functionality of all other portals should be thoroughly tested to ensure there are no functional regressions. [Other Info] * The firefox snap wasn't using this API before version 103.0, which at the time of writing this hasn't officially been released yet (it is due for release tomorrow, 2022-07-26). In the meantime it can be installed from the candidate channel. [Original Description] This is an upstream issue (https://github.com/flatpak/xdg-desktop- portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0. I'm proposing to SRU the corresponding patch to focal. This will be especially useful for browsers packaged as snaps (see bug #1887195 for chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978295/+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 1989313] Re: To support Goodix fp device [27C6:634C]
This bug was fixed in the package libfprint - 1:1.90.2+tod1-0ubuntu1~20.04.10 --- libfprint (1:1.90.2+tod1-0ubuntu1~20.04.10) focal; urgency=medium [ Andy Chi ] * Add support of Goodix fp devices - d/p/goodixmoc-add-PID-0x631C.patch (LP: #1990209) - d/p/goodixmoc-add-PID-0x634C.patch (LP: #1989313) -- Marco Trevisan (Treviño) Mon, 21 Nov 2022 17:01:58 +0100 ** Changed in: libfprint (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1989313 Title: To support Goodix fp device [27C6:634C] Status in OEM Priority Project: Fix Released Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: Fix Released Status in libfprint source package in Jammy: Fix Released Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/151551b52b006e541e62949706cf491561af9ea1 This ID is included in upstream. [Impact] * Devices have Goodix [27C6:634C] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [27C6:634C] will be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1989313/+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 1989313] Re: To support Goodix fp device [27C6:634C]
** Changed in: oem-priority Status: Fix Committed => Fix Released -- 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/1989313 Title: To support Goodix fp device [27C6:634C] Status in OEM Priority Project: Fix Released Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: Fix Released Status in libfprint source package in Jammy: Fix Released Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/151551b52b006e541e62949706cf491561af9ea1 This ID is included in upstream. [Impact] * Devices have Goodix [27C6:634C] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [27C6:634C] will be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1989313/+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 1990209] Re: To support Goodix fp device [27C6:631C]
This bug was fixed in the package libfprint - 1:1.90.2+tod1-0ubuntu1~20.04.10 --- libfprint (1:1.90.2+tod1-0ubuntu1~20.04.10) focal; urgency=medium [ Andy Chi ] * Add support of Goodix fp devices - d/p/goodixmoc-add-PID-0x631C.patch (LP: #1990209) - d/p/goodixmoc-add-PID-0x634C.patch (LP: #1989313) -- Marco Trevisan (Treviño) Mon, 21 Nov 2022 17:01:58 +0100 ** Changed in: libfprint (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1990209 Title: To support Goodix fp device [27C6:631C] Status in OEM Priority Project: Fix Released Status in libfprint package in Ubuntu: New Status in libfprint source package in Focal: Fix Released Status in libfprint source package in Jammy: Fix Released Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/3a8299158600e06b126e72238ebd9156c7f59fc4 This ID is included in upstream. [Impact] * Devices have Goodix [27C6:631C] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [27C6:631C] will be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990209/+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 1990209] Re: To support Goodix fp device [27C6:631C]
** Changed in: oem-priority Status: Fix Committed => Fix Released -- 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/1990209 Title: To support Goodix fp device [27C6:631C] Status in OEM Priority Project: Fix Released Status in libfprint package in Ubuntu: New Status in libfprint source package in Focal: Fix Released Status in libfprint source package in Jammy: Fix Released Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/3a8299158600e06b126e72238ebd9156c7f59fc4 This ID is included in upstream. [Impact] * Devices have Goodix [27C6:631C] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [27C6:631C] will be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990209/+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 1989313] Re: To support Goodix fp device [27C6:634C]
This bug was fixed in the package libfprint - 1:1.94.3+tod1-0ubuntu2~22.04.03 --- libfprint (1:1.94.3+tod1-0ubuntu2~22.04.03) jammy; urgency=medium [ Andy Chi ] * Add new goodix IDs (LP: #1990209 LP: #1989313) - d/p/goodixmoc-add-PID-0x631C.patch - d/p/goodixmoc-add-PID-0x634C.patch -- Marco Trevisan (Treviño) Mon, 21 Nov 2022 19:57:14 +0100 ** Changed in: libfprint (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1989313 Title: To support Goodix fp device [27C6:634C] Status in OEM Priority Project: Fix Committed Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: Fix Committed Status in libfprint source package in Jammy: Fix Released Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/151551b52b006e541e62949706cf491561af9ea1 This ID is included in upstream. [Impact] * Devices have Goodix [27C6:634C] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [27C6:634C] will be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1989313/+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 1990209] Re: To support Goodix fp device [27C6:631C]
This bug was fixed in the package libfprint - 1:1.94.3+tod1-0ubuntu2~22.04.03 --- libfprint (1:1.94.3+tod1-0ubuntu2~22.04.03) jammy; urgency=medium [ Andy Chi ] * Add new goodix IDs (LP: #1990209 LP: #1989313) - d/p/goodixmoc-add-PID-0x631C.patch - d/p/goodixmoc-add-PID-0x634C.patch -- Marco Trevisan (Treviño) Mon, 21 Nov 2022 19:57:14 +0100 ** Changed in: libfprint (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1990209 Title: To support Goodix fp device [27C6:631C] Status in OEM Priority Project: Fix Committed Status in libfprint package in Ubuntu: New Status in libfprint source package in Focal: Fix Committed Status in libfprint source package in Jammy: Fix Released Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/3a8299158600e06b126e72238ebd9156c7f59fc4 This ID is included in upstream. [Impact] * Devices have Goodix [27C6:631C] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [27C6:631C] will be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990209/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
22.10 with latest kernel at the moment (5.19.0-26-generic) speakers still do not work (hp envy 16 Alder Lake-P and Realtek ALC245) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1998444] Re: Backport security fix for CVE-2022-3970
** Changed in: tiff (Ubuntu) Assignee: (unassigned) => David Fernandez Gonzalez (litios) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1998444 Title: Backport security fix for CVE-2022-3970 Status in tiff package in Ubuntu: New Status in tiff source package in Bionic: New Status in tiff source package in Focal: New Status in tiff source package in Jammy: New Status in tiff source package in Kinetic: New Bug description: This CVE patch is desperately needed to fix a build failure caused by a crash in the testsuite of the current libreoffice/kinetic SRU Testing load file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff: *** stack smashing detected ***: terminated Fatal exception: Signal 6 Stack: /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2] /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a] /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc] /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a] /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636] /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386] /lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc] /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1] /lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10] /<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6] /<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5] /<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c] /<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07] /<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f] /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9] /<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5] Aborted (core dumped) make[4]: *** [/<>/solenv/gbuild/CppunitTest.mk:121: /<>/workdir/CppunitTest/vcl_filters_test.test] Error 134 For the log of the failed amd64 kinetic archive build, see https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.3-0ubuntu0.22.10.1/+build/24883181 For the log of the successful amd64 kinetic PPA build with the updated tiff present, see https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+build/24886085 Lunar already includes this fix with the last merge from debian
[Desktop-packages] [Bug 1998444] Re: Backport security fix for CVE-2022-3970
** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1998444 Title: Backport security fix for CVE-2022-3970 Status in tiff package in Ubuntu: New Status in tiff source package in Bionic: New Status in tiff source package in Focal: New Status in tiff source package in Jammy: New Status in tiff source package in Kinetic: New Bug description: This CVE patch is desperately needed to fix a build failure caused by a crash in the testsuite of the current libreoffice/kinetic SRU Testing load file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff: *** stack smashing detected ***: terminated Fatal exception: Signal 6 Stack: /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2] /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a] /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc] /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a] /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636] /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386] /lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc] /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1] /lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10] /<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6] /<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5] /<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c] /<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07] /<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f] /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9] /<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5] Aborted (core dumped) make[4]: *** [/<>/solenv/gbuild/CppunitTest.mk:121: /<>/workdir/CppunitTest/vcl_filters_test.test] Error 134 For the log of the failed amd64 kinetic archive build, see https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.3-0ubuntu0.22.10.1/+build/24883181 For the log of the successful amd64 kinetic PPA build with the updated tiff present, see https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+build/24886085 Lunar already includes this fix with the last merge from debian https://launchpad.net/ubuntu/+source/tiff/4.4.0-6ubuntu1 Presumably this fix is required for all supported
