[Bug 1908223] Re: nmap 7.80 crashes with Assertion `htn.toclock_running == true'
Dear Ubuntu maintainers, do you have any plans of fixing this bug in Ubuntu 20.04 before Ubuntu 22.04 LTS release? In upstream nmap it is said to be fixed since version 7.90 . Do you consider importing version 7.92 into Ubuntu Focal ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908223 Title: nmap 7.80 crashes with Assertion `htn.toclock_running == true' To manage notifications about this bug go to: https://bugs.launchpad.net/nmap/+bug/1908223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939950] [NEW] shim-signed fails to upgrade when NVMe drive is moved into the VM as Virtio drive
Public bug reported: I had to remove a NVMe storage (nvme0n1) from my laptop and temporarily brought it back as a VirtIO (vda) device under a VM. When I received shim-signed upgrade to version 1.51+15.4-0ubuntu9 , I got this : Setting up shim-signed (1.51+15.4-0ubuntu9) ... mount: /var/lib/grub/esp: special device /dev/disk/by-id/nvme-eui.001b448b4993ceb4-part1 does not exist. dpkg: error processing package shim-signed (--configure): installed shim-signed package post-installation script subprocess returned error exit status 32 Errors were encountered while processing: shim-signed E: Sub-process /usr/bin/dpkg returned an error code (1) Looking into /var/lib/dpkg/info/shim-signed.postinst , I see that it calls /usr/lib/grub/grub-multi-install which in turn gets this device name from debconf DB, which it then fails to find among VM devices. Looking into /var/cache/debconf/config.dat , I see it recorded under Name: grub-efi/install_devices , also its nvme0n1p1 partition recorded under Name: grub-efi/partition_description . I am not sure whether it is safe to remove or modify these values by text editor, but running grub-install or dpkg-reconfigure grub-efi-amd64 as root does not change them . Please help me to resolve this situation. ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Description changed: I had to remove a NVMe storage (nvme0n1) from my laptop and temporarily brought it back as a VirtIO (vda) device under a VM. When I received shim-signed upgrade to version 1.51+15.4-0ubuntu9 , I got this : Setting up shim-signed (1.51+15.4-0ubuntu9) ... mount: /var/lib/grub/esp: special device /dev/disk/by-id/nvme-eui.001b448b4993ceb4-part1 does not exist. dpkg: error processing package shim-signed (--configure): - installed shim-signed package post-installation script subprocess returned error exit status 32 + installed shim-signed package post-installation script subprocess returned error exit status 32 Errors were encountered while processing: - shim-signed + shim-signed E: Sub-process /usr/bin/dpkg returned an error code (1) Looking into /var/lib/dpkg/info/shim-signed.postinst , I see that it - calls /usr/lib/grub/grub-multi-install which in turn queries some values - from debconf DB, which it then fails to find among VM devices. + calls /usr/lib/grub/grub-multi-install which in turn received this + device name from debconf DB, which it then fails to find among VM + devices. - Looking into /var/cache/debconf/config.dat , I see it recorded under Name: grub-efi/install_devices , also its nvme0n1p1 partition recorded under Name: grub-efi/partition_description . + Looking into /var/cache/debconf/config.dat , I see it recorded under Name: grub-efi/install_devices , also its nvme0n1p1 partition recorded under Name: grub-efi/partition_description . I am not sure whether it is safe to remove or modify these values by text editor, but running grub-install or dpkg-reconfigure grub-efi-amd64 as root does not change them . Please help me to resolve this situation. ** Description changed: I had to remove a NVMe storage (nvme0n1) from my laptop and temporarily brought it back as a VirtIO (vda) device under a VM. When I received shim-signed upgrade to version 1.51+15.4-0ubuntu9 , I got this : Setting up shim-signed (1.51+15.4-0ubuntu9) ... mount: /var/lib/grub/esp: special device /dev/disk/by-id/nvme-eui.001b448b4993ceb4-part1 does not exist. dpkg: error processing package shim-signed (--configure): installed shim-signed package post-installation script subprocess returned error exit status 32 Errors were encountered while processing: shim-signed E: Sub-process /usr/bin/dpkg returned an error code (1) Looking into /var/lib/dpkg/info/shim-signed.postinst , I see that it - calls /usr/lib/grub/grub-multi-install which in turn received this - device name from debconf DB, which it then fails to find among VM - devices. + calls /usr/lib/grub/grub-multi-install which in turn gets this device + name from debconf DB, which it then fails to find among VM devices. Looking into /var/cache/debconf/config.dat , I see it recorded under Name: grub-efi/install_devices , also its nvme0n1p1 partition recorded under Name: grub-efi/partition_description . I am not sure whether it is safe to remove or modify these values by text editor, but running grub-install or dpkg-reconfigure grub-efi-amd64 as root does not change them . Please help me to resolve this situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939950 Title: shim-signed fails to upgrade when NVMe drive is moved into the VM as Virtio drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1939950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1937951] [NEW] modules for non-existent hardware are loaded for unknown reason (Ubunntu 20.04, kernel 5.4.0-80-generic)
Public bug reported: My laptop is Asus X302LA. I removed its HDD and plugged it externally via USB-SATA convertor. To restore the system's bootability, I had to switch from MODULES=dep to MODULES=most in /etc/initramfs-tools/initramfs.conf and regenerate initramfs images by command update-initramfs -u -k all After a successful boot I checked lsmod output and was surprised by a number of loaded modules for seemingly absent hardware. Like, inv_mpu6050 and ak8975. Do I have a way to check this hardware is actually present and is reporting any meaningful data ? If no, do Ubuntu maintainers of linux kernel and initramfs tools have a way to avoid loading these modules when their hardware is absent ? ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: initramfs-tools (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/1937951 Title: modules for non-existent hardware are loaded for unknown reason (Ubunntu 20.04, kernel 5.4.0-80-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933141] Re: USB Headset stopped working in Ubuntu Impish
Can't reproduce it after the reboot. Can it be caused by too long uptime ? Can't reproduce it with linux-image-generic 5.11.0.20.21+21.10.1 either -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933141 Title: USB Headset stopped working in Ubuntu Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933141] Re: USB Headset stopped working in Ubuntu Impish
** Description changed: - I follow Ubuntu Impish/development on my laptop (Lenovo ideapad 5-15IIL05/81YK00QYRA) - I have all recent Impish updates and kernel linux-image-generic 5.11.0.18.19+21.10.1 into which I rebooted on Jun 5th - Once I tried to plug into it an USB headset Jabra Evolve 20 MS and found that it is visible by lsusb as device 0b0e:0300 but not in audio devices. In dmesg -w, I see two lines + I follow Ubuntu Impish/development on my laptop + (Lenovo ideapad 5-15IIL05/81YK00QYRA). + I have all recent Impish updates and kernel + linux-image-generic 5.11.0.18.19+21.10.1 into which I rebooted on Jun 5th. + Once I tried to plug into it an USB headset Jabra Evolve 20 MS and found that it is visible in lsusb as device 0b0e:0300 but not in audio devices. + In dmesg -w, I see two lines Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7 appearing immediately after plugging this device. - I compared this hardware support with Ubuntu Focal LTS on the nearby - Asus X302LA and found that its modules are loaded as expected, and it - becomes visible, usable and manageable to all audio utilities - (alsamixer, pavucontrol, firefox, vlc, whatever) + I compared this hardware support with Ubuntu Focal LTS on the nearby + Asus X302LA and found that its modules are loaded as expected, + and it becomes visible, usable and manageable to all audio utilities (alsamixer, pavucontrol, firefox, vlc, whatever) - Can this please be checked with Impish and fixed in some way ? + Can this please be checked with Impish and fixed in some way ? I could not determine what module it deems unsigned. Ready to collect and provide additional required information on your request. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933141 Title: USB Headset stopped working in Ubuntu Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933141] [NEW] USB Headset stopped working in Ubuntu Impish
Public bug reported: I follow Ubuntu Impish/development on my laptop (Lenovo ideapad 5-15IIL05/81YK00QYRA) I have all recent Impish updates and kernel linux-image-generic 5.11.0.18.19+21.10.1 into which I rebooted on Jun 5th Once I tried to plug into it an USB headset Jabra Evolve 20 MS and found that it is visible by lsusb as device 0b0e:0300 but not in audio devices. In dmesg -w, I see two lines Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7 appearing immediately after plugging this device. I compared this hardware support with Ubuntu Focal LTS on the nearby Asus X302LA and found that its modules are loaded as expected, and it becomes visible, usable and manageable to all audio utilities (alsamixer, pavucontrol, firefox, vlc, whatever) Can this please be checked with Impish and fixed in some way ? I could not determine what module it deems unsigned. Ready to collect and provide additional required information on your request. ** Affects: linux (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/1933141 Title: USB Headset stopped working in Ubuntu Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Re: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05
$ sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: Sleep Button /dev/input/event3: AT Translated Set 2 keyboard /dev/input/event4: Video Bus /dev/input/event5: Ideapad extra buttons /dev/input/event6: MSFT0001:01 04F3:3140 Mouse /dev/input/event7: MSFT0001:01 04F3:3140 Touchpad /dev/input/event8: sof-hda-dsp Mic /dev/input/event9: sof-hda-dsp Headphone /dev/input/event10: sof-hda-dsp HDMI/DP,pcm=3 /dev/input/event11: sof-hda-dsp HDMI/DP,pcm=4 /dev/input/event12: sof-hda-dsp HDMI/DP,pcm=5 /dev/input/event13: Integrated Camera: Integrated C Select the device event number [0-13]: tried to select 5, could not trigger any events from keyboard tried to select 3, could trigger code 113 (KEY_MUTE), code 114 (KEY_VOLUMEDOWN) and code 115 (KEY_VOLUMEUP) with Fn+F1/F2/F3, _nothing happened_ with pressing Fn+F4 (picture: microphone off), Fn+F5 (picture: brightness down), Fn+F6 (picture: brightness up), Fn+F8 (picture: airplane mode), Fn+Insert (on the right from F12, picture: star and letter S), Fn+PrtSc (picture: scissors and oval pointed cutout) With Fn+F7 (picture: probably switch between local/external display), ^X@sp is printed in the terminal (Konsole), and the following events are dumped : Event: time 1607686644.627232, type 4 (EV_MSC), code 4 (MSC_SCAN), value 19 Event: time 1607686644.627232, type 1 (EV_KEY), code 25 (KEY_P), value 0 Event: time 1607686644.627232, -- SYN_REPORT Event: time 1607686644.632269, type 4 (EV_MSC), code 4 (MSC_SCAN), value db Event: time 1607686644.632269, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 0 Event: time 1607686644.632269, -- SYN_REPORT Fn+F9 (picture: cog wheel or sun) prints ^X@si and code 23 (KEY_I) in the dump, Fn+F10 (picture: lock) prints ^X@sl and code 38 (KEY_L), Fn+F11 (picture: bar with 3 squares within) generated ESC Tab (0x1b 0x9) codes Fn+F12 (picture: calculator) generates code 140 (KEY_CALC) multimedia keys above the Num field generated codes 164 (KEY_PLAYPAUSE), 166 (KEY_STOPCD), 165 (KEY_PREVIOUSSONG) and 163 (KEY_NEXTSONG), accordingly Fn+Space generated no events in evtest, but caused keyboard backlight cycle through medium level, high level and back off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Re: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05
Also I noticed that unplugging power adapter does not make KDE to dim the screen, despite lower screen brightness configured for on-battery mode than on-mains. As if it does not sense difference between "on- battery" and "on-mains" modes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Re: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05
I found that in KDE System Settings/Energy saving I actually can control brightness by moving sliders and clicking Apply or OK. The system just does not react on Fn+F5/F6. So probably the problem is easier than it seemed initially. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907310] Re: initramfs-tools ignores the FRAMEBUFFER option _again_
uninstalled some more hooks and got initrd size of 10 MB (I don't use mdadm on my laptop unlike on server) so everything is probably working well. feel free to close this as "not a bug". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907310 Title: initramfs-tools ignores the FRAMEBUFFER option _again_ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1907310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907310] Re: initramfs-tools ignores the FRAMEBUFFER option _again_
for some strange reason, removing cryptsetup-initramfs helped me to reduce my initrd size back to 12 MB on Hirsute testing laptop. i915 and amdgpu.ko were gone from initrd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907310 Title: initramfs-tools ignores the FRAMEBUFFER option _again_ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1907310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907310] [NEW] initramfs-tools ignores the FRAMEBUFFER option _again_
Public bug reported: see lp:1561643 for the previous 3-year discussion having resulted in a (temporary) fix. Currently, running Ubuntu 21.04 Hirsute, I noticed +60MB growth in initrd files again. Doing lsinitramfs on these images, I found that they are happily stuffed with i915 and amdgpu modules, as well as with netronome nic firmwares which of course everyone surely needs, making initrd of 73 MB. That's with MODULES=dep and FRAMEBUFFER=n in /etc/initramfs-tools/initramfs.conf this does not happen with Ubuntu 20.04, with same options in initramfs.conf. On my Focal system, initrd images have size of 12MB, with largest components being .so libraries and lvm executable. So, I would conclude that initramfs-tools reintroduced this misbehavior after 20.04 release but in some different way. Now trying to compare /usr/share/initramfs-tools content between 20.04 and 21.04. Probably the title of this bug will need to be changed. As I am not allowed to reopen lp:1561643 , I am creating a new bug. ** Affects: initramfs-tools (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/1907310 Title: initramfs-tools ignores the FRAMEBUFFER option _again_ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1907310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442113/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442112/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442111/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442110/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442109/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442108/+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/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442107/+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/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442100/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442106/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442099/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442105/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442097/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442104/+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/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442103/+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/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442102/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442101/+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/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442098/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442096/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442091/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442095/+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/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442094/+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/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442093/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442092/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442090/+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/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442089/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Re: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05
apport information ** Tags added: apport-collected has-workaround hirsute reproducible single-occurrence ubuntu ** Description changed: The keys marked for brightness control on the keyboard are supposed to be Fn+F5 (down) and Fn+F6 (up). But pressing them does not have any effects. Volume control keys Fn+F1 (off), Fn+F2 (down), Fn+F3 (up) all do work, and KDE shows appropriate indicators when they are pressed. I know this is a popular problem with Lenovo laptops. I use Ubuntu 21.04 Hirsute on built-in NVMe, but Ubuntu 20.04 booted from USB flash drive also does not allow me to control screen brightness. Hardware and OS information will be collected on Apport request and attached here. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu55 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: mwg1006 F pulseaudio + mwg1010 F pipewire-media- + /dev/snd/seq:mwg1005 F pipewire + BootLog: + + CasperMD5CheckResult: skip + CompositorRunning: None + CurrentDesktop: KDE + DistUpgraded: Fresh install + DistroCodename: hirsute + DistroRelease: Ubuntu 21.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: I just need to know a workaround + GraphicsCard: + Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) +Subsystem: Lenovo Iris Plus Graphics G1 (Ice Lake) [17aa:3fd9] + HibernationDevice: + #RESUME=UUID=6932e499-f0ad-4456-b93c-2b7f9bf763dc + RESUME=UUID=ce49bc01-a59b-4abf-9110-87bc71689769 + InstallationDate: Installed on 2009-11-01 (4055 days ago) + InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) + MachineType: LENOVO 81YK + NonfreeKernelModules: wl + Package: xorg 1:7.7+19ubuntu15 + PackageArchitecture: amd64 + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-31-generic root=/dev/mapper/vg_c540scadaw-root64 ro rootflags=commit=3600 transparent_hugepage=always init=/lib/systemd/systemd + ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-31-generic N/A + linux-backports-modules-5.8.0-31-generic N/A + linux-firmware1.192 + Tags: hirsute ubuntu single-occurrence reproducible has-workaround + Uname: Linux 5.8.0-31-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm admin cdrom dialout dip disk kvm libvirt lpadmin netdev plugdev sambashare src + _MarkForUpload: True + dmi.bios.date: 07/06/2020 + dmi.bios.release: 1.45 + dmi.bios.vendor: LENOVO + dmi.bios.version: DPCN45WW + dmi.board.asset.tag: NO Asset Tag + dmi.board.name: LNVNB161216 + dmi.board.vendor: LENOVO + dmi.board.version: NO DPK + dmi.chassis.asset.tag: NO Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: IdeaPad 5 15IIL05 + dmi.ec.firmware.release: 1.45 + dmi.modalias: dmi:bvnLENOVO:bvrDPCN45WW:bd07/06/2020:br1.45:efr1.45:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad515IIL05: + dmi.product.family: IdeaPad 5 15IIL05 + dmi.product.name: 81YK + dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 + dmi.product.version: IdeaPad 5 15IIL05 + dmi.sys.vendor: LENOVO + version.compiz: compiz N/A + version.libdrm2: libdrm2 2.4.103-2 + version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.4-1 + version.libgl1-mesa-glx: libgl1-mesa-glx N/A + version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 + version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A + version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1907308/+attachment/5442088/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] Re: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05
** Also affects: xorg (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/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907308] [NEW] screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05
Public bug reported: The keys marked for brightness control on the keyboard are supposed to be Fn+F5 (down) and Fn+F6 (up). But pressing them does not have any effects. Volume control keys Fn+F1 (off), Fn+F2 (down), Fn+F3 (up) all do work, and KDE shows appropriate indicators when they are pressed. I know this is a popular problem with Lenovo laptops. I use Ubuntu 21.04 Hirsute on built-in NVMe, but Ubuntu 20.04 booted from USB flash drive also does not allow me to control screen brightness. Hardware and OS information will be collected on Apport request and attached here. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: xorg (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/1907308 Title: screen brightness up/down keys not working in LENOVO IdeaPad 5 15IIL05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter
I am affected by this bug (P7P55 LX motherboard, GeForce 7600 video, Lubuntu/LXQt 20.04 x86_64 with sddm) See also older bug report at lp:1785184 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1895905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash
** Also affects: lightdm (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/1902871 Title: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1902871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash
Lubuntu 18.04 is based on LXDE, not LXQt, and so it uses lightdm, not sddm. greeter is lightdm-gtk-greeter, which causes traps in libglib like these : ноя 04 16:50:48 user-desktop kernel: traps: lightdm-gtk-gre[673] trap int3 ip:b6f929d0 sp:bf9e9e20 error:0 in libglib-2.0.so.0.5600.4[b6f44000+12e000] ноя 04 16:50:52 user-desktop kernel: traps: lightdm-gtk-gre[736] trap int3 ip:b6fe49d0 sp:bfbcfcd0 error:0 in libglib-2.0.so.0.5600.4[b6f96000+12e000] ноя 04 16:50:54 user-desktop kernel: traps: lightdm-gtk-gre[798] trap int3 ip:b70149d0 sp:bf839010 error:0 in libglib-2.0.so.0.5600.4[b6fc6000+12e000] ноя 04 16:50:56 user-desktop kernel: traps: lightdm-gtk-gre[860] trap int3 ip:b70669d0 sp:bf9a2f40 error:0 in libglib-2.0.so.0.5600.4[b7018000+12e000] ноя 04 16:50:57 user-desktop kernel: traps: lightdm-gtk-gre[922] trap int3 ip:b701a9d0 sp:bfe9c750 error:0 in libglib-2.0.so.0.5600.4[b6fcc000+12e000] ноя 04 16:50:59 user-desktop kernel: traps: lightdm-gtk-gre[984] trap int3 ip:b6fa19d0 sp:bfb4dcb0 error:0 in libglib-2.0.so.0.5600.4[b6f53000+12e000] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902871 Title: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash
** Description changed: Reproduction : - take a bog-standard system with Intel CPU and Intel graphics (mobo like Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock G41C-VS/G31M-S with Intel E3300, or Asrock P4I45GL with Intel Pentium4 2.40GHz) ; + take a bog-standard system with Intel CPU and Intel graphics (mobo like Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock G41C-VS/G41M-VS3/G31M-S with Intel E3300/E3400, or Asrock P4I45GL with Intel Pentium4 2.40GHz) ; install Lubuntu 18.04 i386 on it ; install all latest upgrades including systemd packages of version 237-3ubuntu10.43 ; reboot and watch black screen with blinking text cursor Fix : switch into text console or log in as sudo-capable user over the network look at lightdm crashes in dmesg download past version of systemd packages (237-3ubuntu10.42) install them by dpkg reboot and enjoy your graphic screen again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902871 Title: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash
I found it happens on non-Intel CPUs and VGAs as well. Like, Gigabyte M61PME-S2 with Sempron LE-1200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902871 Title: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash
** Description changed: Reproduction : - take a bog-standard system with Intel CPU and Intel graphics (mobo like Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS/G31M-S with Intel E3300) ; + take a bog-standard system with Intel CPU and Intel graphics (mobo like Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS/G31M-S with Intel E3300, or Asrock P4I45GL with Intel Pentium4 2.40GHz) ; install Lubuntu 18.04 i386 on it ; install all latest upgrades including systemd packages of version 237-3ubuntu10.43 ; reboot and watch black screen with blinking text cursor Fix : switch into text console or log in as sudo-capable user over the network look at lightdm crashes in dmesg download past version of systemd packages (237-3ubuntu10.42) install them by dpkg reboot and enjoy your graphic screen again ** Description changed: Reproduction : - take a bog-standard system with Intel CPU and Intel graphics (mobo like Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS/G31M-S with Intel E3300, or Asrock P4I45GL with Intel Pentium4 2.40GHz) ; + take a bog-standard system with Intel CPU and Intel graphics (mobo like Foxconn 45GM/45CM/45CM-S or ECS 945GCT-M2 with Intel E4500, or ASRock G41C-VS/G31M-S with Intel E3300, or Asrock P4I45GL with Intel Pentium4 2.40GHz) ; install Lubuntu 18.04 i386 on it ; install all latest upgrades including systemd packages of version 237-3ubuntu10.43 ; reboot and watch black screen with blinking text cursor Fix : switch into text console or log in as sudo-capable user over the network look at lightdm crashes in dmesg download past version of systemd packages (237-3ubuntu10.42) install them by dpkg reboot and enjoy your graphic screen again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902871 Title: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902871] Re: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash
** Description changed: Reproduction : - take a bog-standard system with Intel CPU and Intel graphics (mobo like Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS with Intel E3300) ; - install Lubuntu 18.04 i386 on it ; - install all latest upgrades including systemd packages of version 237-3ubuntu10.43 ; - reboot and watch black screen with blinking text cursor + take a bog-standard system with Intel CPU and Intel graphics (mobo like Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS/G31M-S with Intel E3300) ; + install Lubuntu 18.04 i386 on it ; + install all latest upgrades including systemd packages of version 237-3ubuntu10.43 ; + reboot and watch black screen with blinking text cursor Fix : - switch into text console or log in as sudo-capable user over the network - look at lightdm crashes in dmesg - download past version of systemd packages (237-3ubuntu10.42) - install them by dpkg - reboot and enjoy your graphic screen again + switch into text console or log in as sudo-capable user over the network + look at lightdm crashes in dmesg + download past version of systemd packages (237-3ubuntu10.42) + install them by dpkg + reboot and enjoy your graphic screen again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902871 Title: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902871] [NEW] upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash
Public bug reported: Reproduction : take a bog-standard system with Intel CPU and Intel graphics (mobo like Foxconn 45GM/45CM/45CM-S with Intel E4500 or ASRock G41C-VS with Intel E3300) ; install Lubuntu 18.04 i386 on it ; install all latest upgrades including systemd packages of version 237-3ubuntu10.43 ; reboot and watch black screen with blinking text cursor Fix : switch into text console or log in as sudo-capable user over the network look at lightdm crashes in dmesg download past version of systemd packages (237-3ubuntu10.42) install them by dpkg reboot and enjoy your graphic screen again ** 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/1902871 Title: upgrading systemd to v237-3ubuntu10.43 on Ubuntu 18.04 LTS i386 causes lightdm to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753509] Re: avahi-daemon adds/installs every printer on network
please also refer to lp:1379359 and to the GTK2/3 patch at https://launchpad.net/~roman- shipovskij/+archive/ubuntu/gtk+3.0-withoutavahiprinters -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753509 Title: avahi-daemon adds/installs every printer on network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1753509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753509] Re: avahi-daemon adds/installs every printer on network
This bug surely does not belong to "cups-filters" package. And probably it does not belong to Avahi. And to CUPS either. This bug does belong to GTK library and GTK apps which do not provide an option like "list only local CUPS printers, not everything Avahi has sniffed on the network". Avahi is right in its actions, and there are other software relying on its "enable-dbus" option. GTK as library is wrong in having this option enabled by default, and probably some of GTK apps have now learned to override this option properly (that is, in usable and understandable way for an end user). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753509 Title: avahi-daemon adds/installs every printer on network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1753509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884583] Re: vim is dependent on libcanberra0 in Ubuntu 20.04, had no such dependency in Ubuntu 18.04
So this is going to be kept forever ? For vim-nox as well ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884583 Title: vim is dependent on libcanberra0 in Ubuntu 20.04, had no such dependency in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1884583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] Re: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91
1. You should use this adapter in access point mode under hostapd (not in client mode where everything is possibly smooth enough). 2. You should give it a good load, with at least 5 wifi client stations using it, the more is the better. 3. And then just look into your dmesg and stacks that are shown there -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884583] [NEW] vim is dependent on libcanberra0 in Ubuntu 20.04, had no such dependency in Ubuntu 18.04
Public bug reported: which pulls in libasound and some alsa packages which I am not sure why it is useful and desired on most text-only/headless systems. In Debian I also see this dependency arisen with Bullseye/testing and Sid/unstable (but not with Buster/stable) but I don't see any mention of this introduction and its usefulness in the package's changelog. Could the reason of this dependency creation please be investigated, its usefulness evaluated, and if possible, this dependency to be made optional for vim builds ? Surprisingly, installing vim-nox also pulls in libcanberra0. vim-tiny does not pull in libcanberra0, but it also does not have syntax highlighting. What should I do to have syntax highlighting without libcanberra0 overhead ? ** Affects: vim (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/1884583 Title: vim is dependent on libcanberra0 in Ubuntu 20.04, had no such dependency in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1884583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
Thanks, this eliminated the problem. The only unexplained thing is what was the urge to break the "old" package which perfectly worked before. If Ubuntu planned to reorder/restructure package names, the reasonable way would be to turn 'bcmwl-kernel-source' into a dummy/transitional package which would pull new broadcom-sta-* packages as its dependencies. But probably Ubuntu plans were more mysterial than that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876919] [NEW] 6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic x86_64 (Ubuntu Groovy 20.10 dev.branch)
Public bug reported: Diagnostics from apt & dkms post-install : Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-28-generic 5.4.0-29-generic Building for architecture x86_64 Building initial module for 5.4.0-28-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. Probably the patch 0028 adding kernel 5.6 support should not be applied during building on kernel 5.4 As I understand, right now Ubuntu Groovy is still at kernel 5.4, not 5.6 ** Affects: bcmwl (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/1876919 Title: 6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic x86_64 (Ubuntu Groovy 20.10 dev.branch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1876919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] Re: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91
I also noted somewhat similar report at lp:1733194 which probably would be useful to have linked here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] Re: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91
I tried to follow the directions of https://wiki.ubuntu.com/KernelTeam/Netconsole/Early to add early netconsole support to the kernel's initramfs but did not see any signs of this operation succeeded. Had to manually modprobe netconsole with all necessary parameters after the system bootup. Also I noticed that some intermediate kernel stacks recorded in local journalctl were lost to the remote host. Probably because they were sent at 1Gbit/sec and received only at 100Mbit, and my switch is just a simple D-Link DGS-1100-08 without enough storage for multi-packet queues. Or should I increase receive buffer on my RaspberryPi ModelB rsyslog ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] Re: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91
Attaching a log connected with netconsole. Start with the line 'Apr 27 11:40:39' and follow downwards. The most popular message recorded in this dmesg is 'Unhandled alg: 0x707', where 0x707 sometimes is replaced with 0x71b The message immediately preceding reboot is 'ACPI MEMORY or I/O RESET_REG' Last reboots happened on reboot system boot 4.15.0-99-generi Sat May 2 16:53 still running reboot system boot 4.15.0-99-generi Sat May 2 11:01 still running reboot system boot 4.15.0-99-generi Thu Apr 30 15:07 still running reboot system boot 4.15.0-99-generi Wed Apr 29 20:42 still running reboot system boot 4.15.0-96-generi Mon Apr 27 13:21 - 20:41 (2+07:20) reboot system boot 4.15.0-96-generi Mon Apr 27 12:06 - 20:41 (2+08:35) reboot system boot 4.15.0-96-generi Mon Apr 27 12:01 - 20:41 (2+08:40) and the most popular header of multiline message preceding the reboot message is either 'soft lockup' or 'unable to handle NULL pointer dereference' where command pointer is at iwl_trans_pcie_txq_enable+0x62/0x470 or iwl_mvm_tx_tso.isra.22.constprop.24+0x101/0x540 ** Attachment added: "messages.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+attachment/5365078/+files/messages.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] Re: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91
With kernel 4.15.0-96 it started rebooting with weekly intervals (did so on Apr 9th, 16th, 23rd). Also as you know AR9271 is notorious for its hanging firmware, so for some of these reboots I had to unplug-replug it in its USB port, else Linux could not complete its boot. In the nearest weekend I would get a Raspberry Pi to make a netconsole log collector and provide more information. Please keep this bug open, don't close it by any timeout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348891/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348898/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348895/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348896/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348894/+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/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348899/+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/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348893/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348892/+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/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] Re: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91
apport information ** Description changed: My home server/router/access point runs under Ubuntu 18.04.4 with all updates and has 2 wifi adapters operated by hostapd one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 9260 (8086:2526, driver iwlwifi). with kernel 4.15.0-88 it worked quite stable, with reboots required mostly after kernel upgrades (much less frequent reboots due to panics) with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a lot of activity happening via Intel 9260. In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and kernel.panic_on_oops=1 overrides of default values. In dmesg logs preceding the reboot, I see multiple warnings with stacks inside iwl_mvm functions which I could provide by apport. Also, multiple messages like "Command LQ_CMD: a command is already active!" or "Error sending LQ_CMD: time out after 2000ms" Unfortunately I run this box headless and I don't have another wired Ethernet host to capture its panics by netconsole The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, nothing overly special. More details I would provide in your further requests but the current kernel behavior is very annoying. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e + InstallationDate: Installed on 2009-11-01 (3810 days ago) + InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) + MachineType: ASUS All Series + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 loop.max_part=63 + ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.15.0-96-generic N/A + linux-backports-modules-4.15.0-96-generic N/A + linux-firmware 1.173.17 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 4.15.0-96-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago) + UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src + _MarkForUpload: True + dmi.bios.date: 07/22/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2501 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: B85M-G + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.family: ASUS MB + dmi.product.name: All Series + dmi.product.version: System Version + dmi.sys.vendor: ASUS ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348890/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348902/+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/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348900/+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/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348897/+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/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1871430/+attachment/5348901/+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/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] Re: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91
** Tags added: apport-collected bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871430] [NEW] iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91
Public bug reported: My home server/router/access point runs under Ubuntu 18.04.4 with all updates and has 2 wifi adapters operated by hostapd one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 9260 (8086:2526, driver iwlwifi). with kernel 4.15.0-88 it worked quite stable, with reboots required mostly after kernel upgrades (much less frequent reboots due to panics) with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a lot of activity happening via Intel 9260. In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and kernel.panic_on_oops=1 overrides of default values. In dmesg logs preceding the reboot, I see multiple warnings with stacks inside iwl_mvm functions which I could provide by apport. Also, multiple messages like "Command LQ_CMD: a command is already active!" or "Error sending LQ_CMD: time out after 2000ms" Unfortunately I run this box headless and I don't have another wired Ethernet host to capture its panics by netconsole The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, nothing overly special. More details I would provide in your further requests but the current kernel behavior is very annoying. ** Affects: linux (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/1871430 Title: iwlwifi/iwlmvm & Intel 9260 made kernel unstable since 4.15.0-91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862021] Re: opening .rtf file renamed with .doc extension crashes lowriter
On LO 1:6.3.4-0ubuntu1 and Ubuntu Focal Fossa (development branch) 20.04, this is not reproduced. looks like it has been fixed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862021 Title: opening .rtf file renamed with .doc extension crashes lowriter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803309] Re: xmlindent Assertion `strlen(yytext) == 1' failed
In Debian it was fixed in <1 mouth after the initial 18.04 LTS release. Would be great to have it integrated into 18.04 before the end of its long-term support period. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803309 Title: xmlindent Assertion `strlen(yytext) == 1' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862021] [NEW] opening .rtf file renamed with .doc extension crashes lowriter
Public bug reported: Ubuntu 18.04.4, LibreOffice 1:6.0.7-0ubuntu0.18.04.10 (all i386, not amd64, also without JRE to avoid crashes on LP:1699772) We received some files with .doc extension which actually were in RTF format (as 'file' showed) When we tried to open these files, lowriter crashed every time. Abiword opened the same files fine. Probably it detects their type by content, not only by extension. For LO, the cure was to rename them manually from .doc into .rtf, then lowriter could also open them without crashing. Probably some Abiword logic of file type detection should be borrowed into LO to improve user's convenience. Later today I will add my results from LO 1:6.3.4-0ubuntu1 which I test on my home system as a part of upcoming Ubuntu 20.04 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Description changed: - Ubuntu 18.04.4, LibreOffice 1:6.0.7-0ubuntu0.18.04.10 + Ubuntu 18.04.4, LibreOffice 1:6.0.7-0ubuntu0.18.04.10 (all i386. not + amd64, also without JDK to avoid crashes on LP:1699772) We received some files with .doc extension which actually were in RTF format (as 'file' showed) When we tried to open these files, lowriter crashed every time. Abiword opened the same files fine. Probably it detects their type by content, not only by extension. For LO, the cure was to rename them manually from .doc into .rtf, then lowriter could also open them without crashing. Probably some Abiword logic of file type detection should be borrowed into LO to improve user's convenience. Later today I will add my results from LO 1:6.3.4-0ubuntu1 which I test on my home system as a part of upcoming Ubuntu 20.04 ** Description changed: - Ubuntu 18.04.4, LibreOffice 1:6.0.7-0ubuntu0.18.04.10 (all i386. not + Ubuntu 18.04.4, LibreOffice 1:6.0.7-0ubuntu0.18.04.10 (all i386, not amd64, also without JDK to avoid crashes on LP:1699772) We received some files with .doc extension which actually were in RTF format (as 'file' showed) When we tried to open these files, lowriter crashed every time. Abiword opened the same files fine. Probably it detects their type by content, not only by extension. For LO, the cure was to rename them manually from .doc into .rtf, then lowriter could also open them without crashing. Probably some Abiword logic of file type detection should be borrowed into LO to improve user's convenience. Later today I will add my results from LO 1:6.3.4-0ubuntu1 which I test on my home system as a part of upcoming Ubuntu 20.04 ** Description changed: Ubuntu 18.04.4, LibreOffice 1:6.0.7-0ubuntu0.18.04.10 (all i386, not - amd64, also without JDK to avoid crashes on LP:1699772) + amd64, also without JRE to avoid crashes on LP:1699772) We received some files with .doc extension which actually were in RTF format (as 'file' showed) When we tried to open these files, lowriter crashed every time. Abiword opened the same files fine. Probably it detects their type by content, not only by extension. For LO, the cure was to rename them manually from .doc into .rtf, then lowriter could also open them without crashing. Probably some Abiword logic of file type detection should be borrowed into LO to improve user's convenience. Later today I will add my results from LO 1:6.3.4-0ubuntu1 which I test on my home system as a part of upcoming Ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862021 Title: opening .rtf file renamed with .doc extension crashes lowriter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776013] Re: systemd-networkd: DHCP lease lost (Ubuntu 18.04)
The problem I had was not related to netplan, networkd or dhcp client of any kind. I had both my ISP links connected to a VLAN switch DLink DGS-1100-08 and multiplexed to a single Linux router interface with different VLAN numbers. On Linux side, vlan.NNN interfaces were configured to separate each ISP traffic by its VLAN number. These interfaces were managed by separate DHCP clients, requesting dynamic IPs from their corresponding ISP. Both ISPs had a policy permitting only a single MAC address to request a DHCP lease on a single customer's port. And this was combined with the fact that for some Ethernet protocols, DLink VLAN switches of this model do not obey VLAN isolation rules. In part, among them were DLink's own discovery & loobpack detection protocols (Ether.proto number = 0x9000, using multicast MAC addresses prefixed with CF: byte). My both ISPs had a plenty of DLink hardware in their Ethernet segments, and my DLink switch inadvertently served as a bridge for DLink discovery packets, allowing them to fly freely between two VLANs. Which of course was detected by each other ISP's policy as 'stray MACs' on a single customer port, and caused my real MAC to be temporarily kicked out from their valid MAC set, which subsequently caused DHCP lease loss. What resolved by problem once and for all, was installing dual-port PCIe Gigabit Ethernet adapter into my Linux router and physically plugging my ISP links into its separate ports. Detailed discussion can be seen at http://forums.dlink.com/index.php?topic=74704.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776013 Title: systemd-networkd: DHCP lease lost (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1776013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option
can't believe it was fixed in less than 3 short years -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818864] [NEW] migrated LVM2 VG to a different PV and now getting 'error: invalid volume' from update-grub
Public bug reported: my Ubuntu is 18.04.2 with all updates applied in the past my VG resided on /dev/md1 PV I installed new HDDs, created /dev/md0 (this name was unused since previous PV migration some years ago), updated /etc/mdadm/mdadm.conf , moved LVs from /dev/md1 to /dev/md0 (with pvmove), removed /dev/md1 PV from the VG, then stopped and removed /dev/md1 , then updated mdadm.conf again. I regenerated initrd image by dpkg-reconfigure to include updated mdadm.conf and now, when I run update-grub , I get this : Sourcing file `/etc/default/grub' Generating grub configuration file ... error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. Found linux image: /boot/vmlinuz-4.15.0-46-generic Found initrd image: /boot/initrd.img-4.15.0-46-generic error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. I am not sure what could be the cause of this behavior. How can I tell what volume exactly is invalid and how can I fix this situation ? The only potential problem I see is that now I have 2 FAT copies for EFI boot partition having identical UUIDs. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Description changed: my Ubuntu is 18.04.2 with all updates applied in the past my VG resided on /dev/md1 - I installed new HDDs, created /dev/md0 , updated /etc/mdadm/mdadm.conf , moved LVs from /dev/md1 to /dev/md0 (with pvmove), then stopepd and removed /dev/md1 , then updated mdadm.conf again. + I installed new HDDs, created /dev/md0 , updated /etc/mdadm/mdadm.conf , moved LVs from /dev/md1 to /dev/md0 (with pvmove), removed /dev/md1 PV from the VG, then stopped and removed /dev/md1 , then updated mdadm.conf again. I regenerated initrd image by dpkg-reconfigure to include updated mdadm.conf and now, when I run update-grub , I get this : Sourcing file `/etc/default/grub' Generating grub configuration file ... error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. Found linux image: /boot/vmlinuz-4.15.0-46-generic Found initrd image: /boot/initrd.img-4.15.0-46-generic error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. I am not sure what could be the cause of this behavior. How can I tell what volume exactly is invalid and how can I fix this situation ? The only potential problem I see is that now I have 2 FAT copies for EFI boot partition having identical UUIDs. ** Description changed: my Ubuntu is 18.04.2 with all updates applied - in the past my VG resided on /dev/md1 - I installed new HDDs, created /dev/md0 , updated /etc/mdadm/mdadm.conf , moved LVs from /dev/md1 to /dev/md0 (with pvmove), removed /dev/md1 PV from the VG, then stopped and removed /dev/md1 , then updated mdadm.conf again. + in the past my VG resided on /dev/md1 PV + I installed new HDDs, created /dev/md0 (this name was unused since previous PV migration some years ago), updated /etc/mdadm/mdadm.conf , moved LVs from /dev/md1 to /dev/md0 (with pvmove), removed /dev/md1 PV from the VG, then stopped and removed /dev/md1 , then updated mdadm.conf again. I regenerated initrd image by dpkg-reconfigure to include updated mdadm.conf and now, when I run update-grub , I get this : Sourcing file `/etc/default/grub' Generating grub configuration file ... error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. Found linux image: /boot/vmlinuz-4.15.0-46-generic Found initrd image: /boot/initrd.img-4.15.0-46-generic error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. error: invalid volume. I am not sure what could be the cause of this behavior. How can I tell what volume exactly is
[Bug 1429030] Re: netboot mini.iso doesn't support UEFI boot
Add my vote for getting Ubuntu mini.iso compliant with Debian and currently-common sense overall. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429030 Title: netboot mini.iso doesn't support UEFI boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1429030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579168] Re: VPNs to hosts resolving to multiple IPs often fail
well, the discussion has unfolded quickly with a negative response from James Cameron (probably the only remaining/active author of pptpclient). from there, I would see these options of what to do next : - send more responses voicing user concerns and interest in this feature to the started discussion; - propose our own patch for get_ip_address function in pptp.c (not sure I am capable enough as a C programmer, but I would start from OpenSSH patch posted at https://groups.google.com/forum/#!topic/opensshunixdev/lErxlPk_MnA as a source for inspiration ); - create some external wrapper for quickly scanning a list of IPs and returning the fastest-responding one to be substituted into pptp command line. For a start, I would use nmap with arguments like these: nmap --script resolveall --script-args newtargets -PS1723 -sn vpn.server.name # as described at https://serverfault.com/questions/843304/can-nmap-scan-test-all-answers-from-round-robin-dns or at https://security.stackexchange.com/questions/141480/nmap-to-scan-all-resolved-ip-addresses-for-a-given-domain-name and then process its output in some automated way (I only used it manually and interpreted visually). this substitution can be usable with pppd configs stored in /etc/ppp/peers but I am unsure if it could be easily integrated into Network Manager setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/579168 Title: VPNs to hosts resolving to multiple IPs often fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/579168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579168] Re: VPNs to hosts resolving to multiple IPs often fail
please watch the unfolding discussion (or crickets chirping) - https://sourceforge.net/p/pptpclient/mailman/pptpclient-devel/?viewmonth=201811 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/579168 Title: VPNs to hosts resolving to multiple IPs often fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/579168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 579168] Re: VPNs to hosts resolving to multiple IPs often fail
I would attach this bug to pptp-linux package Also I will initiate a discussion about RFC8305 support on pptpclient-devel, expect it to appear in their November 2018 archives soon. ** Also affects: pptp-linux (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/579168 Title: VPNs to hosts resolving to multiple IPs often fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/579168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796504] [NEW] gparted does not see f2fs-tools installed (Ubuntu 18.10 Cosmic)
Public bug reported: $ dpkg -l gparted f2fs-tools ii f2fs-tools 1.10.0-1amd64 Tools for Flash-Friendly File System ii gparted0.32.0-1ubuntu1 amd64 GNOME partition editor $ sudo blkid /dev/sdb1: SEC_TYPE="msdos" UUID="001B-BEEA" TYPE="vfat" PARTUUID="63d47932-01" /dev/sdb2: UUID="4f41dbd2-8204-4d90-acf4-de1d7280d91b" TYPE="f2fs" PARTUUID="63d47932-02" $ sudo fsck /dev/sdb2 fsck з util-linux 2.32 Info: [/dev/sdb2] Disk Model: STORE N GO1.0APPOTECHUDISK��u\�\ӕKP Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 30267392 (14779 MB) Info: MKFS version "Linux version 4.4.0-72-generic (buildd@lcy01-17) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017" Info: FSCK version from "Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018" to "Linux version 4.18.0-8-generic (buildd@lgw01-amd64-055) (gcc version 8.2.0 (Ubuntu 8.2.0-6ubuntu1)) #9-Ubuntu SMP Mon Sep 10 16:12:10 UTC 2018" Info: superblock features = 0 : Info: superblock encrypt level = 0, salt = Info: total FS sectors = 30267392 (14779 MB) Info: CKPT version = 1de1 Info: Found valid nat_bits in checkpoint Info: checkpoint state = 2c5 : allow_nocrc nat_bits crc compacted_summary unmount [FSCK] Unreachable nat entries[Ok..] [0x0] [FSCK] SIT valid block bitmap checking[Ok..] [FSCK] Hard link checking for regular file[Ok..] [0x9] [FSCK] valid_block_count matching with CP [Ok..] [0xc2244] [FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0x157fd] [FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x157fd] [FSCK] valid_inode_count matched with CP [Ok..] [0x156d1] [FSCK] free segment_count matched with CP [Ok..] [0x145a] [FSCK] next block offset is free [Ok..] [FSCK] fixing SIT types [FSCK] other corrupted bugs [Ok..] Done. ... and then, running gparted on /dev/sdb , I get a yellow warning triangle and a message in partition information : "Unable to read the contents of this file system! Because of this some operations may be unavailable. The cause might be a missing software package. The following list of software packages is required for f2fs file system support: f2fs-tools." can this be caused by different mkfs/fsck/kernel versions ? or this is some overlook during gparted development ? ** Affects: gparted (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/1796504 Title: gparted does not see f2fs-tools installed (Ubuntu 18.10 Cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1796504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option
God, I can't believe it would really get into Ubuntu 20.04 Only 1.5 short years of waiting left -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792877] [NEW] during adding SMB printer shared from WinXP, 'Browse' button works but 'Verify' does not
Public bug reported: LUbuntu 18.04.1 with all updates, 32-bit x86 PC, top-level package 'lubuntu-desktop' is installed, smbclient/smbspool are installed but smbd/nmbd are not (to save runtime RAM) MFU Canon MF3228 is attached to Windows XP and shared from it by SMB XP is not a domain member, only workgroup. For 'security' reasons, a user is created on WinXP with name 'print' and password 'print1' (because guest access apparently did not work) Now, I start 'system-config-printer' as root and try to add a printer. I select 'Windows printer via Samba', I enter XP IP and printer share name into 'smb://' field, then click 'Browse'. After a short pause, I get 'Authorization required' dialog where I can enter login, domain/workgroup and password. And there, my Authorization is successful, I can select shared printer name and click 'OK'. But to complete printer setup, I have to enter these login and password into 'Authentication' section, where I see 'Verify' button. Above it I also see 'Username:' and 'Password:' fields, where password is entered above the username for unknown reason, and no field for workgroup or domain. And I was never able to Verify the same login and password fields however I tried. I entered login and password in the reverse, I prepended XP hostname and workgroup name before login, I used '\' and '/' separators - no luck Surely I know that Linux interoperation with Windows is not of top priority with Ubuntu developers, but I would be happy if such kind of a very popular household scenario were tested for Ubuntu LTS releases in some way. Thank you in advance for your responses. ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Description changed: LUbuntu 18.04.1 with all updates, 32-bit x86 PC, top-level package 'lubuntu-desktop' is installed, smbclient/smbspool are installed but smbd/nmbd are not (to save runtime RAM) MFU Canon MF3228 is attached to Windows XP and shared from it by SMB XP is not a domain member, only workgroup. - For 'security' reasons user is created on WinXP with name 'print' and password 'print1' (because guest access apparently did not work) + For 'security' reasons, a user is created on WinXP with name 'print' and password 'print1' (because guest access apparently did not work) - Now, I start 'system-config-printer' as root and try to add a printer - I select 'Windows printer via Samba', I enter IP and printer share name into 'smb://' field, then click 'Browse'. After a short pause, I get 'Authorization required' dialog where I can enter login, domain/workgroup and password. And there, my Authorization is successful, I can select shared printer name and click 'OK'. + Now, I start 'system-config-printer' as root and try to add a printer. + I select 'Windows printer via Samba', I enter XP IP and printer share name into 'smb://' field, then click 'Browse'. After a short pause, I get 'Authorization required' dialog where I can enter login, domain/workgroup and password. And there, my Authorization is successful, I can select shared printer name and click 'OK'. But to complete printer setup, I have to enter these login and password into 'Authentication' section, where I see 'Verify' button. Above it I also see 'Username:' and 'Password:' fields, where password is entered above the username for unknown reason, and no field for workgroup or domain. And I was never unable to Verify the same login and password fields however I tried. I entered login and password in the reverse, I prepended XP hostname and workgroup name before login, I user '\' and '/' separators - no luck Surely I know that Linux interoperation with Windows is not of top priority with Ubuntu developers, but I would be happy if such kind of a very popular household scenario were tested for Ubuntu LTS releases in some way. Thank you in advance for your responses. ** Description changed: LUbuntu 18.04.1 with all updates, 32-bit x86 PC, top-level package 'lubuntu-desktop' is installed, smbclient/smbspool are installed but smbd/nmbd are not (to save runtime RAM) MFU Canon MF3228 is attached to Windows XP and shared from it by SMB XP is not a domain member, only workgroup. For 'security' reasons, a user is created on WinXP with name 'print' and password 'print1' (because guest access apparently did not work) Now, I start 'system-config-printer' as root and try to add a printer. I select 'Windows printer via Samba', I enter XP IP and printer share name into 'smb://' field, then click 'Browse'. After a short pause, I get 'Authorization required' dialog where I can enter login, domain/workgroup and password. And there, my Authorization is successful, I can select shared printer name and click 'OK'. But to complete printer setup, I have to enter these login and password into 'Authentication' section, where I see 'Verify' button. Above it I also see 'Username:' and 'Password:'
[Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
well, what is really mispackaged, is Epson's iscan 1.0.1 package which places its .so backends into /usr/lib/sane , which is now went our of sync with multi-arch library paths like /usr/lib/x86_64-*-*/sane , introduced in some of past Ubuntu release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755033] Re: Lubuntu daily 20180311 black screen for 5 min on ASUS Eee901
Can you remove 'quiet splash' from the kernel's boot command line ? (by editing it in GRUB or Syslinux/ISOLinux menu) Then you would see in textual form, on what systemd boot point it hangs the most. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755033 Title: Lubuntu daily 20180311 black screen for 5 min on ASUS Eee901 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1755033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783579] Re: Not possible to use pppoe or pptp
True, as if its authors happily forgot that ppp/pppoe/pptp is still widely used all over the world Also, systemd-networkd authors look similar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783579 Title: Not possible to use pppoe or pptp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1783579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772348] Re: HP Laserjet M1212nf MFP also affected
I installed Cosmic HPLIP 3.18.7 packages, including libsane-hpaio, and this solved the problem I had with using M1212nf on Ubuntu Bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772348 Title: HP Laserjet M1212nf MFP also affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1772348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
I am not sure everyone needs to install Brother driver to make Epson scanner work (that's in Ubuntu 18.04) I am going to set up samples of Ubuntu LTS from Bionic down to Trusty and probably Precise, and report on their compatibility with the extensive zoo of printers, scanners and MFUs I have on my new job. Having regressions in modern Ubuntu releases where past releases worked well is unacceptable, their causes should be investigated and eliminated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
Dear package maintainers, as you see, 'epkowa' and some other Epson backends are clearly mispackaged. Also, Epson USB device permissions should be set properly by udev Let's see if this problem does have any chances to be fixed in Ubuntu 18.04 before 20.04 is released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613070] Re: i7-6500U screen flickering and blinking
>From what I read on this topic. this could well be Asus hardware problem. Display and mainboard are fed from a single PSU. And when this PSU is on batteries, and the mainboard is taking peak current for its CPU, display LED highlight is getting underpowered and it is going black. I have at least two Asus X302 modifications at hand (X302LA and X302UV), showing exactly this behavior under either Linux (Ubuntu 18.04) or Windows 10 (1803). So I would suppose this is not easily fixable with software. When there'll be time to replace these laptops, I surely will try to ask repairmen about fixing their backlights. But so far, they are our daily-used 'production' systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613070 Title: i7-6500U screen flickering and blinking To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1613070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788681] Re: changed exit code for 'dc' in Ubuntu Bionic
same is reproduced when you run 'dc', enter into it some expression ending with 'p q', and examining its exit code with 'echo $?' afterwards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788681 Title: changed exit code for 'dc' in Ubuntu Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bc/+bug/1788681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788681] [NEW] changed exit code for 'dc' in Ubuntu Bionic
Public bug reported: in Ubuntu Xenial : $ lsb_release -rdc ; echo 1 1 + p q | dc ; echo $? Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial 2 0 in Ubuntu Bionic : $ lsb_release -rdc ; echo 1 1 + p q | dc ; echo $? Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic 2 1 This change causes some scripts using 'dc' to fail, most importantly, 'dphys-swapfile' which for some ironic reason uses 'dc' instead of 'echo $((...))' for its calculations. ** Affects: bc (Ubuntu) Importance: Undecided Status: New ** Affects: dphys-swapfile (Ubuntu) Importance: Undecided Status: New ** Also affects: dphys-swapfile (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/1788681 Title: changed exit code for 'dc' in Ubuntu Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bc/+bug/1788681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regression: many user-space
What's interesting, is that lowriter does not crash in 32-bit LinuxMint-Mate 19 (based on Ubuntu Bionic 18.04) with either 4.15.0-20 initial kernel, or -33 updated from Bionic. with 32-bit Lubuntu 18.04 it still crashes under -33 kernel, so the fix is clearly in some different place. probably LinuxMint authors know some magic incantations -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regression: many user-space
Is there any chance to have this fixed in Ubuntu 18.04 earlier than 20.04 is released ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784173] Re: after upgrade to Xubuntu 18.04 Libreoffice crashes during starting
I did not reproduce this problem under amd64 Ubuntu 18.04 so I would guess that it affects only 32-bit LibreOffice+OpenJDK11 (i386/i686). Probably because testing 32-bit packages is of lesser priority. ** Also affects: openjdk-lts (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/1784173 Title: after upgrade to Xubuntu 18.04 Libreoffice crashes during starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1784173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784173] Re: after upgrade to Xubuntu 18.04 Libreoffice crashes during starting
found this problem with 32-bit Lubuntu 18.04 (i386/i686), my 'lowriter' crashed
in strace there was SIGSEGV in some of spawned processes ('soffice.bin')
what helped me, was removing Java stuff ('apt remove openjdk-11-jre-headless' ,
then 'apt autoremove')
after that, 'lowriter' complained about missing JRE, but at least it started
with working window as expected.
probably this bug should be attributed to OpenJDK packages as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784173
Title:
after upgrade to Xubuntu 18.04 Libreoffice crashes during starting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1784173/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
