[Desktop-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
This bug was fixed in the package ppa-purge - 0.2.8+bzr63-0ubuntu1.23.10.1 --- ppa-purge (0.2.8+bzr63-0ubuntu1.23.10.1) mantic; urgency=medium * Add support for deb822 source format. (LP: #2036761) -- Ghadi Elie Rahme Tue, 19 Mar 2024 14:58:45 + ** Changed in: ppa-purge (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Invalid Status in ppa-purge source package in Mantic: Fix Released Status in software-properties source package in Mantic: Invalid Status in ppa-purge source package in Noble: Fix Released Status in software-properties source package in Noble: Invalid Bug description: Thank you @jbicha for the original bug report! [ Impact ] Currently ppa-purge fails to purge packages on distribution using the deb822 source format. Currently mantic and noble make use of this format and are affected by this issue. When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the custom PPA since it cannot disable deb822 sources and leads to apt still querying the ppa when running: $ apt update In older versions of ubuntu, PPAs used the ".list" format which could be disabled by simply commenting out the "deb" line with a "#". This was the method that ppa-purge used to disable PPAs. This new patch allows ppa-purge to detect and disable deb822 source files by adding an "Enabled: no" field in each component section of the deb822 file. It also removes any line that starts with "Enabled:" to make sure the resulting file is clean. [ Test Plan ] The changes were tested on both mantic and noble in a lxc container using the oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) as the test PPA. The following steps were recorded in a noble lxc container. - First make sure that mesa-utils is installed in your environment: $ sudo apt update && sudo apt install mesa-utils - Add the oibaf PPA to your system using the following command: $ sudo add-apt-repository ppa:oibaf/graphics-drivers - Make sure that the mesa-utils packages were upgraded after adding the PPA: $ sudo apt update && sudo apt upgrade $ dpkg - l | grep mesa - output should be similar to the following: ii libegl-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 9.0.0-2 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd649.0.0-2 amd64Miscellaneous Mesa utilities -- native applications ii mesa-vulkan-drivers:amd64 24.1~git2402280600.41722c~oibaf~n amd64Mesa Vulkan graphics drivers - Install and run ppa-purge: $ sudo apt install ppa-purge $ sudo ppa-purge ppa:oibaf/graphics-drivers - ppa-purge will report at the end that none of the oibaf packages need to be downgraded/removed: libglapi-mesa is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglapi-mesa set to manually installed. libglx-mesa0 is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglx-mesa0 set to manually installed. mesa-vulkan-drivers is already the newest version (24.1~git2402280600.41722c~oibaf~n). mesa-vulkan-drivers set to manually installed. Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble
[Desktop-packages] [Bug 2064093] Re: if-up.d files do not have effect on ubuntu 24.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ifupdown (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2064093 Title: if-up.d files do not have effect on ubuntu 24.04 LTS Status in ifupdown package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Some time ago I wrote a detailed answer to fix an error for lowering MTU size for a cisco-compatible VPN (here:https://unix.stackexchange.com/questions/768757/unable-to-ssh- into-remote-machine-but-able-to-ping-vpnc/768758#768758) After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to lower the MTU size. In particular, if I run the following command from the terminal sudo ifconfig your_tunnel_name mtu 1370 up it seems to lower the MTU size. However, the script under /etc/network/if-up.d is not automatically triggered. Does something change with the newer Ubuntu version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2064093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064093] Re: if-up.d files do not have effect on ubuntu 24.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2064093 Title: if-up.d files do not have effect on ubuntu 24.04 LTS Status in ifupdown package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Some time ago I wrote a detailed answer to fix an error for lowering MTU size for a cisco-compatible VPN (here:https://unix.stackexchange.com/questions/768757/unable-to-ssh- into-remote-machine-but-able-to-ping-vpnc/768758#768758) After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to lower the MTU size. In particular, if I run the following command from the terminal sudo ifconfig your_tunnel_name mtu 1370 up it seems to lower the MTU size. However, the script under /etc/network/if-up.d is not automatically triggered. Does something change with the newer Ubuntu version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2064093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064559] [NEW] Screen clicks not working when app page maximised
You have been subscribed to a public bug: Recently completed a fresh installation of Ubuntu 24.4 When apps are maximised to use full screen, clicks on buttons do not work and instead go through to whatever is behind the app. Restoring the app to a window rather than full screen clicks work normally. This happens for a number of apps but not all. I am using 2 monitors (join) and using monitor 2 as my primary display. Happy to provide more info, but not sure what will be helpful. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- Screen clicks not working when app page maximised https://bugs.launchpad.net/bugs/2064559 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019137] Re: gnome-software should (?) be separated from the packagekit
This bug was fixed in the package gnome-software - 46.1-1 --- gnome-software (46.1-1) unstable; urgency=high * New upstream release -- Jeremy Bícha Mon, 29 Apr 2024 17:05:57 -0400 ** Changed in: gnome-software (Ubuntu) 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/2019137 Title: gnome-software should (?) be separated from the packagekit Status in gnome-software package in Ubuntu: Fix Released Bug description: Given that the Snap Store is currently the default in Ubuntu instead of GNOME Software, the only reason GNOME Software (along with the Snap Store) can be installed is to support Flatpak applications. In the current instance, if you want to add flatpak support, GNOME Software is installed with both the apt packagekit add-on and the flatpak plugin, which is duplication of work (Software Updater already works on updates, and Snap Store works on showing deb apps). And since the future app store explicitly refuses [1], [2] to support flatpak applications, users who need this package format will be forced to put GNOME Software with everything I pointed out above. Therefore, it would be very nice if the developers removed the packagekit add-on from the "gnome-software part" and made it a "plug- in for gnome-software". I, unfortunately, have no such experience with packaging deb packages at the moment, and it turns out that it will obviously be necessary to work out both the code part (which, as far as I can see, won't be very difficult [3]), as well as the part where we will have to figure out where and how to insert the plugin as mandatory (for example, when the user completely gives up on snap packages) and as optional (because the Snap Store already stands). Also, let me know if this needs to be sent to upstream (Debian) instead of here. --- 1. https://github.com/ubuntu-flutter-community/software/issues/126 2. https://github.com/ubuntu-flutter-community/software/issues/30 3. https://build.opensuse.org/request/show/1031279 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056767] Re: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split
This bug was fixed in the package gnome-software - 46.1-1 --- gnome-software (46.1-1) unstable; urgency=high * New upstream release -- Jeremy Bícha Mon, 29 Apr 2024 17:05:57 -0400 ** Changed in: gnome-software (Ubuntu) Status: New => 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/2056767 Title: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split Status in gnome-software package in Ubuntu: Fix Released Bug description: Impact -- I request permission to sync the gnome-software packaging from Debian. The biggest change is splitting gnome-software's .deb support into a separate package, gnome-software-plugin-deb, to match the existing -snap and -flatpak packages. This will allow users and flavors to specifically opt into the parts of the GNOME Software experience they want. For instance, someone may want to use only the Flatpak part because they use the Snap Store to manage .debs and Snaps. Or maybe they want a different combination. This has been requested by multiple users on Ubuntu Discourse and at least one Launchpad bug and one Debian bug. fwupd plugin I am dropping the fwupd plugin (now in a separate package too) to Suggests so upgrades to Ubuntu 24.04 LTS will likely get it uninstalled and new installs won't have it either unless a user explicitly installs it later. Ubuntu Desktop includes the firmware-updater snap. Several Ubuntu desktop flavors also include it. For people who don't want snaps, there is also the gnome-firmware app packaged as a .deb. Because Ubuntu already has update-manager to handle apt update notifications, I am also dropping the autostart file to reduce background RAM use. A few Ubuntu desktop flavors do not provide any firmware updater app at all. Ubuntu Budgie developers thought a firmware updater app was too technical for inclusion in the default Ubuntu 24.04 LTS install. autostart - I have also dropped the autostart file since the fwupd plugin is no longer included by default and Ubuntu already has ways to notify users about available apt updates (update-manager and unattended upgrades) and snaps already automatically update. Potential Problems --- gnome-software has an explicit Recommend: gnome-software-plugin-deb so that people upgrading to Ubuntu 24.04 LTS will keep the deb support installed. That recommends will be dropped for Ubuntu 26.04 LTS because it won't be needed then. (There is a Depends on the virtual packages that enable installing apps.) Full Changelog Entries -- gnome-software (46.0-4) unstable; urgency=medium * Fix typo in gnome-software-plugin-deb package description * Add lintian overrides for desktop-command-not-in-package -- Jeremy Bícha Fri, 29 Mar 2024 16:45:30 -0400 gnome-software (46.0-3) unstable; urgency=medium * Update Homepage * Release to Unstable -- Jeremy Bícha Thu, 28 Mar 2024 13:23:28 -0400 gnome-software (46.0-2) experimental; urgency=medium * Split deb support into separate gnome-software-plugin-deb package (Closes: #1066030) (LP: #2019137, #2056767) * Have each plugin provide a virtual gnome-software-plugin package * Suggest all the gnome-software plugins * Recommend gnome-software-plugin-deb for upgrades * Split firmware update support into separate fwupd plugin & recommend it except on Ubuntu which provides a separate firmware-updater app Intentionally, do not have this provides the virtual gnome-software-plugin since it doesn't allow browsing apps. * Drop patch that hides upstreams Software Sources dialog (Closes: #1060803) * Drop Depends: software-properties-gtk * Stop recommending gnome-software-plugin-snap on Ubuntu -- Jeremy Bícha Wed, 27 Mar 2024 18:33:03 -0400 Build Logs -- https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15898505/+listing-archive-extra Desktop Flavors Affected GNOME Software is currently included in the default install for only Ubuntu Cinnamon. See Joshua's comment below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2056767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064510] [NEW] File manager hang up
You have been subscribed to a public bug: I was doing a large backup of files from an SSD drive to a external USB drive using rsync running in a terminal window. I then opened up a new file manager window and then (i think) I clicked on the same SSD drive (that was being copied) to get its properties (I wanted to see how much disk space was used up). I then got a dialog popup on the screen (I have a screenshot of this attached) saying the following "There was an error while getting the sharing information" Failed to execute child process "net" (No such file or directory) At this point all the file manager windows were unresponsive. They could not be closed, but I think they could be moved and they could come to foreground etc. In the end I had to crash power off my laptop. I took me 4 hours to chkdsk\recover file systems on both my external USB hard drives and the SSD as well (done using Win10 because they were all NTFS drives). Also as an aside (this is probably another bug)... every so often a file manager window will freeze on its righthand side. You can click on various drives on the lefthand side but it never updates the righthand side to show the file\folders on that clicked drive. I end up closing the filemanager window and opening up a new one. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- File manager hang up https://bugs.launchpad.net/bugs/2064510 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064364] Re: gnome-control-center: WireGuard peer info closes on focus loss.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/2064364 Title: gnome-control-center: WireGuard peer info closes on focus loss. Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Just installed a fresh Ubuntu 24.04 LTS In Settings (gnome-control-center) -> Network -> VPN '+'-> WireGuard -> WireGuard -> Peers '+'. When adding a peer for the Wireguard connection, if the popout or window loses focus (for example because we need do copy-paste from another window), the entire "peer" dialog closes and we lose the previous info. It's not reasonable to setup a WireGuard connection manually because typing several long keys by hand is too error prone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058687] Re: [SRU] libreoffice 7.6.6 for mantic
This bug was fixed in the package libreoffice - 4:7.6.6-0ubuntu0.23.10.1
---
libreoffice (4:7.6.6-0ubuntu0.23.10.1) mantic; urgency=medium
* New upstream release (LP: #2058687)
* debian/rules:
- also suggest libreoffice-{hyphenation,spellcheck}-tr in -l10n-tr
and libreoffice-{hyphenation,spellcheck}-fr in -l10n-fr (as for fi)
-- Rico Tzschichholz Thu, 21 Mar 2024 20:20:29
+0100
** Changed in: libreoffice (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2058687
Title:
[SRU] libreoffice 7.6.6 for mantic
Status in libreoffice package in Ubuntu:
Fix Released
Status in libreoffice source package in Mantic:
Fix Released
Bug description:
[Impact]
* LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line:
https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release
* Version 7.6.5 is currently released in mantic. For a list of fixed bugs
compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6
(that's a total of 39 bugs):
https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs
7.6.6 RC3 is identical to the 7.6.6 release
* Given the nature of the project, the complexity of the codebase and
the high level of quality assurance upstream, it is preferable to SRU
a minor release rather than cherry-pick selected bug fixes.
[Testing]
* Upstream testing. Bugs fixed upstream typically include
unit/regression tests, and the release itself is extensively exercised
(both in an automated manner and manually).
* A recent set of upstream's automated jenkins testing can be found here:
https://ci.libreoffice.org/job/gerrit_76/1898/
* More information about the upstream QA testing can be found here:
* Automated tests
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
* Automated UI tests
https://wiki.documentfoundation.org/Development/UITests
* Regression tests
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
* Feature tests
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
* Launchpad testing. The libreoffice packages include autopkgtests that were
run and verified as passing.
Tested build can be found at
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15869507/+listing-archive-extra
* [amd64]
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240323_001335_50e00@/log.gz
* [arm64]
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240324_215819_0b108@/log.gz
* [armhf]
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240322_202324_f628d@/log.gz
* [ppc64el]
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240322_145135_f3904@/log.gz
* [riscv64] not available
* [s390x]
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240322_140411_ca6c5@/log.gz
* General smoke testing of all the applications in the office suite were
carried out by going through the manual testplan as documented by:
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice
[Regression Potential]
* A minor release with a total of 39 bug fixes always carries the
potential for introducing regressions, even though it is a bugfix-only
release, meaning that no new features were added, and no existing
features were removed.
* A combination of autopkgtests and careful smoke testing as
described above should provide reasonable confidence that no
regressions sneaked in.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2058687/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
** Merge proposal linked: https://code.launchpad.net/~juergh/ubuntu-seeds/+git/ubuntu/+merge/465215 -- 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/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064093] [NEW] if-up.d files does not have effect on ubuntu 24.04 LTS
You have been subscribed to a public bug: Some time ago I wrote a detailed answer to fix an error for lowering MTU size for a cisco-compatible VPN (here:https://unix.stackexchange.com/questions/768757/unable-to-ssh- into-remote-machine-but-able-to-ping-vpnc/768758#768758) After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to lower the MTU size. In particular, if I run the following command from the terminal sudo ifconfig your_tunnel_name mtu 1370 up it seems to lower the MTU size. However, the script under /etc/network/if-up.d is not automatically triggered. Does something change with the newer Ubuntu version? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: 24.04 -- if-up.d files does not have effect on ubuntu 24.04 LTS https://bugs.launchpad.net/bugs/2064093 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2052824] Re: ubuntu-drivers list warning messages
*** This bug is a duplicate of bug 2037004 *** https://bugs.launchpad.net/bugs/2037004 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2052824 Title: ubuntu-drivers list warning messages Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Running "ubuntu-drivers list" as root from commandline give the following output, under Ubuntu 23.10: udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. nvidia-driver-535-server, (kernel modules provided by linux-modules-nvidia-535-server-generic-hwe-22.04) nvidia-driver-535-open, (kernel modules provided by linux-modules-nvidia-535-open-generic-hwe-22.04) nvidia-driver-545, (kernel modules provided by linux-modules-nvidia-545-generic-hwe-22.04) nvidia-driver-535, (kernel modules provided by linux-modules-nvidia-535-generic-hwe-22.04) nvidia-driver-525-open, (kernel modules provided by linux-modules-nvidia-525-open-generic-hwe-22.04) nvidia-driver-545-open, (kernel modules provided by linux-modules-nvidia-545-open-generic-hwe-22.04) nvidia-driver-525, (kernel modules provided by linux-modules-nvidia-525-generic-hwe-22.04) nvidia-driver-525-server, (kernel modules provided by linux-modules-nvidia-525-server-generic-hwe-22.04) nvidia-driver-535-server-open, (kernel modules provided by linux-modules-nvidia-535-server-open-generic-hwe-22.04) Additional Info: e# lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 Background: After updating my drivers the /dev/dri directory was not present, so was looking around and tried: apt update ubuntu-drivers install ubuntu-drivers install --gpgpu ubuntu-drivers list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2052824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054907] Re: GNOME Control Center (Settings app) crashes every now and then, especially when switching sections.
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/2054907 Title: GNOME Control Center (Settings app) crashes every now and then, especially when switching sections. Status in gnome-control-center package in Ubuntu: Expired Bug description: On Ubuntu 23.10 (Mantic), GNOME Control Center (the Settings app) keeps crashing every now and then when I am using it; often happening when I switch sections. One of the sections which takes the blame is the Privacy page, which occasionally has a tendency to lock up the Settings app and crash it; at times erroneously showing Thunderbolt settings, even though Thunderbolt does not exist on my system. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Feb 25 08:09:18 2024 InstallationDate: Installed on 2024-02-18 (7 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2054907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054217] Re: Settings app in Ubuntu Mantic keeps crashing
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/2054217 Title: Settings app in Ubuntu Mantic keeps crashing Status in gnome-control-center package in Ubuntu: Expired Bug description: The GNOME settings app in Ubuntu Mantic (23.10, GNOME 45) occasionally keeps crashing when I move around its various sections. At times it even happens consecutively. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Feb 18 08:05:00 2024 InstallationDate: Installed on 2024-02-16 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2054217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2055158] Re: nautilus random crash
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/2055158 Title: nautilus random crash Status in nautilus package in Ubuntu: Expired Bug description: Nautilus crashes at least once a day, often while searching, but also while changing the display from list to icon, or otherwise. Submitting the crash file fails, see my: https://askubuntu.com/questions/1504496/ubuntu-bug-crash-does-not- open-browser-form ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 27 13:13:05 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'captions' b"['size', 'none', 'none']" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'extra-large'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1248, 1048)' InstallationDate: Installed on 2023-06-06 (266 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-10-14 (136 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2055158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063520] [NEW] amdgpu causes GTK4/Libadwaita, etc. rendering text with missing characters
You have been subscribed to a public bug: UPDATE: It seems to be related with `amdgpu` driver, which is the default driver in Ubuntu. After disabling `amdgpu`, problem vanishes. However, software rendering is not a perfect solution. IT SEEMS THAT `amdgpu` in later updates of Ubuntu 23.10 & 24.04 are BUGGY. As no driver alternatives are available right now for Ubuntu 24.04, now I am having a hard time. [UPDATE] Updating to Ubuntu 24.04 DO NOT SOLVE THIS PROBLEM Before updating to Ubuntu 24.04, I do sudo apt upgrade to update my packages on Ubuntu 23.10 first. [UPDATE] Updating to Ubuntu 24.04 DO NOT SOLVE THIS PROBLEM Then I found that every program in GTK4/Libadwaita renders with missing characters, even gdm (I cannot take a screenshot of gdm, but the problems are the same). I toggled "Antialising" in GNOME tweaks, and some characters return TEMPORARILY. Then I opened a new GTK4/Libadwaita program, problems re- occur. Besides, problems exist in Xorg/Wayland, as Ubuntu 23.10 uses Xwayland. Problems exist in Plasma. Texts in desktop icons are missing, too. AND I FOUND THAT the "Graphics" Section (the driver name) has been changed to "AMD Readon 680M" after the update (I think it is something like "AMD Rembrandt" before sudo apt upgrade). (I toggled in GNOME tweaks to make the window display graphics info; if I re-open it, fonts will be missing again) If I hover on the place where text should display, some texts may display but icons would not. This problem affects my life qualify, thus I need to make clear where it is the problem. GTK4? Libadwaita? Graphics? Ubuntu? Because problems does not occur on GTK3 based apps, thus I can submit this issue in Firefox. I tried to open GNOME Calendar and use journalctl to capture logs Apr 26 09:02:00 amber-XiaoXinPro-14-ARP8 gnome-calendar[4462]: gcal_range_union: assertion 'a != NULL' failed Apr 26 09:02:00 amber-XiaoXinPro-14-ARP8 gnome-calendar[4462]: gcal_range_contains_datetime: assertion 'self' failed Apr 26 09:02:00 amber-XiaoXinPro-14-ARP8 gnome-calendar[4462]: Unable to bind the same property on the same instance Apr 26 09:02:00 amber-XiaoXinPro-14-ARP8 dbus-daemon[898]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.103' (uid=1000 pid=4462 comm="/usr/bin/gnome-calendar --gapplication-service" label="unconfined") Apr 26 09:02:00 amber-XiaoXinPro-14-ARP8 systemd[1]: Starting geoclue.service - Location Lookup Service... Apr 26 09:02:00 amber-XiaoXinPro-14-ARP8 dbus-daemon[898]: [system] Successfully activated service 'org.freedesktop.GeoClue2' Apr 26 09:02:00 amber-XiaoXinPro-14-ARP8 systemd[1]: Started geoclue.service - Location Lookup Service. Apr 26 09:02:00 amber-XiaoXinPro-14-ARP8 gnome-shell[3604]: Can't update stage views actor [:0x5e35cde82a20] is on because it needs an allocation. Apr 26 09:02:00 amber-XiaoXinPro-14-ARP8 gnome-shell[3604]: Can't update stage views actor [:0x5e35cb8dff80] is on because it needs an allocation. Apr 26 09:02:03 amber-XiaoXinPro-14-ARP8 gnome-calendar[4462]: Finalizing GcalMonthView 0x612b02571230, but it still has children left: - GcalMonthPopover 0x612b02a78630 If I opened gnome-calendar in terminal, terminal has no new errors messages appending. Disabling amdgpu makes the problem to vanish, however software rendering is not an acceptable option for a Ubuntu Desktop user. Thanks in advance. ** Affects: gtk4 (Ubuntu) Importance: Undecided Status: New -- amdgpu causes GTK4/Libadwaita, etc. rendering text with missing characters https://bugs.launchpad.net/bugs/2063520 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064034] [NEW] Boot takes a long time due to "plymouth-quit-wait"
You have been subscribed to a public bug: Fresh install of Ubuntu 24.04. Boot takes too long. Everything seems corrent, plymount's loading screen disapears after a while (few seconds) and black screen happends. This is the time when GDM3 should shows up. I have to wait few minutes and then after changing TTY by pressing i.e. CTRL+ALT+F2 and then immediately switch back by CTRL+ALT+F1 GDM3 shows up. I figured out, that "plymouth-quit-wait.service" took too much (4+ minutes). See more in attachments. ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New -- Boot takes a long time due to "plymouth-quit-wait" https://bugs.launchpad.net/bugs/2064034 You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064009] [NEW] audio device malfunctioning and crash
You have been subscribed to a public bug: Hi my audio device (Philips screen with sound) crashed after using it few hours. Its working badly (kind of distorsion) anytime, was working fine with 22.10 but works badly with debian 12 (same config). Thx I use a Philips screen with HDMI for image and sound Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-31-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790S CPU @ 3.20GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: Dell Inc. Product Name: OptiPlex 9020 System Version: 00 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:kub1580 F pipewire /dev/snd/controlC1: kub1582 F wireplumber /dev/snd/controlC0: kub1582 F wireplumber /dev/snd/controlC2: kub1582 F wireplumber CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 28 14:35:52 2024 InstallationDate: Installed on 2024-04-25 (3 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) MachineType: Dell Inc. OptiPlex 9020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2019 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0KC9NP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 16 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd05/30/2019:br65.25:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn0KC9NP:rvrA00:cvnDellInc.:ct16:cvr:sku05A4: dmi.product.name: OptiPlex 9020 dmi.product.sku: 05A4 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- audio device malfunctioning and crash https://bugs.launchpad.net/bugs/2064009 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064017] [NEW] Xserver Display flickers when mouse pointer is inside narrow horizontal range band (kernel related)
You have been subscribed to a public bug: My machine information is following : HP EliteBook 840 G3 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] xrandr -q active mode on laptop display : 1368x768 60.01 Tried using 6.8.8-060808 kernel (instead of the lubuntu 24.04 default shipped kernel 6.8.0-31), same issue. Rolling back the kernel to 6.7 fixed the problem,maybe there were some video driver changes from kernel 6.7 to 6.8 ? While using the 6.8 kernel I did some experiments: disabled picom in startup , no effect Tried changing display resolution, just moves vertical position of band. (at the above resolution 1368x768 vertical mouse pointer flicker range is around 640 ( measured running watch -t -n 0.0001 xdotool getmouselocation from a bash terminal) Tried moving refresh rate slightly around 60 Hz by creating a new modeline using cvt tool and adding new mode with xrandr, no effect. tried connecting external display on laptop VGA port and duplicating screen and the issue seems to disappear. tried capturing a video of the desktop using ffmpeg with x11grab, but it does not show the issue. I attached a short video of the laptop display flicker I recorded using my phone ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: LXQt Date: Sun Apr 28 09:44:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079] InstallationDate: Installed on 2024-04-25 (3 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID :3825 USB OPTICAL MOUSE Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 004: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP HD Camera Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP EliteBook 840 G3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=c323b5e4-1a45-4ce4-9f8d-c4f7f9c60388 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.release: 1.42 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.42 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.78 dmi.chassis.asset.tag: 5CG7042V5J dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.120 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.42:bd08/19/2019:br1.42:efr133.120:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.78:cvnHP:ct10:cvr:skuZ2A57UT#ABA: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: Z2A57UT#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption noble ubuntu -- Xserver Display flickers when mouse pointer is inside narrow horizontal range band (kernel related) https://bugs.launchpad.net/bugs/2064017 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062980] Re: nautilus progress bar on ubuntu dock icon does not update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2062980 Title: nautilus progress bar on ubuntu dock icon does not update Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: while copying files from another disk to /home folder, the progress bar on the nautilus icon in ubuntu dock does not update. however, the progress icon within nautilus does update. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 22:46:11 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1301, 915)' ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2062980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062082] Re: 24.04 Wayland vs Nautilus performance problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/2062082 Title: 24.04 Wayland vs Nautilus performance problem Status in nautilus package in Ubuntu: Confirmed Bug description: Apologies if I have misfiled this bug - this is a report of an issue affecting Wayland in Ubuntu 24.04 beta. Using 24.04 beta logging in with Wayland. Nautilus has very significant performance issues. Doesn't happen when logging in with Xorg instead of Wayland. Opening Nautilus windows - including normal windows navigation, and the file download location dialogue in things like Chrome - extremely slow. Takes approx. 10 seconds to process user double clicking to open folder. Attempting to drag folder across screen usually doesn't work, or takes a very long time. Not very skilled at debugging, but programmes like Gimp, which has its own built-in folder explorer for choosing a location to save an image, do not have this problem. Ubuntu 24.04 with X does not have this problem. No performance issues have been noticed with folder navigation, stat'ing files etc. over the command line. It is only nautilus and Wayland that give me this issue, so I suspect it is not an issue with my SSD. The following output was observed when starting nautilus over the command line: /home/me/ $ nautilus . ** Message: 23:43:50.560: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen After approx. 10 seconds, the folder opened on screen. I double clicked on a sub directory, and it took about 9 seconds to open. I have attempted to show that this is not an issue with my SSD here: /home/me/ $ date; cd workspace/; touch foo.txt; ls foo*; cd ../; date; Wed Apr 17 11:58:16 PM BST 2024 foo.txt Wed Apr 17 11:58:16 PM BST 2024 As you can see, no unusual slowdown was observed. Obtaining the following setting for my bug report, I note that the 'Settings' GUI utility is among the areas affect by my very significant system slowdown. I have copied some details about my system including its graphics card in case that helps. # System Details Report --- ## Report details - **Date generated:** 2024-04-17 23:59:54 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX B550-F GAMING - **Memory:** 32.0 GiB - **Processor:** AMD Ryzen™ 7 5800X × 16 - **Graphics:**zink Vulkan 1.3(NVIDIA GeForce GTX 1050 Ti (NVIDIA_PROPRIETARY)) - **Disk Capacity:** 2.0 TB ## Software Information: - **Firmware Version:**2006 - **OS Name:** Ubuntu Noble Numbat (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..09.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 545.29.06 Thu Nov 16 01:59:08 UTC 2023 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 23:44:47 2024 DistUpgraded: 2024-04-11 13:09:51,904 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] InstallationDate: Installed on 2024-04-11 (6 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: ASUS System Product Name ProcEnviron:
[Desktop-packages] [Bug 2063831] Re: Clicking on bottom half of applications switches to background application
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2063831 Title: Clicking on bottom half of applications switches to background application Status in mutter package in Ubuntu: Confirmed Bug description: Basicly having more that 1 GUI application running in full screen and clicking bottom half of the currently opened GUI application will make the other application come to the foreground Eg: Google Chrome & Eclipse IDE are both in fullscreen, - Clicking On Eclipse IDE bottom half of the app window will get chrome to display infront of Eclipse, Eg2: Terminal and DBeaver are both in fullscreen, - Clicking On DBeaver bottom half of the app window will get Termial to display infront of Eclipse, ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:07:41 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-P GT2 [Iris Xe Graphics] [1462:1331] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Ti Mobile] [1462:135d] InstallationDate: Installed on 2024-04-25 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Micro-Star International Co., Ltd. Katana GF66 12UD ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=7c59c657-2812-4b59-8441-927f4302e8fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1584IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-1584 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1584IMS.10C:bd05/05/2022:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF6612UD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1584:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku1584.1: dmi.product.family: GF dmi.product.name: Katana GF66 12UD dmi.product.sku: 1584.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Noble: Won't Fix Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060693] Re: No welcome/login sound on Ubuntu desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libcanberra (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/2060693 Title: No welcome/login sound on Ubuntu desktop Status in libcanberra package in Ubuntu: Confirmed Bug description: Under the Ubuntu desktop for Raspberry Pi, for several recent releases, the startup sound from the Yaru sound theme has failed to play both at the initial setup (from oem-config, where it used to play just before language selection), and at the greeter. This worked in Jammy (22.04), but on at least mantic (23.10) and the forthcoming noble (24.04) (and possibly earlier), this has failed. It's not due to a crash in canberra-gtk-play (used to play the sound). The only hint that something has failed appears in the oem-config.log: Failed to play sound: Not available Unfortunately there's nothing else in the log that hints at why canberra-gtk-play is failing. There are several similar bug report, but I doubt they are related given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a very different sound stack and predates the preinstalled desktop images). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063831] [NEW] Clicking on bottom half of applications switches to background application
You have been subscribed to a public bug: Basicly having more that 1 GUI application running in full screen and clicking bottom half of the currently opened GUI application will make the other application come to the foreground Eg: Google Chrome & Eclipse IDE are both in fullscreen, - Clicking On Eclipse IDE bottom half of the app window will get chrome to display infront of Eclipse, Eg2: Terminal and DBeaver are both in fullscreen, - Clicking On DBeaver bottom half of the app window will get Termial to display infront of Eclipse, ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:07:41 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-P GT2 [Iris Xe Graphics] [1462:1331] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Ti Mobile] [1462:135d] InstallationDate: Installed on 2024-04-25 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Micro-Star International Co., Ltd. Katana GF66 12UD ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=7c59c657-2812-4b59-8441-927f4302e8fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1584IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-1584 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1584IMS.10C:bd05/05/2022:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF6612UD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1584:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku1584.1: dmi.product.family: GF dmi.product.name: Katana GF66 12UD dmi.product.sku: 1584.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ubuntu -- Clicking on bottom half of applications switches to background application https://bugs.launchpad.net/bugs/2063831 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061708] Re: Yubikey stopped working after noble upgrade
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnupg2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/2061708
Title:
Yubikey stopped working after noble upgrade
Status in Arch Linux on Launchpad:
Fix Released
Status in gnupg2 package in Ubuntu:
Confirmed
Status in pcsc-lite package in Ubuntu:
Invalid
Bug description:
In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
If I run this as root it works:
$ sudo gpg --card-status
Reader ...: 1050:0407:X:0
Application ID ...: D27600012401000609082616
Application type .: OpenPGP
Version ..: 2.1
Manufacturer .: Yubico
Serial number :
Name of cardholder: [not set]
Language prefs ...: [not set]
Salutation ...:
URL of public key : [not set]
Login data ...: [not set]
Signature PIN : not forced
Key attributes ...: rsa4096 rsa4096 rsa2048
Max. PIN lengths .: 127 127 127
PIN retry counter : 10 0 10
Signature counter : 1172
UIF setting ..: Sign=off Decrypt=off Auth=off
Signature key :
created :
Encryption key:
created :
Authentication key: [none]
General key info..: [none]
If I manually run pcscd.service then it stops working both as root and
a user.
$ sudo pkill -9 scdaemon
$ sudo systemctl start pcscd.service
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
$ sudo gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
It might be worth mentioning I'm accessing the machine over SSH, so I
also did experiment with a polkit rule like this:
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_card" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_pcsc" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading
polkit.service in case this was a polkit issue, but this didn't do
anything.
Versions in noble:
pcscd: 2.0.3-1build1
libpcslite1: 2.0.3-1build1
gnupg: 2.4.4-2ubuntu17
scdaemon: 2.4.4-2ubuntu17
To manage notifications about this bug go to:
https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990630] Re: [SRU] tracker-extract-3 crashed with signal 31 in __GI_epoll_create1()
This bug was fixed in the package tracker-miners - 3.3.3-0ubuntu0.20.04.3 --- tracker-miners (3.3.3-0ubuntu0.20.04.3) jammy; urgency=medium * Allow epoll_create1 call in seccomp whitelist (LP: #1990630) - d/p/seccomp-allow-epoll-create1.patch -- Talha Can Havadar Wed, 03 Apr 2024 13:27:56 +0200 ** Changed in: tracker-miners (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1990630 Title: [SRU] tracker-extract-3 crashed with signal 31 in __GI_epoll_create1() Status in Tracker: Fix Released Status in tracker-miners package in Ubuntu: Fix Released Status in tracker-miners source package in Jammy: Fix Released Bug description: [Impact] Bug is impacting jammy desktop instances that uses tracker-miners package by default. It keeps restarting the service and this makes the CPU busy. [Where problems could occur] epoll_create1() is the preferred call over epoll_create(), and is used in GLib 2.74 and later due to glib!2868 (merged) so the error described below occurs pretty commonly [Test Case] * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed) * Update tracker-extract to the version in -proposed: sudo apt install -t jammy-proposed tracker-extract * Check journalctl logs to see if `Disallowed syscall "epoll_create1" caught in sandbox` message disappeared and the service is not restarting due to this error. [Regression Potential] The patch doesn't modifies an existing behavior it only allows an additional syscall, so it shouldn't introduce regression Upstream MR: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/419 --- Impact -- As seen by the number of duplicates, this is the most common tracker crash seen in Ubuntu 22.10. According to seeded-in-ubuntu, tracker-miners is included by default only in the Ubuntu Desktop flavor error after upgrade from 22.04 to 22.10 https://errors.ubuntu.com/problem/4f257ae91411857c6bb9266de343d7f189a68474 ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: tracker-extract 3.4.0-1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Sep 23 09:31:40 2022 ExecutablePath: /usr/libexec/tracker-extract-3 InstallationDate: Installed on 2022-05-11 (134 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcCmdline: /usr/libexec/tracker-extract-3 Signal: 31 SourcePackage: tracker-miners StacktraceTop: __GI_epoll_create1 () at ../sysdeps/unix/syscall-template.S:120 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: tracker-extract-3 crashed with signal 31 in __GI_epoll_create1() UpgradeStatus: Upgraded to kinetic on 2022-09-23 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/1990630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-remote-desktop (Ubuntu)
Status: New => Confirmed
--
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/206
Title:
gnome-remote-desktop.service: Failed to determine user credentials: No
such process
Status in gnome-remote-desktop package in Ubuntu:
Confirmed
Bug description:
On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop.
The desktop does not show up though gdm3 is running.
I see the following error messages which might indicate a dependency
issue:
pr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service -
GNOME Remote Desktop...
Apr 24 12:29:35 unmatched (p-daemon)[1752]: gnome-remote-desktop.service:
Failed to determine user credentials: No such process
Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main
process exited, code=exited, status=217/USER
Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed
with result 'exit-code'.
Apr 24 12:29:35 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled
restart job, restart counter is at 1.
Apr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service -
GNOME Remote Desktop...
Apr 24 12:29:35 unmatched (p-daemon)[1753]: gnome-remote-desktop.service:
Failed to determine user credentials: No such process
Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main
process exited, code=exited, status=217/USER
Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed
with result 'exit-code'.
Apr 24 12:29:35 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled
restart job, restart counter is at 2.
Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service -
GNOME Remote Desktop...
Apr 24 12:29:36 unmatched (p-daemon)[1754]: gnome-remote-desktop.service:
Failed to determine user credentials: No such process
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main
process exited, code=exited, status=217/USER
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed
with result 'exit-code'.
Apr 24 12:29:36 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled
restart job, restart counter is at 3.
Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service -
GNOME Remote Desktop...
Apr 24 12:29:36 unmatched (p-daemon)[1755]: gnome-remote-desktop.service:
Failed to determine user credentials: No such process
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main
process exited, code=exited, status=217/USER
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed
with result 'exit-code'.
Apr 24 12:29:36 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled
restart job, restart counter is at 4.
Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service -
GNOME Remote Desktop...
Apr 24 12:29:36 unmatched (p-daemon)[1756]: gnome-remote-desktop.service:
Failed to determine user credentials: No such process
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main
process exited, code=exited, status=217/USER
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed
with result 'exit-code'.
Apr 24 12:29:36 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled
restart job, restart counter is at 5.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Start
request repeated too quickly.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed
with result 'exit-code'.
Apr 24 12:29:36 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-remote-desktop 46.1-1
ProcVersionSignature: Ubuntu 6.8.0-31.31.1-generic 6.8.1
Uname: Linux 6.8.0-31-generic riscv64
ApportVersion: 2.28.1-0ubuntu2
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Apr 24 12:34:26 2024
InstallationDate: Installed on 2024-04-24 (0 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release riscv64
(20240423)
SourcePackage: gnome-remote-desktop
UpgradeStatus: No
[Desktop-packages] [Bug 1972914] Re: frequent 15-sec guest freeze with ubuntu 22.04 host and guest
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-qxl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1972914 Title: frequent 15-sec guest freeze with ubuntu 22.04 host and guest Status in xserver-xorg-video-qxl package in Ubuntu: Confirmed Bug description: I'm running a new installation of Ubuntu 22.04 Desktop on a Thinkpad T450s (core i5-5200, 2 cores / 4 vCPUs, 12 GB memory). Using the virt- manager GUI, I performed what I believe is a simple, plain-vanilla installation of an Ubuntu 22.04 guest running under qemu/kvm with 2 vCPUs and 4 GB memory. I'm seeing very frequent, 15-second freezes of the guest. When it happens, the guest is completely unresponsive. After about 15 seconds, it works normally again, until the next freeze. The duration of the freeze appears to be the same every time. The guest isn't doing much - just open the calculator app and click number buttons. The freeze doesn't happen if I don't interact with the guest (just leave the system monitor running in the guest, so I can see that it's not frozen). I observe the freeze when I have 2 of the 4 vCPUs dedicated to the guest. I do NOT observe it when I have only one vCPU dedicated to the guest. Both the host and guest are using only a small fraction of the memory available to them. When the problem happens, the host indicates that CPU usage is very low across all vCPUs. The host appears to be operating normally when the guest is frozen. I see the following pair of lines in the guest syslog every time the freeze occurs (and only when the freeze occurs): May 10 13:48:40 qemu-jammy kernel: [ 144.259799] qxl :00:01.0: object_init failed for (8298496, 0x0001) May 10 13:48:40 qemu-jammy kernel: [ 144.259819] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO I don't see anything in the host syslog that correlates with the freeze. If I choose "Virtio" in the Video drop-down in the virt-manager GUI, with "3D acceleration" UNchecked, the guest works fine, and the freeze never happens. Unfortunately, that loses fractional scaling, which is important to me. If I check "3D acceleration," the guest won't boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1972914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063476] Re: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/2063476 Title: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 Status in gnome-control-center package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Cannot run gnome-control-center due to missing symbol lookup. Please see the output of the console: ``` ubuntu@kria:~$ gnome-control-center -h gnome-control-center: symbol lookup error: /lib/aarch64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.8 ProcVersionSignature: Ubuntu 5.15.0-1027.31-xilinx-zynqmp 5.15.136 Uname: Linux 5.15.0-1027-xilinx-zynqmp aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk1p1) Date: Thu Apr 25 16:57:26 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063476] Re: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: webkit2gtk (Ubuntu) Status: New => Confirmed -- 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/2063476 Title: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 Status in gnome-control-center package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Cannot run gnome-control-center due to missing symbol lookup. Please see the output of the console: ``` ubuntu@kria:~$ gnome-control-center -h gnome-control-center: symbol lookup error: /lib/aarch64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.8 ProcVersionSignature: Ubuntu 5.15.0-1027.31-xilinx-zynqmp 5.15.136 Uname: Linux 5.15.0-1027-xilinx-zynqmp aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk1p1) Date: Thu Apr 25 16:57:26 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043597] Re: Kernal-sound: [950QED, Realtek ALC298, Speaker, Internal] Pulseaudio fails to detect card
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2043597 Title: Kernal-sound: [950QED, Realtek ALC298, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Confirmed Bug description: The input and output audio does not work for my system and I cannot find a kernel to install to fix this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:jacques1494 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 10:47:30 2023 InstallationDate: Installed on 2022-11-22 (358 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Title: [950QED, Realtek ALC298, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P07AKK.620.220407.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP950QED-KB1US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLB182A1Z-C01-G002-S0001+10.0.22000 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP07AKK.620.220407.SH:bd04/07/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950QED:pvrP07AKK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP950QED-KB1US:rvrSGLB182A1Z-C01-G002-S0001+10.0.22000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PAKK: dmi.product.family: Galaxy Book2 Pro 360 dmi.product.name: 950QED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PAKK dmi.product.version: P07AKK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063387] Re: No tray icon
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rhythmbox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/2063387 Title: No tray icon Status in rhythmbox package in Ubuntu: Confirmed Bug description: When I minimise Rhythmbox it disappears. There's no tray icon and I can see no way to bring it back. It continues playing music but I cannot control it any way. I have to kill the process. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rhythmbox 3.4.4-5ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Thu Apr 25 03:46:54 2024 SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2063387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063304] Re: chromium 124.0.6367.60 fails to draw its window
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qrtr (Ubuntu) Status: New => Confirmed -- 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/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: protection-domain-mapper (Ubuntu) Status: New => Confirmed -- 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/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059756] Re: [SRU] adsys 0.14.1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: golang-1.22 (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 Status in adsys package in Ubuntu: Fix Released Status in golang-1.22 package in Ubuntu: Fix Released Status in adsys source package in Jammy: Confirmed Status in golang-1.22 source package in Jammy: Confirmed Bug description: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise- desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) *
[Desktop-packages] [Bug 2059756] Re: [SRU] adsys 0.14.1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: adsys (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 Status in adsys package in Ubuntu: Fix Released Status in golang-1.22 package in Ubuntu: Fix Released Status in adsys source package in Jammy: Confirmed Status in golang-1.22 source package in Jammy: Confirmed Bug description: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise- desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) * Note:
[Desktop-packages] [Bug 2063341] [NEW] Ubuntu crashesh after KVM swicth back/wake up/suspend
You have been subscribed to a public bug: I've been using Ubuntu for almost 2 years and it's been working fine. I use a KVM switch (built in Benq monitor) all the time. Since last month Ubuntu randomly crashes when I switch back to it. Or it could be wake up/suspend, I can't see when it exactly happens, it's just logging screen after crash. I am running: openVPN, firefox (dozen tabs), chrome (ms teams), slack, postman, 3x Intellij IDEA, VS Code System logs don't show anything meaningful to me or Google and I don't know how to get a clue as to what's going on. I suspect a new version of MS Teams that was introduced a few weeks ago. Please help me I cannot reproduce the crash or find anything on the web about it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:59:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (601 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- Ubuntu crashesh after KVM swicth back/wake up/suspend https://bugs.launchpad.net/bugs/2063341 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063336] [NEW] All Chromium based applications fail to render (dual NVIDIA GPU system)
You have been subscribed to a public bug: I am noticing two - Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly showing transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug noble snap wayland-session -- All Chromium based applications fail to render (dual NVIDIA GPU system) https://bugs.launchpad.net/bugs/2063336 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053289] Re: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2053289 Title: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I tried to record sound with my internal Mic. Nothing is working. I use arecord. ``` bagus:~$ arecord test.wav arecord: main:834: audio open error: Operation not supported bagus:~$ arecord -d 10 -f cd -t wav -D copy foobar.wav ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM copy arecord: main:834: audio open error: No such file or directory bagus:~$ arecord -l List of CAPTURE Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 bagus:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 bagus:~$ apt-cache policy alsa-base alsa-base: Installed: (none) Candidate: 1.0.25+dfsg-0ubuntu7 Version table: 1.0.25+dfsg-0ubuntu7 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2053289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063153] [NEW] Incorrect display Graphics Card in System -> system details
You have been subscribed to a public bug: NVIDIA GeForce RTX 3050 Ti Mobile should be displayed here ** Affects: switcheroo-control (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- Incorrect display Graphics Card in System -> system details https://bugs.launchpad.net/bugs/2063153 You received this bug notification because you are a member of Desktop Packages, which is subscribed to switcheroo-control in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062967] Re: ubuntu-drivers no longer offers nvidia 550 drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2062967 Title: ubuntu-drivers no longer offers nvidia 550 drivers Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: While I am unclear which package update impacted the video drivers detected by ubuntu-drivers, the nvidia 545 and nvidia 550 video drivers are no longer shown as an option on NVIDIA GeForce GTX 1050 video card. I can understand the removal of the nvidia 545 drivers as the current kernel's linux-signatures-nvidia-6.8.0-28-generic package lacks signatures for the nvidia 545 kernel modules for secure boot but the nvidia 550 kernel modules signatures are available. So while it would be acceptable to downgrade the 'tested' default nvidia driver to 535, ubuntu-drivers and Additional Drivers should be offering the nvidia 550 drivers as an untested option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2062967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063228] Re: screen sometimes blinking
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063228 Title: screen sometimes blinking Status in xorg package in Ubuntu: Confirmed Bug description: My screen sometimes starts flashing strongly. I move the mouse cursor, it stops. I put the cursor back in its place, it starts again. I notice this with Firefox because I use it a lot, I don't know if this happens with other software. I'm under wayland (xwayland?) Description: Ubuntu 24.04 LTS Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 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 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 18:57:50 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84bb] InstallationDate: Installed on 2024-04-07 (16 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Pavilion Laptop 14-ce2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2022 dmi.bios.release: 15.27 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056772] Re: Properties of Audio Files Causes Lock Ups
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/2056772 Title: Properties of Audio Files Causes Lock Ups Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: On SMB mounted file systems, right click properties on audio files causes the Nautilus to freeze. Force/Wait appears. The file system has read/write permission. Happens every time for large .flac files. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46~beta-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 10:33:22 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'recursive-search' b"'always'" b'org.gnome.nautilus.preferences' b'show-directory-item-counts' b"'always'" b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1241, 1039)' InstallationDate: Installed on 2022-04-07 (704 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.51.90-1ubuntu1 nautilus-share0.7.5-0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2056772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2052996] Re: nautilus crashes when drag the image file
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/2052996 Title: nautilus crashes when drag the image file Status in Nautilus: New Status in nautilus package in Ubuntu: Confirmed Bug description: Repro Steps - `repro.webm` attached: 1. Run nautilus 2. Navigate to https://plugins.hex-rays.com/. 3. Drag and drop the Hex-Rays logo onto the Desktop. 4. SEGV at 0x000b Crash Report: ProblemType: Crash Signal: 11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 13 14:52:00 2024 DistroRelease: Ubuntu 22.04 JournalErrors: 2월 13 14:51:57 dch3ck-Z790-UD nautilus[104092]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed 2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_get_child: assertion '!g_path_is_absolute (name)' failed 2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_equal: assertion 'G_IS_FILE (file2)' failed 2월 13 14:51:59 dch3ck-Z790-UD nautilus[104092]: g_file_copy: assertion 'G_IS_FILE (destination)' failed ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= LC_ADDRESS=ko_KR.UTF-8 SHELL=/bin/bash LC_NAME=ko_KR.UTF-8 LC_MEASUREMENT=ko_KR.UTF-8 LC_TIME=ko_KR.UTF-8 LC_MONETARY=ko_KR.UTF-8 LANGUAGE=ko:en_AU:en_CA:en_GB:en_US:en LC_TELEPHONE=ko_KR.UTF-8 LC_PAPER=ko_KR.UTF-8 LC_NUMERIC=ko_KR.UTF-8 PATH=(custom, no user) LANG=ko_KR.UTF-8 LC_IDENTIFICATION=ko_KR.UTF-8 * thread #7, name = 'pool-org.gnome.', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) frame #0: 0x55b7dc24e624 nautilus`___lldb_unnamed_symbol4282 + 1140 nautilus`___lldb_unnamed_symbol4282: -> 0x55b7dc24e624 <+1140>: movl (%rax), %ebx 0x55b7dc24e626 <+1142>: testl %r12d, %r12d 0x55b7dc24e629 <+1145>: je 0x55b7dc24ea60; <+2224> 0x55b7dc24e62f <+1151>: movl 0x118(%rsp), %edx (lldb) bt * thread #7, name = 'pool-org.gnome.', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) * frame #0: 0x55b7dc24e624 nautilus`___lldb_unnamed_symbol4282 + 1140 frame #1: 0x55b7dc24fdde nautilus`___lldb_unnamed_symbol4283 + 542 frame #2: 0x7fb6019b1194 libgio-2.0.so.0`___lldb_unnamed_symbol5250 + 116 frame #3: 0x7fb6026876b4 libglib-2.0.so.0`___lldb_unnamed_symbol2565 + 116 frame #4: 0x7fb602684a51 libglib-2.0.so.0`___lldb_unnamed_symbol2558 + 81 frame #5: 0x7fb601294ac3 libc.so.6`start_thread(arg=) at pthread_create.c:442:8 frame #6: 0x7fb601326850 libc.so.6`__clone3 at clone3.S:81 (lldb) c Process 128770 resuming Process 128770 exited with status = 11 (0x000b) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2052996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 Status in thunderbird package in Ubuntu: Confirmed Bug description: This happened during an upgrade from Mantic to Noble. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: thunderbird 2:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Apr 16 13:15:42 2024 ErrorMessage: new thunderbird package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-10 (2076 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SnapChanges: IDStatus Spawn Ready Summary 3563 Error 2024-04-16T13:15:26-07:00 2024-04-16T13:15:42-07:00 Install "thunderbird" snap 3564 Done2024-04-16T13:22:00-07:00 2024-04-16T13:22:09-07:00 Install "thunderbird" snap SourcePackage: thunderbird Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058769] Re: proposed-migration for click 0.5.2-2
This bug was fixed in the package click - 0.5.2-2ubuntu4 --- click (0.5.2-2ubuntu4) noble; urgency=medium * Fix preload path harder. -- Steve Langasek Tue, 23 Apr 2024 04:32:56 + ** Changed in: click (Ubuntu) Status: New => Fix Released -- 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/2058769 Title: proposed-migration for click 0.5.2-2 Status in click package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Invalid Bug description: click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on all archs except amd64. In order to be able to run the tests without all-proposed=1, glib 2.0 is needed, which is why I marked it as affected. Excerpt of the test logs: ERROR: test_list_simple (click_package.tests.integration.test_list.TestList.test_list_simple) -- Traceback (most recent call last): File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py", line 29, in test_list_simple self.click_install(path_to_click, name, user) File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py", line 99, in click_install subprocess.check_call(cmd) File "/usr/lib/python3.12/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--user=root', '--allow-unauthenticated', '/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit status 1. == ERROR: test_debsig_install_valid_signature (click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature) -- Traceback (most recent call last): File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 207, in test_debsig_install_valid_signature subprocess.check_call( File "/usr/lib/python3.12/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--user=root', '/tmp/tmpymtfsjg9/org.example.debsig-valid-sig_1.0_all.click']' returned non-zero exit status 1. == ERROR: test_debsig_install_can_install_with_sig_override (click_package.tests.integration.test_signatures.TestSignatureVerificationNoSignature.test_debsig_install_can_install_with_sig_override) -- Traceback (most recent call last): File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 164, in test_debsig_install_can_install_with_sig_override subprocess.check_call( File "/usr/lib/python3.12/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--allow-unauthenticated', '--user=root', '/tmp/tmpheysy9ze/org.example.debsig-no-sig_1.0_all.click']' returned non-zero exit status 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/2058769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430531] Re: FILEOPEN: Opening file from Samba share produce Document in Use dialog (~/.gvfs or mount.cifs)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1430531 Title: FILEOPEN: Opening file from Samba share produce Document in Use dialog (~/.gvfs or mount.cifs) Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Confirmed Bug description: This bug is somehow related to other - LibO 72337 [1]. I'm on Ubuntu 12.04.5 with all updates and LibreOffice 3.5.7.2 Build ID: 350m1(Build:2) (libreoffice 1:3.5.7-0ubuntu7) from official repository. The problem exists in more modern versions of LibreOffice from PPA (3.6.6-0ubuntu1~precise1~ppa1 , 4.0.4~rc2-0ubuntu1~precise1 , 4.1.6-0ubuntu1~precise1~ppa1 , 4.2.8~rc2-0ubuntu1~precise1 , 4.3.6~rc2-0ubuntu1~precise1 , 4.4.1~rc2-0ubuntu1~precise1). Steps to reproduce: 1. I have shared Public folder (read write, allow guest) from other Ubuntu 12.04.5 laptop using nautilus-share (0.7.3-1ubuntu2), placed test.odt file in it. 2a. I navigate Nautilus on other laptop to smb://laptop/public, clicked 'Open in Terminal here' (or launch terminal and "cd ~/.gvfs/public\ on\ laptop"). Run "libreoffice test.odt" in terminal. 2b. I navigate Nautilus on other laptop to smb://laptop/public, clicked on 'test.odt' file. 2c. I mount share from terminal with sudo mount.cifs //192.168.3.11/public /mnt/smb/ -o uid=`id -u`,gid=`id -g`,guest,sec=none,noperm then libreoffice /mnt/smb/test.odt 3. Got "Document in Use" window with text: Document file 'test.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel 4a. If I click 'Open Read-Only' the document is opened in read-only. 4b. If I click 'Open Copy' the "Untitled 1" document is opened. 4c. Cancel closes this window. Expected results: The "test.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see pp. 3-4 above). This functionality is essential. Please fix this bug. Notes: If I try to open document with the command 'libreoffice smb://laptop/public/test.odt' I run into other bug (bug 1214352). If I use Windows as SMB/CIFS server I can open and edit document from share. Problem does not exist with SFTP(SSH)- or NFS- file-servers. My test results are located in Google Docs/Drive Table ( http://goo.gl/jY9Ubj ). Global Samba config (/etc/samba/smb.conf) is default. My useshare config is: cat /var/lib/samba/usershares/public #VERSION 2 path=/home/norbert/Public comment= usershare_acl=S-1-1-0:F guest_ok=y sharename=Public 1. https://bugs.documentfoundation.org/show_bug.cgi?id=72337 . ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice 1:3.5.7-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-46.77~precise1-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Tue Mar 10 23:52:04 2015 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1430531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054627] Re: Chromium fails to launch/startup up
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2054627 Title: Chromium fails to launch/startup up Status in chromium-browser package in Ubuntu: Expired Bug description: Chromium fails to start up from the KDE interface. I click the icon and nothing happen. When I launch Chromium from the terminal it launches but I get the following output in the terminal: (chrome:55656): Gtk-WARNING **: 20:39:23.626: Theme parsing error: gtk.css:1:21: Failed to import: Error opening file /home/user/snap/chromium/2757/.config/gtk-3.0/colors.css: No such file or directory Gtk-Message: 20:39:23.666: Failed to load module "colorreload-gtk-module" Gtk-Message: 20:39:23.666: Failed to load module "window-decorations-gtk-module" [55656:55656:0221/203923.708230:ERROR:policy_logger.cc(156)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build. (chrome:55656): IBUS-WARNING **: 20:39:24.041: Failed to mkdir /home/user/snap/chromium/2757/.config/ibus/bus: Not a directory ProblemType: Bug DistroRelease: Ubuntu 24.04 Uname: Linux 6.7.5-060705-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 21 20:40:07 2024 InstallationDate: Installed on 2024-02-17 (5 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240213) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Snap: chromium 121.0.6167.184 (stable) SnapChanges: ID Status Spawn Ready Summary 4Done2024-02-21T19:35:25-06:00 2024-02-21T19:35:59-06:00 Install "chromium" snap SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061211] Re: Invalid escape sequences in regexes when installing gedit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gedit (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/2061211
Title:
Invalid escape sequences in regexes when installing gedit
Status in gedit package in Ubuntu:
Confirmed
Bug description:
On a clean install of the 24.04 beta, if you do a "sudo apt install
gedit", you get the following messages at the end of the install:
/usr/lib/x86_64-linux-gnu/gedit/plugins/externaltools/library.py:212:
SyntaxWarning: invalid escape sequence '\-'
RE_KEY = re.compile('^([a-zA-Z_][a-zA-Z0-9_.\-]*)(\[([a-zA-Z_@]+)\])?$')
/usr/lib/x86_64-linux-gnu/gedit/plugins/snippets/substitutionparser.py:162:
SyntaxWarning: invalid escape sequence '\s'
match = re.match('?%s\s*' % self.REG_GROUP, tokens)
So there are 2 issues with regexes.
Bug #2055010 reports the first of these, but not the second, and it
also reports a different issue as "the huger problem" (one that I
can't reproduce). I hope I'm making the right call in opening a new
bug report specifically for these regex issues.
Some more details:
- on the clean install, I did apply all available updates before trying to
install gedit
- you can also reproduce this issue from the live ("try ubuntu") environment
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gedit 46.2-1build1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 08:41:26 2024
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2061211/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054868] Re: invalid escape sequence
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: hplip (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2054868
Title:
invalid escape sequence
Status in hplip package in Ubuntu:
Confirmed
Bug description:
Todays update with python 3.12
/usr/share/hplip/base/LedmWifi.py:34: SyntaxWarning: invalid escape sequence
'\d
'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/device.py:49: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/g.py:304: SyntaxWarning: invalid escape sequence '\|'
spinner = "\|/-\|/-"
/usr/share/hplip/base/g.py:354: SyntaxWarning: invalid escape sequence '\d'
m = re.search('python(\d(\.\d){0,2})', ext_path)#get the python
ve
rsion where the .so file is found
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape
sequence '
\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape
sequence '
\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape
sequence '
\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/base/logger.py:439: SyntaxWarning: invalid escape sequence
'\<'
elem_start = re.findall("(\<\W{0,1}\w+) ?", line)[0]
/usr/share/hplip/base/logger.py:440: SyntaxWarning: invalid escape sequence
'\]'
elem_finished = re.findall("([?|\]\]]*\>)", line)[0]
/usr/share/hplip/base/logger.py:442: SyntaxWarning: invalid escape sequence
'\S'
attrs = re.findall("(\S*?\=\".*?\")", line)
/usr/share/hplip/base/models.py:37: SyntaxWarning: invalid escape sequence
'\d'
pat_prod_num = re.compile("""(\d+)""", re.I)
/usr/share/hplip/base/models.py:428: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:429: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:430: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:431: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:432: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-virgin', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:433: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-dvc', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:434: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:435: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:436: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-id', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:437: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-hp-ink', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:438: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-health-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:439: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-health$', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:440: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-known', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:441: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-level', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:442: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-ack', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:443: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:444: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^in-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:445: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^out-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:446: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^model(\d+)', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/password.py:212: SyntaxWarning: invalid escape sequence
'\
['
cb = cb.replace("[", "\[")
[Desktop-packages] [Bug 2060659] Re: X11 fractional scaling support is missing in 46.0
This bug was fixed in the package mutter - 46.0-1ubuntu9 --- mutter (46.0-1ubuntu9) noble; urgency=medium * Have mutter-common Breaks/Replaces recent magpie-common for org.gnome.mutter.x11.gschema.xml (LP: #2060659) -- Jeremy Bícha Thu, 18 Apr 2024 16:01:26 -0400 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: magpie (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060659 Title: X11 fractional scaling support is missing in 46.0 Status in magpie package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: X11 fractional scaling support is missing in mutter/gnome-shell 46.0 https://salsa.debian.org/gnome- team/mutter/-/commit/414010ddef06757000175c30238371739199d29a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magpie/+bug/2060659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060659] Re: X11 fractional scaling support is missing in 46.0
This bug was fixed in the package magpie - 0.9.3-0ubuntu8 --- magpie (0.9.3-0ubuntu8) noble; urgency=medium * Revert recent X11 fractional scaling changes now that Ubuntu's mutter has regained support (LP: #2060659) - Drop install_x11_schema.patch - Don't try to install mutter gsettings schema - Drop Breaks/Replaces: mutter-common - Bump required mutter-common version -- Jeremy Bícha Thu, 18 Apr 2024 16:09:50 -0400 -- 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/2060659 Title: X11 fractional scaling support is missing in 46.0 Status in magpie package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: X11 fractional scaling support is missing in mutter/gnome-shell 46.0 https://salsa.debian.org/gnome- team/mutter/-/commit/414010ddef06757000175c30238371739199d29a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magpie/+bug/2060659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062418] Re: gedit ships obsolete /usr/bin/gnome-text-editor alternative
This bug was fixed in the package gedit - 46.2-2 --- gedit (46.2-2) unstable; urgency=medium * debian/postinst: Remove gedit as a gnome-text-editor alternative in the alternatives system now that gnome-text-editor is an actual program, provided in the gnome-text-editor package (Closes: #1057184) (LP: #2062418) -- Jeremy Bícha Tue, 23 Jan 2024 16:13:14 -0500 ** Changed in: gedit (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/2062418 Title: gedit ships obsolete /usr/bin/gnome-text-editor alternative Status in gedit package in Ubuntu: Fix Released Status in gedit package in Debian: Fix Released Bug description: gedit ships an entry for Debian's alternatives system for /usr/bin/gnome-text-editor and a corresponding manpage. However, there is now a real app named gnome-text-editor that ships /usr/bin/gnome-text-editor Therefore we should remove the entry in Debian's alternative system. A few more details on the Debian bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2062418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: java-atk-wrapper (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: Confirmed Status in openjdk-8 package in Ubuntu: Fix Released Status in openjdk-8 package in Debian: Fix Released Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them See LP: #1916327 The alternative is to publish atk-wrapper for i386 in mantic, jammy and focal. Options: a) rollback the fix in Ubuntu b) publish atk-wrapper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057651] Re: Rename the ubuntu-advantage-tools package
This bug was fixed in the package wsl-pro-service - 0.1.4 --- wsl-pro-service (0.1.4) noble; urgency=medium * Vendor manually on the host as the go mod vendoring when using dpkg-buildpackage works in a different environment. wsl-pro-service (0.1.3) noble; urgency=medium * Pin Go toolchain to 1.22.2 to fix the following security vulnerabilities: - GO-2024-2687 * Use self-signed certificate chain to communicate with the Windows Agent over mTLS. (LP: #2060548) * Simplify the communication with the agent removing the double server. * Send the READY signal to systemd earlier. * Renamed ubuntu-advantage-tools to ubuntu-pro-client (LP: #2057651) * Restrict landscape.conf file permissions. (thanks iosifache) * Adds a default 'wsl' tag to Landscape configs. * Removed and obfuscated log messages that could leak sensitive information. * More robust handling output of cmd.exe commands. * More careful validation of the .address file contents. * Updated dependencies. -- Didier Roche-Tolomelli Fri, 19 Apr 2024 07:56:41 +0200 ** Changed in: wsl-pro-service (Ubuntu Noble) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wsl-pro-service in Ubuntu. https://bugs.launchpad.net/bugs/2057651 Title: Rename the ubuntu-advantage-tools package Status in wsl-pro-service package in Ubuntu: Fix Released Status in wsl-pro-service source package in Noble: Fix Released Bug description: From ubuntu-advantage-tools v31, it has been renamed to ubuntu-pro- client. The current package is now a transitional package pointing to ubuntu-pro-client. wsl-pro-service depends on ubuntu-advantage-tool thus we should rename the dependency to ubuntu-pro-client to avoid having the transitional package as a dependency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2057651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060548] Re: [FFe] Update and seed wsl-pro-service in the WSL images
This bug was fixed in the package wsl-pro-service - 0.1.4 --- wsl-pro-service (0.1.4) noble; urgency=medium * Vendor manually on the host as the go mod vendoring when using dpkg-buildpackage works in a different environment. wsl-pro-service (0.1.3) noble; urgency=medium * Pin Go toolchain to 1.22.2 to fix the following security vulnerabilities: - GO-2024-2687 * Use self-signed certificate chain to communicate with the Windows Agent over mTLS. (LP: #2060548) * Simplify the communication with the agent removing the double server. * Send the READY signal to systemd earlier. * Renamed ubuntu-advantage-tools to ubuntu-pro-client (LP: #2057651) * Restrict landscape.conf file permissions. (thanks iosifache) * Adds a default 'wsl' tag to Landscape configs. * Removed and obfuscated log messages that could leak sensitive information. * More robust handling output of cmd.exe commands. * More careful validation of the .address file contents. * Updated dependencies. -- Didier Roche-Tolomelli Fri, 19 Apr 2024 07:56:41 +0200 ** Changed in: wsl-pro-service (Ubuntu) Status: Triaged => 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/2060548 Title: [FFe] Update and seed wsl-pro-service in the WSL images Status in ubuntu-meta package in Ubuntu: Fix Released Status in wsl-pro-service package in Ubuntu: Fix Released Bug description: This is a new package for this release. It’s only functional with a Windows agent which is not publically released and under beta for now. As the end of the beta will be after the 24.04 release, we want to get as close as possible to the current code level, knowing that current code will still certainly grow feature-wise once with the Beta user feedback. However, having it seeded (the MIR is approved and security issues fixed but the certificate one, which has been discussed as minor for now) with the current code level will be great to diminish the diff when the SRU that will be needed then. The impact is on existing non beta users (and beta users are using a ppa with the ppa containing the current code level). Current diff is large as the development is very active and won’t really provide anything more. Note that it contains also a packaging change to fix bug #2057651. It also fixes a vulnerability by depending on latest Go and latest x/net/http. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2060548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051855] Re: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/2051855 Title: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen Status in mutter package in Ubuntu: Expired Bug description: Mutter causes desktop to extend beyond screen, looks like 2160p on 1440p screen. This appeared only after installing the latest update of the libmutter package. I am using 2x Samsung S27AG502NUXEN displays in extended desktop mode (join). So far the only fix i have found is holding back this package. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libmutter-13-0 45.2-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 14:33:53 2024 InstallationDate: Installed on 2021-10-04 (849 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-10-16 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2051855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061857] Re: [FFe] enable the new GNOME OneDrive backend
This bug was fixed in the package gnome-online-accounts - 3.50.0-4ubuntu2 --- gnome-online-accounts (3.50.0-4ubuntu2) noble; urgency=medium * debian/control, debian/rules: - enable the Microsoft OneDrive support now that the msgraph MIR has been approved (lp: #2061857) -- Sebastien Bacher Tue, 16 Apr 2024 13:51:26 +0200 ** Changed in: gnome-online-accounts (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2061857 Title: [FFe] enable the new GNOME OneDrive backend Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: Fix Released Bug description: One of the new features of the new GNOME 46 is the support of Microsoft OneDrive accounts. The code relies on a new library 'msgraph'. The MIR bug #2060035 just got approved and such we would like to turn on the option now in Noble. The changes are in - gnome-online-accounts, adding a new provider for OneDrive The package with the change has been built in the desktop ppa https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15971851/+listing-archive-extra The change is basically adding the libmsgraph-dev Build-Depends in debian/control and changing the option to true in debian/rules - gvfs, adding a new backend to be able to browse those locations from nautilus The package is similar built in our ppa https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15972025/+listing-archive-extra And the change are similar Build-Depends/rules option The regression potential is low since those are new backends and not changing existing features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2061857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063049] Re: chromium snap doesnt launch properly on 24.04
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2063049
Title:
chromium snap doesnt launch properly on 24.04
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
chromium snap only launches with titlebar and transparent window after
recent snap update on wayland and intel grafics.
Adding --ozone-platform=wayland fixes the issue for me. (workaround
from bug #1968610)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: chromium-browser 2:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
Uname: Linux 6.8.0-28-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: sway
Date: Sun Apr 21 20:25:30 2024
DiskUsage:
FilesystemType Size Used Avail Use% Mounted on
rpool/ROOT/ubuntu_gk6kaa zfs 50G 7,7G 42G 16% /
tmpfs tmpfs 16G 128M 16G 1% /dev/shm
rpool/USERDATA/k1l_0tberh zfs437G 396G 42G 91% /home/k1l
InstallationDate: Installed on 2022-03-24 (760 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
Snap.Changes:
ID Status Spawn Ready Summary
635 Done2024-04-21T00:51:33+02:00 2024-04-21T00:52:11+02:00 Snap
"chromium" aktualisieren
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to noble on 2024-03-25 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063049/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062980] [NEW] nautilus progress bar on ubuntu dock icon does not update
You have been subscribed to a public bug: while copying files from another disk to /home folder, the progress bar on the nautilus icon in ubuntu dock does not update. however, the progress icon within nautilus does update. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 22:46:11 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1301, 915)' ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- nautilus progress bar on ubuntu dock icon does not update https://bugs.launchpad.net/bugs/2062980 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053019] Re: [nvidia] Second (external) monitor not active after screen lock in Xorg
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
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/2053019
Title:
[nvidia] Second (external) monitor not active after screen lock in
Xorg
Status in mutter package in Ubuntu:
Expired
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Expired
Bug description:
After switching back to Xorg, I have encountered the issue with the
second (external) monitor - after the screen is locked and I unlock
it, the second monitor either shows a blank black screen or is not
even active in Display settings. It's like the configuration is lost
during lock/unclock process.
I am using USB-C to HDMI cable with the second screen and Xorg as
display manager.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 13 12:53:24 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[17aa:3a58]
InstallationDate: Installed on 2024-01-12 (32 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2023
dmi.bios.release: 1.64
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN64WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 7 16ACHg6
dmi.ec.firmware.release: 1.64
dmi.modalias:
dmi:bvnLENOVO:bvrGKCN64WW:bd12/07/2023:br1.64:efr1.64:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2053019/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2053019] Re: [nvidia] Second (external) monitor not active after screen lock in Xorg
[Expired for nvidia-graphics-drivers-535 (Ubuntu) because there has been
no activity for 60 days.]
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Incomplete => Expired
--
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/2053019
Title:
[nvidia] Second (external) monitor not active after screen lock in
Xorg
Status in mutter package in Ubuntu:
Expired
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Expired
Bug description:
After switching back to Xorg, I have encountered the issue with the
second (external) monitor - after the screen is locked and I unlock
it, the second monitor either shows a blank black screen or is not
even active in Display settings. It's like the configuration is lost
during lock/unclock process.
I am using USB-C to HDMI cable with the second screen and Xorg as
display manager.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 13 12:53:24 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[17aa:3a58]
InstallationDate: Installed on 2024-01-12 (32 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2023
dmi.bios.release: 1.64
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN64WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 7 16ACHg6
dmi.ec.firmware.release: 1.64
dmi.modalias:
dmi:bvnLENOVO:bvrGKCN64WW:bd12/07/2023:br1.64:efr1.64:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2053019/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062538] Re: Clicking the top bar shows desktop icons above app window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2062538 Title: Dragging the top bar shows desktop icons above app window Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Sometimes when slowly double clicking the top bar while an app window is maximized, the desktop icons appear above the app and disappears as shown in the attached screen-cast. I also believe that app windows should not be handled from the top bar, like you shouldn't grab it to restore from being maximized; this should should be effective from the app window title bar only! ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 13:06:43 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (28 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu7 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2062538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062538] Re: Clicking the top bar shows desktop icons above app window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2062538 Title: Dragging the top bar shows desktop icons above app window Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Sometimes when slowly double clicking the top bar while an app window is maximized, the desktop icons appear above the app and disappears as shown in the attached screen-cast. I also believe that app windows should not be handled from the top bar, like you shouldn't grab it to restore from being maximized; this should should be effective from the app window title bar only! ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.1-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 13:06:43 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-03-22 (28 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu7 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-11 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2062538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062916] [NEW] evolution has undefined symbol in newest libwebkit2gtk
You have been subscribed to a public bug: evolution: symbol lookup error: /lib/x86_64-linux- gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 The libwebkit2gtk version is libwebkit2gtk-4.0-37_2.44.0-0ubuntu0.22.04.1_amd64.deb ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New -- evolution has undefined symbol in newest libwebkit2gtk https://bugs.launchpad.net/bugs/2062916 You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041193] Re: Incorrect font family name in 30-cjk-aliases.conf
This bug was fixed in the package language-selector - 0.225 --- language-selector (0.225) noble; urgency=medium [ Gunnar Hjalmarsson ] * fontconfig/30-cjk-aliases.conf: - Fix typo in font family name (LP: #2041193) [ Jeremy Bícha ] * Update translations from Launchpad -- Jeremy Bícha Thu, 18 Apr 2024 21:27:07 -0400 ** Changed in: language-selector (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2041193 Title: Incorrect font family name in 30-cjk-aliases.conf Status in language-selector package in Ubuntu: Fix Released Bug description: There is a typo in the definition of "MS UIGothic" in fontconfig/30-cjk-aliases.conf. It should be "MS UI Gothic", i.e. there is a space between "UI" and "Gothic". See https://learn.microsoft.com/en-us/typography/font-list/ms-ui-gothic for typeface details. There would have been no negative effect, since fontconfig seems to ignore whitespace when matching. Just sake of completeness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2041193/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061914] Re: libjavascriptcoregtk-4.0-18 seems to be missing on the latest build (24.04)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: webkit2gtk (Ubuntu) Status: New => Confirmed -- 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/2061914 Title: libjavascriptcoregtk-4.0-18 seems to be missing on the latest build (24.04) Status in webkit2gtk package in Ubuntu: Confirmed Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu >lsb_release -rd No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center as a workaround downloaded from: https://answers.launchpad.net/ubuntu/noble/amd64/libjavascriptcoregtk-4.0-18/2.43.3-1 libjavascriptcoregtk-4.0-18/now 2.43.3-1 amd64 [instalado, local] JavaScript engine library from WebKitGTK 3) What you expected to happen sudo apt install libjavascriptcoregtk-4.0-18 4) What happened instead missing package/not available EXPECTED: gir1.2-javascriptcoregtk-4.0: JavaScript engine library from WebKitGTK - GObject introspection data gir1.2-javascriptcoregtk-4.1: JavaScript engine library from WebKitGTK - GObject introspection data gir1.2-javascriptcoregtk-6.0: JavaScript engine library from WebKitGTK - GObject introspection data gir1.2-webkit-6.0: Web content engine library for GTK - GObject introspection data gir1.2-webkit2-4.0: Web content engine library for GTK - GObject introspection data gir1.2-webkit2-4.1: Web content engine library for GTK - GObject introspection data libjavascriptcoregtk-4.0-18: JavaScript engine library from WebKitGTK libjavascriptcoregtk-4.0-18-dbgsym: debug symbols for libjavascriptcoregtk-4.0-18 libjavascriptcoregtk-4.0-bin: WebKitGTK JavaScript command-line interpreter (transitional dummy package) libjavascriptcoregtk-4.0-bin-dbgsym: No summary available for libjavascriptcoregtk-4.0-bin-dbgsym in ubuntu noble. libjavascriptcoregtk-4.0-dev: JavaScript engine library from WebKitGTK - development files libjavascriptcoregtk-4.1-0: JavaScript engine library from WebKitGTK libjavascriptcoregtk-4.1-0-dbgsym: debug symbols for libjavascriptcoregtk-4.1-0 libjavascriptcoregtk-4.1-dev: JavaScript engine library from WebKitGTK - development files libjavascriptcoregtk-6.0-1: JavaScript engine library from WebKitGTK libjavascriptcoregtk-6.0-1-dbgsym: debug symbols for libjavascriptcoregtk-6.0-1 libjavascriptcoregtk-6.0-dev: JavaScript engine library from WebKitGTK - development files libwebkit2gtk-4.0-37: Web content engine library for GTK libwebkit2gtk-4.0-37-dbgsym: debug symbols for libwebkit2gtk-4.0-37 libwebkit2gtk-4.0-dev: Web content engine library for GTK - development files libwebkit2gtk-4.0-doc: Web content engine library for GTK - documentation libwebkit2gtk-4.1-0: Web content engine library for GTK libwebkit2gtk-4.1-0-dbgsym: debug symbols for libwebkit2gtk-4.1-0 libwebkit2gtk-4.1-dev: Web content engine library for GTK - development files libwebkitgtk-6.0-4: Web content engine library for GTK libwebkitgtk-6.0-4-dbgsym: debug symbols for libwebkitgtk-6.0-4 libwebkitgtk-6.0-dev: Web content engine library for GTK - development files webkit2gtk-driver: WebKitGTK WebDriver support webkit2gtk-driver-dbgsym: debug symbols for webkit2gtk-driver AVAILABLE: Built packages MISSING!!! gir1.2-javascriptcoregtk-4.1 JavaScript engine library from WebKitGTK - GObject introspection data gir1.2-javascriptcoregtk-6.0 JavaScript engine library from WebKitGTK - GObject introspection data gir1.2-webkit-6.0 Web content engine library for GTK - GObject introspection data MISSING!!! gir1.2-webkit2-4.1 Web content engine library for GTK - GObject introspection data MISSING!!! MISSING!!! libjavascriptcoregtk-4.0-bin WebKitGTK JavaScript command-line interpreter (transitional dummy package) MISSING!!! libjavascriptcoregtk-4.1-0 JavaScript engine library from WebKitGTK libjavascriptcoregtk-4.1-0-dbgsym debug symbols for libjavascriptcoregtk-4.1-0 libjavascriptcoregtk-4.1-dev JavaScript engine library from WebKitGTK - development files libjavascriptcoregtk-6.0-1 JavaScript engine library from WebKitGTK libjavascriptcoregtk-6.0-1-dbgsym debug symbols for libjavascriptcoregtk-6.0-1 libjavascriptcoregtk-6.0-dev JavaScript engine library from WebKitGTK - development files libjavascriptcoregtk-bin JavaScript engine library from WebKitGTK - command-line interpreter libjavascriptcoregtk-bin-dbgsym debug symbols for libjavascriptcoregtk-bin libwebkit2gtk-4.0-doc WebKitGTK documentation (transitional dummy package)
[Desktop-packages] [Bug 2060548] Re: [FFe] Update and seed wsl-pro-service in the WSL images
This bug was fixed in the package ubuntu-meta - 1.539 --- ubuntu-meta (1.539) noble; urgency=medium * Refreshed dependencies * Added pemmican-desktop to desktop-raspi (LP: #2062564) * Added pemmican-server to server-raspi (LP: #2062564) * Added trace-cmd to standard-recommends (LP: #2062557) * Added wsl-pro-service to wsl-recommends (LP: #2060548) * Added libgtk-3-0t64 to wsl [amd64 arm64 ppc64el riscv64 s390x] * Removed libgtk-3-0 from wsl * Added libpam-fprintd to desktop-minimal-recommends [armhf], desktop- recommends [armhf] * Added libpam-sss to desktop-minimal-recommends [armhf], desktop- recommends [armhf] -- Didier Roche-Tolomelli Fri, 19 Apr 2024 16:00:57 +0200 ** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => 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/2060548 Title: [FFe] Update and seed wsl-pro-service in the WSL images Status in ubuntu-meta package in Ubuntu: Fix Released Status in wsl-pro-service package in Ubuntu: Triaged Bug description: This is a new package for this release. It’s only functional with a Windows agent which is not publically released and under beta for now. As the end of the beta will be after the 24.04 release, we want to get as close as possible to the current code level, knowing that current code will still certainly grow feature-wise once with the Beta user feedback. However, having it seeded (the MIR is approved and security issues fixed but the certificate one, which has been discussed as minor for now) with the current code level will be great to diminish the diff when the SRU that will be needed then. The impact is on existing non beta users (and beta users are using a ppa with the ppa containing the current code level). Current diff is large as the development is very active and won’t really provide anything more. Note that it contains also a packaging change to fix bug #2057651. It also fixes a vulnerability by depending on latest Go and latest x/net/http. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2060548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062557] Re: [FFe] add trace-cmd to standand seed
This bug was fixed in the package ubuntu-meta - 1.539 --- ubuntu-meta (1.539) noble; urgency=medium * Refreshed dependencies * Added pemmican-desktop to desktop-raspi (LP: #2062564) * Added pemmican-server to server-raspi (LP: #2062564) * Added trace-cmd to standard-recommends (LP: #2062557) * Added wsl-pro-service to wsl-recommends (LP: #2060548) * Added libgtk-3-0t64 to wsl [amd64 arm64 ppc64el riscv64 s390x] * Removed libgtk-3-0 from wsl * Added libpam-fprintd to desktop-minimal-recommends [armhf], desktop- recommends [armhf] * Added libpam-sss to desktop-minimal-recommends [armhf], desktop- recommends [armhf] -- Didier Roche-Tolomelli Fri, 19 Apr 2024 16:00:57 +0200 ** Changed in: ubuntu-meta (Ubuntu) Status: New => 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/2062557 Title: [FFe] add trace-cmd to standand seed Status in trace-cmd package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: trace-cmd is one of the package to be available in Ubuntu by default as part of the Performance Engineering tools initiative. See https://discourse.ubuntu.com/t/spec-include-performance-tooling-in- ubuntu/43134 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/2062557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062564] Re: [FFe] Seed pemmican
This bug was fixed in the package ubuntu-meta - 1.539 --- ubuntu-meta (1.539) noble; urgency=medium * Refreshed dependencies * Added pemmican-desktop to desktop-raspi (LP: #2062564) * Added pemmican-server to server-raspi (LP: #2062564) * Added trace-cmd to standard-recommends (LP: #2062557) * Added wsl-pro-service to wsl-recommends (LP: #2060548) * Added libgtk-3-0t64 to wsl [amd64 arm64 ppc64el riscv64 s390x] * Removed libgtk-3-0 from wsl * Added libpam-fprintd to desktop-minimal-recommends [armhf], desktop- recommends [armhf] * Added libpam-sss to desktop-minimal-recommends [armhf], desktop- recommends [armhf] -- Didier Roche-Tolomelli Fri, 19 Apr 2024 16:00:57 +0200 ** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => 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/2062564 Title: [FFe] Seed pemmican Status in pemmican package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: [ Impact ] Add pemmican to raspi server and desktop images in order that Pi 5 users can be notified if/when overcurrent or undervolt events occur (potentially resulting in brownout, data-corruption, and all manner of other symptoms typically caused as a result of undervolt). [ Test Plan ] On all supported models of Pi: * Boot the image with pemmican installed * Ensure boot proceeds normally with package installed and that no warnings appear On the Pi 5 specifically: * Boot the image normally * Ensure boot proceeds normally with package installed and that no warnings appear * Using bench power-supply to back-feed the Pi, lower voltage until brownout occurs * Reboot and ensure undervolt warning is shown * Shutdown and boot with PSU that cannot negotiate 5A * Ensure deficient PSU warning is shown On the Pi 5 desktop image specifically: * Boot desktop image * Attach USB load tester and raise current draw until USB ports fail * Ensure overcurrent warning is displayed [ Regression Potential ] Quite low given all the tests noted above have already been performed on all supported models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2062564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062580] [NEW] Connecting to bluetooth device requires two attempts
You have been subscribed to a public bug: When connecting to an already paired bluetooth device (Sennheiser HD350BT), the first attempt will result in the 'connected' status after ~20 seconds, but the device will not indicate that the connection was successful and audio does not play through the headphones. Successfully connecting to the headset requires that the bluetooth connection is disabled and then re-enabled, after which the headset indicates a successful connection and audio playback functions correctly through the connected headset. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: joe2161 F pulseaudio /dev/snd/controlC0: joe2161 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 16:52:23 2024 InstallationDate: Installed on 2023-01-17 (457 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Scala_CAS dmi.board.vendor: CZ dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd07/21/2021:br1.8:efr1.5:svnAcer:pnNitroAN515-45:pvrV1.08:rvnCZ:rnScala_CAS:rvrV1.08:cvnAcer:ct10:cvrV1.08:sku: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-45 dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- Connecting to bluetooth device requires two attempts https://bugs.launchpad.net/bugs/2062580 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062177] Re: Remmina crashes after RDP connection
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: remmina (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2062177
Title:
Remmina crashes after RDP connection
Status in remmina package in Ubuntu:
Confirmed
Bug description:
When connecting with RDP Remmina crashes. Syslog show the following:
2024-04-18T13:49:02.969819+02:00 localhost dbus-daemon[3214]: [session
uid=1001 pid=3214] Successfully activated service
'org.gnome.seahorse.Application'
2024-04-18T13:49:03.655883+02:00 localhost systemd[3176]: Started
app-gnome-org.remmina.Remmina-53436.scope - Application launched by gnome-shell.
2024-04-18T13:49:03.656884+02:00 localhost remmina[53441]: Remmina does not
log all output statements. Turn on more verbose output by using
"G_MESSAGES_DEBUG=remmina" as an environment variable.#012More info available
on the Remmina wiki
at:#012https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging
2024-04-18T13:49:03.766401+02:00 localhost remmina[53441]:
gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem
2024-04-18T13:49:13.851397+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key
index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER]
2024-04-18T13:49:13.851716+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE
[obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:637]
2024-04-18T13:49:13.851760+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0:
dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000],
dli_sname=winpr_backtrace [0x70e694e97660]
2024-04-18T13:49:13.851791+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1:
dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000],
dli_sname=winpr_log_backtrace_ex [0x70e694e9f150]
2024-04-18T13:49:13.851803+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2:
dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851815+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3:
dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420],
dli_sname=freerdp_settings_get_bool [0x70e6942658a0]
2024-04-18T13:49:13.851827+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4:
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so
[0x70e6958dd000], dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851839+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5:
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so
[0x70e6958dd000], dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851851+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6:
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851873+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7:
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851885+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable,
address=(nil)
2024-04-18T13:49:14.938231+02:00 localhost
org.remmina.Remmina.desktop[53436]: /usr/bin/remmina-file-wrapper: line 37:
53441 Aborted (core dumped) "$REMMINA" "${@}"
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: remmina 1.4.35+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Apr 18 13:59:31 2024
InstallationDate: Installed on 2022-05-21
[Desktop-packages] [Bug 2062377] [NEW] Ubuntu 24.04. Xorg crash when dmz-white cursor is selected
You have been subscribed to a public bug: 1)Go to xorg 2)Download Gnome Tweak Tool 3)Select DMZ-white 4)crash from the system ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:38:02 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524] Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524] InstallationDate: Installed on 2024-04-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) MachineType: Acer Aspire A715-42G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_CAS dmi.board.vendor: LN dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-42G dmi.product.sku: dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mutter (Ubuntu) Importance: High Status: Confirmed ** Tags: amd64 apport-bug crash noble ubuntu -- Ubuntu 24.04. Xorg crash when dmz-white cursor is selected https://bugs.launchpad.net/bugs/2062377 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061857] Re: [FFe] enable the new GNOME OneDrive backend
This bug was fixed in the package gvfs - 1.54.0-1ubuntu2 --- gvfs (1.54.0-1ubuntu2) noble; urgency=medium * Disable onedrive on i386 and fix the build -- Sebastien Bacher Thu, 18 Apr 2024 15:39:03 +0200 ** Changed in: gvfs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2061857 Title: [FFe] enable the new GNOME OneDrive backend Status in gnome-online-accounts package in Ubuntu: Fix Committed Status in gvfs package in Ubuntu: Fix Released Bug description: One of the new features of the new GNOME 46 is the support of Microsoft OneDrive accounts. The code relies on a new library 'msgraph'. The MIR bug #2060035 just got approved and such we would like to turn on the option now in Noble. The changes are in - gnome-online-accounts, adding a new provider for OneDrive The package with the change has been built in the desktop ppa https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15971851/+listing-archive-extra The change is basically adding the libmsgraph-dev Build-Depends in debian/control and changing the option to true in debian/rules - gvfs, adding a new backend to be able to browse those locations from nautilus The package is similar built in our ppa https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15972025/+listing-archive-extra And the change are similar Build-Depends/rules option The regression potential is low since those are new backends and not changing existing features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2061857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061090] Re: [FFe] add libheif as a dependency
This bug was fixed in the package libgd2 - 2.3.3-9ubuntu5 --- libgd2 (2.3.3-9ubuntu5) noble; urgency=medium * d/control: restore libheif-dev dependency (LP: #2061090). Remaining changes: - Drop the dependencies on libavif, libavif has an extensive rust dependency tree that makes it unsuitable for main. -- Vladimir Petko Tue, 16 Apr 2024 20:23:30 +1200 ** Changed in: libgd2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2061090 Title: [FFe] add libheif as a dependency Status in gnome-control-center package in Ubuntu: Fix Released Status in libgd2 package in Ubuntu: Fix Released Status in shotwell package in Ubuntu: Fix Released Bug description: This issue depends on libheif update[1] as well as security review for libyuv[2] [Why it is needed] libheif is ready to be included in main. Drop delta which removes libheif as a dependencey. This will enable decoding HEIF files by libgd2. See MIR for more details[3] [Build] PPA: ppa:vpa1977/libheif[4] Testing: - piuparts test [5] - check piuparts log that libheif is installed (passes)[5]. [What can go wrong] libheif might pull in unexpected dependencies. Validate that MIR is completed for libheif dependencies in the scope of[1] testing. [Original Description] libheif is ready to be included in main. Drop delta which removes libheif as a dependencey. This will enable decoding HEIF files by libgd2. See MIR for more details - https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/1827442 This exception should be considered in conjunction with https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/2061089 [1] https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/2061089 [2] https://bugs.launchpad.net/ubuntu/+source/libyuv/+bug/2004516 [3] https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/1827442 [4] https://launchpad.net/~vpa1977/+archive/ubuntu/libheif/+packages [5] https://bugs.launchpad.net/ubuntu/+source/libgd2/+bug/2061090/comments/2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2061090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061090] Re: [FFe] add libheif as a dependency
This bug was fixed in the package gnome-control-center - 1:46.0.1-1ubuntu7 --- gnome-control-center (1:46.0.1-1ubuntu7) noble; urgency=medium * Re-enable Location Services for now after more conversation -- Jeremy Bícha Thu, 18 Apr 2024 12:54:43 -0400 -- 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/2061090 Title: [FFe] add libheif as a dependency Status in gnome-control-center package in Ubuntu: Fix Released Status in libgd2 package in Ubuntu: Fix Committed Status in shotwell package in Ubuntu: Fix Released Bug description: This issue depends on libheif update[1] as well as security review for libyuv[2] [Why it is needed] libheif is ready to be included in main. Drop delta which removes libheif as a dependencey. This will enable decoding HEIF files by libgd2. See MIR for more details[3] [Build] PPA: ppa:vpa1977/libheif[4] Testing: - piuparts test [5] - check piuparts log that libheif is installed (passes)[5]. [What can go wrong] libheif might pull in unexpected dependencies. Validate that MIR is completed for libheif dependencies in the scope of[1] testing. [Original Description] libheif is ready to be included in main. Drop delta which removes libheif as a dependencey. This will enable decoding HEIF files by libgd2. See MIR for more details - https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/1827442 This exception should be considered in conjunction with https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/2061089 [1] https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/2061089 [2] https://bugs.launchpad.net/ubuntu/+source/libyuv/+bug/2004516 [3] https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/1827442 [4] https://launchpad.net/~vpa1977/+archive/ubuntu/libheif/+packages [5] https://bugs.launchpad.net/ubuntu/+source/libgd2/+bug/2061090/comments/2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2061090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061090] Re: [FFe] add libheif as a dependency
This bug was fixed in the package shotwell - 0.32.6-1ubuntu1 --- shotwell (0.32.6-1ubuntu1) noble; urgency=medium * Merge with Debian (LP: #2062162). Remaining changes: - d/replace_thumbnailer.sh, d/shotwell-common.README.Debian, d/shotwell.examples, d/shotwell.postrm, d/shotwell.README.Debian: + clean out thumbnailer hacks, that's not user friendly and not something we should recommend. * Add Depends: heif-gdk-pixbuf, heif-thumbnailer (LP: #2061090) * Drop Build-Depends: python3-distutils shotwell (0.32.6-1) unstable; urgency=medium * New upstream release (Closes: #1064455). - debian/shotwell.install: + Install new shotwell-authenticator. * debian/copyright: - Add year 2024 to myself. - Refresh for the new release. * debian/control: - Add Build Depend python3-distutils. -- Jeremy Bícha Thu, 18 Apr 2024 06:44:24 -0400 ** Changed in: shotwell (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2061090 Title: [FFe] add libheif as a dependency Status in gnome-control-center package in Ubuntu: Fix Released Status in libgd2 package in Ubuntu: Fix Committed Status in shotwell package in Ubuntu: Fix Released Bug description: This issue depends on libheif update[1] as well as security review for libyuv[2] [Why it is needed] libheif is ready to be included in main. Drop delta which removes libheif as a dependencey. This will enable decoding HEIF files by libgd2. See MIR for more details[3] [Build] PPA: ppa:vpa1977/libheif[4] Testing: - piuparts test [5] - check piuparts log that libheif is installed (passes)[5]. [What can go wrong] libheif might pull in unexpected dependencies. Validate that MIR is completed for libheif dependencies in the scope of[1] testing. [Original Description] libheif is ready to be included in main. Drop delta which removes libheif as a dependencey. This will enable decoding HEIF files by libgd2. See MIR for more details - https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/1827442 This exception should be considered in conjunction with https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/2061089 [1] https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/2061089 [2] https://bugs.launchpad.net/ubuntu/+source/libyuv/+bug/2004516 [3] https://bugs.launchpad.net/ubuntu/+source/libheif/+bug/1827442 [4] https://launchpad.net/~vpa1977/+archive/ubuntu/libheif/+packages [5] https://bugs.launchpad.net/ubuntu/+source/libgd2/+bug/2061090/comments/2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2061090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062162] Re: Update shotwell to 0.32.6
This bug was fixed in the package shotwell - 0.32.6-1ubuntu1 --- shotwell (0.32.6-1ubuntu1) noble; urgency=medium * Merge with Debian (LP: #2062162). Remaining changes: - d/replace_thumbnailer.sh, d/shotwell-common.README.Debian, d/shotwell.examples, d/shotwell.postrm, d/shotwell.README.Debian: + clean out thumbnailer hacks, that's not user friendly and not something we should recommend. * Add Depends: heif-gdk-pixbuf, heif-thumbnailer (LP: #2061090) * Drop Build-Depends: python3-distutils shotwell (0.32.6-1) unstable; urgency=medium * New upstream release (Closes: #1064455). - debian/shotwell.install: + Install new shotwell-authenticator. * debian/copyright: - Add year 2024 to myself. - Refresh for the new release. * debian/control: - Add Build Depend python3-distutils. -- Jeremy Bícha Thu, 18 Apr 2024 06:44:24 -0400 ** Changed in: shotwell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/2062162 Title: Update shotwell to 0.32.6 Status in shotwell package in Ubuntu: Fix Released Bug description: Impact -- Shotwell 0.32.6 is a new bugfix release in the stable 0.32.x series https://gitlab.gnome.org/GNOME/shotwell/-/blob/shotwell-0.32/NEWS https://gitlab.gnome.org/GNOME/shotwell/-/compare/shotwell-0.32.4...shotwell-0.32.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/2062162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062178] Re: Disable location services in gnome-control-center
This bug was fixed in the package gnome-control-center - 1:46.0.1-1ubuntu7 --- gnome-control-center (1:46.0.1-1ubuntu7) noble; urgency=medium * Re-enable Location Services for now after more conversation -- Jeremy Bícha Thu, 18 Apr 2024 12:54:43 -0400 ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2062178 Title: Disable location services in gnome-control-center Status in gnome-control-center: New Status in Release Notes for Ubuntu: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center package in Debian: New Bug description: Impact -- Mozilla Location Services will be closed to all third parties (including Ubuntu, GNOME, KDE, etc.) on June 12, 2024. Unfortunately, there does not appear to be any suitable replacement for our typical desktop and laptop users. (Mobile devices like phones may have GPS that could be used but those devices would only rarely be using Ubuntu and gnome-control-center.) To avoid later UI changes and disruption only a few months from now, the Ubuntu Desktop team would prefer to disable location services before Ubuntu 24.04 LTS is released. Details --- Specifically, this hides - Privacy & Security > Location - Date & Time > Automatic Timezone - Displays > Night Light > Schedule > Sunrise to Sunset + This last one wasn't done yet, but I expect it for gnome-control-center 46.1 which will be an SRU https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3014 Other Info -- https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2959 gnome-control-center 46.1 to be released in a few days will also disable Location Services by default but with a build-time option for distros who have different deadlines and user profiles. If an alternative location provider is found that works well enough for our users, we intend to re-enable this feature with a Stable Release Update if possible. Because of this issue, Ubuntu has disabled the Location page in gnome- initial-setup for 24.04 LTS already. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2062178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054132] Re: when have splash parameter in cmdline, desktop remain with black screen
[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.] ** Changed in: plymouth (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2054132 Title: when have splash parameter in cmdline, desktop remain with black screen Status in plymouth package in Ubuntu: Expired Bug description: Hello, I installed today Ubuntu Studio, Ubuntu Official and Ubuntu Unity - 24.04. And i notice behaviour regarding plymouth and splash parameter. When have splash parameter in cmdline, desktop remain with black screen forever. For workaround, i remove "splash" parameter from cmdline. System: CPU: 11th Gen Intel(R) Core(TM) i7-1185GRE @ 2.80GHz OS: 24.04 (Noble Numbat) VGA: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) Firmware: 20240202.git36777504-0ubuntu1 00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) (prog-if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] Flags: bus master, fast devsel, latency 0, IRQ 161 Memory at 60 (64-bit, non-prefetchable) [size=16M] Memory at 40 (64-bit, prefetchable) [size=256M] I/O ports at 3000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: [40] Vendor Specific Information: Len=0c Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Capabilities: [320] Single Root I/O Virtualization (SR-IOV) Kernel driver in use: i915 Kernel modules: i915, xe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2054132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059412] Re: SyntaxWarning: invalid escape sequence '\.'
This bug was fixed in the package software-properties - 0.99.48
---
software-properties (0.99.48) noble; urgency=medium
* Fix Python's warning of invalid escape sequence (LP: #2059412).
* Make pressing enter on close button of out-of-date cache dialog trigger
the close button, not the reload button (LP: #2061978).
* Limit the comments in 'other software' tab to a single line (LP: #2060915).
* apt-add-repository --list now displays deb822 sources (LP: #2060331).
-- Nathan Pratta Teodosio Thu, 18 Apr
2024 09:17:51 +0200
** Changed in: software-properties (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/2059412
Title:
SyntaxWarning: invalid escape sequence '\.'
Status in software-properties package in Ubuntu:
Fix Released
Bug description:
Installing software-properties gives
--->
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197:
SyntaxWarning: invalid escape sequence '\.'
elif
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
uri) == None:
<---
Marked as "wishlist" importance because Python still passes that to
re.match as '\.' instead of '.', so the behavior is correct, as can be
confirmed with
--->
% python3 -c 'print("\.")'
:1: SyntaxWarning: invalid escape sequence '\.'
\.
<---
In a future Python version they will be eventually a SyntaxError[1].
[1] https://docs.python.org/3/reference/lexical_analysis.html#escape-
sequences
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059412/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060915] Re: Comments in source files flood "other software"
This bug was fixed in the package software-properties - 0.99.48 --- software-properties (0.99.48) noble; urgency=medium * Fix Python's warning of invalid escape sequence (LP: #2059412). * Make pressing enter on close button of out-of-date cache dialog trigger the close button, not the reload button (LP: #2061978). * Limit the comments in 'other software' tab to a single line (LP: #2060915). * apt-add-repository --list now displays deb822 sources (LP: #2060331). -- Nathan Pratta Teodosio Thu, 18 Apr 2024 09:17:51 +0200 ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2060915 Title: Comments in source files flood "other software" Status in software-properties package in Ubuntu: Fix Released Bug description: Reproduction case: Add the attached source file to /etc/apt/sources.list.d/. You don't need to 'apt update' for this test. Open software-properties-gtk. Issue: All the comments at the top of the file are displayed, flooding the interface. Limiting the number of comment lines displayed and only displaying the full comments in a tool tip (GTK.Tree has a couple of set_tooltip functions) may result in a better user interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060331] Re: add-apt-repository --list not returning any deb822 repositories
This bug was fixed in the package software-properties - 0.99.48 --- software-properties (0.99.48) noble; urgency=medium * Fix Python's warning of invalid escape sequence (LP: #2059412). * Make pressing enter on close button of out-of-date cache dialog trigger the close button, not the reload button (LP: #2061978). * Limit the comments in 'other software' tab to a single line (LP: #2060915). * apt-add-repository --list now displays deb822 sources (LP: #2060331). -- Nathan Pratta Teodosio Thu, 18 Apr 2024 09:17:51 +0200 ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2060331 Title: add-apt-repository --list not returning any deb822 repositories Status in software-properties package in Ubuntu: Fix Released Bug description: Recreating the following bug report (#2052851) with a new title per Jeremy Bícha's (jbicha) request: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2052851 --- On Ubuntu 23.10: * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061978] Re: Pressing enter on close button of out-of-date cache dialog still triggers the reload button
This bug was fixed in the package software-properties - 0.99.48 --- software-properties (0.99.48) noble; urgency=medium * Fix Python's warning of invalid escape sequence (LP: #2059412). * Make pressing enter on close button of out-of-date cache dialog trigger the close button, not the reload button (LP: #2061978). * Limit the comments in 'other software' tab to a single line (LP: #2060915). * apt-add-repository --list now displays deb822 sources (LP: #2060331). -- Nathan Pratta Teodosio Thu, 18 Apr 2024 09:17:51 +0200 ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061978 Title: Pressing enter on close button of out-of-date cache dialog still triggers the reload button Status in software-properties package in Ubuntu: Fix Released Bug description: Start software-properties-gtk, make any change in the sources configuration, e.g. by just toggling universe check button, enter your password and click close. A dialog appears saying that > To install software and updates from newly added or changed sources, you have to reload the information about available software. with a reload and a close button. Press the right arrow key and close will be selected in the interface, evidenced by a faint border around that button. Press the enter key. - Expected: The close button becomes dark for a brief moment, indicating that it has been pressed, and the program exits immediately. - Observed: The reload button becomes dark for a brief moment, indicating that it has been pressed, and the program starts updating the cache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061978/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056458] Re: upgrade to thunderbird snap, missing snapd depdency
This bug was fixed in the package thunderbird - 2:1snap1-0ubuntu3 --- thunderbird (2:1snap1-0ubuntu3) noble; urgency=medium * debian/control: - Pre-Depends on snapd since the preinst script is using it (lp: #2056458) -- Sebastien Bacher Thu, 18 Apr 2024 16:47:38 +0200 ** Changed in: thunderbird (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056458 Title: upgrade to thunderbird snap, missing snapd depdency Status in thunderbird package in Ubuntu: Fix Released Bug description: latest upgrade on noble replaces thunderbird with snap version. This package does not provide snapd dependency. Simple dist-upgrade on installations (lxqt minimal or server installations) not having snapd installed at all breaking thunderbird because of missing snapd. There is another problem with the missing snapd depdency: the package could not be blocked via pin priority on snapd (when i want use package with the same name from anothe ppa). In general the snapd thunderbird is big crap (cursor theme not working, much slower, x11 ssh forwarding issues etc). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062169] Re: Update gnome-settings-daemon to 46.0
This bug was fixed in the package gnome-settings-daemon - 46.0-1ubuntu1 --- gnome-settings-daemon (46.0-1ubuntu1) noble; urgency=medium * Merge with Debian (LP: #2062169). Remaining changes: + debian/control: - Build-depend on accountsservice + debian/patches/ubuntu: - keyboard-sync-input-sources-to-accountsservice.patch - keyboard-Use-ibus-sources-from-locale.patch - lid-close-suspend-support.patch - media-keys-correct-logout-action.patch - media-keys-restore-terminal-keyboard-shortcut-schema.patch - print-notifications-suppress-printer-may-not-be-connected.patch - teach-gsd-about-the-gnome-calculator-snap-.desktop-name.patch + debian/gnome-settings-daemon.install: - Install apport hook gnome-settings-daemon (46.0-1) unstable; urgency=medium [ Jeremy Bícha ] * New upstream release [ Michael Biebl ] * Build-depend on systemd-dev instead of systemd (Closes: #1060576) -- Jeremy Bícha Thu, 18 Apr 2024 06:59:35 -0400 ** Changed in: gnome-settings-daemon (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2062169 Title: Update gnome-settings-daemon to 46.0 Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: Impact -- gnome-settings-daemon is currently at 46 Beta. We should update it to 46.0 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/blob/46.0/NEWS https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/compare/46.beta...46.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2062169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062388] Re: Date/calendar menu border radius is too big and not consistent with quicksettings
This bug was fixed in the package yaru-theme - 24.04.2-0ubuntu1 --- yaru-theme (24.04.2-0ubuntu1) noble; urgency=medium * calendar: Use the same border radius we use for quicksettings (LP: #2062388) * gnome-shell/dock: Tune the icon selection colors (LP: #2061729) * gnome-shell: Use our dash color as the system overlay bg color (LP: #2062121) -- Marco Trevisan (Treviño) Thu, 18 Apr 2024 19:06:05 +0200 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2062388 Title: Date/calendar menu border radius is too big and not consistent with quicksettings Status in yaru-theme package in Ubuntu: Fix Released Bug description: As visible in https://i.imgur.com/sdzlLai.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2062388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062121] Re: Too many grey rectangles in overview search results with Yaru
This bug was fixed in the package yaru-theme - 24.04.2-0ubuntu1 --- yaru-theme (24.04.2-0ubuntu1) noble; urgency=medium * calendar: Use the same border radius we use for quicksettings (LP: #2062388) * gnome-shell/dock: Tune the icon selection colors (LP: #2061729) * gnome-shell: Use our dash color as the system overlay bg color (LP: #2062121) -- Marco Trevisan (Treviño) Thu, 18 Apr 2024 19:06:05 +0200 ** Changed in: yaru-theme (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2062121 Title: Too many grey rectangles in overview search results with Yaru Status in yaru-theme package in Ubuntu: Fix Released Bug description: Too many grey rectangles in overview search results with Yaru. See also bug 2061985 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2062121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062165] Re: Update gnome-calculator to 46.0
This bug was fixed in the package gnome-calculator - 1:46.0-1ubuntu1 --- gnome-calculator (1:46.0-1ubuntu1) noble; urgency=medium * Merge with Debian (LP: #2062165), remaining change: - Add ubuntu/search-provider-Cancel-operations-on-XUbuntuCancel.patch: + Use XUbuntuCancel with GNOME Shell search provider to stop expensive processes that might lead to an unresponsive process gnome-calculator (1:46.0-1) unstable; urgency=medium * New upstream release * Update Homepage -- Jeremy Bícha Thu, 18 Apr 2024 06:50:45 -0400 ** Changed in: gnome-calculator (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/2062165 Title: Update gnome-calculator to 46.0 Status in gnome-calculator package in Ubuntu: Fix Released Bug description: Impact -- gnome-calculator is at 46 Beta. We should update it to 46.0 https://gitlab.gnome.org/GNOME/gnome- calculator/-/compare/46.beta...46.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/2062165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039374] Re: xbrlapi causes long delay in GUI login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: brltty (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/2039374 Title: xbrlapi causes long delay in GUI login Status in brltty package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS xbrlapi 6.4-4ubuntu3 After logging in to the GUI, there is a delay of over 2 minutes before the desktop environment loads (screen will be black with a mouse cursor) This is caused by /etc/X11/Xsession.d/90xbrlapi The script runs xbrlapi, which hangs for 2 minutes or so, presumably because it is trying to connect to a BrlAPI server that doesn't exist on my machine. I guess this packages was installed by orca, because I did not directly install it myself and I don't need it. Did not happen before 22.04 Others have this issue: https://askubuntu.com/questions/1448501/ubuntu-22-04-1-lts-very-long-x-session-login-due-to-90xbrlapi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/2039374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062387] [NEW] cheese stops working when video record button is pressed
You have been subscribed to a public bug: Ubuntu 22.4.4 , Webcam Logitech C279 HD, cheese 44 installed by snap The camera works and pictures can be taken but as soon as Video button is pressed Cheese crashes, probably due to Audio? cheese Gtk-Message: 17:12:58.813: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. (cheese:31586): Gtk-WARNING **: 17:12:58.880: GTK+ module /snap/cheese/40/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Gtk-Message: 17:12:58.880: Failed to load module "canberra-gtk-module" (cheese:31586): Gtk-WARNING **: 17:12:58.882: GTK+ module /snap/cheese/40/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Gtk-Message: 17:12:58.882: Failed to load module "canberra-gtk-module" (cheese:31586): cheese-WARNING **: 17:12:59.963: Can't find vp8enc preset: "Profile Realtime", using alternate preset: "Cheese Realtime". If you see this, make a bug report! (cheese:31586): GStreamer-WARNING **: 17:12:59.963: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): GStreamer-WARNING **: 17:12:59.963: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): GStreamer-WARNING **: 17:12:59.963: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): GStreamer-WARNING **: 17:12:59.986: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): GStreamer-WARNING **: 17:12:59.986: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): GStreamer-WARNING **: 17:12:59.986: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): cheese-WARNING **: 17:13:03.425: Failed to connect stream: Access denied: ../ext/pulse/pulsesrc.c(1622): gst_pulsesrc_prepare (): /GstCameraBin:camerabin/GstAutoAudioSrc:audiosrc/GstPulseSrc:audiosrc- actual-src-puls (cheese:31586): cheese-WARNING **: 17:13:03.426: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstAutoAudioSrc:audiosrc/GstPulseSrc:audiosrc-actual-src-puls: streaming stopped, reason not-negotiated (-4) ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- cheese stops working when video record button is pressed https://bugs.launchpad.net/bugs/2062387 You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991976] Re: the application uses too much CPU, and at the end of the first game, usage goes to 100%
This bug was fixed in the package gnome-mahjongg - 1:3.40.1-1 --- gnome-mahjongg (1:3.40.1-1) unstable; urgency=medium * New upstream release (LP: #2062038) * Drop all patches: applied in new release -- Jeremy Bícha Wed, 17 Apr 2024 13:26:47 -0400 ** Changed in: gnome-mahjongg (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/1991976 Title: the application uses too much CPU, and at the end of the first game, usage goes to 100% Status in gnome-mahjongg package in Ubuntu: Fix Released Bug description: Environment: The OS is Xubuntu 22.04.1. The kernel is Linux 5.15.0-48-generic. The architecture is 64-bit. The machine is Lenovo ThinkPad X1 Carbon 7th generation. I'm using the snap version of the application. Command "gnome-mahjongg -v" yields "gnome-mahjongg 3.38.0". The launch command is "env BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/gnome- mahjongg_gnome-mahjongg.desktop /snap/bin/gnome-mahjongg". After startup, the application uses a lot of CPU; I've seen command top report over 30% usage. When the first game is finished, the usage goes to 100%. This makes application unresponsive, and I have to kill it via the command line or using command xkill. See the screenshot. The application has started to behave only recently, probably after the update to this version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/1991976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062038] Re: Update gnome-mahjongg to 3.40.1
This bug was fixed in the package gnome-mahjongg - 1:3.40.1-1 --- gnome-mahjongg (1:3.40.1-1) unstable; urgency=medium * New upstream release (LP: #2062038) * Drop all patches: applied in new release -- Jeremy Bícha Wed, 17 Apr 2024 13:26:47 -0400 ** Changed in: gnome-mahjongg (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/2062038 Title: Update gnome-mahjongg to 3.40.1 Status in gnome-mahjongg package in Ubuntu: Fix Released Bug description: gnome-mahjongg 3.40.1 includes several important bugfixes and almost a year of translation updates. gnome-mahjopngg is included by default in some Ubuntu desktop flavors. https://gitlab.gnome.org/GNOME/gnome-mahjongg/-/blob/3.40.1/NEWS https://gitlab.gnome.org/GNOME/gnome- mahjongg/-/compare/3.40.0...3.40.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/2062038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
