[Bug 1749393] Re: sbrk() not working under qemu-user with a PIE-compiled binary?
Focal old $ sudo apt install --reinstall qemu-user-static=1:4.2-3ubuntu6.18 Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 21.3 MB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 qemu-user-static amd64 1:4.2-3ubuntu6.18 [21.3 MB] Fetched 21.3 MB in 1s (16.4 MB/s) (Reading database ... 126154 files and directories currently installed.) Preparing to unpack .../qemu-user-static_1%3a4.2-3ubuntu6.18_amd64.deb ... Unpacking qemu-user-static (1:4.2-3ubuntu6.18) over (1:4.2-3ubuntu6.18) ... Setting up qemu-user-static (1:4.2-3ubuntu6.18) ... Processing triggers for man-db (2.9.1-1) ... ubuntu@f-1928075-qemuuserstatic:~$ sudo chroot /home/ubuntu/bullseye-arm64 /bin/sh /debootstrap/debootstrap --second-stage W: Failure trying to run: /sbin/ldconfig W: See //debootstrap/debootstrap.log for details ubuntu@f-1928075-qemuuserstatic:~$ tail -n 2 bullseye-arm64/debootstrap/debootstrap.log qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core dumped) Upgrade ubuntu@f-1928075-qemuuserstatic:~$ apt-cache policy qemu-user-static qemu-user-static: Installed: 1:4.2-3ubuntu6.18 Candidate: 1:4.2-3ubuntu6.19 Version table: 1:4.2-3ubuntu6.19 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 Packages *** 1:4.2-3ubuntu6.18 500 500 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 1:4.2-3ubuntu6.17 500 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 1:4.2-3ubuntu6 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages ubuntu@f-1928075-qemuuserstatic:~$ sudo apt install qemu-user-static Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: qemu-user-static 1 upgraded, 0 newly installed, 0 to remove and 65 not upgraded. Need to get 21.3 MB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 qemu-user-static amd64 1:4.2-3ubuntu6.19 [21.3 MB] Fetched 21.3 MB in 2s (9092 kB/s) (Reading database ... 126160 files and directories currently installed.) Preparing to unpack .../qemu-user-static_1%3a4.2-3ubuntu6.19_amd64.deb ... Unpacking qemu-user-static (1:4.2-3ubuntu6.19) over (1:4.2-3ubuntu6.18) ... Setting up qemu-user-static (1:4.2-3ubuntu6.19) ... Processing triggers for man-db (2.9.1-1) ... ubuntu@f-1928075-qemuuserstatic:~$ sudo update-binfmts --test --display qemu-aarch64 qemu-aarch64 (enabled): package = qemu-user-static type = magic offset = 0 magic = \x7f\x45\x4c\x46\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7\x00 mask = \xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff interpreter = /usr/bin/qemu-aarch64-static detector = Test with new versio ubuntu@f-1928075-qemuuserstatic:~$ sudo chroot /home/ubuntu/bullseye-arm64 /bin/sh /debootstrap/debootstrap --second-stage I: Installing core packages... W: Failure trying to run: dpkg --force-depends --install /var/cache/apt/archives/base-passwd_3.5.51_arm64.deb W: See //debootstrap/debootstrap.log for details ubuntu@f-1928075-qemuuserstatic:~$ tail -n 2 bullseye-arm64/debootstrap/debootstrap.log dpkg: error: parsing file '/var/lib/dpkg/status' near line 5 package 'dpkg': duplicate value for 'Package' field That is the good case and also a full run now completes. $ sudo rm -rf bullseye-arm64; sudo qemu-debootstrap --arch=arm64 bullseye bullseye-arm64 http://ftp.debian.org/debian I: Running command: debootstrap --arch arm64 --foreign bullseye bullseye-arm64 http://ftp.debian.org/debian W: Cannot check Release signature; keyring file not available /usr/share/keyrings/debian-archive-keyring.gpg I: Retrieving InRelease I: Retrieving Packages ... I: Configuring tasksel... I: Configuring libc-bin... I: Base system installed successfully. I can't run the docker test due to networking restrictions, but it was the same fault and the same fix - so that should be ok. If anyone else can test -proposed with docker please feel free to do so. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done 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/1749393 Title: sbrk() not working under qemu-user with a PIE-compiled binary? To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1749393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1945770] Re: firefox: Fail to build against OpenSSL 3.0
This bug was fixed in the package firefox - 95.0+build1-0ubuntu1
---
firefox (95.0+build1-0ubuntu1) jammy; urgency=medium
* New upstream release (95.0+build1)
[ Rico Tzschichholz ]
* Bump build-dep on cargo >= 0.54
- debian/control{,.in}
- debian/patches/relax-cargo-dep.patch
* Update patches
- debian/patches/armhf-rustc-thin-lto.patch
* Pass --without-wasm-sandboxed-libraries
- debian/config/mozconfig.in
* Install more sizes of the firefox application icon
- debian/build/rules.mk
* Bump dump_sys to bf7f6bd855eb6ecb233b52bfa7b2c975b7026540 (LP: #1945770)
- debian/build/create-tarball.py
-- Olivier Tilloy Tue, 30 Nov 2021
20:15:46 +0100
** Changed in: firefox (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945770
Title:
firefox: Fail to build against OpenSSL 3.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1945770/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896734] Re: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack
Fix proposed to branch: master Review: https://review.opendev.org/c/openstack/oslo.privsep/+/819996 ** Changed in: oslo.privsep 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/1896734 Title: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1896734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume
find a lenovo machine which has legacy hda audio desgin, install 20.04 and run dist-upgrade, enable the -proposed channel in the /etc/apt/sources.list and run sudo apt-get update, then run sudo apt install pulseaudio, the puseaudio 1:13.99.1-1ubuntu3.13 is installed. reboot, plug a hdmi monitor, manually select it to be active output, keep the hdmi monotor plugged and reboot, after reboot checking the active output device, it is still the hdmi audio, then run suspend and resume, check the active output device, it is still hdmi audio. Verification done on focal. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done 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/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929926] Re: [UBUNTU 21.10] qemu: target/s390x: Fix translation exception on illegal instruction
FYI - the autopkgtest on lava was flaky and is now resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929926 Title: [UBUNTU 21.10] qemu: target/s390x: Fix translation exception on illegal instruction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952859] Re: /usr/sbin/libvirtd:11:qemuStateShutdownPrepare:virStateShutdownPrepare:virNetDaemonRun:main
*** This bug is a duplicate of bug 1926122 *** https://bugs.launchpad.net/bugs/1926122 Same as bug 1926122 just a slightly different signature ** This bug has been marked a duplicate of bug 1926122 /usr/sbin/libvirtd:11:__GI___pthread_mutex_lock:virThreadPoolStop:qemuStateShutdownPrepare:virStateShutdownPrepare:virNetDaemonRun -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952859 Title: /usr/sbin/libvirtd:11:qemuStateShutdownPrepare:virStateShutdownPrepare:virNetDaemonRun:main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1952859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952859] [NEW] /usr/sbin/libvirtd:11:qemuStateShutdownPrepare:virStateShutdownPrepare:virNetDaemonRun:main
*** This bug is a duplicate of bug 1926122 *** https://bugs.launchpad.net/bugs/1926122 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding libvirt. This problem was most recently seen with package version 7.0.0-2ubuntu2.2, the problem page at https://errors.ubuntu.com/problem/a64b1a56b8d9b88431747a603259e642080dea61 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: focal hirsute impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952859 Title: /usr/sbin/libvirtd:11:qemuStateShutdownPrepare:virStateShutdownPrepare:virNetDaemonRun:main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1952859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952084] Re: snapd.seeded.service never finishes on s390x when privileged or nested
Hi Ian, If snap isn't supported/working in privileged containers that is a constraint that is ok. But while it is ok to "not work" since it is default installed in all images it should at least not block all other activity in there (which blocking the full boot is). Could I ask for making snapd.seeded (or other components if that makes more sense) to detect the situation and leave the system alone then? That is exiting with "sorry I can't" or even better having a condition that doesn't even try to start the service in that case. Setting back to new to reconsider this request. P.S. if anyone points me to an image with the change of 11058 that you referred to I'm willing to test it for you in regard to this issue here. ** Changed in: snapd (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/1952084 Title: snapd.seeded.service never finishes on s390x when privileged or nested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1952084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
** Changed in: thermald (Ubuntu) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (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/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems
** Changed in: monitoring-plugins (Ubuntu) Status: Triaged => 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/1940916 Title: Incorrectly excludes tmpfs filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
@Brian I updated the description. Do you think the information in description is enough to continue the SRU process? And the packages is uploaded to queue. Focal: https://launchpad.net/ubuntu/focal/+upload/27068997/+files/nvidia-prime_0.8.16~0.20.04.2_source.changes Hirsute: https://launchpad.net/ubuntu/hirsute/+upload/27068995/+files/nvidia-prime_0.8.16.2~0.21.04.1_source.changes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942789] Re: On-demand and RTD3 need to be separated
@Brian I updated the description. Do you think the information in description is enough to continue the SRU process? And the packages is uploaded to queue. Focal: https://launchpad.net/ubuntu/focal/+upload/27068997/+files/nvidia-prime_0.8.16~0.20.04.2_source.changes Hirsute: https://launchpad.net/ubuntu/hirsute/+upload/27068995/+files/nvidia-prime_0.8.16.2~0.21.04.1_source.changes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
@Brian I updated the description. Do you think the information in description is enough to continue the SRU process? And the packages is uploaded to queue. Focal: https://launchpad.net/ubuntu/focal/+upload/27068997/+files/nvidia-prime_0.8.16~0.20.04.2_source.changes Hirsute: https://launchpad.net/ubuntu/hirsute/+upload/27068995/+files/nvidia-prime_0.8.16.2~0.21.04.1_source.changes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896734] Re: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack
I logged it locally, and this is how much data was put out: root@tctrko1:~# cat /tmp/debug | wc -c 1179958 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896734 Title: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1896734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode combined offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have offloading feature. + * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942789] Re: On-demand and RTD3 need to be separated
** Description changed:
- RTD3 is a nvidia GPU feature to support runtime suspend.
+ [Steps to reproduce]
+ 1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
+ 2. After the installation, press enter to reboot system
+ 3. prime-select query
- On-demand would be a X offloading feature.
+ [Expected result]
+ on-demand
- They are independent, according to discussion on
- https://github.com/tseliot/ubuntu-drivers-common/issues/55.
+ [Actual result]
+ performance
- Some parts need to be adjusted, e.g.
+ ---
- ```
- # If we are dealing with NVIDIA PRIME, and runtimepm
- # is supported, enable it
- if (os.path.isfile('/run/nvidia_runtimepm_supported') and
- os.path.isfile('/usr/bin/prime-select')):
- print('Trying to select the on-demand PRIME profile')
- try:
- subprocess.call(['prime-select', 'on-demand'])
- except:
- pass
+ It's because ubiquity launches `ubuntu-drivers install --packages-list
+ ...` in live system but install each package to target storage.
- # Create the override file for gpu-manager
- with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
- f.write('# File created by ubuntu-drivers\n')
- ```
+ When installing nvidia-prime, the preinst set "on" to "/etc/prime-
+ discrete" which will be referred by gpu-manager. The gpu-manager will
+ set to performance mode.
+
+ After confirming with Alberto on Mattermost, since we don't have a
+ nvidia driver which lower than 450 version since focal.
+
+ I think we are ok to switch to on-demand mode.
---
[Impact]
- * Ubuntu will set GPU mode to performance as default which may use more power
- * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not
supported
- * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
+ * Ubuntu will set GPU mode to performance as default which may use more power
+ * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not
supported
+ * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
[Test Plan]
- * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU
driver. After the installation, reboot the system. Execute "prime-select query"
should get "on-demand"
- * On non-laptop machine. Can set GPU mode to on-demand
- * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
+ * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU
driver. After the installation, reboot the system. Execute "prime-select query"
should get "on-demand"
+ * On non-laptop machine. Can set GPU mode to on-demand
+ * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
[Where problems could occur]
- * on-demand mode supported after nvidia driver 450. And focal does not have
nvidia driver lower than 450.
- * With GPU supported RTD3 not able enable runtime PM on non-laptop. But
based on the Nvidia README, this case shall not happened.
+ * on-demand mode combined offloading and RTD3. Nvidia driver lower then 450
(nvidia-driver-390) does not supported RTD3 and only have offloading feature.
+ * With GPU supported RTD3 not able enable runtime PM on non-laptop. But
based on the Nvidia README, this case shall not happened.
[Other Info]
X-HWE-Bug: Bug #1946434
Changelogs:
nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
- [ Jeremy Szu ]
- * Set on-demand mode as default nvidia mode (LP: #1942307)
+ [ Jeremy Szu ]
+ * Set on-demand mode as default nvidia mode (LP: #1942307)
- [ Alberto Milone ]
- * prime-select:
- - Detect chassis type and enable RTD3 only
- on laptops (LP: #1942788).
- - on-demand mode doesn't need to depend on
- RTD3 (LP: #1942789).
- - Use bootvga detection when last_gfx_boot
- is not available.
- - Don't check the current profile when setting
- a profile (LP: #1946476).
- - Catch BrokenPipeError.
- - Use bootvga detection when last_gfx_boot is
- not available.
+ [ Alberto Milone ]
+ * prime-select:
+ - Detect chassis type and enable RTD3 only
+ on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+ RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+ is not available.
+ - Don't check the current profile when setting
+ a profile (LP: #1946476).
+ - Catch BrokenPipeError.
+ - Use bootvga detection when last_gfx_boot is
+ not available.
nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
- [ Jeremy Szu ]
- * Set on-demand mode as default nvidia mode (LP: #1942307)
+ [ Jeremy Szu ]
+ * Set on-demand mode as default nvidia mode
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Rick, could you please run some loadings and log the turbstat? thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
** Description changed: - As per LP: #1942307 we now set on-demand as the default. This however, - causes "prime-select on-demand", called by ubuntu-drivers, not to even - try to detect RTD3 and to enable it, since "on-demand" is already set. + [Steps to reproduce] + 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. + 2. After the installation, press enter to reboot system + 3. prime-select query - We cannot make informed choices about RTD3 in the postinstallation - script of nvidia-prime, therefore we should simply drop the check that - prime-select makes to abort if the new profile is determined to be the - same as the current profile. + [Expected result] + on-demand + + [Actual result] + performance + + --- + + It's because ubiquity launches `ubuntu-drivers install --packages-list + ...` in live system but install each package to target storage. + + When installing nvidia-prime, the preinst set "on" to "/etc/prime- + discrete" which will be referred by gpu-manager. The gpu-manager will + set to performance mode. + + After confirming with Alberto on Mattermost, since we don't have a + nvidia driver which lower than 450 version since focal. + + I think we are ok to switch to on-demand mode. --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * on-demand mode combined offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have offloading feature. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile
[Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing
hi binli， I have installed gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.6 source package,I created some different files on the desktop and saved for many times . The icons did't disappear.The issue does be fixed ** 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/1883174 Title: [SRU]Some (or all) desktop icons are missing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929926] Re: [UBUNTU 21.10] qemu: target/s390x: Fix translation exception on illegal instruction
Thanks for accepting this @SRU Team I added block-proposed-hirsute as outlined in the description. Up to testing ... ** Tags added: block-proposed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929926 Title: [UBUNTU 21.10] qemu: target/s390x: Fix translation exception on illegal instruction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. + * on-demand mode combined offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have offloading feature. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896734] Re: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack
The stack trace is the following: Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: -- Green Thread-- Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/bin/neutron-linuxbridge-agent:8 in Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `sys.exit(main())` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/neutron/cmd/eventlet/plugins/linuxbridge_neutron_agent.py:21 in main Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `agent_main.main()` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py:1055 in main Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `manager = LinuxBridgeManager(bridge_mappings, interface_mappings)` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py:93 in __init__ Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `self.check_vxlan_support()` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py:745 in check_vxlan_sup Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `if self.vxlan_ucast_supported():` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py:706 in vxlan_ucast_sup Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `ip_lib.vxlan_in_use(seg_id)):` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/neutron/agent/linux/ip_lib.py:741 in vxlan_in_use Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `interfaces = get_devices_info(namespace)` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/neutron/agent/linux/ip_lib.py:1379 in get_devices_info Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `devices = privileged.get_link_devices(namespace, **kwargs)` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/oslo_privsep/priv_context.py:247 in _wrap Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `return self.channel.remote_call(name, args, kwargs)` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/oslo_privsep/daemon.py:214 in remote_call Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `result = self.send_recv((Message.CALL.value, name, args, kwargs))` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/oslo_privsep/comm.py:172 in send_recv Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `reply = future.result()` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/oslo_privsep/comm.py:109 in result Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `self.condvar.wait()` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /usr/lib/python3.6/threading.py:295 in wait Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `waiter.acquire()` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/eventlet/semaphore.py:115 in acquire Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `hubs.get_hub().switch()` Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: /openstack/venvs/neutron-21.2.6/lib/python3.6/site-packages/eventlet/hubs/hub.py:298 in switch Dec 01 07:19:38 tctrko1 neutron-linuxbridge-agent[18892]: `return self.greenlet.switch()` In this case it looks like `privileged.get_link_devices` is what needs to be optimized which was not covered by the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896734 Title: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1896734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896734] Re: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack
Unfortunately, I'm running into this issue right now in an environment that is running `linuxbridge`. I'm going to assume the number of `VXLAN` interfaces is bubbling up that is causing this issue to occur. Also, since in linuxbridge, there are `brq` and `VXLAN` interfaces. I've got around 219 interfaces in this scenario: root@tctrko1:~# ip link | grep qlen | wc -l 219 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896734 Title: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1896734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
The .debdiff file “modemmanager_1-1.16.6-2~21.10.1-impish.debdiff” is attached for impish(21.10). ** Patch added: "modemmanager_1-1.16.6-2~21.10.1-impish.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5544543/+files/modemmanager_1-1.16.6-2~21.10.1-impish.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
The "01_modem-quectel.patch" extends the quectel:plugin to provide firmware setting status during the FW upgrading process. EM120/160 PCIe modules have been already supported without this patch. I got the confirmation from Quectel engineers about the above. For the regression test, we found 2 laptops having Quectel USB modems and did the test on these laptops. The Quectel USB modems worked with the patched ModemManager. The regression test report is attached here: "RegressionTestReport_ EM05-CE.pdf". ** Description changed: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working + --- Regression test --- + + Verify if one USB modem are still working with these patches for PCIe + modems. + [Where problems could occur] The requested update has 2 parts: 1. Informative 1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually 2. Changes are specific to Foxconn and Quectel modems 2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) In current Ubuntu's certification records for modem: * No other modem uses WWAN subsystem in kernel 5.13 * Modem's FW update is not supported via ModemManager ( < v1.18 ) There is no certificated modems can do the firmware upgrading flow for the regression test. This update should not affect existing modems. The problem would be limited to these two mentioned modems. Each carrier mapping .conf file is for a specific modem. ModemManager will load one of the carrier mapping conf files via the modem manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.) We cannot verify if the carrier mapping is correct. This relies on the manufacturer to provide the correct mapping. - The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. - Modem manufacturer confirmed that the content in the .conf file is absolutely correct. - + The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. + Modem manufacturer confirmed that the content in the .conf file is absolutely correct. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems ** Attachment added: "USB modem regression test" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5544542/+files/RegressionTestReport_%20EM05-CE.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to:
[Bug 1952839] [NEW] package libreoffice-impress 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
Public bug reported: update package is brokened ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-impress 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 1 11:21:09 2021 DuplicateSignature: package:libreoffice-impress:1:6.4.6-0ubuntu0.20.04.1 Removing libreoffice-ogltrans (1:6.4.6-0ubuntu0.20.04.1) ... dpkg: error processing package libreoffice-impress (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2021-06-07 (177 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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: libreoffice Title: package libreoffice-impress 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (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/1952839 Title: package libreoffice-impress 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1952839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752]
Created attachment 144108 New crash information added by DrKonqi gwenview (21.11.90) using Qt 5.15.2 - What I was doing when the application crashed: Attempting to open a family photo I had just exported from Darktable -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139723732405312) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139723732405312) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=139723732405312, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7f13fcc35476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f13fcc1b7b7 in __GI_abort () at abort.c:79 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952836] [NEW] Suspend not working after update to Linux 5.13.0-22
Public bug reported: I use suspend frequently, but after the last update of Linux, the restart fails. However it seems to work partly since the disk activity light is showing activities, but the screen remains black and without power. I have to power off the system by pressing the power-off button for 10 seconds. I suspended the system at 1:35 and I will include the /var/log/kern.log I hope it helps. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 01:41:18 2021 InstallationDate: Installed on 2021-10-09 (52 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-10-14 (47 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade impish third-party-packages wayland-session ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1952836/+attachment/5544519/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952836 Title: Suspend not working after update to Linux 5.13.0-22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1952836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952832] Re: internal speaker not list in sound setting when external audio device is conneceted
Update from https://bugs.launchpad.net/stella/+bug/1948777: 1) --- The Speaker in general doesn't have corresponding jack, so its availability is "unknown". When it's legacy HDA, once a Headphone is plugged, PulseAudio will disable all "unknown" profiles, so the speaker is gone in this case. When it's DMIC, the disablement of "unknown" profile is skipped because it's using UCM. 2) --- The headset jack plug may or may not have ability to determine jack type (i.e. what gets plugged in), and that creates two different behaviors: - When the hardware can determine jack types like most HP and Lenovo hardwares, libgnome-volume-control checks PA status and switches to corresponding device - When the hardware _cannot_ determine jack types like most Dell hardwares, libgnome-volume-control leaves all possible option available. For instance, when something gets plugged in, the system doesn't know it's headphone, mic, or a headset, so it has to leave all options to the user and user is responsible to choose the right device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952832 Title: internal speaker not list in sound setting when external audio device is conneceted To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952832] [NEW] internal speaker not list in sound setting when external audio device is conneceted
Public bug reported: [Summary] internal speaker not list in sound setting when external device is connected [Steps to reproduce] 1) check sound setting, internal speak is listed in sound setting --> output device 2) plug a headset in 3.5mm headphone jack (front port) 3) check sound setting 4) plug headset in line-out port 5) check sound setting [Expected result] internal speaker should list when external audio device is connected. [Actual result] plug a headset in 3.5mm headphone jack (front port) --> headphone and HDMI/DP audio are listed, no internal speaker plug a headset in line-out port --> Line-out and HDMI/DP audio are listed, no internal speaker plug a headset in 3.5mm headphone jack (front port) and a headset in line-out port --> headphone, Line-out and HDMI/DP audio are listed, no internal speaker --- $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.12 Candidate: 1:13.99.1-1ubuntu3.12 Version table: *** 1:13.99.1-1ubuntu3.12 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: oem-priority Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1948777 originate-from-1950565 stella ** Tags added: oem-priority originate-from-1950565 stella ** Tags added: originate-from-1948777 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952832 Title: internal speaker not list in sound setting when external audio device is conneceted To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Attachment added: "lp1952823.webm" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+attachment/5544516/+files/lp1952823.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Tags added: originate-from-1948923 stella -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Description changed: [Summary] - The system screen turns on for a moment after entering suspend. + The screen turns on for a moment when laptop is entering suspend. This issue happens on Dell Latitude 5421. [Steps to reproduce] 1. Enter suspend via power menu 2. Observe the display (Note that `rtcwake` may not able to reproduce this issue. `systemctl suspend` may reproduce this.) [Expected result] The screen should not turn back on if the system is going to suspend. [Actual result] When "Suspend" is clicked, screen turns off, then turns back on for a moment, then turns off before laptop entering suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Tags added: oem-priority originate-from-1952020 somerville ** Tags added: originate-from-1945730 ** Tags added: originate-from-1949668 ** Tags added: originate-from-1947975 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907782] Re: ERROR Service took too long to respond. Disconnecting client.
For me, this happens systematically after waking up from suspend (and I need to suspend my desktop computer because of energy consumption) Same "Service took too long to respond. Disconnecting client." when doing an apt update or zsys-gc.service. Restarting zsysd.service and zsysd.socket doesn't restore normal behavior. Only a reboot does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907782 Title: ERROR Service took too long to respond. Disconnecting client. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1907782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952829] 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/1952829 Title: Trackpad not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950403] Re: Grub failed to install at end of Mate installation on Dell Optiplex 390 64bit Intelx86 corei5
Hey I'm sorry. I just saw a notification. My system is working. I cannot reproduce issue. I can reinstall with my new media? I created a new install media with newer release. Thank you very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950403 Title: Grub failed to install at end of Mate installation on Dell Optiplex 390 64bit Intelx86 corei5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1950403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944505] Re: Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, can't create lock file /var/run/mysqld/mysqlx.sock.lock
[Expired for mysql-8.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mysql-8.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944505 Title: Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, can't create lock file /var/run/mysqld/mysqlx.sock.lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1944505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929346] Re: Bug in the Calamares installer resulting in no installation of the boot loader in the BIOS mode
[Expired for calamares (Ubuntu) because there has been no activity for 60 days.] ** Changed in: calamares (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929346 Title: Bug in the Calamares installer resulting in no installation of the boot loader in the BIOS mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1929346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945684] Re: mysql-server-8.0.postinst: line 191: /usr/share/mysql-common/configure-symlinks: No such file or directory
[Expired for mysql-8.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mysql-8.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945684 Title: mysql-server-8.0.postinst: line 191: /usr/share/mysql- common/configure-symlinks: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1945684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944752] Re: AER PCIe Bus Error for Asus X541UVK
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944752 Title: AER PCIe Bus Error for Asus X541UVK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952829] [NEW] Trackpad not detected
Public bug reported: I've been using Ubuntu on Fujitsu UH-X (very recent model based on 11th gen i5) with double Win/Ubuntu boot setup for a while. The trackpad has always been an issue (not on Windows though), but eventually I found a way to make it work - "sudo modprobe i2c_hid" in Terminal after login. However after update to 21.10 it stopped working, so an external USB mouse is the only option now, and, very much ironically, it stopped working too while I was writing this - it's keyboard only at the moment. So it kinda worked in Ubuntu 20+ up to 21.04, but with 21.10 it's a disaster ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vitaly 3697 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 10:51:03 2021 InstallationDate: Installed on 2021-05-15 (199 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: FUJITSU CLIENT COMPUTING LIMITED UH-X ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=b59b0c88-124c-4627-b7a9-459dc45e5695 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-19 (11 days ago) dmi.bios.date: 04/02/2021 dmi.bios.release: 1.38 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.38 dmi.board.name: FJNB2E0 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.38:bd04/02/2021:br1.38:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnUH-X:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E0:rvrA4:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK01: dmi.product.family: LNV dmi.product.name: UH-X dmi.product.sku: SK01 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952829 Title: Trackpad not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949553] Autopkgtest regression report (libdrm/2.4.107-8ubuntu1~20.04.1)
All autopkgtests for the newly accepted libdrm (2.4.107-8ubuntu1~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: mir/1.7.1-0ubuntu2 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#libdrm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949553 Title: Backport packages for 20.04.4 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951952] Re: FTBFS - python-gear enforces TLSv1.0 usage
Thanks for working on this, Athos. The debdiff looks good and I agree with the backports. I have also verified that the package builds fine with the proposed changes + openssl 3. I just have some small requests before I proceed with the upload: 1) Could you add a period at the end of each changelog entry? I like to treat them as sentences, and as such I consider that they should be properly terminated. 2) Both patches should also have the "Bug-Ubuntu" DEP-3 header in order to help determining why they're needed. 3) When I'm backporting multiple patches for a logical change like this, I like writing a changelog entry like this: * Fix FTBFS with OpenSSL 3. (LP: #1951952) - d/p/add-SNI-support.patch: Add SNI support. - d/p/do-not-force-tls-v1.patch: Do not enforce TLS v1.0 usage. I think it looks more organized and is easier to understand that the patches are part of something bigger. If you could address these points, I can proceed with the upload right away. Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951952 Title: FTBFS - python-gear enforces TLSv1.0 usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-gear/+bug/1951952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406483] Re: Possible to install (and trigger postinstall) of ca-certificates-java before Java has been installed
Tomáš, this bug is seven years old. It would be better to open a new bug. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406483 Title: Possible to install (and trigger postinstall) of ca-certificates-java before Java has been installed To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1406483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930776] Re: failing test with golang 1.16
** Changed in: golang-github-nicksnyder-go-i18n.v2 (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/1930776 Title: failing test with golang 1.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-nicksnyder-go-i18n.v2/+bug/1930776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Description changed: [Summary] The system screen turns on for a moment after entering suspend. This issue happens on Dell Latitude 5421. [Steps to reproduce] 1. Enter suspend via power menu 2. Observe the display (Note that `rtcwake` may not able to reproduce this issue. `systemctl suspend` may reproduce this.) [Expected result] - The system should not turn back on if the system is going to suspend. + The screen should not turn back on if the system is going to suspend. [Actual result] When "Suspend" is clicked, screen turns off, then turns back on for a moment, then turns off before laptop entering suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Attachment added: "nvidia-bug-report.log.gz" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+attachment/5544481/+files/nvidia-bug-report.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] [NEW] Screen blinks when entering suspend
Public bug reported: [Summary] The system screen turns on for a moment after entering suspend. This issue happens on Dell Latitude 5421. [Steps to reproduce] 1. Enter suspend via power menu 2. Observe the display (Note that `rtcwake` may not able to reproduce this issue. `systemctl suspend` may reproduce this.) [Expected result] The screen should not turn back on if the system is going to suspend. [Actual result] When "Suspend" is clicked, screen turns off, then turns back on for a moment, then turns off before laptop entering suspend. ** Affects: nvidia-graphics-drivers-470 (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/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406483] Re: Possible to install (and trigger postinstall) of ca-certificates-java before Java has been installed
The fix synced from Debian checks for JDK (or JRE) directories under /usr/lib/jvm and updates PATH with first found JRE. But it only checks hardcoded paths with java version up to Java 9. On Impish, ca- certificates-java package version is 20190909 and it is checks up to java version 11. So when installing first JDK/JRE newer than 11 the bug can be reproduced. Could you please reopen this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406483 Title: Possible to install (and trigger postinstall) of ca-certificates-java before Java has been installed To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1406483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929926] Autopkgtest regression report (qemu/1:5.2+dfsg-9ubuntu3.3)
All autopkgtests for the newly accepted qemu (1:5.2+dfsg-9ubuntu3.3) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: lava/2020.12-1ubuntu2 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#qemu [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929926 Title: [UBUNTU 21.10] qemu: target/s390x: Fix translation exception on illegal instruction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946957] Autopkgtest regression report (netplan.io/0.103-0ubuntu5~21.04.4)
All autopkgtests for the newly accepted netplan.io (0.103-0ubuntu5~21.04.4) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: netplan.io/0.103-0ubuntu5~21.04.4 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#netplan.io [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946957 Title: Unset of a subtree crashes with invalid (non existing) origin-hint To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1946957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949893] Autopkgtest regression report (netplan.io/0.103-0ubuntu5~21.04.4)
All autopkgtests for the newly accepted netplan.io (0.103-0ubuntu5~21.04.4) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: netplan.io/0.103-0ubuntu5~21.04.4 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#netplan.io [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949893 Title: new interface does not show up after dbus config apply To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1949893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952094] Re: CIFS mount error: iocharset utf8 not found
Yes, i use below in my /etc/default/grub and switch kernel during boot ``` GRUB_SAVEDEFAULT=true GRUB_DEFAULT=saved GRUB_TIMEOUT=10 ``` The dmesg for both kernel is attached. Note that in 5.4.0-91-generic kernel, i modprobe cifs and mount again manually after boot, so cifs loaded log is much later(about 200 seconds) ** Attachment added: "dmesg.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952094/+attachment/5544476/+files/dmesg.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952094 Title: CIFS mount error: iocharset utf8 not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952818] 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/1952818 Title: Fails to suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934510] Re: [MIR] fuse3 as a dependency of qemu 6.0 and GNOME apps
FYI, on open-vm-tools PR there have been some news: > This pull request is being incorporated in the next open-vm-tools release; targeted for Q1 2022. See https://github.com/vmware/open-vm- tools/pull/544/#issuecomment-972880745 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934510 Title: [MIR] fuse3 as a dependency of qemu 6.0 and GNOME apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1934510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware
Hi Mario, SRUed in Bug #1952817. Thank you very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945565 Title: [SRU] Revert amdgpu/renoir firmware To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952817] Re: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1952817 Title: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952800] Re: System freeze on unplug
Thanks for the bug report. Unfortunately you have many unsupported packages installed that are not from Ubuntu but from a PPA (LP-PPA- devacom-gnome-40). Please remove that PPA from your system and then if you continue to have problems open a new bug. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1952800 Title: System freeze on unplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1952800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: impish ** Changed in: gnome-shell (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/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948528] Re: Mouse pointer doesn't reach left edge of screen
*** This bug is a duplicate of bug 1767654 *** https://bugs.launchpad.net/bugs/1767654 It's a common problem with the GPUs in Intel Braswell chips. Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1767654, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1767654 [Intel Braswell] Cursor gets stuck on left side of the screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948528 Title: Mouse pointer doesn't reach left edge of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952748] Re: power consumption is too high, battry lasting for very short time
Thanks for the bug report. Please run 'top' in a Terminal window to find out what process is using the most CPU. ** Also affects: ubuntu Importance: Undecided Status: New ** Changed in: ubuntu Status: New => Incomplete ** Changed in: ubuntu-power-consumption 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/1952748 Title: power consumption is too high, battry lasting for very short time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1952748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952818] [NEW] Fails to suspend
Public bug reported: Occasionally my laptop fails to suspend with a lid close. I always get this message in syslog or kernal.log: kernel: [ 1947.276485] ACPI: button: The lid device is not compliant to SW_LID. But it usually continues and suspends successfully. This time there was nothing in syslog, kern.log, or dmesg after the SW_LID message. It also never locks the screen either, & this time there was a msg on the screen after I opened it up about failing to lock the screen. Description:Ubuntu 21.04 Release:21.04 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45 ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brad 1280 F pulseaudio CasperMD5CheckResult: unknown Date: Tue Nov 30 18:51:44 2021 InstallationDate: Installed on 2021-11-20 (10 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) MachineType: Dell Inc. Vostro 15 7510 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=a07e9fdf-df33-4257-913f-9fe9f42e08a9 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-41-generic N/A linux-backports-modules-5.11.0-41-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-11-29 (1 days ago) dmi.bios.date: 10/14/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0J0MWF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd10/14/2021:br1.2:svnDellInc.:pnVostro157510:pvr:sku0A82:rvnDellInc.:rn0J0MWF:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15 7510 dmi.product.sku: 0A82 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952818 Title: Fails to suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952817] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir
** No longer affects: linux (Ubuntu Jammy) ** Description changed: [Impact] On new amdgpu renoir firmware, the USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Restore the old amdgpu fw, this issue is gone. For new fw, AMD make kernel fix be ready, after backport, the issue is not reproduced on new fw. [Test] After S3 on renoir's platforms, hotplug USB, the USB3.1 devices works good. [Where problems could occur] AMD renoir platform may have issues when suspend. + + Jammy already got this commit via stable updates v5.15.3 ** Summary changed: - [SRU][I/J/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir + [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir ** Description changed: [Impact] On new amdgpu renoir firmware, the USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Restore the old amdgpu fw, this issue is gone. For new fw, AMD make kernel fix be ready, after backport, the issue is not reproduced on new fw. + Cherry-picked from stable kernel release to fix it. [Test] After S3 on renoir's platforms, hotplug USB, the USB3.1 devices works good. [Where problems could occur] AMD renoir platform may have issues when suspend. Jammy already got this commit via stable updates v5.15.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952817 Title: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
This bug was fixed in the package pulseaudio - 1:15.0+dfsg1-1ubuntu2.1 --- pulseaudio (1:15.0+dfsg1-1ubuntu2.1) impish; urgency=medium * debian/patches/gitlab_ice_error.patch: - cherry pick an upstream candidate fix for a segfault issue in the session closing handling (lp: #1942685) -- Sebastien Bacher Fri, 22 Oct 2021 12:28:32 +0200 ** Changed in: pulseaudio (Ubuntu Impish) 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/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942685] Update Released
The verification of the Stable Release Update for pulseaudio has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Checking https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e I see that there are no reports of this for 1:15.0+dfsg1-1ubuntu2.1 in Impish and, reassuringly, no reports of this for 1:15.0+dfsg1-1ubuntu3 in Jammy, either. I think that's sufficient to mark this as verified. ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly
** Package changed: gnome-shell (Ubuntu) => chromium-browser (Ubuntu) ** Changed in: chromium-browser (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952557 Title: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1952557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume
Hello Hui, or anyone else affected, Accepted pulseaudio into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952817] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1952817 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (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/1952817 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952817] [NEW] [SRU][I/J/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir
Public bug reported: [Impact] On new amdgpu renoir firmware, the USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Restore the old amdgpu fw, this issue is gone. For new fw, AMD make kernel fix be ready, after backport, the issue is not reproduced on new fw. [Test] After S3 on renoir's platforms, hotplug USB, the USB3.1 devices works good. [Where problems could occur] AMD renoir platform may have issues when suspend. ** Affects: hwe-next Importance: Undecided Assignee: AaronMa (mapengyu) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1949722 sutton ** Tags added: oem-priority originate-from-1949722 sutton ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** 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.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux-oem-5.13 (Ubuntu Impish) ** No longer affects: linux-oem-5.13 (Ubuntu Jammy) ** No longer affects: linux-oem-5.14 (Ubuntu Impish) ** No longer affects: linux-oem-5.14 (Ubuntu Jammy) ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952817 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949553] Please test proposed package
Hello Timo, or anyone else affected, Accepted libdrm into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.107-8ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949553 Title: Backport packages for 20.04.4 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949553] Re: Backport packages for 20.04.4 HWE stack
Well, that's a compelling reason. ** Changed in: libdrm (Ubuntu Focal) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949553 Title: Backport packages for 20.04.4 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951767] Re: [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Fix Committed ** Summary changed: - [SRU][I/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks + [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951767 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946847] Re: Merge bridge-utils from Debian unstable for 22.04
** Changed in: bridge-utils (Ubuntu) Milestone: ubuntu-21.12 => ubuntu-22.01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946847 Title: Merge bridge-utils from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1946847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946865] Re: Merge libapache2-mod-auth-pgsql from Debian unstable for 22.04
** Changed in: libapache2-mod-auth-pgsql (Ubuntu) Milestone: ubuntu-21.12 => ubuntu-22.01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946865 Title: Merge libapache2-mod-auth-pgsql from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-auth-pgsql/+bug/1946865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946867] Re: Merge libmemcached from Debian unstable for 22.04
** Changed in: libmemcached (Ubuntu) Milestone: ubuntu-21.12 => ubuntu-22.01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946867 Title: Merge libmemcached from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmemcached/+bug/1946867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946876] Re: Merge nagios-nrpe from Debian unstable for 22.04
** Changed in: nagios-nrpe (Ubuntu) Milestone: ubuntu-21.12 => ubuntu-22.01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946876 Title: Merge nagios-nrpe from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1946876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946884] Re: Merge openvpn from Debian unstable for 22.04
** Changed in: openvpn (Ubuntu) Milestone: ubuntu-21.12 => ubuntu-22.01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946884 Title: Merge openvpn from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1946884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946902] Re: Merge sqlparse from Debian unstable for 22.04
** Changed in: sqlparse (Ubuntu) Milestone: ubuntu-21.12 => ubuntu-22.01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946902 Title: Merge sqlparse from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlparse/+bug/1946902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946831] Re: Merge apache2 from Debian unstable for 22.04
** Changed in: apache2 (Ubuntu) Milestone: ubuntu-22.01 => ubuntu-21.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946831 Title: Merge apache2 from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1946831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931582] Re: Add LOGO to /etc/os-release
The format seems clear, from the os-release spec: "...the name of an icon as defined by freedesktop.org Icon Theme Specification" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931582 Title: Add LOGO to /etc/os-release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1931582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950477] Re: Several PHP 7.x / 8.x extension packages do not include the actual shared libraries in Ubuntu 18.04
Hi Stefan, this is text from the PPA about reporting issues: """ You can get more information about the packages at https://deb.sury.org IMPORTANT: The -backports is now required on older Ubuntu releases. BUGS: This PPA now has a issue tracker: https://deb.sury.org/#bug-reporting CAVEATS: 1. If you are using php-gearman, you need to add ppa:ondrej/pkg-gearman 2. If you are using apache2, you are advised to add ppa:ondrej/apache2 3. If you are using nginx, you are advised to add ppa:ondrej/nginx-mainline or ppa:ondrej/nginx """ Hope this helps! ** Changed in: php-imagick (Ubuntu) Status: New => Invalid ** Changed in: php-mcrypt (Ubuntu) Status: New => Invalid ** Changed in: php-xdebug (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/1950477 Title: Several PHP 7.x / 8.x extension packages do not include the actual shared libraries in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-imagick/+bug/1950477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950028] Re: FTBFS against g++ 11
** Bug watch added: Debian Bug tracker #984366 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984366 ** Also affects: thin-provisioning-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984366 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950028 Title: FTBFS against g++ 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thin-provisioning-tools/+bug/1950028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952814] [NEW] Inconsistency detected by ld.so: dl-deps.c when dlopen .so, built with --filter option
Public bug reported:
Having libFilter.so built with --filter=libFiltee.so.
Running prog-bug, which contains dlopen("libFilter.so"), you'll get
"Inconsistency detected by ld.so: dl-deps.c: 553: _dl_map_object_deps:
Assertion `map->l_searchlist.r_list[0] == map' failed!"
The issue is reproducible on Ubuntu 16.04, 18.04, 20.04, although the
dl-deps.c line number may be different.
The attached file contains full C source code, the binaries, and the
build script.
To reproduce:
1) Unzip and cd to the folder.
2) Define LD_LIBRARY_PATH
$ export LD_LIBRARY_PATH=.
3) Run correct executable prog-ok, not having dlopen call, behaves as expected.
$ prog-ok
4) Run prog-bug, which demonstrates the issue, having dlopen, and produces the
above error.
$ prog-bug
Optionally you may rebuild the binaries, using _build.sh script.
The same error appears running:
$ ldd libFilter.so
I am using Ubuntu 18.04.6 LTS with libc6 v2.27-3ubuntu1.4.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libc6 2.27-3ubuntu1.4
ProcVersionSignature: Ubuntu 4.15.0-162.170-generic 4.15.18
Uname: Linux 4.15.0-162-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 30 17:52:07 2021
Dependencies:
gcc-11-base 11.1.0-1ubuntu1~18.04.1 [origin: LP-PPA-ubuntu-toolchain-r-test]
libc6 2.27-3ubuntu1.4
libgcc-s1 11.1.0-1ubuntu1~18.04.1 [origin: LP-PPA-ubuntu-toolchain-r-test]
libgcc1 1:11.1.0-1ubuntu1~18.04.1 [origin: LP-PPA-ubuntu-toolchain-r-test]
InstallationDate: Installed on 2020-05-03 (576 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: glibc
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic dlopen libc6 third-party-packages
** Attachment added: "C source, build script, executables"
https://bugs.launchpad.net/bugs/1952814/+attachment/558/+files/ld_--filter_option.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952814
Title:
Inconsistency detected by ld.so: dl-deps.c when dlopen .so, built with
--filter option
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1952814/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584483] Re: Kubuntu live cd Destop folder widget too small.
Kubuntu no longer uses a desktop folder widget, so this issue can’t happen. ** Changed in: ubuntu Status: Incomplete => 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/1584483 Title: Kubuntu live cd Destop folder widget too small. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1584483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915678] Re: [SRU] iSCSI+Multipath: Volume attachment hungs if sessiong scanning fails
** Description changed: [Impact] - * If some commands like "iscsiadm -m session" fail, the thread can abort immediately without updating any counters like failed_logins or stopped_threads properly, because there are no try-except block to catch exceptions. - * The main thread keeps waiting until these counters are updated, and this results in stuck of volume attachment process. + * If some commands like "iscsiadm -m session" fail, the thread can abort immediately without updating any counters like failed_logins or stopped_threads properly, because there are no try-except block to catch exceptions. + * The main thread keeps waiting until these counters are updated, and this results in stuck of volume attachment process. [Test Case] - * Deploy Cinder with an iSCSI driver and multipath enabled. - - * TBC. + * Deploy Cinder with a backend that uses an iSCSI driver and configure Multipath + * Attach a volume to an instance (first attachment for a period + * See log line like: + 2021-12-01 00:23:24.044 2679 WARNING os_brick.initiator.connectors.iscsi [...] iscsiadm stderr output when getting sessions: iscsiadm: No active sessions. + * Volume attachment never completes + * Passing test: Log line appears but volume attachment succeeds. [Where problems could occur] - * Change primarily introduces error handling and doesn't change implementation details. -As such we may see an error condition logged. + * Change primarily introduces error handling and doesn't change implementation details. + As such we may see an error condition logged. [Other Info] - * - + * - --- Original Description --- Currently we execute login to iscsi portals and device discovery in multiple threads concurrently when multipath is enabled. However if some commands like "iscsiadm -m session" fail, the thread can abort immediately without updating any counters like failed_logins or stopped_threads properly, because there are no try-except block to catch exceptions. However the main thread keeps waiting until these counters are updated, and this results in stuck of volume attachment process. This issue was initially reported in downstream bug https://bugzilla.redhat.com/show_bug.cgi?id=1923975 , and maybe is caused by a bug in iscsiadm command. However we should handle the error more properly because current behavior requires operators to restart services like cinder-volume to resolve the stuck. ** Description changed: [Impact] * If some commands like "iscsiadm -m session" fail, the thread can abort immediately without updating any counters like failed_logins or stopped_threads properly, because there are no try-except block to catch exceptions. * The main thread keeps waiting until these counters are updated, and this results in stuck of volume attachment process. [Test Case] * Deploy Cinder with a backend that uses an iSCSI driver and configure Multipath - * Attach a volume to an instance (first attachment for a period - * See log line like: + * Attach a volume to an instance (first attachment for a period + * See log line like: 2021-12-01 00:23:24.044 2679 WARNING os_brick.initiator.connectors.iscsi [...] iscsiadm stderr output when getting sessions: iscsiadm: No active sessions. - * Volume attachment never completes - * Passing test: Log line appears but volume attachment succeeds. + * Volume attachment never completes + * Passing test: Log line appears but volume attachment succeeds. [Where problems could occur] * Change primarily introduces error handling and doesn't change implementation details. As such we may see an error condition logged. - - [Other Info] - - * - --- Original Description --- Currently we execute login to iscsi portals and device discovery in multiple threads concurrently when multipath is enabled. However if some commands like "iscsiadm -m session" fail, the thread can abort immediately without updating any counters like failed_logins or stopped_threads properly, because there are no try-except block to catch exceptions. However the main thread keeps waiting until these counters are updated, and this results in stuck of volume attachment process. This issue was initially reported in downstream bug https://bugzilla.redhat.com/show_bug.cgi?id=1923975 , and maybe is caused by a bug in iscsiadm command. However we should handle the error more properly because current behavior requires operators to restart services like cinder-volume to resolve the stuck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915678 Title: [SRU] iSCSI+Multipath: Volume attachment hungs if sessiong scanning fails To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915678/+subscriptions -- ubuntu-bugs mailing list
[Bug 1946613] Re: FTBFS - test failure in test_debug_tokenstream
I just ran two autopkgtests using the schroot backend. rust-proc-macro2-1.0.18-1 failed with: thread 'lifetime_invalid' panicked at '"'a#" is not a valid Ident', src/fallback.rs:695:9 rust-proc-macro2-1.0.28-1 passes for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946613 Title: FTBFS - test failure in test_debug_tokenstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-proc-macro2/+bug/1946613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888735] Re: lasagne: autopkgtest fails with newer python-mock
This package was removed from Ubuntu during the development of Hirsute. ** Changed in: lasagne (Ubuntu) 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/1888735 Title: lasagne: autopkgtest fails with newer python-mock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lasagne/+bug/1888735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946613] Re: FTBFS - test failure in test_debug_tokenstream
I'm unable to recreate this using autopkgtest with a qemu backend and package version 1.0.28-1 but its still clearly failing in our autopkgtest environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946613 Title: FTBFS - test failure in test_debug_tokenstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-proc-macro2/+bug/1946613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952800] Re: System freeze on unplug
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952800 Title: System freeze on unplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1952800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920802] Re: autopkgtest fails in hirsute
The latest version of golang-github-rogpeppe-go-internal actually FTBFS in Jammy, so I'm setting this to Invalid to avoid presenting the wrong information on the excuses report. ** Changed in: golang-github-rogpeppe-go-internal (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/1920802 Title: autopkgtest fails in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-rogpeppe-go-internal/+bug/1920802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Hi guys, I'm pretty new to linux (finally decided to get rid of windows after many years). I'm runnig on Ubuntu 21.10 now... I have Asus Zenbook 14 UX431DA which originally came with standard touchpad with fingerprint sensor. So I decided to buy numpad mod hardware piece for my notebook. Succesfully installed yesterday, also did install driver package. Everything is working correctly but without backlight. When I press the numlock button on it, I can type the numbers and symbols, but I'm not able to toggle the brightness (backlight), so I don't see anything on the touchpad. As I am working a lot in excel I really need to get a numpad working properly. So I hope that somebody could help me with this. Thanks, Zee -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware
@Mario The 5.13 kernel will be replaced by 5.14 soon. I will try to SRU it to 5.13 kernel if 5.13 lives long, let me double confirm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945565 Title: [SRU] Revert amdgpu/renoir firmware To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938948] Re: autopkgtest failure due to timeout on rollup-plugin-node-polyfills
In Jammy node-rollup-plugin-node-polyfills is now failing on multiple architectures, additionally running it on a system with more memory does not help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938948 Title: autopkgtest failure due to timeout on rollup-plugin-node-polyfills To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/node-rollup-plugin-node-polyfills/+bug/1938948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944086] Re: rsyslogd crashed with SIGABRT in IO_validate_vtable()
** Information type changed from Private to Public ** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944086 Title: rsyslogd crashed with SIGABRT in IO_validate_vtable() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1944086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941714] Re: rsyslogd crashed with SIGABRT in __vfprintf_internal()
*** This bug is a duplicate of bug 1944086 *** https://bugs.launchpad.net/bugs/1944086 ** This bug has been marked a duplicate of private bug 1944086 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941714 Title: rsyslogd crashed with SIGABRT in __vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1941714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951161] Re: Please merge shadow 1:4.8.1-2 (main) from Debian unstable
This bug was fixed in the package shadow - 1:4.8.1-2ubuntu1
---
shadow (1:4.8.1-2ubuntu1) jammy; urgency=low
* Merge from Debian unstable (LP: #1951161). Remaining changes:
- debian/login.defs:
+ Update documentation of USERGROUPS_ENAB: with pam_umask, the UPG
handling does not only apply to "former (pre-PAM) uses".
+ Update documentation of UMASK: Explain that USERGROUPS_ENAB
will modify this default for UPGs.
+ Enable private home directories by default
- debian/{source_shadow.py,login.install}: Add apport hook
- debian/patches/1010_extrausers.patch: Add support to passwd for
libnss-extrausers
- debian/patches/1011_extrausers_toggle.patch: extrausers support for
useradd and groupadd
- debian/patches/1014_extrausers_delgroup.patch
+ add --extrausers option to "groupdel"
- debian/patches/1013_extrausers_deluser.patch
+ add --extrausers option to "userdel"
- debian/patches/1012_extrausers_chfn.patch
+ add support for --extrausers to the chfn tool
- debian/patches/1015_add_zsys_support.patch
+ Call zsys to handle home directory if available.
- debian/patches/1016_extrausers_gpasswd.patch
+ Add support for extrausers in gpasswd.
- debian/patches/506_relaxed_usernames.patch
+ disallow purely numeric usernames
* Dropped changes, included in Debian:
- debian/passwd.maintscripts: Clean up upstart configuration
-- William 'jawn-smith' Wilson Mon, 15 Nov
2021 16:13:44 -0600
** Changed in: shadow (Ubuntu)
Status: Confirmed => 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/1951161
Title:
Please merge shadow 1:4.8.1-2 (main) from Debian unstable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952674] Re: Kernel 5.13 fails to work with lots of hardware (HP Zbook)
Here the dmesg for a 3400G machine with iGPU only where there is no crash with the HWE kernel 5.13. That's Zen+ instead of Zen2 and Picasso iGPU instead of Renoir. ** Attachment added: "dmesg-kernel-5.13-3400G.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1952674/+attachment/556/+files/dmesg-kernel-5.13-3400G.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952674 Title: Kernel 5.13 fails to work with lots of hardware (HP Zbook) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1952674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
