[Bug 125737] Re: Default /etc/lilo.conf options not optimal
I agree, how can something like a missing option be a hardware error? It's a hardware detection error and I guess more steps are needed in that hardware detection in order for lilo.conf to be complete. Maybe there should be three modes for LILO (or bootloader in general) installation: "Novice" mode should rely solely on autodection, "Intermediate" should allow turning some options off or on in a checkbox list (like aforementioned "prompt", "compact", "large-memory" etc) with a short explanation what does each option do, while "Expert" should allow manual editing of lilo.conf that will be deployed. PS: I can't believe this error (re)surfaced after one year and (almost) five months... -- Default /etc/lilo.conf options not optimal https://bugs.launchpad.net/bugs/125737 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32357] Re: Installer doesn't recognise SATA disks as primary.
I have a mixed SATA / ATA system and same thing happens. During the installation, it seems that the ATA drive was detected as hd0 and grub installed itself there. SATA were hd1, hd2. During the boot, grub detects SATA discs as hd0 and hd1, while ATA is hd2. I fixed it by re-doing the grub-install from the rescue console and editing /boot/grub/menu.lst to change every occurence of hd1 with hd0. Happened to me before, on Ubuntu 7.04. I'm really amazed it didn't get acknowledged/fixed so far. @ Simon Law: The problem is different detection of drives during the installation and after, ie. during the boot of the installed system. It has nothing to do with the hardware itself, rather than with (wild guessing) different kernel, different module loading/order and such from the installation disc compared to installed system. -- Installer doesn't recognise SATA disks as primary. https://bugs.launchpad.net/bugs/32357 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154469] vfat and ntfs partitions checked on every boot
Public bug reported: Binary package hint: base-installer vfat and ntfs partitions, automatically detected during the installation and thus automatically added to /etc/fstab, had fs_passno == 1 (sixth field) in /etc/fstab, which leads to fscking on every boot, slowing down the boot process. That field should be 0 for all fat/vfat partitions, according to man page for fstab. ** Affects: base-installer (Ubuntu) Importance: Undecided Status: New -- vfat and ntfs partitions checked on every boot https://bugs.launchpad.net/bugs/154469 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125737] Default /etc/lilo.conf options not optimal
Public bug reported: Binary package hint: lilo After the installation of Ubuntu 7.04 from the alternate CD, automatically populated /etc/lilo.conf didn't contain some, I believe in majority of cases, needed options. Those options include, but maybe are not limited to: "prompt" (without it, LILO just boots the specified default image, in this case "Linux". In case of multi-boot, this isn't acceptable) "compact" and/or "lba32" (without these options, loading of the kernel takes quite some time instead of 1-2 seconds. Both options when specified together, according to man page, may not work on all systems) "timeout" (when using "prompt", infinite wait time is not acceptable) ** Affects: lilo (Ubuntu) Importance: Undecided Status: New -- Default /etc/lilo.conf options not optimal https://bugs.launchpad.net/bugs/125737 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125730] vfat partition fscked on every boot
Public bug reported: Binary package hint: base-installer vfat partition, which was automatically detected during the installation of Ubuntu 7.04 from the alternate CD, has fs_passno == 1 (sixth field) in /etc/fstab, which leads to it being fscked on every boot. That field should be 0 for all fat/vfat partitions. ** Affects: base-installer (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: base-installer - vfat partition has fs_passno == 1 (sixth field) in /etc/fstab on newly - installed Ubuntu 7.04 which leads to it being fscked on every boot. + vfat partition, which was automatically detected during the installation + of Ubuntu 7.04 from the alternate CD, has fs_passno == 1 (sixth field) + in /etc/fstab, which leads to it being fscked on every boot. That field should be 0 for all fat/vfat partitions. -- vfat partition fscked on every boot https://bugs.launchpad.net/bugs/125730 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 108365] Re: Kubuntu upgrade tool (to 7.04 from 6.10) crashed
The solution is to install python-gpginterface package manually and restart the process: sudo apt-get install python-gnupginterface gksu "sh /cdrom/cdromupgrade" -- Kubuntu upgrade tool (to 7.04 from 6.10) crashed https://bugs.launchpad.net/bugs/108365 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for adept in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 125730] Re: vfat partition fscked on every boot
Still happens, even with Ubuntu 9.10! vfat partition was selected during installation to be mounted on /windows. fsck on boot couldn't check it, causing mounting to "contain errors", thus mounting root partition read-only... This scenario is even worse than previous, which was reported 2.5 years ago. ** Changed in: base-installer (Ubuntu) Status: Invalid => New -- vfat partition fscked on every boot https://bugs.launchpad.net/bugs/125730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125730] Re: vfat partition fscked on every boot
It was a fresh install on a different machine than before. When setting up partitions during the installation, I chose to use the preexisting FAT32 Windows partition as vfat, to be mounted on /windows. Installer put it in fstab, with "1" in the sixth field, causing it to be fscked (with the same priority?) as root partition. If fsck finds errors on vfat partition, Ubuntu will remount root read-only and stop booting. -- vfat partition fscked on every boot https://bugs.launchpad.net/bugs/125730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125730] Re: vfat partition fscked on every boot
Dear Anzenketh, Thank you for replying to the bug report. Please read the first post. It gives you the insight what is wrong, now, as well as 2.5 years ago. To quote fstab(5) man page: "The sixth field, (fs_passno), is used by the fsck(8) program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked." Why does vfat partition have "1" in that sixth field, given by Ubuntu installer, when obvious values for that field are either "0" or "2"? GNU/Linux fsck tools seem to fail on any vfat errors, so maybe "0" would be in order there, would it not? Because it gets checked and fails to be fixed, whole system stops booting right then and there, because root partition is to be remounted read-only on any errors encountered. I'm installing from the 9.10 LiveCD and yes, I'm installing to coexist with Windows (which is already installed); I know that there are better choices than vfat if you go 100% Windows-free. -- vfat partition fscked on every boot https://bugs.launchpad.net/bugs/125730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835838] [NEW] FTP/SFTP support missing because dar-static was compiled without libcurl support
Public bug reported: On Ubuntu Bionic (but using the dar-static package from Disco), dar_static v2.6.2-1 is compiled without libcurl support which effectively disables FTP/SFTP support, which is one of the main selling points of the DAR v2.6 branch $ dar_static -v -v -v -c ftp://example.org Final memory cleanup... Aborting program. The requested operation needs a feature that has been disabled at compilation time: libcurl library Please recompile libdar/dar with libcurl enabled and include the FTP/SFTP support. Thanks. ** Affects: dar (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/1835838 Title: FTP/SFTP support missing because dar-static was compiled without libcurl support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dar/+bug/1835838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666594] [NEW] package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Happened when installing proprietary drivers when booted from USB stick. ProblemType: Package DistroRelease: Ubuntu 10.10 Package: bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 AptOrdering: initramfs-tools: Configure bcmwl-kernel-source: Configure Architecture: i386 Date: Tue Oct 26 02:25:12 2010 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: bcmwl Title: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 maverick -- package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/666594 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666594] Re: package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/666594 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
