[Desktop-packages] [Bug 2091952] Re: ~25 second delay after login for gtk4 apps to start on plucky
** Summary changed: - ~25 second delay after login for gtk4 apps to start on pluck + ~25 second delay after login for gtk4 apps to start on plucky -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2091952 Title: ~25 second delay after login for gtk4 apps to start on plucky Status in gtk4 package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Debian: New Bug description: Impact -- Ubuntu 25.04 "Plucky" is getting gtk4 today. There is approximately a 25 second delay after login for gtk4 apps to start. This is fixed in xdg-desktop-portal-gnome's main branch and we'll get that fix into Ubuntu 25.04 but it might not be until January because of end of year holidays. I'm adding a gtk4 task. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2091952/+subscriptions -- Mailing list: https://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 2091952] [NEW] ~25 second delay after login for gtk4 apps to start on pluck
Public bug reported: Impact -- Ubuntu 25.04 "Plucky" is getting gtk4 today. There is approximately a 25 second delay after login for gtk4 apps to start. This is fixed in xdg-desktop-portal-gnome's main branch and we'll get that fix into Ubuntu 25.04 but it might not be until January because of end of year holidays. I'm adding a gtk4 task. ** Affects: gtk4 (Ubuntu) Importance: Medium Status: Triaged ** Affects: xdg-desktop-portal-gnome (Ubuntu) Importance: Medium Status: Triaged ** Affects: xdg-desktop-portal-gnome (Debian) Importance: Unknown Status: Unknown ** Tags: plucky rls-pp-incoming ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu) Status: New => Triaged ** Changed in: gtk4 (Ubuntu) Importance: Undecided => Medium ** Bug watch added: Debian Bug tracker #1089760 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089760 ** Also affects: xdg-desktop-portal-gnome (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089760 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2091952 Title: ~25 second delay after login for gtk4 apps to start on pluck Status in gtk4 package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Debian: Unknown Bug description: Impact -- Ubuntu 25.04 "Plucky" is getting gtk4 today. There is approximately a 25 second delay after login for gtk4 apps to start. This is fixed in xdg-desktop-portal-gnome's main branch and we'll get that fix into Ubuntu 25.04 but it might not be until January because of end of year holidays. I'm adding a gtk4 task. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2091952/+subscriptions -- Mailing list: https://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 2090614] Re: Update deja-dup to 47.0
** Tags removed: oracular ** Tags added: plucky -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/2090614 Title: Update deja-dup to 47.0 Status in deja-dup package in Ubuntu: New Bug description: Please update to the latest version 47.0: https://gitlab.gnome.org/World/deja-dup/-/blob/main/NEWS.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2090614/+subscriptions -- Mailing list: https://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 2023044] Re: New thumbnails are missing from file chooser
It is not possible to backport the 24.10 fix to 24.04 LTS; it involves updating too many components of the GNOME desktop with too large of changes. Sorry. ** Changed in: xdg-desktop-portal-gnome (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2023044 Title: New thumbnails are missing from file chooser Status in GTK+: New Status in gtk4 package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Bug description: Impact -- Thumbnails do not show in the file chooser (provided by gtk4 which is also used by even non-GTK3 apps if they use xdg-desktop-portal-gnome) until the thumbnail is generated by for instance, viewing the folder in Nautilus. This bug is new to Ubuntu 23.04 because GTK 4.10 is the first stable GTK release to support the "grid view" in the filechooser. Test Case - 1. Use Firefox to download an image file. (This test case assumes you're using the default Firefox distributed as a Snap). 2. In Firefox, use the keyboard shortcut Ctrl+O to open the file chooser. 3. Navigate to where the file was downloaded (your Downloads/ folder?) 4. The file should show a thumbnail image Number 4 doesn't happen correctly until you open the folder in Nautilus at least once. Other Info -- I am linking to what upstream considers the master bug for this issue. But a duplicate of the issue is https://gitlab.gnome.org/GNOME/gtk/-/issues/5663 which has a clearer summary. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2023044/+subscriptions -- Mailing list: https://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 1439173] Re: some -dev packages missing in SDK chroot for packages that are in the framework
** Changed in: ubuntu-meta (Ubuntu) Status: Fix Committed => Fix Released -- 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/1439173 Title: some -dev packages missing in SDK chroot for packages that are in the framework Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: There are some packages in the Ubuntu touch frameworks where the according -dev packages are missing in the chroot. Right now those come to my mind: qtpim5-dev libssl-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1439173/+subscriptions -- Mailing list: https://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 2018425] Re: apt install ubuntu-desktop takes forever
*** This bug is a duplicate of bug 1999178 *** https://bugs.launchpad.net/bugs/1999178 ** This bug has been marked a duplicate of bug 1999178 netplan generator causes deadlock during systemd daemon-reload -- 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/2018425 Title: apt install ubuntu-desktop takes forever Status in subiquity: Invalid Status in ubuntu-meta package in Ubuntu: New Bug description: Install server 23.04 to take advantage of flexible disk partitioning/raid. While installing desktop over the installed server (apt install ubuntu-desktop) it proceeds normally about 40% of the way but after that it slows down tremendously, hanging for minutes in between packages. It eventually (after several hours) completes without error. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 3 11:41:00 2023 InstallationDate: Installed on 2023-04-29 (3 days ago) InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 (20230415) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2018425/+subscriptions -- Mailing list: https://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 1910961] Re: Let user choose browser to install / Remove fixed firefox dependency
Firefox is a Recommends, not a hard dependency. Therefore, I'm closing this issue. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Invalid -- 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/1910961 Title: Let user choose browser to install / Remove fixed firefox dependency Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Hi, I know this is a really core feature of a distribution, and I'm not sure it's the best place to open this discussion, but I'd like to open the idea to have the possibility that the user can choose not to install firefox by default, or even better let the user choose his browser at installation time. Why people would want not to use firefox by default ? * It's been lagging in speed and stability compared to other browser. I've often have some tabs crash, I have to open a new tab copy/pasting the same URL. * Mozilla was advertising a advocate for free speech and internet neutrality. Many people would have different views on this, but latest message from their blog seems they support content being pushed to users "Turn on by default the tools to amplify factual voices over disinformation" ** https://blog.mozilla.org/blog/2021/01/08/we-need-more-than-deplatforming/ ** https://twitter.com/mozilla/status/1347633954497548289 * Third-party cookie is still being a thing. It's something that should have been removed since a long time already, and a push to remove its support is actually being pushed by Apple/Safari and Google/Chrome, and not so actively by Mozilla. There are alternative full opensource browser that user would like to have by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1910961/+subscriptions -- Mailing list: https://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 1036502] Re: Change of icon set
** Changed in: ubuntu-meta (Ubuntu) Status: New => Invalid -- 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/1036502 Title: Change of icon set Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Ubuntu should move away from Tango, to a flat, monochromatic and sharper icon set. The Tango icons have gradients adding an overhead of visual complexity. The flat icons in the top Ubuntu panel look good, and ubuntu must have similar icons across. This seems to be an accepted modern trend, with even Windows 8 adopting flat monochromatic icons for windows 8. Even Google changed its favicon, to a flat blue and white logo instead of multi coloured favicon. Such icons are visually clean and more obvious and hence less confusing. Also in line with Ubuntu's goal to deliver on par performance on devices of all form factors, I doubt how Tango will behave on small devices with lower dpi and also on high dpi like the retina. Flat icons should be much more consistent across all screens. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubuntu-desktop 1.267 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Tue Aug 14 11:16:22 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to precise on 2012-08-06 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1036502/+subscriptions -- Mailing list: https://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 1518130] Re: libpng is installed by default
You can uninstall plymouth-theme-ubuntu-text if you want. It is only a Recommends. I have retitled this bug since we're not going to stop packages from being built with PNG support; however, maybe we can evaluate whether we need to have a Plymouth theme in ubuntu-standard. ** Summary changed: - libpng is installed by default + Remove plymouth-theme-ubuntu-text from ubuntu-standard? -- 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/1518130 Title: Remove plymouth-theme-ubuntu-text from ubuntu-standard? Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu server cloud images include libpng by default. This is unnecessary and poor practice. It wastes space and poses a security risk. Looks like it is installed because "ubuntu-standard" recommends "plymouth-theme-ubuntu-text" which depends on "libplymouth2" which depends on "libpng12-0". The description for "plymouth-theme-ubuntu-text" is "graphical boot animation and logger - ubuntu-logo theme". This is obviously inappropriate for any server image, and especially for a cloud-based server image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1518130/+subscriptions -- Mailing list: https://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 1570537] Re: git installed by default in ubuntu-server & ubuntu-wsl
** Summary changed: - git installed by default + git installed by default in ubuntu-server & ubuntu-wsl -- 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/1570537 Title: git installed by default in ubuntu-server & ubuntu-wsl Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I've just installed the latest daily build and it seems that default install has become pretty bloated with unneeded packages, along with lxd, also the git gets installed. I'm totally aware that this is a popular tool but IMHO this shouldn't be installed by default as it's a primary development tool. The deploys on server are usually done without it so if one needs it to do deploys then they should install it manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1570537/+subscriptions -- Mailing list: https://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 1726395] Re: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE
** Changed in: ubuntu-meta (Ubuntu) Status: In Progress => Fix Released -- 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/1726395 Title: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell Desktop Environment. It's 5 years old software (latest release 2012-10-16) and is needed only for old GNOME flashback (fallback) session. Gnome-screensaver shouldn't be running on GNOME Shell - users can't unlock the screen because of important bugs in gnome-screensaver, see bug #1716278 and bug #1699670 (Gnome screensaver lock always responses "incorrect password" when last active window's language is not the language of the password) for example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726395/+subscriptions -- Mailing list: https://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 1910961] Re: Let user choose browser to install / Remove fixed firefox dependency
At this time, we do not wish to have a browser choice screen in the install. You are able to install something else if you want and set it as the default web browser. You can even uninstall Firefox if it bothers you that it is installed. -- 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/1910961 Title: Let user choose browser to install / Remove fixed firefox dependency Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Hi, I know this is a really core feature of a distribution, and I'm not sure it's the best place to open this discussion, but I'd like to open the idea to have the possibility that the user can choose not to install firefox by default, or even better let the user choose his browser at installation time. Why people would want not to use firefox by default ? * It's been lagging in speed and stability compared to other browser. I've often have some tabs crash, I have to open a new tab copy/pasting the same URL. * Mozilla was advertising a advocate for free speech and internet neutrality. Many people would have different views on this, but latest message from their blog seems they support content being pushed to users "Turn on by default the tools to amplify factual voices over disinformation" ** https://blog.mozilla.org/blog/2021/01/08/we-need-more-than-deplatforming/ ** https://twitter.com/mozilla/status/1347633954497548289 * Third-party cookie is still being a thing. It's something that should have been removed since a long time already, and a push to remove its support is actually being pushed by Apple/Safari and Google/Chrome, and not so actively by Mozilla. There are alternative full opensource browser that user would like to have by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1910961/+subscriptions -- Mailing list: https://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 1956109] Re: printer-driver-ptouch is included with multiple metapackages for the minimal install
I am closing this bug because no justification was provided for this suggested change. ** Changed in: ubuntu-mate-meta (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-meta (Ubuntu) Status: New => Invalid ** Changed in: xubuntu-meta (Ubuntu) Status: New => Invalid -- 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/1956109 Title: printer-driver-ptouch is included with multiple metapackages for the minimal install Status in ubuntu-mate-meta package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Invalid Bug description: A label printer driver is a recommended dependency in many metapackages. It is also installed with the minimal Ubuntu ISO option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1956109/+subscriptions -- Mailing list: https://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 2081090] Re: gutenprint FTBFS due to 64-bit restriction
The Debian issue is that https://bugs.debian.org/1064089 was reported indicating that gutenprint should be part of the time_t transition, but no patch was attached nor was an upload made to Experimental. Using the logic from comment 5 here, we can ignore this issue on the Debian side if we wait until Debian 13. Otherwise, would you or Adrien or someone on your team want to submit a patch now? The gutenprint library has no reverse dependencies in Debian. I don't know if that matters. ** Bug watch added: Debian Bug tracker #1064089 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064089 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gutenprint in Ubuntu. https://bugs.launchpad.net/bugs/2081090 Title: gutenprint FTBFS due to 64-bit restriction Status in gutenprint package in Ubuntu: Fix Released Bug description: The FTBFS[0] report shows an issue for gutenprint: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: architecture-is-64-bit but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed The problem is that the package now no longer builds for armhf[1], which is 32-bit. This appears to have been an intentional change by Debian: gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium * do not build this package on 32bit architectures anymore Closes: #1064088 Closes: #1064089 There was no patch attached to #1064089, so I can not reproduce the problems mentioned in #1064088. I am fed up with this poorly done transition, so I won't spend more time with this. Sorry 32bit people. -- Thorsten Alteholz Fri, 26 Apr 2024 23:10:00 +0200 The transition referenced in the changelog is the time_t transition performed late last cycle; presumably then reversing this change in Ubuntu would merely exchange this FTBFS for a different one. (Perhaps one avenue of solution would be to create the requested time_t patch for #1064088?) The question is then if the armhf binary for gutenprint was deleted from the archive, would that result in other issues within the printing stack? 0: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-oracular-oracular.html#ubuntu-server-pkgset 1: https://launchpad.net/ubuntu/+source/gutenprint/5.3.4.20220624T01008808d602-3/+build/28712797 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/2081090/+subscriptions -- Mailing list: https://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 1704492] Re: Prebase vowels not moved to before consonants joined by virama
This issue is fixed in Ubuntu 18.04 LTS and newer. ** Changed in: harfbuzz (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to harfbuzz in Ubuntu. https://bugs.launchpad.net/bugs/1704492 Title: Prebase vowels not moved to before consonants joined by virama Status in harfbuzz package in Ubuntu: Fix Released Bug description: This bug was present in the implementation of USE up to Version 1.1.2 of HarfBuzz - https://github.com/behdad/harfbuzz/issues/180 records problem and fix in Version 1.1.3. The bug also affects the much- afflicted Tai Tham script, e.g. in the word ᩉ᩠ᩅᩯᩁ /wɛːn/ 'ring (n.)'. Unfortunately, LTS Ubuntu release 16.04 is still at Version 1.0.1 - there are no backports from Yakkety (Harfbuzz 1.2.7) or Zesty (Harfbuzz 1.4.2). Potentially unsafe work-arounds include building HarfBuzz (e.g. Version 1.4.6) and replacing the sharable object libharfbuzz.so.0 with a user-generated sharable object. It is possible to backport from Yakkety oneself using the Firefox example in "Recommended alternative to pinning" at https://help.ubuntu.com/community/PinningHowto. Note that the final command is sudo apt-get -b source -t yakkety harfbuzz One then installs the corrected object by means of the command sudo dpkg -i libharfbuzz0b_1.2.7-1_i386.deb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libharfbuzz0b 1.0.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-102.149-generic 3.13.11-ckt39 Uname: Linux 3.13.0-102-generic i686 ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 CurrentDesktop: Unity Date: Fri Jul 14 22:21:04 2017 InstallationDate: Installed on 2010-12-28 (2390 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: harfbuzz UpgradeStatus: Upgraded to xenial on 2016-11-19 (237 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/harfbuzz/+bug/1704492/+subscriptions -- Mailing list: https://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 2083629] Re: Update fonts-noto-color-emoji to 2.047
** Changed in: fonts-noto-color-emoji (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: fonts-noto-color-emoji (Ubuntu Noble) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/2083629 Title: Update fonts-noto-color-emoji to 2.047 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: In Progress Status in fonts-noto-color-emoji source package in Noble: In Progress Status in fonts-noto-color-emoji source package in Oracular: Fix Released Bug description: Impact == Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the New link to see the new emoji. https://emojipedia.org/google/16.0/ Or see https://blog.emojipedia.org/google-debuts-emoji-16-0-support/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle Test Plan = The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont Where problems could occur == Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. Other Info == This update is only for display of the new emoji. It does not affect gnome-characters, the gtk3 or gtk4 emoji choosers, or any other emoji choosers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/2083629/+subscriptions -- Mailing list: https://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 2083714] Re: Update gtk4 to 4.16.3
I have successfully completed all the test cases with gtk4 4.16.3+ds-0ubuntu1 on Ubuntu 24.10. ** Tags removed: verification-needed verification-needed-oracular ** Tags added: verification-done verification-done-oracular ** Description changed: There is a new point release in the stable GTK 4.16 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.16.3/NEWS - Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- - snap install portal-test + snap install portal-test --edge snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- Many of the default Ubuntu desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are not affected by this SRU. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2083714 Title: Update gtk4 to 4.16.3 Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Oracular: Fix Committed Bug description: There is a new point release in the stable GTK 4.16 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.16.3/NEWS Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test --edge snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- Many of the default Ubuntu desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are not affected by this SRU. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2083714/+subscriptions -- Mailing list: https://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 2081090] Re: gutenprint FTBFS due to 64-bit restriction
I also added a reminder Jira card for myself to re-enable 32-bit builds for gutenprint once Debian 13 is released since they will be past the time_t transition then. We should be able to get gutenprint back on armhf in time for Ubuntu 24.04 LTS, assuming armhf is still around for us then. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gutenprint in Ubuntu. https://bugs.launchpad.net/bugs/2081090 Title: gutenprint FTBFS due to 64-bit restriction Status in gutenprint package in Ubuntu: Fix Released Bug description: The FTBFS[0] report shows an issue for gutenprint: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: architecture-is-64-bit but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed The problem is that the package now no longer builds for armhf[1], which is 32-bit. This appears to have been an intentional change by Debian: gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium * do not build this package on 32bit architectures anymore Closes: #1064088 Closes: #1064089 There was no patch attached to #1064089, so I can not reproduce the problems mentioned in #1064088. I am fed up with this poorly done transition, so I won't spend more time with this. Sorry 32bit people. -- Thorsten Alteholz Fri, 26 Apr 2024 23:10:00 +0200 The transition referenced in the changelog is the time_t transition performed late last cycle; presumably then reversing this change in Ubuntu would merely exchange this FTBFS for a different one. (Perhaps one avenue of solution would be to create the requested time_t patch for #1064088?) The question is then if the armhf binary for gutenprint was deleted from the archive, would that result in other issues within the printing stack? 0: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-oracular-oracular.html#ubuntu-server-pkgset 1: https://launchpad.net/ubuntu/+source/gutenprint/5.3.4.20220624T01008808d602-3/+build/28712797 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/2081090/+subscriptions -- Mailing list: https://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 2081090] Re: gutenprint FTBFS due to 64-bit restriction
This bug was fixed in the package gutenprint - 5.3.4.20220624T01008808d602-4 --- gutenprint (5.3.4.20220624T01008808d602-4) unstable; urgency=medium * Team upload * Stop building gimp-gutenprint (Closes: #1088069) * Stop building libgutenprintui: it was only used by the gimp plugin (Closes: #603342, #967507) -- Jeremy Bícha Thu, 05 Dec 2024 15:59:37 -0500 ** Changed in: gutenprint (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gutenprint in Ubuntu. https://bugs.launchpad.net/bugs/2081090 Title: gutenprint FTBFS due to 64-bit restriction Status in gutenprint package in Ubuntu: Fix Released Bug description: The FTBFS[0] report shows an issue for gutenprint: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: architecture-is-64-bit but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed The problem is that the package now no longer builds for armhf[1], which is 32-bit. This appears to have been an intentional change by Debian: gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium * do not build this package on 32bit architectures anymore Closes: #1064088 Closes: #1064089 There was no patch attached to #1064089, so I can not reproduce the problems mentioned in #1064088. I am fed up with this poorly done transition, so I won't spend more time with this. Sorry 32bit people. -- Thorsten Alteholz Fri, 26 Apr 2024 23:10:00 +0200 The transition referenced in the changelog is the time_t transition performed late last cycle; presumably then reversing this change in Ubuntu would merely exchange this FTBFS for a different one. (Perhaps one avenue of solution would be to create the requested time_t patch for #1064088?) The question is then if the armhf binary for gutenprint was deleted from the archive, would that result in other issues within the printing stack? 0: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-oracular-oracular.html#ubuntu-server-pkgset 1: https://launchpad.net/ubuntu/+source/gutenprint/5.3.4.20220624T01008808d602-3/+build/28712797 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/2081090/+subscriptions -- Mailing list: https://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 2081090] Re: gutenprint FTBFS due to 64-bit restriction
I can do that for the other packages, but what about the arch:all packages printer-driver-all and printer-driver-all-enforce? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gutenprint in Ubuntu. https://bugs.launchpad.net/bugs/2081090 Title: gutenprint FTBFS due to 64-bit restriction Status in gutenprint package in Ubuntu: Triaged Bug description: The FTBFS[0] report shows an issue for gutenprint: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: architecture-is-64-bit but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed The problem is that the package now no longer builds for armhf[1], which is 32-bit. This appears to have been an intentional change by Debian: gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium * do not build this package on 32bit architectures anymore Closes: #1064088 Closes: #1064089 There was no patch attached to #1064089, so I can not reproduce the problems mentioned in #1064088. I am fed up with this poorly done transition, so I won't spend more time with this. Sorry 32bit people. -- Thorsten Alteholz Fri, 26 Apr 2024 23:10:00 +0200 The transition referenced in the changelog is the time_t transition performed late last cycle; presumably then reversing this change in Ubuntu would merely exchange this FTBFS for a different one. (Perhaps one avenue of solution would be to create the requested time_t patch for #1064088?) The question is then if the armhf binary for gutenprint was deleted from the archive, would that result in other issues within the printing stack? 0: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-oracular-oracular.html#ubuntu-server-pkgset 1: https://launchpad.net/ubuntu/+source/gutenprint/5.3.4.20220624T01008808d602-3/+build/28712797 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/2081090/+subscriptions -- Mailing list: https://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 2081090] Re: gutenprint FTBFS due to 64-bit restriction
No Ubuntu Desktop flavor supports armhf. The metapackages are only built on armhf because it usually doesn't really hurt for them to be built there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gutenprint in Ubuntu. https://bugs.launchpad.net/bugs/2081090 Title: gutenprint FTBFS due to 64-bit restriction Status in gutenprint package in Ubuntu: Triaged Bug description: The FTBFS[0] report shows an issue for gutenprint: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: architecture-is-64-bit but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed The problem is that the package now no longer builds for armhf[1], which is 32-bit. This appears to have been an intentional change by Debian: gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium * do not build this package on 32bit architectures anymore Closes: #1064088 Closes: #1064089 There was no patch attached to #1064089, so I can not reproduce the problems mentioned in #1064088. I am fed up with this poorly done transition, so I won't spend more time with this. Sorry 32bit people. -- Thorsten Alteholz Fri, 26 Apr 2024 23:10:00 +0200 The transition referenced in the changelog is the time_t transition performed late last cycle; presumably then reversing this change in Ubuntu would merely exchange this FTBFS for a different one. (Perhaps one avenue of solution would be to create the requested time_t patch for #1064088?) The question is then if the armhf binary for gutenprint was deleted from the archive, would that result in other issues within the printing stack? 0: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-oracular-oracular.html#ubuntu-server-pkgset 1: https://launchpad.net/ubuntu/+source/gutenprint/5.3.4.20220624T01008808d602-3/+build/28712797 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/2081090/+subscriptions -- Mailing list: https://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 2081090] Re: gutenprint FTBFS due to 64-bit restriction
The Kubuntu/Lubuntu/Ubuntu MATE recommends will go away as soon as we regenerate the metapackages after gutenprint is removed again on armhf. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gutenprint in Ubuntu. https://bugs.launchpad.net/bugs/2081090 Title: gutenprint FTBFS due to 64-bit restriction Status in gutenprint package in Ubuntu: Triaged Bug description: The FTBFS[0] report shows an issue for gutenprint: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: architecture-is-64-bit but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed The problem is that the package now no longer builds for armhf[1], which is 32-bit. This appears to have been an intentional change by Debian: gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium * do not build this package on 32bit architectures anymore Closes: #1064088 Closes: #1064089 There was no patch attached to #1064089, so I can not reproduce the problems mentioned in #1064088. I am fed up with this poorly done transition, so I won't spend more time with this. Sorry 32bit people. -- Thorsten Alteholz Fri, 26 Apr 2024 23:10:00 +0200 The transition referenced in the changelog is the time_t transition performed late last cycle; presumably then reversing this change in Ubuntu would merely exchange this FTBFS for a different one. (Perhaps one avenue of solution would be to create the requested time_t patch for #1064088?) The question is then if the armhf binary for gutenprint was deleted from the archive, would that result in other issues within the printing stack? 0: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-oracular-oracular.html#ubuntu-server-pkgset 1: https://launchpad.net/ubuntu/+source/gutenprint/5.3.4.20220624T01008808d602-3/+build/28712797 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/2081090/+subscriptions -- Mailing list: https://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 2081090] Re: gutenprint FTBFS due to 64-bit restriction
I do not believe adding this Ubuntu diff was helpful. The actual reverse dependency output is: $ reverse-depends -b src:gutenprint No reverse dependencies found $ reverse-depends src:gutenprint Reverse-Recommends == * cups-backend-bjnp [amd64 arm64 armhf ppc64el riscv64 s390x] * kubuntu-desktop [amd64 arm64 armhf ppc64el riscv64] * lubuntu-desktop [amd64 arm64 armhf ppc64el riscv64 s390x] * lubuntu-desktop-minimal [amd64 arm64 armhf ppc64el riscv64 s390x] * printer-driver-all(for printer-driver-gutenprint) * ubuntu-mate-core [amd64 arm64 armhf ppc64el riscv64 s390x] * ubuntu-mate-desktop [amd64 arm64 armhf ppc64el riscv64 s390x] Reverse-Depends === * printer-driver-all-enforce(for printer-driver-gutenprint) printer-driver-all-enforce is an arch: all package so the unsatisfiable dependency on armhf is not a problem and actually gutenprint with the build dependency change migrated to oracular without a problem. There is a large and increasing number of universe packages that don't build on armhf, often with build-dependencies on architecture-is-64-bit. I do not think we need to try to undo those Debian changes in Ubuntu. Therefore, I intend to sync a newer version of gutenprint to undo this fix. ** Changed in: gutenprint (Ubuntu) Status: Fix Released => Triaged ** Changed in: gutenprint (Ubuntu) Assignee: Till Kamppeter (till-kamppeter) => (unassigned) ** Changed in: gutenprint (Ubuntu) Importance: High => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gutenprint in Ubuntu. https://bugs.launchpad.net/bugs/2081090 Title: gutenprint FTBFS due to 64-bit restriction Status in gutenprint package in Ubuntu: Triaged Bug description: The FTBFS[0] report shows an issue for gutenprint: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: architecture-is-64-bit but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed The problem is that the package now no longer builds for armhf[1], which is 32-bit. This appears to have been an intentional change by Debian: gutenprint (5.3.4.20220624T01008808d602-2) unstable; urgency=medium * do not build this package on 32bit architectures anymore Closes: #1064088 Closes: #1064089 There was no patch attached to #1064089, so I can not reproduce the problems mentioned in #1064088. I am fed up with this poorly done transition, so I won't spend more time with this. Sorry 32bit people. -- Thorsten Alteholz Fri, 26 Apr 2024 23:10:00 +0200 The transition referenced in the changelog is the time_t transition performed late last cycle; presumably then reversing this change in Ubuntu would merely exchange this FTBFS for a different one. (Perhaps one avenue of solution would be to create the requested time_t patch for #1064088?) The question is then if the armhf binary for gutenprint was deleted from the archive, would that result in other issues within the printing stack? 0: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20240912-oracular-oracular.html#ubuntu-server-pkgset 1: https://launchpad.net/ubuntu/+source/gutenprint/5.3.4.20220624T01008808d602-3/+build/28712797 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/2081090/+subscriptions -- Mailing list: https://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 2083629] Re: Update fonts-noto-color-emoji to 2.047
** Description changed: Impact == - - Ubuntu has included Google's color emoji font by default for years. - Annually, the Unicode Consortium releases a new Unicode standard with - new emoji. Internet communication platforms quickly adopt the new emoji - and it's important that those emoji also work on the latest Ubuntu - release. + Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the New link to see the new emoji. https://emojipedia.org/google/16.0/ Or see https://blog.emojipedia.org/google-debuts-emoji-16-0-support/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle Test Plan = The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont Where problems could occur == Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. Other Info == - There hasn't yet been a stable release of CLDR to match the new Unicode 16 version. Until this happens, we can't update gnome-characters to show the new emoji. Also, until that happens, emojibase won't update their data which is used for GTK's emoji choosers. There are some technical details about how those updates work at https://wiki.ubuntu.com/DesktopTeam/Emoji + This update is only for display of the new emoji. - We will likely do SRUs later for gnome-characters, gtk4 and gtk3 for new - emoji enablement. - - If this isn't accepted before Ubuntu 24.10's release, we will do an SRU - later. + It does not affect gnome-characters, the gtk3 or gtk4 emoji choosers, or + any other emoji choosers. ** Also affects: fonts-noto-color-emoji (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: fonts-noto-color-emoji (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: fonts-noto-color-emoji (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: fonts-noto-color-emoji (Ubuntu Oracular) Status: New => Fix Released ** Changed in: fonts-noto-color-emoji (Ubuntu Noble) Status: New => Triaged ** Changed in: fonts-noto-color-emoji (Ubuntu Jammy) Status: New => Triaged ** Changed in: fonts-noto-color-emoji (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: fonts-noto-color-emoji (Ubuntu Noble) Importance: Undecided => Low ** Changed in: fonts-noto-color-emoji (Ubuntu Oracular) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/2083629 Title: Update fonts-noto-color-emoji to 2.047 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Triaged Status in fonts-noto-color-emoji source package in Noble: Triaged Status in fonts-noto-color-emoji source package in Oracular: Fix Released Bug description: Impact == Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the New link to see the new emoji. https://emojipedia.org/google/16.0/ Or see https://blog.emojipedia.org/google-debuts-emoji-16-0-support/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle Test Plan = The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont Where problems could occur == Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue.
[Desktop-packages] [Bug 2028312] Re: does not support spec 1.5
** Changed in: desktop-file-utils (Ubuntu) Status: Triaged => Fix Released -- 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: Fix Released 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 2088609] [NEW] Update glib for Unicode 16
Public bug reported: glib needs to be updated to enable the GNOME Characters app to fully support the new emoji in Unicode 16, ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: In Progress ** Tags: noble oracular -- 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/2088609 Title: Update glib for Unicode 16 Status in glib2.0 package in Ubuntu: In Progress Bug description: glib needs to be updated to enable the GNOME Characters app to fully support the new emoji in Unicode 16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2088609/+subscriptions -- Mailing list: https://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 2088446] Re: UTF16 document saved with automatic encoding detection is saved as UTF8 instead of UTF16
Thank you for reporting this issue. I have forwarded your report to the developers of gnome-text-editor: https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/743 ** Changed in: gnome-text-editor (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gnome-text-editor/-/issues #743 https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/743 ** Also affects: gnome-text-editor via https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/743 Importance: Unknown Status: Unknown ** Changed in: gnome-text-editor (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2088446 Title: UTF16 document saved with automatic encoding detection is saved as UTF8 instead of UTF16 Status in GNOME Text Editor: Unknown Status in gnome-text-editor package in Ubuntu: Triaged Bug description: UTF16 document saved with automatic encoding detection is saved as UTF8 instead of UTF16. Example given: -- - There is an "UTF16_sample.txt" document included in this bug. It's an UTF16 encoded file: $ file UTF16_sample.txt UTF16_sample.txt: Unicode text, UTF-16, little-endian text, with CRLF line terminators - Open it with with gnome-text-editor. It is correctly interpreted and it's content are shown as: aeiouáéíóú AEIOUÁÉÍÓÚ - Don't modify it's content, just save the document. It uses automatic encoding detection but it saves the document as UTF8 instead of UTF16: $ file UTF16_sample.txt UTF16_sample.txt: Unicode text, UTF-8 text, with CRLF line terminators In my opinion this is a bug because the encoding should be the same of the original file when saving with automatic encoding detection. But, if it's not being considered a bug, I think that at least there should be a warning when saving is going to replace a document with a different encoding using automatic encoding detection. Note: if UTF16 encoding is manually selected in "Save As" dialog the resulting file encoding is correct so the problem should be the autodetection that worked for reading the document but fails when saving. Additional Info: $ lsb_release -rd: Description: Ubuntu 24.10 Release: 24.10 $ apt-cache policy gnome-text-editor gnome-text-editor: Instalados: 47.0-1ubuntu2 Candidato: 47.0-1ubuntu2 Tabla de versión: *** 47.0-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports oracular/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-text-editor/+bug/2088446/+subscriptions -- Mailing list: https://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 2086846] Re: Please merge libjpeg-turbo 1:2.1.5-3 from debian unstable
** Changed in: libjpeg-turbo (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/2086846 Title: Please merge libjpeg-turbo 1:2.1.5-3 from debian unstable Status in libjpeg-turbo package in Ubuntu: Fix Committed Bug description: libjpeg-turbo (1:2.1.5-3) unstable; urgency=medium [ Pino Toscano ] * Enable Java binding only where Java is available. [ Debian Janitor ] * Remove constraints unnecessary since buster (oldstable). [ Mike Gabriel ] * debian/control: + White-space fix in B-D field + trailing comma. + Bump Standards-Version to 4.7.0. No changes needed. -- Mike Gabriel Thu, 25 Apr 2024 16:17:41 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/2086846/+subscriptions -- Mailing list: https://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 2088201] Re: Please merge grilo-plugins 0.3.16-3 from debian unstable
** Changed in: grilo-plugins (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: grilo-plugins (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: grilo-plugins (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/2088201
Title:
Please merge grilo-plugins 0.3.16-3 from debian unstable
Status in grilo-plugins package in Ubuntu:
Fix Committed
Bug description:
grilo-plugins (0.3.16-3) unstable; urgency=medium
* Remove non-working plugins: appletrailers, euronews and raitv.
-- Alberto Garcia Fri, 25 Oct 2024 11:25:50 +0200
grilo-plugins (0.3.16-2) unstable; urgency=medium
[ Jeremy Bícha ]
* Drop unused Build-Depends: libgdata-dev (Closes: #1082014)
[ Alberto Garcia ]
* debian/control:
- Remove OpenSubtitles and YouTube from the package description.
- Update Standards-Version to 4.7.0 (no changes).
* debian/copyright:
- Update copyright years.
-- Alberto Garcia Wed, 18 Sep 2024 14:58:31 +0200
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/2088201/+subscriptions
--
Mailing list: https://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 1875243] Re: Unexpressed dependency between gnome-control-center and mutter-common
There is now an upstream issue since vanilla gnome-control-center also has a dependency on mutter-common https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues/59 ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released ** Changed in: gnome-control-center (Ubuntu) Status: Fix Released => Fix Committed ** Bug watch added: gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues #59 https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues/59 -- 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/1875243 Title: Unexpressed dependency between gnome-control-center and mutter-common Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: Ubuntu Release: 20.04 Package Version: 1:3.36.1-1ubuntu5 Steps to reproduce: Pre-requisite: Ubuntu system with gnome-control-center installed but not mutter-common (ex: Regolith 1.4/20.04) 1. launch gnome-control-center from terminal 2. navigate to display tab Observed behaviour: (gnome-control-center:54513): GLib-GIO-ERROR **: 13:49:43.782: Settings schema 'org.gnome.mutter' is not installed (core dumped) Expected behaviour: no crash Once I install the package mutter-common, the crash does not occur and I am able to use gnome-control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1875243/+subscriptions -- Mailing list: https://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 2077538] Re: gnome-remote-desktop uses software rendering
** Bug watch added: gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues #224 https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/224 ** Also affects: gnome-remote-desktop via https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/224 Importance: Unknown Status: Unknown ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2077538 Title: gnome-remote-desktop uses software rendering Status in GNOME Remote Desktop: Unknown Status in gnome-remote-desktop package in Ubuntu: Triaged Bug description: gnome-remote-desktop uses software rendering by default, which is incredible slow on some hardwares. If the user is added to the video and render group, graphics acceleration is used. These groups are not in the default, so I think it would make sense to add them. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-remote-desktop 46.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 21 13:35:14 2024 InstallationDate: Installed on 2024-08-12 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-remote-desktop UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-remote-desktop/+bug/2077538/+subscriptions -- Mailing list: https://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 2014606] Re: libgspell-1-common is required by libgspell-1-2 but is empty.
We aren't going to diverge from Debian because of this minor issue. Several other packages are affected by this and it's basically intentional behavior. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gspell in Ubuntu. https://bugs.launchpad.net/bugs/2014606 Title: libgspell-1-common is required by libgspell-1-2 but is empty. Status in gspell package in Ubuntu: Won't Fix Bug description: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libgspell-1-common/filelist It doesn't need to be required, recommended or even exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gspell/+bug/2014606/+subscriptions -- Mailing list: https://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 2014606] Re: libgspell-1-common is required by libgspell-1-2 but is empty.
** Changed in: gspell (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gspell in Ubuntu. https://bugs.launchpad.net/bugs/2014606 Title: libgspell-1-common is required by libgspell-1-2 but is empty. Status in gspell package in Ubuntu: Won't Fix Bug description: The Debian version list of files look like translations that were automatically stripped for Ubuntu- https://packages.debian.org/sid/all/libgspell-1-common/filelist It doesn't need to be required, recommended or even exist at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gspell/+bug/2014606/+subscriptions -- Mailing list: https://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 2084839] Re: Settings app slows down and freezes on Appearance tab
I've linked a Debian bug & its upstream link that sounds to me like it's the same issue. ** Bug watch added: Debian Bug tracker #1079580 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079580 ** Also affects: gnome-control-center (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079580 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #3198 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3198 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3198 Importance: Unknown Status: Unknown -- 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/2084839 Title: Settings app slows down and freezes on Appearance tab Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Status in gnome-control-center package in Debian: Unknown Bug description: I have a couple different desktops installed on Ubuntu -- the regular Ubuntu Wayland and Xorg, but also Gnome and Xubuntu. This installs additional desktop artwork (wallpapers). As a result, when I open Settings and go to the Appearance tab, everything suddenly slows down. It then freezes, along with the rest of the desktop. Once it eventually unsticks itself, whatever software I happen to have open -- usually Firefox, Thunderbird, and Discord -- have shut off. I've checked the logs -- there seems to be some issue with large amounts of memory being used, resulting in Ubuntu shutting down Firefox/Thunderbird/Discord, and the gnome-control-center / app- gnome.org.gnome.Settings failing to respond. This is the message I found in Logs afterwards: 20:39:15 systemd: app-gnome-org.gnome.Settings-19194.scope: Consumed 1min 37.065s CPU time, 5.9G memory peak, 144.3M memory swap peak. I'm currently using Ubuntu 24.10 on Xorg, but I've had this issue on Wayland as well. I've attached the log messages for review. My system specifications are as follows: # System Details Report --- ## Report details - **Date generated:** 2024-10-17 21:38:06 ## Hardware Information: - **Hardware Model:** HP Laptop - **Memory:** 8.0 GiB - **Processor:** Intel® Celeron® N4020 × 2 - **Graphics:**Intel® UHD Graphics 600 (GLK 2) - **Disk Capacity:** 1.0 TB ## Software Information: - **Firmware Version:**F.63 - **OS Name:** Ubuntu 24.10 - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 47 - **Windowing System:**X11 - **Kernel Version:** Linux 6.11.0-8-generic Thank you kindly for your time. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-control-center 1:47.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 21:21:18 2024 InstallationDate: Installed on 2024-10-12 (5 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2084839/+subscriptions -- Mailing list: https://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 2084895] Re: libproxy: gobject-introspection support is disabled
I have begun work on this at https://salsa.debian.org/gnome- team/libproxy/-/merge_requests/6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/2084895 Title: libproxy: gobject-introspection support is disabled Status in libproxy package in Ubuntu: New Bug description: Currently libproxy is build without gobject-introspection support leading to missing support for different programming language. This leads to application written in vala, python & co not being able to use the correct proxy within such an environment. Please build libproxy with gobject-introspection support enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/2084895/+subscriptions -- Mailing list: https://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 2051015] Re: Unable to install : dependencies missing
Those dependencies exist in Ubuntu 24.04 LTS. What version of Ubuntu are you using? ** Changed in: harfbuzz (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to harfbuzz in Ubuntu. https://bugs.launchpad.net/bugs/2051015 Title: Unable to install : dependencies missing Status in harfbuzz package in Ubuntu: Incomplete Bug description: Version 8.3.0-2 Package depends on gir1.2-freetype2-2.0-dev and gir1.2-gobject-2.0-dev that do not exist. So this version cannot be installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/harfbuzz/+bug/2051015/+subscriptions -- Mailing list: https://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 2083274] Re: cursor sizes are wrong in Plasma/Wayland with gtk4 4.16 and scaling
** Description changed: Impact -- - If scaling (200% or fractional scaling like 125%, etc.) is enabled, cursor sizes are wrong with KDE Plasma. + If scaling (200% or fractional scaling like 125%, etc.) is enabled, cursor sizes are wrong (too big) with KDE Plasma. + + This happens with gtk4 4.16 on Ubuntu 24.10. I don't believe this + happens with Ubuntu 24.04 LTS. There is a fix for GNOME 48 (Ubuntu + 25.04) but it also requires mutter changes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2083274 Title: cursor sizes are wrong in Plasma/Wayland with gtk4 4.16 and scaling Status in GTK+: Unknown Status in gtk4 package in Ubuntu: Triaged Status in gtk4 package in Debian: Fix Released Bug description: Impact -- If scaling (200% or fractional scaling like 125%, etc.) is enabled, cursor sizes are wrong (too big) with KDE Plasma. This happens with gtk4 4.16 on Ubuntu 24.10. I don't believe this happens with Ubuntu 24.04 LTS. There is a fix for GNOME 48 (Ubuntu 25.04) but it also requires mutter changes. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2083274/+subscriptions -- Mailing list: https://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 2083274] Re: cursor sizes are wrong in Plasma/Wayland with gtk4 4.16 and scaling
** Description changed: Impact -- If scaling (200% or fractional scaling like 125%, etc.) is enabled, cursor sizes are wrong with KDE Plasma. - - This has been fixed in gtk4 main and will likely be included in a future - 4.16.x release but we would prefer to fix this issue before Ubuntu 24.10 - is released. ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #7031 https://gitlab.gnome.org/GNOME/gtk/-/issues/7031 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/7031 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2083274 Title: cursor sizes are wrong in Plasma/Wayland with gtk4 4.16 and scaling Status in GTK+: Unknown Status in gtk4 package in Ubuntu: Triaged Status in gtk4 package in Debian: Fix Released Bug description: Impact -- If scaling (200% or fractional scaling like 125%, etc.) is enabled, cursor sizes are wrong with KDE Plasma. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2083274/+subscriptions -- Mailing list: https://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 2083715] Re: Update gtk4 to 4.16.3
accidental duplicate ** Changed in: gtk4 (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2083715 Title: Update gtk4 to 4.16.3 Status in gtk4 package in Ubuntu: Invalid Bug description: There is a new point release in the stable GTK 4.16 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.16.3/NEWS Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- Many of the default Ubuntu desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are not affected by this SRU. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2083715/+subscriptions -- Mailing list: https://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 2083714] [NEW] Update gtk4 to 4.16.3
Public bug reported: There is a new point release in the stable GTK 4.16 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.16.3/NEWS Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- Many of the default Ubuntu desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are not affected by this SRU. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gtk4 (Ubuntu) Importance: High Status: Triaged ** Tags: oracular upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2083714 Title: Update gtk4 to 4.16.3 Status in gtk4 package in Ubuntu: Triaged Bug description: There is a new point release in the stable GTK 4.16 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.16.3/NEWS Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- Many of the default Ubuntu desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are not affected by this SRU. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2083714/+subscriptions -- Mailing list: https://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 2083715] [NEW] Update gtk4 to 4.16.3
Public bug reported: There is a new point release in the stable GTK 4.16 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.16.3/NEWS Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- Many of the default Ubuntu desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are not affected by this SRU. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gtk4 (Ubuntu) Importance: High Status: Triaged ** Tags: oracular upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2083715 Title: Update gtk4 to 4.16.3 Status in gtk4 package in Ubuntu: Triaged Bug description: There is a new point release in the stable GTK 4.16 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.16.3/NEWS Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- Many of the default Ubuntu desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are not affected by this SRU. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2083715/+subscriptions -- Mailing list: https://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 2083629] Re: Update fonts-noto-color-emoji to 2.047
** Description changed: Impact == Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the New link to see the new emoji. https://emojipedia.org/google/16.0/ Or see https://blog.emojipedia.org/google-debuts-emoji-16-0-support/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle Test Plan = The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont Where problems could occur == Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. Other Info == There hasn't yet been a stable release of CLDR to match the new Unicode 16 version. Until this happens, we can't update gnome-characters to show the new emoji. Also, until that happens, emojibase won't update their data which is used for GTK's emoji choosers. We will likely do SRUs later for gnome-characters, gtk4 and gtk3 for new emoji enablement. + + If this isn't accepted before Ubuntu 24.10's release, we will do an SRU + later. ** Description changed: Impact == Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the New link to see the new emoji. https://emojipedia.org/google/16.0/ Or see https://blog.emojipedia.org/google-debuts-emoji-16-0-support/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle Test Plan = The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont Where problems could occur == Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. Other Info == - There hasn't yet been a stable release of CLDR to match the new Unicode 16 version. Until this happens, we can't update gnome-characters to show the new emoji. Also, until that happens, emojibase won't update their data which is used for GTK's emoji choosers. + There hasn't yet been a stable release of CLDR to match the new Unicode 16 version. Until this happens, we can't update gnome-characters to show the new emoji. Also, until that happens, emojibase won't update their data which is used for GTK's emoji choosers. There are some technical details about how those updates work at https://wiki.ubuntu.com/DesktopTeam/Emoji We will likely do SRUs later for gnome-characters, gtk4 and gtk3 for new emoji enablement. If this isn't accepted before Ubuntu 24.10's release, we will do an SRU later. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/2083629 Title: Update fonts-noto-color-emoji to 2.047 Status in fonts-noto-color-emoji package in Ubuntu: In Progress Bug description: Impact == Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the New link to see the new em
[Desktop-packages] [Bug 2083629] [NEW] Update fonts-noto-color-emoji to 2.047
Public bug reported: Impact == Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the New link to see the new emoji. https://emojipedia.org/google/16.0/ Or see https://blog.emojipedia.org/google-debuts-emoji-16-0-support/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle Test Plan = The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont Where problems could occur == Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. Other Info == There hasn't yet been a stable release of CLDR to match the new Unicode 16 version. Until this happens, we can't update gnome-characters to show the new emoji. Also, until that happens, emojibase won't update their data which is used for GTK's emoji choosers. We will likely do SRUs later for gnome-characters, gtk4 and gtk3 for new emoji enablement. ** Affects: fonts-noto-color-emoji (Ubuntu) Importance: Low Status: In Progress ** Tags: oracular upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/2083629 Title: Update fonts-noto-color-emoji to 2.047 Status in fonts-noto-color-emoji package in Ubuntu: In Progress Bug description: Impact == Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the New link to see the new emoji. https://emojipedia.org/google/16.0/ Or see https://blog.emojipedia.org/google-debuts-emoji-16-0-support/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle Test Plan = The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont Where problems could occur == Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. Other Info == There hasn't yet been a stable release of CLDR to match the new Unicode 16 version. Until this happens, we can't update gnome-characters to show the new emoji. Also, until that happens, emojibase won't update their data which is used for GTK's emoji choosers. We will likely do SRUs later for gnome-characters, gtk4 and gtk3 for new emoji enablement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/2083629/+subscriptions -- Mailing list: https://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 2083546] [NEW] autopkgtests are failing on some architectures
Public bug reported: Impact -- We added autopkgtests to the highway library as part of its MIR (LP: #2070807). Those autopkgtests are passing on amd64 but are failing on some architectures. highway and jpeg-xl will not be promoted to main until Ubuntu 25.04, but since the fix exists, I thought it was worth trying to get the autopkgtests passing on more architectures for Ubuntu 24.10. On the other hand, this fix isn't critical at all. highway is seeded in all the Ubuntu desktop flavors except for Ubuntu Desktop. ** Affects: highway (Ubuntu) Importance: Low Status: In Progress ** Tags: oracular -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to highway in Ubuntu. https://bugs.launchpad.net/bugs/2083546 Title: autopkgtests are failing on some architectures Status in highway package in Ubuntu: In Progress Bug description: Impact -- We added autopkgtests to the highway library as part of its MIR (LP: #2070807). Those autopkgtests are passing on amd64 but are failing on some architectures. highway and jpeg-xl will not be promoted to main until Ubuntu 25.04, but since the fix exists, I thought it was worth trying to get the autopkgtests passing on more architectures for Ubuntu 24.10. On the other hand, this fix isn't critical at all. highway is seeded in all the Ubuntu desktop flavors except for Ubuntu Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/highway/+bug/2083546/+subscriptions -- Mailing list: https://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 2083528] Re: libgdata: FTBFS with gcc-14 on armhf
** Tags added: ftbfs oracular
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgdata in Ubuntu.
https://bugs.launchpad.net/bugs/2083528
Title:
libgdata: FTBFS with gcc-14 on armhf
Status in libgdata package in Ubuntu:
In Progress
Bug description:
libgdata fails to build on armhf with the strict pointer type matching
of gcc-14, because it internally mixes 64-bit time_t and 32-bit
GTimeVal.
../demos/calendar/calendar-cli.c: In function ‘tv_to_iso8601_date’:
../demos/calendar/calendar-cli.c:47:22: error: passing argument 1 of ‘gmtime’
from incompatible pointer type [-Wincompatible-pointer-types]
47 | tm = gmtime (&tv->tv_sec);
| ^~~
| |
| glong * {aka long int *}
[...]
/usr/include/time.h:140:18: note: expected ‘const time_t *’ {aka ‘const long
long int *’} but argument is of type ‘glong *’ {aka ‘long int *’}
https://launchpadlibrarian.net/749244194/buildlog_ubuntu-oracular-
armhf.libgdata_0.18.1-7_BUILDING.txt.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgdata/+bug/2083528/+subscriptions
--
Mailing list: https://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 2078055] Re: librsvg needs cargo-c but it's not available on i386
** Changed in: rust-cargo-c (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2078055 Title: librsvg needs cargo-c but it's not available on i386 Status in librsvg package in Ubuntu: Fix Released Status in rust-cargo-c package in Ubuntu: Fix Released Bug description: Starting with the librsvg 2.59 series (2.58.9*), librsvg requires cargo-c to build. cargo-c comes from the Debian source rust-cargo-c. The issue is that librsvg needs to be built on i386, but rust-cargo-c is not currently built for i386. The list of Build-Depends is kinda long. Currently except for librsvg, I believe the only rust-related packages built on i386 are rustc and cargo (which is totally different from cargo-c). https://packages.debian.org/source/unstable/rust-cargo-c Option 1 Stop building librsvg on i386. This might not be practical but it would offer some simplicity. I'm not sure of a perfect way to discover reverse-depends on i386. We may be able to drop gtk4's build dependency on librsvg. It looks like it is optional for cairo, but not sure whether it would be a good idea to attempt to remove it there. Option 2 Build cargo-c as arch:all. Unfortunately, this won't work since cargo-c ships arch-specific binaries unlike many of the rust-* .deb packages. Option 3 Attempt to vendor cargo-c inside the librsvg package. This is what I suspect to be the solution we'll need to go with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2078055/+subscriptions -- Mailing list: https://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 2083440] [NEW] FFe: unvendor libspelling from gnome-text-editor
Public bug reported: gnome-text-editor switched to using libspelling with their 47 RC release at the beginning of September. libspelling is based on code that was originally written for gnome-text-editor and gnome-builder. At that point, Ubuntu 24.10 already had gnome-text-editor 47 Beta and it takes time for a package to be promoted to main. Therefore, we vendored libspelling in Ubuntu's gnome-text-editor packaging and began the MIR process. Since the MIR was approved today, we would like to remove the vendoring and promote libspelling to main. This would simplify our packaging. If this Feature Freeze Exception is not approved, we will unvendor libspelling for Ubuntu 25.04 instead. MIR link is LP: #2080062 ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New ** Tags: oracular -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2083440 Title: FFe: unvendor libspelling from gnome-text-editor Status in gnome-text-editor package in Ubuntu: New Bug description: gnome-text-editor switched to using libspelling with their 47 RC release at the beginning of September. libspelling is based on code that was originally written for gnome-text-editor and gnome-builder. At that point, Ubuntu 24.10 already had gnome-text-editor 47 Beta and it takes time for a package to be promoted to main. Therefore, we vendored libspelling in Ubuntu's gnome-text-editor packaging and began the MIR process. Since the MIR was approved today, we would like to remove the vendoring and promote libspelling to main. This would simplify our packaging. If this Feature Freeze Exception is not approved, we will unvendor libspelling for Ubuntu 25.04 instead. MIR link is LP: #2080062 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2083440/+subscriptions -- Mailing list: https://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 2083344] [NEW] Update oracular to new mozjs releases
Public bug reported: Impact -- ** Affects: mozjs115 (Ubuntu) Importance: Undecided Status: New ** Affects: mozjs128 (Ubuntu) Importance: Undecided Status: New ** Tags: oracular upgrade-software-version ** Also affects: mozjs115 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs115 in Ubuntu. https://bugs.launchpad.net/bugs/2083344 Title: Update oracular to new mozjs releases Status in mozjs115 package in Ubuntu: New Status in mozjs128 package in Ubuntu: New Bug description: Impact -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs115/+bug/2083344/+subscriptions -- Mailing list: https://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 2082087] Re: Update gstreamer packages from 1.24.7 to 1.24.8 for oracular
** Changed in: gst-libav1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-ugly1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-python1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2082087 Title: Update gstreamer packages from 1.24.7 to 1.24.8 for oracular Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 1.24 series. It would be helpful to have these fixes in Ubuntu 24.10 before the release. https://gstreamer.freedesktop.org/releases/1.24/#1.24.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/2082087/+subscriptions -- Mailing list: https://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 2083274] [NEW] cursor sizes are wrong in Plasma/Wayland with gtk4 4.16 and scaling
Public bug reported: Impact -- If scaling (200% or fractional scaling like 125%, etc.) is enabled, cursor sizes are wrong with KDE Plasma. This has been fixed in gtk4 main and will likely be included in a future 4.16.x release but we would prefer to fix this issue before Ubuntu 24.10 is released. ** Affects: gtk4 (Ubuntu) Importance: Medium Status: Triaged ** Affects: gtk4 (Debian) Importance: Unknown Status: Unknown ** Tags: oracular ** Bug watch added: Debian Bug tracker #1083055 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083055 ** Also affects: gtk4 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083055 Importance: Unknown Status: Unknown ** Description changed: Impact -- - If fractional scaling is enabled, cursor sizes are wrong with KDE Plasma. + If scaling (200% or fractional scaling like 125%, etc.) is enabled, cursor sizes are wrong with KDE Plasma. This has been fixed in gtk4 main and will likely be included in a future 4.16.x release but we would prefer to fix this issue before Ubuntu 24.10 is released. ** Summary changed: - cursor sizes are wrong in Plasma/Wayland with gtk4 4.16 and fractional scaling + cursor sizes are wrong in Plasma/Wayland with gtk4 4.16 and scaling -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2083274 Title: cursor sizes are wrong in Plasma/Wayland with gtk4 4.16 and scaling Status in gtk4 package in Ubuntu: Triaged Status in gtk4 package in Debian: Unknown Bug description: Impact -- If scaling (200% or fractional scaling like 125%, etc.) is enabled, cursor sizes are wrong with KDE Plasma. This has been fixed in gtk4 main and will likely be included in a future 4.16.x release but we would prefer to fix this issue before Ubuntu 24.10 is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2083274/+subscriptions -- Mailing list: https://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 2082017] Re: Consider reverting to ngl renderer for oracular
** Changed in: gtk4 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2082017 Title: Consider reverting to ngl renderer for oracular Status in gtk4 package in Ubuntu: Fix Committed Bug description: Background -- gtk4 switched their default renderer to ngl for the 4.14 series, included in Ubuntu 24.04 LTS and they switched the default render again to vulkan for the 4.16 series included in Ubuntu 24.10. This was preannounced here: https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ We were unable to get a prerelease of gtk4 4.16 into Debian before 4.16.0 was released and there has been only limited end user testing of the vulkan renderer used in gtk 4.16. Historically, the Ubuntu Desktop team has only done limited bugfix SRUs of GTK to non-LTS releases. There's not a policy against it at all; it's just been a tradeoff with limited capacity and too many things to do. This is a proposal to switch back to the ngl renderer for Ubuntu 24.10 to approximately match what is used in Ubuntu 24.04 LTS. For Ubuntu 25.04, we would go back to using gtk4's default renderer (vulkan). Intel - gtk4 is working fine for me on Intel graphics on a laptop from a few years ago. But there have been issues for people who use other graphics drivers. Open Issues --- https://gitlab.gnome.org/GNOME/gtk/-/issues/?label_name%5B%5D=Vulkan%20Renderer Timing -- If we are going to make a switch, we need to do it very soon (this week or by Monday) because we are late in the Ubuntu 24.10 release process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2082017/+subscriptions -- Mailing list: https://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 2083260] [NEW] Update gnome-remote-desktop to 47.0
Public bug reported: Impact -- This is just a translations update. Also it is a nicer version number: 47.0 instead of 47~rc https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/47.0/NEWS We use Ubuntu language packs for this package so now is basically the last time to update translations for Ubuntu 24.10 (since we have not been updating language packs except for LTS point releases) Other Info --- We run the upstream test suite both at build time and as autopkgtests ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: In Progress ** Tags: oracular -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2083260 Title: Update gnome-remote-desktop to 47.0 Status in gnome-remote-desktop package in Ubuntu: In Progress Bug description: Impact -- This is just a translations update. Also it is a nicer version number: 47.0 instead of 47~rc https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/47.0/NEWS We use Ubuntu language packs for this package so now is basically the last time to update translations for Ubuntu 24.10 (since we have not been updating language packs except for LTS point releases) Other Info --- We run the upstream test suite both at build time and as autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2083260/+subscriptions -- Mailing list: https://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 2083241] Re: Update webkit2gtk to 2.46.1
** Changed in: webkit2gtk (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2083241 Title: Update webkit2gtk to 2.46.1 Status in webkit2gtk package in Ubuntu: Fix Committed Bug description: Impact -- New webkit2gtk releases usually include security fixes and are therefore handled similar to how new Firefox releases are handled. webkit2gtk 2.46.1 will be released as a security update to Ubuntu 24.04 LTS soon (and 22.04 LTS if it builds there). It would be helpful to get this built now for 24.10 before Final Freeze. Otherwise, it will just get updated later. This is the first point release in the stable 2.46.x series and includes several other bug fixes also. https://webkitgtk.org/2024/09/30/webkitgtk2.46.1-released.html Other Info -- The last time we built this package, it took about 2.5 days to do the riscv64 build. https://launchpad.net/ubuntu/+source/webkit2gtk/2.46.0-2/+latestbuild/riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2083241/+subscriptions -- Mailing list: https://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 2083259] [NEW] Update librsvg to 2.59.1
Public bug reported: Impact - There is a new bugfix release in the stable 2.59.x series https://gitlab.gnome.org/GNOME/librsvg/-/blob/2.59.1/NEWS Other Info - This package has a thorough test suite and minimal autopkgtests ** Affects: librsvg (Ubuntu) Importance: Undecided Status: In Progress ** Tags: oracular -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2083259 Title: Update librsvg to 2.59.1 Status in librsvg package in Ubuntu: In Progress Bug description: Impact - There is a new bugfix release in the stable 2.59.x series https://gitlab.gnome.org/GNOME/librsvg/-/blob/2.59.1/NEWS Other Info - This package has a thorough test suite and minimal autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2083259/+subscriptions -- Mailing list: https://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 2083241] Re: Update webkit2gtk to 2.46.1
** Description changed: Impact -- - New webkit2gtk releases usually include security features. webkit2gtk 2.46.1 will be released as a security update to Ubuntu 24.04 LTS soon (and 22.04 LTS if it builds there). It would be helpful to get this built now for 24.10 before Final Freeze. Otherwise, it will just get updated later. + New webkit2gtk releases usually include security fixes and are therefore handled similar to how new Firefox releases are handled. webkit2gtk 2.46.1 will be released as a security update to Ubuntu 24.04 LTS soon (and 22.04 LTS if it builds there). It would be helpful to get this built now for 24.10 before Final Freeze. Otherwise, it will just get updated later. This is the first point release in the stable 2.46.x series and includes several other bug fixes also. https://webkitgtk.org/2024/09/30/webkitgtk2.46.1-released.html Other Info -- The last time we built this package, it took about 2.5 days to do the riscv64 build. https://launchpad.net/ubuntu/+source/webkit2gtk/2.46.0-2/+latestbuild/riscv64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2083241 Title: Update webkit2gtk to 2.46.1 Status in webkit2gtk package in Ubuntu: Triaged Bug description: Impact -- New webkit2gtk releases usually include security fixes and are therefore handled similar to how new Firefox releases are handled. webkit2gtk 2.46.1 will be released as a security update to Ubuntu 24.04 LTS soon (and 22.04 LTS if it builds there). It would be helpful to get this built now for 24.10 before Final Freeze. Otherwise, it will just get updated later. This is the first point release in the stable 2.46.x series and includes several other bug fixes also. https://webkitgtk.org/2024/09/30/webkitgtk2.46.1-released.html Other Info -- The last time we built this package, it took about 2.5 days to do the riscv64 build. https://launchpad.net/ubuntu/+source/webkit2gtk/2.46.0-2/+latestbuild/riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2083241/+subscriptions -- Mailing list: https://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 2083241] [NEW] Update webkit2gtk to 2.46.1
Public bug reported: Impact -- New webkit2gtk releases usually include security features. webkit2gtk 2.46.1 will be released as a security update to Ubuntu 24.04 LTS soon (and 22.04 LTS if it builds there). It would be helpful to get this built now for 24.10 before Final Freeze. Otherwise, it will just get updated later. This is the first point release in the stable 2.46.x series and includes several other bug fixes also. https://webkitgtk.org/2024/09/30/webkitgtk2.46.1-released.html Other Info -- The last time we built this package, it took about 2.5 days to do the riscv64 build. https://launchpad.net/ubuntu/+source/webkit2gtk/2.46.0-2/+latestbuild/riscv64 ** Affects: webkit2gtk (Ubuntu) Importance: Medium Status: Triaged ** Tags: oracular -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2083241 Title: Update webkit2gtk to 2.46.1 Status in webkit2gtk package in Ubuntu: Triaged Bug description: Impact -- New webkit2gtk releases usually include security features. webkit2gtk 2.46.1 will be released as a security update to Ubuntu 24.04 LTS soon (and 22.04 LTS if it builds there). It would be helpful to get this built now for 24.10 before Final Freeze. Otherwise, it will just get updated later. This is the first point release in the stable 2.46.x series and includes several other bug fixes also. https://webkitgtk.org/2024/09/30/webkitgtk2.46.1-released.html Other Info -- The last time we built this package, it took about 2.5 days to do the riscv64 build. https://launchpad.net/ubuntu/+source/webkit2gtk/2.46.0-2/+latestbuild/riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2083241/+subscriptions -- Mailing list: https://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 2082532] Re: Background color of some apps in Ubuntu 24.10 beta vary with accent colour
** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- 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/2082532 Title: Background color of some apps in Ubuntu 24.10 beta vary with accent colour Status in gnome-control-center package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: New Bug description: In Ubuntu 24.10 beta, the background color of some apps, such as the Settings app and the Calculator app goes darker when using the Yellow accent colour. This problem does not occur with any other accent colour. Attached is a comparison of the two apps; showing the issue when using Yellow accent colour, and how it normally should be (I've used Orange accent colour to demonstrate the latter.) Even though in my testing I have found the issue with these two apps, this issue might persist on other apps as well. My hitch is that the yellow accent colour had been ported from upstream Gnome without changing the background colour attribute in question; while the other accent colours are from prior Ubuntu versions. Please look into this issue and follow up ASAP. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-control-center 1:47.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 26 20:53:25 2024 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oracular on 2024-09-23 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2082532/+subscriptions -- Mailing list: https://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 2082017] Re: Consider reverting to ngl renderer for oracular
** Changed in: gtk4 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2082017 Title: Consider reverting to ngl renderer for oracular Status in gtk4 package in Ubuntu: In Progress Bug description: Background -- gtk4 switched their default renderer to ngl for the 4.14 series, included in Ubuntu 24.04 LTS and they switched the default render again to vulkan for the 4.16 series included in Ubuntu 24.10. This was preannounced here: https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ We were unable to get a prerelease of gtk4 4.16 into Debian before 4.16.0 was released and there has been only limited end user testing of the vulkan renderer used in gtk 4.16. Historically, the Ubuntu Desktop team has only done limited bugfix SRUs of GTK to non-LTS releases. There's not a policy against it at all; it's just been a tradeoff with limited capacity and too many things to do. This is a proposal to switch back to the ngl renderer for Ubuntu 24.10 to approximately match what is used in Ubuntu 24.04 LTS. For Ubuntu 25.04, we would go back to using gtk4's default renderer (vulkan). Intel - gtk4 is working fine for me on Intel graphics on a laptop from a few years ago. But there have been issues for people who use other graphics drivers. Open Issues --- https://gitlab.gnome.org/GNOME/gtk/-/issues/?label_name%5B%5D=Vulkan%20Renderer Timing -- If we are going to make a switch, we need to do it very soon (this week or by Monday) because we are late in the Ubuntu 24.10 release process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2082017/+subscriptions -- Mailing list: https://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 2082087] [NEW] Update gstreamer packages from 1.24.7 to 1.24.8 for oracular
Public bug reported: Impact -- There is a new bugfix release in the stable 1.24 series. It would be helpful to have these fixes in Ubuntu 24.10 before the release. https://gstreamer.freedesktop.org/releases/1.24/#1.24.8 ** Affects: gst-libav1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gst-plugins-ugly1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gst-python1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: oracular ** Also affects: gst-libav1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-ugly1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-python1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2082087 Title: Update gstreamer packages from 1.24.7 to 1.24.8 for oracular Status in gst-libav1.0 package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gst-plugins-good1.0 package in Ubuntu: New Status in gst-plugins-ugly1.0 package in Ubuntu: New Status in gst-python1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Bug description: Impact -- There is a new bugfix release in the stable 1.24 series. It would be helpful to have these fixes in Ubuntu 24.10 before the release. https://gstreamer.freedesktop.org/releases/1.24/#1.24.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/2082087/+subscriptions -- Mailing list: https://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 2082017] [NEW] Consider reverting to ngl renderer for oracular
Public bug reported: Background -- gtk4 switched their default renderer to ngl for the 4.14 series, included in Ubuntu 24.04 LTS and they switched the default render again to vulkan for the 4.16 series included in Ubuntu 24.10. This was preannounced here: https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ We were unable to get a prerelease of gtk4 4.16 into Debian before 4.16.0 was released and there has been only limited end user testing of the vulkan renderer used in gtk 4.16. Historically, the Ubuntu Desktop team has only done limited bugfix SRUs of GTK to non-LTS releases. There's not a policy against it at all; it's just been a tradeoff with limited capacity and too many things to do. This is a proposal to switch back to the ngl renderer for Ubuntu 24.10 to approximately match what is used in Ubuntu 24.04 LTS. For Ubuntu 25.04, we would go back to using gtk4's default renderer (vulkan). Intel - gtk4 is working fine for me on Intel graphics on a laptop from a few years ago. But there have been issues for people who use other graphics drivers. Open Issues --- https://gitlab.gnome.org/GNOME/gtk/-/issues/?label_name%5B%5D=Vulkan%20Renderer Timing -- If we are going to make a switch, we need to do it very soon (this week or by Monday) because we are late in the Ubuntu 24.10 release process. ** Affects: gtk4 (Ubuntu) Importance: High Status: New ** Tags: oracular -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2082017 Title: Consider reverting to ngl renderer for oracular Status in gtk4 package in Ubuntu: New Bug description: Background -- gtk4 switched their default renderer to ngl for the 4.14 series, included in Ubuntu 24.04 LTS and they switched the default render again to vulkan for the 4.16 series included in Ubuntu 24.10. This was preannounced here: https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ We were unable to get a prerelease of gtk4 4.16 into Debian before 4.16.0 was released and there has been only limited end user testing of the vulkan renderer used in gtk 4.16. Historically, the Ubuntu Desktop team has only done limited bugfix SRUs of GTK to non-LTS releases. There's not a policy against it at all; it's just been a tradeoff with limited capacity and too many things to do. This is a proposal to switch back to the ngl renderer for Ubuntu 24.10 to approximately match what is used in Ubuntu 24.04 LTS. For Ubuntu 25.04, we would go back to using gtk4's default renderer (vulkan). Intel - gtk4 is working fine for me on Intel graphics on a laptop from a few years ago. But there have been issues for people who use other graphics drivers. Open Issues --- https://gitlab.gnome.org/GNOME/gtk/-/issues/?label_name%5B%5D=Vulkan%20Renderer Timing -- If we are going to make a switch, we need to do it very soon (this week or by Monday) because we are late in the Ubuntu 24.10 release process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2082017/+subscriptions -- Mailing list: https://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 2073430] Re: Automatic Time Zone not working on 24.04
This has been uploaded to the SRU queue for noble. Therefore, I am unsubscribing ubuntu-sponsors. Feel free to resubscribe if you have anything else that needs to be sponsored. -- 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/2073430 Title: Automatic Time Zone not working on 24.04 Status in OEM Priority Project: Triaged Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Noble: Triaged Bug description: [Impact] I tick "automatic time zone" in the Date & Time settings, it does nothing, and when I return to Date & Time, the option is unselected again. This system is a fresh 24.04 install. See attached video. Here is fix from upstream. https://gitlab.gnome.org/GNOME/gnome-control- center/-/merge_requests/2785 [Test Plan] * Find a machine with 24.04 * Launch `settings` and enable "automatic time zone" in the Date & Time settings, and close `settings` * Launch `settings` again to check "automatic time zone" item. [Where problems could occur] * This patch is picked from upstream, it's low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2073430/+subscriptions -- Mailing list: https://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 2078055] Re: librsvg needs cargo-c but it's not available on i386
** Changed in: librsvg (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2078055 Title: librsvg needs cargo-c but it's not available on i386 Status in librsvg package in Ubuntu: Fix Released Status in rust-cargo-c package in Ubuntu: Triaged Bug description: Starting with the librsvg 2.59 series (2.58.9*), librsvg requires cargo-c to build. cargo-c comes from the Debian source rust-cargo-c. The issue is that librsvg needs to be built on i386, but rust-cargo-c is not currently built for i386. The list of Build-Depends is kinda long. Currently except for librsvg, I believe the only rust-related packages built on i386 are rustc and cargo (which is totally different from cargo-c). https://packages.debian.org/source/unstable/rust-cargo-c Option 1 Stop building librsvg on i386. This might not be practical but it would offer some simplicity. I'm not sure of a perfect way to discover reverse-depends on i386. We may be able to drop gtk4's build dependency on librsvg. It looks like it is optional for cairo, but not sure whether it would be a good idea to attempt to remove it there. Option 2 Build cargo-c as arch:all. Unfortunately, this won't work since cargo-c ships arch-specific binaries unlike many of the rust-* .deb packages. Option 3 Attempt to vendor cargo-c inside the librsvg package. This is what I suspect to be the solution we'll need to go with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2078055/+subscriptions -- Mailing list: https://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 2078055] Re: librsvg needs cargo-c but it's not available on i386
The autopkgtests are also failing: https://autopkgtest.ubuntu.com/packages/rust-cargo-c -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2078055 Title: librsvg needs cargo-c but it's not available on i386 Status in librsvg package in Ubuntu: Triaged Status in rust-cargo-c package in Ubuntu: Triaged Bug description: Starting with the librsvg 2.59 series (2.58.9*), librsvg requires cargo-c to build. cargo-c comes from the Debian source rust-cargo-c. The issue is that librsvg needs to be built on i386, but rust-cargo-c is not currently built for i386. The list of Build-Depends is kinda long. Currently except for librsvg, I believe the only rust-related packages built on i386 are rustc and cargo (which is totally different from cargo-c). https://packages.debian.org/source/unstable/rust-cargo-c Option 1 Stop building librsvg on i386. This might not be practical but it would offer some simplicity. I'm not sure of a perfect way to discover reverse-depends on i386. We may be able to drop gtk4's build dependency on librsvg. It looks like it is optional for cairo, but not sure whether it would be a good idea to attempt to remove it there. Option 2 Build cargo-c as arch:all. Unfortunately, this won't work since cargo-c ships arch-specific binaries unlike many of the rust-* .deb packages. Option 3 Attempt to vendor cargo-c inside the librsvg package. This is what I suspect to be the solution we'll need to go with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2078055/+subscriptions -- Mailing list: https://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 2078055] Re: librsvg needs cargo-c but it's not available on i386
Liu, Matthias sponsored your upload and it fixed the librsvg build. The excuses report has this complaint though: librust-cargo-c-dev/i386 has unsatisfiable dependency I suggest that we build the librust-cargo-c-dev packages on all architectures except for i386 (or alternatively I guess you could convert it to arch: all). librsvg only needs the binary package cargo-c on i386. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2078055 Title: librsvg needs cargo-c but it's not available on i386 Status in librsvg package in Ubuntu: Triaged Status in rust-cargo-c package in Ubuntu: Triaged Bug description: Starting with the librsvg 2.59 series (2.58.9*), librsvg requires cargo-c to build. cargo-c comes from the Debian source rust-cargo-c. The issue is that librsvg needs to be built on i386, but rust-cargo-c is not currently built for i386. The list of Build-Depends is kinda long. Currently except for librsvg, I believe the only rust-related packages built on i386 are rustc and cargo (which is totally different from cargo-c). https://packages.debian.org/source/unstable/rust-cargo-c Option 1 Stop building librsvg on i386. This might not be practical but it would offer some simplicity. I'm not sure of a perfect way to discover reverse-depends on i386. We may be able to drop gtk4's build dependency on librsvg. It looks like it is optional for cairo, but not sure whether it would be a good idea to attempt to remove it there. Option 2 Build cargo-c as arch:all. Unfortunately, this won't work since cargo-c ships arch-specific binaries unlike many of the rust-* .deb packages. Option 3 Attempt to vendor cargo-c inside the librsvg package. This is what I suspect to be the solution we'll need to go with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2078055/+subscriptions -- Mailing list: https://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 2079895] Re: epiphany-browser fails to build on s390x with webkit 2.45
https://launchpad.net/ubuntu/+source/epiphany-browser/47.0-1 ** Changed in: webkit2gtk (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2079895 Title: epiphany-browser fails to build on s390x with webkit 2.45 Status in Webkit: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in webkit2gtk package in Ubuntu: Fix Released Bug description: Once webkit2gtk is updated to >= 2.45.3, epiphany's build tests fail for s390x. I worked around this for Ubuntu 24.10 by removing epiphany-browser on s390x but we'll need to do something else for Ubuntu 24.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2079895/+subscriptions -- Mailing list: https://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 2081093] Re: webkit2gtk autopkgtest failure on armhf
https://launchpad.net/ubuntu/+source/webkit2gtk/2.46.0-2 ** Changed in: webkit2gtk (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2081093 Title: webkit2gtk autopkgtest failure on armhf Status in webkit2gtk package in Ubuntu: Fix Released Status in webkit2gtk package in Debian: Confirmed Bug description: The webkit2gtk autopkgtests for surf and ruby-gnome are failing on armhf. This began happening sometime between 2.45.6 and 2.45.92-1. I was told that this can be easily reproduced in an armhf porterbox. Quoted message follows: xvfb-run --server-args='-screen 0 640x480x16' /usr/lib/*/webkit2gtk-4.1/MiniBrowser https://webkitgtk.org/ The Web process crashes, here is a stack trace: https://paste.debian.net/plainh/9dacd159 The relevant part (I think) is: Core was generated by `/usr/lib/arm-linux-gnueabihf/webkit2gtk-4.1/WebKitWebProcess 21 123 122'. Program terminated with signal SIGABRT, Aborted. #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:47 (gdb) bt [...] #5 WTF::Config::AssertNotFrozenScope::~AssertNotFrozenScope () at ./Source/WTF/wtf/WTFConfig.h:128 #6 WTF::SignalHandlers::finalize () at ./Source/WTF/wtf/threads/Signals.cpp:608 [...] #16 WTF::Config::finalize () at ./Source/WTF/wtf/WTFConfig.cpp:120 #17 0xf419267c in JSC::Config::finalize () at ./Source/JavaScriptCore/runtime/JSCConfig.h:49 #18 JSC::VM::VM () at ./Source/JavaScriptCore/runtime/VM.cpp:436 #19 0xf4192e00 in JSC::VM::create () at ./Source/JavaScriptCore/runtime/VM.cpp:551 #20 0xf5d593c2 in WebCore::commonVMSlow () at ./Source/WebCore/bindings/js/CommonVM.cpp:68 #21 0xf5109776 in WebCore::commonVM () at ./build-soup3/WebCore/PrivateHeaders/WebCore/CommonVM.h:52 #22 WebKit::WebProcess::initializeWebProcess () at ./Source/WebKit/WebProcess/WebProcess.cpp:605 That's RELEASE_ASSERT(!g_wtfConfig.isPermanentlyFrozen); To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2081093/+subscriptions -- Mailing list: https://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 2081093] Re: webkit2gtk autopkgtest failure on armhf
** Changed in: webkit2gtk (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2081093 Title: webkit2gtk autopkgtest failure on armhf Status in webkit2gtk package in Ubuntu: Fix Committed Status in webkit2gtk package in Debian: Confirmed Bug description: The webkit2gtk autopkgtests for surf and ruby-gnome are failing on armhf. This began happening sometime between 2.45.6 and 2.45.92-1. I was told that this can be easily reproduced in an armhf porterbox. Quoted message follows: xvfb-run --server-args='-screen 0 640x480x16' /usr/lib/*/webkit2gtk-4.1/MiniBrowser https://webkitgtk.org/ The Web process crashes, here is a stack trace: https://paste.debian.net/plainh/9dacd159 The relevant part (I think) is: Core was generated by `/usr/lib/arm-linux-gnueabihf/webkit2gtk-4.1/WebKitWebProcess 21 123 122'. Program terminated with signal SIGABRT, Aborted. #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:47 (gdb) bt [...] #5 WTF::Config::AssertNotFrozenScope::~AssertNotFrozenScope () at ./Source/WTF/wtf/WTFConfig.h:128 #6 WTF::SignalHandlers::finalize () at ./Source/WTF/wtf/threads/Signals.cpp:608 [...] #16 WTF::Config::finalize () at ./Source/WTF/wtf/WTFConfig.cpp:120 #17 0xf419267c in JSC::Config::finalize () at ./Source/JavaScriptCore/runtime/JSCConfig.h:49 #18 JSC::VM::VM () at ./Source/JavaScriptCore/runtime/VM.cpp:436 #19 0xf4192e00 in JSC::VM::create () at ./Source/JavaScriptCore/runtime/VM.cpp:551 #20 0xf5d593c2 in WebCore::commonVMSlow () at ./Source/WebCore/bindings/js/CommonVM.cpp:68 #21 0xf5109776 in WebCore::commonVM () at ./build-soup3/WebCore/PrivateHeaders/WebCore/CommonVM.h:52 #22 WebKit::WebProcess::initializeWebProcess () at ./Source/WebKit/WebProcess/WebProcess.cpp:605 That's RELEASE_ASSERT(!g_wtfConfig.isPermanentlyFrozen); To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2081093/+subscriptions -- Mailing list: https://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 2079895] Re: epiphany-browser fails to build on s390x with webkit 2.45
** Changed in: webkit2gtk (Ubuntu) Status: Triaged => Fix Committed ** Changed in: epiphany-browser (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2079895 Title: epiphany-browser fails to build on s390x with webkit 2.45 Status in Webkit: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in webkit2gtk package in Ubuntu: Fix Committed Bug description: Once webkit2gtk is updated to >= 2.45.3, epiphany's build tests fail for s390x. I worked around this for Ubuntu 24.10 by removing epiphany-browser on s390x but we'll need to do something else for Ubuntu 24.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2079895/+subscriptions -- Mailing list: https://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 2081219] [NEW] Add additional mutter fractional scaling gsettings flag
Public bug reported: The GNOME 47 release notes mention that there is a new experimental mutter gsettings feature, xwayland-native-scaling. Should we update display-Allow-fractional-scaling-to-be-enabled.patch to also enable that feature? > GNOME 47 includes an enhanced fractional display scaling feature, which provides better support for legacy X11 apps. This feature is still considered experimental and should only be used for testing. To enable it, you can run the following from the command line: gsettings set org.gnome.mutter experimental-features '["scale-monitor-framebuffer", "xwayland-native-scaling"]' https://release.gnome.org/47 ** Affects: gnome-control-center (Ubuntu) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Triaged ** Tags: oracular ** Summary changed: - Add additional mutter scaling gsettings flag + Add additional mutter fractional scaling gsettings flag -- 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/2081219 Title: Add additional mutter fractional scaling gsettings flag Status in gnome-control-center package in Ubuntu: Triaged Bug description: The GNOME 47 release notes mention that there is a new experimental mutter gsettings feature, xwayland-native-scaling. Should we update display-Allow-fractional-scaling-to-be-enabled.patch to also enable that feature? > GNOME 47 includes an enhanced fractional display scaling feature, which provides better support for legacy X11 apps. This feature is still considered experimental and should only be used for testing. To enable it, you can run the following from the command line: gsettings set org.gnome.mutter experimental-features '["scale-monitor- framebuffer", "xwayland-native-scaling"]' https://release.gnome.org/47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2081219/+subscriptions -- Mailing list: https://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 2078055] Re: librsvg needs cargo-c but it's not available on i386
Liu, The best practices around Rust vendoring are still a work-in-progress. It is an interesting technique to use a second .orig tarball to contain the vendoring. I used a different method when I vendored gnome-snapshot. Because workflows are not standard yet, could you add a debian/README.source file to briefly explain how to update this package? And nitpicking, but could you update remove-nghttp2-sys.patch to include a patch description? I already have your .orig tarballs from the PPA link you shared with me. Therefore I think the easiest is if you would give me a diff against that version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2078055 Title: librsvg needs cargo-c but it's not available on i386 Status in librsvg package in Ubuntu: Triaged Status in rust-cargo-c package in Ubuntu: Triaged Bug description: Starting with the librsvg 2.59 series (2.58.9*), librsvg requires cargo-c to build. cargo-c comes from the Debian source rust-cargo-c. The issue is that librsvg needs to be built on i386, but rust-cargo-c is not currently built for i386. The list of Build-Depends is kinda long. Currently except for librsvg, I believe the only rust-related packages built on i386 are rustc and cargo (which is totally different from cargo-c). https://packages.debian.org/source/unstable/rust-cargo-c Option 1 Stop building librsvg on i386. This might not be practical but it would offer some simplicity. I'm not sure of a perfect way to discover reverse-depends on i386. We may be able to drop gtk4's build dependency on librsvg. It looks like it is optional for cairo, but not sure whether it would be a good idea to attempt to remove it there. Option 2 Build cargo-c as arch:all. Unfortunately, this won't work since cargo-c ships arch-specific binaries unlike many of the rust-* .deb packages. Option 3 Attempt to vendor cargo-c inside the librsvg package. This is what I suspect to be the solution we'll need to go with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2078055/+subscriptions -- Mailing list: https://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 2081093] Re: webkit2gtk autopkgtest failure on armhf
** Bug watch added: Debian Bug tracker #1082148 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082148 ** Also affects: webkit2gtk (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082148 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2081093 Title: webkit2gtk autopkgtest failure on armhf Status in webkit2gtk package in Ubuntu: Triaged Status in webkit2gtk package in Debian: Confirmed Bug description: The webkit2gtk autopkgtests for surf and ruby-gnome are failing on armhf. This began happening sometime between 2.45.6 and 2.45.92-1. I was told that this can be easily reproduced in an armhf porterbox. Quoted message follows: xvfb-run --server-args='-screen 0 640x480x16' /usr/lib/*/webkit2gtk-4.1/MiniBrowser https://webkitgtk.org/ The Web process crashes, here is a stack trace: https://paste.debian.net/plainh/9dacd159 The relevant part (I think) is: Core was generated by `/usr/lib/arm-linux-gnueabihf/webkit2gtk-4.1/WebKitWebProcess 21 123 122'. Program terminated with signal SIGABRT, Aborted. #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:47 (gdb) bt [...] #5 WTF::Config::AssertNotFrozenScope::~AssertNotFrozenScope () at ./Source/WTF/wtf/WTFConfig.h:128 #6 WTF::SignalHandlers::finalize () at ./Source/WTF/wtf/threads/Signals.cpp:608 [...] #16 WTF::Config::finalize () at ./Source/WTF/wtf/WTFConfig.cpp:120 #17 0xf419267c in JSC::Config::finalize () at ./Source/JavaScriptCore/runtime/JSCConfig.h:49 #18 JSC::VM::VM () at ./Source/JavaScriptCore/runtime/VM.cpp:436 #19 0xf4192e00 in JSC::VM::create () at ./Source/JavaScriptCore/runtime/VM.cpp:551 #20 0xf5d593c2 in WebCore::commonVMSlow () at ./Source/WebCore/bindings/js/CommonVM.cpp:68 #21 0xf5109776 in WebCore::commonVM () at ./build-soup3/WebCore/PrivateHeaders/WebCore/CommonVM.h:52 #22 WebKit::WebProcess::initializeWebProcess () at ./Source/WebKit/WebProcess/WebProcess.cpp:605 That's RELEASE_ASSERT(!g_wtfConfig.isPermanentlyFrozen); To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2081093/+subscriptions -- Mailing list: https://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 2081093] [NEW] webkit2gtk autopkgtest failure on armhf
Public bug reported: The webkit2gtk autopkgtests for surf and ruby-gnome are failing on armhf. This began happening sometime between 2.45.6 and 2.45.92-1. I was told that this can be easily reproduced in an armhf porterbox. Quoted message follows: xvfb-run --server-args='-screen 0 640x480x16' /usr/lib/*/webkit2gtk-4.1/MiniBrowser https://webkitgtk.org/ The Web process crashes, here is a stack trace: https://paste.debian.net/plainh/9dacd159 The relevant part (I think) is: Core was generated by `/usr/lib/arm-linux-gnueabihf/webkit2gtk-4.1/WebKitWebProcess 21 123 122'. Program terminated with signal SIGABRT, Aborted. #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:47 (gdb) bt [...] #5 WTF::Config::AssertNotFrozenScope::~AssertNotFrozenScope () at ./Source/WTF/wtf/WTFConfig.h:128 #6 WTF::SignalHandlers::finalize () at ./Source/WTF/wtf/threads/Signals.cpp:608 [...] #16 WTF::Config::finalize () at ./Source/WTF/wtf/WTFConfig.cpp:120 #17 0xf419267c in JSC::Config::finalize () at ./Source/JavaScriptCore/runtime/JSCConfig.h:49 #18 JSC::VM::VM () at ./Source/JavaScriptCore/runtime/VM.cpp:436 #19 0xf4192e00 in JSC::VM::create () at ./Source/JavaScriptCore/runtime/VM.cpp:551 #20 0xf5d593c2 in WebCore::commonVMSlow () at ./Source/WebCore/bindings/js/CommonVM.cpp:68 #21 0xf5109776 in WebCore::commonVM () at ./build-soup3/WebCore/PrivateHeaders/WebCore/CommonVM.h:52 #22 WebKit::WebProcess::initializeWebProcess () at ./Source/WebKit/WebProcess/WebProcess.cpp:605 That's RELEASE_ASSERT(!g_wtfConfig.isPermanentlyFrozen); ** Affects: webkit2gtk (Ubuntu) Importance: High Status: Triaged ** Tags: oracular update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2081093 Title: webkit2gtk autopkgtest failure on armhf Status in webkit2gtk package in Ubuntu: Triaged Bug description: The webkit2gtk autopkgtests for surf and ruby-gnome are failing on armhf. This began happening sometime between 2.45.6 and 2.45.92-1. I was told that this can be easily reproduced in an armhf porterbox. Quoted message follows: xvfb-run --server-args='-screen 0 640x480x16' /usr/lib/*/webkit2gtk-4.1/MiniBrowser https://webkitgtk.org/ The Web process crashes, here is a stack trace: https://paste.debian.net/plainh/9dacd159 The relevant part (I think) is: Core was generated by `/usr/lib/arm-linux-gnueabihf/webkit2gtk-4.1/WebKitWebProcess 21 123 122'. Program terminated with signal SIGABRT, Aborted. #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:47 (gdb) bt [...] #5 WTF::Config::AssertNotFrozenScope::~AssertNotFrozenScope () at ./Source/WTF/wtf/WTFConfig.h:128 #6 WTF::SignalHandlers::finalize () at ./Source/WTF/wtf/threads/Signals.cpp:608 [...] #16 WTF::Config::finalize () at ./Source/WTF/wtf/WTFConfig.cpp:120 #17 0xf419267c in JSC::Config::finalize () at ./Source/JavaScriptCore/runtime/JSCConfig.h:49 #18 JSC::VM::VM () at ./Source/JavaScriptCore/runtime/VM.cpp:436 #19 0xf4192e00 in JSC::VM::create () at ./Source/JavaScriptCore/runtime/VM.cpp:551 #20 0xf5d593c2 in WebCore::commonVMSlow () at ./Source/WebCore/bindings/js/CommonVM.cpp:68 #21 0xf5109776 in WebCore::commonVM () at ./build-soup3/WebCore/PrivateHeaders/WebCore/CommonVM.h:52 #22 WebKit::WebProcess::initializeWebProcess () at ./Source/WebKit/WebProcess/WebProcess.cpp:605 That's RELEASE_ASSERT(!g_wtfConfig.isPermanentlyFrozen); To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2081093/+subscriptions -- Mailing list: https://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 2080968] Re: Aisleriot starts with a green empty window
*** This bug is a duplicate of bug 2080919 *** https://bugs.launchpad.net/bugs/2080919 Yes, I've already built the fix. See the duplicate bug. ** This bug has been marked a duplicate of bug 2080919 [oracular] aisleriot doesn't work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2080968 Title: Aisleriot starts with a green empty window Status in aisleriot package in Ubuntu: New Bug description: After last updates aisleriot starts with a green empty window and a message: can not find solitaire... Removed and reinstalled, same problem. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: aisleriot 1:3.22.34-1 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 17 17:30:31 2024 InstallationDate: Installed on 2024-06-04 (105 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240604) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2080968/+subscriptions -- Mailing list: https://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 2080919] Re: [oracular] aisleriot doesn't work
I fixed this by syncing https://launchpad.net/ubuntu/+source/guile-3.0/3.0.10+really3.0.9-1 and then rebuilding aisleriot. This makes me concerned about other Guile apps that have been built since the end of June though. ** Changed in: aisleriot (Ubuntu) Status: Triaged => Fix Committed ** Also affects: gnucash (Ubuntu) Importance: Undecided Status: New ** Changed in: gnucash (Ubuntu) Status: New => Fix Committed ** Changed in: gnucash (Ubuntu) Importance: Undecided => Critical ** Changed in: gnucash (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2080919 Title: [oracular] aisleriot doesn't work Status in aisleriot package in Ubuntu: Fix Committed Status in gnucash package in Ubuntu: Fix Committed Bug description: aisleriot was rebuilt today for Ubuntu 24.10 and stopped working. However, the Debian build works. My first theory is that this is related to guile-3.0 which was stuck in oracular-proposed for a few months. I have synced a revert version of guile-3.0 from Debian. Terminal output === ;;; WARNING: loading compiled file /usr/lib/x86_64-linux-gnu/aisleriot/guile/3.0/klondike.go failed: ;;; In procedure load-thunk-from-memory: incompatible bytecode version Scheme exception: -- 8< -- Variation: klondike Scheme error: (primitive-load-path Unable to find file ~S in load path (klondike) #f) Scheme tag: misc-error Backtrace: In ice-9/boot-9.scm: 1752:10 5 (with-exception-handler _ _ #:unwind? _ # _) In unknown file: 4 (apply-smob/0 #) In ice-9/boot-9.scm: 1752:10 3 (with-exception-handler _ _ #:unwind? _ # _) In unknown file: 2 (apply-smob/0 #) In ice-9/boot-9.scm: 1685:16 1 (raise-exception _ #:continuable? _) In unknown file: 0 (apply-smob/1 # #<&comp…>) Deck State: No cards in deck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2080919/+subscriptions -- Mailing list: https://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 2080919] [NEW] [oracular] aisleriot doesn't work
Public bug reported: aisleriot was rebuilt today for Ubuntu 24.10 and stopped working. However, the Debian build works. My first theory is that this is related to guile-3.0 which was stuck in oracular-proposed for a few months. I have synced a revert version of guile-3.0 from Debian. Terminal output === ;;; WARNING: loading compiled file /usr/lib/x86_64-linux-gnu/aisleriot/guile/3.0/klondike.go failed: ;;; In procedure load-thunk-from-memory: incompatible bytecode version Scheme exception: -- 8< -- Variation: klondike Scheme error: (primitive-load-path Unable to find file ~S in load path (klondike) #f) Scheme tag: misc-error Backtrace: In ice-9/boot-9.scm: 1752:10 5 (with-exception-handler _ _ #:unwind? _ # _) In unknown file: 4 (apply-smob/0 #) In ice-9/boot-9.scm: 1752:10 3 (with-exception-handler _ _ #:unwind? _ # _) In unknown file: 2 (apply-smob/0 #) In ice-9/boot-9.scm: 1685:16 1 (raise-exception _ #:continuable? _) In unknown file: 0 (apply-smob/1 # #<&comp…>) Deck State: No cards in deck ** Affects: aisleriot (Ubuntu) Importance: High Status: Triaged ** Tags: oracular update-excuse ** Tags added: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2080919 Title: [oracular] aisleriot doesn't work Status in aisleriot package in Ubuntu: Triaged Bug description: aisleriot was rebuilt today for Ubuntu 24.10 and stopped working. However, the Debian build works. My first theory is that this is related to guile-3.0 which was stuck in oracular-proposed for a few months. I have synced a revert version of guile-3.0 from Debian. Terminal output === ;;; WARNING: loading compiled file /usr/lib/x86_64-linux-gnu/aisleriot/guile/3.0/klondike.go failed: ;;; In procedure load-thunk-from-memory: incompatible bytecode version Scheme exception: -- 8< -- Variation: klondike Scheme error: (primitive-load-path Unable to find file ~S in load path (klondike) #f) Scheme tag: misc-error Backtrace: In ice-9/boot-9.scm: 1752:10 5 (with-exception-handler _ _ #:unwind? _ # _) In unknown file: 4 (apply-smob/0 #) In ice-9/boot-9.scm: 1752:10 3 (with-exception-handler _ _ #:unwind? _ # _) In unknown file: 2 (apply-smob/0 #) In ice-9/boot-9.scm: 1685:16 1 (raise-exception _ #:continuable? _) In unknown file: 0 (apply-smob/1 # #<&comp…>) Deck State: No cards in deck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2080919/+subscriptions -- Mailing list: https://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 2011404] Re: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire
** No longer affects: pulseaudio (Ubuntu) ** No longer affects: pipewire (Ubuntu) ** Also affects: ubuntu-gnome-meta (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: ubuntu-gnome-meta (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: ubuntu-gnome-meta (Ubuntu Noble) Status: New => Triaged ** Changed in: ubuntu-gnome-meta (Ubuntu Noble) Importance: Undecided => High ** Changed in: ubuntu-gnome-meta (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2011404 Title: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire Status in ubuntu-gnome-meta package in Ubuntu: Fix Committed Status in ubuntu-gnome-meta source package in Noble: Triaged Bug description: Package vanilla-gnome-desktop 0.97 depends on pulseaudio which conflicts with pipewire-alsa and pipewire-audio which in turn are required for upgrading gnome to version 43. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/2011404/+subscriptions -- Mailing list: https://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 2076869] Re: When changing file or folder names using the Nautilus GUI, Japanese input is not possible.
** Also affects: nautilus (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Noble) Importance: Undecided Status: New ** No longer affects: nautilus (Ubuntu Noble) ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged ** Changed in: mutter (Ubuntu Noble) Status: New => Triaged ** Tags added: fixed-in-mutter-46.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2076869 Title: When changing file or folder names using the Nautilus GUI, Japanese input is not possible. Status in Nautilus: Fix Released Status in mutter package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Triaged Status in mutter source package in Noble: Triaged Bug description: # lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 # apt-cache policy nautilus nautilus: インストールされているバージョン: 1:46.2-0ubuntu0.2 候補: 1:46.2-0ubuntu0.2 バージョンテーブル: *** 1:46.2-0ubuntu0.2 500 500 http://jp.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:46.0-0ubuntu2 500 500 http://jp.archive.ubuntu.com/ubuntu noble/main amd64 Packages # description Japanese input is not possible when changing file and folder names using the nautilus GUI. This problem only occurs in the input form for changing file and folder names that can be displayed using F2 or the right-click menu. Japanese input is possible without any problems in the address bar at the top of the nautilus GUI. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 13 15:11:04 2024 GsettingsChanges: InstallationDate: Installed on 2024-08-04 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=ja_JP.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 44.3-0ubuntu1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2076869/+subscriptions -- Mailing list: https://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 1350705] Re: [Wishlist] Allow file operations like rename/delete in "Open/Save file" dialog
This is fixed in Ubuntu 24.10 where nautilus powers the file chooser for apps that use the xdg-desktop-portal which includes the Firefox and Chromium snaps and apps that use libadwaita. ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Fix Released ** Package changed: ubuntu => xdg-desktop-portal-gnome (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1350705 Title: [Wishlist] Allow file operations like rename/delete in "Open/Save file" dialog Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Bug description: Hi, I believe this is a nautilus-related request. It would be a real time saver if one could rename or delete files/folders from within the open/save file dialogs. Some typical situations where this is very useful: * you want to change the name of a folder in which you want to save the file. Possibly because have just created this folder from the very same dialog and made a typo in the name; * you want to cleanup the destination folder from obsolete files before saving; * you want to keep a backup of an existing file in the same folder, by renaming it before saving the new file. Windows offers this feature for as far as I can remember. It is not to try replicate behaviour, but it is a really nice feature, which does not impact the GUI look: * 2 extra entries in the contextual menu * 2-3 key bindings (F2, Delete, and Shift Delete) which already exist in plain Nautilus. Thank you. Bests, Renaud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/1350705/+subscriptions -- Mailing list: https://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 1585818] Re: The selection is not shown when renaming in nautilus.
I believe this was fixed long ago. ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1585818 Title: The selection is not shown when renaming in nautilus. Status in Ubuntu: Fix Released Bug description: When you rename something in nautilus and select part of the text, the selection is not shown. Steps to reproduce: * Right click on a file or a folder and click rename. (at this time the name should be automatically selected) * If not automatically selected, manually select part of the name. Expected behavior: * selected text color should change from black to white (or from white to a brighter white if the dark theme is enabled). * selected text background color should change from white to blue (or other color) (or from dark-grey to to blue (or other color) if the dark theme is enabled). Actual behavior: * the text color is changing in the expected way. * the background color is not changing (or is set to a transparent color). In the attached screenshot I've selected only "ThisTextIsSelected" and NOT selected "ThisIsNotSelected". In the screenshot is shown the behavior with both the light and dark Adwaita theme. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 26 00:00:46 2016 GsettingsChanges: b'org.gnome.nautilus.preferences' b'sort-directories-first' b'true' b'org.gnome.nautilus.window-state' b'sidebar-width' b'228' b'org.gnome.nautilus.window-state' b'geometry' b"'967x757+556+239'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'RabbitVCS::age_column', 'RabbitVCS::author_column', 'RabbitVCS::revision_column', 'RabbitVCS::status_column']" InstallationDate: Installed on 2016-04-22 (32 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1585818/+subscriptions -- Mailing list: https://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 1980334] Re: Support Quectel's modem(EM120/160) firmware update, fwupd
** Changed in: gnome-firmware (Ubuntu) Status: New => Fix Released ** Changed in: gnome-software (Ubuntu) Status: New => Fix Released ** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1980334 Title: Support Quectel's modem(EM120/160) firmware update, fwupd Status in OEM Priority Project: Fix Released Status in fwupd package in Ubuntu: Fix Released Status in gnome-firmware package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in libxmlb package in Ubuntu: Fix Released Status in fwupd source package in Focal: Fix Released Status in gnome-firmware source package in Focal: Fix Released Status in gnome-software source package in Focal: Fix Released Status in libxmlb source package in Focal: Fix Released Status in fwupd source package in Kinetic: Fix Released Status in gnome-firmware source package in Kinetic: Won't Fix Status in gnome-software source package in Kinetic: Won't Fix Status in libxmlb source package in Kinetic: Fix Released Bug description: [Impact] * EM120/160 firmware update's fw can't get updated. [Test Plan] * Use a machine with EM120/160 and test fw upgrade or reinstall. For the rest of the SRU document, please check lp:1982103 Note: the SRU of fwupd is following the exception in https://wiki.ubuntu.com/firmware-updates. We also need to upgrade libxmlb due to fwupd is its only major consumer, and without that, we could not have the correct fwupd function on this one. -- The current fwupd packages in focal have to be rebuild with the latest 1.18.6 modem manager[1] in updates channel. In the modem-manager plugin of fwupd, there are several version check macros to determine the version of modem-manager, for instance: https://git.launchpad.net/ubuntu/+source/fwupd/tree/plugins/modem- manager/fu-mm-device.c?h=ubuntu/focal-updates#n22 #if MM_CHECK_VERSION(1, 17, 2) #include "fu-firehose-updater.h" #endif If the version is equal to or newer than 1.17.2, fwupd will have different behaviors. And the previous version in Focal is 1.16.6 so we have to rebuild or do a version bump to make sure it compile with the new modem manager. [1] https://launchpad.net/ubuntu/+source/modemmanager/1.18.6-1~ubuntu20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1980334/+subscriptions -- Mailing list: https://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 1984840] Re: bump libxml version for gnome-software and gnome-firmware
** Changed in: gnome-firmware (Ubuntu) Status: In Progress => Fix Released ** Changed in: gnome-software (Ubuntu) Status: In Progress => Fix Released ** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1984840 Title: bump libxml version for gnome-software and gnome-firmware Status in OEM Priority Project: Fix Released Status in gnome-firmware package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-firmware source package in Focal: Fix Released Status in gnome-software source package in Focal: Fix Released Bug description: We'll need to upgrade foacl/libxmlb to version 0.3.6 because of lp:1980334, which will bump the runtime from libxmlb1 to libxmlb2. Given so, we'll modify the control file to build-depend on the new focal/libxmlb so we'll be sure that it will have right dependency after focal/libxmlb is upgraded. [Impact] * need to upgrade libxmlb so that EM120/160 firmware update cound be upgraded. (lp:1980334) * Since after upgrade, libxmlb1 will become libxmlb2. So we need to bump version in the control file to make sure it build against the new libxmlb. [Test Plan] * install the upgraded fwupd/libxmlb and gnome-software and gnome-firmware. Find a machine that have pending firmware upgrade. 1. check if the device list is the same before/after upgrade 2. make sure those two app still could upgrade the firmware after upgrade. * other test on fwupd will be covered by their bugs. [Where problems could occur] * Given libxmlb is only used to do fw upgrade, if it pass the test above, I can't see other think could happen. [Other Info] * It will be better of the gnome-software / snap-store snap could be rebuilt after this is release (if they are build on focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984840/+subscriptions -- Mailing list: https://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 2073430] Re: Automatic Time Zone not working on 24.04
** Also affects: gnome-control-center (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-control-center (Ubuntu Noble) Status: New => Triaged -- 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/2073430 Title: Automatic Time Zone not working on 24.04 Status in OEM Priority Project: Triaged Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Noble: Triaged Bug description: [Impact] I tick "automatic time zone" in the Date & Time settings, it does nothing, and when I return to Date & Time, the option is unselected again. This system is a fresh 24.04 install. See attached video. Here is fix from upstream. https://gitlab.gnome.org/GNOME/gnome-control- center/-/merge_requests/2785 [Test Plan] * Find a machine with 24.04 * Launch `settings` and enable "automatic time zone" in the Date & Time settings, and close `settings` * Launch `settings` again to check "automatic time zone" item. [Where problems could occur] * This patch is picked from upstream, it's low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2073430/+subscriptions -- Mailing list: https://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 2061687] Re: Snapshot doesn't work until camera is unplugged and plugged back in or pipewire or wireplumber is restarted
** No longer affects: wireplumber (Ubuntu) ** Also affects: pipewire (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-snapshot (Ubuntu Noble) Importance: Undecided Status: New ** No longer affects: gnome-snapshot (Ubuntu Noble) ** Changed in: pipewire (Ubuntu) Status: Triaged => Fix Committed ** Changed in: pipewire (Ubuntu Noble) Status: New => Triaged ** Changed in: pipewire (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2061687 Title: Snapshot doesn't work until camera is unplugged and plugged back in or pipewire or wireplumber is restarted Status in OEM Priority Project: New Status in PipeWire: Fix Released Status in gnome-snapshot package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Fix Committed Status in pipewire source package in Noble: Triaged Bug description: Ubuntu 24.04 LTS Beta On multiple computers, it appears like Snapshot doesn't work until I either: - unplug the external USB webcam and plug it back in - use the Fn key to disable the internal webcam and re-enable it - or use a more complex method for internal webcams that don't have a hardware button to disable and enable them I have reported this issue upstream Workaround -- In a terminal run systemctl --user restart wireplumber.service To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2061687/+subscriptions -- Mailing list: https://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 2077461] Re: [draft] FFe: Install sysprof app in default Ubuntu install
** Tags removed: block-proposed -- 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/2077461 Title: [draft] FFe: Install sysprof app in default Ubuntu install Status in ubuntu-meta package in Ubuntu: Triaged Bug description: This is filed as a draft to provide early notice to the Ubuntu Release Team as requested. It is not yet ready for action since the libdex MIR has not been approved yet. LP: #2066262 Impact == The Ubuntu Desktop team wishes to install the sysprof app in the default Ubuntu Desktop install for 24.10. This is part of a distro-wide Performance Engineering effort discussed in various places such as https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame-pointers-by-default For clarification, this change is for both the default and full installation options. This will be done by adding Recommends: sysprof in the ubuntu-desktop-minimal package (and seed). No changes are needed in any other packages. Installing the sysprof app by default has no impact on any other packages. Why this wasn't done earlier The Ubuntu Security team was unable to finish their security review for sysprof's dependency, libdex, before Feature Freeze Testing === I don't believe any other testing is needed for this change. However, there is a manual test to verify that the app works: https://wiki.ubuntu.com/DesktopTeam/TestPlans/Sysprof To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2077461/+subscriptions -- Mailing list: https://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 2080275] Re: ubuntu desktop in gnome control center displays nothing
Try installing ubuntu-desktop-minimal -- 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/2080275 Title: ubuntu desktop in gnome control center displays nothing Status in gnome-control-center package in Ubuntu: New Bug description: Hi, After migration from 22.04.1 LTS to 24.04.1 LTS, I discovered that the option "ubuntu deskop" in parameter do not display anything except a sentence (I translate it from french to english) : "no ubuntu parameter found" . Please report a bug to Launchpad. I also tried to run from the command line, hereunder is the result: $ /usr/bin/gnome-control-center 20:44:05.8694 cc-ubuntu-panel[20052]: WARNING: No Ding is installed here. Please fix your installation. 20:44:05.8694 cc-ubuntu-panel[20052]: WARNING: No Ubuntu Dock is installed here. Panel disabled. Please fix your installation. 20:44:08.9010 Gtk[20052]: WARNING: Finalizing AdwPreferencesPage 0x57a65c1ebf30, but it still has children left: - GtkCenterBox 0x57a65c1f7b40 Do I need to install "Ding" and "Ubuntu Dock" , if yes, it means it was not installed during upgrade. Thanks and congrats to all developpers team! Hereunder are additionals information: $ lsb_release -rd No LSB modules are available. Description:Ubuntu 24.04.1 LTS Release:24.04 $ apt-cache policy gnome-control-center gnome-control-center: Installé : 1:46.0.1-1ubuntu7 Candidat : 1:46.0.1-1ubuntu7 Table de version : *** 1:46.0.1-1ubuntu7 500 500 http://fr.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status $ dpkg -l | grep gnome-control-center ii gnome-control-center 1:46.0.1-1ubuntu7 amd64utilities to configure the GNOME desktop ii gnome-control-center-data 1:46.0.1-1ubuntu7 all configuration applets for GNOME - data files ii gnome-control-center-faces 1:46.0.1-1ubuntu7 all utilities to configure the GNOME desktop - faces images ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46.0.1-1ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-44.44-generic 6.8.12 Uname: Linux 6.8.0-44-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 10 20:44:51 2024 InstallationDate: Installed on 2021-08-27 (1110 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to noble on 2024-09-10 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2080275/+subscriptions -- Mailing list: https://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 2073042] Re: Outdated relative to gtk4 (4.10 < 4.14)
Our Stable Release Update guidelines won't allow us to update gtkmm4.0 in Ubuntu 24.04 LTS from 4.10 to 4.14 https://wiki.ubuntu.com/StableReleaseUpdates Ubuntu 24.10 will be released next month with gtk4 4.16 and gtkmm4.0 4.16. Therefore, I am closing this bug since it is fixed in our development release. ** Changed in: gtkmm4.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtkmm4.0 in Ubuntu. https://bugs.launchpad.net/bugs/2073042 Title: Outdated relative to gtk4 (4.10 < 4.14) Status in gtkmm4.0 package in Ubuntu: Fix Released Bug description: Why is Ubuntu 24.04 shipping a version of gtkmm (4.10) that is outdated by more than a year compared to its version of gtk4 (4.14)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkmm4.0/+bug/2073042/+subscriptions -- Mailing list: https://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 2080073] Re: 47rc: unable to resize mattermost, discord windows
Yes, that commit fixes my issue. ** Changed in: mutter (Ubuntu) Status: New => Fix Committed ** Tags added: fixed-in-mutter-47.0 fixed-upstream -- 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/2080073 Title: 47rc: unable to resize mattermost, discord windows Status in mutter package in Ubuntu: Fix Committed Bug description: After installing gnome-shell & mutter 47~rc from Salsa and logging in, I am unable to resize or maximize my Mattermost and Discord windows. These are Snap apps. I am able to resize my Element and Telegram windows. Those are also Snap apps. This bug only affects the Wayland session. I do not experience this bug with the Ubuntu on Xorg session. The issue goes away if I revert to oracular's 47~beta packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2080073/+subscriptions -- Mailing list: https://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 2080073] [NEW] 47rc: unable to resize mattermost, discord windows
Public bug reported: After installing gnome-shell & mutter 47~rc from Salsa and logging in, I am unable to resize or maximize my Mattermost and Discord windows. These are Snap apps. I am able to resize my Element and Telegram windows. Those are also Snap apps. This bug only affects the Wayland session. I do not experience this bug with the Ubuntu on Xorg session. The issue goes away if I revert to oracular's 47~beta packages. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: oracular -- 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/2080073 Title: 47rc: unable to resize mattermost, discord windows Status in mutter package in Ubuntu: New Bug description: After installing gnome-shell & mutter 47~rc from Salsa and logging in, I am unable to resize or maximize my Mattermost and Discord windows. These are Snap apps. I am able to resize my Element and Telegram windows. Those are also Snap apps. This bug only affects the Wayland session. I do not experience this bug with the Ubuntu on Xorg session. The issue goes away if I revert to oracular's 47~beta packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2080073/+subscriptions -- Mailing list: https://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 2077108] Re: gjs 1.81 autopkgtest failure
** Changed in: gjs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2077108 Title: gjs 1.81 autopkgtest failure Status in gjs: Fix Released Status in gjs package in Ubuntu: Fix Released Bug description: The autopkgtests for gjs 1.81 are failing. I have reported this issue upstream. There were some buildsystem changes in the 1.81 series that may have contributed to this. To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/2077108/+subscriptions -- Mailing list: https://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 2079477] Re: rust-gstreamer-video autopkgtest failure on s390x
I have restored my workaround patch to ignore this issue since I have higher priorities this week. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2079477 Title: rust-gstreamer-video autopkgtest failure on s390x Status in gst-plugins-base: New Status in gst-plugins-base1.0 package in Ubuntu: Triaged Status in rust-gstreamer-video package in Ubuntu: Triaged Bug description: I'm working with upstream on this issue. https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/7412 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-base/+bug/2079477/+subscriptions -- Mailing list: https://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 2077461] Re: [draft] FFe: Install sysprof app in default Ubuntu install
I set block-proposed because this is only a Recommends so I want sysprof/libdex/libpanel to be promoted to main first. -- 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/2077461 Title: [draft] FFe: Install sysprof app in default Ubuntu install Status in ubuntu-meta package in Ubuntu: Triaged Bug description: This is filed as a draft to provide early notice to the Ubuntu Release Team as requested. It is not yet ready for action since the libdex MIR has not been approved yet. LP: #2066262 Impact == The Ubuntu Desktop team wishes to install the sysprof app in the default Ubuntu Desktop install for 24.10. This is part of a distro-wide Performance Engineering effort discussed in various places such as https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame-pointers-by-default For clarification, this change is for both the default and full installation options. This will be done by adding Recommends: sysprof in the ubuntu-desktop-minimal package (and seed). No changes are needed in any other packages. Installing the sysprof app by default has no impact on any other packages. Why this wasn't done earlier The Ubuntu Security team was unable to finish their security review for sysprof's dependency, libdex, before Feature Freeze Testing === I don't believe any other testing is needed for this change. However, there is a manual test to verify that the app works: https://wiki.ubuntu.com/DesktopTeam/TestPlans/Sysprof To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2077461/+subscriptions -- Mailing list: https://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 2077461] Re: [draft] FFe: Install sysprof app in default Ubuntu install
** Tags added: block-proposed -- 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/2077461 Title: [draft] FFe: Install sysprof app in default Ubuntu install Status in ubuntu-meta package in Ubuntu: Triaged Bug description: This is filed as a draft to provide early notice to the Ubuntu Release Team as requested. It is not yet ready for action since the libdex MIR has not been approved yet. LP: #2066262 Impact == The Ubuntu Desktop team wishes to install the sysprof app in the default Ubuntu Desktop install for 24.10. This is part of a distro-wide Performance Engineering effort discussed in various places such as https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame-pointers-by-default For clarification, this change is for both the default and full installation options. This will be done by adding Recommends: sysprof in the ubuntu-desktop-minimal package (and seed). No changes are needed in any other packages. Installing the sysprof app by default has no impact on any other packages. Why this wasn't done earlier The Ubuntu Security team was unable to finish their security review for sysprof's dependency, libdex, before Feature Freeze Testing === I don't believe any other testing is needed for this change. However, there is a manual test to verify that the app works: https://wiki.ubuntu.com/DesktopTeam/TestPlans/Sysprof To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2077461/+subscriptions -- Mailing list: https://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 2079895] [NEW] epiphany-browser fails to build on s390x with webkit 2.45
Public bug reported: Once webkit2gtk is updated to >= 2.45.3, epiphany's build tests fail for s390x. I worked around this for Ubuntu 24.10 by removing epiphany-browser on s390x but we'll need to do something else for Ubuntu 24.04 LTS. ** Affects: webkit Importance: Unknown Status: Unknown ** Affects: epiphany-browser (Ubuntu) Importance: High Status: Triaged ** Affects: webkit2gtk (Ubuntu) Importance: High Status: Triaged ** Tags: ftbfs noble oracular update-excuse ** Also affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Bug watch added: bugs.webkit.org/ #279220 https://bugs.webkit.org/show_bug.cgi?id=279220 ** Also affects: webkit via https://bugs.webkit.org/show_bug.cgi?id=279220 Importance: Unknown Status: Unknown ** Changed in: webkit2gtk (Ubuntu) Status: New => Triaged ** Changed in: webkit2gtk (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2079895 Title: epiphany-browser fails to build on s390x with webkit 2.45 Status in Webkit: Unknown Status in epiphany-browser package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: Triaged Bug description: Once webkit2gtk is updated to >= 2.45.3, epiphany's build tests fail for s390x. I worked around this for Ubuntu 24.10 by removing epiphany-browser on s390x but we'll need to do something else for Ubuntu 24.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2079895/+subscriptions -- Mailing list: https://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 2076994] Re: Update and re-enable keyboard layout option patches
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Committed -- 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/2076994 Title: Update and re-enable keyboard layout option patches Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: Ubuntu's gnome-control-center packaging has 2 patches to enable additional configuration for the Alternate Characters Key & Compose Key options in the Keyboard panel. These subpages were rewritten for the 47 release cycle. To ensure we got the gnome-control-center 47 Beta (and other things) into Ubuntu 24.10 before Feature Freeze, I temporarily disabled those patches. The patches should be updated and re-enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2076994/+subscriptions -- Mailing list: https://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 2079477] Re: rust-gstreamer-video autopkgtest failure on s390x
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #3754 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3754 ** Also affects: gst-plugins-base via https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3754 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2079477 Title: rust-gstreamer-video autopkgtest failure on s390x Status in gst-plugins-base: Unknown Status in gst-plugins-base1.0 package in Ubuntu: Triaged Status in rust-gstreamer-video package in Ubuntu: Triaged Bug description: I'm working with upstream on this issue. https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/7412 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-base/+bug/2079477/+subscriptions -- Mailing list: https://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 2078971] Re: Update cairo to 1.18.2
** Changed in: cairo (Ubuntu) Status: In Progress => Fix Committed ** Changed in: pycairo (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/2078971 Title: Update cairo to 1.18.2 Status in cairo package in Ubuntu: Fix Committed Status in pycairo package in Ubuntu: Fix Committed Bug description: pycairo's autopkgtest is sensitive to the upstream version of cairo so it needs to be rebuilt for this update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/2078971/+subscriptions -- Mailing list: https://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 2079477] [NEW] rust-gstreamer-video autopkgtest failure on s390x
Public bug reported: I'm working with upstream on this issue. https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/7412 ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: High Assignee: Jeremy Bícha (jbicha) Status: Triaged ** Affects: rust-gstreamer-video (Ubuntu) Importance: High Assignee: Jeremy Bícha (jbicha) Status: Triaged ** Tags: oracular update-excuse ** Also affects: rust-gstreamer-video (Ubuntu) Importance: Undecided Status: New ** Changed in: rust-gstreamer-video (Ubuntu) Assignee: (unassigned) => Jeremy Bícha (jbicha) ** Changed in: rust-gstreamer-video (Ubuntu) Importance: Undecided => High ** Changed in: rust-gstreamer-video (Ubuntu) Status: New => Triaged ** Description changed: I'm working with upstream on this issue. + + https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/7412 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2079477 Title: rust-gstreamer-video autopkgtest failure on s390x Status in gst-plugins-base1.0 package in Ubuntu: Triaged Status in rust-gstreamer-video package in Ubuntu: Triaged Bug description: I'm working with upstream on this issue. https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/7412 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/2079477/+subscriptions -- Mailing list: https://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 2078971] Re: Update cairo to 1.18.2
** Also affects: pycairo (Ubuntu) Importance: Undecided Status: New ** Description changed: - . + pycairo's autopkgtest is sensitive to the upstream version of cairo so + it needs to be rebuilt for this update. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/2078971 Title: Update cairo to 1.18.2 Status in cairo package in Ubuntu: In Progress Status in pycairo package in Ubuntu: New Bug description: pycairo's autopkgtest is sensitive to the upstream version of cairo so it needs to be rebuilt for this update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/2078971/+subscriptions -- Mailing list: https://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 2077965] Re: mesa 24.2 broke gst-plugins-base1.0 build tests
I'm closing this bug since gst-plugins-base1.0 now builds with the version of mesa in oracular-proposed ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => Fix Released ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2077965 Title: mesa 24.2 broke gst-plugins-base1.0 build tests Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa package in Debian: New Bug description: gst-plugins-base1.0 fails to build on amd64 (the only architecture where build test failures are currently not ignored) https://launchpad.net/ubuntu/+source/gst-plugins-base1.0/1.24.7-1 The build completes successfully in a PPA where oracular-proposed is not enabled. I believe this failure is because of mesa 24.0.2 which is currently in oracular-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/2077965/+subscriptions -- Mailing list: https://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 2064698] Re: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get [### Promise created here: ### getProperty@file:///usr/share/gnome-shell/extens
** Changed in: gnome-shell-extension-appindicator (Ubuntu Oracular) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2064698 Title: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get [### Promise created here: ### getProperty@file:///usr/share/gnome-shell/extensions/ubuntu- appindicat...@ubuntu.com/dbusProxy.js:89:33] Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Committed Status in gnome-shell-extension-appindicator source package in Noble: In Progress Status in gnome-shell-extension-appindicator source package in Oracular: Fix Committed Bug description: [ Impact ] Chromium and Electron apps implement the KStatusNotifierItem spec without exposing some DBus properties that the spec describes. The app-indicator feature can work without those properties, but gnome-shell-extension-appindicator will log a big error message to the system journal every time the app refreshes the indicator. Because failing to access those properties is not fatal, we can avoid dumping an error to the system journal. Instead, we'll only print a debug message, not visible by default unless enabled with G_MESSAGES_DEBUG="Ubuntu-AppIndicators" in the shell's environment. The full error message can be seen in comment #3 [ Test Plan ] Reproducing the issue involves using an Electron-based application that uses AppIndicators. I'm going to use Mattermost as an example of one. * Install the mattermost-desktop snap * Log in * Click the 3-dots button on the top-left * Navigate to File > Settings * Tick `Show icon in the notification area` * Restart the app * In a terminal window start printing journal logs with `journalctl -f` * Get someone to send a message to any channel that you participate in. * Verify that the error (comment #3) was not logged to the journal [ Where problems could occur ] The AppIndicator extension is an important feature of Ubuntu Desktop. If misconfigured, the extension may crash the desktop. The patch only touches printing logs, so should not affect the well behavior of the extension. Problems can be detected by using applications that expose app- indicators. [ Original Description ] Every session I see those errors in the attached log file. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 3 08:54:53 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (41 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2064698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
