[Bug 1966007] Re: Flood of Bluetooth Malicious advertisind data

2022-03-29 Thread Andras Tim
The `gnome-terminal` is not affected by the kernel's Bluetooth issue... ** Package changed: gnome-terminal (Ubuntu) => linux-signed (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966007 Titl

[Bug 1876157] Re: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020

2021-05-03 Thread Andras Tim
I have the same issue as comment #6 on Ubuntu Server 20.04.1 installer that booted from a flash drive. HW: 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop) 00:14.0 USB

[Bug 1780196] Re: Timed out Availability of block devices service

2018-07-23 Thread Andras Tim
** Also affects: mdadm (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/1780196 Title: Timed out Availability of block devices service To manage no

[Bug 1780196] Re: Timed out Availability of block devices service

2018-07-11 Thread Andras Tim
I think it can be fixed in 2 ways: * blkdeactivate handles properly the syncing software-raid arrays * re-order this service, to be after the "standard" software-raid deinit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs

[Bug 1780196] Re: Timed out Availability of block devices service

2018-07-11 Thread Andras Tim
FYI: This problem can happen when the md0 device still synchronizing. Now, when the md0 is in sync, the service stopped as well: # journalctl -b -1 -u blk-availability.service systemd[1]: Starting Availability of block devices... systemd[1]: Started Availability of block devices. systemd[1]: Stop

[Bug 1780196] Re: Timed out Availability of block devices service

2018-07-11 Thread Andras Tim
I found the commit where introduced this blkdeactivate: https://sourceware.org/git/?p=lvm2.git;a=commit;h=c698ee14bbb1310cf2383c8977d14a8e29139f8c > Traverses the tree of block devices and tries to deactivate them. > Currently, it supports device-mapper-based devices together with LVM. > See man/b

[Bug 1780196] [NEW] Timed out Availability of block devices service

2018-07-05 Thread Andras Tim
Public bug reported: On a fresh Ubuntu 18.04 (64 bit) Server install, the blk- availability.service always killed by timeout at shutdown. I think the dependency of this service is bad, but I don't know what would be the good shutdown order for this. An almost same config has been worked on Xenia

[Bug 1574125] Re: [Lenovo G50-70] suspend not working after upgrade

2016-08-18 Thread Andras Tim
A kernel upgrade was fixed my problem. I updated my Xenial kernel (4.4.0-34.53) to the latest Yakkety kernel (4.6.3-040603.201606241434) Installed .debs, what solves my problem: * http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6.3-yakkety/linux-headers-4.6.3-040603_4.6.3-040603.201606241434_all

[Bug 1574125] Re: [Lenovo G50-70] suspend not working after upgrade

2016-08-18 Thread Andras Tim
I have this problem on my Dell Latitude E5440 :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574125 Title: [Lenovo G50-70] suspend not working after upgrade To manage notifications about this bu