[Desktop-packages] [Bug 2028864] Re: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64)
I suspect this is a general problem with Nvidia proprietary drivers being accessible in snaps. Not Tegra-specific. First we will need apps to start using graphics-core22 instead of gnome-42-2204 to get OpenGL support. It might help if gnome-42-2204 is ported to use graphics-core22 first. Second we'll want to verify that amd64 apps can now use nvidia-core22. Third someone will need to add Tegra support to arm64 builds of nvidia- core22. That's probably better than creating a whole new 'tegra-core22' snap? ** Tags added: arm64 nvidia snap tegra -- 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/2028864 Title: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64) Status in chromium-browser package in Ubuntu: New Bug description: Tegra Orin platforms come in various flavor / dev kit. They all ship with a 'slightly' customized Ubuntu image. One of the customization is the addition of the Nvidia GPU drivers for Tegra. When running chromium browser debian package (either when running 18.04, or when running 22.04 with the package fetched from this PPA: https://launchpad.net/~nteodosio/+archive/ubuntu/chromium/+packages) then chromium works with hardware acceleration, as reported in chrome://gpu: Graphics Feature Status Canvas: Hardware accelerated Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Hardware accelerated Multiple Raster Threads: Enabled OpenGL: Enabled Rasterization: Hardware accelerated Raw Draw: Disabled Video Decode: Hardware accelerated Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated WebGPU: Disabled When using the snap version of chromium browser (on either 20.04 or 22.04), hardware acceleration is disabled, as shown in chrome://gpu: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Software only. Hardware acceleration disabled Multiple Raster Threads: Enabled OpenGL: Disabled Rasterization: Software only. Hardware acceleration disabled Raw Draw: Disabled Skia Graphite: Disabled Video Decode: Software only. Hardware acceleration disabled Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Software only, hardware acceleration unavailable WebGL2: Software only, hardware acceleration unavailable WebGPU: Disabled Problems Detected WebGPU has been disabled via blocklist or the command line. Disabled Features: webgpu Accelerated video encode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_encode Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable. Disabled Features: gpu_compositing These tests are done with X11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887172] Re: [snap] Hardware accelerated video decoding does not work with nvidia proprietary drivers
Retitled to clarify that we're probably not expecting the Nvidia driver to ever support VA-API. It would be VDPAU support in Chromium instead per comment #1. ** Summary changed: - [snap] VA-API does not work with nvidia proprietary drivers + [snap] Hardware accelerated video decoding does not work with nvidia proprietary drivers -- 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/1887172 Title: [snap] Hardware accelerated video decoding does not work with nvidia proprietary drivers Status in chromium-browser package in Ubuntu: Triaged Bug description: After installing the candidate/vaapi channel, I still do not get hardware acceleration for video decoding from my NVIDIA gpu, see: ``` $ LIBVA_MESSAGING_LEVEL=2 snap run chromium Gtk-Message: 09:07:37.215: Failed to load module "canberra-gtk-module" Gtk-Message: 09:07:37.216: Failed to load module "canberra-gtk-module" libva info: VA-API version 1.7.0 libva info: Trying to open /snap/chromium/1191/usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so libva info: va_openDriver() returns -1 [141337:141337:0710/090737.297551:ERROR:vaapi_wrapper.cc(480)] vaInitialize failed: unknown libva error ``` For me, I am on Focal, so I had to manually install the vdpau-va- driver from cosmic from https://launchpad.net/ubuntu/+source/vdpau- video/0.7.4-7, (presumably on i.e. 18.04 I could just have installed it with apt install), which provides the various files in /var/lib/snapd/gl/vdpau, and then I also had to add that package along with libvdpau1 into the chromium snap, at which point it loads the libraries but I then run into very relevant errors: ``` libva info: VA-API version 1.7.0 libva info: Trying to open /snap/chromium/x3/usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 [121136:121136:0710/082840.674481:ERROR:vaapi_wrapper.cc(900)] vaQuerySurfaceAttributes failed, VA error: invalid parameter [121136:121136:0710/082840.674608:ERROR:vaapi_wrapper.cc(789)] FillProfileInfo_Locked failed for va_profile VAProfileMPEG2Simple and entrypoint 1 [121136:121136:0710/082840.674647:ERROR:vaapi_wrapper.cc(900)] vaQuerySurfaceAttributes failed, VA error: invalid parameter [121136:121136:0710/082840.674680:ERROR:vaapi_wrapper.cc(789)] FillProfileInfo_Locked failed for va_profile VAProfileMPEG2Main and entrypoint 1 [121136:121136:0710/082840.674709:ERROR:vaapi_wrapper.cc(900)] vaQuerySurfaceAttributes failed, VA error: invalid parameter [121136:121136:0710/082840.674739:ERROR:vaapi_wrapper.cc(789)] FillProfileInfo_Locked failed for va_profile VAProfileMPEG4Simple and entrypoint 1 [121136:121136:0710/082840.674791:ERROR:vaapi_wrapper.cc(900)] vaQuerySurfaceAttributes failed, VA error: invalid parameter [121136:121136:0710/082840.674817:ERROR:vaapi_wrapper.cc(789)] FillProfileInfo_Locked failed for va_profile VAProfileMPEG4AdvancedSimple and entrypoint 1 [121136:121136:0710/082840.674844:ERROR:vaapi_wrapper.cc(900)] vaQuerySurfaceAttributes failed, VA error: invalid parameter [121136:121136:0710/082840.674870:ERROR:vaapi_wrapper.cc(789)] FillProfileInfo_Locked failed for va_profile VAProfileH264Baseline and entrypoint 1 [121136:121136:0710/082840.674896:ERROR:vaapi_wrapper.cc(900)] vaQuerySurfaceAttributes failed, VA error: invalid parameter [121136:121136:0710/082840.674920:ERROR:vaapi_wrapper.cc(789)] FillProfileInfo_Locked failed for va_profile VAProfileH264Main and entrypoint 1 [121136:121136:0710/082840.674946:ERROR:vaapi_wrapper.cc(900)] vaQuerySurfaceAttributes failed, VA error: invalid parameter [121136:121136:0710/082840.674971:ERROR:vaapi_wrapper.cc(789)] FillProfileInfo_Locked failed for va_profile VAProfileH264High and entrypoint 1 [121136:121136:0710/082840.674996:ERROR:vaapi_wrapper.cc(900)] vaQuerySurfaceAttributes failed, VA error: invalid parameter [121136:121136:0710/082840.675020:ERROR:vaapi_wrapper.cc(789)] FillProfileInfo_Locked failed for va_profile VAProfileVC1Simple and entrypoint 1 [121136:121136:0710/082840.675046:ERROR:vaapi_wrapper.cc(900)] vaQuerySurfaceAttributes failed, VA error: invalid parameter [121136:121136:0710/082840.675073:ERROR:vaapi_wrapper.cc(789)] FillProfileInfo_Locked failed for va_profile VAProfileVC1Main and entrypoint 1 [121136:121136:0710/082840.675097:ERROR:vaapi_wrapper.cc(900)] vaQuerySurfaceAttributes failed, VA error: invalid parameter [121136:121136:0710/082840.675122:ERROR:vaapi_wrapper.cc(789)] FillProfileInfo_Locked failed for va_profile VAProfileVC1Advanced and entrypoint 1 ``` at which point I am stuck trying to get it to work. FWIW, this is with ubuntu 20.04, snapd 2.45.1, nvidia drivers 440, and X11 with gdm. Also I had to modify the desktop-launch script with this PR:
[Desktop-packages] [Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: * "$HOME/.config/monitors.xml" is not installed by default in Ubuntu during the installation at this writing, you have to generate it by running the GUI preferences `$ gnome-control-center display` for GNOME, and `$ mate-display-properties` for MATE. * Both GNOME and MATE can be run on the same distro, which causes compatibility issues with monitors.xml: monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name for MATE is defined at https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and for GNOME it is defined at https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008. Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour - monitors.xml in Ubuntu 23.04, and 22.04: + monitors.xml in Ubuntu 23.10, 23.04, and 22.04: ``` - - - 0 - 0 - 1 - yes - - - Virtual-1 - unknown - unknown - unknown - - - 1600 - 900 - 60.000 - - - - + + + 0 + 0 + 1 + yes + + + Virtual-1 + unknown + unknown + unknown + + + 1600 + 900 + 60.000 + + + + ``` monitors.xml in Ubuntu 22.04 (with ubuntu-mate-desktop installed), or 23.04 (with ubuntu-mate-desktop installed): ``` - - - - 0 - 0 - yes - - - Virtual-1 - ??? - 0x - 0x - - - 1600 - 900 - 60.000 - - - - - - - 0 - 0 - 1 - yes - - - Virtual-1 - unknown - unknown - unknown - - - 1280 - 800 - 59.810 - - - - + + + + 0 + 0 + yes + + + Virtual-1 + ??? + 0x + 0x + + + 1600 + 900 + 60.000 + + + + + + + 0 + 0 + 1 + yes + + + Virtual-1 + unknown + unknown + unknown + + + 1280 + 800 + 59.810 + + + + ``` monitors.xml in Ubuntu MATE 22.04, Ubuntu MATE 23.04, ubuntu-mate-desktop from Ubuntu 22.04, or ubuntu-mate-desktop from Ubuntu 23.04: ``` - - no - - ??? - 0x - 0x - 1600 - 900 - 60 - 0 - 0 - normal - no - no - yes - - - - - - - - + + no + + ??? + 0x + 0x + 1600 + 900 + 60 + 0 + 0 + normal + no + no + yes + + + + + + + + ``` Steps to reproduce the behaviour Steps I used to reproduce the issue in Ubuntu 22.04 with ubuntu-mate-desktop installed: * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Log out, and log in to MATE. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will generate "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, the screen resolution (1600x900 configured in MATE) not used by GNOME (https://github.com/mate-desktop/mate-control-center/assets/6416073/1b978bd7-22dd-4b42-a5b5-d32ec2d42f21), instead a fallback resolution is used. * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) move "$HOME/.config/monitors.xml" (that was generated by MATE) to "$HOME/.config/monitors-v1-backup.xml" 2) generate a new "$HOME/.config/monitors.xml" 3) Change the screen resolution directly (https://github.com/mate-desktop/mate-control-center/assets/6416073/6a841086-6936-4a21-9d43-ca1a605a9806). Close the window. *
[Desktop-packages] [Bug 2013542] Re: [lunar] windows size/position is not saved for some apps
** Tags added: regression-release ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2013542 Title: [lunar] windows size/position is not saved for some apps Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Hi, Lunar up to date, Ubuntu session, Wayland or X11 1) open Synaptic not in full screen 2) change window size to full screen 3) close Synaptic 4) open Synaptic 5) its window is not maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028853] Re: Window management - window size and state is not restored
*** This bug is a duplicate of bug 2013542 *** https://bugs.launchpad.net/bugs/2013542 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2013542, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: lunar ** This bug has been marked a duplicate of bug 2013542 [lunar] windows size/position is not saved for some apps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2028853 Title: Window management - window size and state is not restored Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 23.04 gnome-shell 44.2 X11 When maximizing a window like i.e. Nemo or Evolution and closing it, starting the app again leads to an unmaximized window. This behaviour is always the same within one session or after reboot. Firefox (not snap! but .deb install) for instance just shows this behaviour after a session restart/reboot. Within the session it remembers the window size and state. I expect that the window size of the last state before closing is restored after starting the app again. That was the normal behaviour until the upgrade to 23.04. 44.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 100 /var/lib/dpkg/status 44.0-2ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu lunar/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2028853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028888] Re: No web browser installed in the canary image
** Summary changed: - Can't use ubuntu-bug in the canary image + No web browser installed in the canary image -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/202 Title: No web browser installed in the canary image Status in ubuntu-meta package in Ubuntu: New Bug description: ubuntu-bug wants to launch a web browser but there isn't one available in the mantic-desktop-canary iso. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028888] [NEW] No web browser installed in the canary image
Public bug reported: ubuntu-bug wants to launch a web browser but there isn't one available in the mantic-desktop-canary iso. See the attached screenshot. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: cuqa-manual-testing rls-mm-incoming ** Attachment added: "Screenshot from 2023-07-27 14-29-33.png" https://bugs.launchpad.net/bugs/202/+attachment/5688911/+files/Screenshot%20from%202023-07-27%2014-29-33.png ** Tags added: cuqa-manual-testing ** Tags added: rls-mm-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/202 Title: No web browser installed in the canary image Status in ubuntu-meta package in Ubuntu: New Bug description: ubuntu-bug wants to launch a web browser but there isn't one available in the mantic-desktop-canary iso. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Apparmor in jammy-proposed has the necessary changes, we just need a new evince upload to jammy without the recommends then. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Committed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028887] Re: package libreoffice-impress 1:7.3.7-0ubuntu0.22.04.3 failed to install/upgrade: installed libreoffice-impress package post-installation script subprocess returned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2028887 Title: package libreoffice-impress 1:7.3.7-0ubuntu0.22.04.3 failed to install/upgrade: installed libreoffice-impress package post- installation script subprocess returned error exit status 128 Status in libreoffice package in Ubuntu: New Bug description: after re-install from older 22.04-ppatchlevel and update via Aktualisierungsverwaltung ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-impress 1:7.3.7-0ubuntu0.22.04.3 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 27 12:16:28 2023 DuplicateSignature: package:libreoffice-impress:1:7.3.7-0ubuntu0.22.04.3 Setting up libreoffice-impress (1:7.3.7-0ubuntu0.22.04.3) ... dpkg: error processing package libreoffice-impress (--configure): installed libreoffice-impress package post-installation script subprocess returned error exit status 128 ErrorMessage: installed libreoffice-impress package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2023-07-27 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: libreoffice Title: package libreoffice-impress 1:7.3.7-0ubuntu0.22.04.3 failed to install/upgrade: installed libreoffice-impress package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2028887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028887] [NEW] package libreoffice-impress 1:7.3.7-0ubuntu0.22.04.3 failed to install/upgrade: installed libreoffice-impress package post-installation script subprocess returne
Public bug reported: after re-install from older 22.04-ppatchlevel and update via Aktualisierungsverwaltung ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-impress 1:7.3.7-0ubuntu0.22.04.3 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 27 12:16:28 2023 DuplicateSignature: package:libreoffice-impress:1:7.3.7-0ubuntu0.22.04.3 Setting up libreoffice-impress (1:7.3.7-0ubuntu0.22.04.3) ... dpkg: error processing package libreoffice-impress (--configure): installed libreoffice-impress package post-installation script subprocess returned error exit status 128 ErrorMessage: installed libreoffice-impress package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2023-07-27 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: libreoffice Title: package libreoffice-impress 1:7.3.7-0ubuntu0.22.04.3 failed to install/upgrade: installed libreoffice-impress package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2028887 Title: package libreoffice-impress 1:7.3.7-0ubuntu0.22.04.3 failed to install/upgrade: installed libreoffice-impress package post- installation script subprocess returned error exit status 128 Status in libreoffice package in Ubuntu: New Bug description: after re-install from older 22.04-ppatchlevel and update via Aktualisierungsverwaltung ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-impress 1:7.3.7-0ubuntu0.22.04.3 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 27 12:16:28 2023 DuplicateSignature: package:libreoffice-impress:1:7.3.7-0ubuntu0.22.04.3 Setting up libreoffice-impress (1:7.3.7-0ubuntu0.22.04.3) ... dpkg: error processing package libreoffice-impress (--configure): installed libreoffice-impress package post-installation script subprocess returned error exit status 128 ErrorMessage: installed libreoffice-impress package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2023-07-27 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: libreoffice Title: package libreoffice-impress 1:7.3.7-0ubuntu0.22.04.3 failed to install/upgrade: installed libreoffice-impress package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2028887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1971984] Update Released
Thank you Andreas, the Ubuntu bug Team did a great job. Op do 27 jul 2023 om 22:31 schreef Andreas Hasenack < 1971...@bugs.launchpad.net>: > The verification of the Stable Release Update for pcsc-lite has > completed successfully and the package is now being released to > -updates. Subsequently, the Ubuntu Stable Release Updates Team is being > unsubscribed and will not receive messages about this bug report. In > the event that you encounter a regression using the package from > -updates please report a new bug using ubuntu-bug and tag the bug report > regression-update so we can easily find any regressions. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1971984 > > Title: > pcscd.socket is disabled after installation > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Released Status in pcsc-lite source package in Kinetic: Won't Fix Status in pcsc-lite source package in Lunar: Fix Released Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028886] [NEW] gnome-control-center wifi , crashes selecting wifi adapters for hidden networks
Public bug reported: Have two wifi adapters, PCI and USB. When selecting the 2nd adapter from the hidden networks options this causes a crash. I can use other tools like nmtui and wifi works fine, so this is an issue with the parser of this particular service? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 27 13:19:23 2023 InstallationDate: Installed on 2021-12-14 (590 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 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "scipt/log of events" https://bugs.launchpad.net/bugs/2028886/+attachment/5688901/+files/gnome-control-center-wifi-crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028886 Title: gnome-control-center wifi , crashes selecting wifi adapters for hidden networks Status in gnome-control-center package in Ubuntu: New Bug description: Have two wifi adapters, PCI and USB. When selecting the 2nd adapter from the hidden networks options this causes a crash. I can use other tools like nmtui and wifi works fine, so this is an issue with the parser of this particular service? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 27 13:19:23 2023 InstallationDate: Installed on 2021-12-14 (590 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 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
This bug was fixed in the package pcsc-lite - 1.9.5-3ubuntu1 --- pcsc-lite (1.9.5-3ubuntu1) jammy; urgency=medium * Fix dh_installsystemd doesn't handle files in /usr/lib/systemd/system. Closes: #103429 and LP: #1971984 -- Brian Murray Tue, 27 Jun 2023 16:46:08 -0700 ** Changed in: pcsc-lite (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Released Status in pcsc-lite source package in Kinetic: Won't Fix Status in pcsc-lite source package in Lunar: Fix Released Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Update Released
The verification of the Stable Release Update for pcsc-lite has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Released Status in pcsc-lite source package in Kinetic: Won't Fix Status in pcsc-lite source package in Lunar: Fix Released Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
This bug was fixed in the package pcsc-lite - 1.9.9-1ubuntu0.23.04.1 --- pcsc-lite (1.9.9-1ubuntu0.23.04.1) lunar; urgency=medium * Fix dh_installsystemd doesn't handle files in /usr/lib/systemd/system. Closes: #103429 and LP: #1971984 -- Brian Murray Tue, 27 Jun 2023 16:29:54 -0700 ** Changed in: pcsc-lite (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Released Status in pcsc-lite source package in Kinetic: Won't Fix Status in pcsc-lite source package in Lunar: Fix Released Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Tags removed: verification-needed verification-needed-kinetic verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Committed Status in pcsc-lite source package in Kinetic: Won't Fix Status in pcsc-lite source package in Lunar: Fix Committed Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
I tested this update in Lunar (both a fresh install from -proposed and an upgrade to -proposed) and confirm that the socket is enabled: Do you want to continue? [Y/n] Y Get:1 http://192.168.10.7/ubuntu lunar-proposed/universe amd64 pcscd amd64 1.9.9-1ubuntu0.23.04.1 [58.6 kB] Get:2 http://192.168.10.7/ubuntu lunar-proposed/main amd64 libpcsclite1 amd64 1.9.9-1ubuntu0.23.04.1 [20.5 kB] Fetched 79.1 kB in 0s (679 kB/s) (Reading database ... 241412 files and directories currently installed.) Preparing to unpack .../pcscd_1.9.9-1ubuntu0.23.04.1_amd64.deb ... Unpacking pcscd (1.9.9-1ubuntu0.23.04.1) over (1.9.9-1) ... Preparing to unpack .../libpcsclite1_1.9.9-1ubuntu0.23.04.1_amd64.deb ... Unpacking libpcsclite1:amd64 (1.9.9-1ubuntu0.23.04.1) over (1.9.9-1) ... Setting up libpcsclite1:amd64 (1.9.9-1ubuntu0.23.04.1) ... Setting up pcscd (1.9.9-1ubuntu0.23.04.1) ... Created symlink /etc/systemd/system/sockets.target.wants/pcscd.socket \u2192 /lib/systemd/system/pcscd.socket. pcscd.service is a disabled or a static unit not running, not starting it. Processing triggers for libc-bin (2.37-0ubuntu2) ... Processing triggers for man-db (2.11.2-1) ... bdmurray@clean-lunar-amd64:~$ systemctl status pcscd.socket \u25cf pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; enabled; preset: enabled) Active: active (listening) since Thu 2023-07-27 12:31:53 PDT; 20s ago Until: Thu 2023-07-27 12:31:53 PDT; 20s ago Triggers: \u25cf pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) CGroup: /system.slice/pcscd.socket Jul 27 12:31:53 clean-lunar-amd64 systemd[1]: Listening on pcscd.socket - PC/SC Smart Card Daemon Activation Socket. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Committed Status in pcsc-lite source package in Kinetic: Won't Fix Status in pcsc-lite source package in Lunar: Fix Committed Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993154] Re: Sane genesys 1.0.29 and later drive HP Scanjet 3670 motor beyond limits
Has there been a fix issued to resolve this problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1993154 Title: Sane genesys 1.0.29 and later drive HP Scanjet 3670 motor beyond limits Status in sane-backends package in Ubuntu: Confirmed Bug description: [Impact] When using scan-image with a HP ScanJet 3670 scanner under Xubuntu Jammy 22.04 at 300 dpi or more, the scanner motor is incorrectly driven by the driver: - when scanning an A4 page, the driver attempts to drive motor out of limits at the bottom of the page, resulting in a grinding sound. - the resulting image misses horizontal stripes. - the resulting image has an incorrect aspect ratio (it should be bigger in the vertical dimension). This doesn't happen under Xubuntu Xenial 16.04 (64 bit). This is a serious regression. [Test case] - install Xubuntu Jammy - install sane package - install flatbed scanner HP ScanJet 3670 - run Document Scanner in "Image" mode with default parameters (resulting in a full-size, color, 300 dpi scan) - check scanner noise at bottom of document and resulting image [Analysis] Genesys driver under Jammy is libsane-genesys.so.1.1.1 Genesys driver under Xenial is libsane-genesys.so.1.0.25 This library has been entirely changed between releases 1.0.28 (which is written in C) and 1.0.29 (which has been relocated in its own subdir and is written in C++). When libsane-genesys.so.1.0.25 is copied to Jammy environment and symlink libsane-genesys.so.1 is adjusted to make it point at this file, the problem disappears entirely, the scanner works as expected and the resulting image is fine. When libsane-genesys.so.1.0.29 is copied to Jammy environment and symlink libsane-genesys.so.1 is adjusted to make it point at this file, the problem appears again. Please note that other files haven't been modified and belong to Jammy's version 1.1.1. Therefore, it is likely that something has been broken between versions 1.0.28 and 1.0.29 of libsane-genesys.so, when converting its sources from C to C++. [Details] OS version: Ubuntu 22.04.1 LTS Packages versions: libsane1 1.1.1-5 Log file attached for Jammy case (will attach Xenial case in a later step if possible). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1993154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993154] Re: Sane genesys 1.0.29 and later drive HP Scanjet 3670 motor beyond limits
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1993154 Title: Sane genesys 1.0.29 and later drive HP Scanjet 3670 motor beyond limits Status in sane-backends package in Ubuntu: Confirmed Bug description: [Impact] When using scan-image with a HP ScanJet 3670 scanner under Xubuntu Jammy 22.04 at 300 dpi or more, the scanner motor is incorrectly driven by the driver: - when scanning an A4 page, the driver attempts to drive motor out of limits at the bottom of the page, resulting in a grinding sound. - the resulting image misses horizontal stripes. - the resulting image has an incorrect aspect ratio (it should be bigger in the vertical dimension). This doesn't happen under Xubuntu Xenial 16.04 (64 bit). This is a serious regression. [Test case] - install Xubuntu Jammy - install sane package - install flatbed scanner HP ScanJet 3670 - run Document Scanner in "Image" mode with default parameters (resulting in a full-size, color, 300 dpi scan) - check scanner noise at bottom of document and resulting image [Analysis] Genesys driver under Jammy is libsane-genesys.so.1.1.1 Genesys driver under Xenial is libsane-genesys.so.1.0.25 This library has been entirely changed between releases 1.0.28 (which is written in C) and 1.0.29 (which has been relocated in its own subdir and is written in C++). When libsane-genesys.so.1.0.25 is copied to Jammy environment and symlink libsane-genesys.so.1 is adjusted to make it point at this file, the problem disappears entirely, the scanner works as expected and the resulting image is fine. When libsane-genesys.so.1.0.29 is copied to Jammy environment and symlink libsane-genesys.so.1 is adjusted to make it point at this file, the problem appears again. Please note that other files haven't been modified and belong to Jammy's version 1.1.1. Therefore, it is likely that something has been broken between versions 1.0.28 and 1.0.29 of libsane-genesys.so, when converting its sources from C to C++. [Details] OS version: Ubuntu 22.04.1 LTS Packages versions: libsane1 1.1.1-5 Log file attached for Jammy case (will attach Xenial case in a later step if possible). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1993154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
This is missing a lunar verification before jammy (already verified) can be released. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Committed Status in pcsc-lite source package in Kinetic: Won't Fix Status in pcsc-lite source package in Lunar: Fix Committed Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023400] Re: Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2023400 Title: Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification Status in Mozilla Thunderbird: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: When I receive an e-mail, a notification appears. I click it in order for Thunderbird to open on the correct e-mail. But Thunderbird doesn't open right away, a new notification "'Thunderbird' is ready" appears, which I have to click in order for Thunderbird to open correctly. Related : https://bugzilla.mozilla.org/show_bug.cgi?id=1745714 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:31:36 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 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: https://bugs.launchpad.net/thunderbird/+bug/2023400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023400] Re: Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2023400 Title: Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification Status in Mozilla Thunderbird: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: When I receive an e-mail, a notification appears. I click it in order for Thunderbird to open on the correct e-mail. But Thunderbird doesn't open right away, a new notification "'Thunderbird' is ready" appears, which I have to click in order for Thunderbird to open correctly. Related : https://bugzilla.mozilla.org/show_bug.cgi?id=1745714 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:31:36 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 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: https://bugs.launchpad.net/thunderbird/+bug/2023400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
Removing rls-mm-incoming, as this seems to be done. ** Tags removed: rls-mm-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Committed Bug description: Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in mantic-proposed. See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3 When I downgrade glib in my sbuild environment, everything works as expected: $ apt install libglib2.0-0=2.76.3-1ubuntu1 libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1 libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1 The build also works fine in Debian unstable, which is using glib2.0 2.74.6-2. Netplan is using plenty of GLib's keyfile functions (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to producing a different output with this newer release (some strange line breaks injected in the middle of a keyfile). Example keyfile from the test_wifis.test_wifi_wowlan test, that should be generated by Netplan and the way it fails: Expected output: ``` [connection] id=netplan-wl0-homenet type=wifi interface-name=wl0 [wifi] wake-on-wlan=330 ssid=homenet mode=infrastructure [ipv4] method=link-local [ipv6] method=ignore ``` Failure: ``` E AssertionError: '[con[88 chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n' E [connection] E id=netplan-wl0-homenet E type=wifi E interface-name=wl0 E E [wifi] E wake-on-wlan=330 E - E ssid=homenet E mode=infrastructure E + E [ipv4] E method=link-local E E [ipv6] E method=ignore ``` To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2026826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028312] Re: does not support spec 1.5
Yes, however their repository is not very active. It's going to be a waiting game. I think I will just use a rolling release distribution instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2028312 Title: does not support spec 1.5 Status in desktop-file-utils package in Ubuntu: New Status in desktop-file-utils package in Debian: New Bug description: This package's code is a bit behind from the upstream code. In 2022, code was committed to support 1.5: https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/commit/56d220dd679c7c3a8f995a41a27a7d6f3df49dea When trying to validate .desktop files in Ubuntu that are running 1.5, I am getting errors. I am running Ubuntu 23.04 desktop-file-utils 0.26-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2028312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028869] [NEW] Selecting on a touchscreen with a finger does not work
Public bug reported: I have a laptop with a touch screen that supports both finger and stylus operations. Clicking on desktop icons works perfectly on both. Drawing a selection box works when using the stylus but not when using a finger. Touch + drag is essentially a no-op. I would expect both of these to work the same way. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-3 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 27 18:12:17 2023 InstallationDate: Installed on 2022-10-28 (271 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: Upgraded to lunar on 2023-04-10 (108 days ago) ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/2028869 Title: Selecting on a touchscreen with a finger does not work Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: I have a laptop with a touch screen that supports both finger and stylus operations. Clicking on desktop icons works perfectly on both. Drawing a selection box works when using the stylus but not when using a finger. Touch + drag is essentially a no-op. I would expect both of these to work the same way. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-3 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 27 18:12:17 2023 InstallationDate: Installed on 2022-10-28 (271 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: Upgraded to lunar on 2023-04-10 (108 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2028869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy
Ah, right. Debootstrap is more low-level, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2028769 Title: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The Gnome desktop might fail. [ Other Info ] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
Kinetic is EOL. ** Changed in: pcsc-lite (Ubuntu Kinetic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Committed Status in pcsc-lite source package in Kinetic: Won't Fix Status in pcsc-lite source package in Lunar: Fix Committed Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028864] Re: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64)
** Attachment added: "terminal_logs_deb.txt" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028864/+attachment/5688860/+files/terminal_logs_deb.txt -- 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/2028864 Title: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64) Status in chromium-browser package in Ubuntu: New Bug description: Tegra Orin platforms come in various flavor / dev kit. They all ship with a 'slightly' customized Ubuntu image. One of the customization is the addition of the Nvidia GPU drivers for Tegra. When running chromium browser debian package (either when running 18.04, or when running 22.04 with the package fetched from this PPA: https://launchpad.net/~nteodosio/+archive/ubuntu/chromium/+packages) then chromium works with hardware acceleration, as reported in chrome://gpu: Graphics Feature Status Canvas: Hardware accelerated Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Hardware accelerated Multiple Raster Threads: Enabled OpenGL: Enabled Rasterization: Hardware accelerated Raw Draw: Disabled Video Decode: Hardware accelerated Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated WebGPU: Disabled When using the snap version of chromium browser (on either 20.04 or 22.04), hardware acceleration is disabled, as shown in chrome://gpu: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Software only. Hardware acceleration disabled Multiple Raster Threads: Enabled OpenGL: Disabled Rasterization: Software only. Hardware acceleration disabled Raw Draw: Disabled Skia Graphite: Disabled Video Decode: Software only. Hardware acceleration disabled Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Software only, hardware acceleration unavailable WebGL2: Software only, hardware acceleration unavailable WebGPU: Disabled Problems Detected WebGPU has been disabled via blocklist or the command line. Disabled Features: webgpu Accelerated video encode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_encode Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable. Disabled Features: gpu_compositing These tests are done with X11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028864] [NEW] [snap] chromium browser does not work with accelerated graphics on Tegra (arm64)
Public bug reported: Tegra Orin platforms come in various flavor / dev kit. They all ship with a 'slightly' customized Ubuntu image. One of the customization is the addition of the Nvidia GPU drivers for Tegra. When running chromium browser debian package (either when running 18.04, or when running 22.04 with the package fetched from this PPA: https://launchpad.net/~nteodosio/+archive/ubuntu/chromium/+packages) then chromium works with hardware acceleration, as reported in chrome://gpu: Graphics Feature Status Canvas: Hardware accelerated Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Hardware accelerated Multiple Raster Threads: Enabled OpenGL: Enabled Rasterization: Hardware accelerated Raw Draw: Disabled Video Decode: Hardware accelerated Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated WebGPU: Disabled When using the snap version of chromium browser (on either 20.04 or 22.04), hardware acceleration is disabled, as shown in chrome://gpu: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Software only. Hardware acceleration disabled Multiple Raster Threads: Enabled OpenGL: Disabled Rasterization: Software only. Hardware acceleration disabled Raw Draw: Disabled Skia Graphite: Disabled Video Decode: Software only. Hardware acceleration disabled Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Software only, hardware acceleration unavailable WebGL2: Software only, hardware acceleration unavailable WebGPU: Disabled Problems Detected WebGPU has been disabled via blocklist or the command line. Disabled Features: webgpu Accelerated video encode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_encode Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable. Disabled Features: gpu_compositing These tests are done with X11. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Attachment added: "terminal_logs_snap.txt" https://bugs.launchpad.net/bugs/2028864/+attachment/5688859/+files/terminal_logs_snap.txt -- 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/2028864 Title: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64) Status in chromium-browser package in Ubuntu: New Bug description: Tegra Orin platforms come in various flavor / dev kit. They all ship with a 'slightly' customized Ubuntu image. One of the customization is the addition of the Nvidia GPU drivers for Tegra. When running chromium browser debian package (either when running 18.04, or when running 22.04 with the package fetched from this PPA: https://launchpad.net/~nteodosio/+archive/ubuntu/chromium/+packages) then chromium works with hardware acceleration, as reported in chrome://gpu: Graphics Feature Status Canvas: Hardware accelerated Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Hardware accelerated Multiple Raster Threads: Enabled OpenGL: Enabled Rasterization: Hardware accelerated Raw Draw: Disabled Video Decode: Hardware accelerated Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated WebGPU: Disabled When using the snap version of chromium browser (on either 20.04 or 22.04), hardware acceleration is disabled, as shown in chrome://gpu: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Software only. Hardware acceleration disabled Multiple Raster Threads: Enabled OpenGL: Disabled Rasterization: Software only. Hardware acceleration disabled Raw Draw: Disabled Skia Graphite: Disabled Video Decode: Software only. Hardware acceleration disabled Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Software only, hardware acceleration unavailable WebGL2: Software only, hardware acceleration unavailable WebGPU: Disabled Problems Detected WebGPU has been disabled via blocklist or the command line. Disabled Features: webgpu Accelerated video encode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_encode Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall
[Desktop-packages] [Bug 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy
Debootstrap just installs a minimal number of packages, not the desktop packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2028769 Title: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The Gnome desktop might fail. [ Other Info ] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: - * monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` - * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 + * "$HOME/.config/monitors.xml" is not installed by default in Ubuntu during the installation at this writing, you have to generate it by running the GUI preferences `$ gnome-control-center display` for GNOME, and `$ mate-display-properties` for MATE. + * Both GNOME and MATE can be run on the same distro, which causes compatibility issues with monitors.xml: monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` + * The monitors.xml file name for MATE is defined at https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and for GNOME it is defined at https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008. Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour monitors.xml in Ubuntu 23.04, and 22.04: ``` 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60.000 ``` monitors.xml in Ubuntu 22.04 (with ubuntu-mate-desktop installed), or 23.04 (with ubuntu-mate-desktop installed): ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60.000 0 0 1 yes Virtual-1 unknown unknown unknown 1280 800 59.810 ``` monitors.xml in Ubuntu MATE 22.04, Ubuntu MATE 23.04, ubuntu-mate-desktop from Ubuntu 22.04, or ubuntu-mate-desktop from Ubuntu 23.04: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour - Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: - * GNOME via `$ gnome-control-center display` - * MATE via `$ mate-display-properties` - - Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): + Steps I used to reproduce the issue in Ubuntu 22.04 with ubuntu-mate-desktop installed: * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` - * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. + * Log out, and log in to MATE. + * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will generate "$HOME/.config/monitors.xml" + * Log out from MATE. From the display manager, log into GNOME. + * As you can see, the screen resolution (1600x900 configured in MATE) not used by GNOME (https://github.com/mate-desktop/mate-control-center/assets/6416073/1b978bd7-22dd-4b42-a5b5-d32ec2d42f21), instead a fallback resolution is used. + * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) move "$HOME/.config/monitors.xml" (that was generated by MATE) to "$HOME/.config/monitors-v1-backup.xml" 2) generate a new "$HOME/.config/monitors.xml" 3) Change the screen resolution directly (https://github.com/mate-desktop/mate-control-center/assets/6416073/6a841086-6936-4a21-9d43-ca1a605a9806). Close the window. * Log out from GNOME. From the display manager, log into
[Desktop-packages] [Bug 2026586] Re: Update gnome-shell to 44.3
This bug was fixed in the package gnome-shell - 44.3-0ubuntu1 --- gnome-shell (44.3-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2026586) -- Jeremy Bícha Fri, 07 Jul 2023 09:41:10 -0400 ** Changed in: gnome-shell (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026586 Title: Update gnome-shell to 44.3 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.3/NEWS Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) There is a critical apt bug LP: #2025462 that is triggered if we manually bump GNOME Shell's dependency on Mutter to a version that has not been fully phased. We have not bumped GNOME Shell's dependencies in this update so that bug will not happen here. Nevertheless, it is ok to let mutter fully phase first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026544] Re: Update mutter to 44.3
This bug was fixed in the package mutter - 44.3-0ubuntu1 --- mutter (44.3-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2026544) -- Jeremy Bícha Fri, 07 Jul 2023 09:22:18 -0400 ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Fix Released -- 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/2026544 Title: Update mutter to 44.3 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.3/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This also includes a minor update of the triple buffering patch so that it still applies cleanly and to try to fix a crash on resume from sleep (LP: #2020049) It is believed that new upstream release also fixes LP: #2023766 and LP: #2016990 but those bugs have been left out of debian/changelog to not slow down the SRU process with verifying those bug fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026544] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2026544 Title: Update mutter to 44.3 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.3/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This also includes a minor update of the triple buffering patch so that it still applies cleanly and to try to fix a crash on resume from sleep (LP: #2020049) It is believed that new upstream release also fixes LP: #2023766 and LP: #2016990 but those bugs have been left out of debian/changelog to not slow down the SRU process with verifying those bug fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026586] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026586 Title: Update gnome-shell to 44.3 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.3/NEWS Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) There is a critical apt bug LP: #2025462 that is triggered if we manually bump GNOME Shell's dependency on Mutter to a version that has not been fully phased. We have not bumped GNOME Shell's dependencies in this update so that bug will not happen here. Nevertheless, it is ok to let mutter fully phase first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026586] Re: Update gnome-shell to 44.3
> (Except for the workrave extension but that was already broken when Ubuntu > 23.04 was released and > mentioned in every SRU since. I believed it's fixed in 23.10 so it needs to > be SRU'd.) https://bugs.launchpad.net/ubuntu/+source/workrave/+bug/2017302 I suppose, and https://bugs.launchpad.net/ubuntu/+source/workrave/+bug/2023089 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026586 Title: Update gnome-shell to 44.3 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.3/NEWS Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) There is a critical apt bug LP: #2025462 that is triggered if we manually bump GNOME Shell's dependency on Mutter to a version that has not been fully phased. We have not bumped GNOME Shell's dependencies in this update so that bug will not happen here. Nevertheless, it is ok to let mutter fully phase first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: * monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour monitors.xml in Ubuntu 23.04, and 22.04: ``` 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60.000 ``` - monitors.xml in Ubuntu MATE 22.04, and 23.04: + monitors.xml in Ubuntu 22.04 (with ubuntu-mate-desktop installed), or + 23.04 (with ubuntu-mate-desktop installed): + + ``` + + + + + 0 + 0 + yes + + + Virtual-1 + ??? + 0x + 0x + + + 1600 + 900 + 60.000 + + + + + + + 0 + 0 + 1 + yes + + + Virtual-1 + unknown + unknown + unknown + + + 1280 + 800 + 59.810 + + + + + + ``` + + monitors.xml in Ubuntu MATE 22.04, Ubuntu MATE 23.04, ubuntu-mate-desktop from Ubuntu 22.04, or ubuntu-mate-desktop from Ubuntu 23.04: ``` - - no - - ??? - 0x - 0x - 1600 - 900 - 60 - 0 - 0 - normal - no - no - yes - - - - - - - - + + no + + ??? + 0x + 0x + 1600 + 900 + 60 + 0 + 0 + normal + no + no + yes + + + + + + + + ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97
[Desktop-packages] [Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
This bug was fixed in the package gnome-control-center - 1:41.7-0ubuntu0.22.04.7 --- gnome-control-center (1:41.7-0ubuntu0.22.04.7) jammy; urgency=medium * Cherry-pick 3 patches to fix mirror mode crash when resolution of the 2 monitors don't match (LP: #2026228) -- Dirk Su Fri, 07 Jul 2023 12:45:49 +0800 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Released Status in gnome-control-center source package in Kinetic: Won't Fix Status in gnome-control-center source package in Lunar: Fix Released Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] Mirror mode is only an option if there are only 2 monitors connected even if one monitor is disabled. A laptop's internal screen counts as one of the monitors. This particular bug requires two screens that have a screen resolution that they don't both share. (See comment 12 for an example). 1. Connect the monitors 2. Open the GNOME Settings app (gnome-control-center) 3. On the left sidebar, click Displays to switch to the Display panel 4. Switch to mirror mode 3. gnome-control-center won't crash [Where problems could occur] This only modifies the code related to mirror mode in Displays panel. For Lunar, check variable (best_mode) before using it. This patch is backported from GNOME 45 Alpha. For Jammy, include the Lunar patch and update the way to find cloning mode. These 2 additional patches are backported from gnome-control- center 43. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
This bug was fixed in the package gnome-control-center - 1:44.0-1ubuntu6 --- gnome-control-center (1:44.0-1ubuntu6) lunar; urgency=medium * Add patch to fix mirror mode crash when resolution of the 2 monitors don't match (LP: #2026228) -- Dirk Su Fri, 07 Jul 2023 09:15:28 +0800 ** Changed in: gnome-control-center (Ubuntu Lunar) Status: Fix Committed => Fix Released ** Changed in: gnome-control-center (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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Released Status in gnome-control-center source package in Kinetic: Won't Fix Status in gnome-control-center source package in Lunar: Fix Released Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] Mirror mode is only an option if there are only 2 monitors connected even if one monitor is disabled. A laptop's internal screen counts as one of the monitors. This particular bug requires two screens that have a screen resolution that they don't both share. (See comment 12 for an example). 1. Connect the monitors 2. Open the GNOME Settings app (gnome-control-center) 3. On the left sidebar, click Displays to switch to the Display panel 4. Switch to mirror mode 3. gnome-control-center won't crash [Where problems could occur] This only modifies the code related to mirror mode in Displays panel. For Lunar, check variable (best_mode) before using it. This patch is backported from GNOME 45 Alpha. For Jammy, include the Lunar patch and update the way to find cloning mode. These 2 additional patches are backported from gnome-control- center 43. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026228] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Released Status in gnome-control-center source package in Kinetic: Won't Fix Status in gnome-control-center source package in Lunar: Fix Released Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] Mirror mode is only an option if there are only 2 monitors connected even if one monitor is disabled. A laptop's internal screen counts as one of the monitors. This particular bug requires two screens that have a screen resolution that they don't both share. (See comment 12 for an example). 1. Connect the monitors 2. Open the GNOME Settings app (gnome-control-center) 3. On the left sidebar, click Displays to switch to the Display panel 4. Switch to mirror mode 3. gnome-control-center won't crash [Where problems could occur] This only modifies the code related to mirror mode in Displays panel. For Lunar, check variable (best_mode) before using it. This patch is backported from GNOME 45 Alpha. For Jammy, include the Lunar patch and update the way to find cloning mode. These 2 additional patches are backported from gnome-control- center 43. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028853] [NEW] Window management - window size and state is not restored
Public bug reported: Ubuntu 23.04 gnome-shell 44.2 X11 When maximizing a window like i.e. Nemo or Evolution and closing it, starting the app again leads to an unmaximized window. This behaviour is always the same within one session or after reboot. Firefox (not snap! but .deb install) for instance just shows this behaviour after a session restart/reboot. Within the session it remembers the window size and state. I expect that the window size of the last state before closing is restored after starting the app again. That was the normal behaviour until the upgrade to 23.04. 44.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 100 /var/lib/dpkg/status 44.0-2ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu lunar/main amd64 Packages ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2028853 Title: Window management - window size and state is not restored Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 23.04 gnome-shell 44.2 X11 When maximizing a window like i.e. Nemo or Evolution and closing it, starting the app again leads to an unmaximized window. This behaviour is always the same within one session or after reboot. Firefox (not snap! but .deb install) for instance just shows this behaviour after a session restart/reboot. Within the session it remembers the window size and state. I expect that the window size of the last state before closing is restored after starting the app again. That was the normal behaviour until the upgrade to 23.04. 44.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 100 /var/lib/dpkg/status 44.0-2ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu lunar/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2028853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
Thanks for sharing your resuilts, David! -- 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/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028832] [NEW] NetworkManager : sharing per ethernet needs to switch off and on
Public bug reported: Hello, My Lenovo laptop is connected to the Internet trough Wifi and I need to share the Internet (tethering) trough my ethernet port (Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)) to a Rapsberry Pi 3. To achieve this, I setup the ethernet network with NetworkManager (sharing the link with IPV4 and IPV6 is desactivated). This sharing is configured to switch on automatically when NetworkManager is started. But that sharing never goes up automatically. I need to manually switch off and on the ethernet link in NetworkManager and then tethering trough ethernet works fine. There seems to be a bug in NetworkManager considering the automatic setup up of a ethernet sharing link. Can you solve that? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2028832 Title: NetworkManager : sharing per ethernet needs to switch off and on Status in network-manager package in Ubuntu: New Bug description: Hello, My Lenovo laptop is connected to the Internet trough Wifi and I need to share the Internet (tethering) trough my ethernet port (Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)) to a Rapsberry Pi 3. To achieve this, I setup the ethernet network with NetworkManager (sharing the link with IPV4 and IPV6 is desactivated). This sharing is configured to switch on automatically when NetworkManager is started. But that sharing never goes up automatically. I need to manually switch off and on the ethernet link in NetworkManager and then tethering trough ethernet works fine. There seems to be a bug in NetworkManager considering the automatic setup up of a ethernet sharing link. Can you solve that? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2028832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028831] [NEW] malcontent-control 0.11.0-4 always crashes when I click on username in LiveUSB environment
Public bug reported: malcontent-control 0.11.0-4 always crashes when I click on username in LiveUSB environment I've installed backported malcontent-control 0.11.0-4 on Ubuntu 22.04 from ppa:ubuntu-backports-testers - build logs are here: https://launchpad.net/~baltix/+archive/ubuntu/ppa/+build/26455032 I see these error messages in terminal: ~$ malcontent-control (malcontent-control:100153): GLib-GObject-WARNING **: 10:54:35.625: invalid cast from 'MctCarouselItem' to 'MctCarousel' (malcontent-control:100153): GLib-GObject-WARNING **: 10:54:35.625: ../../../gobject/gsignal.c:3318: signal id '143' is invalid for instance '0x55cfc40c1b30' (malcontent-control:100153): Gtk-CRITICAL **: 10:54:35.625: gtk_stack_set_visible_child_name: assertion 'GTK_IS_STACK (stack)' failed (malcontent-control:100153): Gtk-CRITICAL **: 10:54:35.625: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed Segmentation fault Latest line sometimes changes to "Bus error": ~$ malcontent-control (malcontent-control:100237): GLib-GObject-WARNING **: 10:55:11.959: invalid cast from 'MctCarouselItem' to 'MctCarousel' (malcontent-control:100237): GLib-GObject-WARNING **: 10:55:11.960: ../../../gobject/gsignal.c:3318: signal id '143' is invalid for instance '0x55f9ccbbbc20' (malcontent-control:100237): Gtk-CRITICAL **: 10:55:11.960: gtk_stack_set_visible_child_name: assertion 'GTK_IS_STACK (stack)' failed (malcontent-control:100237): Gtk-CRITICAL **: 10:55:11.960: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed Bus error No crash if I start older malcontent-control from Ubuntu Jammy official archive (version 10.4) ** Affects: malcontent (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to malcontent in Ubuntu. https://bugs.launchpad.net/bugs/2028831 Title: malcontent-control 0.11.0-4 always crashes when I click on username in LiveUSB environment Status in malcontent package in Ubuntu: New Bug description: malcontent-control 0.11.0-4 always crashes when I click on username in LiveUSB environment I've installed backported malcontent-control 0.11.0-4 on Ubuntu 22.04 from ppa:ubuntu-backports-testers - build logs are here: https://launchpad.net/~baltix/+archive/ubuntu/ppa/+build/26455032 I see these error messages in terminal: ~$ malcontent-control (malcontent-control:100153): GLib-GObject-WARNING **: 10:54:35.625: invalid cast from 'MctCarouselItem' to 'MctCarousel' (malcontent-control:100153): GLib-GObject-WARNING **: 10:54:35.625: ../../../gobject/gsignal.c:3318: signal id '143' is invalid for instance '0x55cfc40c1b30' (malcontent-control:100153): Gtk-CRITICAL **: 10:54:35.625: gtk_stack_set_visible_child_name: assertion 'GTK_IS_STACK (stack)' failed (malcontent-control:100153): Gtk-CRITICAL **: 10:54:35.625: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed Segmentation fault Latest line sometimes changes to "Bus error": ~$ malcontent-control (malcontent-control:100237): GLib-GObject-WARNING **: 10:55:11.959: invalid cast from 'MctCarouselItem' to 'MctCarousel' (malcontent-control:100237): GLib-GObject-WARNING **: 10:55:11.960: ../../../gobject/gsignal.c:3318: signal id '143' is invalid for instance '0x55f9ccbbbc20' (malcontent-control:100237): Gtk-CRITICAL **: 10:55:11.960: gtk_stack_set_visible_child_name: assertion 'GTK_IS_STACK (stack)' failed (malcontent-control:100237): Gtk-CRITICAL **: 10:55:11.960: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed Bus error No crash if I start older malcontent-control from Ubuntu Jammy official archive (version 10.4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/malcontent/+bug/2028831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922047] Re: Touchpad scrolling is too fast
Also being tracked in: https://gitlab.gnome.org/GNOME/gtk/-/issues/4793 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4793 https://gitlab.gnome.org/GNOME/gtk/-/issues/4793 -- 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/1922047 Title: Touchpad scrolling is too fast Status in Mozilla Firefox: Confirmed Status in GTK+: Fix Released Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1922047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922047]
yes , I have a build. Ok I'll write a patch and you can check it from there -- 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/1922047 Title: Touchpad scrolling is too fast Status in Mozilla Firefox: Confirmed Status in GTK+: Fix Released Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1922047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922047]
(In reply to renevietnam29 from comment #9) > you can assign it to me if its still open botond Sure! Do you have a local build of Firefox already? If not, you can find instructions [here](https://firefox-source- docs.mozilla.org/setup/index.html). As discussed in comment 4, we are initially only looking to change the value of the [apz.gtk.pangesture.delta_mode](https://searchfox.org/mozilla- central/rev/0b55b868c17835942d40ca3fedfca8057481207b/modules/libpref/init/StaticPrefList.yaml#593) pref, to 2 (pixel mode), and only on the Nightly branch. You can see an example of making a pref value conditional on Nightly [here](https://searchfox.org/mozilla- central/rev/0b55b868c17835942d40ca3fedfca8057481207b/modules/libpref/init/StaticPrefList.yaml#4539-4543). -- 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/1922047 Title: Touchpad scrolling is too fast Status in Mozilla Firefox: Confirmed Status in GTK+: Fix Released Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1922047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922047]
you can assign it to me if its still open botond -- 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/1922047 Title: Touchpad scrolling is too fast Status in Mozilla Firefox: Confirmed Status in GTK+: Fix Released Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1922047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028822] [NEW] snap breaks alternate policies.json location of toolkit.policies.perUserDir=true
Public bug reported: repro 1. launch snap using firefox -P 2. create test profile 3. open about:prefs set bool toolkit.policies.perUserDir=true 4. ensure no file at /etc/firefox/policies/policies.json 5. ensure file at: /run/user/$(id -u)/firefox/policies.json 6. close & restart firefox -P and select test profile expected: policy parsed (and applied, if valid) actual: policy not parsed, error logged syslog AVC apparmor="DENIED" operation="open" profile="snap.firefox.firefox" name="/run/user/1002/firefox/policies.json" pid=303974 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1002 ouid=1002 about:policies Error reading JSON file: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIXPCComponents_Utils.readUTF8File]" nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)" location: "JS frame :: resource://gre/modules/EnterprisePoliciesParent.sys.mjs :: _readData :: line 614" data: no] workaround for my use case, launching two firefox instances with different settings, abusing test feature: export XPCSHELL_TEST_PROFILE_DIR=magic then configure browser.policies.alternatePath=/etc/firefox/policies/custom.json Not a dupe, the default location /etc/firefox/policies/policies.json works: LP: #1975853 Background on the secondary location: https://bugzilla.mozilla.org/show_bug.cgi?id=1583466 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: snap -- 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/2028822 Title: snap breaks alternate policies.json location of toolkit.policies.perUserDir=true Status in firefox package in Ubuntu: New Bug description: repro 1. launch snap using firefox -P 2. create test profile 3. open about:prefs set bool toolkit.policies.perUserDir=true 4. ensure no file at /etc/firefox/policies/policies.json 5. ensure file at: /run/user/$(id -u)/firefox/policies.json 6. close & restart firefox -P and select test profile expected: policy parsed (and applied, if valid) actual: policy not parsed, error logged syslog AVC apparmor="DENIED" operation="open" profile="snap.firefox.firefox" name="/run/user/1002/firefox/policies.json" pid=303974 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1002 ouid=1002 about:policies Error reading JSON file: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIXPCComponents_Utils.readUTF8File]" nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)" location: "JS frame :: resource://gre/modules/EnterprisePoliciesParent.sys.mjs :: _readData :: line 614" data: no] workaround for my use case, launching two firefox instances with different settings, abusing test feature: export XPCSHELL_TEST_PROFILE_DIR=magic then configure browser.policies.alternatePath=/etc/firefox/policies/custom.json Not a dupe, the default location /etc/firefox/policies/policies.json works: LP: #1975853 Background on the secondary location: https://bugzilla.mozilla.org/show_bug.cgi?id=1583466 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2028822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
