[Desktop-packages] [Bug 322210] Re: [needs-packaging] PPD for Dymo LabelWriter 400 not complete
I have been using a SUPVAN label maker https://us.supvan.com/ for two years. We were buying blank labels from China and custom-made ink cartridges. The prices were increasing so we looked to source other choices. I am in Canada and do eBay business. We need to print many shipping labels at home every day. Does anybody have any recommendations? -- 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/322210 Title: [needs-packaging] PPD for Dymo LabelWriter 400 not complete Status in cups package in Ubuntu: Invalid Bug description: Binary package hint: cups Release: 8.10 Cups package version: 1.3.9-2ubuntu6.1 I installed Dymo LabelWriter 400 with the Multi-Purpose labels 11354. I chose the only available driver: Dymo Label Printer, 1.3 Problem: I could not set the correct label size as the Multi-Purpose labels are missing from the ppd-file. The result is that I get printouts which do not fit the labels. Solution: I downloaded the driver from the manufacturer and extracted the lines for the Multi-Purpose labels from their ppd-file. drivers page: https://global.dymo.com/enUS/RNW/RNW.html?pg=std_adp.php_faqid=101 driver file: http://www.dymo.com/media/Software/dymo-cups-drivers-1.0.3.tar.gz What should be done is that the ppd-file in cups should be updated with all the labels in the manufacturers ppd. Depending on their license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/322210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 322210] Re: [needs-packaging] PPD for Dymo LabelWriter 400 not complete
I have been using a SUPVAN label maker https://us.supvan.com/ for two years. We were buying blank labels from China and custom-made ink cartridges. The prices were increasing so we looked to source other choices. I am in Canada and do eBay business. We need to print many shipping labels at home every day. Does anybody have any recommendations? -- 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/322210 Title: [needs-packaging] PPD for Dymo LabelWriter 400 not complete Status in cups package in Ubuntu: Invalid Bug description: Binary package hint: cups Release: 8.10 Cups package version: 1.3.9-2ubuntu6.1 I installed Dymo LabelWriter 400 with the Multi-Purpose labels 11354. I chose the only available driver: Dymo Label Printer, 1.3 Problem: I could not set the correct label size as the Multi-Purpose labels are missing from the ppd-file. The result is that I get printouts which do not fit the labels. Solution: I downloaded the driver from the manufacturer and extracted the lines for the Multi-Purpose labels from their ppd-file. drivers page: https://global.dymo.com/enUS/RNW/RNW.html?pg=std_adp.php_faqid=101 driver file: http://www.dymo.com/media/Software/dymo-cups-drivers-1.0.3.tar.gz What should be done is that the ppd-file in cups should be updated with all the labels in the manufacturers ppd. Depending on their license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/322210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
And I just realized the message "invalid value (typically too big)" is
from the Cairo library. It's the description for
CAIRO_STATUS_INVALID_SIZE.
** Also affects: cairo (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cairo (Ubuntu)
Status: New => Triaged
** Changed in: cairo (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in cairo package in Ubuntu:
Triaged
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules/5.19.0-35.36)
All autopkgtests for the newly accepted linux-restricted-modules (5.19.0-35.36) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-lowlatency/5.19.0-1018.19)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency (5.19.0-1018.19) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules- lowlatency [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995305] Re: Cursor blurry with fractional scaling in some apps
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1995305 Title: Cursor blurry with fractional scaling in some apps Status in mutter package in Ubuntu: Confirmed Bug description: When using fractional scaling, the mouse cursor is blurry in some applications. Notably, this includes Settings and Nautilus. See the two screenshots for comparison. I'm on Ubuntu 22.10 on Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1995305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-66.73~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 (5.15.0-66.73~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006675] Re: Memory leak when hdmi switcher is not sending data/not outputting
Your log seems to only be full of bug 1857392. It's quite unusual to see that message every 10-15 seconds so I wonder what's triggering it. Any repeating action like that can cause leaks too. I can also see at least two leak fixes that haven't made it into 20.04 yet: bug 1876641 and bug 1962565. So the next thing you should try is disabling the Ubuntu Dock extension and then log in again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/2006675 Title: Memory leak when hdmi switcher is not sending data/not outputting Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006675] Re: Memory leak when hdmi switcher is not sending data/not outputting
The extensions directory does not exist, so I have no unsupported extensions. Here is the requested log file. ** Attachment added: "gslog.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+attachment/5646014/+files/gslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/2006675 Title: Memory leak when hdmi switcher is not sending data/not outputting Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006590] Re: Xorg freeze after rebooting
*** This bug is a duplicate of bug 1717878 *** https://bugs.launchpad.net/bugs/1717878 Thanks. That shows it is gdm3 crashing, so please: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Xorg freeze after rebooting + gdm3 crashes with SIGTRAP on startup ** Package changed: ubuntu => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2006590 Title: gdm3 crashes with SIGTRAP on startup Status in gdm3 package in Ubuntu: Incomplete Bug description: Suddenly this week, my GUI (ubuntu 22.10) does not open, stuck on the console text. I tried to free some space (by uninstall a app), then to check/update the paquets (dkpg). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.86.01 Wed Oct 26 09:12:38 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Feb 8 12:13:40 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 950M] [1025:1094] InstallationDate: Installed on 2022-05-03 (280 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 25a7:fa23 Areson Technology Corp 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.32 dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 2006590] [NEW] gdm3 crashes with SIGTRAP on startup
You have been subscribed to a public bug: Suddenly this week, my GUI (ubuntu 22.10) does not open, stuck on the console text. I tried to free some space (by uninstall a app), then to check/update the paquets (dkpg). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.86.01 Wed Oct 26 09:12:38 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Feb 8 12:13:40 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 950M] [1025:1094] InstallationDate: Installed on 2022-05-03 (280 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 25a7:fa23 Areson Technology Corp 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.32 dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug freeze kinetic ubuntu -- gdm3 crashes with SIGTRAP on startup https://bugs.launchpad.net/bugs/2006590 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 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 2006675] Re: Memory leak when hdmi switcher is not sending data/not outputting
OK, while it's that size please also collect the latest log messages from gnome-shell by: journalctl -b0 /usr/bin/gnome-shell > gslog.txt and attach the resulting text file here. It might also pay to check for any unsupported extensions in: ~/.local/share/gnome-shell/extensions/ That directory should either be empty or not exist. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/2006675 Title: Memory leak when hdmi switcher is not sending data/not outputting Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules/5.4.0-144.161)
All autopkgtests for the newly accepted linux-restricted-modules (5.4.0-144.161) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841113] Re: Update to 2.13.92
https://launchpad.net/ubuntu/+source/fontconfig/2.14.1-3ubuntu1 ** Changed in: fontconfig (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1841113 Title: Update to 2.13.92 Status in fontconfig package in Ubuntu: Fix Released Bug description: The new version has non trivial changes and needs proper testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1841113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
>One-copy patch does not apply to 111. That is regrettable. I'll do a quick test to see if a higher --fuzz helps, by any chance. Which would be a trivial fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006756] Re: composite emoji shows extra vertical color lines
Hello Jeremy, or anyone else affected, Accepted pango1.0 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pango1.0/1.50.6+ds-2ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pango1.0 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 source package in Jammy: Fix Committed Bug description: Impact -- Composite emoji (such as [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- This is a one line fix cherry-picked from pango 1.50.8 (plus 30+ lines for a test case). pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
One-copy patch does not apply to 111. Beta has just moved 110->111. Thus the next build of beta will fail. ** Tags added: candidate-ok -- 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/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds with minigbm switch to software compositor on amd.
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Bram Stolk (b-stolk) ** Changed in: chromium-browser (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds with minigbm switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
** Tags added: beta-ok candidate-failed dev-failed ** Tags removed: candidate-failed -- 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/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006675] Re: Memory leak when hdmi switcher is not sending data/not outputting
I believe the memory leak still exists. It is now 1.3 GB in size. I was reporting the size given by system monitor in the processes tab, which appears to be physical memory. I don't know the best way of getting all the data, so here is the relevant data about memory size from what I got using ps aux | grep "gnome-shell" USER PID %CPU %MEMVSZ RSSTTY STAT START TIME COMMAND ryan-li+2531 4.3 8.8 5815292 1445944 ?Ssl 01:02 32:02 /usr/bin/gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/2006675 Title: Memory leak when hdmi switcher is not sending data/not outputting Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
Cherry picked to all branches, currently building. ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
** Merge proposal linked: https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/437104 -- 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/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006625] Re: Merge modemmanager 1.20.4-1 (main) from Debian unstable (main)
I've uploaded this to lunar-proposed and unsubscribed ubuntu-sponsors. Please feel free to resubscribe if you have something else that needs to be sponsored. ** Changed in: modemmanager (Ubuntu) Status: New => Fix Committed -- 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/2006625 Title: Merge modemmanager 1.20.4-1 (main) from Debian unstable (main) Status in modemmanager package in Ubuntu: Fix Committed Bug description: Please merge modemmanager 1.20.4-1 (main) from Debian unstable (main) Changelog entries since current lunar version 1.20.0-1ubuntu1: modemmanager (1.20.4-1) unstable; urgency=medium * New upstream version 1.20.4 * d/control: bump Standards-Version, no change required -- Arnaud Ferraris Tue, 03 Jan 2023 13:34:49 +0100 modemmanager (1.20.2-1) unstable; urgency=medium * d/watch: only watch for stable releases. ModemManager has a x.y.z version numbering scheme where y is even for stable releases and odd for development ones. Stable release candidates have x.y-rcz version numbers with y being an even number. This change ensures we only watch for stable releases, including RCs. * New upstream version 1.20.2 * d/patches: drop upstreamed patch -- Arnaud Ferraris Mon, 19 Dec 2022 13:59:08 +0100 Remaining differences with modemmanager from Debian unstable: * Build without libqrtr for now, the MIR is blocked since we don't have hardware available to do the required testing of the feature, include some workarounds to fix the build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2006625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006744] Re: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict
** Package changed: mesa (Ubuntu) => mesa-amber (Ubuntu) -- 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/2006744 Title: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict Status in mesa-amber package in Ubuntu: New Bug description: I enabled lunar-proposed today (with APT::Default-Release "lunar- proposed";) and got the error below during update: Preparing to unpack .../39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Then it will be broken: root@deleteme-lunar:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 22.3.4-1ubuntu1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@deleteme-lunar:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 python3.10-minimal Use 'apt autoremove' to remove them. The following additional packages will be installed: libgl1-mesa-dri The following packages will be upgraded: libgl1-mesa-dri 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62 not fully installed or removed. Need to get 0 B/7806 kB of archives. After this operation, 809 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 81205 files and directories currently installed.) Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Errors were encountered while processing: /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) How to reproduce: 1. Spin up a Lunar VM 2. Enable -proposed 3. Install libgl1-mesa-dri and libgl1-amber-dri 4. Add APT::Default-Release "lunar-proposed"; to /etc/apt/apt.conf.d/somefile 5. Try to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa-amber/+bug/2006744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006628] Re: Merge libqmi 1.32.2-1 (main) from Debian unstable (main)
https://launchpad.net/ubuntu/+source/libqmi/1.32.2-1ubuntu1 ** Changed in: libqmi (Ubuntu) Status: New => Fix Committed ** Changed in: libqmi (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/2006628 Title: Merge libqmi 1.32.2-1 (main) from Debian unstable (main) Status in libqmi package in Ubuntu: Fix Released Bug description: Please merge libqmi 1.32.2-1 (main) from Debian unstable (main) Changelog entries since current lunar version 1.32.0-1ubuntu2: libqmi (1.32.2-1) unstable; urgency=medium * d/watch: only watch for stable releases `libqmi` has a x.y.z version numbering scheme where y is even for stable releases and odd for development ones. Stable release candidates have x.y-rcz version numbers with y being an even number. This change ensures we only watch for stable releases, including RCs. * New upstream version 1.32.2 -- Arnaud Ferraris Mon, 19 Dec 2022 11:51:57 +0100 Remaining differences with libqmi from Debian unstable: * Build without libqrtr for now, the MIR is blocked since we don't have hardware available to do the required testing of the feature, include some workarounds to fix the build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/2006628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006756] Re: composite emoji shows extra vertical color lines
** Description changed: Impact -- Composite emoji (such as [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- - This is a one line fix cherry-picked from pango 1.50.8 + This is a one line fix cherry-picked from pango 1.50.8 (plus 30+ lines for a test case). pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 source package in Jammy: In Progress Bug description: Impact -- Composite emoji (such as [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- This is a one line fix cherry-picked from pango 1.50.8 (plus 30+ lines for a test case). pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990677] Re: Update fonts-noto-color-emoji for Unicode 15
I opened bug 2006756 for the composite emoji display issue (not a regression caused by this update). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Fix Released Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.0/ [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See Debian #788791 for instance. Perhaps this is a bug with font caching. To avoid this bug, it's recommended to restart your computer after applying the update. We are adding a postinst to tell Ubuntu's update-notifier to prompt the user to restart. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] This bug is fixed in the current development release. Fix is released: https://bugs.launchpad.net/ubuntu/+source/fonts-noto- color-emoji/+bug/1989626 This update requires the nototools update to be accepted as a build dependency LP: #1990681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879137] Re: The snap-store is using hundreds of MiBs of RAM.
Hey Guys, I am using Ubuntu 22.04.1 LTS x86_64. The problem still persists. ** Attachment added: "Snap Store High Memory Usage Bug.png" https://bugs.launchpad.net/snap-store-desktop/+bug/1879137/+attachment/5645928/+files/Snap%20Store%20%20High%20Memory%20Usage%20Bug.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1879137 Title: The snap-store is using hundreds of MiBs of RAM. Status in GNOME Software: New Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: The snap-store process is intermittently using hundreds of megabytes of RAM. Is this normal? Is there a solution? Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1879137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006756] [NEW] composite emoji shows extra vertical color lines
Public bug reported: Impact -- Composite emoji (such as [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- This is a one line fix cherry-picked from pango 1.50.8 pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. ** Affects: pango1.0 (Ubuntu) Importance: Low Status: Fix Released ** Affects: pango1.0 (Ubuntu Jammy) Importance: Low Status: In Progress ** Tags: jammy ** Attachment added: "red-black-line-emoji.png" https://bugs.launchpad.net/bugs/2006756/+attachment/5645929/+files/red-black-line-emoji.png ** Also affects: pango1.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: pango1.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: pango1.0 (Ubuntu Jammy) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 source package in Jammy: In Progress Bug description: Impact -- Composite emoji (such as [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- This is a one line fix cherry-picked from pango 1.50.8 pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006754] Re: hdmi audio not working after suspend to ram
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/2006754 Title: hdmi audio not working after suspend to ram Status in alsa-driver package in Ubuntu: New Bug description: Hello I installed a new Kubuntu 22.10 system on a Beelink GTR6 (AMD Ryzen 9 6900HX). Everything is running fine. Except that after a wakeup from a suspend to RAM, there is no more Audio coming through the loudspeakers in my HDMI monitor, although every widget, audio control etc still say that audio is playing. I have not yet found any way to reactivate the audio, except of a complete reboot of the system. I am not sure, how to debug this. I have tried very many recommendations from the net (to restart pipewire, wireplumber, disconnect the HDMI device, open amixer, ...), but none worked. Thanks Michael --- Betriebssystem: Kubuntu 22.10 KDE-Plasma-Version: 5.25.5 KDE-Frameworks-Version: 5.98.0 Qt-Version: 5.15.6 Kernel-Version: 5.19.0-31-generic (64-bit) Grafik-Plattform: X11 Prozessoren: 16 × AMD Ryzen 9 6900HX with Radeon Graphics Speicher: 28.2 GiB Arbeitsspeicher Grafikprozessor: REMBRANDT Hersteller: AZW Produktname: GTR Systemversion: V02 Affected package: No idea, maybe pipewire, wireplumber, but probably a kernel driver Expected result: HDMI audio should work after wakeup from a suspend- to-ram Some output from pw-cli ls: ``` id 0, type PipeWire:Interface:Core/3 object.serial = "0" core.name = "pipewire-0" id 1, type PipeWire:Interface:Module/3 object.serial = "1" module.name = "libpipewire-module-rt" id 2, type PipeWire:Interface:Module/3 object.serial = "2" module.name = "libpipewire-module-protocol-native" id 3, type PipeWire:Interface:Module/3 object.serial = "3" module.name = "libpipewire-module-profiler" id 4, type PipeWire:Interface:Profiler/3 object.serial = "4" id 5, type PipeWire:Interface:Module/3 object.serial = "5" module.name = "libpipewire-module-metadata" id 6, type PipeWire:Interface:Factory/3 object.serial = "6" module.id = "5" factory.name = "metadata" factory.type.name = "PipeWire:Interface:Metadata" factory.type.version = "3" id 7, type PipeWire:Interface:Module/3 object.serial = "7" module.name = "libpipewire-module-spa-device-factory" id 8, type PipeWire:Interface:Factory/3 object.serial = "8" module.id = "7" factory.name = "spa-device-factory" factory.type.name = "PipeWire:Interface:Device" factory.type.version = "3" id 9, type PipeWire:Interface:Module/3 object.serial = "9" module.name = "libpipewire-module-spa-node-factory" id 10, type PipeWire:Interface:Factory/3 object.serial = "10" module.id = "9" factory.name = "spa-node-factory" factory.type.name = "PipeWire:Interface:Node" factory.type.version = "3" id 11, type PipeWire:Interface:Module/3 object.serial = "11" module.name = "libpipewire-module-client-node" id 12, type PipeWire:Interface:Factory/3 object.serial = "12" module.id = "11" factory.name = "client-node" factory.type.name = "PipeWire:Interface:ClientNode" factory.type.version = "4" id 13, type PipeWire:Interface:Module/3 object.serial = "13" module.name = "libpipewire-module-client-device" id 14, type PipeWire:Interface:Factory/3 object.serial = "14" module.id = "13" factory.name = "client-device" factory.type.name = "Spa:Pointer:Interface:Device" factory.type.version = "0" id 15, type PipeWire:Interface:Module/3 object.serial = "15" module.name = "libpipewire-module-portal" id 16, type PipeWire:Interface:Module/3 object.serial = "16" module.name = "libpipewire-module-access" id 17, type PipeWire:Interface:Module/3 object.serial = "17" module.name = "libpipewire-module-adapter" id 18, type PipeWire:Interface:Factory/3 object.serial = "18" module.id = "17" factory.name = "adapter" factory.type.name = "PipeWire:Interface:Node"
[Desktop-packages] [Bug 2006754] [NEW] hdmi audio not working after suspend to ram
You have been subscribed to a public bug: Hello I installed a new Kubuntu 22.10 system on a Beelink GTR6 (AMD Ryzen 9 6900HX). Everything is running fine. Except that after a wakeup from a suspend to RAM, there is no more Audio coming through the loudspeakers in my HDMI monitor, although every widget, audio control etc still say that audio is playing. I have not yet found any way to reactivate the audio, except of a complete reboot of the system. I am not sure, how to debug this. I have tried very many recommendations from the net (to restart pipewire, wireplumber, disconnect the HDMI device, open amixer, ...), but none worked. Thanks Michael --- Betriebssystem: Kubuntu 22.10 KDE-Plasma-Version: 5.25.5 KDE-Frameworks-Version: 5.98.0 Qt-Version: 5.15.6 Kernel-Version: 5.19.0-31-generic (64-bit) Grafik-Plattform: X11 Prozessoren: 16 × AMD Ryzen 9 6900HX with Radeon Graphics Speicher: 28.2 GiB Arbeitsspeicher Grafikprozessor: REMBRANDT Hersteller: AZW Produktname: GTR Systemversion: V02 Affected package: No idea, maybe pipewire, wireplumber, but probably a kernel driver Expected result: HDMI audio should work after wakeup from a suspend-to- ram Some output from pw-cli ls: ``` id 0, type PipeWire:Interface:Core/3 object.serial = "0" core.name = "pipewire-0" id 1, type PipeWire:Interface:Module/3 object.serial = "1" module.name = "libpipewire-module-rt" id 2, type PipeWire:Interface:Module/3 object.serial = "2" module.name = "libpipewire-module-protocol-native" id 3, type PipeWire:Interface:Module/3 object.serial = "3" module.name = "libpipewire-module-profiler" id 4, type PipeWire:Interface:Profiler/3 object.serial = "4" id 5, type PipeWire:Interface:Module/3 object.serial = "5" module.name = "libpipewire-module-metadata" id 6, type PipeWire:Interface:Factory/3 object.serial = "6" module.id = "5" factory.name = "metadata" factory.type.name = "PipeWire:Interface:Metadata" factory.type.version = "3" id 7, type PipeWire:Interface:Module/3 object.serial = "7" module.name = "libpipewire-module-spa-device-factory" id 8, type PipeWire:Interface:Factory/3 object.serial = "8" module.id = "7" factory.name = "spa-device-factory" factory.type.name = "PipeWire:Interface:Device" factory.type.version = "3" id 9, type PipeWire:Interface:Module/3 object.serial = "9" module.name = "libpipewire-module-spa-node-factory" id 10, type PipeWire:Interface:Factory/3 object.serial = "10" module.id = "9" factory.name = "spa-node-factory" factory.type.name = "PipeWire:Interface:Node" factory.type.version = "3" id 11, type PipeWire:Interface:Module/3 object.serial = "11" module.name = "libpipewire-module-client-node" id 12, type PipeWire:Interface:Factory/3 object.serial = "12" module.id = "11" factory.name = "client-node" factory.type.name = "PipeWire:Interface:ClientNode" factory.type.version = "4" id 13, type PipeWire:Interface:Module/3 object.serial = "13" module.name = "libpipewire-module-client-device" id 14, type PipeWire:Interface:Factory/3 object.serial = "14" module.id = "13" factory.name = "client-device" factory.type.name = "Spa:Pointer:Interface:Device" factory.type.version = "0" id 15, type PipeWire:Interface:Module/3 object.serial = "15" module.name = "libpipewire-module-portal" id 16, type PipeWire:Interface:Module/3 object.serial = "16" module.name = "libpipewire-module-access" id 17, type PipeWire:Interface:Module/3 object.serial = "17" module.name = "libpipewire-module-adapter" id 18, type PipeWire:Interface:Factory/3 object.serial = "18" module.id = "17" factory.name = "adapter" factory.type.name = "PipeWire:Interface:Node" factory.type.version = "3" id 19, type PipeWire:Interface:Module/3 object.serial = "19" module.name = "libpipewire-module-link-factory" id 20, type PipeWire:Interface:Factory/3 object.serial = "20" module.id = "19" factory.name = "link-factory" factory.type.name =
[Desktop-packages] [Bug 1992667] Re: Application windows invisible (on DG2 graphics)
22.2 is in jammy-updates ** Changed in: mesa (Ubuntu Jammy) Status: New => Fix Released -- 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/1992667 Title: Application windows invisible (on DG2 graphics) Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-6.0 source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006645] Re: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open
are you saying this is a regression due to the upgrade from 22.0.x to 22.2.x? ** Also affects: mesa (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2006645 Title: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Bug description: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7735#note_1674704 99% sure it's this bug on Mesa's gitlab. Installing the kisak-mesa PPA fixed the issue for me. Any chance of a backport for the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006744] [NEW] libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict
Public bug reported: I enabled lunar-proposed today (with APT::Default-Release "lunar- proposed";) and got the error below during update: Preparing to unpack .../39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Then it will be broken: root@deleteme-lunar:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 22.3.4-1ubuntu1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@deleteme-lunar:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 python3.10-minimal Use 'apt autoremove' to remove them. The following additional packages will be installed: libgl1-mesa-dri The following packages will be upgraded: libgl1-mesa-dri 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62 not fully installed or removed. Need to get 0 B/7806 kB of archives. After this operation, 809 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 81205 files and directories currently installed.) Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Errors were encountered while processing: /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) How to reproduce: 1. Spin up a Lunar VM 2. Enable -proposed 3. Install libgl1-mesa-dri and libgl1-amber-dri 4. Add APT::Default-Release "lunar-proposed"; to /etc/apt/apt.conf.d/somefile 5. Try to upgrade ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/2006744 Title: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict Status in mesa package in Ubuntu: New Bug description: I enabled lunar-proposed today (with APT::Default-Release "lunar- proposed";) and got the error below during update: Preparing to unpack .../39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Then it will be broken: root@deleteme-lunar:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 22.3.4-1ubuntu1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@deleteme-lunar:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 python3.10-minimal Use 'apt autoremove' to remove them. The following additional packages will be installed: libgl1-mesa-dri The following packages will be upgraded: libgl1-mesa-dri 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62 not fully installed or removed. Need to get 0 B/7806 kB of archives. After this operation, 809 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 81205 files and directories currently installed.) Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking
[Desktop-packages] [Bug 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
ACK on the debdiff in comment #8. I have slightly adjusted it to add the bug number to the changelog and to fix the urls in the patch. I have uploaded it to the security team PPA here: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa Please test it to make sure it works properly, and comment back in this bug, at which point I will release it as a security update. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: In Progress Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 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: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006645] Re: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open
I'm on Jammy. Sorry I thought I filed against the Jammy package -- 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/2006645 Title: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open Status in mesa package in Ubuntu: Fix Committed Bug description: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7735#note_1674704 99% sure it's this bug on Mesa's gitlab. Installing the kisak-mesa PPA fixed the issue for me. Any chance of a backport for the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006674] Re: GTK-3.0 themes not working with 22.04
** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** No longer affects: sssd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2006674 Title: GTK-3.0 themes not working with 22.04 Status in gtk4 package in Ubuntu: New Bug description: I am trying to migrate my customized theme on ubuntu 22.04 , but it is not taking effect . I read through different portals and found that in 22.04 themes are migrated to gtk-4.0 and there should be a folder present with the name gtk-4.0 inside the theme. I tried migrating my gtk-3.0 to gtk-4.0 but still not able to apply the theme . Can you please help me out are their any specific steps which needs to be done for migrating my customized theme. I am trying to change the color of the dialog which comes if we are closing any unsaved file from red to blue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2006674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
> your first log contains this error Indeed, I forced a error out with sys.exit[1] when it reached that step just so as to not waste time building the whole thing. Since you'll be working on that, I'm reassigning. [1] https://git.launchpad.net/~nteodosio/chromium- browser/commit/?id=5e90d5716f7214ce6e2818572c218ef95ae3e798 ** Tags removed: patch ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Triaged ** Changed in: chromium-browser (Ubuntu) Assignee: Nathan Teodosio (nteodosio) => Bram Stolk (b-stolk) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: Triaged Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979412] Re: [snap] Chromium crashes when downloading
** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1979412 Title: [snap] Chromium crashes when downloading Status in chromium-browser package in Ubuntu: Confirmed Bug description: For a couple of weeks, I observe random crashes of Chromium when you click on a link that starts a non-HTML download (e.g. PDF or an MS Excel file). After restarting Chromium and restoring the tabs, a second click on the link starts the download without problems, probably because this issue is not 100% reproducible in the first place. Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit) on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1979412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004037] Re: Ubuntu Pro: Changing network state wreaks havoc
This bug was fixed in the package gnome-initial-setup - 42.0.1-1ubuntu2.2 --- gnome-initial-setup (42.0.1-1ubuntu2.2) jammy; urgency=medium [ Nathan Teodosio ] * debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch: - fix an incorrect pointer use in the connectivity callback (lp: #2004037) -- Sebastien Bacher Tue, 31 Jan 2023 09:10:36 +0100 ** Changed in: gnome-initial-setup (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2004037 Title: Ubuntu Pro: Changing network state wreaks havoc Status in gnome-initial-setup package in Ubuntu: Fix Released Status in gnome-initial-setup source package in Jammy: Fix Released Bug description: * Impact Changing the connection state in Ubuntu Pro pages wreaks havoc in the program, often leading to segmentation faults. This is caused by the pass of the wrong pointer to the network state change callback. * Testcase Use the testcase on bug #2003231 to validate the Ubuntu Pro workflow, while on the Ubuntu Pro page change the connectivity, the UI should adapt without crashing * Regression Potential The patch is a pointer change in the connectivity callback from the Ubuntu Pro page so if a bug was introduced it would be on that screen and having to do with connectivity changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2004037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006719] Re: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/2006719 Title: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 109.0.1+build1-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-52.58~20.04.1-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: digtrg 883 F pulseaudio /dev/snd/controlC0: digtrg 883 F pulseaudio BuildID: 20230127170202 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Feb 9 13:46:02 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-08-22 (171 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.5.252 dev wlx8416f90f32a4 proto dhcp metric 600 169.254.0.0/16 dev wlx8416f90f32a4 scope link metric 1000 192.168.5.0/24 dev wlx8416f90f32a4 proto kernel scope link src 192.168.5.90 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-02-09 (0 days ago) dmi.bios.date: 06/02/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0327 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81-M1 dmi.board.vendor: Acer dmi.board.version: 1.02 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: PEGATRON CORPORATION dmi.chassis.version: 1.02 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0327:bd06/02/2016:br4.6:svnAcer:pnVeritonM200-H81:pvr1.02:rvnAcer:rnH81-M1:rvr1.02:cvnPEGATRONCORPORATION:ct3:cvr1.02:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Veriton M200-H81 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2006719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006719] [NEW] package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Public bug reported: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 109.0.1+build1-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-52.58~20.04.1-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: digtrg 883 F pulseaudio /dev/snd/controlC0: digtrg 883 F pulseaudio BuildID: 20230127170202 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Feb 9 13:46:02 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-08-22 (171 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.5.252 dev wlx8416f90f32a4 proto dhcp metric 600 169.254.0.0/16 dev wlx8416f90f32a4 scope link metric 1000 192.168.5.0/24 dev wlx8416f90f32a4 proto kernel scope link src 192.168.5.90 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-02-09 (0 days ago) dmi.bios.date: 06/02/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0327 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81-M1 dmi.board.vendor: Acer dmi.board.version: 1.02 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: PEGATRON CORPORATION dmi.chassis.version: 1.02 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0327:bd06/02/2016:br4.6:svnAcer:pnVeritonM200-H81:pvr1.02:rvnAcer:rnH81-M1:rvr1.02:cvnPEGATRONCORPORATION:ct3:cvr1.02:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Veriton M200-H81 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.02 dmi.sys.vendor: Acer ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2006719 Title: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 109.0.1+build1-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-52.58~20.04.1-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: digtrg 883 F pulseaudio /dev/snd/controlC0: digtrg 883 F pulseaudio BuildID: 20230127170202 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Feb 9 13:46:02 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-08-22 (171 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.5.252 dev wlx8416f90f32a4 proto dhcp metric 600 169.254.0.0/16 dev wlx8416f90f32a4 scope link metric 1000 192.168.5.0/24 dev wlx8416f90f32a4 proto kernel scope link src 192.168.5.90 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-02-09 (0 days ago) dmi.bios.date: 06/02/2016 dmi.bios.release: 4.6
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
** Changed in: chromium-browser (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: In Progress Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006645] Re: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open
lunar proposed is currently at 22.3.4-1ubuntu1 . ** Changed in: mesa (Ubuntu) Status: New => Fix Committed -- 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/2006645 Title: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open Status in mesa package in Ubuntu: Fix Committed Bug description: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7735#note_1674704 99% sure it's this bug on Mesa's gitlab. Installing the kisak-mesa PPA fixed the issue for me. Any chance of a backport for the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006645] Re: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open
The fix commit should be in https://gitlab.freedesktop.org/mesa/mesa/-/commit/381de3c809fce5427308c696bbd313360194eff4 which is applied in mesa 22.3.1+ and 23.0.0+. Which Ubuntu version are you using? -- 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/2006645 Title: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open Status in mesa package in Ubuntu: Fix Committed Bug description: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7735#note_1674704 99% sure it's this bug on Mesa's gitlab. Installing the kisak-mesa PPA fixed the issue for me. Any chance of a backport for the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006586] Re: Ubuntu Pro: Segmentation faults when quit gnome-initial-setup
Thanks, that's basically bug #2004518, I've nagged the SRU team to get the corresponding upload accepted. I'm just curious but why is exiting the wizard from the context menu an oem priority? ** Changed in: gnome-initial-setup (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2006586 Title: Ubuntu Pro: Segmentation faults when quit gnome-initial-setup Status in OEM Priority Project: New Status in gnome-initial-setup package in Ubuntu: Invalid Bug description: Click 'Quit' from applications menu directly after the gnome-initial-setup show, then this issue will be reproduced. ubuntu: 22.04.1 gnome-initial-setup: 42.0.1-1ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2006586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
