[Bug 1625358] Re: os-prober tries to mount bios_grub (BIOS boot) partition
My parted output for this partition is: Number Start End SizeFile system Name Flags 1 1049kB 8389kB 7340kB bios_grub bios_grub Ideally, the bios_grub flag could be used to tell relevant code (os- prober, apparently) to ignore this partition. That would eliminate 96 scary messages from my boot log. There are two disks on my system (for failover purposes), each with a bios_grub flag. Each one gets 48 of these useless messages. For some reason, os-prober is probing each disk multiple times. Since I monitor my logs closely, I'd love to have these go away. Log messages for one of the two disks appears below, just in case there's some new information in them. --- > Dec 21 05:26:46 samantha kernel: [1024918.757361] EXT4-fs (sda1): VFS: Can't > find ext4 filesystem -> Dec 21 05:26:46 samantha kernel: [1024918.762203] EXT4-fs (sda1): VFS: Can't find ext4 filesystem -> Dec 21 05:26:46 samantha kernel: [1024918.767102] EXT4-fs (sda1): VFS: Can't find ext4 filesystem -> Dec 21 05:26:46 samantha kernel: [1024918.771882] squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sda1 -> Dec 21 05:26:46 samantha kernel: [1024918.776705] FAT-fs (sda1): invalid media value (0x7d) -> Dec 21 05:26:46 samantha kernel: [1024918.776803] FAT-fs (sda1): Can't find a valid FAT filesystem -> Dec 21 05:26:46 samantha kernel: [1024918.791838] XFS (sda1): Invalid superblock magic number -> Dec 21 05:26:46 samantha kernel: [1024918.801632] FAT-fs (sda1): invalid media value (0x7d) -> Dec 21 05:26:46 samantha kernel: [1024918.801730] FAT-fs (sda1): Can't find a valid FAT filesystem -> Dec 21 05:26:46 samantha kernel: [1024918.815672] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sda1. -> Dec 21 05:26:47 samantha kernel: [1024918.843397] hfsplus: unable to find HFS+ superblock -> Dec 21 05:26:47 samantha kernel: [1024918.848163] qnx4: no qnx4 filesystem (no root dir). -> Dec 21 05:26:47 samantha kernel: [1024918.852787] ufs: You didn't specify the type of your ufs filesystem -> Dec 21 05:26:47 samantha kernel: [1024918.852787] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... -> Dec 21 05:26:47 samantha kernel: [1024918.852787] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old -> Dec 21 05:26:47 samantha kernel: [1024918.853511] ufs: ufs_fill_super(): bad magic number -> Dec 21 05:26:47 samantha kernel: [1024918.863201] hfs: can't find a HFS filesystem on dev sda1 -> Dec 21 05:26:47 samantha kernel: [1024919.062796] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem -> Dec 21 05:26:47 samantha kernel: [1024919.067520] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem -> Dec 21 05:26:47 samantha kernel: [1024919.072411] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem -> Dec 21 05:26:47 samantha kernel: [1024919.077055] squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sdb1 -> Dec 21 05:26:47 samantha kernel: [1024919.081806] FAT-fs (sdb1): invalid media value (0x7d) -> Dec 21 05:26:47 samantha kernel: [1024919.081904] FAT-fs (sdb1): Can't find a valid FAT filesystem -> Dec 21 05:26:47 samantha kernel: [1024919.097725] XFS (sdb1): Invalid superblock magic number -> Dec 21 05:26:47 samantha kernel: [1024919.107655] FAT-fs (sdb1): invalid media value (0x7d) -> Dec 21 05:26:47 samantha kernel: [1024919.107754] FAT-fs (sdb1): Can't find a valid FAT filesystem -> Dec 21 05:26:47 samantha kernel: [1024919.121471] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sdb1. -> Dec 21 05:26:47 samantha kernel: [1024919.126085] hfsplus: unable to find HFS+ superblock -> Dec 21 05:26:47 samantha kernel: [1024919.130815] qnx4: no qnx4 filesystem (no root dir). -> Dec 21 05:26:47 samantha kernel: [1024919.135241] ufs: You didn't specify the type of your ufs filesystem -> Dec 21 05:26:47 samantha kernel: [1024919.135241] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... -> Dec 21 05:26:47 samantha kernel: [1024919.135241] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old -> Dec 21 05:26:47 samantha kernel: [1024919.135996] ufs: ufs_fill_super(): bad magic number -> Dec 21 05:26:47 samantha kernel: [1024919.145351] hfs: can't find a HFS filesystem on dev sdb1 -> Dec 21 05:27:41 samantha kernel: [1024973.119969] EXT4-fs (sda1): VFS: Can't find ext4 filesystem -> Dec 21 05:27:41 samantha kernel: [1024973.124592] EXT4-fs (sda1): VFS: Can't find ext4 filesystem -> Dec 21 05:27:41 samantha kernel: [1024973.129261] EXT4-fs (sda1): VFS: Can't find ext4 filesystem -> Dec 21 05:27:41 samantha kernel: [1024973.133842] squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sda1 -> Dec 21 05:27:41 samantha kernel: [1024973.138461] FAT-fs (sda1): invalid media value (0x7d) -> Dec 21 05:27:41 samantha kernel: [1024973.138559] FAT-fs (sda1): Can't find a valid FAT filesystem -> Dec 21 05:27:41 samantha
[Bug 50093] Re: Some sysctl's are ignored on boot
*** This bug is a duplicate of bug 771372 *** https://bugs.launchpad.net/bugs/771372 This is still a problem in 16.04 LTS/xenial. I lost a whole workday chasing this down after an upgrade. I don't think it's a duplicate of 771372, as the above discussion indicates there is no "right" place to run procps, and 771372 works on that presumption. Instead, the start-up process needs to be reworked, or at least the network-related settings need to be reassigned to the network start-up process instead of living in procps. With the increased use of bridges (KVM, LXC, etc.), we should have a smooth start-up process for bridges and bridge-related settings. I confess I don't understand all the complexities others apparently see. We need someone that really understands the relevant start-up processes to architect a good solution. What can we do to get a little attention on this problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctl's are ignored on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610583] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-p
This happened when I was trying to change from Gnome to KDE. It asked me a question that made no sense to this totally inexperienced linux user, and I figured that I had a slightly better chance of being correct if I chose the first of the 2 options. It had something to do with windows [which I need for a few programs], and maybe network managers, but I'm not really sure. Here's what the terminal looked like when I typed the terminal command to install KDE again: brian@brian-XPS-8500:~$ sudo apt-get install kubuntu-desktop [sudo] password for brian: Reading package lists... Done Building dependency tree Reading state information... Done kubuntu-desktop is already the newest version (1.338). You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: kde-telepathy-minimal : Depends: kde-config-telepathy-accounts (>= 15.04.0) but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). brian@brian-XPS-8500:~$ apt-get -f install E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied) E: Unable to lock the administration directory (/var/lib/dpkg/), are you root? So I can't tell if this is a bug, or if I chose the wrong option when I tried to install KDE. As far as I can tell, I can't get into KDE, I've tried restarting and logging off. Please help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610583 Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package account- plugin-facebook 0.12+16.04.20160126-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kaccounts-providers/+bug/1610583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125628] Re: No spell check in the Subect field of new messages
This bug applies to 2.10.1-0ubuntu2 which is the latest version. -- No spell check in the Subect field of new messages https://bugs.launchpad.net/bugs/125628 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
