[Bug 2056303] Re: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
buntu 6.5.0-21.21~22.04.1-generic 6.5.8 ** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+attachment/5753222/+files/version.log ** Description changed: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. + + In the dmesg there is this line, + + [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd + + which somewhere was indicated that it would be improved in the hwe + kernel (that's why I tried it). Apparently the issue isn't fully fixex, + but the error seems to be handled better. (Source: + https://forums.linuxmint.com/viewtopic.php?t=410244 ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056303] Re: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+attachment/5753221/+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/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056303] [NEW] several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
Public bug reported: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/2056303/+attachment/5753220/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969664] Re: 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timout
Tried out the test image by adding the following lines to my Vagrantfile: config.vm.box = "ubuntu/jammy64" config.vm.box_url = "https://people.canonical.com/~jchittum/vagrant-testing/ubuntu-jammy-vagrant-TESTING-20220419.box"; This works for me on Debian Bullseye with virtualbox 6.1.32 and vagrant 2.2.14. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969664 Title: 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timout To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1969664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] Re: no memory hot-plugging in cloud-images
installed mentioned kernel version an did a memory hot-plugging test which was sucessfull kernel version: root@ubuntu:/boot# uname -a Linux ubuntu 5.4.0-1040-kvm #41-Ubuntu SMP Fri May 14 20:43:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux module in kernel configuration is set: root@ubuntu:/boot# grep -i CONFIG_ACPI_HOTPLUG_MEMORY /boot/config-5.4.0-1040-kvm CONFIG_ACPI_HOTPLUG_MEMORY=y memory before memory hot-plugging: root@ubuntu:/boot# free -k totalusedfree shared buff/cache available Mem:4027608 149232 3621316 480 257060 3828108 Swap: 0 0 0 memory after memory hot-plugging: root@ubuntu:/boot# free -k totalusedfree shared buff/cache available Mem: 10319064 249788 9802568 480 266708 9960284 Swap: 0 0 0 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] Re: no memory hot-plugging in cloud-images
root@ubuntu:~# cat /etc/apt/sources.list.d/ubuntu-focal-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ focal-proposed restricted main multiverse universe root@ubuntu:~# apt policy linux-image-kvm linux-image-kvm: Installed: 5.4.0.1033.31 Candidate: 5.4.0.1039.37 Version table: 5.4.0.1040.38 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 5.4.0.1039.37 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages *** 5.4.0.1033.31 100 100 /var/lib/dpkg/status 5.4.0.1009.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] Re: no memory hot-plugging in cloud-images
updated kernel: ... Setting up linux-image-5.4.0-1039-kvm (5.4.0-1039.40) ... I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-1039-kvm I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-1039-kvm ... unfortunately the kernel config is still not set: root@ubuntu:~# grep -i CONFIG_ACPI_HOTPLUG_MEMORY /boot/config-5.4.0-1039-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set ** Tags removed: verification-done-focal ** Tags added: verification-failed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] Re: no memory hot-plugging in cloud-images
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] Re: no memory hot-plugging in cloud-images
We tested the kernel release 5.4.0-1040-kvm and it looks much more better now. Memory gets added automaticly to the system. Also all events are visible now: monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[14203.153504] add /devices/system/memory/memory56 (memory) KERNEL[14203.153549] add /devices/system/memory/memory57 (memory) KERNEL[14203.153557] add /devices/system/memory/memory58 (memory) KERNEL[14203.153564] add /devices/system/memory/memory59 (memory) KERNEL[14203.153571] add /devices/system/memory/memory60 (memory) KERNEL[14203.153578] add /devices/system/memory/memory61 (memory) KERNEL[14203.153585] add /devices/system/memory/memory62 (memory) KERNEL[14203.153592] add /devices/system/memory/memory63 (memory) KERNEL[14203.158264] online /devices/system/memory/memory56 (memory) UDEV [14203.158904] add /devices/system/memory/memory56 (memory) KERNEL[14203.159596] online /devices/system/memory/memory58 (memory) UDEV [14203.159619] add /devices/system/memory/memory58 (memory) UDEV [14203.160208] online /devices/system/memory/memory58 (memory) KERNEL[14203.160232] online /devices/system/memory/memory60 (memory) UDEV [14203.160391] add /devices/system/memory/memory60 (memory) UDEV [14203.160688] online /devices/system/memory/memory56 (memory) UDEV [14203.161505] online /devices/system/memory/memory60 (memory) KERNEL[14203.161745] online /devices/system/memory/memory62 (memory) UDEV [14203.161818] add /devices/system/memory/memory62 (memory) KERNEL[14203.162450] online /devices/system/memory/memory63 (memory) UDEV [14203.162561] add /devices/system/memory/memory63 (memory) UDEV [14203.162769] online /devices/system/memory/memory62 (memory) UDEV [14203.163352] online /devices/system/memory/memory63 (memory) KERNEL[14203.172589] online /devices/system/memory/memory61 (memory) UDEV [14203.172722] add /devices/system/memory/memory61 (memory) UDEV [14203.173936] online /devices/system/memory/memory61 (memory) KERNEL[14203.180667] online /devices/system/memory/memory59 (memory) UDEV [14203.180817] add /devices/system/memory/memory59 (memory) UDEV [14203.182015] online /devices/system/memory/memory59 (memory) KERNEL[14203.188645] online /devices/system/memory/memory57 (memory) UDEV [14203.188715] add /devices/system/memory/memory57 (memory) UDEV [14203.189542] online /devices/system/memory/memory57 (memory) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] Re: no memory hot-plugging in cloud-images
qemu -name $ -m 1024,slots=255,maxmem=256G -M pc-i440fx-2.7 -enable-kvm -no-user-config -nodefaults -rtc base=utc -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0,max-bytes=1024,period=1000,bus=pci.0,addr=0x3 -netdev tap,ifname=$,id=hostnet6,vhost=on,vhostforce=on,vnet_hdr=on,script=no,downscript=no -device virtio-net-pci,netdev=hostnet6,id=net6,mac=$,bus=pci.0,addr=0x6 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc $ -vga qxl -cpu Haswell,+ssbd,+spec-ctrl,+vmx,+md-clear,+pdpe1gb,+stibp,-vmx-entry-load-perf-global-ctrl,-vmx-exit-load-perf-global-ctrl -smp 4,sockets=32,cores=1,maxcpus=64,threads=2 -object iothread,id=iothread5 -drive file=$,if=none,id=drive-virtio-disk5,format=raw,snapshot=off,aio=native,cache=none -device virtio-blk-pci,serial=$,bus=pci.0,addr=0x5,drive=drive-virtio-disk5,iothread=iothread5,num-queues=2,id=virtio-disk5,bootindex=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] Re: no memory hot-plugging in cloud-images
Well for memory hotplug the -m paramter is important. Here is how i started the VM: qemu -name myfancyvm -m 1024,slots=255,maxmem=256G... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489834/+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/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489833/+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/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489832/+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/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489831/+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/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489830/+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/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489829/+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/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489828/+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/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489827/+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/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] Re: no memory hot-plugging in cloud-images
apport information ** Tags added: apport-collected focal uec-images ** Description changed: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 + --- + ProblemType: Bug + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + CRDA: N/A + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 + ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-1038-kvm N/A + linux-backports-modules-5.4.0-1038-kvm N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.4.0-1038-kvm x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: 1.12.0-1 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-2.7 + dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-2.7 + dmi.sys.vendor: QEMU ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489825/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489826/+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/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602264] Re: libvirtd crashes with double free or corruption (out)
It is my opinion at this time that the bug is really in glibc. These functions like _nss_extrausers_endgrent() must share state from call to call, and therefore cannot possibly be thread safe. Unfortunately, the fix with making the shared state thread-local could probably make problems for callers which try to be careful when using these functions, but still take into account the globally shared state (which isn't global any more with the patch). For instance, if one thread calls _nss_extrausers_setgrent() under some lock, and another thread later calls _nss_extrausers_endgrent() under some lock, this would reasonably be expected to work, but it won't with the thread-local state. The getgrouplist() is documented as thread safe, while it calls these functions without locking. I think the fix should be made in glibc by adding appropriate locking there. I have filed a report for glibc: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1923738 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602264 Title: libvirtd crashes with double free or corruption (out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-extrausers/+bug/1602264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923738] Re: getgrouplist(3) is not thread-safe
Also see https://bugs.launchpad.net/ubuntu/+source/libnss-extrausers/+bug/1602264 which refers to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831390 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923738 Title: getgrouplist(3) is not thread-safe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1923738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923738] [NEW] getgrouplist(3) is not thread-safe
Public bug reported:
Hello glibc people!
While investigating some threading-related problem in a third-party
program, I discovered that this program calls getgrouplist(3) from
multiple threads, assuming that this is thread-safe. Indeed, the the man
page claims that it is:
┌───┬───┬┐
│Interface │ Attribute │ Value │
├───┼───┼┤
│getgrouplist() │ Thread safety │ MT-Safe locale │
└───┴───┴┘
However, consider the stack traces below.
[Switching to Thread 0x7f691c5ff700 (LWP 30714)]
Thread 353 "mount.quobyte" hit Breakpoint 10, 0x7f694e7eb3c0 in
_nss_extrausers_setgrent () from /usr/lib/libnss_extrausers.so.2
(gdb) bt
#0 0x7f694e7eb3c0 in _nss_extrausers_setgrent () from
/usr/lib/libnss_extrausers.so.2
#1 0x7f695c72750a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x7f695c72793e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3 0x7f695c727ab1 in getgrouplist () from /lib/x86_64-linux-gnu/libc.so.6
[ remaining frames are from the third-party program - omitted ]
(gdb) c
Continuing.
[Switching to Thread 0x7f68971ff700 (LWP 30934)]
Thread 375 "mount.quobyte" hit Breakpoint 12, 0x7f694e7eb460 in
_nss_extrausers_getgrent_r () from /usr/lib/libnss_extrausers.so.2
(gdb) bt
#0 0x7f694e7eb460 in _nss_extrausers_getgrent_r () from
/usr/lib/libnss_extrausers.so.2
#1 0x7f695c7275ad in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x7f695c72793e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3 0x7f695c727ab1 in getgrouplist () from /lib/x86_64-linux-gnu/libc.so.6
[ remaining frames are from the third-party program - omitted ]
getgrouplist calls _nss_*_setgrent() and _nss_*_getgrent_r(), which are not
thread safe. These functions can't be, since their signature has no way to
store the FILE* or other reference to the group file that they have to keep
between calls. Seeing these functions here should ring some alarm bells.
For example, this is from libnss-extrausers, showing the thead-unsafe
function signature and the global variable groupsfile it uses. This
signature is forced on it from NSS.
enum nss_status _nss_extrausers_setgrent(void) {
enum nss_status status = NSS_STATUS_SUCCESS;
if (groupsfile == NULL) {
groupsfile = fopen(GROUPSFILE, "re");
if (groupsfile == NULL)
status = errno == EAGAIN ? NSS_STATUS_TRYAGAIN :
NSS_STATUS_UNAVAIL;
} else {
rewind(groupsfile);
}
return status;
}
I looked at glibc/grp/initgroups.c, where getgrouplist() is defined. I
didn't find proof of locking there. The stack traces above are from
Bionic, but the sources I examined didn't seem to differ materially
between versions in this area.
ii libc-bin 2.27-3ubuntu1.4 amd64GNU C Library:
Binaries
ii libc-dev-bin 2.27-3ubuntu1.4 amd64GNU C Library:
Development binaries
ii libc6:amd64 2.27-3ubuntu1.4 amd64GNU C Library: Shared
libraries
ii libc6-dev:amd64 2.27-3ubuntu1.4 amd64GNU C Library:
Development Libraries and Header Files
So I can only conclude that getgrouplist(3) is not thread-safe, despite
documentation.
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #831390
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831390
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923738
Title:
getgrouplist(3) is not thread-safe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1923738/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920809] [NEW] Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade.
Public bug reported: I sent a bug report with ubuntu-bug ubuntu-release-upgrader-core ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18 Uname: Linux 4.15.0-139-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Mar 22 20:31:48 2021 InstallationDate: Installed on 2017-04-05 (1446 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-03-22 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920809 Title: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1920809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916959] Re: Start of LTS upgrade 18.04 to 20.04 failed/aborted
Ah, kisak-mesa seems to have been the culprit. After sudo ppa-purge ppa:kisak/kisak-mesa the upgrade is now running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916959 Title: Start of LTS upgrade 18.04 to 20.04 failed/aborted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1916959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916959] Re: Start of LTS upgrade 18.04 to 20.04 failed/aborted
How is it possible to identfy the key package(s), that hinder(s) the upgrade? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916959 Title: Start of LTS upgrade 18.04 to 20.04 failed/aborted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1916959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916959] [NEW] Start of LTS upgrade 18.04 to 20.04 failed/aborted
Public bug reported: do-release-upgrade aborted with error: "Es konnte nicht ermittelt werden, welche Systemaktualisierungen verfügbar sind Ein unlösbares Problem trat während der Berechnung der Systemaktualisierung auf. Wenn keine dieser zutrifft, melden Sie bitte den Fehler mithilfe des Befehls 'ubuntu-bug ubuntu-release-upgrader-core' in einem Terminal. Wenn Sie dies selbst untersuchen möchten, finden Sie in den Protokolldateien unter »/var/log/dist-upgrade« Details zur Systemaktualisierung. Schauen Sie sich insbesondere »main.log« und »apt.log« an. " Before that it aborted and told to use ppa-purge, but not which package to purge, so I removed all launchpad/ppa sources from the source list. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Feb 25 22:57:24 2021 InstallationDate: Installed on 2016-04-28 (1764 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-02-25 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916959 Title: Start of LTS upgrade 18.04 to 20.04 failed/aborted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1916959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905425] [NEW] dh_virtualenv is buggy or absent in the latest THREE LTS releases
Public bug reported:
See upstream bug https://github.com/spotify/dh-virtualenv/issues/316 :
Shebang line is sometimes not rewritten because it is #!/bin/sh
We have a package called s11stack-manager which is built for Ubuntu 16.04LTS
Xenial and 18.04LTS Bionic on Launchpad and installs a virtualenv.
In the installed files, the scripts in the bin directory (such as bin/pip)
refer to a non-existing python:
```
#!/bin/sh
'''exec'
/build/s11stack-manager-3u9Lm2/s11stack-manager-0.18.1+syseleven+bionic/debian/s11stack-manager/opt/syseleven/venvs/s11stack-manager/bin/python3
"$0" "$@"
' '''
```
The build process leaves a reference to the build directory
`/build/s11stack-manager-3u9Lm2/s11stack-manager-0.18.1+syseleven+bionic/debian/s11stack-manager/opt/syseleven/venvs/s11stack-manager/bin/python`
instead of correcting it to `/opt/syseleven/venvs/s11stack-manager/bin/python`.
This seems to be a bug in `dh_virtualenv`. It has code to changes the paths,
but it expects those paths to be in the first line of the scripts, following
#!. However, sometimes, `virtualenv` creates a different script beginning, like
so:
```
#!/bin/sh
'''exec'
/home/syseleven/s11stack-manager-0.18.1+syseleven+bionic/debian/s11stack-manager/opt/syseleven/venvs/s11stack-manager/bin/python3
"$0" "$@"
' '''
```
and that pattern is not recognised, so it is not fixed.
(that is from a manual invocation on a Bionic installation)
See code: /usr/lib/python2.7/dist-packages/dh_virtualenv/deployment.py
fix_shebangs(self).
This bug is also visible when I invoke the `dh_virtualenv` command
myself on Ubuntu 16.04 and 18.04. There is apparently no package of
`dh_virtualenv` for Ubuntu 20.04LTS; this matches with what's listed on
https://packages.ubuntu.com/search?keywords=dh-virtualenv .
Our `debian/rules` file is
```
#!/usr/bin/make -f
export DH_VIRTUALENV_INSTALL_ROOT=/opt/syseleven/venvs
export S11STACK_MANAGER_CONFIG=
%:
dh $@ --with python-virtualenv
override_dh_virtualenv:
dh_virtualenv --extra-virtualenv-arg "--never-download" --extra-pip-arg
"--no-index" --extra-pip-arg "--find-links=file://${PWD}/debian/pypi"
--extra-pip-arg "--no-cache-dir" --python /usr/bin/python3 --builtin-venv
--requirements requirements-builddeb.txt
```
This bug is also visible when I invoke the `dh_virtualenv` command
myself on Ubuntu 16.04 and 18.04. There is apparently no package of
`dh_virtualenv` for Ubuntu 20.04LTS; this matches with what's listed on
https://packages.ubuntu.com/search?keywords=dh-virtualenv .
Looking at the upstream git repo the bug may be fixed in the main branch
but the latest THREE Ubuntu LTS releases have old versions of this
package (16.04, 18.04), or are missing the package altogether (20.04).
** Affects: dh-virtualenv (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/1905425
Title:
dh_virtualenv is buggy or absent in the latest THREE LTS releases
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-virtualenv/+bug/1905425/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898361] [NEW] Output format of 'date' command has changed and breaks scripts
Public bug reported: I just updated my remote server to 20.04.1 (from 18.04.x), and now the date command outputs the time like so: $ date Sat 03 Oct 2020 03:00:20 PM CEST with AM/PM, instead of the 24-hour format it used before. This breaks scripts that rely on the output from the date command (and also users who are used to 24 hour format are highly annoyed). My locale is pretty default: $ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=en_US.UTF-8 One would think that changing LC_TIME might influence the output: $ LC_TIME=C date Sat 03 Oct 2020 03:01:56 PM CEST No, it doesn't. Nor do LC_NUMERIC, LC_MESSAGES, etc: $ LC_NUMERIC=C date Sat 03 Oct 2020 03:02:36 PM CEST $ LC_MESSAGES=C date Sat 03 Oct 2020 03:02:41 PM CEST $ LC_CTYPE=C date Sat 03 Oct 2020 03:02:47 PM CEST $ LC_MEASUREMENT=C date Sat 03 Oct 2020 03:03:12 PM CEST Only LC_ALL seems to have an influence: $ LC_ALL=C date Sat Oct 3 15:03:19 CEST 2020 This seems wrong. At least LC_TIME should have an effect here, and it would be even better if basic system utilities didn't just randomly change their output format. Please change it back. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: coreutils 8.30-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 3 14:56:31 2020 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: Upgraded to focal on 2020-10-02 (1 days ago) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 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/1898361 Title: Output format of 'date' command has changed and breaks scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1898361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878996] Re: Blueman uses incorrect hardcoded path to iptables binary
what needs to be done to get the fix into ubuntu 20.04? backport the patch from blueman 2.1.3 to 2.1.2? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878996 Title: Blueman uses incorrect hardcoded path to iptables binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1878996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895433] Re: Missing log files from snapd
"Snaps automatisch auffrischen" is German for "automatically refresh snaps". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895433 Title: Missing log files from snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1895433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895433] Re: Missing log files from snapd
Both show more or less the same # snap changes ID Status SpawnReadySummary 113 Error yesterday at 15:57 CEST yesterday at 15:57 CEST Snaps automatisch auffrischen: "snapd", "chromium" 114 Error today at 09:38 CEST today at 09:38 CEST Snaps automatisch auffrischen: "snapd", "chromium" 115 Error today at 13:13 CEST today at 13:13 CEST Snaps automatisch auffrischen: "snapd", "chromium" and # snap debug state /var/lib/snapd/state.json ID Status SpawnReadyLabel Summary 113 Error yesterday at 15:57 CEST yesterday at 15:57 CEST auto-refresh Snaps automatisch auffrischen: "snapd", "chromium" 114 Error today at 09:38 CEST today at 09:38 CEST auto-refresh Snaps automatisch auffrischen: "snapd", "chromium" 115 Error today at 13:13 CEST today at 13:13 CEST auto-refresh Snaps automatisch auffrischen: "snapd", "chromium" After stopping snap, it hasn't shown the noted behaviour anymore, even though it restarted again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895433 Title: Missing log files from snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1895433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895433] Re: Missing log files from snapd
`journalctl -u snapd` shows the same entries as `journalctl _SYSTEMD_UNIT=snapd.service`. So, still no info, what snap was doing at the time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895433 Title: Missing log files from snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1895433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895433] [NEW] Missing log files from snapd
Public bug reported: snapd is running constantly, using about 10% CPU and accessing the disk without any hint of what it is doing. # ls -l /var/log/snap* /bin/ls: cannot access '/var/log/snap*': No such file or directory # journalctl _SYSTEMD_UNIT=snapd.service doesn't show anything either. The last entry is from yesterday evening. I would expect, that snapd is reporting somehow what it is doing, at least some message when it is starting a major task, preferably showing progress along the way. --- # systemctl stop snapd "solved" the problem for now, without showing any missing functionality. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Description changed: snapd is running constantly, using about 10% CPU and accessing the disk without any hint of what it is doing. # ls -l /var/log/snap* /bin/ls: cannot access '/var/log/snap*': No such file or directory # journalctl _SYSTEMD_UNIT=snapd.service doesn't show anything either. The last entry is from yesterday evening. I would expect, that snapd is reporting somehow what it is doing, at least some message when it is starting a major task, preferably showing progress along the way. + + --- + + # systemctl stop snapd + + "solved" the problem for now, without showing any missing functionality. ** Project changed: gitlptools => snapd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895433 Title: Missing log files from snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1895433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895430] Re: Missing man pages for snapd, snapctl
** Project changed: gitlptools => snapd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895430 Title: Missing man pages for snapd, snapctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1895430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890641] Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
I had also the Prblem with the missing of /lib/firmware/rtl_nic/rtl8125a-3.fw Then i have found the rtl8125a-3.fw on git https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtl_nic then download and copy in the directory /lib/firmware/rtl_nic/ and the command $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic reboot and all is ok -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890641 Title: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1890641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883690] Re: ubuntu-bug - where and how?
apport is not installed, I just installed id. Looks like it is not part of a default server installation. I will try it in the next bug found. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883690 Title: ubuntu-bug - where and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1883690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883688] Re: ntp not starting at boot
I had no idea that ntp is depreceated. ** Changed in: ntp (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883688 Title: ntp not starting at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1883688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883690] [NEW] ubuntu-bug - where and how?
Public bug reported: # cat /etc/os-release NAME="Ubuntu" VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" The manual says, I shall use ubuntu-bug to report a bug, but: # ubuntu-bug -bash: ubuntu-bug: command not found # apt install ubuntu-bug Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package ubuntu-bug ** 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/1883690 Title: ubuntu-bug - where and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1883690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883688] [NEW] ntp not starting at boot
Public bug reported: # cat /etc/os-release NAME="Ubuntu" VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" Package: ntp Status: install ok installed Priority: optional Section: net Installed-Size: 1906 Maintainer: Ubuntu Developers Architecture: amd64 Version: 1:4.2.8p10+dfsg-5ubuntu7.1 I noticed that ntpd is not running when I log in the first time after booting. Starting it manually works just fine. ** Affects: ntp (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/1883688 Title: ntp not starting at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1883688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880855] Re: grub-installer should mount efivarfs
Note: if a fix is used to add some more code similar to the bit I quoted above (using `umount_on_exit`): `umount_on_exit` has to be fixed too, to unmount in reverse order. Also, it seems that when the unmounting eventually happens, IFS is not set back to default, so the field splitting doesn't work. Conceivably there could be a fix in debian/postint to do the mount before even invoking `grub-installer`. But in that case a similar change should be made to `rescue.d/80grub-reinstall`. So it seems better to have it in `grub-install` itself. I am attaching a patch. ** Patch added: "Mount and unmount $ROOT/sys/firmware/efi/efivars" https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1880855/+attachment/5380616/+files/grub-installer.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880855 Title: grub-installer should mount efivarfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1880855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880855] Re: grub-installer should mount efivarfs
** Branch linked: lp:~ubuntu-core-dev/grub-installer/ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880855 Title: grub-installer should mount efivarfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1880855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821251] Re: please add cnf support to debmirror
This may be patched upstream, but it is not present in the version which today installs on Focal 20.04 (reported as 1:2.27ubuntu1). One reason might be that https://code.launchpad.net/~vcs- imports/debmirror/trunk (which is about this package, right?) reports that "Last successful import was on 2014-11-07. " Possibly this is caused by the fact that the upstream repo has moved from git://git.debian.org/collab-maint/debmirror.git (listed on that page) to https://salsa.debian.org/debian/debmirror as shown in comment #6. Another reason why Focal cannot mirror itself successfully is reported in this bug: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1879348 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821251 Title: please add cnf support to debmirror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1821251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880855] [NEW] grub-installer should mount efivarfs
Public bug reported: I am trying to install Focal 20.04 on an UEFI machine, but it fails at the end when installing grub. Here are messages from syslog: May 26 11:51:56 grub-installer: info: Running chroot /target grub-install --force "dummy" May 26 11:51:56 grub-installer: Installing for x86_64-efi platform. May 26 11:51:57 grub-installer: File descriptor 3 (pipe:[37905]) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 4 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 5 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 6 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 8 (/dev/sdb1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 3 (pipe:[37905]) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 4 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 5 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 6 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 8 (/dev/sdb1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: grub-install: warning: Cannot read EFI Boot* variables. May 26 11:51:57 grub-installer: grub-install: warning: read_file: could not read from file: Input/output error. May 26 11:51:57 grub-installer: grub-install: warning: vars_get_variable: read_file(/sys/firmware/efi/vars/Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var) failed: Input/output error. May 26 11:51:57 grub-installer: grub-install: warning: efi_get_variable: ops->get_variable failed: Input/output error. May 26 11:51:57 grub-installer: grub-install: error: failed to register the EFI boot entry: Input/output error. May 26 11:51:57 grub-installer: error: Running 'grub-install --force "dummy"' failed. May 26 11:51:57 debconf: --> SUBST grub-installer/grub-install-failed BOOTDEV dummy May 26 11:51:57 debconf: Adding [BOOTDEV] -> [dummy] May 26 11:51:57 debconf: <-- 0 May 26 11:51:57 debconf: --> INPUT critical grub-installer/grub-install-failed Note the failed access to /sys/firmware/efi/vars/Boot0001-8be4df61-93ca- 11d2-aa0d-00e098032b8c/raw_var Looking at the EFI boot-related variables also fails with efibootmgr: ~ # mount -t sysfs sys /target/sys ~ # chroot /target efibootmgr Skipping unreadable variable "Boot0001": Input/output error BootCurrent: 0005 Timeout: 1 seconds BootOrder: 0005,0006,0007,0008,0004,0001 Boot0004* UEFI: Built-in EFI Shell Boot0005* UEFI: PXE IPv4 Mellanox Network Adapter - 98:03:9B:xx:xx:xx Boot0006* UEFI: PXE IPv4 Mellanox Network Adapter - 98:03:9B:xx:xx:xx Boot0007* UEFI: PXE IPv6 Mellanox Network Adapter - 98:03:9B:xx:xx:xx Boot0008* UEFI: PXE IPv6 Mellanox Network Adapter - 98:03:9B:xx:xx:xx MirroredPercentageAbove4G: 0.00 MirrorMemoryBelow4GB: false Note again the problem with Boot001. Doing the same with a Xenial 18.04 system, there is no such error: [08:30:21] root@cbk130411:~# efibootmgr BootCurrent: 0005 Timeout: 1 seconds BootOrder: 0005,0006,0007,0008,0009 Boot0001 Hard Drive Boot0004* UEFI: Built-in EFI Shell Boot0005* UEFI: PXE IPv4 Mellanox Network Adapter - 98:03:9B:xx:xx:xx Boot0006* UEFI: PXE IPv4 Mellanox Network Adapter - 98:03:9B:xx:xx:xx Boot0007* UEFI: PXE IPv6 Mellanox Network Adapter - 98:03:9B:xx:xx:xx Boot0008* UEFI: PXE IPv6 Mellanox Network Adapter - 98:03:9B:xx:xx:xx Boot0009* ubuntu [08:30:07] root@cbk130411:~# efibootmgr -v BootCurrent: 0005 Timeout: 1 seconds BootOrder: 0005,0006,0007,0008,0009 Boot0001 Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..GO..NO..I.N.T.E.L. .S.S.D.S.C.2.K.G.4.8.0.G.8.LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_DATA-THAT-IS-VERY-LONG...LOTS-OF_
[Bug 1054323] Re: Server Installer fails at 'grub install dummy' in EFI mode
May 26 11:51:56 grub-installer: info: Running chroot /target grub-install --force "dummy" May 26 11:51:56 grub-installer: Installing for x86_64-efi platform. May 26 11:51:57 grub-installer: File descriptor 3 (pipe:[37905]) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 4 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 5 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 6 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 8 (/dev/sdb1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 3 (pipe:[37905]) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 4 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 5 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 6 (/dev/ttyS1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: File descriptor 8 (/dev/sdb1) leaked on vgs invocation. Parent PID 3610: grub-install May 26 11:51:57 grub-installer: grub-install: warning: Cannot read EFI Boot* variables. May 26 11:51:57 grub-installer: grub-install: warning: read_file: could not read from file: Input/output error. May 26 11:51:57 grub-installer: grub-install: warning: vars_get_variable: read_file(/sys/firmware/efi/vars/Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var) failed: Input/output error. May 26 11:51:57 grub-installer: grub-install: warning: efi_get_variable: ops->get_variable failed: Input/output error. May 26 11:51:57 grub-installer: grub-install: error: failed to register the EFI boot entry: Input/output error. May 26 11:51:57 grub-installer: error: Running 'grub-install --force "dummy"' failed. May 26 11:51:57 debconf: --> SUBST grub-installer/grub-install-failed BOOTDEV dummy May 26 11:51:57 debconf: Adding [BOOTDEV] -> [dummy] May 26 11:51:57 debconf: <-- 0 May 26 11:51:57 debconf: --> INPUT critical grub-installer/grub-install-failed On the other hand, maybe the real problem is the Input/output errors on the EFI variables. Is there some way to skip installing the boot loader? We boot from PXE anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054323 Title: Server Installer fails at 'grub install dummy' in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1054323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054323] Re: Server Installer fails at 'grub install dummy' in EFI mode
Can it be that this problem has come back in focal? I get a very similar problem, and the sys file system does not seem to be mounted in /target. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054323 Title: Server Installer fails at 'grub install dummy' in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1054323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782214] Re: apt-mirror failing to download all files needed for install
Yes, it is also missing all files from http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/. Debmirror mirrors this if you give the --di option. An additional difficulty is that the equivalent for http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer- amd64/current/images/for focal is http://archive.ubuntu.com/ubuntu/dists/focal/main/installer- amd64/current/legacy-images/ because for some reason Ubuntu decided for an incompatible change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782214 Title: apt-mirror failing to download all files needed for install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1782214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879348] Re: debmirror fails on focal because of legacy-images
** Patch added: "debmirror patch for focal fossa installer directory" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1879348/+attachment/5373955/+files/debmirror.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879348 Title: debmirror fails on focal because of legacy-images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1879348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879348] Re: debmirror fails on focal because of legacy-images
This should patch it:
--- /usr/bin/debmirror 2017-07-22 01:09:37.0 +
+++ ./debmirror 2020-05-19 07:49:07.409643328 +
@@ -2679,7 +2679,7 @@
if ($use_cache) {
say(": using cache.");
foreach my $file (sort keys %files) {
- next if (@di_dists && $file =~ m:installer-\w(-|\w)*/current/images/:);
+ next if (@di_dists && $file =~
m:installer-\w(-|\w)*/current/[a-z-]*images/:);
if ($files{$file} == 2 && -f $file) {
say("deleting $file") if ($verbose);
if (! $do_dry_run) {
@@ -2696,7 +2696,7 @@
foreach my $file (`find . -type f 2>/dev/null`) {
chomp $file;
$file=~s:^\./::;
- next if (@di_dists && $file =~ m:installer-\w(-|\w)*/current/images/:);
+ next if (@di_dists && $file =~
m:installer-\w(-|\w)*/current/[a-z-]*images/:);
unless ((exists $files{$file} &&
$files{$file} != -1 && $files{$file} != 2) or
(defined($ignore) && $file=~/$ignore/o)) {
@@ -2764,9 +2764,18 @@
my $image_dir = "dists/$dist/main/installer-$arch/current/images";
make_dir ("$tdir/$image_dir");
+ my @old_errlog = @errlog;
+ my $old_num_errors = $num_errors;
if (!remote_get("$image_dir/MD5SUMS", $tdir)) {
-say("Failed to download $image_dir/MD5SUMS; skipping.");
-return;
+say("Failed to download $image_dir/MD5SUMS; trying legacy-images.");
+ $image_dir = "dists/$dist/main/installer-$arch/current/legacy-images";
+ make_dir ("$tdir/$image_dir");
+ if (!remote_get("$image_dir/MD5SUMS", $tdir)) {
+ say("Failed to download $image_dir/MD5SUMS; skipping.");
+ return;
+ }
+ @errlog = @old_errlog;
+ $num_errors = $old_num_errors;
}
if (-f "$tdir/$image_dir/MD5SUMS") {
$bytes_to_get += -s _; # As we did not have the size earlier
@@ -2841,7 +2850,7 @@
sub di_cleanup {
# Clean up obsolete files
foreach my $image_dir (`find dists/ -type d -name images 2>/dev/null`) {
-next unless $image_dir =~ m:/installer-\w(-|\w)*/current/images$:;
+next unless $image_dir =~ m:/installer-\w(-|\w)*/current/[a-z-]*images$:;
chomp $image_dir;
chdir("$image_dir") or die "unable to chdir($image_dir): $!\n";
foreach my $file (`find . -type f 2>/dev/null`) {
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879348
Title:
debmirror fails on focal because of legacy-images
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1879348/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879348] Re: debmirror fails on focal because of legacy-images
** Description changed: If you use debmirror to mirror the focal repository, and use `--di-dist focal --di-arch=arches`, then the mirroring process fails, because it expects to fetch files from http://archive.ubuntu.com/ubuntu/dists/focal/main/installer- amd64/current/images/ but that does not exist. Instead there is http://archive.ubuntu.com/ubuntu/dists/focal/main/installer- amd64/current/legacy-images/. - $ --host archive.ubuntu.com --method http --rsync-extra=none --diff=none --root ubuntu --keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg --arch amd64 --dist focal --section main,restricted,main/debian-installer,restricted/debian-installer,universe/debian-installer,multiverse/debian-installer --di-dist focal --di-arch=arches --progress --verbose --debug /home/syseleven/dm + $ /usr/bin/debmirror --host archive.ubuntu.com --method http --rsync-extra=none --diff=none --root ubuntu --keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg --arch amd64 --dist focal --section main,restricted,main/debian-installer,restricted/debian-installer,universe/debian-installer,multiverse/debian-installer --di-dist focal --di-arch=arches --progress --verbose --debug /home/syseleven/dm ... /usr/bin/debmirror: Created directory: .temp/d-i/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/focal/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/focal/main/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/focal/main/installer-amd64/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/focal/main/installer-amd64/current/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/focal/main/installer-amd64/current/images/ http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/images/MD5SUMS => [ 3%] Getting: dists/focal/main/installer-amd64/current/images/MD5SUMS... #** GET http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/images/MD5SUMS ==> 404 Not Found 404 Not Found failed 404 Not Found Failed to download dists/focal/main/installer-amd64/current/images/MD5SUMS; skipping. Errors: - Download of dists/focal/main/installer-amd64/current/images/MD5SUMS failed: 404 Not Found + Download of dists/focal/main/installer-amd64/current/images/MD5SUMS failed: 404 Not Found Failed to download some Package, Sources or Release files! WARNING: releasing 1 pending lock... - - Also, it is quite annoying that you can't specify `--dist bionic,focal-updates,focal-security,focal-backports`. It will fail because these distributions don't exist yet. However, at some point they wull probably exist, but you won't mirror them. + Also, it is quite annoying that you can't specify `--dist bionic,focal- + updates,focal-security,focal-backports`. It will fail because these + distributions don't exist yet. However, at some point they wull probably + exist, but you won't mirror them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879348 Title: debmirror fails on focal because of legacy-images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1879348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879348] [NEW] debmirror fails on focal because of legacy-images
Public bug reported: If you use debmirror to mirror the focal repository, and use `--di-dist focal --di-arch=arches`, then the mirroring process fails, because it expects to fetch files from http://archive.ubuntu.com/ubuntu/dists/focal/main/installer- amd64/current/images/ but that does not exist. Instead there is http://archive.ubuntu.com/ubuntu/dists/focal/main/installer- amd64/current/legacy-images/. $ --host archive.ubuntu.com --method http --rsync-extra=none --diff=none --root ubuntu --keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg --arch amd64 --dist focal --section main,restricted,main/debian-installer,restricted/debian-installer,universe/debian-installer,multiverse/debian-installer --di-dist focal --di-arch=arches --progress --verbose --debug /home/syseleven/dm ... /usr/bin/debmirror: Created directory: .temp/d-i/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/focal/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/focal/main/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/focal/main/installer-amd64/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/focal/main/installer-amd64/current/ /usr/bin/debmirror: Created directory: .temp/d-i/dists/focal/main/installer-amd64/current/images/ http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/images/MD5SUMS => [ 3%] Getting: dists/focal/main/installer-amd64/current/images/MD5SUMS... #** GET http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/images/MD5SUMS ==> 404 Not Found 404 Not Found failed 404 Not Found Failed to download dists/focal/main/installer-amd64/current/images/MD5SUMS; skipping. Errors: Download of dists/focal/main/installer-amd64/current/images/MD5SUMS failed: 404 Not Found Failed to download some Package, Sources or Release files! WARNING: releasing 1 pending lock... Also, it is quite annoying that you can't specify `--dist bionic,focal-updates,focal-security,focal-backports`. It will fail because these distributions don't exist yet. However, at some point they wull probably exist, but you won't mirror them. ** Affects: debmirror (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/1879348 Title: debmirror fails on focal because of legacy-images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1879348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729754] Re: Python3 version of launchpadlib doesn't properly upload binary attachments to Launchpad
@cjwatson: Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729754 Title: Python3 version of launchpadlib doesn't properly upload binary attachments to Launchpad To manage notifications about this bug go to: https://bugs.launchpad.net/wadllib/+bug/1729754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729754] Re: Python3 version of launchpadlib doesn't properly upload binary attachments to Launchpad
Why isn't there an -1.3.3 version available at https://launchpad.net/wadllib/+download ? It is listed above as " Fix Released" in comment #13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729754 Title: Python3 version of launchpadlib doesn't properly upload binary attachments to Launchpad To manage notifications about this bug go to: https://bugs.launchpad.net/wadllib/+bug/1729754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840463] [NEW] 19.10 Bluetooth mouse is laggy/ slugish
Public bug reported: Have testet Kubuntu, Ubuntu and Xubuntu 19.10 bluetooth is sluggish/ laggy, have also testet the laptop mouseplate, that works good and usb mouse with dongle. ** Affects: compiz-plugins-main (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/1840463 Title: 19.10 Bluetooth mouse is laggy/ slugish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/1840463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822462] [NEW] apt-get reports signature problem when /tmp is full
Public bug reported: 1) Description:Ubuntu Bionic Beaver (development branch) Release:18.04 2) apt: Installed: 1.6.10 Candidate: 1.6.10 Version table: *** 1.6.10 100 100 /var/lib/dpkg/status 3) I would expect a helpful error message, saying there's not enough disk space, or maybe even pointing at the /tmp partition. 4) My /tmp partition was full, when I tried `apt-get update`. It failed with the following errors: Get:1 http://de.archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Err:1 http://de.archive.ubuntu.com/ubuntu bionic InRelease Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic_InRelease into data and signature failed Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB] Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease Splitting up /var/lib/apt/lists/partial/security.ubuntu.com_ubuntu_dists_bionic-security_InRelease into data and signature failed Get:3 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease [88,7 kB] Err:3 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic-updates_InRelease into data and signature failed Get:4 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB] Err:4 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic-backports_InRelease into data and signature failed Reading package lists... Done W: GPG error: http://de.archive.ubuntu.com/ubuntu bionic InRelease: Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic_InRelease into data and signature failed E: The repository 'http://de.archive.ubuntu.com/ubuntu bionic InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://security.ubuntu.com/ubuntu bionic-security InRelease: Splitting up /var/lib/apt/lists/partial/security.ubuntu.com_ubuntu_dists_bionic-security_InRelease into data and signature failed E: The repository 'http://security.ubuntu.com/ubuntu bionic-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease: Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic-updates_InRelease into data and signature failed E: The repository 'http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease: Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic-backports_InRelease into data and signature failed E: The repository 'http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. The hint at unsigned repositories is misleading and it took quite some time to figure out the real problem. Therefore, I would expect an error message pointing at the real culprit, which in this case was missing disk space. --- After removing files from /tmp, apt-get update succeeds as expected: Get:1 http://de.archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:2 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease [88,7 kB] Get:3 http://security.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB] Get:4 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB] Get:5 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1.019 kB] Get:6 http://de.archive.ubuntu.com/ubuntu bionic/main Translation-en [516 kB] Get:7 http://de.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [9.184 B] Get:8 http://de.archive.ubuntu.com/ubuntu bionic/restricted Translation-en [3.584 B] Get:9 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8.570 kB] Get:10 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [284 kB] Get:11 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en [104 kB] Get:12 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [4.296 B] Get:13 http://security.ubuntu.com/ubuntu bionic-security/restricted Translation-en [2.192 B] Get:14 http://de.archive.ubuntu.com/ubuntu bionic/universe Tra
Re: [Bug 1800785] Re: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess new libgs9-common package pre-installation script gab den Fehler-Ausgangsstatus 1 zurüc
Thank you very much for your help. Yes, I tried to fix the problem with my printer and it works, but only one day. I am very pleased, that I can update again and my printers works too. On 31.10.18 12:15, Marc Deslauriers wrote: > Here's the error log: > > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/ps_gray.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/ps_cmyk.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/gray_to_k.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/default_gray.icc' not owned by > package 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/lab.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/srgb.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/default_cmyk.icc' not owned by > package 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/ps_rgb.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/sgray.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/default_rgb.icc' not owned by > package 'libgs9-common:all' > > Did you manually copy files into the > /usr/share/ghostscript/9.25/iccprofiles directory to try and fix an > upgrade issue? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800785 Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess new libgs9-common package pre- installation script gab den Fehler-Ausgangsstatus 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1800785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800785] [NEW] package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess new libgs9-common package pre-installation script gab den Fehler-Ausgangsstatus 1 zurück
Public bug reported: ? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: ghostscript-x:amd64: Install ghostscript:amd64: Install libgs9:amd64: Install libgs9-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 31 09:19:21 2018 ErrorMessage: Unterprozess new libgs9-common package pre-installation script gab den Fehler-Ausgangsstatus 1 zurück InstallationDate: Installed on 2018-01-29 (274 days ago) InstallationMedia: budgie-remix 16.04.3 "Budgie-remix" - Release amd64 (20170804) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, 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.1 apt 1.6.6 SourcePackage: ghostscript Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess new libgs9-common package pre-installation script gab den Fehler-Ausgangsstatus 1 zurück UpgradeStatus: Upgraded to bionic on 2018-10-25 (5 days ago) ** Affects: ghostscript (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/1800785 Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess new libgs9-common package pre- installation script gab den Fehler-Ausgangsstatus 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1800785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791893] Re: Trailing garbage data when sending on an AF_PACKET socket
No Problem in 4.15.0-32 and before. Problem since 4.15.0-33-generic with raw socket => EtherCAT/SOEM (Simple Open Ethercat Master). I can confirm it's fixed in 4.15.0-38-generic (SOEM ok). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791893 Title: Trailing garbage data when sending on an AF_PACKET socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Hello, have a Telcast F7 should be also the Touchpad SYNA3602, but not working with Kernel 4.15035. Does anyone know when the patch comes in the current Ubuntu kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776155] Re: Touchpad detected as SYNA3602, does not work at all.
Does anyone know when the patch in the official Ubuntu 18.04 kernel comes? Thanks Olaf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776155 Title: Touchpad detected as SYNA3602, does not work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382984] Re: Jekyll missing dependency ruby-mercenary
I built a Docker container based on Ubuntu Bionic, and just installed package jekyll. Running jekyll with either `jekyll serve` or `jekyll build` works properly for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382984 Title: Jekyll missing dependency ruby-mercenary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jekyll/+bug/1382984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382984] Re: Jekyll missing dependency ruby-mercenary
How do I close this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382984 Title: Jekyll missing dependency ruby-mercenary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jekyll/+bug/1382984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
@jsalisbury: I had the machine tested with this kernel: Linux xa-xubu 4.18.0-041800rc1-generic #201806162031 SMP Sun Jun 17 00:34:22 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux that I found via your link [0]. The result is that in this kernel, the problem is gone. So that sounds like good news! I think there was another commenter asking me to try a (probably different) upstream kernel, but it seems gone now. To them I can report that I didn't try building a kernel myself, but hopefully their proposal was close enough to using the Ubuntu mainline kernel that this test gives them the answer they are looking for. ** Tags added: kernel-fixed-upstream ** 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/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
Yes, the problem started after an upgrade. From what I can see in the logs it seems that first the machine was upgraded from Ubuntu 17.10 to 18.04, apparently without problem. Then a few days later, the working kernel Ubuntu 4.13.0-43.48-generic 4.13.16 was replaced by 4.15.0-23.25-generic 4.15.18 which fails. It will not be so easy to test another kernel, but I'll try. It will definitely be some days before I can report a result, I suspect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
Oops, the above message was not supposed to be mailed here... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777245] Re: stom
On Sat 16 Jun 2018 at 14:31:49 +0200, Guus en Anneke wrote: > Hoi Olaf, > eerst startte ik op met > Ubuntu met Linux 4.15.0-23 generic(recovery mode) > Ik kreeg een lange lijst met data. Toen herstelmenu, waarna rare dingen, > gekleurde strepen van letters. > > Opnieuw opgestart met > Ubuntu met Linux 4.13.0-43 generic > Gister ook met deze opgestart. Was nummer 3 in het lijstje en leek op nr 1. > vandaar dat ik vandaag met nr 2 op ging starten om te zien wat die deed.Niet > goed dus. > Ik heb een bug ingediend bij Ubuntu; je kan 'm nalezen op https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245 Daarin staat ook dat je 7 dagen geleden een nieuwe XUbuntu-versie hebt geinstalleerd (van 17.10 naar 18.04)... daar had ik beter even bij kunnen meekijken! Ik heb dat namelijk op mijn laptop ook gedaan en dat was niet geheel zonder problemen... Ik heb ook de 4.13.0-43 standaard gemaakt voor het opstarten (hopelijk). Wanneer er een nieuwe versie uitkomt, moet je die eens proberen. Ik merk het hier vanzelf want mijn laptop heeft dus dezelfde Ubuntu-versie. Ik zal laten weten wanneer het zover is. Voor de 4.15.0-23-versie heb ik een opstart-optie toegevoegd die ik ergens tegenkwam. Iemand met soortgelijke problemen had er baat bij; als je tijd over hebt moet je maar eens die versie proberen (ik denk niet dat je verschil ziet in het menu) en zien of het helpt. Ik hoor graag wat het effekt is (sukses of niet), dan kan ik dat bij de bugmelding toevoegen. Groetjes, -Olaf. -- ___ Olaf 'Rhialto' Seibert -- Wayland: Those who don't understand X \X/ rhialto/at/falu.nl -- are condemned to reinvent it. Poorly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
** Attachment added: "extract from kernel log for 4.15.0.23-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245/+attachment/5153352/+files/dmesg-4.15.0-23-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
** Summary changed: - X freezes + X freezes with kernel 4.15.0-23-generic (AMDGPU) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777245] Re: X freezes
** Description changed: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. + + I filed this bug using apport-cli, running the older (working) kernel, + not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rhialto 21222 F pulseaudio /dev/snd/controlC0: rhialto 21222 F pulseaudio Date: Sat Jun 16 16:03:46 2018 InstallationDate: Installed on 2017-10-29 (230 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Releas
[Bug 1777245] [NEW] X freezes
Public bug reported: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rhialto 21222 F pulseaudio /dev/snd/controlC0: rhialto 21222 F pulseaudio Date: Sat Jun 16 16:03:46 2018 InstallationDate: Installed on 2017-10-29 (230 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: enp1s0no wireless extensions. lono wireless extensions. MachineType: LENOVO 90G9001RNY ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed root=UUID=103b7
[Bug 1495276] Re: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion `*_head == _item' failed.
Yes, I have this at every boot with Xubuntu 17.10 too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495276 Title: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion `*_head == _item' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1495276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL
2017-12-06 9:15 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>: > What can I do next to further investigate this in order to provide > feedback over here in an efficient way ? Thinking aloud: 1. Share table structure 2. Copy table to another name, add optimize table for the copy and see if it still crashes. 3. If yes, try to isolate the crashes to specific columns by dropping them one at a time. 4. If no, try to replicate the load on the second table to see if you can cause the crashes. -- Olaf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729536 Title: InnoDB: Failing assertion: sym_node->table != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1729536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL
2017-12-01 10:32 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>: > I reactivated one set of optimize queries for this night and it crashed > with the exact same backtrace. So I can confirm this is indeed related > to this specific set. However, there is nothing fancy about them at all. Nice! It might also be good to know if just the truncates works fine or crashes as well. > It is a simple SQL script with 9 OPTIMIZE statements being run from the mysql > client (CLI) on a single database. > OPTIMIZE TABLE Table1; > OPTIMIZE TABLE Table2; > OPTIMIZE TABLE Table3; An idea here would be to first test the first half of the queries, next day try the second half, to further isolate the culprit. Gr, -- Olaf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729536 Title: InnoDB: Failing assertion: sym_node->table != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1729536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL
2017-11-30 9:12 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>: > @Olaf: it wasn't available anymore unfortunately. > > After deactivating the OPTIMIZE statements and changing the TRUNCATE > statement to DELETE FROM in our pre-production scripts, I can happily > confirm there was no outage on our server during this night. > > If this can help investigating this bug in any way? My guess: 1. Test with just the optimize enabled. 2. Test with just the truncate enabled. 3. If the crashes return, try to narrow it down to specific queries / tables. -- Olaf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729536 Title: InnoDB: Failing assertion: sym_node->table != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1729536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL
2017-11-29 10:46 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>: > @ChristianEhrhardt > Thanks for your replies and initiatives. Much appreciated. > I did indeed notice the install package we could rollback to using apt-get > install mysql-server=XXX was 5.7.11, but this version is more than a year and > a half old, which doesn't sound like such a good idea. 5.7.19 might still be available in your local apt cache: /var/cache/apt/archives -- Olaf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729536 Title: InnoDB: Failing assertion: sym_node->table != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1729536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL
Hi, > I thought it was related specifically to replication, but according to your message, it seems it can happen for some other reason as well ? Yes, we're not using replication at all. I think the assert is a low-level one. Something before, probably unrelated to this stacktrace, goes wrong and this is only noticed later. > What I do know though is that it has to be somehow reproducible because the timeframe within which it happens is the same every day. That's interesting. What makes this timeframe different from other timeframes? Are you altering tables? Gr, Olaf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729536 Title: InnoDB: Failing assertion: sym_node->table != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1729536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL
2017-11-03 10:55 GMT+01:00 ChristianEhrhardt <1729...@bugs.launchpad.net>: > Hi Olaf, > there seem to be some related known issues in percona/mysql, see bug 1399471 > for more details and follow referenced further bugs from there. > > I'll explicitly subscribe Lars to take a look, but as printed in the > error message it would be great if you could file (and mention the > number here) a bug at [1] the upstream bug tracker for mysql. They might > have a backportable fix known already. Since upstream requires Oracle accounts I don't file bugs there anymore.. Note that we're running 5.7.20, I'm not sure why any backporting would be required. > You'd have to check if [2] or [3] are your case already. [2] doesn't seem applicable as our crash doesn't happen consistently at startup. Not sure about [3] > In general many of the issues seem related to e.g. migrating from > percona - does your setup have any percona history that could be > related? I didn't setup the server but I don't think so. I think it was first installed with Ubuntu 16.04.. didn't that include MySQL 5.7 already? If so, I don't think there were any upgrades. -- Olaf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729536 Title: InnoDB: Failing assertion: sym_node->table != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1729536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729536] [NEW] InnoDB: Failing assertion: sym_node->table != NULL
Public bug reported: V: 5.7.20-0ubuntu0.16.04.1 I think it was when I added a field to a table (via phpMyAdmin). 2017-11-02 09:36:47 0x7fdc38ff9700 InnoDB: Assertion failure in thread 140583825807104 in file pars0pars.cc line 822 InnoDB: Failing assertion: sym_node->table != NULL InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 08:36:47 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=40 max_threads=151 thread_count=8 connection_count=8 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76385 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x3 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe8a93b] /usr/sbin/mysqld(handle_fatal_signal+0x489)[0x786749] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fdc5b70f390] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7fdc5aac8428] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fdc5aaca02a] /usr/sbin/mysqld[0x75c31a] /usr/sbin/mysqld(_Z21pars_insert_statementP10sym_node_tPvP10sel_node_t+0x3a8)[0x1024088] /usr/sbin/mysqld(_Z7yyparsev+0x1227)[0x12455d7] /usr/sbin/mysqld(_Z8pars_sqlP11pars_info_tPKc+0x9e)[0x10258de] /usr/sbin/mysqld(_Z13fts_parse_sqlP11fts_table_tP11pars_info_tPKc+0x190)[0x12251e0] /usr/sbin/mysqld(_Z14fts_write_nodeP5trx_tPP10que_fork_tP11fts_table_tP12fts_string_tP10fts_node_t+0x292)[0x11ffa52] /usr/sbin/mysqld[0x12031d8] /usr/sbin/mysqld(_Z14fts_sync_tableP12dict_table_tbbb+0x329)[0x1209219] /usr/sbin/mysqld(_Z23fts_optimize_sync_tablem+0x42)[0x1210b62] /usr/sbin/mysqld(_Z19fts_optimize_threadPv+0x57c)[0x121a0bc] /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fdc5b7056ba] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fdc5ab9a3dd] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 2017-11-02T08:36:47.822416Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000) ** Affects: mysql-5.7 (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/1729536 Title: InnoDB: Failing assertion: sym_node->table != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1729536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711041] [NEW] package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
Public bug reported: info ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libasound2-plugins:i386 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 16 06:58:58 2017 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2017-05-25 (82 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: alsa-plugins Title: package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711041 Title: package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1711041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703229] Re: package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
sadd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703229 Title: package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1703229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
I can also confirm this bug with Ubuntu 16.04 and kernel 4.10.0-27-generic on a Dell XPS 13 from 2015. I had a system freeze yesterday and today. In the months before I never experienced any problems despite heavy swapping. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704608] [NEW] package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half
Public bug reported: no info ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsamplerate0:i386 0.1.8-8 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 Date: Fri Jul 14 15:12:16 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu9 ErrorMessage: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) InstallationDate: Installed on 2017-05-25 (51 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libsamplerate Title: package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libsamplerate (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704608 Title: package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsamplerate/+bug/1704608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703229] [NEW] package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
Public bug reported: mhgkhg ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libasound2-plugins:i386 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun Jul 9 15:33:02 2017 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2017-05-25 (44 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: alsa-plugins Title: package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703229 Title: package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1703229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666851] Re: mini-httpd unknown SSL Config Option
This also affects me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666851 Title: mini-httpd unknown SSL Config Option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mini-httpd/+bug/1666851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694587] [NEW] package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half
Public bug reported: i try to install Gimp via Terminal. Doesnt work ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsamplerate0:i386 0.1.8-8 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed May 31 06:12:20 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu7 ErrorMessage: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) InstallationDate: Installed on 2017-05-25 (5 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libsamplerate Title: package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libsamplerate (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694587 Title: package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsamplerate/+bug/1694587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689660] [NEW] systemd-fsckd busy spawning fsck
Public bug reported: I rebooted my laptop after a crash. Fsck couldn't repair the /var partition, so I was greeted with "Welcome to Emergency!" and the request to look at `journalctl -xb`. After logging in, and journalctl telling me about the broken /var partition, I tried fsck /dev/mapper/vg0-var which immediately returned with a message stating that /dev/mapper/vg0-var is busy. Looking at the processes with `ps aux | grep fsck` gave - systemd-fsckd - /sbin/fsck /dev/mapper/vg0-var - fsck.ext2 /dev/mapper/vg0-var Trying to kill `fsck.ext2` or `fsck` was futile, because `fsck` was dying and restarting faster, than I could look at the process list. Killing `systemd-fsckd` finally ended the busy loop. But still, I couldn't check my /var partition, because now systemd has mounted my /var partition, even though it told me before, it was in need of repair. After unmounting /var, I could finally do the much needed `fsck /dev/mapper/vg0-var`. --- I would expect 1. systemd-fsck stop restarting fsck, when it was aware, that it must be checked manually 2. systemd *not* mount an unchecked file system, especially when systemd-fsckd stopped with an error or was killed --- Description:Ubuntu 16.04 LTS Release:16.04 --- systemd: Installed: 229-4ubuntu10 Candidate: 229-4ubuntu16 Version table: 229-4ubuntu16 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages --- ** Affects: systemd (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/1689660 Title: systemd-fsckd busy spawning fsck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1689660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547870] Re: libsane-dev lacks sanei.h header required by some scanner drivers
Please note that all `sanei*` files are for internal use by the sane- backends package only. These files are *not* intended to be shared in any way outside of the scope of sane-backends. If third party backends want to reuse some of these files that is their decision and that's fine buty they should include (and maintain) their own copies. The SANE project does not and will not guarantee any kind of API/ABI compatibility for what's in the `sanei*` files. None of the `sanei*.h` header files belong in a `libsane-dev` package and I suggest to close this bug report as a "Won't fix". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547870 Title: libsane-dev lacks sanei.h header required by some scanner drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1547870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687269] [NEW] package mythtv-status 0.10.8-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Public bug reported: I don't know. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: mythtv-status 0.10.8-1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sun Apr 30 11:30:32 2017 ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-04-18 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: mythtv-status Title: package mythtv-status 0.10.8-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mythtv-status (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687269 Title: package mythtv-status 0.10.8-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/1687269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316873] Re: Left mouse button stops working
The latest Nvidia proprietary driver update in Ubuntu 16.04 (automated updates) caused my left mouse button to fail after a while. I tried several mice and USB ports, all the same. Login out and in a gain is a remedy. Restart not necessary. It feels as this is a lightdm bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1316873 Title: Left mouse button stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Attached is the acpi-dump from my Asus G752VM running Ubuntu 16.04. Same Touchpad (ELAN 0x3043, Version 0x100) as the above G752VS. ** Attachment added: "acpi-dump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456/+attachment/4840455/+files/acpi-dump -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738617] Re: package should not depend on wpasupplicant
This bug is still valid in Xenial 16.04. My system is connected via LAN and doesn't have a wireless card installed. Because of the dependency, wpa_cli is run on each suspend/resume cycle and fails of course. There is no technical reason for this dependency, and a recommendation is strong enough to satisfy the perceived need, while still allowing to get rid of wpasupplicant. I consider shifting the decision to Debian maintainers a dummy argument. It would not be the first time, where changes flow from Ubuntu to Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/738617 Title: package should not depend on wpasupplicant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/738617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
My dmesg | grep -i elan and xinput list looks exactly like OP above - except that I have a different USB mouse attached: Microsoft Microsoft 3-Button Mouse with IntelliEye™ id=9[slave pointer (2)] That mouse worked right away - installing Ubuntu 16.04.1 and then the Nvidia proprietary drivers was no problem. Almost everything works fine - except Touchpad and the Fn keys. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Same with Asus G752VM running Ubuntu 16.04. ** 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/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292830] Re: Resuming from sleep makes black borders around windows appear
Ubuntu 16.04 on Asus G75 with Nvidia 660M. It doesn't happen every time waking from sleep - I'd say there is a roughly 20-30% chance this happens in my case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292830 Title: Resuming from sleep makes black borders around windows appear To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1292830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661145] [NEW] Feature request for juju status
Public bug reported: Hi Everyone, this is a feature request for juju status : If I could set a FLAG so that I only see the APP's or the Units or just the machines but still exactly same layout just reduced down to for example unit it would help me a lot. Since I do have deployed a bunch it would be nice to have a sort of scoll function and auto refresh with it as well. A work around I have is : watch -n 0.1 -c juju status --color But it is not perfect and won't allow me to scroll up and down. Also a FLAG for STATUS would be extremly helpful as well : active, error and so on. sysadmin@sf2-maas00:~$ juju show-status ModelControllerCloud/Region Version default maas-prod-controller maas-prod 2.0.2 AppVersion Status Scale Charm Store Rev OS Notes ceph-mon 10.2.3 active 3 ceph-mon jujucharms6 ubuntu ceph-osd 10.2.3 error5 ceph-osd jujucharms 238 ubuntu ceph-radosgw 10.2.3 active 3 ceph-radosgw jujucharms 245 ubuntu cinder 9.0.0active 3 cinder jujucharms 257 ubuntu cinder-ceph9.0.0active 3 cinder-ceph jujucharms 221 ubuntu dashboard-hacluster active 3 hacluster jujucharms 31 ubuntu glance 13.0.0 active 3 glance jujucharms 253 ubuntu hacluster active 24 hacluster jujucharms 31 ubuntu keystone 10.0.0 active 3 keystone jujucharms 258 ubuntu neutron-api9.0.0active 3 neutron-api jujucharms 246 ubuntu neutron-gateway9.0.0active 1 neutron-gateway jujucharms 232 ubuntu neutron-openvswitch9.0.0active 5 neutron-openvswitch jujucharms 238 ubuntu nova-cloud-controller 14.0.1 active 3 nova-cloud-controller jujucharms 292 ubuntu nova-compute 14.0.1 active 5 nova-compute jujucharms 259 ubuntu ntp unknown 6 ntp jujucharms0 ubuntu openstack-dashboard10.0.0 active 3 openstack-dashboard jujucharms 243 ubuntu percona-cluster5.6.21-25.8 active 3 percona-cluster jujucharms 246 ubuntu rabbitmq-server3.5.7active 3 rabbitmq-server jujucharms 54 ubuntu Unit Workload Agent Machine Public address Ports Message ceph-mon/0* activeidle 0/lxd/0 10.5.100.13 Unit is ready and clustered ceph-mon/1activeidle 1/lxd/0 10.5.100.88 Unit is ready and clustered ceph-mon/2activeidle 2/lxd/0 10.5.100.139 Unit is ready and clustered ceph-osd/0* activeidle 0 10.5.100.152 Unit is ready (1 OSD) ceph-osd/1error idle 1 10.5.100.153 hook failed: "config-changed" ceph-osd/2activeidle 2 10.5.100.154 Unit is ready (1 OSD) ceph-osd/4activeidle 3 10.5.100.14 Unit is ready (1 OSD) ceph-osd/5activeidle 6 10.5.100.151 Unit is ready (1 OSD) ceph-radosgw/0* activeidle 0/lxd/1 10.5.100.12880/tcp Unit is ready hacluster/0*activeidle 10.5.100.128 Unit is ready and clustered ceph-radosgw/1activeidle 1/lxd/1 10.5.100.13180/tcp Unit is ready hacluster/2 activeidle 10.5.100.131 Unit is ready and clustered ceph-radosgw/2activeidle 2/lxd/1 10.5.100.15780/tcp Unit is ready hacluster/15activeidle 10.5.100.157 Unit is ready and clustered cinder/0* activeidle 0/lxd/2 10.5.100.1338776/tcp Unit is ready cinder-ceph/0* activeidle 10.5.100.133 Unit is ready hacluster/1 activeidle 10.5.100.133 Unit is ready and clustered cinder/1 activeidle 1/lxd/2 10.5.100.1498776/tcp Unit is ready cinder-ceph/1 activeidle 10.5.100.149 Unit is ready hacluster/6 activeidle 10.5.100.149 Unit is ready and clustered cinder/2 activeidle 2/lxd/2 10.5.100.1958776/tcp Unit is rea
[Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
It started with the 16.04 upgrade. I noticed that the mouse cursor works a few seconds after login but after my Psensor (temperature display) started up, the mouse cursor jumps. Wonder what library Psensor is using. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649397] Re: maas-dhcpd.service won't start
sysadmin@sf2-maas00:~$ maas sysadmin vlan update fabric-0 untagged
dhcp_on=True primary_rack=sf2-maas00
Success.
Machine-readable output follows:
{
"mtu": 1500,
"resource_uri": "/MAAS/api/2.0/vlans/0/",
"fabric": "fabric-0",
"name": "untagged",
"secondary_rack": null,
"id": 0,
"external_dhcp": null,
"vid": 0,
"dhcp_on": true,
"primary_rack": "s4x6ge"
}
I had to run on the CLI this command above which now finally fixed the
DHCPD to start proper and no longer shows BLANK on the DHCPD... still
don't make sense.
I also chatted with brendand about this issue.
now when I even do check a service status it shows it :
sysadmin@sf2-maas00:~$ service maas-dhcpd status
● maas-dhcpd.service - MAAS instance of ISC DHCP server for IPv4
Loaded: loaded (/lib/systemd/system/maas-dhcpd.service; enabled; vendor
preset: enabled)
Active: active (running) since Tue 2016-12-13 14:53:20 UTC; 32s ago
Docs: man:dhcpd(8)
Process: 3856 ExecStartPre=/bin/mkdir -p /var/lib/maas/dhcp (code=exited,
status=0/SUCCESS)
Process: 3853 ExecStartPre=/bin/mkdir -p /run/maas/dhcp (code=exited,
status=0/SUCCESS)
Main PID: 3859 (dhcpd)
Tasks: 1
Memory: 9.8M
CPU: 72ms
CGroup: /system.slice/maas-dhcpd.service
└─3859 dhcpd -user dhcpd -group dhcpd -f -q -4 -pf
/run/maas/dhcp/dhcpd.pid -cf /var/lib/maas/dhcpd.conf -lf
/var/lib/maas/dhcp/dhcpd.leases em1
Dec 13 14:53:25 sf2-maas00 dhcpd[3859]: DHCPDISCOVER from 78:2b:cb:56:45:a2 via
10.5.100.1
Dec 13 14:53:25 sf2-maas00 dhcpd[3859]: DHCPOFFER on 10.5.100.250 to
78:2b:cb:56:45:a2 via 10.5.100.1
Dec 13 14:53:27 sf2-maas00 dhcpd[3859]: DHCPDISCOVER from 78:2b:cb:56:45:a2 via
em1
Dec 13 14:53:27 sf2-maas00 dhcpd[3859]: DHCPOFFER on 10.5.100.250 to
78:2b:cb:56:45:a2 via em1
Dec 13 14:53:27 sf2-maas00 dhcpd[3859]: DHCPDISCOVER from 78:2b:cb:56:45:a2 via
10.5.100.1
Dec 13 14:53:27 sf2-maas00 dhcpd[3859]: DHCPOFFER on 10.5.100.250 to
78:2b:cb:56:45:a2 via 10.5.100.1
Dec 13 14:53:31 sf2-maas00 dhcpd[3859]: DHCPDISCOVER from 78:2b:cb:56:45:a2 via
em1
Dec 13 14:53:31 sf2-maas00 dhcpd[3859]: DHCPOFFER on 10.5.100.250 to
78:2b:cb:56:45:a2 via em1
Dec 13 14:53:31 sf2-maas00 dhcpd[3859]: DHCPDISCOVER from 78:2b:cb:56:45:a2 via
10.5.100.1
Dec 13 14:53:31 sf2-maas00 dhcpd[3859]: DHCPOFFER on 10.5.100.250 to
78:2b:cb:56:45:a2 via 10.5.100.1
still leaves the issue why doesn't the GUI does it automatically ? h
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649397
Title:
maas-dhcpd.service won't start
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1649397/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649397] Re: maas-dhcpd.service won't start
Andres this is a bug so stop closing things without my ok. The MAAS is fully configured and operational. Since the latest patches it no longer works because some jack ass broke the code. I don't like it when people deploy code which is not signed off. So Andres leave this bug open because it certainly is a bug. Olaf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649397 Title: maas-dhcpd.service won't start To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1649397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649397] Re: maas-dhcpd.service won't start
root@sf2-maas00:~# service maas-dhcpd status ● maas-dhcpd.service - MAAS instance of ISC DHCP server for IPv4 Loaded: loaded (/lib/systemd/system/maas-dhcpd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-12-12 21:32:20 UTC; 2min 38s ago Condition: start condition failed at Mon 2016-12-12 21:34:57 UTC; 1s ago ConditionPathExists=/var/lib/maas/dhcpd.conf was not met Docs: man:dhcpd(8) Process: 2933 ExecStart=/bin/sh -ec INTERFACES=$(cat /var/lib/maas/dhcpd-interfaces); LEASES_FILE=/var/lib/maas/dhcp/dhcpd.leases; [ -e $LEASES_FILE ] || touch $LEASES_FILE; / Process: 2922 ExecStartPre=/bin/mkdir -p /var/lib/maas/dhcp (code=exited, status=0/SUCCESS) Process: 2893 ExecStartPre=/bin/mkdir -p /run/maas/dhcp (code=exited, status=0/SUCCESS) Main PID: 2933 (code=exited, status=1/FAILURE) Dec 12 21:32:19 sf2-maas00 systemd[1]: Starting MAAS instance of ISC DHCP server for IPv4... Dec 12 21:32:19 sf2-maas00 systemd[1]: Started MAAS instance of ISC DHCP server for IPv4. Dec 12 21:32:20 sf2-maas00 systemd[1]: maas-dhcpd.service: Main process exited, code=exited, status=1/FAILURE Dec 12 21:32:20 sf2-maas00 systemd[1]: maas-dhcpd.service: Unit entered failed state. Dec 12 21:32:20 sf2-maas00 systemd[1]: maas-dhcpd.service: Failed with result 'exit-code'. Ok even if you recreate the file with chmod maas:maas when ever you do a reboot of the box it is removed automatically even it should not be removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649397 Title: maas-dhcpd.service won't start To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1649397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
