[Bug 2078745] Re: Unable to upgrade to 24.04 due to error: "The package 'postgresql-14-postgis-3' is marked for removal but it is in the removal deny list."
In my case, the installer allowed me to remove postgres-14 and complete the upgrade. Then once running on 24.04 I wondered where my database had gone. I found the new database postgres-16 on port 5433 but my data was on the old cluster without a recent backup. The process is clear to me now, but it wasn't clear enough during the installation to avoid the bear trap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078745 Title: Unable to upgrade to 24.04 due to error: "The package 'postgresql-14-postgis-3' is marked for removal but it is in the removal deny list." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975669] Re: USB devices are not working on Raspberry pi zero 2 with arm64 image
I got some more accessories to try yesterday, turns out the problem is related to micro usb to usb type-A/tupe-C adapter, only one of the five I tried worked both in armhf and arm64 images. With that one, everything looks fine now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975669 Title: USB devices are not working on Raspberry pi zero 2 with arm64 image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1975669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975669] [NEW] USB devices are not working on Raspberry pi zero 2 with arm64 image
Public bug reported: [Summary] USB devices are not working on Raspberry pi zero 2 with arm64 image. I have tried following devices with adapters: rpiz2 micro usb -> usb type-c -> usb type-c storage rpiz2 micro usb -> usb type-c -> usb type-a -> usb type-a storage rpiz2 micro usb -> usb type-c -> usb type-c ethernet dongle rpiz2 micro usb -> usb type-c -> usb type-a -> usb type-a ethernet dongle I have checked both 20.04 and 22.04, all these devices work fine with armhf images but not work with arm64 images. And all these devices work fine on Raspberry pi 3a+ with armhf and arm64 images [Steps to reproduce] 1. Flash image to SD card 2. Boot into system 3. Check usb device with lsusb [Expected result] All usb devices are working fine. [Actual result] USB devices are not working on Raspberry pi zero 2 with arm64 image. [Additional information] SKU: Raspberry pi zero 2 Kernel: 5.15.0-1008-raspi ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-raspi 5.15.0.1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 25 04:00 seq crw-rw 1 root audio 116, 33 May 25 04:00 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-1008-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Wed May 25 06:36:24 2022 ImageMediaBuild: 20220419 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:6A:C0:29 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-1008-raspi N/A linux-backports-modules-5.15.0-1008-raspi N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: bcm2835_codec bcm2835_isp bcm2835_v4l2 vc_sm_cma bcm2835_mmal_vchiq snd_bcm2835 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image jammy raspi-image staging uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975669 Title: USB devices are not working on Raspberry pi zero 2 with arm64 image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1975669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
I've installed Evolution 3.44.1-0ubuntu1 from the proposed updates and text now displays background as expected. This is resolved 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/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
Hi, Sure, the output is as follows: gsettings get org.gnome.desktop.interface gtk-theme 'Yaru-blue-dark' gsettings get org.gnome.desktop.interface color-scheme 'prefer-dark' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967020] Re: WebKitWebProcess crashed with SIGSEGV
Evolution-3.44.0-1ubuntu1 in Jammy proposed fixes the issue. ** Changed in: webkit2gtk (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/1967020 Title: WebKitWebProcess crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
This is not a bug rather a regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
This bug may be related to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1272001 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967020] Re: WebKitWebProcess crashed with SIGSEGV
Attached crash file. ** Attachment added: "_usr_bin_evolution.1000.crash" https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+attachment/5581391/+files/_usr_bin_evolution.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967020 Title: WebKitWebProcess crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967020] Re: WebKitWebProcess crashed with SIGSEGV
Apr 19 16:00:48 ROC-Cube systemd[4105]: app-gnome-org.inkscape.Inkscape-29481.scope: Consumed 25.374s CPU time. Apr 19 16:00:51 ROC-Cube kernel: [ 2524.702434] evolution[28125]: segfault at 0 ip 7f6cf7dc4536 sp 7ffc3fc482e8 error 4 in libwebkit2gtk-4.0.so.37.56.4[7f6cf7872000+2739000] Apr 19 16:00:51 ROC-Cube kernel: [ 2524.702443] Code: 89 e7 ff d3 eb d2 e8 c9 e2 ab ff 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 8b 47 28 48 8d 15 c1 2a 00 00 48 8b b8 a8 01 00 00 <48> 8b 07 48 8b 40 30 48 39 d0 75 06 31 c0 c3 0f 1f 00 ff e0 66 0f Apr 19 16:00:51 ROC-Cube systemd[1]: Starting Process error reports when automatic reporting is enabled... Apr 19 16:00:51 ROC-Cube systemd[1]: Started crash report submission. Apr 19 16:00:51 ROC-Cube whoopsie[33941]: [16:00:51] Using lock path: /var/lock/whoopsie/lock Apr 19 16:00:51 ROC-Cube systemd[1]: whoopsie.service: Deactivated successfully. Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_opt_ExpanDrive_SharedSupport_exfs.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_share_teams_teams.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_bin_nextcloud.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_bin_gnome-calendar.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_libexec_gnome-shell-calendar-server.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_lib_x86_64-linux-gnu_webkit2gtk-4.0_WebKitWebProcess.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube systemd[1]: Started crash report submission. Apr 19 16:00:51 ROC-Cube whoopsie[33945]: [16:00:51] Using lock path: /var/lock/whoopsie/lock Apr 19 16:00:51 ROC-Cube systemd[1]: whoopsie.service: Deactivated successfully. Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:Collecting info for /var/crash/_usr_bin_evolution.1000.crash... Apr 19 16:00:54 ROC-Cube whoopsie-upload-all[33940]: INFO:root:Marking /var/crash/_usr_bin_evolution.1000.crash for whoopsie upload Apr 19 16:00:54 ROC-Cube whoopsie-upload-all[33940]: INFO:root:Waiting for whoopsie to upload reports (timeout: 20 s) Apr 19 16:00:54 ROC-Cube whoopsie-upload-all[33940]: INFO:root: missing (remaining: 20 s): /var/crash/_usr_bin_evolution.1000.uploaded Apr 19 16:00:54 ROC-Cube systemd[1]: Started crash report submission. Apr 19 16:00:54 ROC-Cube whoopsie[35085]: [16:00:54] Using lock path: /var/lock/whoopsie/lock Apr 19 16:00:54 ROC-Cube whoopsie[35085]: [16:00:54] Parsing /var/crash/_usr_bin_evolution.1000.crash. Apr 19 16:00:54 ROC-Cube whoopsie[35085]: [16:00:54] Uploading /var/crash/_usr_bin_evolution.1000.crash. Apr 19 16:00:55 ROC-Cube systemd[4105]: app-gnome-org.gnome.Evolution-28125.scope: Consumed 15.552s CPU time. Apr 19 16:00:57 ROC-Cube whoopsie[35085]: [16:00:57] Sent; server replied with: No error Apr 19 16:00:57 ROC-Cube whoopsie[35085]: [16:00:57] Response code: 200 Apr 19 16:00:57 ROC-Cube whoopsie[35085]: [16:00:57] Reported OOPS ID 14381f7c-bfa6-11ec-8ad4-fa163e993415 Apr 19 16:00:57 ROC-Cube systemd[1]: whoopsie.service: Deactivated successfully. Apr 19 16:01:04 ROC-Cube whoopsie-upload-all[33940]: INFO:root:All reports uploaded successfully Apr 19 16:01:04 ROC-Cube systemd[1]: apport-autoreport.service: Deactivated successfully. Apr 19 16:01:04 ROC-Cube systemd[1]: Finished Process error reports when automatic reporting is enabled. Apr 19 16:01:04 ROC-Cube systemd[1]: apport-autoreport.service: Consumed 2.810s CPU time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967020 Title: WebKitWebProcess crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967020] Re: WebKitWebProcess crashed with SIGSEGV
Actually, a correction. Evolution starts fine but if I go to type an email (or reply) the editor window is blank. Closing the new or reply message window THEN crashes Evolution. ** Attachment added: "image832.png" https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+attachment/5581390/+files/image832.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967020 Title: WebKitWebProcess crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967020] Re: WebKitWebProcess crashed with SIGSEGV
I'm also having this with Jammy. I am using Wayland with the AMD opensource GPU drivers. The following appears in syslog: Apr 19 15:45:56 ROC-Cube kernel: [ 1629.677203] evolution[23936]: segfault at 0 ip 7fef9c195536 sp 7ffe2be1cf88 error 4 in libwebkit2gtk-4.0.so.37.56.4[7fef9bc43000+2739000] Apr 19 15:45:56 ROC-Cube kernel: [ 1629.677216] Code: 89 e7 ff d3 eb d2 e8 c9 e2 ab ff 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 8b 47 28 48 8d 15 c1 2a 00 00 48 8b b8 a8 01 00 00 <48> 8b 07 48 8b 40 30 48 39 d0 75 06 31 c0 c3 0f 1f 00 ff e0 66 0f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967020 Title: WebKitWebProcess crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
One quick question. On 21.10 the preview rendered with a white background even when using a dark theme. Please see the attached. And thanks for looking at this bug/question. I appreciate it. :) G. ** Attachment added: "White background previously with 21.10" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969251/+attachment/5581004/+files/Screenshot%20from%202022-04-16%2011-13-33.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] [NEW] Evolution dark background in HTML message (Jammy 22.04)
Public bug reported: When using a dark theme in Jammy (22.04) beta, Evolution will display a dark background with black text for HTML emails in the message preview. Previously in Impish, the background was white with dark text. This only occurs when using a dark theme, If you use a light theme, the background of the email is also light. Release: Ubuntu Jammy Jellyfish (development branch) Please see attached screenshot. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Attachment added: "Example of HTML email rendering using Jammy 22.04" https://bugs.launchpad.net/bugs/1969251/+attachment/5580994/+files/image832.png ** Summary changed: - Evolution dark background in HTML message + Evolution dark background in HTML message (Jammy 22.04) ** Package changed: evolution (Ubuntu) => yaru-theme (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1964263] Re: package linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
It was an error on my part, I resolved the issue Sent from my iPhone > On Mar 11, 2022, at 1:00 PM, Brian Murray <1964...@bugs.launchpad.net> wrote: > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It seems that there was an error on your system when > trying to update a package on your system due to a lack of free space on > your system. Please resolve this situation manually and try the update > again. > > ** Changed in: initramfs-tools (Ubuntu) > Status: Confirmed => Invalid > > ** Changed in: initramfs-tools (Ubuntu) > Importance: Undecided => Low > > ** Tags added: no-free-space > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1964263 > > Title: > package linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 failed to > install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools > exited with return code 1 > > Status in initramfs-tools package in Ubuntu: > Invalid > > Bug description: > I'm unable to download newer version of Python > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 > ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 > Uname: Linux 5.13.0-30-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.21 > Architecture: amd64 > CasperMD5CheckResult: skip > Date: Tue Mar 8 14:36:20 2022 > ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with > return code 1 > Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, > 3.8.2-0ubuntu2 > PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 > RelatedPackageVersions: > dpkg 1.19.7ubuntu3 > apt 2.0.6 > SourcePackage: initramfs-tools > Title: package linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 failed to > install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited > with return code 1 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964263/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964263 Title: package linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964263] [NEW] package linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: I'm unable to download newer version of Python ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 8 14:36:20 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964263 Title: package linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962234] [NEW] Don't know
Public bug reported: Don't know ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.32 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 CrashDB: ubuntu Date: Fri Feb 25 10:11:00 2022 InstallationDate: Installed on 2018-01-27 (1489 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2022-02-24 (0 days ago) VarLogDistupgradeAptlog: Log time: 2022-02-25 10:09:47.784298 Log time: 2022-02-25 10:10:18.349828 Log time: 2022-02-25 10:10:56.087760 Log time: 2022-02-25 10:11:06.695532 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962234 Title: Don't know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1962234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961203] Re: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+
ubuntu@ubuntu:~$ sudo apt install linux-firmware Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: linux-firmware 1 upgraded, 0 newly installed, 0 to remove and 87 not upgraded. Need to get 199 MB of archives. After this operation, 1,594 kB of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports impish-updates/main arm64 linux-firmware all 1.201.4 [199 MB] Fetched 199 MB in 4min 56s (671 kB/s) (Reading database ... 82311 files and directories currently installed.) Preparing to unpack .../linux-firmware_1.201.4_all.deb ... Unpacking linux-firmware (1.201.4) over (1.201) ... Setting up linux-firmware (1.201.4) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 update-initramfs: failed for /boot/initrd.img-5.13.0-1008-raspi with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-firmware needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961203 Title: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1961203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961203] Re: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+
** Tags added: sru ** Description changed: [Description] Failed to upgrade linux-firmware on rpi3a+ [Steps to reproduce] 1. Flash following image on rpi3a+: - https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz + https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt install linux-firmware [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ - Kernel Version: 5.13.0-1016-raspi + Kernel Version: 5.13.0-1008-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961203 Title: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1961203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961186] Re: [SRU][Impish] Unable to boot rpi3a+ after apt dist-upgrade
** Description changed: [Description] Unable to boot rpi3a+ after apt dist-upgrade [Steps to reproduce] 1. Flash following image on rpi3a+: - https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz?_ga=2.116775055.84446.1645092439-394390262.1600931043 + https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt dist-upgrade -y 5. Reboot the system 6. Check kernel version using "uname -a" [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] + Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ Kernel Version: 5.13.0-1016-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961186 Title: [SRU][Impish] Unable to boot rpi3a+ after apt dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1961186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961203] [NEW] [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+
Public bug reported: [Description] Failed to upgrade linux-firmware on rpi3a+ [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt install linux-firmware [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ Kernel Version: 5.13.0-1016-raspi ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Package changed: linux-raspi (Ubuntu) => linux-firmware (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961203 Title: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1961203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961186] Re: [SRU][Impish] Unable to boot rpi3a+ after apt dist-upgrade
** Summary changed: - [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade + [SRU][Impish] Unable to boot rpi3a+ after apt dist-upgrade ** Description changed: [Description] - Unable to boot rpi3+ after apt dist-upgrade + Unable to boot rpi3a+ after apt dist-upgrade [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz?_ga=2.116775055.84446.1645092439-394390262.1600931043 2. Boot into system 3. sudo apt update 4. sudo apt dist-upgrade -y 5. Reboot the system 6. Check kernel version using "uname -a" [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Hardware: rpi3a+ Kernel Version: 5.13.0-1016-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961186 Title: [SRU][Impish] Unable to boot rpi3a+ after apt dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1961186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961186] Re: [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade
** Tags added: sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961186 Title: [SRU][Impish] Unable to boot rpi3a+ after apt dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1961186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961186] Re: [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade
** Package changed: linux-firmware-raspi2 (Ubuntu) => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961186 Title: [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1961186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961186] Re: [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade
** Summary changed: - [SRU] Unable to boot rpi3+ after apt dist-upgrade + [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961186 Title: [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1961186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961186] Re: [SRU] Unable to boot rpi3+ after apt dist-upgrade
** Summary changed: - [SRU] Kernel is not upgraded on rpi3+ when running apt dist-upgrade + [SRU] Unable to boot rpi3+ after apt dist-upgrade ** Description changed: [Description] - Kernel is not upgraded on rpi3a+ when running apt dist-upgrade + Unable to boot rpi3+ after apt dist-upgrade [Steps to reproduce] 1. Flash following image on rpi3a+: - https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz?_ga=2.116775055.84446.1645092439-394390262.1600931043 + https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz?_ga=2.116775055.84446.1645092439-394390262.1600931043 2. Boot into system 3. sudo apt update 4. sudo apt dist-upgrade -y 5. Reboot the system 6. Check kernel version using "uname -a" [Actual result] - Error when upgrading kernel, and kernel is not upgraded + Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] - Kernel is upgraded to correct version + System can boot up and kernel is upgraded to correct version [Additional information] Hardware: rpi3a+ Kernel Version: 5.13.0-1016-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961186 Title: [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1961186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961186] Re: [SRU] Kernel is not upgraded on rpi3+ when running apt dist-upgrade
** Attachment added: "dist-upgrade.log" https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1961186/+attachment/5561576/+files/dist-upgrade.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961186 Title: [SRU] Unable to boot rpi3+ after apt dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1961186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961186] [NEW] [SRU] Unable to boot rpi3+ after apt dist-upgrade
Public bug reported: [Description] Unable to boot rpi3+ after apt dist-upgrade [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz?_ga=2.116775055.84446.1645092439-394390262.1600931043 2. Boot into system 3. sudo apt update 4. sudo apt dist-upgrade -y 5. Reboot the system 6. Check kernel version using "uname -a" [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Hardware: rpi3a+ Kernel Version: 5.13.0-1016-raspi ** Affects: linux-firmware-raspi2 (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/1961186 Title: [SRU] Unable to boot rpi3+ after apt dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1961186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950064] Re: [Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi
** Description changed: [Description] Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi [Steps to reproduce] 1. Flash image (see additional information) 2. Boot into system 3. apt dist-upgrade all packages and reboot 4. Enable proposed repository - 5. apt dist-upgrade all packages and reboot + 5. apt install linux-raspi + 6. Reboot [Actual result] Device does not boot into system [Expected result] Boot into system successfully [Additional information] Hardware: rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ Image: ubuntu-21.04-preinstalled-server-arm64+raspi.img.xz ubuntu-21.04-preinstalled-server-armhf+raspi.img.xz Kernel Version: 5.11.0-1022.23-raspi ** Attachment added: "console log from rpi3b" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+attachment/5538785/+files/hirsute_console_rpi3b.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950064 Title: [Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950117] Re: [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi
** Tags added: sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950117 Title: [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950064] Re: [Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi
** Tags added: sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950064 Title: [Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950064] Re: [Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi
** Summary changed: - Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi + [Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950064 Title: [Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950117] Re: [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi
** Attachment added: "console log from rpi3b" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950117/+attachment/5538767/+files/impish_console_rpi3b.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950117 Title: [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950117] Re: [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi
** Attachment added: "console log from cm3+" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950117/+attachment/5538768/+files/impish_console_cm3p.log ** Description changed: [Description] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi. Fail rate: 12 times out of 14 attempts [Steps to reproduce] 1. Flash image (see additional information) 2. Boot into system 3. apt dist-upgrade all packages and reboot 4. Enable proposed repository - 5. apt dist-upgrade all packages and reboot + 5. apt install linux-raspi + 6. Reboot [Actual result] Device does not boot into system [Expected result] Boot into system successfully [Additional information] Hardware: rpi3 and cm3+ Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz -ubuntu-21.10-preinstalled-server-armhf+raspi.img.xz + ubuntu-21.10-preinstalled-server-armhf+raspi.img.xz Kernel Version: 5.13.0-1010.11-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950117 Title: [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950064] Re: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi
** Description changed: [Description] Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi [Steps to reproduce] 1. Flash image (see additional information) 2. Boot into system 3. apt dist-upgrade all packages and reboot 4. Enable proposed repository - 5. Upgrade kernel to 5.11.0-1022 - 4. Reboot the system + 5. apt dist-upgrade all packages and reboot [Actual result] Device does not boot into system [Expected result] Boot into system successfully [Additional information] Hardware: rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ Image: ubuntu-21.04-preinstalled-server-arm64+raspi.img.xz ubuntu-21.04-preinstalled-server-armhf+raspi.img.xz Kernel Version: 5.11.0-1022.23-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950064 Title: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950117] [NEW] [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi
Public bug reported: [Description] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi. Fail rate: 12 times out of 14 attempts [Steps to reproduce] 1. Flash image (see additional information) 2. Boot into system 3. apt dist-upgrade all packages and reboot 4. Enable proposed repository 5. apt dist-upgrade all packages and reboot [Actual result] Device does not boot into system [Expected result] Boot into system successfully [Additional information] Hardware: rpi3 and cm3+ Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz ubuntu-21.10-preinstalled-server-armhf+raspi.img.xz Kernel Version: 5.13.0-1010.11-raspi ** Affects: linux-raspi (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/1950117 Title: [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950064] Re: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi
** Attachment added: "console log from rpi3a+" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+attachment/5538596/+files/console_rpi3ap.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950064 Title: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950064] Re: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi
** Attachment added: "console log from rpi2" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+attachment/5538595/+files/console_rpi2.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950064 Title: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950064] Re: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi
** Attachment added: "console log from cm3+" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+attachment/5538594/+files/console_cm3p.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950064 Title: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950064] Re: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi
** Attachment added: "console log from rpi3b+" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+attachment/5538593/+files/console_log.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950064 Title: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950064] [NEW] Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi
Public bug reported: [Description] Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi [Steps to reproduce] 1. Flash image (see additional information) 2. Boot into system 3. apt dist-upgrade all packages and reboot 4. Enable proposed repository 5. Upgrade kernel to 5.11.0-1022 4. Reboot the system [Actual result] Device does not boot into system [Expected result] Boot into system successfully [Additional information] Hardware: rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ Image: ubuntu-21.04-preinstalled-server-arm64+raspi.img.xz ubuntu-21.04-preinstalled-server-armhf+raspi.img.xz Kernel Version: 5.11.0-1022.23-raspi ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: [Description] Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi [Steps to reproduce] 1. Flash image (see additional information) 2. Boot into system 3. apt dist-upgrade all packages and reboot 4. Enable proposed repository 5. Upgrade kernel to 5.11.0-1022 4. Reboot the system [Actual result] Device does not boot into system [Expected result] Boot into system successfully [Additional information] Hardware: rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ - Image: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz - https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-armhf+raspi.img.xz + Image: ubuntu-21.04-preinstalled-server-arm64+raspi.img.xz + ubuntu-21.04-preinstalled-server-armhf+raspi.img.xz Kernel Version: 5.11.0-1022.23-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950064 Title: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912866] Re: [18.04.3] WLAN device disappear after upgrading linux-firmware-raspi2
Hi Varisht, rpi4b is not supported by this 4.15 kernel, please try ubuntu 18.04.6 or 20.04 image: https://ubuntu.com/download/raspberry-pi ** Tags added: sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912866 Title: [18.04.3] WLAN device disappear after upgrading linux-firmware-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1912866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945291] [NEW] package console-data 2:1.12-8 failed to install/upgrade: installed console-data package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1887520 *** https://bugs.launchpad.net/bugs/1887520 Public bug reported: I get an error at every update of the following form [[ Setting up console-data (2:1.12-8) ... Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/Client/ConfModule.pm line 121, line 374. Looking for keymap to install: console-data/keymap/full doesn't exist Usage: install-keymap [ keymap_file | NONE | KERNEL ] dpkg: error processing package console-data (--configure): installed console-data package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of console-common: console-common depends on console-data; however: Package console-data is not configured yet. ]] This has been happening for over a month now. I'm using Ubuntu 20.04.3 LTS. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: console-data 2:1.12-8 ProcVersionSignature: Ubuntu 5.4.0-86.97-generic 5.4.133 Uname: Linux 5.4.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 28 08:26:10 2021 ErrorMessage: installed console-data package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-10-20 (1803 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: console-data Title: package console-data 2:1.12-8 failed to install/upgrade: installed console-data package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-02-23 (216 days ago) ** Affects: console-data (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945291 Title: package console-data 2:1.12-8 failed to install/upgrade: installed console-data package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-data/+bug/1945291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912866] Re: [18.04.3] WLAN device disappear after upgrading linux-firmware-raspi2
** Description changed: [Description] WLAN device disappear after upgrading linux-firmware-raspi2 Package Version: 1.20200601+arm64-0ubuntu2~18.04.1 [upgradable from: 1.20190215-0ubuntu0.18.04.1] [Steps to reproduce] 1. Flash image http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04.3-preinstalled-server-arm64+raspi3.img.xz 2. Boot into system 3. Upgrade linux-firmware-raspi2 4. Reboot the system 5. Check wireless device using "ip a" - [Expected result] + [Actual result] WLAN device disappear after upgrading linux-firmware-raspi2 - [Actual result] + [Expected result] WLAN device works fine [Additional information] Hardware: rpi3b, rpi3b+, rpi3a+ Kernel Version: 4.15.0-1077-raspi2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912866 Title: [18.04.3] WLAN device disappear after upgrading linux-firmware-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1912866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923053] Re: [SRU] nextcloud crashed with SIGSEGV.
$ apt-cache policy nextcloud-desktop nextcloud-desktop: Installed: 3.1.1-1ubuntu1.1 Candidate: 3.1.1-1ubuntu1.1 Version table: *** 3.1.1-1ubuntu1.1 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 3.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages Works 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/1923053 Title: [SRU] nextcloud crashed with SIGSEGV. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918450] [NEW] Ubuntu 20 install failed on grub install
Public bug reported: Ubuntu 20 being installed over previous Ubuntu 18 installation. Dual Boot computer with Windows 10. Installation works fine until grub install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 10 17:06:20 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918450 Title: Ubuntu 20 install failed on grub install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1918450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912905] [NEW] Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server image
Public bug reported: [Description] Can't find WLAN device on Raspberry Pi CM4L with 20.10 armhf preinstall server image. This only happens on armhf image. [Steps to reproduce] 1. Flash image http://cdimage.ubuntu.com/ubuntu/releases/groovy/release/ubuntu-20.10-preinstalled-server-armhf+raspi.img.xz 2. Boot into system 5. Check wireless device using "ip a" [Expected result] Can't find WLAN device [Actual result] WLAN device works fine [Additional information] Hardware: RPI-CM4L Kernel Version: 5.8.0-1006-raspi, 5.8.0-1012-raspi, 5.8.0-1013-raspi ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: [Description] - Can't find WLAN device on Raspberry Pi CM4L with 20.10 armhf preinstall server image + Can't find WLAN device on Raspberry Pi CM4L with 20.10 armhf preinstall server image. + This only happens on armhf image. [Steps to reproduce] 1. Flash image http://cdimage.ubuntu.com/ubuntu/releases/groovy/release/ubuntu-20.10-preinstalled-server-armhf+raspi.img.xz 2. Boot into system 5. Check wireless device using "ip a" [Expected result] Can't find WLAN device [Actual result] WLAN device works fine [Additional information] Hardware: RPI-CM4L Kernel Version: 5.8.0-1006-raspi, 5.8.0-1012-raspi, 5.8.0-1013-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912905 Title: Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1912905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912385] Re: No wlan interfaces found on CM4 after firmware update
Also happens on 20.04 armhf released image after dist-upgrade everything with proposed repository enabled. Image: ubuntu-20.04.1-preinstalled-server-armhf+raspi.img.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912385 Title: No wlan interfaces found on CM4 after firmware update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1912385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912385] Re: No wlan interfaces found on CM4 after firmware update
Also happens on 20.04 armhf and 20.10 armhf released image after dist- upgrade everything with proposed repository enabled. Image: ubuntu-20.04.1-preinstalled-server-armhf+raspi.img.xz ubuntu-20.10-preinstalled-server-armhf+raspi.img.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912385 Title: No wlan interfaces found on CM4 after firmware update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1912385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912866] [NEW] [18.04.3] WLAN device disappear after upgrading linux-firmware-raspi2
Public bug reported: [Description] WLAN device disappear after upgrading linux-firmware-raspi2 Package Version: 1.20200601+arm64-0ubuntu2~18.04.1 [upgradable from: 1.20190215-0ubuntu0.18.04.1] [Steps to reproduce] 1. Flash image http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04.3-preinstalled-server-arm64+raspi3.img.xz 2. Boot into system 3. Upgrade linux-firmware-raspi2 4. Reboot the system 5. Check wireless device using "ip a" [Expected result] WLAN device disappear after upgrading linux-firmware-raspi2 [Actual result] WLAN device works fine [Additional information] Hardware: rpi3b, rpi3b+, rpi3a+ Kernel Version: 4.15.0-1077-raspi2 ** Affects: linux-firmware-raspi2 (Ubuntu) Importance: Undecided Status: New ** Description changed: [Description] WLAN device disappear after upgrading linux-firmware-raspi2 Package Version: 1.20200601+arm64-0ubuntu2~18.04.1 [upgradable from: 1.20190215-0ubuntu0.18.04.1] [Steps to reproduce] - 1. Flash image + 1. Flash image http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04.3-preinstalled-server-arm64+raspi3.img.xz 2. Boot into system 3. Upgrade linux-firmware-raspi2 4. Reboot the system 5. Check wireless device using "ip a" [Expected result] WLAN device disappear after upgrading linux-firmware-raspi2 [Actual result] WLAN device works fine [Additional information] Hardware: rpi3b, rpi3b+, rpi3a+ Kernel Version: 4.15.0-1077-raspi2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912866 Title: [18.04.3] WLAN device disappear after upgrading linux-firmware-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1912866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908713] Re: Fix suspend error of SOF driver
** Tags added: cert-sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908713 Title: Fix suspend error of SOF driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909249] Re: Wireless device disappear after upgrading to b/4.15.0-1072.76-raspi2 kernel
** Changed in: linux-raspi2 (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/1909249 Title: Wireless device disappear after upgrading to b/4.15.0-1072.76-raspi2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1909249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909249] [NEW] Wireless device disappear after upgrading to b/4.15.0-1072.76-raspi2 kernel
Public bug reported: Wireless device disappear after upgrading to b/4.15.0-1072.76-raspi2 kernel This also happens on all current b/4.15.0 kernels after 1072.76. [Reproduce steps] 1. Flash image ubuntu-18.04.3-preinstalled-server-armhf+raspi3.img.xz 2. Upgrade to latest kernel 3. Reboot 4. Check output of command: ip a [Results] Expected: Can find wlan0 device Actual: Can't find wlan0 device [Machine information] Can reproduce on following models: Raspberry Pi 3b Raspberry Pi 3b+ Raspberry Pi 3a+ ** Affects: linux-raspi2 (Ubuntu) Importance: Critical Status: New ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909249 Title: Wireless device disappear after upgrading to b/4.15.0-1072.76-raspi2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1909249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902774] [NEW] No way to change checker background
Public bug reported: Bug appeared after upgrading Ubuntu 20 LTS. Version of gThumb is 3.8.0. Viewing SVG with transparency set used to show as white. Now it shows as checkerboard. After googling I changed settings in Image Viewer but not picked up in gThumb. Maybe it needs a restart .. anyway I use gThumb daily and cannot live with checkerboard. Please fix or advise, thanks ** Affects: gthumb (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/1902774 Title: No way to change checker background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1902774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Hi, Sorry for the delay in getting back to you. As mentioned, adding the absolut path to my auto.DataVol1 file has fixed the issue for me. I think it would be preferably to add files to nsswitch.conf rather than looking for conf entries in /etc/sssd. For me, the only thing inside /etc/sssd is a /etc/sssd/conf.d directory. Both /etc/sssd & /etc/sssd/conf.d have no configuration files. I susptect that if I were to set-up the new Active Directory login, that /etc/sssd would be populated with the appropriate .conf files however I still suggest just adding a fallback to msswitch would be less invasive. G. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Andreas, As per comment #25, I've added the absolute path to auto.DataVol1 in /etc/auto.master as I can confirm it working. With you comment on having: automount: sss [NOTFOUND=continue] files as part of /etc/nsswitch.conf, I suggest that to not break people's existing configs, that this may be a default for the the package developers for all the relevant switch options. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898817] Re: Wifi device disappear after upgrading linux-firmware-raspi2 with 18.04.3 preinstalled image
** Summary changed: - Wifi device disappear after upgrading linux-firmware-raspi2 + Wifi device disappear after upgrading linux-firmware-raspi2 with 18.04.3 preinstalled image ** Summary changed: - Wifi device disappear after upgrading linux-firmware-raspi2 with 18.04.3 preinstalled image + Wifi device disappear after upgrading linux-firmware-raspi2 with 18.04.3 preinstalled server image ** Description changed: [Impact] Wifi device disappear after upgrading linux-firmware-raspi2. Can reproduce on rpi3b, rpi3b+, and rpi3a+. + This only happens on 18.04.3 preinstalled server image, with 4.15 kernel. [Test Case] 1. dd the image in an SD card: - http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04.3-preinstalled-server-arm64+raspi3.img.xz + http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04.3-preinstalled-server-arm64+raspi3.img.xz 2. Boot rpi device with the sd card 3. Upgrade the linux-firmware-raspi2 package using following command: -sudo apt update -sudo apt install linux-firmware-raspi2 + sudo apt update + sudo apt install linux-firmware-raspi2 4. Reboot: -sudo reboot + sudo reboot 5. Check with command: -ip a + ip a Expected Result wlan0 is still there and workable. Actual Result wlan0 device disappeared. [Additional Info] Command output: ubuntu@ubuntu:~$ sudo apt update Hit:1 http://ports.ubuntu.com/ubuntu-ports bionic InRelease Get:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease [74.6 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease [88.7 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages [1,096 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main Translation-en [360 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted arm64 Packages [2,084 B] Get:8 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted Translation-en [23.0 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe arm64 Packages [1,471 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe Translation-en [351 kB] Get:11 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse arm64 Packages [5,068 B] Get:12 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse Translation-en [6,920 B] Get:13 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main arm64 Packages [9,992 B] Get:14 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main Translation-en [4,764 B] Get:15 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe arm64 Packages [9,932 B] Get:16 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe Translation-en [4,588 B] Get:17 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages [803 kB] Get:18 http://ports.ubuntu.com/ubuntu-ports bionic-security/main Translation-en [269 kB] Get:19 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted arm64 Packages [1,172 B] Get:20 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted Translation-en [20.4 kB] Get:21 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe arm64 Packages [933 kB] Get:22 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe Translation-en [239 kB] Get:23 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse arm64 Packages [2,360 B] Get:24 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse Translation-en [2,908 B] - Fetched 5,867 kB in 6s (962 kB/s) + Fetched 5,867 kB in 6s (962 kB/s) Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done 178 packages can be upgraded. Run 'apt list --upgradable' to see them. ubuntu@ubuntu:~$ sudo apt install linux-firmware-raspi2 Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following packages will be upgraded: - linux-firmware-raspi2 + linux-firmware-raspi2 1 upgraded, 0 newly installed, 0 to remove and 177 not upgraded. Need to get 5,200 kB of archives. After this operation, 11.4 MB of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse arm64 linux-firmware-raspi2 arm64 1.20200601+arm64-0ubuntu2~18.04.1 [5,200 kB] - Fetched 5,200 kB in 3s (1,944 kB/s) + Fetched 5,200 kB in 3s (1,944 kB/s) (Reading database ... 62519 files and directories currently installed.) Preparing to unpack .../linux-firmware-raspi2_1.20200601+arm64-0ubuntu2~18.04.1_arm64.deb ... Adding 'diversion of /lib/firmware/brcm/brcmfmac43455-sdio.bin to /lib/firmware/brcm/brcmfmac43455-sdio.bin.distrib
[Bug 1898817] [NEW] Wifi device disappear after upgrading linux-firmware-raspi2
Public bug reported: [Impact] Wifi device disappear after upgrading linux-firmware-raspi2. Can reproduce on rpi3b, rpi3b+, and rpi3a+. [Test Case] 1. dd the image in an SD card: http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04.3-preinstalled-server-arm64+raspi3.img.xz 2. Boot rpi device with the sd card 3. Upgrade the linux-firmware-raspi2 package using following command: sudo apt update sudo apt install linux-firmware-raspi2 4. Reboot: sudo reboot 5. Check with command: ip a Expected Result wlan0 is still there and workable. Actual Result wlan0 device disappeared. [Additional Info] Command output: ubuntu@ubuntu:~$ sudo apt update Hit:1 http://ports.ubuntu.com/ubuntu-ports bionic InRelease Get:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease [74.6 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease [88.7 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages [1,096 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main Translation-en [360 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted arm64 Packages [2,084 B] Get:8 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted Translation-en [23.0 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe arm64 Packages [1,471 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe Translation-en [351 kB] Get:11 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse arm64 Packages [5,068 B] Get:12 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse Translation-en [6,920 B] Get:13 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main arm64 Packages [9,992 B] Get:14 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main Translation-en [4,764 B] Get:15 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe arm64 Packages [9,932 B] Get:16 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe Translation-en [4,588 B] Get:17 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages [803 kB] Get:18 http://ports.ubuntu.com/ubuntu-ports bionic-security/main Translation-en [269 kB] Get:19 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted arm64 Packages [1,172 B] Get:20 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted Translation-en [20.4 kB] Get:21 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe arm64 Packages [933 kB] Get:22 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe Translation-en [239 kB] Get:23 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse arm64 Packages [2,360 B] Get:24 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse Translation-en [2,908 B] Fetched 5,867 kB in 6s (962 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 178 packages can be upgraded. Run 'apt list --upgradable' to see them. ubuntu@ubuntu:~$ sudo apt install linux-firmware-raspi2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: linux-firmware-raspi2 1 upgraded, 0 newly installed, 0 to remove and 177 not upgraded. Need to get 5,200 kB of archives. After this operation, 11.4 MB of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse arm64 linux-firmware-raspi2 arm64 1.20200601+arm64-0ubuntu2~18.04.1 [5,200 kB] Fetched 5,200 kB in 3s (1,944 kB/s) (Reading database ... 62519 files and directories currently installed.) Preparing to unpack .../linux-firmware-raspi2_1.20200601+arm64-0ubuntu2~18.04.1_arm64.deb ... Adding 'diversion of /lib/firmware/brcm/brcmfmac43455-sdio.bin to /lib/firmware/brcm/brcmfmac43455-sdio.bin.distrib by linux-firmware-raspi2' Adding 'diversion of /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt to /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt.distrib by linux-firmware-raspi2' Adding 'diversion of /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt to /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt.distrib by linux-firmware-raspi2' Adding 'diversion of /lib/firmware/brcm/brcmfmac43430-sdio.bin to /lib/firmware/brcm/brcmfmac43430-sdio.bin.distrib by linux-firmware-raspi2' Adding 'diversion of /lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt to /lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt.distrib by linux-firmware-raspi2' Unpacking linux-firmware-raspi2 (1.20200601+arm64-0ubuntu2~18.04.1) over (1.20190215-0ubuntu0.18.04.1) ... Setting up linux-firmware-raspi2 (1.20200601+arm64-0ubuntu2~18.04.1) ... ubuntu@ubuntu:~$ sudo reboot Connection to 10.1
[Bug 1841955] Re: Can't upgrade kernel on raspberry pi3a+
** Changed in: linux-raspi2 (Ubuntu) Status: New => Fix Released ** Changed in: linux-raspi2 (Ubuntu Bionic) 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/1841955 Title: Can't upgrade kernel on raspberry pi3a+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1841955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Hi, Well this explains why this is starting to happen: https://code.launchpad.net/~jibel/ubiquity/+git/ubiquity-1/+merge/390221 They're adding Active Directory to the new user creation in the installer. There's also a design doc that explicitly mentions SSSD: https://docs.google.com/document/d/1_KEGJa2-ka1oNCzMvLlQg9rNW9JESzHAcgqrjP3DkW4/edit?ts=5f561950# SHame is going to break other set-ups along the way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Same here aas in comment #15. I didn't have SSSD installed prior to the upgrade and it was "ubuntu-desktop-minimal" that pulled SSSD in. Not only did it break my automount but also login and sudo would take about a 4 seconds delay to succeed - as I guess it was trying to auth via SSS. Grepped from the update log: apt.log: Installing sssd as Recommends of ubuntu-desktop-minimal apt.log:MarkInstall sssd:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log:Installing python3-sss as Depends of sssd apt.log: MarkInstall python3-sss:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log:Installing sssd-ad as Depends of sssd apt.log: MarkInstall sssd-ad:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log: Installing libsss-idmap0 as Depends of sssd-ad apt.log:MarkInstall libsss-idmap0:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: Installing sssd-ad-common as Depends of sssd-ad apt.log:MarkInstall sssd-ad-common:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log:Installing sssd-common as Depends of sssd-ad-common apt.log: MarkInstall sssd-common:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log: Installing libc-ares2 as Depends of sssd-common apt.log: Installing libdhash1 as Depends of sssd-common apt.log: Installing libini-config5 as Depends of sssd-common apt.log: Installing libsss-certmap0 as Depends of sssd-common apt.log:MarkInstall libsss-certmap0:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: Installing libsss-nss-idmap0 as Depends of sssd-common apt.log:MarkInstall libsss-nss-idmap0:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: Installing libnss-sss as Recommends of sssd-common apt.log:MarkInstall libnss-sss:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: Installing libpam-sss as Recommends of sssd-common apt.log:MarkInstall libpam-sss:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log:Installing libpam-pwquality as Depends of libpam-sss apt.log: Installing libsss-sudo as Recommends of sssd-common apt.log:MarkInstall libsss-sudo:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: Installing sssd-krb5-common as Depends of sssd-ad apt.log:MarkInstall sssd-krb5-common:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log:Installing sssd-ipa as Depends of sssd apt.log: MarkInstall sssd-ipa:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log: Installing libipa-hbac0 as Depends of sssd-ipa apt.log:Installing sssd-krb5 as Depends of sssd apt.log: MarkInstall sssd-krb5:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log:Installing sssd-ldap as Depends of sssd apt.log: MarkInstall sssd-ldap:amd64 < none -> 2.3.1-2 @un uN IPb > FU=0 apt.log: Installing ldap-utils as Recommends of sssd-ldap apt.log:Installing sssd-proxy as Depends of sssd apt.log: MarkInstall sssd-proxy:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: new important dependency: sssd-tools:amd64 apt.log: Installing sssd-tools as Recommends of ubuntu-desktop-minimal apt.log:MarkInstall sssd-tools:amd64 < none -> 2.3.1-2 @un uN IPb > FU=0 apt.log:Installing sssd-dbus as Recommends of sssd-tools apt.log: MarkInstall sssd-dbus:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: new important dependency: sssd:amd64 apt.log: Installing sssd as Recommends of ubuntu-desktop-minimal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
I wouldn't suggest that SSSD has anything done particularly for AutoFS but I would make a case for the package maintainers having a default /etc/sssd config file(s) that if nothing else has options commented/hashed out and ready ti be uncommented and used. This would be much like how *insert your favourite packge here* have a long list of commented options. Grnted, this isn't a serious issue, rather, a small quality of life improvement. :) Oh, one last point. If SSSD comes unconfigured and there unused 'out of the box', should another (meta)package have SSSD dependancy in the first place? (Ref: Timo comment #11) Your thoughts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Understood. I guess the last thing I can do here is take the 20.04 VM I've made and upgrade it to Groovy to see if SSSD is installed as a dependancy of something else. I'll do that over the next day or two. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
After doing a fresh install of 20.04 in a VM and then installing autofs, I've concluded that SSSD isn't needed for my setup. This does leave the question why SSSD was installed and if it was installed upon upgrade to Groovy. Either way, it seems that when SSSD is installed (either on 20.04 or 20.10), SSSD doesn't come with a working config under /etc/sssd On my install of Groovy, I removed SSSD and now my automounts are working correctly. Should SSSD have a default working config under /etc/sssd when its packages are installed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
I installed 20.04 fresh in a Gnome Boxes VM and installed autofs (sudo apt-get install autofs). SSSD was not installed as a dependancy. Then, I installed SSSD (sudo apt-get install sssd) just to see what /etc/sssd looked like and it's actually the same. there's no config file under /etc/sssd and and empty /etc/sssd/conf.d directory I executed a systemctl start sssd and it threw the same errors. I didn't have autofs configured and did not try to start autofs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Nope, there's no files under /etc/sssd and I didn't touch this directory when upgrading to the Groovy daily image. When I have a moment, I'll install 20.04 in a VM for a comparison of what should be in /etc/sssd But as far as /etc/nsswitch.conf goes: # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: files systemd sss group: files systemd sss shadow: files sss gshadow:files hosts: files mdns4_minimal [NOTFOUND=return] dns mymachines networks: files protocols: db files services: db files sss ethers: db files rpc:db files netgroup: nis sss sudoers:files sss automount: sss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
I never looked at SSD closely prior to upgrading from 20.04 to 20.10 so I don't know what was there before as it 'just worked'. Presently though, the only thing under /etc/sssd is an empty conf.d (/etc/sssd/conf.d) directory. I did reinstall the SSSD packages after upgrade to 20.10 however the /etc/sssd directory didn't change from being empty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Trying to restart SSSD give the following errors with journlctl -xe: The job identifier is 11972 and the job result is failed. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD Sudo Service responder socket. ░░ Subject: A start job for unit sssd-sudo.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-sudo.socket has finished with a failure. ░░ ░░ The job identifier is 12071 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-sudo.socket: Job sssd-sudo.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD AutoFS Service responder socket. ░░ Subject: A start job for unit sssd-autofs.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-autofs.socket has finished with a failure. ░░ ░░ The job identifier is 11968 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-autofs.socket: Job sssd-autofs.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD PAM Service responder socket. ░░ Subject: A start job for unit sssd-pam.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-pam.socket has finished with a failure. ░░ ░░ The job identifier is 12073 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD PAM Service responder private socket. ░░ Subject: A start job for unit sssd-pam-priv.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-pam-priv.socket has finished with a failure. ░░ ░░ The job identifier is 12074 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-pam-priv.socket: Job sssd-pam-priv.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD SSH Service responder socket. ░░ Subject: A start job for unit sssd-ssh.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-ssh.socket has finished with a failure. ░░ ░░ The job identifier is 12070 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-ssh.socket: Job sssd-ssh.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD PAC Service responder socket. ░░ Subject: A start job for unit sssd-pac.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-pac.socket has finished with a failure. ░░ ░░ The job identifier is 12075 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-pac.socket: Job sssd-pac.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD NSS Service responder socket. ░░ Subject: A start job for unit sssd-nss.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-nss.socket has finished with a failure. ░░ ░░ The job identifier is 12069 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start failed with result 'dependency'. And syslog: root@ROC-Cube:~# tail /var/log/syslog Sep 25 04:24:47 ROC-Cube systemd[1]: Dependency failed for SSSD PAM Service responder socket. Sep 25 04:24:47 ROC-Cube systemd[1]: Dependency failed for SSSD PAM Service responder private socket. Sep 25 04:24:47 ROC-Cube systemd[1]: sssd-pam-priv.socket: Job sssd-pam-priv.socket/start failed with result 'dependency'. Sep 25 04:24:47 ROC-Cube systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'. Sep 25 04:24:47 ROC-Cube systemd[1]: Dependency failed for SSSD SSH Service responder socket. Sep 25 04:24:47 ROC-Cube systemd[1]: sssd-ssh.socket: Job sssd-ssh.socket/start failed with result 'dependency'. Sep 25 04:24:47 ROC-Cube systemd[1]: Dependency failed for SSSD PAC Service responder socket. Sep 25 04:24:47 ROC-Cube systemd[1]: sssd-pac.socket: Job sssd-pac.socket/start failed with result 'dependency'. Sep 25 04:24:47 ROC-Cube systemd[1]: Dependency failed for SSSD NSS Service responder socket. Sep 25 04:24:47 ROC-Cube systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start failed with result 'dependency'. ** Summary changed: - Automount fails due to SSSD + Automount fails due to SSSD config (Groovy Gorilla) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bu
[Bug 1897153] [NEW] Automount fails due to SSSD config (Groovy Gorilla)
Public bug reported: Using the same automount config from 20.04, Groovy Gorilla fails to automount mount points with SSD errors such as the following: -From journalctl -xe: Sep 25 04:04:43 ROC-Cube systemd[1]: Stopping Automounts filesystems on demand... ░░ Subject: A stop job for unit autofs.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A stop job for unit autofs.service has begun execution. ░░ ░░ The job identifier is 8075. Sep 25 04:04:43 ROC-Cube automount[1838]: umount_autofs_indirect: ask umount returned busy /mnt/GGData Sep 25 04:04:44 ROC-Cube systemd[1]: autofs.service: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit autofs.service has successfully entered the 'dead' state. Sep 25 04:04:44 ROC-Cube systemd[1]: Stopped Automounts filesystems on demand. ░░ Subject: A stop job for unit autofs.service has finished ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A stop job for unit autofs.service has finished. ░░ ░░ The job identifier is 8075 and the job result is done. Sep 25 04:04:44 ROC-Cube systemd[1]: Starting Automounts filesystems on demand... ░░ Subject: A start job for unit autofs.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit autofs.service has begun execution. ░░ ░░ The job identifier is 8075. Sep 25 04:04:44 ROC-Cube automount[13523]: setautomntent: lookup(sss): setautomntent: No such file or directory Sep 25 04:04:44 ROC-Cube systemd[1]: tmp-auto8NobgK.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit tmp-auto8NobgK.mount has successfully entered the 'dead' state. Sep 25 04:04:44 ROC-Cube automount[13523]: setautomntent: lookup(sss): setautomntent: No such file or directory Sep 25 04:04:44 ROC-Cube systemd[2685]: tmp-autoxIakpM.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit UNIT has successfully entered the 'dead' state. Sep 25 04:04:44 ROC-Cube systemd[1]: tmp-autoxIakpM.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit tmp-autoxIakpM.mount has successfully entered the 'dead' state. Sep 25 04:04:44 ROC-Cube systemd[1]: Started Automounts filesystems on demand. ░░ Subject: A start job for unit autofs.service has finished successfully ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit autofs.service has finished successfully. ░░ ░░ The job identifier is 8075. >From tail /var/log/syslog: Sep 25 04:13:38 ROC-Cube automount[13523]: umount_autofs_indirect: ask umount returned busy /mnt/GGData Sep 25 04:13:40 ROC-Cube systemd[1]: autofs.service: Succeeded. Sep 25 04:13:40 ROC-Cube systemd[1]: Stopped Automounts filesystems on demand. Sep 25 04:13:40 ROC-Cube systemd[1]: Starting Automounts filesystems on demand... Sep 25 04:13:40 ROC-Cube automount[15237]: setautomntent: lookup(sss): setautomntent: No such file or directory Sep 25 04:13:40 ROC-Cube systemd[2685]: tmp-autonc2nfm.mount: Succeeded. Sep 25 04:13:40 ROC-Cube automount[15237]: setautomntent: lookup(sss): setautomntent: No such file or directory Sep 25 04:13:40 ROC-Cube systemd[1]: tmp-autonc2nfm.mount: Succeeded. Sep 25 04:13:40 ROC-Cube systemd[1]: Started Automounts filesystems on demand. Sep 25 04:13:40 ROC-Cube systemd[2685]: tmp-autopnDion.mount: Succeeded. >From auto.DataVol1: root@ROC-Cube:~# cat /etc/auto.DataVol1 #/mnt/GGData-fstype=nfs 10.0.0.13:/GGData Tracktion -fstype=nfs 10.0.0.13:/GGData/Tracktion C64 -fstype=nfs 10.0.0.13:/GGData/C64 Development -fstype=nfs 10.0.0.13:/GGData/Development Retro -fstype=nfs 10.0.0.13:/GGData/Retro Inkscape-fstype=nfs 10.0.0.13:/GGData/Inkscape >From /etc/auto.master: /mnt/GGData auto.DataVol1 --ghost ** Affects: sssd (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/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD
Additional points: * Able to always reproduce * Able to manually mount volumes (doing so as temp workaround) dpkg -l sssd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii sssd 2.3.1-2 amd64System Security Services Daemon -- metapackage root@ROC-Cube:~# dpkg -l autofs Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--== ii autofs 5.1.6-3ubuntu1 amd64kernel-based automounter for Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893686] Re: [nvidia] Some apps are partially transparent/corrupt
I have not had the same issue with Chromium, but I suspect you might be right and it's still related. Any thoughts right now on when 450 reaches official? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893686 Title: [nvidia] Some apps are partially transparent/corrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1893686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893686] Re: [nvidia] Some apps are partially transparent/corrupt
Thanks, Daniel... I don't know as I run Firefox rather than Chromium. Let me fire it up and play with it for a day or two and see if I get the same issue. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893686 Title: [nvidia] Some apps are partially transparent/corrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1893686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893686] Re: [nvidia] Some apps show semi-random corruption
Uploading additional grab with my camera showing the corruption on Gnome Tweaks window where it looks as though a terminal window behind Firefox (two windows back from this) is showing through. ** Attachment added: "IMG_20200901_095617.jpg" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1893686/+attachment/5406588/+files/IMG_20200901_095617.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893686 Title: [nvidia] Some apps show semi-random corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1893686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326761] Re: Tevii S471 DVB-S2 card hangs on firmware upload
Just tried my HDStar DVB-S2 USB tuner again on Ubuntu 20.04 with a 5.8.5 kernel. The issue persists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326761 Title: Tevii S471 DVB-S2 card hangs on firmware upload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893686] Re: [nvidia] Some apps show semi-random corruption
Please see attached. As you can see I have the Ubuntu Software tool to the right, and I have Gnome Tweaks open to the left. You can also see other apps that are showing normal functioning. Gnome Tweaks particularly doesn't seem to show corrupted window decorations unless Ubuntu Software is open. Oddly also, Tweaks' window decoration issues don't seem to be coming up on the screenshot. I am seeing moving pixels of random discoloration particularly in the drop shadows. Often red. ** Attachment added: "Screenshot from 2020-09-01 07-00-24.png" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1893686/+attachment/5406498/+files/Screenshot%20from%202020-09-01%2007-00-24.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893686 Title: [nvidia] Some apps show semi-random corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1893686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893686] [NEW] Some apps show semi-random corruption
Public bug reported: NVidia drivers in Ubuntu 20.04 show corruption in certain applications. Most egregious bug appears to be "Ubuntu Software Center" which is almost completely transparent and unusable. Also see occasional corruption in window decorations in other apps, namely Gnome Tweaks as a prime example. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 13:33:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell UHD Graphics 630 (Desktop 9 Series) [1028:08f7] NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU104 [GeForce RTX 2080 Rev. A] [1028:3729] InstallationDate: Installed on 2020-06-25 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R8 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=c80a6058-31c8-4117-a747-3193e765eff9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.12 dmi.board.name: 02XRCM dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.12:bd02/20/2020:svnAlienware:pnAlienwareAuroraR8:pvr1.0.12:rvnAlienware:rn02XRCM:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R8 dmi.product.sku: 08F7 dmi.product.version: 1.0.12 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "Screenshot from 2020-08-31 13-28-00.png" https://bugs.launchpad.net/bugs/1893686/+attachment/5406205/+files/Screenshot%20from%202020-08-31%2013-28-00.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893686 Title: Some apps show semi-random corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1893686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882039] Re: The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs
** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic 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/1882039 Title: The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882039] Re: The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs
** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882039 Title: The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879796] Re: File descriptor leak in libva2
This patch has been merged by libva -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879796 Title: File descriptor leak in libva2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1879796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882039] Re: The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) 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/1882039 Title: The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882039] [NEW] The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs
Public bug reported: [Impact] There is performance overhead observed when many threads are using hugetlbfs in the database environment. [Fix] bdfbd98bc018 hugetlbfs: take read_lock on i_mmap for PMD sharing The patch improves the locking by using the read lock instead of the write lock. And it allows multiple threads searching the suitable shared VMA. As there is no modification inside the searching process. The improvement increases the parallelism and decreases the waiting time of the other threads. [Test] The customer stand-up a database with seed data. Then they have a loading "driver" which makes a bunch of connections that look like user workflows from the database perspective. Finally, the measuring response times improvement can be observed for these "users" as well as various other metrics at the database level. [Regression Potential] The modification is only in replacing the write lock to a read one. And there is no modification inside the loop. The regression probability is low. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Gavin Guo (mimi0213kimo) Status: New ** Tags: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882039 Title: The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879796] [NEW] File descriptor leak in libva2
Public bug reported: I believe there is a file descriptor leak in libva. I have attached sample code which simply opens and calls vaInitialize and vaTerminate in a loop. Running this code will eventually run out of file descriptors. I have submitted a pull request here: https://github.com/intel/libva/pull/418 ** Affects: libva (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Demonstrates leak by opening and closing libva" https://bugs.launchpad.net/bugs/1879796/+attachment/5374841/+files/vainfo.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879796 Title: File descriptor leak in libva2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1879796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878374] [NEW] UC20 stuck at installing system on some Intel NUC systems with nvme
Public bug reported: UC20 stuck at installing system on some Intel NUC systems with nvme. Tried system with/without secure boot, both can reproduce this issue. Tried system with/without hardware TPM 2.0, both can reproduce this issue. Screen capture: https://drive.google.com/open?id=1BuyxqyjXucjedk2U6I4E5yqn_NABRmS9 Hardware information: Intel NUC NUC7i3DNHE Intel NUC NUC7i5DNHE Intel NUC NUC7i7DNH ** Affects: 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/1878374 Title: UC20 stuck at installing system on some Intel NUC systems with nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1878374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877969] Re: Failed to build knem.ko on on xenial-hwe 4.15 kernel
I found there's already a bug for this issue, closing this one: https://bugs.launchpad.net/argos/+bug/1779115 ** Changed in: ubuntu Status: New => Invalid ** Description changed: Failed to build knem.ko after upgrading kernel to 4.15.0-100.101~16.04.1. Didn't see function lost in the test. - Test Output: Found dkms build error messages in /var/log/apt/term.log === build log === ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Build of knem.ko failed for: 4.15.0-100-generic (x86_64) Consult the make.log in the build directory /var/lib/dkms/knem/1.1.2.90mlnx3/build/ for more information. ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/mlnx-ofed-kernel/4.2/build/make.log for more information. ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/nvidia-peer-memory/1.0/build/make.log for more information. Setting up linux-headers-generic-hwe-16.04 (4.15.0.100.107) ... Setting up linux-generic-hwe-16.04 (4.15.0.100.107) ... Processing triggers for linux-image-4.15.0-100-generic (4.15.0-100.101~16.04.1) ... /etc/kernel/postinst.d/dkms: ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Build of knem.ko failed for: 4.15.0-100-generic (x86_64) Consult the make.log in the build directory /var/lib/dkms/knem/1.1.2.90mlnx3/build/ for more information. ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/mlnx-ofed-kernel/4.2/build/make.log for more information. ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/nvidia-peer-memory/1.0/build/make.log for more information. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-100-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. /etc/kernel/postinst.d/x-grub-legacy-ec2: Hardware info: Machine: Nvidia DGX-1 - CID: 201802-26098 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877969 Title: Failed to build knem.ko on on xenial-hwe 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877969] Re: Failed to build knem.ko on on xenial-hwe 4.15 kernel
I found there's already a bug for this issue in the project, closing this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877969 Title: Failed to build knem.ko on on xenial-hwe 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877966] Re: Failed to build tp-smapi dkms on xenial-hwe 4.15 kernel
** Description changed: - Failed to build tp-smapi dkms after upgrading kernel to - 4.15.0-100.101~16.04.1-generic. + Failed to build tp-smapi dkms after upgrading kernel to 4.15.0-100.101~16.04.1-generic. + Didn't see function lost in the test. + Test output: 4 modules for 4.4.0-179-generic 3 modules for 4.15.0-100-generic DKMS module number is inconsistent. Some modules may not be built. === DKMS status === bbswitch, 0.8, 4.15.0-100-generic, x86_64: installed bbswitch, 0.8, 4.15.0-58-generic, x86_64: installed bbswitch, 0.8, 4.4.0-179-generic, x86_64: installed fwts-efi-runtime-dkms, 20.02.00, 4.15.0-100-generic, x86_64: installed fwts-efi-runtime-dkms, 20.02.00, 4.15.0-58-generic, x86_64: installed fwts-efi-runtime-dkms, 20.02.00, 4.4.0-179-generic, x86_64: installed nvidia-384, 384.130, 4.15.0-100-generic, x86_64: installed nvidia-384, 384.130, 4.15.0-58-generic, x86_64: installed nvidia-384, 384.130, 4.4.0-179-generic, x86_64: installed tp-smapi, 0.41, 4.4.0-179-generic, x86_64: installed Found dkms build error messages in /var/log/apt/term.log === build log === Building module: cleaning build area make KERNELRELEASE=4.15.0-100-generic -C /lib/modules/4.15.0-100-generic/build M=/var/lib/dkms/tp-smapi/0.41/build(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/tp-smapi/0.41/build/make.log for more information. -...done. + ...done. Setting up linux-headers-generic-hwe-16.04 (4.15.0.100.107) ... Setting up linux-generic-hwe-16.04 (4.15.0.100.107) ... Setting up linux-libc-dev:amd64 (4.4.0-179.209) ... -- Building module: cleaning build area make KERNELRELEASE=4.15.0-100-generic -C /lib/modules/4.15.0-100-generic/build M=/var/lib/dkms/tp-smapi/0.41/build(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/tp-smapi/0.41/build/make.log for more information. -...done. + ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-100-generic W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877966 Title: Failed to build tp-smapi dkms on xenial-hwe 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tp-smapi/+bug/1877966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877969] [NEW] Failed to build knem.ko on on xenial-hwe 4.15 kernel
Public bug reported: Failed to build knem.ko after upgrading kernel to 4.15.0-100.101~16.04.1. Didn't see function lost in the test. Test Output: Found dkms build error messages in /var/log/apt/term.log === build log === ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Build of knem.ko failed for: 4.15.0-100-generic (x86_64) Consult the make.log in the build directory /var/lib/dkms/knem/1.1.2.90mlnx3/build/ for more information. ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/mlnx-ofed-kernel/4.2/build/make.log for more information. ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/nvidia-peer-memory/1.0/build/make.log for more information. Setting up linux-headers-generic-hwe-16.04 (4.15.0.100.107) ... Setting up linux-generic-hwe-16.04 (4.15.0.100.107) ... Processing triggers for linux-image-4.15.0-100-generic (4.15.0-100.101~16.04.1) ... /etc/kernel/postinst.d/dkms: ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Build of knem.ko failed for: 4.15.0-100-generic (x86_64) Consult the make.log in the build directory /var/lib/dkms/knem/1.1.2.90mlnx3/build/ for more information. ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/mlnx-ofed-kernel/4.2/build/make.log for more information. ERROR (dkms apport): kernel package linux-headers-4.15.0-100-generic is not supported Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/nvidia-peer-memory/1.0/build/make.log for more information. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-100-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. /etc/kernel/postinst.d/x-grub-legacy-ec2: Hardware info: Machine: Nvidia DGX-1 CID: 201802-26098 ** Affects: 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/1877969 Title: Failed to build knem.ko on on xenial-hwe 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877966] [NEW] Failed to build tp-smapi dkms on xenial-hwe 4.15 kernel
Public bug reported: Failed to build tp-smapi dkms after upgrading kernel to 4.15.0-100.101~16.04.1-generic. Didn't see function lost in the test. Test output: 4 modules for 4.4.0-179-generic 3 modules for 4.15.0-100-generic DKMS module number is inconsistent. Some modules may not be built. === DKMS status === bbswitch, 0.8, 4.15.0-100-generic, x86_64: installed bbswitch, 0.8, 4.15.0-58-generic, x86_64: installed bbswitch, 0.8, 4.4.0-179-generic, x86_64: installed fwts-efi-runtime-dkms, 20.02.00, 4.15.0-100-generic, x86_64: installed fwts-efi-runtime-dkms, 20.02.00, 4.15.0-58-generic, x86_64: installed fwts-efi-runtime-dkms, 20.02.00, 4.4.0-179-generic, x86_64: installed nvidia-384, 384.130, 4.15.0-100-generic, x86_64: installed nvidia-384, 384.130, 4.15.0-58-generic, x86_64: installed nvidia-384, 384.130, 4.4.0-179-generic, x86_64: installed tp-smapi, 0.41, 4.4.0-179-generic, x86_64: installed Found dkms build error messages in /var/log/apt/term.log === build log === Building module: cleaning build area make KERNELRELEASE=4.15.0-100-generic -C /lib/modules/4.15.0-100-generic/build M=/var/lib/dkms/tp-smapi/0.41/build(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/tp-smapi/0.41/build/make.log for more information. ...done. Setting up linux-headers-generic-hwe-16.04 (4.15.0.100.107) ... Setting up linux-generic-hwe-16.04 (4.15.0.100.107) ... Setting up linux-libc-dev:amd64 (4.4.0-179.209) ... -- Building module: cleaning build area make KERNELRELEASE=4.15.0-100-generic -C /lib/modules/4.15.0-100-generic/build M=/var/lib/dkms/tp-smapi/0.41/build(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 4.15.0-100-generic (x86_64) Consult /var/lib/dkms/tp-smapi/0.41/build/make.log for more information. ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-100-generic W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 ** Affects: tp-smapi (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/1877966 Title: Failed to build tp-smapi dkms on xenial-hwe 4.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tp-smapi/+bug/1877966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872034] [NEW] [Focal] No HDMI output through thunderbolt docking station
Public bug reported: I can find monitor in display list, but no output from it. Also, I can't switch to extend mode, it failed to apply the setting and switched back to mirror mode. [Steps] 1. Connect a thunderbolt docking station to thunderbolt port. 2. Connect HDMI monitor to HDMI port on the docking station. 3. Switch mode in display setting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:44:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872034 Title: [Focal] No HDMI output through thunderbolt docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
** Description changed: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. + [Reproduce steps] + 1. Scan and pair BT headset in Bluetooth setting + 2. Switch to HSP/HFP profile in Sound setting + 3. Test sound output/input + + [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 1359 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 1359 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
** This bug is no longer a duplicate of bug 1576559 Refused to switch profile to headset_head_unit: Not connected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871794] [NEW] [Bluetooth] No audio output/input in HSP/HFP mode
Public bug reported: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865495] Re: xenial/linux-deeplens: 4.15.0-1019.19 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: DeepLens: https://certification.canonical.com/hardware/201801-26078/submission/163784/ DeepRacer: https://certification.canonical.com/hardware/201903-26883/submission/163783/ ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865495 Title: xenial/linux-deeplens: 4.15.0-1019.19 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865495] Re: xenial/linux-deeplens: 4.15.0-1019.19 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865495 Title: xenial/linux-deeplens: 4.15.0-1019.19 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
Test result: https://docs.google.com/spreadsheets/d/1A_nTnwoxzFGpirKbqpQL4bYVBD0ZbDJVicjuZpgVbv4/edit#gid=566033014 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1854485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865140] Re: bionic/linux-hwe-5.0: 5.0.0-43.47~18.04.1 -proposed tracker
Seems no official image will upgrade to this kernel, confirming if this test should be skipped. ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865140 Title: bionic/linux-hwe-5.0: 5.0.0-43.47~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864726] Re: bionic/linux-raspi2: 4.15.0-1057.61 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: Rpi2b-armhf: https://certification.canonical.com/hardware/201906-27188/submission/163332/ Rpi3b-arm64: https://certification.canonical.com/hardware/201811-26649/submission/163378/ Rpi3b-armhf: https://certification.canonical.com/hardware/201811-26649/submission/163344/ Rpi3a+-arm64: https://certification.canonical.com/hardware/201901-26785/submission/163340/ Rpi3a+-armhf: https://certification.canonical.com/hardware/201901-26785/submission/163346/ Rpi3b+-arm64: https://certification.canonical.com/hardware/201810-26542/submission/163338/ Rpi3b+-armhf: https://certification.canonical.com/hardware/201810-26542/submission/163374/ CM3-arm64: https://certification.canonical.com/hardware/201711-25992/submission/163331/ CM3-armhf: https://certification.canonical.com/hardware/201711-25992/submission/163337/ CM3+-arm64: https://certification.canonical.com/hardware/201908-27277/submission/163329/ CM3+-armhf: https://certification.canonical.com/hardware/201908-27277/submission/163373/ ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864726 Title: bionic/linux-raspi2: 4.15.0-1057.61 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863268] Re: bionic/linux-raspi2-5.3: 5.3.0-1019.21~18.04.1 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: Rpi2b-armhf: https://certification.canonical.com/hardware/201906-27188/submission/162883/ Rpi3b-arm64: https://certification.canonical.com/hardware/201811-26649/submission/162885/ Rpi3b-armhf: https://certification.canonical.com/hardware/201811-26649/submission/162879/ Rpi3a+-arm64: https://certification.canonical.com/hardware/201901-26785/submission/162884/ Rpi3a+-armhf: https://certification.canonical.com/hardware/201901-26785/submission/162878/ Rpi3b+-arm64: https://certification.canonical.com/hardware/201810-26542/submission/162882/ Rpi3b+-armhf: https://certification.canonical.com/hardware/201810-26542/submission/162877/ Rpi4b-1g-arm64: https://certification.canonical.com/hardware/201911-27471/submission/162869/ Rpi4b-1g-armhf: https://certification.canonical.com/hardware/201910-27407/submission/162875/ Rpi4b-2g-arm64: https://certification.canonical.com/hardware/201911-27507/submission/162870/ Rpi4b-2g-armhf: https://certification.canonical.com/hardware/201911-27506/submission/162874/ Rpi4b-4g-arm64: https://certification.canonical.com/hardware/201911-27456/submission/162871/ Rpi4b-4g-armhf: https://certification.canonical.com/hardware/201911-27455/submission/162872/ CM3-arm64: Unable to test, no space to upgrade kernel CM3-armhf: Unable to test, no space to upgrade kernel CM3+-arm64: https://certification.canonical.com/hardware/201908-27277/submission/162881/ CM3+-armhf: https://certification.canonical.com/hardware/201908-27277/submission/162876/ ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863268 Title: bionic/linux-raspi2-5.3: 5.3.0-1019.21~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863324] Re: xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: rpi2-armhf: https://certification.canonical.com/hardware/201906-27188/submission/163237/ ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863324 Title: xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
