[Bug 1962490] Re: Support VF groups rate limit
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Bodong Wang (bodong-wang) ** Changed in: linux-bluefield (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/1962490 Title: Support VF groups rate limit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1962490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928259] Re: Package upgrade won't restart services
** Changed in: nfs-utils (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/1928259 Title: Package upgrade won't restart services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1928259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962468] Re: Remove old/obsolete/unnecessary firmware files
** Tags added: kern-2600 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962468 Title: Remove old/obsolete/unnecessary firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1962468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962529] [NEW] package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Public bug reported: error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 1 11:31:43 2022 ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-28 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ca.pem', 'server-cert.pem', 'debian-5.7.flag', 'binlog.01', 'undo_002', 'binlog.index', 'ibdata1', '#ib_16384_0.dblwr', 'private_key.pem', 'ib_logfile0', 'sys', 'ib_buffer_pool', '#innodb_temp', 'public_key.pem', 'mysql.ibd', 'undo_001', '#ib_16384_1.dblwr', 'ib_logfile1', 'performance_schema', 'server-key.pem', 'binlog.02', 'client-key.pem', 'ca-key.pem', 'client-cert.pem', 'auto.cnf', 'mysql'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=81583280-1151-412c-ab6f-79eb91863295 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962529 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1962529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
** Summary changed: - [Wayland][Nvidia] gdm default use Xorg in 22.04 + [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04
** Tags added: jammy nvidia ** Changed in: gdm3 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962276] Re: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed
** Changed in: upower (Ubuntu) Status: Incomplete => Fix Released ** Summary changed: - [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed + Laptop monitor does not turn off/disconnect when the lid is closed ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Bug watch added: Debian Bug tracker #1006368 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 ** Also affects: upower via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 Importance: Unknown Status: Unknown ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: Laptop monitor does not turn off/disconnect when the lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1962276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962351] Re: login screen shown on inactive monitor
*** This bug is a duplicate of bug 1962276 *** https://bugs.launchpad.net/bugs/1962276 ** This bug has been marked a duplicate of bug 1962276 Laptop monitor does not turn off/disconnect when the lid is closed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962351 Title: login screen shown on inactive monitor To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1962351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04
** Description changed: + [Impact] + + * In Ubuntu 22.04, gdm should use Wayland by default even if proprietary nVidia driver is in use. + * gdm upstream prefers Wayland if nvidia version newer than (or equal) to 510. It same as Ubuntu's strategy[1]. + + [Test Plan] + + Steps: + 1. Download jammy daily build + 2. Install nvidia driver by selecting "install third-party packages.." during the installation. + 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. + + [Where problems could occur] + * If nVidia GPU doesn't support Wayland then it will be a problem but it doesn't means this patch leads a regression, instead, the problem should always there as it is if the user switches to Wayland mode no matter default mode. + * This ticket switches the default mode to Wayland. If there is a problem then user will encounter it after the installation which has bad experience. + * However, it's not regression because Jammy is a new LTS version and we decide to switch to Wayland. If a problem occurs, then we fix it. + + --- + [Steps to reproduce] 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Expect result] gdm using wayland (at least with nvidia-510) [Actual result] gdm using xorg 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy gdm3 gdm3: Installed: 41.3-1ubuntu2 Candidate: 41.3-1ubuntu2 Version table: *** 41.3-1ubuntu2 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Reference: - Ubuntu Jammy should use Wayland as default with nVidia + [1] Ubuntu Jammy should use Wayland as default with nVidia https://docs.google.com/document/d/1wK4vGUXaDG2Nd7e3XGI9kDpNzReka_VOHO7sgRqce5s/edit?disco=VxVMzfA -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: ipywidgets (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/1954649 Title: autopkgtest regressions with python3.10 as supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04
Test on my P350 with nvidia-510 on Jammy daily build with dist-upgrade. ** Patch added: "gdm.rules-Prefer-Wayland-with-NVIDIA-510.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1962523/+attachment/5564288/+files/gdm.rules-Prefer-Wayland-with-NVIDIA-510.debdiff ** Changed in: oem-priority Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962276] Re: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed
Hi Daniel you are correct. I booted into the 5.15.0-18.18-generic and suspend and clam shell mode works as expected. Thanks Rue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04
** Description changed: [Steps to reproduce] 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Expect result] - gdm using wayland + gdm using wayland (at least with nvidia-510) [Actual result] gdm using xorg 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy gdm3 gdm3: - Installed: 41.3-1ubuntu2 - Candidate: 41.3-1ubuntu2 - Version table: - *** 41.3-1ubuntu2 500 - 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 41.3-1ubuntu2 + Candidate: 41.3-1ubuntu2 + Version table: + *** 41.3-1ubuntu2 500 + 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + 100 /var/lib/dpkg/status Reference: Ubuntu Jammy should use Wayland as default with nVidia https://docs.google.com/document/d/1wK4vGUXaDG2Nd7e3XGI9kDpNzReka_VOHO7sgRqce5s/edit?disco=VxVMzfA ** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962471] Re: iwlwifi fails after suspend (Failed to start RT ucode: -110)
We have verified that the issue can be fixed with the Intel -67 iwlwifi firmware. Probably the firmware newer than -67 might have fix for it. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/iwlwifi-ty-a0-gf-a0-67.ucode Could you install the firmware to your system, and update the kernel here https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1948375 for loading later firmware version? Please let us know if the solution works for your system too. Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962471 Title: iwlwifi fails after suspend (Failed to start RT ucode: -110) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564287/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564286/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564285/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564284/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564283/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564282/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564281/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564280/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564278/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564279/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564276/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564277/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1962485/+attachment/5564275/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962485 Title: Kernel Crash [general protection fault: [#1] SMP NOPTI] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962485] Re: Kernel Crash [general protection fault: 0000 [#1] SMP NOPTI]
apport information ** Tags added: apport-collected ** Description changed: Hi, I am running openstack xena release on ubuntu focal. Today my compute node running ubuntu focal crashed with due to kernel and dump has been generated in /var/crash/. Below is the kernel trace in crash dump. [455151.890114] general protection fault: [#1] SMP NOPTI [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded Tainted: G OE 5.4.0-88-generic #99-Ubuntu [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 10/06/2021 [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60 [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 3f 00 74 25 e8 cf ff ff ff 41 01 c5 48 83 c3 40 48 83 3b 00 [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202 [455151.891707] RAX: RBX: 9387c594f280 RCX: [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 0314a8c0f1b16f3e [455151.892130] RBP: a6b477487ba0 R08: R09: bc6ed7f0 [455151.892341] R10: a6b477487cd0 R11: 0001 R12: [455151.892552] R13: R14: 9391e5684000 R15: bd5f9880 [455151.892767] FS: 7f69950c75c0() GS:9391feac() knlGS: [455151.893016] CS: 0010 DS: ES: CR0: 80050033 [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 00340ee0 [455151.893434] Call Trace: [455151.893514] count_subheaders.part.0+0x31/0x60 [455151.893646] unregister_sysctl_table+0x30/0x90 [455151.893781] unregister_net_sysctl_table+0xe/0x10 [455151.893922] __devinet_sysctl_unregister.isra.0+0x2c/0x60 [455151.894082] devinet_sysctl_unregister+0x29/0x40 [455151.894220] inetdev_event+0x1e8/0x560 [455151.894334] ? skb_dequeue+0x5f/0x70 [455151.89] notifier_call_chain+0x55/0x80 [455151.894565] ? notifier_call_chain+0x55/0x80 [455151.894693] raw_notifier_call_chain+0x16/0x20 [455151.894829] call_netdevice_notifiers_info+0x2e/0x60 [455151.894983] ? tun_show_owner+0x60/0x60 [455151.895098] rollback_registered_many+0x36e/0x520 [455151.895239] unregister_netdevice_queue+0x94/0x120 [455151.895383] __tun_detach+0x421/0x430 [455151.895495] tun_chr_close+0x3a/0x70 [455151.895605] __fput+0xcc/0x260 [455151.895698] fput+0xe/0x10 [455151.895792] task_work_run+0x8f/0xb0 [455151.895903] exit_to_usermode_loop+0x131/0x160 [455151.896036] do_syscall_64+0x163/0x190 [455151.896150] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [455151.896302] RIP: 0033:0x7f69965ba3fb [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44 [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 0003 [455151.897201] RAX: RBX: 557fe0875e50 RCX: 7f69965ba3fb [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 002b [455151.897637] RBP: 557fe0887460 R08: R09: [455151.904390] R10: 0032 R11: 0293 R12: 557fe0875e50 [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 557fe0747900 I didn't find any documented details on kernel 5.4 for this bug. I have uploaded the logs via ubuntu-bug linux command. # uname -a Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 5.4.0-88.99-generic 5.4.140 I am using Dell R6525 with EPYC 7532 CPUs. Let me know if there is there are more information needed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-88-generic 5.4.0-88.99 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 28 17:38 seq crw-rw 1 root audio 116, 33 Feb 28 17:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Mon Feb 28 21:20:20 2022 InstallationDate: Installed on 2021-07-29 (214 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R6525 PciMultimedia: ProcEnviron: TERM=xterm-256color
[Bug 1962523] [NEW] [Wayland][Nvidia] gdm default use Xorg in 22.04
Public bug reported: [Steps to reproduce] 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Expect result] gdm using wayland [Actual result] gdm using xorg 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 Codename: jammy 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy gdm3 gdm3: Installed: 41.3-1ubuntu2 Candidate: 41.3-1ubuntu2 Version table: *** 41.3-1ubuntu2 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Reference: Ubuntu Jammy should use Wayland as default with nVidia https://docs.google.com/document/d/1wK4vGUXaDG2Nd7e3XGI9kDpNzReka_VOHO7sgRqce5s/edit?disco=VxVMzfA ** Affects: oem-priority Importance: Critical Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962276] Re: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed
Sure no problem. I will report back -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723560] Re: telegram-desktop crashed with SIGABRT in pa_threaded_mainloop_unlock()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telegram-desktop (Ubuntu) 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/1723560 Title: telegram-desktop crashed with SIGABRT in pa_threaded_mainloop_unlock() To manage notifications about this bug go to: https://bugs.launchpad.net/telegram-desktop/+bug/1723560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933186] Re: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_plac
** Tags removed: fixed-in-42.0 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933186 Title: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1933186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962276] Re: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed
I wonder if the new kernel in comment #10 worked /because/ the upower update to 0.99.16-2 arrived at the same time... rue: Please test the Ubuntu kernel again (5.15.0-18.18-generic) ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** Changed in: upower (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Bug watch removed: Debian Bug tracker #1006368 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962518] Re: KDE panel disappeared after update
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: plasma-workspace (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/plasma-workspace/+question/700770 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962518 Title: KDE panel disappeared after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1962518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962518] Re: KDE panel disappeared after update
Finally, here is the output of running plasmashell in the foreground when it failed to create the panel (nothing looks suspicious to me): craigster0@p51:/var/log$ ps -fp 9877 UID PIDPPID C STIME TTY TIME CMD craigst+9877 1 0 19:09 ?00:00:01 /usr/bin/plasmashell craigster0@p51:/var/log$ kill 9877 craigster0@p51:/var/log$ plasmashell org.kde.plasmaquick: Applet preload policy set to 1 kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/" kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/" kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Next/contents/images/" file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Plasma Shell startup completed ^Z [1]+ Stopped plasmashell craigster0@p51:/var/log$ bg [1]+ plasmashell & -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1962518 Title: KDE panel disappeared after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1962518/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1962518] Re: KDE panel disappeared after update
And the other config files ** Attachment added: "Plasmashell config file 2 of 2 that I moved out of the way." https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1962518/+attachment/5564253/+files/plasmashellrc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962518 Title: KDE panel disappeared after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1962518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962518] [NEW] KDE panel disappeared after update
Public bug reported: I updated a bunch of packages today for my Ubuntu 20.04 system. After restarting the computer, the KDE panel did not appear, which is a huge problem. I will upload /var/log/dpkg.log if that is possible. After searching the internet, I tried killing and restarting plasmashell. That didn't help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plasma-workspace 4:5.18.8-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Feb 28 19:45:05 2022 InstallationDate: Installed on 2021-11-28 (92 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: plasma-workspace UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: plasma-workspace (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug focal ** Attachment added: "Package update history. The problem occured after the updates on 2022-02-28." https://bugs.launchpad.net/bugs/1962518/+attachment/5564248/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962518 Title: KDE panel disappeared after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1962518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962518] Re: KDE panel disappeared after update
And I have a work around! Thanks to the information in this post: https://archived.forum.manjaro.org/t/how-to-reset-kde-panel-widgets-etc- after-becoming-invisible-following-display-config-change/155280 It suggests: % rm ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/.config/plasmashellrc i'm a little more cautious so I moved them out of the way: % mkdir ~/.config,cya % mv ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/.config/plasmashellrc ~/.config,cya/. then I killed plasmashell and restarted it and the panel was back! Opening the bug here so other folks with the same problem will know the work around. I suspect it will be hard to actually fix this. ** Attachment added: "Config file 1 of 2 that I moved out of the way to fix this." https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1962518/+attachment/5564252/+files/plasma-org.kde.plasma.desktop-appletsrc -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1962518 Title: KDE panel disappeared after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1962518/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1962484] Re: Doesn't work with TP-Link Archer T2U Plus
** Changed in: rtl8812au (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/1962484 Title: Doesn't work with TP-Link Archer T2U Plus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1962484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951683] Re: Freeze
Thanks. It appears there have been no relevant crash reports from that machine: https://errors.ubuntu.com/user/e85201b46e9f1cd63274a63c5926fbb947a65e98887bdffa63fc5cf3e1a51379df0326aa35c54b472f5bb7443a49964f84a569d7fb5efb75d5c48e5148695c87 Next time a freeze happens, please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951683 Title: Freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1951683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962454] Re: Oops pages show wrong time window in JournalErrors
And in this example, JournalErrors is from the wrong day: https://errors.ubuntu.com/oops/779ee4de-8891-11ec-8fa0-fa163e983629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962454 Title: Oops pages show wrong time window in JournalErrors To manage notifications about this bug go to: https://bugs.launchpad.net/errors/+bug/1962454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962515] Re: Intermittent AX211 iwlwifi RT ucode init failed -110 at boot
For oem-5.14, the 1st proposed solution is to run backport-iwlwifi-dkms (impish 9340 should be sufficient to load -67 fw). Mark WONTFIX until further updates. ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962515 Title: Intermittent AX211 iwlwifi RT ucode init failed -110 at boot To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1962515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962515] [NEW] Intermittent AX211 iwlwifi RT ucode init failed -110 at boot
Public bug reported: [ 5.675835] iwlwifi :00:14.3: enabling device ( -> 0002) [ 5.693214] iwlwifi :00:14.3: api flags index 2 larger than supported by driver [ 5.693277] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.25 [ 5.698065] iwlwifi :00:14.3: loaded firmware version 64.97bbee0a.0 so-a0-gf-a0-64.ucode op_mode iwlmvm [ 5.933114] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz, REV=0x370 [ 6.101350] iwlwifi :00:14.3: loaded PNVM version 0x4b50f925 [ 6.113388] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000 [ 6.181309] iwlwifi :00:14.3: base HW address: 7c:50:79:c9:29:67 [ 6.201398] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 [ 7.396811] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x71f7, CPU2 Status: 0xb03 [ 7.396859] iwlwifi :00:14.3: UMAC PC: 0xc0081906 [ 7.396912] iwlwifi :00:14.3: LMAC PC: 0x1541c [ 7.396914] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 7.399116] iwlwifi :00:14.3: Loaded firmware version: 64.97bbee0a.0 so-a0-gf-a0-64.ucode [ 7.399119] iwlwifi :00:14.3: 0x | ADVANCED_SYSASSERT [ 7.399121] iwlwifi :00:14.3: 0x | trm_hw_status0 [ 7.399123] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 7.399124] iwlwifi :00:14.3: 0x | branchlink2 [ 7.399125] iwlwifi :00:14.3: 0x | interruptlink1 [ 7.399127] iwlwifi :00:14.3: 0x | interruptlink2 [ 7.399128] iwlwifi :00:14.3: 0x | data1 [ 7.399129] iwlwifi :00:14.3: 0x | data2 [ 7.399130] iwlwifi :00:14.3: 0x | data3 [ 7.399132] iwlwifi :00:14.3: 0x | beacon time [ 7.399133] iwlwifi :00:14.3: 0x | tsf low [ 7.399134] iwlwifi :00:14.3: 0x | tsf hi [ 7.399135] iwlwifi :00:14.3: 0x | time gp1 [ 7.399136] iwlwifi :00:14.3: 0x | time gp2 [ 7.399137] iwlwifi :00:14.3: 0x | uCode revision type [ 7.399139] iwlwifi :00:14.3: 0x | uCode version major [ 7.399140] iwlwifi :00:14.3: 0x | uCode version minor [ 7.399141] iwlwifi :00:14.3: 0x | hw version [ 7.399143] iwlwifi :00:14.3: 0x | board version [ 7.399144] iwlwifi :00:14.3: 0x | hcmd [ 7.399145] iwlwifi :00:14.3: 0x | isr0 [ 7.399146] iwlwifi :00:14.3: 0x | isr1 [ 7.399147] iwlwifi :00:14.3: 0x | isr2 [ 7.399148] iwlwifi :00:14.3: 0x | isr3 [ 7.399149] iwlwifi :00:14.3: 0x | isr4 [ 7.399150] iwlwifi :00:14.3: 0x | last cmd Id [ 7.399152] iwlwifi :00:14.3: 0x | wait_event [ 7.399153] iwlwifi :00:14.3: 0x | l2p_control [ 7.399154] iwlwifi :00:14.3: 0x | l2p_duration [ 7.399155] iwlwifi :00:14.3: 0x | l2p_mhvalid [ 7.399157] iwlwifi :00:14.3: 0x | l2p_addr_match [ 7.399158] iwlwifi :00:14.3: 0x | lmpm_pmg_sel [ 7.399159] iwlwifi :00:14.3: 0x | timestamp [ 7.399161] iwlwifi :00:14.3: 0x | flow_handler [ 7.399222] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 7.399223] iwlwifi :00:14.3: Transport status: 0x0042, valid: 7 [ 7.399224] iwlwifi :00:14.3: 0x2066 | NMI_INTERRUPT_HOST [ 7.399226] iwlwifi :00:14.3: 0x | umac branchlink1 [ 7.399227] iwlwifi :00:14.3: 0x8045DE0C | umac branchlink2 [ 7.399227] iwlwifi :00:14.3: 0x80481126 | umac interruptlink1 [ 7.399228] iwlwifi :00:14.3: 0xC00821AC | umac interruptlink2 [ 7.399229] iwlwifi :00:14.3: 0x0100 | umac data1 [ 7.399230] iwlwifi :00:14.3: 0xC00821AC | umac data2 [ 7.399231] iwlwifi :00:14.3: 0x | umac data3 [ 7.399231] iwlwifi :00:14.3: 0x0040 | umac major [ 7.399232] iwlwifi :00:14.3: 0x97BBEE0A | umac minor [ 7.399233] iwlwifi :00:14.3: 0x000F6F15 | frame pointer [ 7.399234] iwlwifi :00:14.3: 0xC0887F00 | stack pointer [ 7.399234] iwlwifi :00:14.3: 0x | last host cmd [ 7.399235] iwlwifi :00:14.3: 0x0404 | isr status reg [ 7.399274] iwlwifi :00:14.3: IML/ROM dump: [ 7.399275] iwlwifi :00:14.3: 0x0B03 | IML/ROM error/state [ 7.399286] iwlwifi :00:14.3: 0x71F7 | IML/ROM data1 [ 7.399296] iwlwifi :00:14.3: 0x0080 | IML/ROM WFPM_AUTH_KEY_0 [ 7.399303] iwlwifi :00:14.3: Fseq Registers: [ 7.399306] iwlwifi :00:14.3: 0x6000 | FSEQ_ERROR_CODE [ 7.399352] iwlwifi :00:14.3: 0x803C | FSEQ_TOP_INIT_VERSION [ 7.399358] iwlwifi :00:14.3: 0x0017 | FSEQ_CNVIO_INIT_VERSION [ 7.399404] iwlwifi :00:14.3: 0xA652 | FSEQ_OTP_VERSION [ 7.399410] iwlwifi :00:14.3: 0x0003 | FSEQ_TOP_CONTENT_VERSION [ 7.399456] iwlwifi :00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN [ 7.399461] iwlwifi :00:14.3: 0x00080400 | FSEQ_CNVI_ID [ 7.399465] iwlwifi :00:14.3: 0x00400410 | FSEQ_CNVR_ID [ 7.399468] iwlwifi :00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP [ 7.399475] iwlwifi :00:14.3: 0x00400410 |
[Bug 1951683] Re: Freeze
Thanks Daniel. cat /var/lib/whoopsie/whoopsie-id e85201b46e9f1cd63274a63c5926fbb947a65e98887bdffa63fc5cf3e1a51379df0326aa35c54b472f5bb7443a49964f84a569d7fb5efb75d5c48e5148695c87root@robert-msiLaptop:/home/rbrown# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951683 Title: Freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1951683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452115] Re: Python interpreter binary is not compiled as PIE
For posterity - this is how I did the analysis above: # download the current python3.9 source package and rebuild it with PIE enabled apt source python3.9 cd python3.9-3.9.10/ sed -i "/export DEB_BUILD_MAINT_OPTIONS=hardening=-pie/d" debian/rules dch -i -D jammy "Enable PIE (LP: #1452115)" update-maintainer # sbuild assumes you already have a jammy-amd64 schroot setup sbuild # use a LXD VM for testing lxc launch --vm images:ubuntu/jammy sec-jammy-amd64 # stop the VM and disable UEFI secure boot lxc stop sec-jammy-amd64 # ensure secureboot is not used so we can use the msr module later lxc config set set-jammy-amd64 security.secureboot=false lxc start sec-jammy-amd64 # make sure VM has full disk allocated lxc exec sec-jammy-amd64 -- growpart /dev/sda 2 lxc exec sec-jammy-amd64 -- resize2fs /dev/sda2 lxc file push ../*.deb sec-jammy-amd64/root/ lxc shell sec-jammy-amd64 # then inside the LXD VM install and run pyperformance with and without the new python3.9 apt install python3-pip pip3 install pyperformance # tune for system performance modprobe msr python3.9 -m pyperf system tune # get baseline numbers without PIE pyperformance run --python=/usr/bin/python3.9 -o py3.9.json # install our debs we built above that have PIE enabled apt install ./python3.9_3.9.10-2ubuntu1_amd64.deb ./libpython3.9-stdlib_3.9.10-2ubuntu1_amd64.deb ./python3.9-minimal_3.9.10-2ubuntu1_amd64.deb ./libpython3.9-minimal_3.9.10-2ubuntu1_amd64.deb ./libpython3.9_3.9.10-2ubuntu1_amd64.deb ./libpython3.9-dev_3.9.10-2ubuntu1_amd64.deb ./python3.9-dev_3.9.10-2ubuntu1_amd64.deb # check they have PIE apt install devscripts hardening-check /usr/bin/python3.9 # re-run pyperformance with PIE pyperformance run --python=/usr/bin/python3.9 -o py3.9-pie.json # and compare the results python3 -m pyperf compare_to py3.9.json py3.9-pie.json --table -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1452115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951683] Re: Freeze
What is the content of the file: /var/lib/whoopsie/whoopsie-id ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951683 Title: Freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1951683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452115] Re: Python interpreter binary is not compiled as PIE
I am actively looking at this - FWIW the performance results with PIE enabled look good - https://paste.ubuntu.com/p/PZjqMFSNSR/ - so I am discussing internally whether this is something that can still land for Ubuntu 22.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1452115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909678] Re: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login-screen
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: xwayland (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: xwayland (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909678 Title: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login- screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951683] Re: Freeze
New crash today. Log attached. cat /var/crash/kexec_cmd /sbin/kexec -p -s --command-line="BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-89-generic root=UUID=3405df65-a898-4ac8-86a0-474b4da9b724 ro rootflags=subvol=@ quiet splash vt.handoff=7 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz No file created *.crash No new file posted at https://errors.ubuntu.com/user/ID ** Attachment added: "syslog22022-03-01.txt" https://bugs.launchpad.net/ubuntu/+bug/1951683/+attachment/5564230/+files/syslog22022-03-01.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951683 Title: Freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1951683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962357] Re: gnome-shell takes a lot of ram
Kay-Ro, that sounds like bug 1876641 so try: gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false and then log in again. If that doesn't solve your issue then please open a new bug by running: ubuntu-bug gnome-shell instead of commenting here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962357 Title: gnome-shell takes a lot of ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1962357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950836] Re: gdm wants to do smartcard auth against yubikey with pcscd installed
*** This bug is a duplicate of bug 1933027 *** https://bugs.launchpad.net/bugs/1933027 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) 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/1950836 Title: gdm wants to do smartcard auth against yubikey with pcscd installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1950836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
From the screenshot in comment #5 and the gnome-shell (v40) source code: Установить обновления и перезапустить Система будет автоматически выключена через %d секунд [✓] Установить отложенные обновления ПО Note that's two major releases behind what is in jammy proposed right now so we should retest with gnome-shell 42 when it's ready. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962481] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) 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/1962481 Title: kubuntu 20.04 LTS didn't startx with dual gfxcard on board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962484] Re: Doesn't work with TP-Link Archer T2U Plus
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1962484 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. FYI: You should upgrade your system, the 5.11 kernel you mention is no longer supported & if all security fixes had been applied; your system would be using a supported kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962484 Title: Doesn't work with TP-Link Archer T2U Plus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1962484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958148] Re: mkinitramfs is too slow
Where is the discussion happening? I ran the same benchmarks for my i7-6770HQ 4-core system. This really needs revising. While disk space using in /boot is a concern, in this example at least -10 would use only 8MB (10%) more space and cut the time taken from 2m1s to 13s. zstd.0 84M 0m2.150s zstd.1 96M 0m1.236s zstd.2 90M 0m1.350s zstd.3 84M 0m2.235s zstd.4 84M 0m3.355s zstd.5 81M 0m5.679s zstd.6 81M 0m7.416s zstd.7 78M 0m8.857s zstd.8 77M 0m10.134s zstd.9 77M 0m11.238s zstd.10 72M 0m13.232s zstd.11 72M 0m14.897s zstd.12 72M 0m19.343s zstd.13 72M 0m26.327s zstd.14 72M 0m30.948s zstd.15 72M 0m40.913s zstd.16 70M 0m59.517s zstd.17 66M 1m15.854s zstd.18 64M 1m36.227s zstd.19 64M 2m1.417s -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958148 Title: mkinitramfs is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962481] Re: kubuntu 20.04 LTS didn't startx with dual gfxcard on board
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962481 Title: kubuntu 20.04 LTS didn't startx with dual gfxcard on board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962510] [NEW] failing tests with new sssd, blocks python3-defaults
Public bug reported: adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. ** Affects: adsys (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed ** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962510 Title: failing tests with new sssd, blocks python3-defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.
This seems to be the same as https://bugs.launchpad.net/ubuntu/+source/evolution-data- server/+bug/1952107 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959473 Title: Evolution: Migrate to People API to retain programmatic access to Google Contacts. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1959473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962277] Re: To support Synaptics fp device
** Also affects: libfprint (Ubuntu Jammy) Importance: Medium Status: New ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) 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/1962277 Title: To support Synaptics fp device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956497] Re: UBSAN warning on unplugging USB4 DP alt mode from AMD Yellow Carp graphics card
Landed via linux-stable to linux-oem-5.14 version -1023, linux/jammy version 5.15.0-19.19. ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: hwe-next 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/1956497 Title: UBSAN warning on unplugging USB4 DP alt mode from AMD Yellow Carp graphics card To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962277] Re: To support Synaptics fp device
** Tags added: amd originate-from-1961609 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962277 Title: To support Synaptics fp device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926094] Re: Cursor not visible when renaming file/folder under Yaru-MATE-dark theme
https://github.com/ubuntu-mate/ubuntu-mate-artwork/issues/83 ** Bug watch added: github.com/ubuntu-mate/ubuntu-mate-artwork/issues #83 https://github.com/ubuntu-mate/ubuntu-mate-artwork/issues/83 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926094 Title: Cursor not visible when renaming file/folder under Yaru-MATE-dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1926094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961971] Re: Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e currently
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961971 Title: Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e currently To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961739] Re: PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform
While that fix is marked stable, we're waiting it to land via linux- stable. See https://lists.ubuntu.com/archives/kernel- team/2022-February/128290.html. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961739 Title: PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962277] Re: To support Synaptics fp device
** Changed in: oem-priority Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962277 Title: To support Synaptics fp device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962454] Re: Oops pages show wrong time window in JournalErrors
Yes for gnome-shell we want the journal in the seconds after the crash to see the Javascript stack dump (if any). But for some other crashes we need to also see what happened just before the crash. Maybe collect 10 seconds before to 10 seconds after the crash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962454 Title: Oops pages show wrong time window in JournalErrors To manage notifications about this bug go to: https://bugs.launchpad.net/errors/+bug/1962454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
To clarify, Alex's upower problem is bug 1962351. For the moment this bug of rue's is a kernel bug. ** No longer affects: upower (Ubuntu) ** No longer affects: mutter (Ubuntu) ** No longer affects: gnome-settings-daemon (Ubuntu) ** Summary changed: - [jammy] Laptop monitor does not turn off/disconnect when the lid is closed + [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962351] Re: login screen shown on inactive monitor
Tracking in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 per discussion with Alex. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962351 Title: login screen shown on inactive monitor To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1962351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962351] Re: login screen shown on inactive monitor
upower (0.99.16-2) unstable; urgency=medium ** This bug is no longer a duplicate of bug 1760849 Login screen appears on only one monitor and it's not the one I want ** Package changed: gdm3 (Ubuntu) => upower (Ubuntu) ** Bug watch added: Debian Bug tracker #1006368 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 ** Also affects: upower via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 Importance: Unknown Status: Unknown ** Changed in: upower (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/1962351 Title: login screen shown on inactive monitor To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1962351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960905] Re: ntpsec: FTBFS with OpenSSL 3.0
** Changed in: ntpsec (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/1960905 Title: ntpsec: FTBFS with OpenSSL 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntpsec/+bug/1960905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961376] Re: Unable to complete Xenial to Cosmic release upgrade
YUP! That's what I'M TRYING TO DO AND IT"S FAILING! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961376 Title: Unable to complete Xenial to Cosmic release upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1961376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
I am typically using Gnome3 with ubuntu 20.04 (standard ubuntu). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
Confirming that this is an issue even with the Dell customized ubuntu 20.04 version for the Dell XPS 13 laptop. I find about 30% cpu useage for gnome-shell when multiload-indicator is running. I also find that high framerate, high res youtube videos stutter when multiload-indicator is running but they run much smoother when multiload-indicator is closed. I am using an intel evo i7 processor and intel Xe graphics card. I am still struggling to understand if there is an update to fix this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893935] Re: [MIR] python3-vitrageclient
This bug was fixed in the package heat - 1:17.0.0+git2022011216.9af3af156-0ubuntu3 --- heat (1:17.0.0+git2022011216.9af3af156-0ubuntu3) jammy; urgency=medium * d/p/drop-zun(client).patch: Rename patch and drop zun.py as well. -- Corey Bryant Thu, 27 Jan 2022 10:30:29 -0500 ** Changed in: heat (Ubuntu Jammy) 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/1893935 Title: [MIR] python3-vitrageclient To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
> "so this is fixed already in f and later" - think you mean "b and later" here? yes sorry, fixed in b and later ** Description changed: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, - so this is fixed already in f and later. + so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962332 Title: xenial systemd fails to start if cgroup2 is mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893935] Re: [MIR] python3-vitrageclient
Override component to main python-vitrageclient 4.4.0-0ubuntu2 in jammy: universe/misc -> main python-vitrageclient-doc 4.4.0-0ubuntu2 in jammy amd64: universe/doc/optional/100% -> main python-vitrageclient-doc 4.4.0-0ubuntu2 in jammy arm64: universe/doc/optional/100% -> main python-vitrageclient-doc 4.4.0-0ubuntu2 in jammy armhf: universe/doc/optional/100% -> main python-vitrageclient-doc 4.4.0-0ubuntu2 in jammy i386: universe/doc/optional/100% -> main python-vitrageclient-doc 4.4.0-0ubuntu2 in jammy ppc64el: universe/doc/optional/100% -> main python-vitrageclient-doc 4.4.0-0ubuntu2 in jammy riscv64: universe/doc/optional/100% -> main python-vitrageclient-doc 4.4.0-0ubuntu2 in jammy s390x: universe/doc/optional/100% -> main python3-vitrageclient 4.4.0-0ubuntu2 in jammy amd64: universe/python/optional/100% -> main python3-vitrageclient 4.4.0-0ubuntu2 in jammy arm64: universe/python/optional/100% -> main python3-vitrageclient 4.4.0-0ubuntu2 in jammy armhf: universe/python/optional/100% -> main python3-vitrageclient 4.4.0-0ubuntu2 in jammy i386: universe/python/optional/100% -> main python3-vitrageclient 4.4.0-0ubuntu2 in jammy ppc64el: universe/python/optional/100% -> main python3-vitrageclient 4.4.0-0ubuntu2 in jammy riscv64: universe/python/optional/100% -> main python3-vitrageclient 4.4.0-0ubuntu2 in jammy s390x: universe/python/optional/100% -> main 15 publications overridden. ** Changed in: python-vitrageclient (Ubuntu Jammy) 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/1893935 Title: [MIR] python3-vitrageclient To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1893935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950317] Re: [MIR] Wireguard
Override component to main wireguard 1.0.20210914-1ubuntu2 in jammy: universe/misc -> main wireguard 1.0.20210914-1ubuntu2 in jammy amd64: universe/net/optional/100% -> main wireguard 1.0.20210914-1ubuntu2 in jammy arm64: universe/net/optional/100% -> main wireguard 1.0.20210914-1ubuntu2 in jammy armhf: universe/net/optional/100% -> main wireguard 1.0.20210914-1ubuntu2 in jammy i386: universe/net/optional/100% -> main wireguard 1.0.20210914-1ubuntu2 in jammy ppc64el: universe/net/optional/100% -> main wireguard 1.0.20210914-1ubuntu2 in jammy riscv64: universe/net/optional/100% -> main wireguard 1.0.20210914-1ubuntu2 in jammy s390x: universe/net/optional/100% -> main wireguard-tools 1.0.20210914-1ubuntu2 in jammy amd64: universe/net/optional/100% -> main wireguard-tools 1.0.20210914-1ubuntu2 in jammy arm64: universe/net/optional/100% -> main wireguard-tools 1.0.20210914-1ubuntu2 in jammy armhf: universe/net/optional/100% -> main wireguard-tools 1.0.20210914-1ubuntu2 in jammy ppc64el: universe/net/optional/100% -> main wireguard-tools 1.0.20210914-1ubuntu2 in jammy riscv64: universe/net/optional/100% -> main wireguard-tools 1.0.20210914-1ubuntu2 in jammy s390x: universe/net/optional/100% -> main 14 publications overridden. ** Changed in: wireguard (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/1950317 Title: [MIR] Wireguard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
(not reassigning because I'm not sure of a public team that can be used for ESM bug assignments, but I've contacted the engineering team internally.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962332 Title: xenial systemd fails to start if cgroup2 is mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
NB this has been assigned to Canonical Foundations, but as Ubuntu 16.04 is in Extended Security Maintenance now, this is actually a decision for our ESM Team to make regarding the path forward on whether xenial containers will be supported on jammy hosts, and if so, to update systemd for it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962332 Title: xenial systemd fails to start if cgroup2 is mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
"so this is fixed already in f and later" - think you mean "b and later" here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962332 Title: xenial systemd fails to start if cgroup2 is mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
Well, it may or may not be a bug in gnome-shell which implements the dialog; but it is definitely not a bug in update-notifier which is not involved in the communication between gnome-shell and systemd. It is likely a bug in gnome-shell signalling the wrong thing to systemd in this situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
As far as I can say, the dialog itself works as intended. The bug is, that the Ubuntu box is rebooting instead of turninging off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962493] Re: Compiled with Java 11
It appears 4.21 might be requiring Java SE 11. Maybe the latest version which is compatible with Java 8 is 4.20. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962493 Title: Compiled with Java 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse-jdt-core/+bug/1962493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948377] [linux-iot/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948377 Title: [SRU][F] USB: serial: pl2303: add support for PL2303HXN To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1948377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
In fact, I just searched my system and found these strings in gnome- shell after all, so reassigning back to there. ** Package changed: update-notifier (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
Thanks. The messages in question do not come from either update- notifier or update-manager as far as I can see (in particular, the source string for 'the system will...' is not present in either source package). I am not sure which package is actually presenting this dialog. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962493] [NEW] Compiled with Java 11
Public bug reported: It appears 4.21-1 version of this package was compiled with Java 11. If check the classes in this package with `file` I see version 55.0 (Java SE 11). This causes errors such as: ``` with root cause java.lang.UnsupportedClassVersionError: org/eclipse/jdt/internal/compiler/Compiler has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 ``` For compatibility reasons it should be compiled using Java 8. Otherwise many apps will fail to function eg. with Tomcat. ** Affects: eclipse-jdt-core (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962493 Title: Compiled with Java 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse-jdt-core/+bug/1962493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952107] Re: Google Contacts API Deprecated
Malfunction still persits (see below). Verbindung zu Adressbuch »xx...@gmail.com : Kontakte« fehlgeschlagen Ungültige Anfrageadresse oder -kopfzeile, oder nicht unterstützter Nicht-Standardparameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860987] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Focal) 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/1860987 Title: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860987] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) 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/1860987 Title: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947362] Re: Add Ubuntu Jammy as a known release
Verified on bionic: ubuntu@juju-e14b64-adt-9:~$ mk-sbuild jammy Specified release (jammy) not known to debootstrap ubuntu@juju-e14b64-adt-9:~$ sudo apt install -t bionic-proposed debootstrap Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: ubuntu-archive-keyring The following packages will be upgraded: debootstrap 1 upgraded, 0 newly installed, 0 to remove and 14 not upgraded. Need to get 35.2 kB of archives. After this operation, 1024 B of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main ppc64el debootstrap all 1.0.95ubuntu0.10 [35.2 kB] Fetched 35.2 kB in 0s (151 kB/s) (Reading database ... 130947 files and directories currently installed.) Preparing to unpack .../debootstrap_1.0.95ubuntu0.10_all.deb ... Unpacking debootstrap (1.0.95ubuntu0.10) over (1.0.95ubuntu0.9) ... Setting up debootstrap (1.0.95ubuntu0.10) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... ubuntu@juju-e14b64-adt-9:~$ mk-sbuild jammy I: Retrieving InRelease I: Checking Release signature ... ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947362 Title: Add Ubuntu Jammy as a known release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1947362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860987] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel
above commit https://kernel.ubuntu.com/git/ubuntu/ubuntu- groovy.git/commit/include/uapi/linux/openvswitch.h?id=bd1903b7c4596ba6f7677d0dfefd05ba5876707d is not available, any suggestion how to get that patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860987 Title: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962463] Re: Please remove from Jammy archive
Removing packages from jammy: kubuntu-driver-manager 15.10ubuntu4 in jammy kubuntu-driver-manager 15.10ubuntu4 in jammy amd64 kubuntu-driver-manager 15.10ubuntu4 in jammy arm64 kubuntu-driver-manager 15.10ubuntu4 in jammy armhf kubuntu-driver-manager 15.10ubuntu4 in jammy ppc64el kubuntu-driver-manager 15.10ubuntu4 in jammy riscv64 kubuntu-driver-manager 15.10ubuntu4 in jammy s390x kubuntu-driver-manager-dbg 15.10ubuntu4 in jammy amd64 kubuntu-driver-manager-dbg 15.10ubuntu4 in jammy arm64 kubuntu-driver-manager-dbg 15.10ubuntu4 in jammy armhf kubuntu-driver-manager-dbg 15.10ubuntu4 in jammy ppc64el kubuntu-driver-manager-dbg 15.10ubuntu4 in jammy riscv64 kubuntu-driver-manager-dbg 15.10ubuntu4 in jammy s390x Comment: Ubuntu-specific, unmaintained/superseded; LP: #1962463 1 package successfully removed. ** Changed in: kubuntu-driver-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/1962463 Title: Please remove from Jammy archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1962463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962491] [NEW] Please demote universe php8.1 binaries to universe
Public bug reported: Please demote php8.1-dba, php8.1-imap, php8.1-interbase, and php8.1-zip to universe. These four binary packages from php8.1 appear to have been included in main, that should rather be in universe, because they have dependencies on other binaries from universe. php8.0-dba, php8.1-dba: 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages php8.0-imap, php8.1-imap: 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages php8.0-interbase, php8.1-interbase: 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages php8.0-zip, php8.1-zip: 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages These cause the following update excuses: php8.1-dba/ in main cannot depend on libqdbm14 in universe php8.1-dba/ in main cannot depend on libqdbm14 in universe php8.1-imap/ in main cannot depend on libc-client2007e in universe php8.1-interbase/ in main cannot depend on libfbclient2 in universe php8.1-zip/ in main cannot depend on libzip4 in universe Impossible Depends: php8.1 -> libc-client2007e/8:2007f~dfsg-7build1/ Impossible Depends: php8.1 -> libfbclient2/3.0.8.33535.ds4-1ubuntu2/ Impossible Depends: php8.1 -> libzip4/1.7.3-1ubuntu2/ https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#php8.1 ** Affects: php8.1 (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/1962491 Title: Please demote universe php8.1 binaries to universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php8.1/+bug/1962491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962463] Re: Please remove from Jammy archive
$ reverse-depends src:kubuntu-driver-manager $ reverse-depends src:kubuntu-driver-manager -a source $ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962463 Title: Please remove from Jammy archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1962463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962481] Re: kubuntu 20.04 LTS didn't startx with dual gfxcard on board
I create clear reinstallation now without nvidia driver - same result. after poweron screen freeze with special logo of laptop model. but i can switch to tty2, then i can "startx" manually, but it didn-t start automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962481 Title: kubuntu 20.04 LTS didn't startx with dual gfxcard on board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962481] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1962481/+attachment/5564218/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962481 Title: kubuntu 20.04 LTS didn't startx with dual gfxcard on board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962481] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1962481/+attachment/5564217/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962481 Title: kubuntu 20.04 LTS didn't startx with dual gfxcard on board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962481] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1962481/+attachment/5564215/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962481 Title: kubuntu 20.04 LTS didn't startx with dual gfxcard on board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
