[Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
Hi Maria, I don't think your issue is the same I got. Note that my problem happened with or without the dock, and I wasn't even reaching grub. That's the big difference here. If you lose the video after grub, than your problem is elsewhere, and my suggestion is to boot without "quiet splash" on the grup command line, so that you can see where the boot is stuck. If it reaches the end of the boot process and it is just unable to start X (so GDM, LightDM or whatever), then your problem might be related to the drivers, maybe not blacklisting nouveau or things like these. Maybe as suggested elsewhere [1], you just need to uninstall the buggy xserver-xorg-video-intel package. What is more important here is that my problem got solved by setting the "Set Optimized" option in the BIOS to true. This solved a huge amount of problems, the last one I'm waiting to solve before closing this bug is to understand how to boot without a customized /etc/X11/xorg.conf. Hope this helps. [1] https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879484 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879484] Re: Lenovo X1 Extreme with thunderbolt docking station causes overheat with concert of fans
Ok, I'll check with Cinnamon, but with GNOME, using the CPUFreq applet as I wrote things are doing well, you can find attached the up-to-date journal1.txt. What about the xorg.conf issue? Do you have any suggestion on that front? ** Attachment added: "journal1.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879484/+attachment/5374585/+files/journal1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879484 Title: Lenovo X1 Extreme with thunderbolt docking station causes overheat with concert of fans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879484] Re: Lenovo X1 Extreme with thunderbolt docking station causes overheat with concert of fans
Hi Daniel and thanks for your answer. First of all I removed the "xserver-xorg-video-intel" package, but I still need an /etc/X11/xorg.conf configured as described here [1] (replacing "intel" with "modeset") to make lightdm or gdm3 start a session. Without it, it simply don't start. Is this expected or do I need to apply some sort of trick to make X start? About the over heating, I installed CPUFreq [2] and things improved a lot, mainly under Gnome on which fans are silent the most of the time, Cinnamon still lacks somehow because of some sort of missing full integration. The journal.txt I've attached to this comment comes from a Cinnamon session, hope this helps somehow. I'm open for any kind of suggestions and tests. Thanks! [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741 [2] https://github.com/konkor/cpufreq ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879484/+attachment/5374565/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879484 Title: Lenovo X1 Extreme with thunderbolt docking station causes overheat with concert of fans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
Do you have any suggestions about what could be the difference here? Since I didn't do a fresh install, but an upgrade from 19.10? Without that xorg.conf there's no way to see X. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879484] [NEW] Lenovo X1 Extreme with thunderbolt docking station causes overheat with concert of fans
Public bug reported: Hey everyone, after resolving some of the problems I got after upgrading to 20.04 [1] I'm now using my Lenovo X1 Extreme Gen 2 with the thunderbolt docking station (and an HDMI monitor attached). Everything worked out of the box, except for the increased general heat of the system (constantly over 70 °C) and the consequent concert of fans that makes working aside the (closed) laptop almost impossible. It is really hard to understand if there's a specific process causing the CPU to be so constantly stressed, and what is more curious is that monitoring the general status of the system resources (CPU, Memory and so on) there are no peaks, it shows a normal usage, which is what I do: browser, mail, and some console. Something I would expect that with 16 cpu and 32 gigs of RAM should not be a concern. Both thermald and tlp services are obviously installed and running. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4 Uname: Linux 5.6.0-1008-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Tue May 19 12:41:24 2020 DistUpgraded: 2020-04-28 11:09:59,157 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8324, 5.4.0-31-generic, x86_64: installed nvidia, 440.64, 5.4.0-31-generic, x86_64: installed nvidia, 440.64, 5.6.0-1008-oem, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2019-12-10 (161 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1008-oem root=UUID=c61df9cc-bd36-4ed2-8f52-de114bbf3fc3 ro rd.driver.blacklist=nouveau modprobe.blacklist=nouveau SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (21 days ago) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal performance ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879484 Title: Lenovo X1 Extreme with thunderbolt docking station causes overheat with concert of fans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
Hi there, I wanted to add that I've tried the Thunderbolt dock and everything seems to be working as expected, even if there's a lot more of fan noise while the laptop is attached to the dock (maybe I'll open a specific bug on this issue). For this bug I don't think there's only one thing to clarify before closing it, and it is the one related to the Xorg configuration. Since out-of-the-box I was not able to have an X session working unless using the manual Xorg configuration described in the previous comment. Is there any advice on this? It is just the way it should be? Once we clarify this I think we can safely close this bug. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
I was able to get LightDM (or GDM) with hybrid graphics only by manually specifying an /etc/X11/xorg.conf file like follows (I generated it with nvidia-xconfig and then made manual modifications following this [1]): # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 440.64 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 1650 with Max-Q Design" BusID "PCI:1:0:0" EndSection Section "Device" Identifier "Device1" Driver "intel" VendorName "Intel" BusID "PCI:0@0:2:0" Option "AccelMethod" "SNA" EndSection Section "Screen" Identifier "Screen1" Device "Device1" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 Option "AllowEmptyInitialConfiguration" "True" SubSection "Display" Depth 24 EndSubSection EndSection Are you using a similar configuration for X or it just works for you out of the box? About the BIOS, I checked and "Set Optimized" was Disable for me, turning it to Enable seems to make me able to reboot with a Thunderbolt adapter connected to the port. Many thanks for your help! [1] https://gist.github.com/alexlee-gk/76a409f62a53883971a18a11af93241b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
Hey AaronMa, What do you mean with "found that LID close until the BIOS logo show, unless the laptop will shut down."? So you tested using the HDMI cable directly attached to the laptop and everything worked even with something attached to the thunderbolt port? Which kind of docking station are you using? With that said I've tried the latest BIOS: BIOS Information Vendor: LENOVO Version: N2OET42W (1.29 ) Release Date: 01/20/2020 Address: 0xE Runtime Size: 128 kB ROM Size: 32 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 3.5"/720 kB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.29 Firmware Revision: 1.22 And results are the same: if something is attached to thunderbolt, no way to see even grub, if nothing is attached (and LID is closed) then I see grub loading on the external monitor but I don't get GDM. What do you mean exactly with "BIOS should be default setting with optimized enabled"? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
Just a follow up with my investigations in the issue, that might be useful for users in a similar situation. The problem related to grub not loading and fans lifting with no tomorrow is related to Thunderbolt. If I leave any kind of device (network adapter, webcam, whatever) attached to any of the two Thunderbolt ports, then any kind of boot (or reboot) will likely fail like I described above. While looking for solutions, I got into the certification page of my laptop [1] and saw that it says: "This system was tested with 18.04 LTS, running the 4.15.0-1059-oem kernel." Now, this kernel is not present in 20.04, but I've installed 5.6.0-1008-oem and despite of the certification, nothing changes at all. So, the state of things right now: - If I want to be sure the system will load grub, then nothing should be connected to the Thunderbolt port; - If I want to use HDMI output I MUST set "Discrete" (and not "Hybrid") in the BIOS for the display adapter; - If I want GDM/LightDM/Whatsoever to be loaded than the laptop lid should be left open until the end of the boot process, otherwise a blank screen with a single cursor (and a concert of fans) will be the only thing you'll have; Note that this counts for ANY kind of Thunderbolt setting I set inside the BIOS, so likely to be a Grub/EFI compatibility issue, but I have no more clue for now. With this kind of problems I think that writing this laptop is certified by Ubuntu seems ridiculous. I'm available for any kind of suggestions/proposal you have. [1] https://certification.ubuntu.com/hardware/201906-27150 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1398424] Re: Double characters on inactive terminal
Problem is still present on Ubuntu 20.04 LTS, workaround (setting "none" as input method) still fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1398424 Title: Double characters on inactive terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1398424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876741] [NEW] Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
Public bug reported: Hey everyone, just upgraded to 20.04 in my Lenovo X1 Carbon laptop and found myself in really big troubles. I always started my laptop pressing the power button and then closing the laptop lid, because I'm using an external HDMI display. This worked always well with Ubuntu 19.10. With 20.04 the system crash. These are the actions that reproduce the problem: 1 - Boot the system, pressing the power button and closing the laptop lid with an external HDMI display attached to the laptop; 2 - See on the external HDMI display the boot progress: BIOS loading and then grub not appearing; 3 - Listen to the fans that are about to make the laptop lift; 4 - Press the power button to force off the laptop; At this point the only way to have everything back is: 1 - Detach any external device; 2 - Detach the power cable; 3 - Wait 3 seconds or more; 4 - Open the laptop lid; 5 - Attach the power cable; 6 - Press the power button; Without doing exactly as I written the laptop will not boot up, even if I force power off, after starting it again, after the BIOS display, the screen goes blank and the fans lift. NOTE 1: I already disabled secure boot in the BIOS, and also selected discrete graphics for the display (otherwise I'm not able to even start X); NOTE 2: the scenario is exactly the same with nvidia-driver-435 and nvidia-driver-440; NOTE 3: if I leave the laptop lid open, everything is just fine; ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-28-generic 5.4.0-28.32 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rasca 2750 F pulseaudio /dev/snd/controlC1: rasca 2750 F pulseaudio /dev/snd/controlC0: rasca 2750 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 16:24:47 2020 InstallationDate: Installed on 2019-12-10 (146 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=c61df9cc-bd36-4ed2-8f52-de114bbf3fc3 ro rd.driver.blacklist=nouveau RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET43W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET43W(1.30):bd03/24/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal hdmi nvidia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hey Dennis, the value you put in RESUME variable must match your logical volume path. /dev/vg_system/lv_swap matches mine, but yours might be different. Check with lvdisplay what is the name of your logical volume and then use it inside the resume file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Just as an additional confirmation, having the full LVM device path inside /etc/initramfs-tools/conf.d/resume like: RESUME=/dev/vg_system/lv_swap and running: sudo update-initramfs -u fixed the issue (also) for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
