[Bug 2054795] Re: Calamares - Installation failed - Bad main script file
Installing Kubuntu noble-desktop-amd64.iso as of 2024 March 05. Error says main.py but related to networking. Main script file /usr/lib/x86_64-linux- gnu/calamares/modules/networkcfg/main.py for python job networkcfg raised an exception. Graphics show Lubuntu during install before crash. Then desktop crashes both after install crash or with Try Kubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054795 Title: Calamares - Installation failed - Bad main script file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2054795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055726] Re: If Kubuntu installation fails, Plasma crashes when attempting to launch once Calamares quits
Crash occurs both with try Kubuntu and when installer crashes with this error Main script file /usr/lib/x86_64-linux-gnu/calamares/modules/networkcfg/main.py for python job networkcfg raised an exception Graphics during install are still Lubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055726 Title: If Kubuntu installation fails, Plasma crashes when attempting to launch once Calamares quits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2055726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950132] Re: Kubuntu Jammy Jellyfish daily-live test install crashes
*** This bug is a duplicate of bug 1951399 *** https://bugs.launchpad.net/bugs/1951399 Do not know login password when using installer. Its in an encrypted file in my main working install. Error posted: kubuntu@kubuntu:~$ ubuntu-bug ubiquity /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead. Latest ISO from Nov. 21. Booted using grub2's loopmount. Have to umount /isodevice or it crashes (all older versions were same). Used manual partitioning to reuse existing old install, changed (tried to) ESP from sda1 to sdb1, but had to umount /sda1 and mount sdb1 as ESP while on screen adding login info. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950132 Title: Kubuntu Jammy Jellyfish daily-live test install crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1950132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895490] Re: no destination host name is cups-browsed running
Same error. But changed printer from default to one with .local at end of name then worked. Not sure why hpcups 3.20.3 printer and driverless cups-filter 1.27.4 printer are also configured but do not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895490 Title: no destination host name is cups-browsed running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
Just installed Hirsute as of April 18,2021. hirsute-desktop-amd64.iso Same issue. I tried to use Ubiquity installer options to change where grub is installed and they did not work. Used grub2's loopmount to boot ISO. It mounts isodevice to NVMe drive but installer, when it asks to remove mounts does not remove it. I have to manually unmount it. Then it does not show mount of ESP on NVMe drive, but once past partitioning screen and saying not to use ESP on NVMe drive, it mounts ESP on NVMe drive. I have to check mounts during install process, unmount isodevice and unmount incorrect ESP and mount correct ESP. mount sudo umount -lrf /dev/nvme0n1p5 lsblk -f mount sudo umount /dev/nvme0n1p1 sudo mount /dev/sda1 /target/boot/efi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906256] Re: grub-install: error: cannot find EFI directory.
Windows requires MBR(msdos) partitioning for BIOS boot. Ubuntu will let you install in UEFI mode to MBR drive, but probably should not as Windows wants boot partition to be its partition with boot files (system), but UEFI wants boot flag on ESP - efi system partition. UEFI highly recommends gpt partitioning for UEFI, and Windows only installs in UEFI mode to gpt drives. Normal reinstall in different mode will erase drive. So if you attempt to reinstall Windows in UEFI mode, it will convert drive to gpt & totally erase drive. Or have good backups. Either reinstall Windows in UEFI mode since you have UEFI hardware. Microsoft has required vendors to install in UEFI mode to gpt partitioned drives since 2012 and release of Windows 8. Or only install Ubuntu in 40 year old BIOS/MBR configuration. How you boot install media, UEFI or BIOS is then how it installs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906256 Title: grub-install: error: cannot find EFI directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1906256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816296] Re: Unable to connect to dbus: Could not connect: Permission denied
Using focal Kubuntu. Firefox filling .xsession-errors Has pyqt5 (5.14.1+dfsg-3build1) focal; & current versions of other dbus related files that are standard. fred@z97-focal-kubuntu:~$ uname -a Linux z97-focal-kubuntu 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux fred@z97-focal-kubuntu:~$ echo $DESKTOP_SESSION plasma fred@z97-focal-kubuntu:~$ cat /etc/X11/default-display-manager /usr/bin/sddm fred@z97-focal-kubuntu:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" fred@z97-focal-kubuntu:~$ apt show firefox Package: firefox Version: 84.0+build3-0ubuntu0.20.04.1 ** (/usr/lib/firefox/firefox:112432): WARNING **: 09:37:31.184: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112483): WARNING **: 09:37:31.636: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112515): WARNING **: 09:37:31.830: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112540): WARNING **: 09:37:31.970: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112609): WARNING **: 09:37:33.138: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112734): WARNING **: 09:38:27.515: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112782): WARNING **: 09:38:27.981: Unable to connect to dbus: Could not connect: Permission denied ** (/usr/lib/firefox/firefox:112833): WARNING **: 09:38:28.518: Unable to connect to dbus: Could not connect: Permission denied -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816296 Title: Unable to connect to dbus: Could not connect: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-gtk-module/+bug/1816296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875166] Re: grub-efi-amd64.postinst not running grub-install when GRUB_DISTRIBUTOR changed
Running Kubuntu 20.04.1 and changed distributor. Did not create folder nor add new UEFI entry. It did update /EFI/ubuntu with new dates on files. sudo dpkg-reconfigure grub-efi-amd64-signed fred@z97-focal-kubuntu:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" fred@z97-focal-kubuntu:~$ echo $DESKTOP_SESSION plasma GRUB_DISTRIBUTOR=kubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875166 Title: grub-efi-amd64.postinst not running grub-install when GRUB_DISTRIBUTOR changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1875166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877861] Re: When installing grub to multiple EFI partitions they all have the same label in the EFI vars
Similar: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1450783 And: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1450783 And: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1561712 I do change /etc/default/grub and get new entry in UEFI. GRUB_DISTRIBUTOR=kubuntu But it always uses /EFI/ubuntu/grub.cfg to boot not /EFI/kubuntu/grub.cfg. But a different entry in UEFI. Or you can create an entry like shown in Bug above with grub-install --bootloader-id=myid or just in UEFI with efibootmgr and different description.Entry in UEFI uses GUID/partUUID to know which ESP to boot from. Most systems only allow one active ESP per device, but once configured, you may be able to use any FAT32 partition with .efi boot files. If in different ESP, then any of the options to create a different id should work, but you may need /EFI/ubuntu folder in ESP 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/1877861 Title: When installing grub to multiple EFI partitions they all have the same label in the EFI vars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1877861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
Now also applies to Groovy. Tried to install test version of Groovy into HDD. Did not want defaults in NVMe SSD changed, so during Something Else install changed combo box to sda, told it not to use ESP on NVMe drive, use ESP on sda. Also told it not to use swap and it did not use swap, but used ESP on NVMe drive. At name & password screen had to change mount /dev/sda8 on /target type ext4 (rw,relatime,errors=remount-ro) /dev/nvme0n1p1 on /target/boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) ubuntu@ubuntu:~$ sudo umount /dev/sda8 umount: /target: target is busy. ubuntu@ubuntu:~$ sudo umount /dev/nvme0n1p1 ubuntu@ubuntu:~$ sudo mount /dev/sda1 /target/boot/efi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861004] Re: Using loopback command crashes grub on 19.10
Duplicat of https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861004 Title: Using loopback command crashes grub on 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1861004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826159] Re: gsd-print-notifications assert failure: free(): invalid pointer
I seem to be getting both IPv4 & IPv6 with same hostname, so then printer does not connect. I turned off IPv6 and now it works, but have to release it every time. sudo nano /etc/cups/cups-browsed.conf Changed to use only IPv4 # IPBasedDeviceURIs IPv4 IPBasedDeviceURIs IPv4 fred@fred-Z170N-focal:~$ apt show cups Package: cups Version: 2.3.1-9ubuntu1 Priority: optional https://github.com/OpenPrinting/cups-filters/issues/22 https://github.com/lathiat/avahi/issues/125 ** Bug watch added: github.com/OpenPrinting/cups-filters/issues #22 https://github.com/OpenPrinting/cups-filters/issues/22 ** Bug watch added: github.com/lathiat/avahi/issues #125 https://github.com/lathiat/avahi/issues/125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826159 Title: gsd-print-notifications assert failure: free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1826159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826159] Re: gsd-print-notifications assert failure: free(): invalid pointer
May be related to this bug as printing issues started with it. https://bugs.launchpad.net/ubuntu/+source/ippusbxd/+bug/1866838 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826159 Title: gsd-print-notifications assert failure: free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1826159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764860] Re: dbus crashed with SIGABRT in _dbus_abort()
Just had this error in 20.04. But may be related to this already reported: [Bug 1866838] [NEW] ippusbxd crashed with SIGSEGV in usb_conn_acquire() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764860 Title: dbus crashed with SIGABRT in _dbus_abort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1764860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799213] Re: Gtk-CRITICAL gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Posts twice about every 10 seconds. fred@fred-Z170N-focal:~$ echo $DESKTOP_SESSION gnome-flashback-metacity fred@fred-Z170N-focal:~$ gnome-shell --version GNOME Shell 3.34.3 fred@fred-Z170N-focal:~$ lsb_release -d Description:Ubuntu Focal Fossa (development branch) Feb 9 11:13:31 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Feb 9 11:13:31 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Feb 9 11:13:31 fred-Z170N-focal nm-applet[1680]: Can't set a parent on widget which has a parent Feb 9 11:13:41 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Feb 9 11:13:41 fred-Z170N-focal nm-applet[1680]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799213 Title: Gtk-CRITICAL gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1799213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155216] Re: Unable to umount isodevice
Same error with 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/1155216 Title: Unable to umount isodevice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1155216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1435414] Re: cups-browsed assert failure: *** Error in `/usr/sbin/cups-browsed': corrupted double-linked list: 0x0000000000e0a7a0 ***
Error in Focal. Shows my printer twice in system settings, printers. HP ENVY 4500 series hp:/usb/ENVY_4500_series?serial=CN49Q1206R05X4 HP Envy 4500 Series, hpcups 3.19.12 implicitclass://HP_ENVY_4500_series_845FC1_/ HP ENVY 4500 series, driverless, cups-filters 1.26.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1435414 Title: cups-browsed assert failure: *** Error in `/usr/sbin/cups-browsed': corrupted double-linked list: 0x00e0a7a0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1435414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855531] Re: Installation - partition manager is breaking
For me I forced the unmount of /dev/sda5 which is where /isodevice mounted. sudo umount -lrf /isodevice Similar issue: https://askubuntu.com/questions/1157619/install-cannot-modify-hard-disk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855531 Title: Installation - partition manager is breaking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1855531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855531] Re: Installation - partition manager is breaking
Similar issue with Ubiquity 20.04.3 as of Dec 7, 2019. Installing to sdb, asked it to unmount sda partitions, but it said it could not unmount sda5 where isodevice is mounted. Selected to not use ESP on sda, but use ESP on sdb, unselected swap on sda & swap on sdb. Install to sdb12, format and use as ext4 & use as /. Lots of warnings & error messages GtkBox does not have a child property XDG_RUNTIME_DIR (/run/user/999) is not owned by us (uid 0) Gtk-CRITICAL gtk_widget_set .. failed /usr/lib/ubiquity/plugins/ubi-usersetup.py:372: Warning: Source ID 12889 was not found when attempting to remove it GLib.source_remove(self.hostname_timeout_id) Gdk-Message: 13:41:25.443: ubiquity: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** Attachment added: "Full debug" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1855531/+attachment/5310568/+files/debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855531 Title: Installation - partition manager is breaking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1855531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] [NEW] Grub 2.04 Out of memory error, No server error
Public bug reported:
Trying to loop mount ISO.
Installed grub 2.04 to flash drive in UEFI mode from 19.10
Flash drive does not boot and gives Out of memory error & no server error. Must
load kernel first.
Re-installed grub from 18.04 to same flash drive using same boot stanza.
Booted without issue.
>From 18.04
fred@Bionic-Z170N:~$ grub-install -V
grub-install (GRUB) 2.02-2ubuntu8.13
from 19.10
fred@fred-Z170N-eoan:~$ grub-install -V
grub-install (GRUB) 2.04-1ubuntu12
Boot stanza that works in 2.02 but not in 2.04
menuentry "Focal Live ISO" {
set isofile="/ISO/focal-desktop-amd64.iso"
loopback loop (hd0,1)$isofile
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile toram
noeject
initrd (loop)/casper/initrd
}
** Affects: grub2 (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/1851311
Title:
Grub 2.04 Out of memory error, No server error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847898] Re: System doesn't boot after installation - Legacy mode / 2 disks
Related bugs: Ubuntu Installer uses wrong bootloader location for USB/sdb UEFI installs https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1173457 Posted work around to manually unmount & mount correct ESP during install https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379 https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1229488 https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1229488 EFI doesn't show multiple installs of the same operating system https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1561712 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847898 Title: System doesn't boot after installation - Legacy mode / 2 disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1847898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849534] [NEW] ISO extracted to FAT32 does not support links error
Public bug reported: Attempting to extract ISO to FAT32 partition for UEFI install which used to work. But get error that FAT32 does not support links. Found these links: fred@Bionic-Z170N:/media/fred/Ubuntu 20.04 LTS amd64$ find . -type l -ls 2761 0 lr-xr-xr-x 1 fred fred5 Oct 18 20:36 ./dists/stable -> focal 2765 0 lr-xr-xr-x 1 fred fred5 Oct 18 20:36 ./dists/unstable -> focal 1330 0 lr-xr-xr-x 1 fred fred1 Oct 18 20:36 ./ubuntu -> . ** Affects: ubuntu-meta (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/1849534 Title: ISO extracted to FAT32 does not support links error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1849534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist
At this point better to start a thread on Ubuntu forums. https://ubuntuforums.org/forumdisplay.php?f=339 Already many similar questions and answers. Also from live installer: Please copy & paste link to the Boot-info summary report ( do not post report), the auto fix sometimes can create more issues. https://help.ubuntu.com/community/Boot-Repair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675079 Title: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
Also applies to Cosmic, Disco & Eoan. Never been fixed. Just installed Debian Buster to see how it handled grub. I did not select an ESP and it told me to go back and choose a partition as /efi/boot. I choose sdb's ESP and it installed without issue to ESP on sda, and did not overwrite my Ubuntu boot in sda. It did make Buster first in UEFI boot order, but my Ubuntu was second in UEFI boot order & Buster's grub2 os-prober found all my other install, so I could boot them. Probably will use Debian's version of grub since it works, even to boot my Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
Noted that target is not mounted until sometime after partitioning screen in Something Else. I unmounted & remounted after adding user & password, but before continuing after that screen. Also install still used original ESP in fstab. I had to go back & change fstab from sda's ESP to external drive or any second drive's ESP to have correct entry in fstab. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
