[Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
Thanks for the clarification! I'm running 6.5.0-21-generic #21~22.04.1 now. I'll report if the problem occurs again (in my usage it happened every one or two days). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055124] [NEW] WiFi adapter cannot get IP configuration from Netgear orbi RBR20
Public bug reported: Since a recent Ubuntu update (~6 weeks ago), my laptop cannot connect anymore to my Netgear Orbi RBR20 WiFi access point. The wifi connection is still working fine with my Android smartphone set as a WiFi access point. My other devices can connect successfully to the Orbi RBR20: printers, smartphones, TV, tablets, desktop, Sonos, Netatmo... Expected: - Get an IP address from the Netgear Orbi RBR20. Happened instead: - No IP address obtained, stuck with no WiFi connectivity. ThinkPad X13 Gen2 with Ubuntu 22.04.4 LTS: -- fred@ThinkPad:~$ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy Mediatek WiFi adapter: -- *-network description: Interface réseau sans fil produit: MT7921 802.11ax PCI Express Wireless Network Adapter fabricant: MEDIATEK Corp. identifiant matériel: 0 information bus: pci@:03:00.0 nom logique: wlp3s0 nom logique: /dev/fb0 version: 00 numéro de série: 74:97:79:8a:36:e7 bits: 64 bits horloge: 33MHz fonctionnalités: pciexpress msi pm bus_master cap_list ethernet physical wireless fb configuration : broadcast=yes depth=32 driver=mt7921e driverversion=6.5.0-15-generic firmware=01-20220209150915 latency=0 link=yes mode=1920x1200 multicast=yes visual=truecolor wireless=IEEE 802.11 xres=1920 yres=1200 ressources : mémoireE/S:40-3f mémoireE/S:40-3f mémoireE/S:40-3f irq:87 mémoire:47020-4702f mémoire:47030-470303fff mémoire:470304000-470304fff No power saving: [connection] wifi.powersave = 2 Cannot obtain IP configuration: --- DEVICE TYPE STATE CONNECTION wlp3s0 wifi connexion (obtention de la configuration IP) ORBIchamprond Device association looks OK: [241460.865152] wlp3s0: authenticate with c2:a5:11:2f:00:c1 [241460.883343] wlp3s0: send auth to c2:a5:11:2f:00:c1 (try 1/3) [241460.886001] wlp3s0: authenticated [241460.887489] wlp3s0: associate with c2:a5:11:2f:00:c1 (try 1/3) [241460.991496] wlp3s0: associate with c2:a5:11:2f:00:c1 (try 2/3) [241461.016131] wlp3s0: RX AssocResp from c2:a5:11:2f:00:c1 (capab=0x1511 status=0 aid=1) [241461.046179] wlp3s0: associated RBR20 firmware version: v2.7.3.22 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: wifi ** Tags added: wifi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055124 Title: WiFi adapter cannot get IP configuration from Netgear orbi RBR20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2055124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044973] Re: ubuntu-drivers install the wrong version of Nvidia driver on some machines
@Francis I've confirmed that the DUT has already used the latest ubuntu-drivers from proposed. Setting up ubuntu-drivers-common (1:0.9.0~0.20.04.8) ... But it doesn't seem to solve the issue. Please check following messages. + _run sudo ubuntu-drivers devices + ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ubuntu@10.102.153.239 sudo ubuntu-drivers devices WARNING:root:_pkg_get_support nvidia-driver-525: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-535: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-535-open: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-525-server: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-535-server-open: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-525-open: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-535-server: package has invalid Support PBheader, cannot determine support level == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd2191sv1028sd0949bc03sc00i00 vendor : NVIDIA Corporation model: TU116M [GeForce GTX 1660 Ti Mobile] driver : nvidia-driver-450-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-535 - distro non-free driver : nvidia-driver-535-open - distro non-free driver : nvidia-driver-418-server - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-470 - distro non-free driver : nvidia-driver-535-server-open - distro non-free recommended driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-535-server - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-modules-nvidia-535-server-open-generic : Depends: linux-modules-nvidia-535-server-open-5.4.0-173-generic (= 5.4.0-173.191) but it is not going to be installed E: Unable to correct problems, you have held broken packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044973 Title: ubuntu-drivers install the wrong version of Nvidia driver on some machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2044973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055121] Re: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure B
is this the expected behavior from ubuntu when we do bios reset to default and clear NVRAM ??? ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055121 Title: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055121] Re: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure B
LifeCycle controller logs --- UEFI0074-The Secure Boot policy has been modified since the last time the system was started. Detailed Description: The system BIOS logs this message after detecting a change in Secure Boot policy settings. Such a change may result from user configuration or a system BIOS update. Changes to the following settings trigger this message: 1) Secure Boot (Enable/Disable) 2) Secure Boot Policy (Standard/Custom) 3) Platform Key 4) Key Exchange Keys 5) Authorized Signature Database (db) 6) Forbidden Signature Database (dbx). Recommended Action:Review the Secure Boot policy settings in System Setup > System BIOS > Security Settings page. If policy changes were expected, no action is necessary. Otherwise, modify the Secure Boot policy settings as needed. Dmesg logs -- root@ubuntu:~# dmesg |grep -i secure [0.00] secureboot: Secure boot disabled [0.012309] secureboot: Secure boot disabled [ 10.251237] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0' [ 10.258614] (2017): 242ade75ac4a15e50d50c84b0d45ff3eae707a03' [ 10.266502] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (ESM 2018): 365188c1d374d6b07c3c8f240f8ef722433d6a8b' [ 10.273814] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2019): c0746fd6c5da3ae827864651ad66ae47fe24b3e8' [ 10.280706] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v1): a8d54bbb3825cfb94fa13c9f8a594a195c107b8d' [ 10.288123] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v2): 4cf046892d6fd3c9a5b03f98d845f90851dc6a8c' [ 10.295040] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v3): 100437bb6de6e469b581e61cd66bce3ef4ed53af' [ 10.301685] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (Ubuntu Core 2019): c1d57b8f6b743f23ee41f4f7ee292f06eecadfb9' [ 10.485916] integrity: Loaded X.509 cert 'VMware, Inc.: VMware Secure Boot Signing: 04597f3e1ffb240bba0ff0f05d5eb05f3e15f6d7' [ 10.522527] blacklist: Revoked X.509 cert 'Debian Secure Boot Signer: 00a7468def' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055121 Title: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055121] [NEW] [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure
Private bug reported: Description: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing in dmesg. Version-Release ubuntu 22.04.3, 24.04.4 Steps to Reproduce: 1. BIOS (Reset default and clear NVRAM) 2. install ubuntu 22.04.3 / 24.04.4 3. Post OS installation reboot the system and check LC logs warning messgae will be displayed. 4. Check dmesg for logs like : Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing. Note: This warning and dmesg logs will be showed only when you deafault bios and clear NVRAM. not seen warning message without clearing BIOS NVRAM. Is this the behavaviour is expected when install os after clearing BIOS NVRAM? ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055121 Title: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054632] Re: ninja command failing for upstream libvirt compilation
** Changed in: ubuntu-power-systems Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054632 Title: ninja command failing for upstream libvirt compilation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2054632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054769] Re: Boot animation and login screen use different display scales
Fix proposed: https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/307 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054769 Title: Boot animation and login screen use different display scales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049904] Re: meson x rustc library ordering issue
** Changed in: meson (Debian) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049904 Title: meson x rustc library ordering issue To manage notifications about this bug go to: https://bugs.launchpad.net/meson/+bug/2049904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055099] Re: Got GIMP crash debug
Most likely this crash was caused by using new glib at runtime at local testing "using GLib version 2.79.2 (compiled against version 2.78.0)". and doesn't occur with packaged version, so that please close this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055099 Title: Got GIMP crash debug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2055099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
Relevant upstream issue https://github.com/fail2ban/fail2ban/issues/3487 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
So whilst in Ubuntu we do have python-pyasyncore which provides asyncore, we don't have asynchat so this might need to be packaged separately OR vendored into fail2ban -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
asynchat was removed in python 3.12, which just became the default python3 in 24.04 ** Information type changed from Private Security to Public ** Bug watch added: github.com/fail2ban/fail2ban/issues #3487 https://github.com/fail2ban/fail2ban/issues/3487 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054301] Re: [worker/event] Some child processes aren't killed on reload (graceful), being stuck in state "Sending Reply", leaving old logfiles open, disk fills up, server stops responding after
Hi Mitchell, the application - for now - needs PHP 7.4 but the dev says it should be possible to make it compatible with 8.1. Will report back when it's running with 8.1 from the official Ubuntu jammy repositories. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054301 Title: [worker/event] Some child processes aren't killed on reload (graceful), being stuck in state "Sending Reply", leaving old logfiles open, disk fills up, server stops responding after some days, DoS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2054301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051838] Re: /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too many files to send
Also have this issue (100% cpu usage by /usr/sbin/rsyslogd) with Firefox in Sway on Ubuntu 22.04. So far I've only noticed this after reloading the sway config (`swaymsg reload` or Mod+Shift+c). Fabien (afabien) wrote: > To avoid having disk full problems, I used the following workaround: > > I created a file /etc/rsyslog.d/10-no-gdm-wayland.conf > Containing the following lines: > :msg, contains, "Error: WaylandMessage::Write() too many files to send" ~ > :msg, contains, " :" ~ > > And then restarted rsyslog (as root): systemctl restart rsyslog.service This workaround didn't work for me, even after replacing the `~` with `stop`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051838 Title: /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too many files to send To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055116] [NEW] please sync qpid-proton-j-extensions 1.2.4-2 from debian unstable
Public bug reported: The fix for LP: #2054236 was integrated in debian in 1.2.4-2. This is no more delta remaining. ** Affects: qpid-proton-j-extensions (Ubuntu) Importance: Undecided Status: New ** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/qpid-proton-j-extensions/+git/qpid-proton-j-extensions/+merge/461325 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055116 Title: please sync qpid-proton-j-extensions 1.2.4-2 from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpid-proton-j-extensions/+bug/2055116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
** Description changed: 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, I do not remember] - and the system cannot recover. Call the system administrator” message - after a red FAILED in the terminal. The system administrator is myself, + 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 our 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 + 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= + 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 + 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 + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.45.90 connected started full enabled enabled enabled missing enabled ** Tags added: network-manager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055007] Re: Software & Updates simply does not start, Update Manager crashes when I try to check out the checkbox of an update.
The second problem has been solved: now, Update Manager is working perfectly. ** Changed in: update-manager (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055007 Title: Software & Updates simply does not start, Update Manager crashes when I try to check out the checkbox of an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2055007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055007] Re: Software & Updates simply does not start, Update Manager crashes when I try to check out the checkbox of an update.
So it can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055007 Title: Software & Updates simply does not start, Update Manager crashes when I try to check out the checkbox of an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2055007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055007] Re: Software & Updates simply does not start, Update Manager crashes when I try to check out the checkbox of an update.
I was able to fix the first-mentioned problem by changing /usr/lib/python3/dist-packages/aptsources/sourceslist.py (I attached the fixed version as a patch to this message). It disabled .sources extension to the handled files, causing that problem. ** Attachment added: "sourceslist.py" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2055007/+attachment/5749669/+files/sourceslist.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055007 Title: Software & Updates simply does not start, Update Manager crashes when I try to check out the checkbox of an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2055007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055115] Re: please sync libthread-pool 4.0.0-2 from debian/unstable
** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/libthread-pool/+git/libthread-pool/+merge/461323 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055115 Title: please sync libthread-pool 4.0.0-2 from debian/unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libthread-pool/+bug/2055115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055115] [NEW] please sync libthread-pool 4.0.0-2 from debian/unstable
Public bug reported: version 4.0.0-2~exp1 contains fix for LP: #2009537 which is the only delta present. Current debian version: 4.0.0-2. ** Affects: libthread-pool (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055115 Title: please sync libthread-pool 4.0.0-2 from debian/unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libthread-pool/+bug/2055115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1080.76)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1080.76) for focal have finished running. The following regressions have been reported in tests triggered by the package: acpi-call/unknown (arm64) ddcci-driver-linux/unknown (arm64) dm-writeboost/unknown (arm64) dpdk/unknown (arm64) fwts/unknown (arm64) glibc/unknown (arm64) gost-crypto/unknown (arm64) iptables-netflow/unknown (arm64) langford/unknown (arm64) lttng-modules/unknown (arm64) wireguard-linux-compat/1.0.20201112-1~20.04.1 (arm64) zfs-linux/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054991] Re: please merge sparse 0.6.4-4 from debian/unstable
** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/sparse/+git/sparse/+merge/461321 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054991 Title: please merge sparse 0.6.4-4 from debian/unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sparse/+bug/2054991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055113] Re: sparse 0.6.4-4 fails to build from source in noble
sparse build log ** Attachment added: "sparse-ftbfs.log.gz" https://bugs.launchpad.net/ubuntu/+source/sparse/+bug/2055113/+attachment/5749665/+files/sparse-ftbfs.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055113 Title: sparse 0.6.4-4 fails to build from source in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sparse/+bug/2055113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055113] [NEW] sparse 0.6.4-4 fails to build from source in noble
Public bug reported: A number of tests fail with the coredump caused by the buffer overflow: TESTvla-sizeof var X var (vla-sizeof4.c) Using command : test-linearize -Wvla $file Expecting exit value: 0 error: actual error text does not match expected error text. error: see vla-sizeof4.c.error.* for further investigation. --- vla-sizeof4.c.error.expected2024-02-27 12:26:33.627119178 +1300 +++ vla-sizeof4.c.error.got 2024-02-27 12:26:33.627119178 +1300 @@ -1,2 +1,4 @@ vla-sizeof4.c:6:16: warning: Variable length array is used. vla-sizeof4.c:6:13: warning: Variable length array is used. +*** buffer overflow detected ***: terminated +Aborted (core dumped) See the attached log ** Affects: sparse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055113 Title: sparse 0.6.4-4 fails to build from source in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sparse/+bug/2055113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055006] Re: Crash
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 ** This bug has been marked a duplicate of bug 1861609 Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055006 Title: Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2055006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110
Changes have been landed under tag 20230919.git3672ccab-0ubuntu2.6, and verified in 20230919.git3672ccab-0ubuntu2.8, which is lately respined as 20230919.git3672ccab-0ubuntu2.9 with no additional change made. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048853 Title: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2048853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055037] Re: My screen radomly starts flickering
By the way, there's a typo in: 1915.enable_psr=0 which would usually be: i915.enable_psr=0 but even that won't help here because you have AMD graphics, not Intel. The equivalent workaround for AMD graphics is: amdgpu.dcdebugmask=0x10 so please try that. ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055037 Title: My screen radomly starts flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2055037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055037] Re: My screen radomly starts flickering
There are lots of amdgpu errors in your system log, so let's start there. ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055037 Title: My screen radomly starts flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2055037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052640] Re: New NVIDIA release 470.239.06
I have done my typical CUDA based testing with this package using the generic, nvidia and gcp kernels using bionic, focal, jammy and mantic (amd64 only so far). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052640 Title: New NVIDIA release 470.239.06 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/2052640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055032] Re: SEG/11 in Wayland _st_theme_get_matched_properties()
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Tags added: jammy ** Description changed: Crashed after unlocking session from being away for a couple days. - Crash report ID is c81ddc34-d487-11ee-ba77-fa163e171f02 + Crash report ID is https://errors.ubuntu.com/oops/c81ddc34-d487-11ee- + ba77-fa163e171f02 ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055032 Title: SEG/11 in Wayland _st_theme_get_matched_properties() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2055032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054571] Re: New NVIDIA release 535.161.07
I have done my typical CUDA based testing with this package using the generic, nvidia and gcp kernels using bionic, focal, jammy and mantic (amd64 only so far). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054571 Title: New NVIDIA release 535.161.07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2054571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051965] Re: QEmu with TCG acceleration (without KVM) causes kernel panics with guest kernels >=6.3
Performing the verification for Mantic. Verifying that we're using the QEMU package from mantic-proposed: $ apt policy qemu-system-x86 qemu-system-x86: Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.3 Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.3 Version table: *** 1:8.0.4+dfsg-1ubuntu3.23.10.3 100 100 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:8.0.4+dfsg-1ubuntu3.23.10.2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages 1:8.0.4+dfsg-1ubuntu3 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu mantic/main amd64 Packages Running the tests in a loop and verifying that the guest Linux kernel doesn't panic: $ sudo INPUT_BUILD_SKIP_PACKETDRILL=1 INPUT_BUILD_SKIP_PERF=1 INPUT_NO_BLOCK=1 $HOME/repr/entrypoint.sh auto-normal ... == Summary == fatal: No names found, cannot describe anything. Ref: Mode: normal Extra kconfig: / All tests: ok 1 test: selftest_mptcp_connect KVM Validation: Success! ✅ This concludes the verification for Mantic. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051965 Title: QEmu with TCG acceleration (without KVM) causes kernel panics with guest kernels >=6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2051965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054866] Re: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to install/upgrade: installed linux-headers-6.5.0-21-generic package post-installation script subprocess returned error exit
Find the problem, it isn't a broken/unsupported DKMS module for my case. The system's default gcc/g++ version is 13. While installing CUDA 11.8, I used update-alternatives to change the gcc/g++ version to 11. Switch back to gcc/g++ 13 solved this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054866 Title: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to install/upgrade: installed linux-headers-6.5.0-21-generic package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051921] Re: Update WiFi/BT firmware as per MediaTek's request
Verified packages on noble and mantic/jammy-proposed. 1. noble: mt7663 WiFi/BT firmware are removed. 2. noble/mantic/jammy: a. SCAN: Pass b. connect to AP: Pass c. ping test: Pass 3. checksum: Pass $ md5sum /lib/firmware/mediatek/WIFI_* 0a4d833efe94a56c502de8a38405d8fe /lib/firmware/mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin 8d0a4f6dc2d01a8b442ae0b8d76d9122 /lib/firmware/mediatek/WIFI_RAM_CODE_MT7961_1.bin --- Board: g700 and g510 ** Tags added: verification-done-jammy verification-done-mantic ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051921 Title: Update WiFi/BT firmware as per MediaTek's request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-mediatek-genio/+bug/2051921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055105] Re: please merge cron 3.0pl1-184 from debian unstable
** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/cron/+git/cron/+merge/461317 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055105 Title: please merge cron 3.0pl1-184 from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/2055105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055105] [NEW] please merge cron 3.0pl1-184 from debian unstable
Public bug reported: tracking bug ** Affects: cron (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055105 Title: please merge cron 3.0pl1-184 from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/2055105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1990856] Autopkgtest regression report (debootstrap/1.0.126+nmu1ubuntu0.7)
All autopkgtests for the newly accepted debootstrap (1.0.126+nmu1ubuntu0.7) for jammy have finished running. The following regressions have been reported in tests triggered by the package: debuerreotype/0.14-1 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#debootstrap [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1990856 Title: Does not consider all versions in Packages files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1990856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054925] Autopkgtest regression report (debootstrap/1.0.126+nmu1ubuntu0.7)
All autopkgtests for the newly accepted debootstrap (1.0.126+nmu1ubuntu0.7) for jammy have finished running. The following regressions have been reported in tests triggered by the package: debuerreotype/0.14-1 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#debootstrap [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2030684] Re: tzname[1] empty after tzset() with env TZ="UTC"
** Also affects: php8.3 (Ubuntu) Importance: Undecided Status: New ** Changed in: php8.3 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2030684 Title: tzname[1] empty after tzset() with env TZ="UTC" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/django-mailman3/+bug/2030684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054841] Re: Please remove and block php8.2 from sync'ing in noble
Thanks, Steve! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054841 Title: Please remove and block php8.2 from sync'ing in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php8.2/+bug/2054841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055100] Re: please merge nfs-utils 2.6.4-3 from debian unstable
** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/461312 ** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/461313 ** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/461314 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055100 Title: please merge nfs-utils 2.6.4-3 from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2055100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.4.0.1119.112)
All autopkgtests for the newly accepted linux-meta-oracle (5.4.0.1119.112) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.23 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oracle [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861609] Re: Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper
** Tags added: bionic jammy mantic noble ** Summary changed: - Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper + Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] ** Description changed: Xorg crashed with assertion failure (usually in a VM): privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. - and call stack comes from DRIMoveBuffersHelper - WORKAROUND Select 'Ubuntu on Wayland' on the login screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861609 Title: Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1861609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 ** This bug has been marked a duplicate of bug 1861609 Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055006] Re: Crash
If 'ubuntu-bug' fails then try using 'apport-cli' to handle crash files instead. The crash report you linked to is bug 1861609. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055006 Title: Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2055006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055103] [NEW] /usr/lib/xorg/Xorg:Xorg: ../../../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.1-3ubuntu2.1, the problem page at https://errors.ubuntu.com/problem/e0bf19ca61a90032292ab167b4009523a9684945 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic jammy kinetic kylin-18.04 kylin-22.04 kylin-23.04 lunar mantic noble zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055103 Title: /usr/lib/xorg/Xorg:Xorg: ../../../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2055103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055103] Re: /usr/lib/xorg/Xorg:Xorg: ../../../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 ** This bug has been marked a duplicate of bug 1861609 Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055103 Title: /usr/lib/xorg/Xorg:Xorg: ../../../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2055103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054121] Re: Random Freezing
OK thanks. It looks like whatever caused the problem didn't make it into the system log before the reboot. To fix that we add an extra step: 1. Note the exact time and date of the freeze. 2. Press 'Alt + PrtSc + S' a couple of times. Or just waiting 30 seconds might also work. 3. Reboot. 4. Run: journalctl -b-1 > prevboot.txt 5. Attach the resulting text file here along with a note telling us the exact time and date of the freeze. 6. Check /var/crash for crash files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054121 Title: Random Freezing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051045] Re: Freeze in kernel 6.5 (but 6.2 works)
I suggest you keep using older kernels for the time being. Please also subscribe to bug 2028165 because that does seem to be happening on your system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051045 Title: Freeze in kernel 6.5 (but 6.2 works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055042] Re: Merge unbound 1.19.1-1 from debian
This bug was fixed in the package unbound - 1.19.1-1ubuntu1 --- unbound (1.19.1-1ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2055042). Remaining changes: - Don't build with hiredis on i386. hiredis and redis are not built on i386 and require bootstrapping due to circular build-dependencies; simpler to just disable this in the i386 unbound server binary (that no one will ever use). -- Andreas Hasenack Mon, 26 Feb 2024 10:03:33 -0300 ** Changed in: unbound (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055042 Title: Merge unbound 1.19.1-1 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2055042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055100] [NEW] please merge nfs-utils 2.6.4-3 from debian unstable
Public bug reported: tracking bug ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055100 Title: please merge nfs-utils 2.6.4-3 from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2055100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939138] Re: Fwupd missing uefi plugin for riscv64
Fwupd 1.9.14 is built with uefi capsules plugin for this architecture. ** Changed in: fwupd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939138 Title: Fwupd missing uefi plugin for riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1939138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052981] Re: classmate: FTBFS with default Java 21
** Changed in: classmate (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052981 Title: classmate: FTBFS with default Java 21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/classmate/+bug/2052981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055074] Re: Merge sssd from Debian unstable for noble
This bug was fixed in the package sssd - 2.9.4-1ubuntu1
---
sssd (2.9.4-1ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2055074). Remaining changes:
- d/control: Drop libgdm-dev Build-Depend on i386.
- d/control: Don't build sssd-tools on i386, now uninstallable due
to added python3-{click,systemd} dependencies.
- d/apparmor-profile: Add some entries to apparmor-profile file
to get rid of the extraneous ALLOWED messages visible in the
/var/log/syslog. (LP #1999190)
* Drop changes:
- d/t/control: Remove "needs-sudo" restriction from smartcard tests,
replace with "needs-root". This is needed because Ubuntu's
autopkgtest infrastructure doesn't support "needs-sudo".
- d/t/sssd-smart-card-pam-auth-configs-tester.sh,
d/t/sssd-softhism2-certificates-tests.sh: Add code to handle
${AUTOPKGTEST_NORMAL_USER}.
[ Incorporated by Debian. ]
-- Sergio Durigan Junior Mon, 26 Feb
2024 14:08:42 -0500
** Changed in: sssd (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055074
Title:
Merge sssd from Debian unstable for noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2055074/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054628] Re: please merge munin 2.0.75-1 from debian/unstable
This bug was fixed in the package munin - 2.0.75-1ubuntu1 --- munin (2.0.75-1ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2054628). Remaining changes: - d/p/munin-node-configure-doc-fix.patch: Remove deprecated argument exitonerror and update some snmp arguments to match their correct naming. - Drop sysvinit autopkgtests, sysvinit is not supported in Ubuntu - Add missing test dependency on net-tools for netstat plugin. - d/Makefile.config: Use java_compat_level provided by java-common to set --release level. * New changes: - d/t/munin-node/02.plugins.t: add conditional postfix plugin to the plugin list test. munin (2.0.75-1) unstable; urgency=medium * new upstream version: - plugins/ipmi_: handle "0.000" as "na" in temperature critical/warning. -- Vladimir Petko Thu, 22 Feb 2024 17:17:06 +1300 ** Changed in: munin (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054628 Title: please merge munin 2.0.75-1 from debian/unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/2054628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055078] Re: Please merge (2.5.2-2) from Debian
This bug was fixed in the package php-symfony-contracts - 2.5.2-2ubuntu1 --- php-symfony-contracts (2.5.2-2ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2055078). Remaining changes: - d/p/fix-build-with-php8.patch: Add patch to fix build and tests with PHP 8. - d/p/bump-php-cache-container.patch: Add patch to bump php-psr-container dependency to make it work w/ the one in archive. - d/control: Tighten BD on php-psr-container. -- Athos Ribeiro Mon, 26 Feb 2024 16:16:44 -0300 ** Changed in: php-symfony-contracts (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055078 Title: Please merge (2.5.2-2) from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-symfony-contracts/+bug/2055078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049217] Re: requestsync fails with ModuleNotFoundError: No module named 'keyring' error
MP to change Depends:python3-launchpadlib to Depends:python3-launchpadlib-desktop in ubuntu-dev-tools: https://code.launchpad.net/~cpete/ubuntu-dev-tools/+git/ubuntu-dev- tools/+merge/461309 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049217 Title: requestsync fails with ModuleNotFoundError: No module named 'keyring' error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-launchpadlib/+bug/2049217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049217] Re: requestsync fails with ModuleNotFoundError: No module named 'keyring' error
** Merge proposal linked: https://code.launchpad.net/~cpete/ubuntu-dev-tools/+git/ubuntu-dev-tools/+merge/461309 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049217 Title: requestsync fails with ModuleNotFoundError: No module named 'keyring' error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-launchpadlib/+bug/2049217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039219] Re: please provide jtreg7 for stable releases (focal, jammy)
This bug was fixed in the package jtreg7 - 7.3.1+1~us2-0ubuntu1~22.04.1 --- jtreg7 (7.3.1+1~us2-0ubuntu1~22.04.1) jammy-security; urgency=medium * Vendor jtreg7 dependencies: apiguardian, hawt-jni, jansi1, jline3, junit4, junit5, libhamcrest-java, opentest4j, opentest4j-reporting, picocli, testng7, univocity-parsers to allow backports (LP: #2039219). - d/watch: build MUT original tarball. - d/component-scripts: add scripts to build the bundled components. - d/copyright: include bundled components copyrights. * d/control: downgrade debhelper compatibility level to 11 for backports. * d/rules: fix man page generation by using the version option. * Repack original tarball to drop excluded files. * d/t/self-test: use vendored dependencies. * Upload to Ubuntu 22.04.1. -- Vladimir Petko Wed, 14 Feb 2024 18:17:58 +1300 ** Changed in: jtreg7 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039219 Title: please provide jtreg7 for stable releases (focal, jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jtreg7/+bug/2039219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2054865] Re: Package virtualbox-dkms-6.1.50 fails to install
On 2/26/24 00:13, Gianfranco Costamagna wrote: > Which dkms version are you using? > $ dpkg -l |grep dkms > The problem was a mismatch between the gcc used to build the kernel and the injstalled gcc version. The kernel was built with gcc-12. The default Ubuntu 22.04 version is gcc-11. I use the default OS gcc to, hopefully, avoid conflicts such as this. Tom Dean -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054865 Title: Package virtualbox-dkms-6.1.50 fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2054865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2054865] Re: Package virtualbox-dkms-6.1.50 fails to install
On 2/26/24 00:13, Gianfranco Costamagna wrote: > Which dkms version are you using? > $ dpkg -l |grep dkms > > dpkg -l |grep dkms ii dkms 2.8.7-2ubuntu2 all Dynamic Kernel Module Support Framework ii virtualbox-dkms 6.1.50-dfsg-1~ubuntu1.22.04.1 amd64x86 virtualization solution - kernel module sources for dkms -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054865 Title: Package virtualbox-dkms-6.1.50 fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2054865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767902] Re: equivs-build --full ... no upstream tarball found
This was fixed in equivs 2.3.0, first found in Ubuntu 20.10 Groovy Gorilla. --full or --source functions normally on Ubuntu 23.10 and 22.04. This bug still affects Ubuntu 18.04 and Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767902 Title: equivs-build --full ... no upstream tarball found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/equivs/+bug/1767902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054301] Re: [worker/event] Some child processes aren't killed on reload (graceful), being stuck in state "Sending Reply", leaving old logfiles open, disk fills up, server stops responding after
Thanks for the additional info! Is there a reason you need to use ondrej's PHP package? I'd be curious if this could be reproduced using php 8.1.2-1ubuntu2.14 from the Ubuntu archives. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054301 Title: [worker/event] Some child processes aren't killed on reload (graceful), being stuck in state "Sending Reply", leaving old logfiles open, disk fills up, server stops responding after some days, DoS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2054301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887655] Re: unattended-upgrades triggers reboot despite configuration
Also seeing this issue on 20.04. Same behaviour as above (occurence is random and the symptoms and log information is the same). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887655 Title: unattended-upgrades triggers reboot despite configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1887655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055099] [NEW] Got GIMP crash debug
Public bug reported: Hello, got a crash window debug at GIMP exit with "To help us improve GIMP, you can report the bug ..." message There it is % lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 % LANG=C apt-cache policy gimp gimp: Installed: 2.10.34-1ubuntu0.23.10.1 Candidate: 2.10.34-1ubuntu0.23.10.1 Version table: *** 2.10.34-1ubuntu0.23.10.1 990 990 http://archive.ubuntu.com/ubuntu mantic-updates/universe amd64 Packages 990 http://security.ubuntu.com/ubuntu mantic-security/universe amd64 Packages 100 /var/lib/dpkg/status 2.10.34-1 990 990 http://archive.ubuntu.com/ubuntu mantic/universe amd64 Packages ``` GNU Image Manipulation Program version 2.10.34 git-describe: GIMP_2_10_34 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 13.2.0-4ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-13 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-13-XYspKM/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-XYspKM/gcc-13-13.2.0/debian/tmp-gcn/usr --enable-offload-defaulted --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=2 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 13.2.0 (Ubuntu 13.2.0-4ubuntu3) # Libraries # using babl version 0.1.106 (compiled against version 0.1.106) using GEGL version 0.4.44 (compiled against version 0.4.44) using GLib version 2.79.2 (compiled against version 2.78.0) using GdkPixbuf version 2.42.10 (compiled against version 2.42.10) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.51.0 (compiled against version 1.51.0) using Fontconfig version 2.14.2 (compiled against version 2.14.2) using Cairo version 1.18.0 (compiled against version 1.18.0) ``` > fatal error: Помилка адресування Stack trace: ``` # Stack traces obtained from PID 421981 - Thread 421981 # [New LWP 421983] [New LWP 421984] [New LWP 421985] [New LWP 421989] [New LWP 421990] [New LWP 421991] [New LWP 421998] [New LWP 422053] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f0e4831a7dc in __GI___libc_read (nbytes=256, buf=0x7ffd2a975310, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7f0e47a702c0 (LWP 421981) "gimp-2.10"0x7f0e4831a7dc in __GI___libc_read (nbytes=256, buf=0x7ffd2a975310, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7f0e46b756c0 (LWP 421983) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7f0e463746c0 (LWP 421984) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7f0e3db736c0 (LWP 421985) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7f0e3cb716c0 (LWP 421989) "pool-spawner" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7f0e3d3726c0 (LWP 421990) "gmain"0x7f0e4831a20f in __GI___poll (fds=0x56261a60b0a0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 7Thread 0x7f0e44bff6c0 (LWP 421991) "gdbus"0x7f0e4831a20f in __GI___poll (fds=0x7f0e2c000b90, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 8Thread 0x7f0e0a3fc6c0 (LWP 421998) "async"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7f0dfaffd6c0 (LWP 422053) "swap writer" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Thread 9 (Thread 0x7f0dfaffd6c0 (LWP 422053) "swap writer"): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 No
[Bug 2054484] Re: Update the agent to upstream tag 20240213.00
This bug was fixed in the package google-guest-agent - 20240213.00-0ubuntu1 --- google-guest-agent (20240213.00-0ubuntu1) noble; urgency=medium [ Utkarsh Gupta ] * Add a reason to include include-binaries file. [ Chloé 'kajiya' Smith ] * New upstream version, v20240213.00. (LP: #2054484) * d/extra/vendor: Update the vendored dependencies. * d/source/include-binaries: add new file. -- Chloé 'kajiya' Smith Wed, 21 Feb 2024 00:25:47 + ** Changed in: google-guest-agent (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054484 Title: Update the agent to upstream tag 20240213.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2054484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055064] Re: Merge 3.8.2+dfsg-1 from debian unstable
This bug was fixed in the package php-doctrine-dbal - 3.8.2+dfsg-1ubuntu1 --- php-doctrine-dbal (3.8.2+dfsg-1ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2055064). Remaining changes: - d/p/skip-middleware-tests.patch: drop tests incompatible with php-psr-log >= 3. -- Athos Ribeiro Mon, 26 Feb 2024 15:25:28 -0300 ** Changed in: php-doctrine-dbal (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055064 Title: Merge 3.8.2+dfsg-1 from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-doctrine-dbal/+bug/2055064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055069] Re: Please merge 1.2.2-2 from Debian unstable
This bug was fixed in the package php-klogger - 1.2.2-2ubuntu1 --- php-klogger (1.2.2-2ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2055069). Remaining changes: - d/p/0005-psr-logger-compliance.patch: comply with php-psr-log 3. (LP #1967796) -- Athos Ribeiro Mon, 26 Feb 2024 15:58:19 -0300 ** Changed in: php-klogger (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055069 Title: Please merge 1.2.2-2 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-klogger/+bug/2055069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055098] [NEW] Ripgrep zsh autocompletion no longer installs after 14.x upgrade
Public bug reported:
After upgrading to Ripgrep 14, zsh autocompletion is no longer installed
properly
Ripgrep 14 includes /usr/share/zsh/vendor-completions/rg.zsh
Ripgrep 12 includes /usr/share/zsh/vendor-completions/_rg
The 14 one is invalid, I think the function requires the naming scheme
(not certain).
Reproducer:
```
$ docker run -it ubuntu:noble
root@68026c046d27:/# apt update; apt install -y zsh ripgrep
root@68026c046d27:/# zsh
68026c046d27# autoload -Uz compinit; compinit
68026c046d27# for key val in "${(@kv)_comps}"; do
echo "$key -> $val"
done | rg rg
# No completion defined
68026c046d27# mv /usr/share/zsh/vendor-completions/rg.zsh
/usr/share/zsh/vendor-completions/_rg
68026c046d27# autoload -Uz compinit; compinit
68026c046d27# for key val in "${(@kv)_comps}"; do
echo "$key -> $val"
done | rg rg
rg -> _rg
```
This also applies to debian's packaging
** Affects: rust-ripgrep (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055098
Title:
Ripgrep zsh autocompletion no longer installs after 14.x upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-ripgrep/+bug/2055098/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1990856] Autopkgtest regression report (debootstrap/1.0.126+nmu1ubuntu0.6)
All autopkgtests for the newly accepted debootstrap (1.0.126+nmu1ubuntu0.6) for jammy have finished running. The following regressions have been reported in tests triggered by the package: debuerreotype/0.14-1 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#debootstrap [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1990856 Title: Does not consider all versions in Packages files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1990856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."
Also, the various packages here have a similar error message but the error is probably caused by different things. This is a generic error message from init-system-helpers. Now, with that said, I agree init-system-helpers should be more verbose when this error happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003756 Title: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."
netvicious or Dan, do you have the AMI that you used to produce that error with proftpd-core? I also tried reproduction on ami-0dffe9017aa8424a2 in eu-north-1 and was not able to reproduce that failure. I just booted a fresh t3.micro instance with the above AMI, then proceeded to run `apt update -y && apt install -y proftpd`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2003756 Title: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1990856] Autopkgtest regression report (debootstrap/1.0.126+nmu1ubuntu0.6)
All autopkgtests for the newly accepted debootstrap (1.0.126+nmu1ubuntu0.6) for jammy have finished running. The following regressions have been reported in tests triggered by the package: debuerreotype/0.14-1 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#debootstrap [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1990856 Title: Does not consider all versions in Packages files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1990856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054924] Re: color emoji are broken with fontconfig 2.15
The workaround detailed upstream works for me - removing /etc/fonts/conf.d/70-no-bitmaps.conf and re-generating your fonts cache. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054924 Title: color emoji are broken with fontconfig 2.15 To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/2054924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053207] Re: glib requires gobject-introspection >= 1.78.1-13
** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053207 Title: glib requires gobject-introspection >= 1.78.1-13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048788] Re: sbuild autopkgtest just skips the unshare tests
This has been fixed in 0.85.6 via https://salsa.debian.org/debian/sbuild/-/merge_requests/57 ** Changed in: sbuild (Ubuntu) Importance: Undecided => Medium ** Changed in: sbuild (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048788 Title: sbuild autopkgtest just skips the unshare tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/2048788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64
This has been fixed in sbuild 0.85.6 via https://salsa.debian.org/debian/sbuild/-/merge_requests/57 ** Changed in: sbuild (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052295 Title: autopkgtest unshare-qemuwrapper failing on amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918740] Re: sbuild 0.81.2ubuntu4 tests stuck
This has been fixed between then and 0.85.6. ** Changed in: sbuild (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918740 Title: sbuild 0.81.2ubuntu4 tests stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/1918740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
This bug was fixed in the package ghostwriter - 23.08.5+ds-0ubuntu1 --- ghostwriter (23.08.5+ds-0ubuntu1) noble; urgency=medium * New upstream release (23.08.5) ghostwriter (23.08.4+ds-0ubuntu2) noble; urgency=medium * Add apparmor profile to fix userns. (LP: #2046844) -- Scarlett Moore Thu, 22 Feb 2024 09:31:12 -0700 ** Changed in: ghostwriter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054632] Re: ninja command failing for upstream libvirt compilation
Hello, As Frank mentioned, it would be really useful if we could actually reproduce this problem with our package. Also, I'm curious about something. If you are building libvirt directly from upstream sources, would it really make a difference if our package had the patch after all? Thank you in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054632 Title: ninja command failing for upstream libvirt compilation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2054632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055062] Re: merge 0.7.2-4 from deiban unstable
This bug was fixed in the package lua-dbi - 0.7.2-4ubuntu1 --- lua-dbi (0.7.2-4ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2055062). Remaining changes: - debian/patches/mysql-8.0: Adjustments to allow build against MySQL 8.0 to fix FTBFS. -- Athos Ribeiro Mon, 26 Feb 2024 15:17:21 -0300 ** Changed in: lua-dbi (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055062 Title: merge 0.7.2-4 from deiban unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua-dbi/+bug/2055062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 284401] Re: gcc fails when "-Wall" "-Wno-long-double" parametres used together
Launchpad has imported 31 comments from the remote bug at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28322. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2006-07-08T23:03:50+00:00 Debian GCC maintainers wrote: [forwarded from http://bugs.debian.org/367657] Summary: GCC should be more tolerant of gcc -Wno-this-is-not-a-recognised-warning as specified in detail below. Discussion: Occasionally, GCC introduces new warnings. For example, GCC 4 has introduced warnings about discrepancies in signedness of integers pointed to by otherwise-compatible pointers. Furthermore, because GCC has traditionally had such good warnings, and such good configurability of warnings, and because no-one looks at warnings that don't cause build failures, many people (myself included) use -Werror in nearly all of their projects. However, when new warnings are introduced, there is a problem with the configurability: Like any warning, whether or not you want it enabled depends on your coding style and practices and on other rather subjective details. This means that there can be no universally correct default for a new warning; turning it on by default is sometimes a reasonable value judgement on the part of the compiler authors. When a new warning is introduced and enabled by default, then the author of a project whose coding style warrants disabling that warning is faced with a difficult choice: * they can set the build system to say -Wno-new-warning (for whatever value of `new-warning' is relevant) so that it builds on new compilers but so that users of older GCC's need to override the build system to remove -Wno-new-warning (which the older GCC doesn't understand); * they can turn off -Werror, leaving themselves open to the massive bugs which are often hidden by warnings which are ignored (perhaps bugs which don't show up and aren't warned about on the developer's system, because of the various type differences between systems); * they can leave things as they are and require users of the new compiler to override the build system. * they can add complexity to the build system to try to autodetect the available compiler options; this usually works but it makes the build system more complex - note that in some projects this might be the only reason why something like autoconf might be required. None of these are the right answer. I would like to propose a straightforward answer which can easily be implemented in GCC and leaves everything correct. With this change, it is much easier to make portable packages which still make good and strict use of GCC's excellent warnings system. Specification of the proposed new behaviour: 1. GCC should ignore unknown -Wno-* options if no other warnings are to be issued. This is always correct since the only effect of such an option would be to suppress warnings which might otherwise be issued. If no warnings are to be issued at all then treating even an unknown suppression as a no-op is clearly correct. 2. If some other warnings are to be issued, then it is necessary to report on stderr if any unknown (and therefore unheeded) suppressions were in force, in case the user intended for one of the relevant suppressions to apply to the warning(s) in question. This will alert the user to the lack of support for that suppression in this gcc (ie, either to the user's typo or the wrong gcc version). The combination of (1) and (2) will minimise stderr noise about unknown suppressions as far as I think is reasonably possible. 3. Obviously unknown suppressions ignored according to (1) should not count as errors for -Werror. Whether unknown suppressions reported according to (2) should count as as errors for -Werror is not important because the actual warning will count as an error for -Werror. So the diagnostic from (2) above can be a real `warning', or simply an appropriate message issued to stderr the first time a warning is to be issued despite the presence of unknown -Wno-* options. 4. Whenever a new GCC warning is introduced, or the scope of an existing warning significantly extended, a corresponding -Wno-* option should be introduced at the same time. (AFAIAA current GCC development practice seems to abide by this principle.) 5. The changes to implement (1) and (2) should be backported to earlier GCCs and earlier Debian branches insofar as practical. Reply at: https://bugs.launchpad.net/ubuntu/+source/gcc-4.2/+bug/284401/comments/0 On 2006-07-09T10:41:01+00:00 Pinskia wrote: This is more of a policy issue rather than a bug. > Occasionally, GCC
[Bug 2054183] Re: nautilus not generating thumbnails anymore
the solution to not lose the configuration after the reboot : sudo nano /etc/rc.local The bash: #!/bin/bash # Votre commande ici sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 sudo chmod +x /etc/rc.local -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054183 Title: nautilus not generating thumbnails anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2054183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049253] Re: remove celery and rdeps, fails with Python 3.12
** Changed in: celery (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049253 Title: remove celery and rdeps, fails with Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/celery/+bug/2049253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054236] Re: qpid-proton-j-extensions: FTBFS with default Java 21
** Changed in: qpid-proton-j-extensions (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054236 Title: qpid-proton-j-extensions: FTBFS with default Java 21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpid-proton-j-extensions/+bug/2054236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052318] Re: pycountry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13
** Changed in: pycountry (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052318
Title:
pycountry: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.12 3.11" returned exit code 13
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/2052318/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1990856] Re: Does not consider all versions in Packages files
Hello Dan, or anyone else affected, Accepted debootstrap into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.126+nmu1ubuntu0.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-jammy ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1990856 Title: Does not consider all versions in Packages files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1990856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
Hello Åka, or anyone else affected, Accepted debootstrap into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.126+nmu1ubuntu0.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debootstrap (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054872] Re: Cannot change IRQ 70 affinity: Input/output error
Hi, Thank you for taking the time to report bugs and help make Ubuntu better. To act on this report, We'll need some more information, specifically: What impact this bug is having on users (is this just the logging spam?) Specific, minimal steps to reproduce it (are you able to isolate what is causing the log entries to be recorded?) Specific configuration Please add a comment with the extra information, and then set the bug status back to "New". ** Changed in: irqbalance (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054872 Title: Cannot change IRQ 70 affinity: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2054872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
I confirmed that the resulting target dir of debootstrap in Jammy (with patch/MERGED_USR=no) and Mantic is the same, with a comparison of `ls -lR` (normalized for Month/Day/Time fields). ... Test command for Jammy (patched) and Mantic: # debootstrap --arch=amd64 --variant=minbase --keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg noble /tmp/nobletest http://archive.ubuntu.com/ubuntu Dir listing for Jammy (patched) and Mantic: deboostrap-jammy # ls -lR /tmp/nobletest/ > list.jammy deboostrap-mantic # ls -lR /tmp/nobletest/ > list.mantic Normalization and comparison: $ sed -i 's/[A-Z][a-z][a-z] .[0-9] [0-9][0-9]:[0-9][0-9]/DATETIME/' list.jammy list.mantic $ diff -U0 list.jammy list.mantic --- list.jammy 2024-02-26 19:39:49.102864808 -0300 +++ list.mantic 2024-02-26 19:39:49.114864569 -0300 @@ -76 +76 @@ --rw-r--r-- 1 root root 18 DATETIME hostname +-rw-r--r-- 1 root root 19 DATETIME hostname @@ -7093 +7093 @@ --rw-r--r-- 1 root root 60238 DATETIME bootstrap.log +-rw-r--r-- 1 root root 60045 DATETIME bootstrap.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054826] Re: screen log filename length is capped at 70 characters
Hi Imre, This seems to be truncated due to the width of your terminal window, since "colon" is used as a command through the window and it does not span new lines when a command is longer than the window witdh. However, there is a -L option you could pass to screen to set a new logfile name whose maximum length is set to PATH_MAX, which should be greater. I am setting this as an opinion since it seems to me that this is not a bug, but a design decision in screen. If you disagree, please set this bug status back to new and provide additional information on why you believe this is a bug. In this case, it would also be nice to file a bug upstream. ** Changed in: screen (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054826 Title: screen log filename length is capped at 70 characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/2054826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
Slrry I can make this clearer too by adding a mantic task and marking it as fix released. ** Also affects: base-files (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: debootstrap (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: debootstrap (Ubuntu Mantic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
TL;DR: The fix is not needed on Mantic.
This is just to expand a bit on the brief note in '[Where problems could
occur]' ("moved to merging post-extraction"), for clarity.
The code in `scripts/gutsy` (used for noble) is different between Mantic
and Jammy with regards to the order of package extraction and usr-merge
setup, in first_stage_install().
The issue happens in Jammy because usr-merge setup runs _before_
extraction (thus extraction of base-files fails as the
/{bin,lib,lib64,sbin} symlinks already exist):
setup_merged_usr
extract $required
But it doesn't happen in Mantic because usr-merge setup runs _after_
extraction (thus extraction of base-files works as the symlinks don't
yet exist):
extract $required
merge_usr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054925
Title:
Debootstrap fails for Noble with base-files 13ubuntu7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052707] Re: [24.04 FEAT] bump powerpc-utils to version 1.3.12
This bug was fixed in the package powerpc-utils - 1.3.12-0ubuntu1 --- powerpc-utils (1.3.12-0ubuntu1) noble; urgency=medium * New upstream release (LP: #2052707) - Run update-maintainer script, since this package is now Ubuntu-specific. - Remove dh-autoreconf Build-Depends in d/control to solve lintian message "useless-autoreconf-build-depends". -- Patricia Domingues Fri, 16 Feb 2024 14:22:16 -0300 ** Changed in: powerpc-utils (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052707 Title: [24.04 FEAT] bump powerpc-utils to version 1.3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2052707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054479] Re: Merge libvirt from Debian unstable for noble
This bug was fixed in the package libvirt - 10.0.0-2ubuntu1 --- libvirt (10.0.0-2ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2054479). Remaining changes: - Disable libssh2 support (universe dependency) - d/control: add libzfslinux-dev to build-deps - d/control: drop libvirt-lxc, vbox and xen drivers to suggest - debian/patches/ubuntu/ovmf_paths.patch: adjust paths to secboot.fd UEFI Secure Boot enabled variants of the OVMF firmware and variable store for the paths where we ship these files in Ubuntu. - Set qemu-group to kvm (for compat with older ubuntu) - Additional apport package-hook - Autostart default bridged network (As upstream does, but not Debian). In addition to just enabling it our solution provides: + do not autostart if subnet is already taken (e.g. in guests). + iterate some alternative subnets before giving up - d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is the group based access to libvirt functions as it was used in Ubuntu for quite a long time. + d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests due to the group access change. + d/libvirt-daemon-system.postinst: add users in sudo to the libvirt group. - Update README.Debian with Ubuntu changes - d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx - fix autopkgtests (LP 1899180) + d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making vmlinuz available and accessible (Debian bug 848314) + d/t/control: fix smoke-qemu-session by ensuring the service will run installing libvirt-daemon-system + d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as long as the following undefine succeeds + d/t/smoke-lxc: use systemd instead of sysV to restart the service + d/t/control, d/t/smoke-lxc: retry service restart and skip test if failing; This was flaky on some release/architectures + d/t/smoke-lxc: retry check_domain being flaky on arm64 - dnsmasq related enhancements + run dnsmasq as libvirt-dnsmasq (LP 1743718) + d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group + d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group on purge + d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user libvirt-dnsmasq and adapt the self tests to expect that config + d/libvirt-daemon-system.postinst: fix old libvirt-dnsmasq users group + Add dnsmasq configuration to work with system wide dnsmasq-base - d/p/ubuntu/set-default-machine-to-ubuntu.patch: to select default machine type correctly with newer qemu/libvirt - d/p/ubuntu/lp-1861125-ubuntu-models: recognize Ubuntu models for (LP 1861125) fixups - d/p/ubuntu/wait-for-qemu-kvm.patch - avoid hangs on startup (LP 1887592) - d/libvirt-daemon-system.libvirt-guests.default: shut guests down in parallel - Apparmor Delta that is Ubuntu specific or yet to be upstreamed split into logical pieces. File names in debian/patches/ubuntu-aa/: + 0020-virt-aa-helper-ubuntu-storage-paths.patch: apparmor, virt-aa-helper: Allow various storage pools and image locations + 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor, libvirt-qemu: Add 9p support + 0031-virt-aa-helper-Ask-for-no-deny-rule-for-readonly-dis.patch: virt-aa-helper: Ask for no deny rule for readonly disk + 0032-apparmor-libvirt-qemu-Allow-reading-charm-specific-c.patch: apparmor, libvirt-qemu: Allow reading charm-specific ceph config + 0033-UBUNTU-only-apparmor-for-kvm.powerpc-LP-1680384.patch: allow commands executed by ubuntu only kvm wrapper on ppc64el (LP 1686621 LP 1680384 LP 1784023) + 0034-apparmor-virt-aa-helper-access-for-snapped-nova.patch: apparmor, virt-aa-helper: access for snapped nova + lp-1815910-allow-vhost-hotplug.patch: avoid apparmor issues with vhost-net/vhost-vsock/vhost-scsi hotplug (LP 1815910) - libvirt should not use user/group tss for swtpm (LP 1948880) + d/libvirt-daemon-system.postinst: own swtpm logdir by user swtpm + d/p/u/swtpm-by-swtpm-user.patch: change default spawned swtpm processes to user swtpm and adapt expected self test result changes triggered by this + d/libvirt-daemon-system.postinst: create user/group swtpm if not present due to swtpm-tools (LP 1951975) - d/control: Use libc6-dev instead of libc-dev as a build dependency - d/libvirt-clients.lintian-overrides: Add script-not-executable lintian override - libvirt-uri.sh, d/rules: Automatically switch default libvirt URI for users via user profile (xen URI on dom0, qemu:///system otherwise) + Update: Set LIBVIRT_DEFAULT_URI to "qemu:///system"
[Bug 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
The iso from today, Ubuntu-MATE 24.04 LTS "Noble Numbat" - Daily amd64 (20240226) has just installed perfectly in KVM with no problem booting to a full GUI. It seems that the arctica-greeter difficulty has been overcome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045063] Re: Demote glusterfs for noble
After discussing the release-upgrade options in a mailing list thread[1], and internally with some colleagues, I have decided to not change the release upgrader to handle the glusterfs demotion. This is an opinion, and I might change it depending on feedback on the 24.04 release and/or beta. The release upgrade is only enabled for LTS versions at the first point release, so there is time to gather feedback until then. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2024-January/042872.html 2. https://lists.ubuntu.com/archives/ubuntu-devel/2024-January/042876.html ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Triaged => Opinion ** Also affects: ubuntu-release-notes Importance: Undecided Status: New ** Changed in: ubuntu-release-notes Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-release-notes Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045063 Title: Demote glusterfs for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2045063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
