[Bug 1853369] [NEW] [19.10] Boot hangs at "loading initial ramdisk"
Public bug reported: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 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 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB 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) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Laptop Lock: Not Present Version: Not Specified Serial Number: 5QRHRF2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Laptop Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSBC1 Internal Connector Type: None External Reference Designator: USB TYPEC External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0007, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JHDMI1 Internal Connector Type: None External Reference Designator: HDMI External Connector Type: Other Port Type: Video Port Handle 0x0008, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JCR Internal Connector Type: None External Reference Designator: CARD READER External Conne
Re: [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
I did an upgrade to day from 19.04 -> 19.10 -> 20.04 and now the system still hangs. Tried all bios settings suggested in this thread. I'll try the grub fix, from David Wilson, but disco packages is not available anymore. I would say that this bug should have status updated. On Tue, May 19, 2020 at 5:20 AM John Nelson <1853...@bugs.launchpad.net> wrote: > Ran into this today applying a mass set of updates to an 18.04 system > that was last updated sometime last year. Running on a 2007 iMac. > > Apple hasn't made firmware updates for this model in years -- and > firmware updates require MacOS installed anyway AFIAK -- so that > approach is closed to me. > > That said, David Wilson's workaround at #7 above worked perfectly. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1853369 > > Title: > [19.10] Boot hangs at "loading initial ramdisk" > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions > -- Mvh -fredrik-normann- Sent from my Gmail Account -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
@zeorin Thanks for that info. I had to do the following extra. Since I use LUKS encrypted disk and uefi. 1) Open the encrypted disk in File explorer 2) Mount the lvm partition on /mnt mount /dev/ubuntu-vg/root /mnt Mount boot mount /dev/nvme0n1p2 /mnt/boot Mount efi mount /dev/nvme0n1p1 /mnt/boot/efi Standard chroot mounts mount --bind /proc /mnt/proc mount --bind /dev /mnt/dev mount --bind /sys /mnt/sys mount --bind /run /mnt/run <-- This was not listed. Then chroot into /mnt After adding the new apt sources and pinning the grub version and 'apt update && apt upgrade' I had to manually install 'grub2-common'. It did not install by default with 'apt upgrade'. After this was done. I ran update-grub and grub-install. With efi mounted this worked and I could reboot with old working grub. This is bug needs to be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
I think this is related to suspend. If I reboot my computer, and pair my headset, I get sound. when I suspend my computer and try to turn on the bluetooth connection I get the error message dmesg. Ubuntu 17.04 did not have this problem, but 17.10 and 18.04 has. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748565 Title: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1748565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
[27656.334177] usb 1-7: USB disconnect, device number 5 [27712.841243] usb 1-7: new full-speed USB device number 11 using xhci_hcd [27712.990551] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b [27712.990556] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [27712.993366] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015 [27712.994365] Bluetooth: hci0: Device revision is 16 [27712.994367] Bluetooth: hci0: Secure boot is enabled [27712.994369] Bluetooth: hci0: OTP lock is enabled [27712.994370] Bluetooth: hci0: API lock is enabled [27712.994372] Bluetooth: hci0: Debug lock is disabled [27712.994375] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [27712.994850] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi [27714.572396] Bluetooth: hci0: Waiting for firmware download to complete [27714.572400] Bluetooth: hci0: Firmware loaded in 1543294 usecs [27714.572517] Bluetooth: hci0: Waiting for device to boot [27714.584421] Bluetooth: hci0: Device booted in 11674 usecs [27714.584469] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc [27714.587439] Bluetooth: hci0: Applying Intel DDC parameters completed [27719.936384] Bluetooth: hci0: last event is not cmd complete (0x0f) [27735.811353] Bluetooth: hci0: last event is not cmd complete (0x0f) [27751.680367] Bluetooth: hci0: last event is not cmd complete (0x0f) [27766.592465] Bluetooth: hci0: advertising data len corrected [27769.863398] Bluetooth: hci0: last event is not cmd complete (0x0f) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748565 Title: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1748565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597466] Re: dpkg giving warning about '/etc/lsb-release' version number not starting with a digit when there is no apparent problem in the file
Saw this today: sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: base-files libmozjs-52-0 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 5,946 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 base-files amd64 10.1ubuntu2.2 [58.2 kB] Get:2 http://security.ubuntu.com/ubuntu bionic-security/main amd64 libmozjs-52-0 amd64 52.9.1-0ubuntu0.18.04.1 [5,887 kB] Fetched 5,946 kB in 1s (4,039 kB/s) (Reading database ... 337169 files and directories currently installed.) Preparing to unpack .../base-files_10.1ubuntu2.2_amd64.deb ... Warning: Stopping motd-news.service, but it can still be activated by: motd-news.timer Unpacking base-files (10.1ubuntu2.2) over (10.1ubuntu2.1) ... Setting up base-files (10.1ubuntu2.2) ... Installing new version of config file /etc/update-motd.d/50-motd-news ... motd-news.service is a disabled or a static unit, not starting it. (Reading database ... 337169 files and directories currently installed.) Preparing to unpack .../libmozjs-52-0_52.9.1-0ubuntu0.18.04.1_amd64.deb ... Unpacking libmozjs-52-0:amd64 (52.9.1-0ubuntu0.18.04.1) over (52.8.1-0ubuntu0.18.04.1) ... Setting up libmozjs-52-0:amd64 (52.9.1-0ubuntu0.18.04.1) ... Processing triggers for install-info (6.5.0.dfsg.1-2) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.3-1ubuntu7) ... update-initramfs: deferring update (trigger activated) Processing triggers for cracklib-runtime (2.9.2-5build1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2) ... Processing triggers for plymouth-theme-kubuntu-text (1:18.04ubuntu11) ... dpkg: warning: version '/etc/lsb-release' has bad syntax: version number does not start with digit rmdir: failed to remove '/lib/plymouth/': No such file or directory update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.130ubuntu3.2pop3) ... update-initramfs: Generating /boot/initrd.img-4.15.0-32-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597466 Title: dpkg giving warning about '/etc/lsb-release' version number not starting with a digit when there is no apparent problem in the file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1597466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000
17.10 and this shows up in syslog: Oct 23 10:32:43 normann kernel: [16449.935879] ieee80211 phy0: Hardware restart was requested Oct 23 10:33:04 normann kernel: [16470.892551] iwlwifi :03:00.0: regular scan timed out Oct 23 10:33:04 normann kernel: [16470.893902] iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x200. Oct 23 10:33:04 normann kernel: [16470.894261] iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 23 10:33:04 normann kernel: [16470.894267] iwlwifi :03:00.0: Status: 0x0200, count: 6 Oct 23 10:33:04 normann kernel: [16470.894271] iwlwifi :03:00.0: Loaded firmware version: 31.532993.0 Oct 23 10:33:04 normann kernel: [16470.894275] iwlwifi :03:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN Oct 23 10:33:04 normann kernel: [16470.894279] iwlwifi :03:00.0: 0x002002F2 | trm_hw_status0 Oct 23 10:33:04 normann kernel: [16470.894283] iwlwifi :03:00.0: 0x | trm_hw_status1 Oct 23 10:33:04 normann kernel: [16470.894286] iwlwifi :03:00.0: 0x0002484C | branchlink2 Oct 23 10:33:04 normann kernel: [16470.894289] iwlwifi :03:00.0: 0x0003936E | interruptlink1 Oct 23 10:33:04 normann kernel: [16470.894293] iwlwifi :03:00.0: 0x2BB4 | interruptlink2 Oct 23 10:33:04 normann kernel: [16470.894296] iwlwifi :03:00.0: 0x | data1 Oct 23 10:33:04 normann kernel: [16470.894300] iwlwifi :03:00.0: 0x0080 | data2 Oct 23 10:33:04 normann kernel: [16470.894303] iwlwifi :03:00.0: 0x0783 | data3 Oct 23 10:33:04 normann kernel: [16470.894307] iwlwifi :03:00.0: 0x20802E9C | beacon time Oct 23 10:33:04 normann kernel: [16470.894310] iwlwifi :03:00.0: 0xEC6AC168 | tsf low Oct 23 10:33:04 normann kernel: [16470.894313] iwlwifi :03:00.0: 0x022E | tsf hi Oct 23 10:33:04 normann kernel: [16470.894317] iwlwifi :03:00.0: 0x | time gp1 Oct 23 10:33:04 normann kernel: [16470.894320] iwlwifi :03:00.0: 0x012F924B | time gp2 Oct 23 10:33:04 normann kernel: [16470.894324] iwlwifi :03:00.0: 0x0001 | uCode revision type Oct 23 10:33:04 normann kernel: [16470.894327] iwlwifi :03:00.0: 0x001F | uCode version major Oct 23 10:33:04 normann kernel: [16470.894330] iwlwifi :03:00.0: 0x00082201 | uCode version minor Oct 23 10:33:04 normann kernel: [16470.894334] iwlwifi :03:00.0: 0x0230 | hw version Oct 23 10:33:04 normann kernel: [16470.894337] iwlwifi :03:00.0: 0x00C89000 | board version Oct 23 10:33:04 normann kernel: [16470.894340] iwlwifi :03:00.0: 0x0058019C | hcmd Oct 23 10:33:04 normann kernel: [16470.894344] iwlwifi :03:00.0: 0x22F22000 | isr0 Oct 23 10:33:04 normann kernel: [16470.894347] iwlwifi :03:00.0: 0x00804000 | isr1 Oct 23 10:33:04 normann kernel: [16470.894350] iwlwifi :03:00.0: 0x08001802 | isr2 Oct 23 10:33:04 normann kernel: [16470.894353] iwlwifi :03:00.0: 0x00400080 | isr3 Oct 23 10:33:04 normann kernel: [16470.894357] iwlwifi :03:00.0: 0x | isr4 Oct 23 10:33:04 normann kernel: [16470.894360] iwlwifi :03:00.0: 0x0058019C | last cmd Id Oct 23 10:33:04 normann kernel: [16470.894363] iwlwifi :03:00.0: 0x | wait_event Oct 23 10:33:04 normann kernel: [16470.894367] iwlwifi :03:00.0: 0xA7E1 | l2p_control Oct 23 10:33:04 normann kernel: [16470.894370] iwlwifi :03:00.0: 0x1C22 | l2p_duration Oct 23 10:33:04 normann kernel: [16470.894374] iwlwifi :03:00.0: 0x | l2p_mhvalid Oct 23 10:33:04 normann kernel: [16470.894377] iwlwifi :03:00.0: 0x00F0 | l2p_addr_match Oct 23 10:33:04 normann kernel: [16470.894380] iwlwifi :03:00.0: 0x000D | lmpm_pmg_sel Oct 23 10:33:04 normann kernel: [16470.894384] iwlwifi :03:00.0: 0x15062149 | timestamp Oct 23 10:33:04 normann kernel: [16470.894387] iwlwifi :03:00.0: 0x00340818 | flow_handler Oct 23 10:33:04 normann kernel: [16470.894582] iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 23 10:33:04 normann kernel: [16470.894586] iwlwifi :03:00.0: Status: 0x0200, count: 7 Oct 23 10:33:04 normann kernel: [16470.894590] iwlwifi :03:00.0: 0x0070 | ADVANCED_SYSASSERT Oct 23 10:33:04 normann kernel: [16470.894593] iwlwifi :03:00.0: 0x | umac branchlink1 Oct 23 10:33:04 normann kernel: [16470.894597] iwlwifi :03:00.0: 0xC0086950 | umac branchlink2 Oct 23 10:33:04 normann kernel: [16470.894600] iwlwifi :03:00.0: 0xC008C17E | umac interruptlink1 Oct 23 10:33:04 normann kernel: [16470.894603] iwlwifi :03:00.0: 0xC00842BC | umac interruptlink2 Oct 23 10:33:04 normann kernel: [16470.894607] iwlwifi :03:00.0: 0x0800 | umac data1 Oct 23 10:33:04 normann kernel: [16470.894610] iwlwifi :03:00.0: 0xC00842BC | umac data2 Oct 23 10:33:04 normann kernel: [16470.894613] iwlwifi :03:00.0: 0xDEADBEEF | umac data3 Oct 23 10:33:04 normann kernel: [16470.894617] iwlwifi :03:00.0: 0x001F | umac major Oct 23 10:33:04 normann kernel: [16470.894620] iwlwifi :
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
I encountered this bug when doing a do-release-upgrade. Unable to boot. If I update now, will kernel 5.3.0-24-generic be used? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944121] [NEW] removing packages in installer crashed
Public bug reported: Installer crashed. Was sent here to report bug. It happend in the final stage of removing packages not needed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 14:20:14 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944121 Title: removing packages in installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1944121] Re: removing packages in installer crashed
Hi,
It was some trouble with the disk. Please close.
Regards,
-fredrik-
On Tue, Sep 21, 2021 at 10:20 AM Sebastien Bacher <
1944...@bugs.launchpad.net> wrote:
> Thank you for your bug report, the log has repetitions of
>
> 'Sep 20 12:20:16 ubuntu kernel: [ 908.880196] ata3.00: configured for
> UDMA/100
> Sep 20 12:20:16 ubuntu kernel: [ 908.880209] ata3: EH complete
> Sep 20 12:20:16 ubuntu kernel: [ 908.892826] ata3.00: exception Emask 0x0
> SAct 0x0 SErr 0x4 action 0x0
> Sep 20 12:20:16 ubuntu kernel: [ 908.892833] ata3.00: irq_stat 0x4001
> Sep 20 12:20:16 ubuntu kernel: [ 908.892835] ata3: SError: { CommWake }
> Sep 20 12:20:16 ubuntu kernel: [ 908.892838] ata3.00: failed command:
> WRITE DMA EXT
> Sep 20 12:20:16 ubuntu kernel: [ 908.892840] ata3.00: cmd
> 35/00:50:c0:71:27/00:00:1a:00:00/e0 tag 20 dma 40960 out
> Sep 20 12:20:16 ubuntu kernel: [ 908.892840] res
> 51/04:50:c0:71:27/00:00:1a:00:00/e0 Emask 0x1 (device error)
> Sep 20 12:20:16 ubuntu kernel: [ 908.892846] ata3.00: status: { DRDY ERR }
> Sep 20 12:20:16 ubuntu kernel: [ 908.892848] ata3.00: error: { ABRT }'
>
> could you check your disk for errors?
>
> ** Changed in: ubiquity (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1944121
>
> Title:
> removing packages in installer crashed
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944121/+subscriptions
>
>
--
Mvh.
-fredrik-normann-
Sent from my Gmail Account
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944121
Title:
removing packages in installer crashed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944121/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
