[Bug 2078589] Re: fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common:
Okay, I will note that the fix for my login was very specific: I had a file, /etc/profile.d/ZZZ-pulseaudio-k.sh, which was running "pulseaudio -k" at system startup, which broke audio and seemed to confuse the system long enough that my login screen would just freeze for a minute or two. So, if you've ever kludged pulseaudio at your system level and then tried to upgrade ... look into that. :) Agree that system upgrades for people who have been doing weird business on their systems for a decade are, not shockingly, tricky. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078589 Title: fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2078589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078589] Re: fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common:
Thank you, Stuart for both the clues and the reminder that with a free, open source project, a little patience goes a long way. What worked for me: sudo apt remove kubuntu-settings-desktop sudo do-release-upgrade -m desktop This ended in a reboot. When it came back, the login screen was frozen. I think you don't need to do what I did next: control+alt+f1 login sudo apt install kubuntu-settings-desktop sudo reboot Because when it came back, the login screen was still frozen. But after a minute or two I guess whatever it was timed out, a new logo appeared, and I was able to log in like normal. So, give it a try, folks: sudo apt remove kubuntu-settings-desktop sudo do-release-upgrade -m deskt Thanks again, Stuart, to you, all the contributors and maintainers, and all the users who make this software experience the best it can be. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078589 Title: fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2078589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083087] [NEW] can not upgrade kubuntu 22.04 LTS to 24.04 LTS
Public bug reported: Description:Ubuntu 22.04.5 LTS Release:22.04 Ran: sudo apt-get update && sudo apt-get dist-upgrade sudo do-release-upgrade -m desktop [...] An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. [...] 0-18:29 djh@noneedto /v/l/dist-upgrade> grep -i err main.log 2024-09-27 18:20:25,278 DEBUG running doUpdate() (showErrors=False) 2024-09-27 18:20:38,853 DEBUG Obsolete: adobe-flashplugin e2fslibs gcc-6-base google-chrome-stable libcomerr2 libfam0 libhogweed4 libicu66 libldap-2.4-2 libldap-2.4-2:i386 libmpdec2 libnettle6 libruby2.7 libsodium27 libssl1.1 libvkd3d-shader1:i386 linux-headers-5.4.0-67 linux-headers-5.4.0-96 mfcj650dwcupswrapper:i386 mfcj650dwlpr:i386 multiarch-support slack-desktop vdpau-va-driver vkd3d-compiler:i386 zoom 2024-09-27 18:20:39,311 DEBUG running doUpdate() (showErrors=True) 2024-09-27 18:21:41,278 DEBUG Searching for replacement for libblockdev-part-err2 2024-09-27 18:21:41,278 DEBUG Failed to find a replacement for libblockdev-part-err2 2024-09-27 18:21:41,396 DEBUG Searching for replacement for libcanberra-gtk3-0 2024-09-27 18:21:41,396 DEBUG Found replacement libcanberra-gtk3-0t64 for libcanberra-gtk3-0 2024-09-27 18:21:41,436 DEBUG Searching for replacement for libcanberra0 2024-09-27 18:21:41,436 DEBUG Found replacement libcanberra0t64 for libcanberra0 2024-09-27 18:21:41,748 DEBUG Searching for replacement for libcomerr2 2024-09-27 18:21:41,748 DEBUG Found replacement libcom-err2 for libcomerr2 2024-09-27 18:21:50,110 ERROR Dist-upgrade failed: 'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.' All the hits in apt.log are just package names with "err" in them. Right before the ERROR in main.log is a bunch of stuff like: 2024-09-27 18:21:49,421 DEBUG Searching for replacement for vkd3d-compiler:i386 2024-09-27 18:21:49,421 DEBUG Failed to find a replacement for vkd3d-compiler:i386 2024-09-27 18:21:49,422 DEBUG Searching for replacement for xapp 2024-09-27 18:21:49,423 DEBUG Failed to find a replacement for xapp 2024-09-27 18:21:49,424 DEBUG Searching for replacement for youtube-dl 2024-09-27 18:21:49,424 DEBUG Failed to find a replacement for youtube-dl 2024-09-27 18:21:49,425 DEBUG Searching for replacement for zoom 2024-09-27 18:21:49,425 DEBUG Failed to find a replacement for zoom I tried removing sources.list.d to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.20 ProcVersionSignature: Ubuntu 5.15.0-122.132-generic 5.15.163 Uname: Linux 5.15.0-122-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Sep 27 18:23:48 2024 InstallationDate: Installed on 2016-04-24 (3078 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-09-28 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages ** Attachment added: "main.log" https://bugs.launchpad.net/bugs/2083087/+attachment/5822651/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083087 Title: can not upgrade kubuntu 22.04 LTS to 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059149] Re: Crash
Ok, can confirm after having disabled Gnome's 'screen lock' entirely, that this is triggered merely by the 'Screen blanking' being invoked. For now will workaround by disabling that, but in case it's useful here's the dmesg output from when this happened just now when the screen blanked. Leaving out the remaining call stack as it's no different from previously. ``` [Sun Sep 1 22:11:08 2024] audit: type=1400 audit(1725225069.215:107): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=8136 comm="snap-confine" capability=12 capname="net_admin" [Sun Sep 1 22:11:08 2024] audit: type=1400 audit(1725225069.215:108): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=8136 comm="snap-confine" capability=38 capname="perfmon" [Sun Sep 1 22:19:09 2024] simple-framebuffer simple-framebuffer.0: swiotlb buffer is full (sz: 1802240 bytes), total 32768 (slots), used 86 (slots) [Sun Sep 1 22:19:09 2024] simple-framebuffer simple-framebuffer.0: swiotlb buffer is full (sz: 1802240 bytes), total 32768 (slots), used 86 (slots) [Sun Sep 1 22:19:10 2024] simple-framebuffer simple-framebuffer.0: swiotlb buffer is full (sz: 2068480 bytes), total 32768 (slots), used 12 (slots) [Sun Sep 1 22:19:12 2024] usb 1-3.2: USB disconnect, device number 5 [Sun Sep 1 22:19:15 2024] simple-framebuffer simple-framebuffer.0: swiotlb buffer is full (sz: 442368 bytes), total 32768 (slots), used 6096 (slots) [Sun Sep 1 22:19:15 2024] [ cut here ] [Sun Sep 1 22:19:15 2024] simple-framebuffer simple-framebuffer.0: drm_WARN_ON(map->is_iomem) [Sun Sep 1 22:19:15 2024] WARNING: CPU: 9 PID: 2746 at drivers/gpu/drm/drm_gem_shmem_helper.c:319 drm_gem_shmem_vmap+0x1a5/0x1e0 [Sun Sep 1 22:19:15 2024] Modules linked in: veth xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter nft_chain_nat xt_nat nf_nat nfnetlink_queue xt_commen> [Sun Sep 1 22:19:15 2024] btusb ac97_bus videobuf2_memops snd_pcm_dmaengine videobuf2_v4l2 btrtl snd_usb_audio kvm_intel snd_hda_intel btintel videodev btbcm snd_intel_dspcfg btmtk s> [Sun Sep 1 22:19:15 2024] hid_logitech_dj hid_generic cdc_ncm usbhid cdc_ether usbnet hid mii nvme crc32_pclmul r8169 nvme_core i2c_i801 spi_intel_pci intel_lpss_pci ahci xhci_pci sp> [Sun Sep 1 22:19:15 2024] CPU: 9 PID: 2746 Comm: Xorg Tainted: P OE 6.8.0-40-generic #40~22.04.3-Ubuntu [Sun Sep 1 22:19:15 2024] Hardware name: Gigabyte Technology Co., Ltd. B760M DS3H DDR4/B760M DS3H DDR4, BIOS F17 05/08/2024 [Sun Sep 1 22:19:15 2024] RIP: 0010:drm_gem_shmem_vmap+0x1a5/0x1e0 [Sun Sep 1 22:19:15 2024] Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 c4 a3 ec ff 48 c7 c1 39 19 09 a5 4c 89 ea 48 c7 c7 17 9b 08 a5 48 89 c6 e8 ab 34 46 ff <0f> 0b 48 8b 83 f0 00 00> [Sun Sep 1 22:19:15 2024] RSP: 0018:bfb243e2b940 EFLAGS: 00010246 [Sun Sep 1 22:19:15 2024] RAX: RBX: 9f9b84897000 RCX: [Sun Sep 1 22:19:15 2024] RDX: RSI: RDI: [Sun Sep 1 22:19:15 2024] RBP: bfb243e2b960 R08: R09: [Sun Sep 1 22:19:15 2024] R10: R11: R12: 9f9dfa6634c8 [Sun Sep 1 22:19:15 2024] R13: 9f9b829c6e20 R14: 9f9dfa6634c8 R15: 9f9dfa6634c8 [Sun Sep 1 22:19:15 2024] FS: 7a451114ea80() GS:9faaff88() knlGS: [Sun Sep 1 22:19:15 2024] CS: 0010 DS: ES: CR0: 80050033 [Sun Sep 1 22:19:15 2024] CR2: 5d8582fb9e1c CR3: 00010ad88000 CR4: 00f50ef0 [Sun Sep 1 22:19:15 2024] PKRU: 5554 [Sun Sep 1 22:19:15 2024] Call Trace: [Sun Sep 1 22:19:15 2024] [Sun Sep 1 22:19:15 2024] ? show_regs+0x6d/0x80 [Sun Sep 1 22:19:15 2024] ? __warn+0x89/0x160 ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059149 Title: Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059149] Re: Crash
I'm having the same issue right now. I've just applied latest updates, but not sure whether they're relevant - seems more relevant that I've just moved to using HDMI audio based on the content of this crash, but either could be involved. Attaching requested diagnostic files - please let me know if I need to re-open this as a new bug since this one is 'Expired'. `sudo journalctl -b0 > journal.txt` -> `journal.txt` `sudo journalctl -b-1 > prevjournal.txt` -> `prevjournal.txt` `sudo find /var/crash -mtime -1` yields no new files (crash was about 10 minutes ago). `/var/lib/whoopsie/whoopsie-id` is dated several hours prior to this particular crash. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059149/+attachment/5812024/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059149 Title: Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059149] Re: Crash
`prevjournal.txt` (looks like I can't attach multiple files to a single post) If it helps, current system with the issue is an i7-12700F with an NVIDIA GeForce RTX 4070 SUPER (pci-id 10de:2783). I also have a suspicion that problematic behaviour only ensues after playing Steam games full screen, and Gnome screensaver then kicking in, but I have yet to gather firm evidence of that. ** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059149/+attachment/5812025/+files/prevjournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059149 Title: Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078267] [NEW] unresolvable error in upgrade to 24.04
Public bug reported: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. The package 'postgresql-12' is marked for removal but it is in the removal deny list. To prevent data loss, postgresql packages are not removed automatically during the upgrade. If you are certain you no longer need postgresql-12, you can manually remove it and try the upgrade again. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. And yet... ii postgresql-12 12.20-0ubuntu0.20.04.1 amd64 object-relational SQL database, version 12 server un postgresql-9.1 (no description available) un postgresql-client (no description available) ii postgresql-client-1212.20-0ubuntu0.20.04.1 amd64front-end programs for PostgreSQL 12 ii postgresql-client-common255.pgdg20.04+1all manager for multiple PostgreSQL client versions ii postgresql-common 255.pgdg20.04+1all PostgreSQL database-cluster manager un postgresql-contrib-12 (no description available) un postgresql-doc-12 (no description available) un postgresql-doc-16 (no description available) un postgresql-pgmp (no description available) un postgresql-server-dev-12(no description available) un postgresql-server-dev-all (no description available) ~ ~ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 5.15.0-116.126-generic 5.15.158 Uname: Linux 5.15.0-116-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1001:123:86264:2024-08-24 20:34:27.778159678 -0400:2024-08-24 20:34:27.778159678 -0400:/var/crash/_usr_lib_oem-unity-auto-scale.py.1001.crash CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 14:36:15 2024 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-22 (3202 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-08-28 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2018-08-07T20:08:53.388109 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078267 Title: unresolvable error in upgrade to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074084] Re: Caplock inversed in Ubuntu 23.10
I see. I will try that and come back to you then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074084 Title: Caplock inversed in Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074084] [NEW] Caplock inversed in Ubuntu 23.10
Public bug reported:
The Caplock button on my OMEN16 Ubuntu 23.10/Win 11 laptop is inversed, it is
lit when it is not in Caplock state and vice virsa. For more detailed
information, see this bug report.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/267999
I basically just want to provide my system data to deal with that bug.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-44-generic 6.5.0-44.44
ProcVersionSignature: Ubuntu 6.5.0-44.44-generic 6.5.13
Uname: Linux 6.5.0-44-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: danny-wenjue-zhang 3833 F pipewire
danny-wenjue-zhang 3836 F wireplumber
/dev/snd/controlC0: danny-wenjue-zhang 3836 F wireplumber
/dev/snd/seq:danny-wenjue-zhang 3833 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 25 21:31:53 2024
InstallationDate: Installed on 2024-01-06 (201 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-44-generic
root=UUID=89848867-b092-4ef7-ae34-4b3c80a5da79 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-44-generic N/A
linux-backports-modules-6.5.0-44-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.10
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2024
dmi.bios.release: 15.21
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8BAB
dmi.board.vendor: HP
dmi.board.version: 76.53
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 76.53
dmi.modalias:
dmi:bvnInsyde:bvrF.21:bd05/29/2024:br15.21:efr76.53:svnHP:pnOMENbyHPGamingLaptop16-wf0xxx:pvrType1ProductConfigId:rvnHP:rn8BAB:rvr76.53:cvnHP:ct10:cvrChassisVersion:sku81L09PA#AB2:
dmi.product.family: 103C_5335M7 HP OMEN
dmi.product.name: OMEN by HP Gaming Laptop 16-wf0xxx
dmi.product.sku: 81L09PA#AB2
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074084
Title:
Caplock inversed in Ubuntu 23.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074084/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 267999] Re: Sometimes Caps Lock works inverted
Confirmed the bug in my OMEN16 Win11/Ubuntu 23.10 dual start system. The related issue can not be repeated in Windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/267999 Title: Sometimes Caps Lock works inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/267999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520979] Re: Grub multiboot is unable to load Xen under EFI
I see according to this: `https://xenbits.xen.org/docs/unstable/support- matrix.html` that Host UEFI SecureBoot status is 'Experimental' on versions 4.18 and 4.19, and no status on previous versions. Maybe I'll try v4.18 (Ubuntu Noble Numbat 24.04 uses Xen v4.17) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520979 Title: Grub multiboot is unable to load Xen under EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1520979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520979] Re: Grub multiboot is unable to load Xen under EFI
The problem is in Fedora 40 too. I have also tried the following (with Ubuntu Noble Numbat 24.04): Added new CodeSigning key to UEFI db keystore. Rebuilt shim-15.8 with the new key. Added Canonical Codesigning key from shim-signed source package to UEFI db keystore. Signed all my efi's with the new key (shimx64, mmx64, fbx64, grubx64, Xen) I didn't sign the kernel as I added the Canonical key to the db keystore. Results: Booted linux kernel fine. Still get same problem with Xen even though its signed, and the key is being recognised by SecureBoot and shim on the other efi's. Also added `insmod multiboot2` statements to `/etc/grub.d/20_linux_xen` so they would be at the top of each xen menu block in the `/boot/efi/grub/grub.cfg` Maybe I should get on the grub mailing lists before spending more time on this in case I'm wasting my time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520979 Title: Grub multiboot is unable to load Xen under EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1520979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520979] Re: Grub multiboot is unable to load Xen under EFI
The problem is in Ubuntu Jammy with version v2.06 of grub as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520979 Title: Grub multiboot is unable to load Xen under EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1520979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520979] Re: Grub multiboot is unable to load Xen under EFI
I tried to use Xen with Ubuntu Noble Numbat 24.04 with UEFI SecureBoot and it fails on line 179 of sb.c : https://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/kern/efi/sb.c with the message "prohibited by secure boot policy". I have repeated this with a clean Ubuntu Minimal Server install in a Qemu VM with UEFI. I am in the process of trying it with a clean Ubuntu Jammy minimal server VM. (which uses grub v2.06 instead of v2.12) I was looking at the code and wondering if it was something to do with the multiboot grub verifier, but I think I may have to install a debug version of grub to get the debug messages. I haven't found any bugs on the main grub bug report page about it as yet (https://savannah.gnu.org/bugs/?group=grub) I haven't submitted anything to the main bug list yet as I more familiar with launchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520979 Title: Grub multiboot is unable to load Xen under EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1520979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066581] [NEW] Mantic/Noble Distribution Upgrade could not install 'gconf2'
Public bug reported: After selecting to perform a Distribution Upgrade from Mantic to Noble Numbat within the update-manager I got a message from the upgrade process saying : "Could not install 'gconf2'. The upgrade will continue but the 'gconf2' package may not be in a working state. Please consider submitting a bug report about it. dependency problems - leaving triggers unprocessed. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:24.04.18 ProcVersionSignature: Ubuntu 6.5.0-35.35-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:5845369:2024-05-23 13:51:26.963325914 +1200:2024-05-23 13:51:27.039326860 +1200:/var/crash/_usr_bin_gnote.1000.crash 600:0:0:3059099:2024-05-23 13:49:22.63786 +1200:2024-05-23 13:49:22.641777836 +1200:/var/crash/gconf2.0.crash 640:1000:124:6654350:2024-05-23 13:51:19.671235207 +1200:2024-05-23 13:51:17.259205202 +1200:/var/crash/_usr_lib_x86_64-linux-gnu_gstreamer1.0_gstreamer-1.0_gst-plugin-scanner.1000.crash 600:117:124:37:2024-05-23 13:51:29.695359895 +1200:2024-05-23 13:51:29.695359895 +1200:/var/crash/_usr_bin_gnote.1000.uploaded 644:1000:124:0:2024-05-23 13:51:26.963325914 +1200:2024-05-23 13:51:26.963325914 +1200:/var/crash/_usr_bin_gnote.1000.upload CurrentDesktop: GNOME Date: Thu May 23 13:55:24 2024 InstallationDate: Installed on 2022-06-05 (718 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220602) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2024-05-23 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade mantic ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/2066581/+attachment/5781525/+files/Screenshot%20from%202024-05-23%2013-50-44.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066581 Title: Mantic/Noble Distribution Upgrade could not install 'gconf2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2066581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Ignore what I said about Noble Numbat, it was actually a fresh Mantic installation that creates the bpool with incorrect compatibility flags. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Just thought I would add the salient findings from Bug #2041739. * update-grub/grub-probe fails when the `feature@extensible_dataset` flag is enabled on bpool * this happens when the bpool is created without the `-o compatibility=grub2,ubuntu-22.04` compatibility flags and a subsequent snapshot is taken. * a successful work around is to backup bpool and recreate it using the `-o compatibility=grub2,ubuntu-22.04` flags Further thoughts: * apparently problem is still happening with fresh Ubuntu Noble Numbat installations, which implies NN installation process not creating bpool with correct compatibility flags * problem should be fixed in grub, but work-around compatibility flags works as long as they are used consistently * I am not sure how our findings relate with the discussion around kernel/module versions. I am using the latest version of Ubuntu Mantic with kernel version 6.5.0-28-generic successfully. I also have linux-genereic-hwe-22.04-edge package installed on my system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041739] Re: update-grub giving errors and apparently not locating /boot on correct zfs pool after upgrade to Ubuntu Mantic
*** This bug is a duplicate of bug 2051999 *** https://bugs.launchpad.net/bugs/2051999 That would seem to indicate the Ubuntu Mantic installation process is creating the bpool with zfs flags that are incompatible with grub. I wonder if the problem is still present in Noble Numbat/24.04? Are you able to check which zfs flags/features are set after the bpool is created? (use `zpool get all bpool` to get flags) You will need to backup your /boot directory and recreate you bpool with the `-o compatibility=grub2,ubuntu-22.04 \` option, as described earlier in this thread. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041739 Title: update-grub giving errors and apparently not locating /boot on correct zfs pool after upgrade to Ubuntu Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/2041739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670313] Re: armhf unit tests as root fail on adt tests, never run on builders
thanks all ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670313 Title: armhf unit tests as root fail on adt tests, never run on builders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1670313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
After 5 years there's still no fix. This is so annoying. I'm now getting rid of all snap packages and installing deb variants instead. Finally I'll purge snap and if these weird decisions keep on going I'll also move to another distro. Common Canonical. Seriously? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947431] Re: Black/boot logo screen on wayland session after installing nvidia drivers
** Description changed: Just did a fresh install. First thing I did was installing nvidia drivers. Tried wayland session and got a black screen with the boot logo page. Tried the instructions here: https://askubuntu.com/questions/1369250/how-do-i-enable-wayland-on- - ubuntu-21-10-nvidia but couldn't do it. I am submitting this as a bug + ubuntu-21-10-nvidia but didn't cut it. I am submitting this as a bug since it's a fresh install with the official drivers. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.74-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 22:27:53 2021 InstallationDate: Installed on 2021-10-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Just did a fresh install. First thing I did was installing nvidia drivers. Tried wayland session and got a black screen with the boot logo page. Tried the instructions here: https://askubuntu.com/questions/1369250/how-do-i-enable-wayland-on- ubuntu-21-10-nvidia but didn't cut it. I am submitting this as a bug since it's a fresh install with the official drivers. + + Another thing to notice is that using the recovery option on grub I was able to get a wayland session, but some apps would crash the session + and the nvidia GUI menu doesn't work (blank GUI) there but works + normally on X11. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.74-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 22:27:53 2021 InstallationDate: Installed on 2021-10-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947431 Title: Black/boot logo screen on wayland session after installing nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1947431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947431] [NEW] Black/boot logo screen on wayland session after installing nvidia drivers
Public bug reported: Just did a fresh install. First thing I did was installing nvidia drivers. Tried wayland session and got a black screen with the boot logo page. Tried the instructions here: https://askubuntu.com/questions/1369250/how-do-i-enable-wayland-on- ubuntu-21-10-nvidia but didn't cut it. I am submitting this as a bug since it's a fresh install with the official drivers. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.74-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 22:27:53 2021 InstallationDate: Installed on 2021-10-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947431 Title: Black/boot logo screen on wayland session after installing nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1947431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925833] Re: apt-transport-https reparses URLs, breaking CloudFront signing
Great, thanks for sharing both answers. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925833 Title: apt-transport-https reparses URLs, breaking CloudFront signing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925833] [NEW] apt-transport-https reparses URLs, breaking CloudFront signing
Public bug reported: CloudFront URL signing requires that the the whole URL matches the signature, as compared to S3 URLs which prune the querystring before validating the signature. The URL re-parsing which I'm pretty sure was introduced in resolving #1651923 decodes some HTML entities which were encoded before signing. That invalidates the signature and results in permission denied errors. In my case, the equal and semicolon chars from the return-content-disposition header are being decoded, but it applies to any entity which is "optionally" encoded. Personally, I think that the URL returned in a Location: redirect header should be handled as-is, and if some piece of garbage http server is generating redirects which contain spaces or are otherwise invalid, the problem lies with the web server generating invalid redirects and not in apt failing to follow broken URLs. I say that knowing full well that the http spec says those things should be identical, so CloudFront also falls into the general "garbage" category by breaking the spec by requiring a specific format for identical characters. Either way, things are what they are. Rather than unnecessarily fully reencoding the URL, I'd suggest that apt-transport-https (and presumably the http transport as well, but I don't know) should at most just replace the spaces with plusses or %20s to keep the original bug resolved without breaking other stuff. :) PS: I tried to report this against the apt-transport-https package, but the bug tool says that doesn't exist in Ubuntu. That's weird, considering it's definitely a package (https://packages.ubuntu.com/groovy/apt-transport-https), so I assume the apt maintainer will know how to triage. Sorry. ** Affects: apt (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/1925833 Title: apt-transport-https reparses URLs, breaking CloudFront signing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.
This fix breaks CloudFront URLs, because the reencoding of URLs results in some HTML entities being replaced by their plain characters. CloudFront signing requires that the the whole URL matches the signature, as compared to S3 URLs which prune the querystring before validating the signature. That explains why this fix worked ok on S3. I'll open a new bug since this is so old that reopening doesn't make sense, but also making a note here for future web search purposes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651923 Title: apt https method decodes redirect locations and sends them to the destination undecoded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] Re: Dell XPS 13 2in1 wakes from sleep when moved on 20.04
This patch has been included in 5.12-rc7. I have tried the Ubuntu mainline kernel build for 5.12-rc7. I can confirm that the changeset mentioned above works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] Re: Dell XPS 13 2in1 wakes from sleep when moved on 20.04
I found an interesting line in the dmesg output: intel-hid INTC1051:00: unknown event 0xcd The 0xcd event indicates a switch from or to tablet mode, confirming my diagnosis that the accelerometer wakes the laptop form suspend. Incidentally, goolging for this very event showed me the following patch: https://www.spinics.net/lists/platform-driver-x86/msg25277.html I would ask the Ubuntu Kernel team to include this as soon as possible in the OEM kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5472006/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5472005/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5472004/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5472003/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5472002/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5472001/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5472000/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471999/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471989/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] Re: Dell XPS 13 2in1 wakes from sleep when moved on 20.04
apport information ** Tags added: apport-collected focal wayland-session ** Description changed: Dell XPS 13 9310 2in1, running Ubuntu OEM kernel (20.04) on 20.04 LTS. Laptop suspends and wakes up when lid is closed and opened, respectively. Laptop erroneously wakes up also in following conditions: 1. lid is closed and laptop is moved/rotated. 2. lid is open, suspended manually (via power button), and laptop is moved/rotated. Until I found out about case 2, I assumed that the hall sensor triggered on slight opening of the lid. However, case 2 shows that this is unlikely a hard ware defect/sensitivity. I suspect that the accelaration sensor triggers waking up from sleep. I can confirm that the problem persist after stopping the iio-sensor-prox service via systemctl. I did not find which kernel module is reponsible for tracking this sensor. Suggestions? + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: dvandyk1207 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-12-26 (65 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: Dell Inc. XPS 13 9310 2-in-1 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1048-oem root=UUID=9104c339-1746-4791-b1ff-0d439dfd75e0 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.6.0-1048.52-oem 5.6.19 + RelatedPackageVersions: + linux-restricted-modules-5.6.0-1048-oem N/A + linux-backports-modules-5.6.0-1048-oem N/A + linux-firmware 1.187.9 + Tags: wayland-session focal + Uname: Linux 5.6.0-1048-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/05/2020 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.1.1 + dmi.board.name: 0062CR + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 31 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd10/05/2020:svnDellInc.:pnXPS1393102-in-1:pvr:rvnDellInc.:rn0062CR:rvrA00:cvnDellInc.:ct31:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 13 9310 2-in-1 + dmi.product.sku: 09FF + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471988/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471998/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471997/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471996/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471995/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471991/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471993/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471994/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471992/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1917210/+attachment/5471990/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917210] [NEW] Dell XPS 13 2in1 wakes from sleep when moved on 20.04
Public bug reported: Dell XPS 13 9310 2in1, running Ubuntu OEM kernel (20.04) on 20.04 LTS. Laptop suspends and wakes up when lid is closed and opened, respectively. Laptop erroneously wakes up also in following conditions: 1. lid is closed and laptop is moved/rotated. 2. lid is open, suspended manually (via power button), and laptop is moved/rotated. Until I found out about case 2, I assumed that the hall sensor triggered on slight opening of the lid. However, case 2 shows that this is unlikely a hard ware defect/sensitivity. I suspect that the accelaration sensor triggers waking up from sleep. I can confirm that the problem persist after stopping the iio-sensor-prox service via systemctl. I did not find which kernel module is reponsible for tracking this sensor. Suggestions? ** 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/1917210 Title: Dell XPS 13 2in1 wakes from sleep when moved on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1917210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809438] Re: systemd-resolved segfaults
I seem to be affected by the same issue. I get regular DNS query time- outs coinciding with a lot of the following log messages (syslog): systemd-resolved[1119]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Eventually systemd-resolved crashes. This happens more frequently (/or only) when connected to wifi. Trace extracted from an Apport crash report (cause was a segmentation fault): #0 0x7efeaa3c62ed in sd_event_source_unref (p=0x1b01030036100326) at ../src/libsystemd/sd-event/sd-event.c:1912 __PRETTY_FUNCTION__ = "sd_event_source_unref" #1 0x561894e7f162 in dns_query_stop (q=q@entry=0x5618967255b0) at ../src/resolve/resolved-dns-query.c:336 c = __PRETTY_FUNCTION__ = "dns_query_stop" #2 0x561894e7f1d0 in dns_query_complete (q=0x5618967255b0, state=) at ../src/resolve/resolved-dns-query.c:528 __PRETTY_FUNCTION__ = "dns_query_complete" #3 0x561894e7f33f in on_query_timeout (s=, usec=, userdata=) at ../src/resolve/resolved-dns-query.c:539 q = __PRETTY_FUNCTION__ = "on_query_timeout" #4 0x7efeaa3ceb76 in source_dispatch (s=s@entry=0x561896722680) at ../src/libsystemd/sd-event/sd-event.c:3201 saved_type = SOURCE_TIME_BOOTTIME r = __PRETTY_FUNCTION__ = "source_dispatch" __func__ = "source_dispatch" #5 0x7efeaa3ceef1 in sd_event_dispatch (e=e@entry=0x5618966cfcd0) at ../src/libsystemd/sd-event/sd-event.c:3634 ref = p = r = __PRETTY_FUNCTION__ = "sd_event_dispatch" #6 0x7efeaa3d0928 in sd_event_run (e=e@entry=0x5618966cfcd0, timeout=timeout@entry=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:3692 r = 1 __PRETTY_FUNCTION__ = "sd_event_run" #7 0x7efeaa3d0b4f in sd_event_loop (e=0x5618966cfcd0) at ../src/libsystemd/sd-event/sd-event.c:3714 ref = 0x5618966cfcd0 r = __PRETTY_FUNCTION__ = "sd_event_loop" #8 0x561894e5a22a in run (argv=, argc=) at ../src/resolve/resolved.c:84 notify_stop = 0x561894ea3d70 "STOPPING=1\nSTATUS=Shutting down..." Log statement from the kernel log: traps: systemd-resolve[1162] general protection fault ip:7efeaa3c62ed sp:7ffef7d6f1b0 error:0 in libsystemd-shared-245.so[7efeaa39e000+174000] (Although the trace started with a notify_stop, the system was not shutdown at the time) Other details: Release: Ubuntu 20.04.01 (amd64) Systemd package version: 245.4-4ubuntu3.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809438 Title: systemd-resolved segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915789] Re: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
That will teach me for subscribing to hirsute-proposed updates! Hopefully I can switch the ownership back from a LiveUSB . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915789 Title: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911136] Re: kernel module build for Nvidia crash and virtualBox too
*** This bug is a duplicate of bug 1901904 *** https://bugs.launchpad.net/bugs/1901904 ** Attachment added: "detailed system information" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1911136/+attachment/5456090/+files/inxi.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911136 Title: kernel module build for Nvidia crash and virtualBox too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1911136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911136] Re: kernel module build for Nvidia crash and virtualBox too
*** This bug is a duplicate of bug 1901904 *** https://bugs.launchpad.net/bugs/1901904 The duplicate Status could be wrong. It doesn't only affect VirtualBox. The following things aren't working for me when booting with kernel 5.8 (with 5.4 everything works fine): - keyboard backlight - keyboard fn keys - wifi - touchpad There may some more broken things but these I noticed directly. Device: Asus UX392F -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911136 Title: kernel module build for Nvidia crash and virtualBox too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1911136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900891] Re: /usr/sbin/openconnect: undefined symbol: openconnect_has_tss2_blob_support, version OPENCONNECT_5_5
For what it is worth, I have been running openconnect built from source, I just can't wrap Plasma's GUI around it. 0-11:41 djh@djh-p5510 ~/openconnect-8.00> head openconnect #! /bin/bash # openconnect - temporary wrapper script for .libs/openconnect # Generated by libtool (GNU libtool) 2.4.6 # # The openconnect program cannot be directly executed until all the libtool # libraries that it depends on are installed. # # This wrapper script should never be moved out of the build directory. # If it is, it will not operate correctly. 0-11:41 djh@djh-p5510 ~/openconnect-8.00> ls .libs/ libopenconnect.la@ libopenconnect_la-http.o libopenconnect_la-auth-common.o libopenconnect.lai libopenconnect_la-auth-globalprotect.o libopenconnect_la-iconv.o libopenconnect_la-auth-juniper.olibopenconnect_la-library.o libopenconnect_la-auth.olibopenconnect_la-lzo.o libopenconnect_la-compat.o libopenconnect_la-lzs.o libopenconnect_la-cstp.olibopenconnect_la-mainloop.o libopenconnect_la-digest.o libopenconnect_la-ntlm.o libopenconnect_la-dtls.olibopenconnect_la-oath.o libopenconnect_la-esp.o libopenconnect_la-oncp.o libopenconnect_la-esp-seqno.o libopenconnect_la-script.o libopenconnect_la-gnutls-dtls.o libopenconnect_la-ssl.o libopenconnect_la-gnutls-esp.o libopenconnect_la-tun.o libopenconnect_la-gnutls.o libopenconnect_la-version.o libopenconnect_la-gnutls_tpm2.o libopenconnect.so@ libopenconnect_la-gnutls_tpm.o libopenconnect.so.5@ libopenconnect_la-gpst.olibopenconnect.so.5.5.0* libopenconnect_la-http-auth.o openconnect* 0-11:41 djh@djh-p5510 ~/openconnect-8.00> .libs/openconnect .libs/openconnect: symbol lookup error: .libs/openconnect: undefined symbol: openconnect_has_tss2_blob_support, version OPENCONNECT_5_5 That looks familiar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900891 Title: /usr/sbin/openconnect: undefined symbol: openconnect_has_tss2_blob_support, version OPENCONNECT_5_5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1900891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900891] Re: /usr/sbin/openconnect: undefined symbol: openconnect_has_tss2_blob_support, version OPENCONNECT_5_5
A workaround for me for now: 1) Build openconnect from source 2) sudo make install 3) sudo ln /usr/local/sbin/openconnect /usr/sbin/openconnect Now KDE Plasma can connect to my VPN. Yay! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900891 Title: /usr/sbin/openconnect: undefined symbol: openconnect_has_tss2_blob_support, version OPENCONNECT_5_5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1900891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900891] [NEW] /usr/sbin/openconnect: undefined symbol: openconnect_has_tss2_blob_support, version OPENCONNECT_5_5
Public bug reported: > /usr/sbin/openconnect /usr/sbin/openconnect: symbol lookup error: /usr/sbin/openconnect: undefined symbol: openconnect_has_tss2_blob_support, version OPENCONNECT_5_5 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openconnect 8.05-1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 21 11:30:48 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-15 (858 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: openconnect UpgradeStatus: Upgraded to focal on 2020-10-13 (8 days ago) ** Affects: openconnect (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/1900891 Title: /usr/sbin/openconnect: undefined symbol: openconnect_has_tss2_blob_support, version OPENCONNECT_5_5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1900891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899103] Re: libpam-cap causes PAM applications to crash
Confirmed the issue ** Changed in: libcap2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899103 Title: libpam-cap causes PAM applications to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1899103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898031] Re: Upgrading from 18.04.4 LTS to 20.04.1 LTS
Fix Make sure using latest official mirror. e.g. us.archive.ubuntu.com then try sudo apt update sudo apt upgrade sudo do-release-upgrade ** Attachment removed: "/var/log/dist-upgrade/main.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898031/+attachment/5416044/+files/main.log ** Attachment removed: "CurrentDmesg.txt.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898031/+attachment/5416045/+files/CurrentDmesg.txt.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898031/+attachment/5416046/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898031/+attachment/5416047/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898031/+attachment/5416048/+files/ProcEnviron.txt ** Attachment removed: "VarLogDistupgradeAptclonesystemstate.tar.gz" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898031/+attachment/5416049/+files/VarLogDistupgradeAptclonesystemstate.tar.gz ** Attachment removed: "VarLogDistupgradeAptlog.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898031/+attachment/5416050/+files/VarLogDistupgradeAptlog.txt ** Attachment removed: "VarLogDistupgradeLspcitxt.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898031/+attachment/5416051/+files/VarLogDistupgradeLspcitxt.txt ** Attachment removed: "VarLogDistupgradeMainlog.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898031/+attachment/5416052/+files/VarLogDistupgradeMainlog.txt ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898031 Title: Upgrading from 18.04.4 LTS to 20.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
I'm experiencing the same issue in 20.04, dual monitor setup, fractional scaling using the default wayland on gnome 3.36.4. I have a vega 56 and use the amdgpu drivers. If I leave the ghost cursor and get on with something else it will eventually change to a square of random brightly coloured pixels overlaid (doesn't show on printscreen). It's as if there's a dodgy block of vram where the display memory is. Logging out and back in solves the issue until my screen locks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795207] Re: upgrade to ubuntu-18.04: 'ubuntu-minimal' not found
Confirmed affecting me upgrating from 18.04.5 LTS to 20.04.1 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795207 Title: upgrade to ubuntu-18.04: 'ubuntu-minimal' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1795207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898031] [NEW] Upgrading from 18.04.4 LTS to 20.04.1 LTS
*** This bug is a security vulnerability *** Private security bug reported: 1) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 3) Upgrade should run without issue 4) Upgrade failed /var/log/dist-upgrade/mail.log file attached ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 [origin: unknown] ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu Date: Thu Oct 1 21:27:26 2020 InstallationDate: Installed on 2014-07-11 (2273 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-01 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages ** Attachment added: "/var/log/dist-upgrade/mail.log" https://bugs.launchpad.net/bugs/1898031/+attachment/5416044/+files/main.log ** Information type changed from Public to Private Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898031 Title: Upgrading from 18.04.4 LTS to 20.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
Since no one responded yet, I installed the updated packages from #33, and still have the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861219] Re: QLogic FC paths added when issue_lip
Hello, Can this be compiled for me to test? Thank you, Danny Marceau -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861219 Title: QLogic FC paths added when issue_lip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882933] [NEW] If I want to scan some files with clamdscan I get the following error: lstat() failed: No such file or directory. ERROR
Public bug reported: lstat() failed: No such file or directory. ERROR ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: clamav 0.102.3+dfsg-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jun 10 13:10:12 2020 InstallationDate: Installed on 2020-05-31 (9 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: clamav UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: clamav (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal 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/1882933 Title: If I want to scan some files with clamdscan I get the following error: lstat() failed: No such file or directory. ERROR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1882933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876210] Re: cryptsetup: WARNING: could not determine root device from /etc/fstab
I have experienced this now, on a VM. Kernel Panic,with: Cannot open root device "vda1" or unknown-block(0,0): error -6 5.3.0-53-generic I reboot and manually select the older kernel from GRUB. (4.15.0-101-generic) If I do this: djh@stage-batchexecutionservice0 ~> sudo update-initramfs -u -k 5.3.0-53-generic [sudo] password for djh: update-initramfs: Generating /boot/initrd.img-5.3.0-53-generic djh@stage-batchexecutionservice0 ~> sudo reboot I reproduce the kernel panic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876210 Title: cryptsetup: WARNING: could not determine root device from /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1876210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
verified pulseaudio version - 1:11.1-1ubuntu7.7 in a hp sff[0] which has dual front jacks, works well, didn't find any Regression potential. [0]https://www8.hp.com/h20195/v2/GetPDF.aspx/4AA7-5395EEAP.pdf ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
Thanks, on Lubuntu 18.04.4 LTS, it's /lib/udev/hwdb.d/70-mouse.hwdb. I found the mouse far too slow after the update. Personally, I like to be able to quickly move the cursor from the left to right edge of my 1920 x 1080 screen in about an inch of physical movement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867421 Title: Microsoft Classic IntelliMouse moves way too fast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
I'm running Lubuntu 18.04.4 LTS and recently upgraded to a Microsoft Classic Intellimouse and find the current speed to be fine. Settings at present are the defaults (in Input Device Preferences, acceleration 2.0 and sensitivity 10). I received notification about this update today and am concerned I won't be able to change back to the current speed (cap will be put in place). Please confirm that this will be possible and if the update/changes will be easy to remove/reset later if not (steps for this would be useful). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867421 Title: Microsoft Classic IntelliMouse moves way too fast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871194] Re: nagios-nrpe-server fails to launch after reboot
We use libnss-ldapd. I think it may be sufficient to claim: "System users generally have to be resolvable during early boot already. This means they should not be provided by any networked service ..." [1] So, is this even a bug? If your OS uses systemd, then you need to ensure your system users are resolvable early in boot. I am disappointed that the tmpfiles service can't make your tmpfiles when you launch the service that requires them. I mean ... really? But that is life. Stick your nagios user and group in /etc/passwd and /etc/group and focus on those things that make you happy in this life. If you agree, then please feel free to close this out. [1] https://systemd.io/UIDS-GIDS/#notes-on-resolvability-of-user-and- group-names ** Changed in: nagios-nrpe (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871194 Title: nagios-nrpe-server fails to launch after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1871194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871194] Re: nagios-nrpe-server fails to launch after reboot
Paride, IF the nagios user is in LDAP, then /var/run/nagios will not be created by systemd at boot time, or any time after that. I can confirm that the following sequences fail to get nagios-nrpe- server running: sudo service nagios-nrpe-server restart sudo service nagios-nrpe-server stop sudo service nagios-nrpe-server start sudo systemctl stop nagios-nrpe-server sudo systemctl start nagios-nrpe-server Nothing in there triggers systems to create the missing directory: May 05 11:04:08 dmz-gnt03-04 systemd[1]: Started Nagios Remote Plugin Executor. May 05 11:04:08 dmz-gnt03-04 nrpe[10603]: Starting up daemon May 05 11:04:08 dmz-gnt03-04 nrpe[10603]: Cannot write to pidfile '/var/run/nagios/nrpe.pid' - check your privileges. May 05 11:04:08 dmz-gnt03-04 systemd[1]: nagios-nrpe-server.service: Main process exited, code=exited, status=2/INVALIDARGUMENT May 05 11:04:08 dmz-gnt03-04 systemd[1]: nagios-nrpe-server.service: Failed with result 'exit-code'. > ls -ld /var/run/nagios ls: cannot access '/var/run/nagios': No such file or directory The only recourse is manual mkdir/chown. ** Changed in: nagios-nrpe (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871194 Title: nagios-nrpe-server fails to launch after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1871194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871194] Re: nagios-nrpe-server fails to launch after reboot
Paride, unfortunately, when systemd fails to create /var/lib/nagios during system boot, the nagios-nrpe-server service can not be started manually. If the operator creates the missing directory and chowns it to nagios, they can then start the service manually. ** Changed in: nagios-nrpe (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871194 Title: nagios-nrpe-server fails to launch after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1871194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871194] Re: nagios-nrpe-server fails to launch after reboot
I am still testing but it looks like the problem for me is that we have (had) the nagios user in LDAP. Systemd says that the tmpfiles.d stuff will NOT work when you specify a non-local user. I think it is more correct to provision our system-level users in system-level files. I should have a more conclusive understanding next week, but this bug may be more of a feature request, at best. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871194 Title: nagios-nrpe-server fails to launch after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1871194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876210] Re: cryptsetup: WARNING: could not determine root device from /etc/fstab
If I set the UUID of /, the warnings from update-initramfs disappear. 0-16:40 djh@c24-03-01 ~> grep UUID /etc/fstab # device; this may be used with UUID= as a more robust way to name devices UUID="9d35e010-3466-4f75-8adb-cd770c67762c" / ext4 defaults 0 0 0-16:39 djh@c24-03-01 ~> sudo update-initramfs -u -k 5.3.0-51-generic update-initramfs: Generating /boot/initrd.img-5.3.0-51-generic Bootstrap on the kernel yields the same kernel panic, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876210 Title: cryptsetup: WARNING: could not determine root device from /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1876210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876210] [NEW] cryptsetup: WARNING: could not determine root device from /etc/fstab
Public bug reported: My system can not reboot on its default kernel. I get a kernel panic: VFS: Cannot open root device "md0p1" or unknown-block(0,0): error -6 I go to grub and boot the previous kernel successfully. 0-16:29 djh@c24-03-01 ~> uname -a Linux c24-03-01.mtv.quantifind.com 5.3.0-47-generic #39~18.04.1-Ubuntu SMP Mon Apr 6 17:04:32 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 0-16:29 djh@c24-03-01 ~> sudo update-initramfs -u -k 5.3.0-51-generic update-initramfs: Generating /boot/initrd.img-5.3.0-51-generic cryptsetup: WARNING: failed to detect canonical device of /dev/md0p1 cryptsetup: WARNING: could not determine root device from /etc/fstab Here is what I have got: 0-16:29 djh@c24-03-01 ~> cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/md0p1 during curtin installation /dev/md0p1 / ext4 defaults 0 0 # /boot/efi was on /dev/sdc1 during curtin installation /dev/disk/by-uuid/0386-D289 /boot/efi vfat defaults 0 0 /swap.img noneswapsw 0 0 0-16:30 djh@c24-03-01 ~> cat /proc/mdstat Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 sdf2[0] sde2[1] 233772032 blocks super 1.2 [2/2] [UU] bitmap: 2/2 pages [8KB], 65536KB chunk unused devices: 0-16:30 djh@c24-03-01 ~> cat /etc/crypttab # luks-sda /dev/sda /etc/luks-keyfile luks luks-sdb /dev/sdb /etc/luks-keyfile luks luks-sdc /dev/sdc /etc/luks-keyfile luks luks-sdd /dev/sdd /etc/luks-keyfile luks The luks devices go into LVM and are used by ganeti. 0-16:30 djh@c24-03-01 ~> apt show cryptsetup Package: cryptsetup Version: 2:2.0.2-1ubuntu1.1 [ . . . ] 0-16:31 djh@c24-03-01 ~> apt show cryptsetup-bin Package: cryptsetup-bin Version: 2:2.0.2-1ubuntu1.1 Possibly-related issue upstream. It looks like debian has a newer version? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784881 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-47-generic 5.3.0-47.39~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Thu Apr 30 16:33:32 2020 InstallationDate: Installed on 2020-02-27 (63 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed 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/1876210 Title: cryptsetup: WARNING: could not determine root device from /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1876210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872291] [NEW] grub installer
Public bug reported: grub instller ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.14 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394.3 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 07:10:11 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.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 bionic ubiquity-18.04.14.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872291 Title: grub installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1872291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872028] [NEW] [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound from internal speaker
Public bug reported: [Reproduce steps] 1. Install 20.04 daily build on 4/9. 2. Do dist-upgrade after installation. 3. Go to System Setting->Sound->Output, press the test button. 4. There is no sound output while press the Front right and Front left button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1358 F pulseaudio /dev/snd/pcmC0D0c: u 1358 F...m pulseaudio /dev/snd/pcmC0D0p: u 1358 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 04:11:26 2020 InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1358 F pulseaudio /dev/snd/pcmC0D0c: u 1358 F...m pulseaudio /dev/snd/pcmC0D0p: u 1358 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: HP dmi.bios.version: R12 Ver. 02.03.01 dmi.board.name: 85A2 dmi.board.vendor: HP dmi.board.version: KBC Version 08.93.00 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR12Ver.02.03.01:bd09/26/2019:svnHP:pnHPProOne400G520.0-inAll-in-One:pvr:rvnHP:rn85A2:rvrKBCVersion08.93.00:cvnHP:ct13:cvr: dmi.product.family: 103C_53307F HP ProOne dmi.product.name: HP ProOne 400 G5 20.0-in All-in-One dmi.product.sku: 6AE44AV dmi.sys.vendor: HP ** Affects: alsa-driver (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/1872028 Title: [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound from internal speaker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1872028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871810] [NEW] package gir1.2-flatpak-1.0:amd64 1.6.2-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: sudo apt update && sudo apt upgrade -y ProblemType: Package DistroRelease: Ubuntu 20.04 Package: gir1.2-flatpak-1.0:amd64 1.6.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 Date: Thu Apr 9 10:38:48 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1ubuntu1 SourcePackage: flatpak Title: package gir1.2-flatpak-1.0:amd64 1.6.2-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flatpak (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/1871810 Title: package gir1.2-flatpak-1.0:amd64 1.6.2-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1871810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871194] [NEW] nagios-nrpe-server fails to launch after reboot
Public bug reported: Ubuntu 18.04, nagios-nrpe-server 3.2.1-1ubuntu1 At boot time, the service fails with this error message: Cannot write to pidfile '/var/run/nagios/nrpe.pid' - check your privileges. I can make /var/run/nagios/ and chown it to nagios manually, but /var/run appears to get wiped at boot time. I reckon the systemd service file can be configured to handle the making of the subdirectory? *** 0-11:43 djh@c24-03-02 ~> lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 0-11:43 djh@c24-03-02 ~> apt-cache policy nagios-nrpe-server nagios-nrpe-server: Installed: 3.2.1-1ubuntu1 Candidate: 3.2.1-1ubuntu1 Version table: *** 3.2.1-1ubuntu1 500 500 http://archive.mtv.qd.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: nagios-nrpe (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/1871194 Title: nagios-nrpe-server fails to launch after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1871194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
I am seeing this same issue on my system. Any help would be greatly appreciated. I am using Ubuntu 16.04 with the 4.15.0-88-generic kernel. I have seen it on both host controllers on the motherboard. Here is the info for the host controllers. 00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [8086:a2af] (prog-if 30 [XHCI]) Subsystem: ASRock Incorporation Device [1849:a2af] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/bugs/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861219] Re: QLogic FC paths added when issue_lip
Hello, I have updated the kernel and now see a different issue with paths. Instead of gaining an extra path, I lose all paths but the one I issue the lip reset on. root@ICTM1607S02H4:~# uname -r 5.5.0-050500-generic 36d039ea0003ef43c2b545930232c dm-2 NETAPP,INF-01-00 size=100G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw |-+- policy='service-time 0' prio=50 status=active | |- 12:0:0:4 sdd 8:48 active ready running | `- 14:0:0:4 sdn 8:208 active ready running `-+- policy='service-time 0' prio=10 status=enabled |- 13:0:0:4 sdi 8:128 active ready running `- 15:0:0:4 sds 65:32 active ready running root@ICTM1607S02H4:~# echo 1 > /sys/class/fc_host/host15/issue_lip multipath -ll 36d039ea0003ef43c2b545930232c dm-2 NETAPP,INF-01-00 size=100G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw |-+- policy='service-time 0' prio=0 status=enabled | |- 12:0:0:4 sdd 8:48 failed faulty running | `- 14:0:0:4 sdn 8:208 failed faulty running `-+- policy='service-time 0' prio=10 status=active |- 13:0:0:4 sdi 8:128 failed faulty running `- 15:0:0:4 sds 65:32 active ready running Paths do not come back. 36d039ea0003ef43c2b545930232c dm-2 NETAPP,INF-01-00 size=100G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=10 status=active `- 15:0:0:4 sds 65:32 active ready running Thank you, Danny Marceau -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861219 Title: QLogic FC paths added when issue_lip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861219] Re: QLogic FC paths added when issue_lip
** Attachment added: "apport.linux-image-4.15.0-74-generic.whedmz3u.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+attachment/5326074/+files/apport.linux-image-4.15.0-74-generic.whedmz3u.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861219 Title: QLogic FC paths added when issue_lip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861219] Re: QLogic FC paths added when issue_lip
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+attachment/5326076/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861219 Title: QLogic FC paths added when issue_lip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861219] Re: QLogic FC paths added when issue_lip
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+attachment/5326077/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861219 Title: QLogic FC paths added when issue_lip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861219] Re: QLogic FC paths added when issue_lip
** Attachment added: "hung task log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+attachment/5326075/+files/hung%20task%20log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861219 Title: QLogic FC paths added when issue_lip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861219] Re: QLogic FC paths added when issue_lip
The zip file originally attached includes apport.linux- image-4.15.0-74-generic.whedmz3u.apport ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861219 Title: QLogic FC paths added when issue_lip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861219] [NEW] QLogic FC paths added when issue_lip
Public bug reported: My QLogic direct-connect SANboot host with Ubuntu Server 18.04 LTS is seeing paths added during testing. Specifically added when running the command below: echo 1 > /sys/class/fc_host/host15/issue_lip There should be four paths total but if I run the command above five times, I will see nine total paths. The server will hang and require a reboot eventually as multiple hung_task_timeout errors show up in logs. Information on HBAs below: root@ICTM1607S02H4:~# cat /sys/class/fc_host/host*/symbolic_name QLE2742 FW:v8.08.231 DVR:v10.00.00.02-k QLE2742 FW:v8.08.231 DVR:v10.00.00.02-k QLE2692 FW:v8.08.231 DVR:v10.00.00.02-k QLE2692 FW:v8.08.231 DVR:v10.00.00.02-k An example of what a volume looks like in multipath -ll after the issue_lip occurs: root@ICTM1607S02H4:~# multipath -ll 36d039ea0003ebb14009e58b1fabf dm-3 NETAPP,INF-01-00 size=160G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw |-+- policy='service-time 0' prio=50 status=active | |- 13:0:0:0 sdl 8:176 active ready running | |- 15:0:0:0 sdq 65:0 active ready running | `- 15:0:1:0 sdv 65:80 active ready running `-+- policy='service-time 0' prio=10 status=enabled |- 12:0:0:0 sdb 8:16 active ready running `- 14:0:0:0 sdc 8:32 active ready running Notice how a path is added after issue_lip. 1) version_signature.log Ubuntu 4.15.0-74.84-generic 4.15.18 2) lspci -vnvn output is in a file attached. root@ICTM1607S02H4:~# lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 root@ICTM1607S02H4:~# apt-cache policy linux-image-generic linux-image-generic: Installed: 4.15.0.74.76 Candidate: 4.15.0.74.76 Version table: *** 4.15.0.74.76 500 500 http://repomirror-ict.eng.netapp.com/ubuntu bionic-updates/main amd64 Packages 500 http://repomirror-ict.eng.netapp.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.20.23 500 500 http://repomirror-ict.eng.netapp.com/ubuntu bionic/main amd64 Packages I expected the bus reset to quickly add and remove, but it seems removal is not happening. The number of paths grow after each bus reset causing instability with the OS. I have attached logs.zip which contains four files. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "logs.zip" https://bugs.launchpad.net/bugs/1861219/+attachment/5323620/+files/logs.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861219 Title: QLogic FC paths added when issue_lip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854650] [NEW] Installation will not finish after "CD" error (boot USB)
Public bug reported: Installer did not find software to install (CD configuration errror) I am trying to install from a live USB. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-lowlatency 5.3.1 Uname: Linux 5.3.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 Date: Sun Dec 1 21:42:37 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz initrd=/casper/initrd file=/cdrom/preseed/ubuntustudio.seed quiet splash --- persistent LiveMediaBuild: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.21 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854650 Title: Installation will not finish after "CD" error (boot USB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1854650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849368] Re: apt-get update issues invalid range requests for previously completed downloads
Looking deeper, I think we might also have a backend that's not correctly handling If-Range and returning the 416 before considering if the Release file is out of date, which is why we get stuck in a file size mismatch between Releases and Packages.gz. Does look like there are maybe some issues around the handling of that error, and certainly the check for the host supporting range support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849368 Title: apt-get update issues invalid range requests for previously completed downloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849368] [NEW] apt-get update issues invalid range requests for previously completed downloads
Public bug reported: When an apt-get update fails, for instance due to a mismatch between the Release and Packages.gz due to a mirror sync/index update, it leaves files in the /var/lib/apt/lists/partial for the distribution: 15466565 16 -rw-r--r-- 1 root root13860 Oct 22 12:50 /var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release 1543 4 -rw-r--r-- 1 root root 475 Oct 22 12:50 /var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg 15471150 0 -rw-r--r-- 1 root root0 Oct 22 12:52 /var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED In this case both Release and Release.gpg were complete, however when running apt-get update again it issues the revalidation requests for these resources with Range headers that are the length of the file resulting in '416 Requested Range Not Satisfiable': GET .../Release HTTP/1.1 Cache-Control: max-age=0 Accept: text/* Range: bytes=13860- If-Range: Tue, 22 Oct 2019 12:50:05 GMT User-Agent: Debian APT-HTTP/1.3 (1.6.12) HTTP/1.1 416 Requested Range Not Satisfiable It appears: - There's no way for apt-get to know if the file is complete so this logic will always be hit if the file exists https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962 - The logic for determining whether a server supports range requests is only entered if an Accept-Range header exists, however an absence of this header means support is not available - https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251 ** Affects: apt (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/1849368 Title: apt-get update issues invalid range requests for previously completed downloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849368] Re: apt-get update issues invalid range requests for previously completed downloads
Excuse the slightly bogus filenames in that listing - I manually redacted our host/distribution details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849368 Title: apt-get update issues invalid range requests for previously completed downloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841054] [NEW] package grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit st
Public bug reported: I reinstalled ubuntu 18.04 in which I used a partition that was used by OpenSuse before. After installation of Ubuntu I performed the first update when a system problem was mentioned for which this error report was made. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Aug 22 14:34:02 2019 DuplicateSignature: package:grub-efi-amd64-signed:1.93.14+2.02-2ubuntu8.13 Setting up grub-efi-amd64-signed (1.93.14+2.02-2ubuntu8.13) ... dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 255 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 255 InstallationDate: Installed on 2019-08-20 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.11 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 255 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841054 Title: package grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1841054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818435] [NEW] grub package cant be installed
Public bug reported: Grub wasn't able to install for some reason ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 21:07:54 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) 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 bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818435 Title: grub package cant be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1818435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816846] Re: segfault in libc-2.23.so netinstall installation pxe
Confirming the issue. Using initrd.gz and linux from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/, as suggested above, works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816846 Title: segfault in libc-2.23.so netinstall installation pxe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1816846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816876] Re: Ubuntu 16.04 amd64 netboot install fails with segfault
I'm also hitting this bug with the netinstall. ** Attachment added: "qemu screenshot" https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1816876/+attachment/5240549/+files/Screenshot%20from%202019-02-21%2008-57-23.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816876 Title: Ubuntu 16.04 amd64 netboot install fails with segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1816876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769137] Re: after 17.10->18.4 upgrade, the system did not start due to missing libGL.so.1 and libGLESv2.so.2 files
I had the same issue when upgrading from 16.04.5 to 18.04.1 LTS on a Intel NUC NUC8i3BEH model. I used the fix that yaroslav used and it works also in my case: ln -s /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 /usr/lib/x86_64-linux-gnu/libGL.so.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769137 Title: after 17.10->18.4 upgrade, the system did not start due to missing libGL.so.1 and libGLESv2.so.2 files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1769137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
I have an Apple MacBook Pro 11,2 running Cosmic with this same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786951] Re: Update to 60.0
Hi there, I wanted to inquire on the status of Thunderbird 60.2.1 being available on Ubuntu's xenial repo. Any news on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786951 Title: Update to 60.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1786951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790531] Re: Choosing encryption in installer encrypts disk before confirmation of installation
Any assistance would really be appreciated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790531 Title: Choosing encryption in installer encrypts disk before confirmation of installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1790531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790531] [NEW] Choosing encryption in installer encrypts disk before confirmation of installation
Public bug reported: When testing out a new OS, I chose the option to install Ubuntu and enable LUKS encryption + LVM. I was waiting for the confirmation page to ensure that the installer was installing to the correct disk. It turns out I'd chosen the wrong disk (my main disk) and I figured that I'd simply be able to rollback the installer at the confirmation screen. The horrific violation of my expectations was that the installer _encrypted my main disk and setup LVM_ BEFORE i confirmed the installation. Now I'm stuck with my main disk being encrypted and unmountable. I'm trying desperately to recover my main disk which I cannot boot from, can decrypt but cannot mount. Please assist! ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: luks lvm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790531 Title: Choosing encryption in installer encrypts disk before confirmation of installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1790531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788655] [NEW] package grub-efi-amd64-signed 1.93.4+2.02-2ubuntu8.3 failed to install/upgrade: instalado grub-efi-amd64-signed paquete post-installation guión el subproceso devolvió un error con
Public bug reported: Just appear a confirmation window about send a report making an update & upgrade with sudo o terminal session ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64-signed 1.93.4+2.02-2ubuntu8.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Aug 23 11:24:35 2018 ErrorMessage: instalado grub-efi-amd64-signed paquete post-installation guión el subproceso devolvió un error con estado de salida 1 InstallationDate: Installed on 2014-12-23 (1339 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.93.4+2.02-2ubuntu8.3 failed to install/upgrade: instalado grub-efi-amd64-signed paquete post-installation guión el subproceso devolvió un error con estado de salida 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788655 Title: package grub-efi-amd64-signed 1.93.4+2.02-2ubuntu8.3 failed to install/upgrade: instalado grub-efi-amd64-signed paquete post- installation guión el subproceso devolvió un error con estado de salida 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1788655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786946] [NEW] grub-efi-amd64-signed package failed
Public bug reported: Installing on a laptop with an existing Windows 10 Pro installation. Installed 3 Ubuntu partitions (/, /home, and swap) within free space. Was install Bionic Beaver using a bootable USB flash drive. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 14 08:29:44 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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 bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786946 Title: grub-efi-amd64-signed package failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1786946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783385] Re: intel-microcode: update to 20180703 drop
Any update on the testing effort? The timeline on a release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783385 Title: intel-microcode: update to 20180703 drop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1783385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
