[Bug 1975421] Re: Make Plymouth hide ALL messages on boot, reboot, halt. Plymouth ignores --no-boot-log flag
*** This bug is a duplicate of bug 1970069 *** https://bugs.launchpad.net/bugs/1970069 well i'm getting to the roots of this step by step.. but as far as i see it now i reported a bug where kernel parameters that set the loglevel are beeing ignored by system daemons that monitor the init process. the other bug is about plymouth not hiding these messages. so the headline of this bug should be corrected.. or.. i'll do another report that pinpoints the problem better because it's probaly not even a plymouth problem ? ** Description changed: - running a fresh install of kubuntu 22.04 + running a fresh install of kubuntu 22.04 plymouth version: 0.9.5+git20211018-1ubuntu3 + What should happen: + no bootmessages should be printed to console in the first place - What should happen: - Plymouth should totally cover all bootmessages (no bootmessages should be printed to console in the first place) + What actually happens: + When Plymouth quits the last 2-3 messages are visible - so some boot messages are printed to console never the less - What actually happens: - When Plymouth quits the last 2-3 messages are visible - - on shutdown i get: + on shutdown for example i get: [OK] Reached target Late Shutdown Services [OK] Finished System Power Off [OK] Reached target System Power off - - it seems to be absolutely impossible to hide all boot messages + it seems to be absolutely impossible to hide all boot messages i've done everything from this arch wiki site (and more) to get a silent boot: https://wiki.archlinux.org/title/silent_boot (this makes all acpi warnings and more go away.. but the [OK] reached/finished messages are not affected by those kernel parameters (this should also be fixed) - My Kernelparameters: - fbcon=nodefer rd.systemd.show_status=false vt.global_cursor_default=0 quiet splash loglevel=3 rd.udev.log_level=3 + My Kernelparameters:quiet splash fbcon=nodefer rd.systemd.show_status=0 + systemd.show_status=0 vt.global_cursor_default=0 loglevel=0 + rd.udev.log_level=0 udev.log_level=0 rd.systemd.log_level=0 + systemd.log_level=0 - - What part of the system throws these messages ? i thought it is systemd? + What part of the system throws these messages ? + i thought it is systemd? so i even edited files in /usr/lib/systemd/system in order to set the StandardOutput to null for all of the halt and reboot and plymouth scripts and i edited the plymouth start and stop scripts and added -no-boot-log but plymouth totally ignores this flag and still logs everything to console and to /var/log/boot.log - - this defies the whole purpose of plymouth if plymouth itself spams the console with messages and if it's systemd why doesn't it respect the kernel parameters + this defies the whole purpose of plymouth if plymouth itself spams the + console with messages and if it's systemd why doesn't it respect the + kernel parameters -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975421 Title: Make Plymouth hide ALL messages on boot, reboot, halt. Plymouth ignores --no-boot-log flag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1975421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975421] Re: Make Plymouth hide ALL messages on boot, reboot, halt. Plymouth ignores --no-boot-log flag
*** This bug is a duplicate of bug 1970069 *** https://bugs.launchpad.net/bugs/1970069 i'm quite sure that this is NOT a duplicate.. the other bug refers to some kernel upgrades that lead to error messages with acpi and usb devices in 22.04 (i also have these kernel messages but they are easily hidden with the kernel boot parameters i've mentioned above - especially loglevel=0) my bugreport says that even with all of these kernel parameters in place i still have the [OK] Finished ServiceXY messages. so they are related (because if plymouth would do it's job it wouldn't matter that those boot parameters are ignored) but they actually target two different problems also i believe that these messages (the ones i am talking about) aren't kernel messages but systemd or plymouth logs they are written to boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975421 Title: Make Plymouth hide ALL messages on boot, reboot, halt. Plymouth ignores --no-boot-log flag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1975421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975421] [NEW] Make Plymouth hide ALL messages on boot, reboot, halt. Plymouth ignores --no-boot-log flag
Public bug reported: running a fresh install of kubuntu 22.04 plymouth version: 0.9.5+git20211018-1ubuntu3 What should happen: Plymouth should totally cover all bootmessages (no bootmessages should be printed to console in the first place) What actually happens: When Plymouth quits the last 2-3 messages are visible on shutdown i get: [OK] Reached target Late Shutdown Services [OK] Finished System Power Off [OK] Reached target System Power off it seems to be absolutely impossible to hide all boot messages i've done everything from this arch wiki site (and more) to get a silent boot: https://wiki.archlinux.org/title/silent_boot (this makes all acpi warnings and more go away.. but the [OK] reached/finished messages are not affected by those kernel parameters (this should also be fixed) My Kernelparameters: fbcon=nodefer rd.systemd.show_status=false vt.global_cursor_default=0 quiet splash loglevel=3 rd.udev.log_level=3 What part of the system throws these messages ? i thought it is systemd? so i even edited files in /usr/lib/systemd/system in order to set the StandardOutput to null for all of the halt and reboot and plymouth scripts and i edited the plymouth start and stop scripts and added -no-boot-log but plymouth totally ignores this flag and still logs everything to console and to /var/log/boot.log this defies the whole purpose of plymouth if plymouth itself spams the console with messages and if it's systemd why doesn't it respect the kernel parameters ** Affects: plymouth (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/1975421 Title: Make Plymouth hide ALL messages on boot, reboot, halt. Plymouth ignores --no-boot-log flag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1975421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851123] Re: Ubuntu 19.10 and focal live cloned create and mount casper-rw partition
i just wanted do add than IMHO automatically mounting "anything" in live mode is the worst desgin decision ever and btw. it produces bugs beyond your imagination... for example: on an customized live image there is an instance of nginx running... in order to start nginx it checks if /var/log/nginx/error.log (and access.log) are available... now casper mounts "casper-rw" or "writable" into /var/log and those files are gone.. therfore nginx start fails.. this is true for a lot of other situations... i'm glad to here that i can "opt-out" but the linux way to such "features" would be "opt-in" so please make this optional !! thx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851123 Title: Ubuntu 19.10 and focal live cloned create and mount casper-rw partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489855] Re: Change to mount sequence order breaks persistence on casper-rw partitions
this is really disappointing... mount: mounting /cow on /root falied: invalid argument overlay mount failed i just changed the lines in /usr/share/initramfs-tools/scripts/casper and the live system booted without any problems... could you please finally fix this bug !! @seann-giffin i thought the same thing and therefore changed to ext2 - unfortunately it happens a lot that the flashdrives were removed in an unfortunate way ... we had a lot of filesystem errors... it seemed that ext4 was more healthy on the long run -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1489855 Title: Change to mount sequence order breaks persistence on casper-rw partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489855] Re: Change to mount sequence order breaks persistence on casper-rw partitions
well.. no.. if you change the squashfs file you replace the whole system.. you will then have ubuntu 14.04 and NOT 16.04 just use the information from post #14 (the path to the file in question) and replace the faulty version of the function setupunionfs() with the one i attached to post #15 glhf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1489855 Title: Change to mount sequence order breaks persistence on casper-rw partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489855] Re: Change to mount sequence order breaks persistence on casper-rw partitions
ok... i ran into this bug AGAIN and i was dumb enough to think that this would definitely be resolved by now (since the bugfix is already provided here) i lost hours with debugging until i finally realized that this bug is still there.. could you please fix this ? it's 2 minutes work ... copy and paste ! and casper is not usable in persistent mode.. this bug is critical ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1489855 Title: Change to mount sequence order breaks persistence on casper-rw partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489790] [NEW] syslinux install is broken on kubuntu 15.10 beta1
Public bug reported: syslinux -if /dev/sdb1 finishes fine but when starting the usb flashdrive it simply says boot error performing the same step on a 14.04 machine and the usb flashdrive is able to show me the syslinux options and boot properly. uname -a Linux wald 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:25:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux dpkg -l|grep syslinux ii syslinux 3:6.03+dfsg-8ubuntu2 -- using the start-disk-creator (usb-creator-kde) leads to the same result.. the created flashdrive doesn't boot. ** Affects: casper (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/1489790 Title: syslinux install is broken on kubuntu 15.10 beta1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489790] Re: syslinux install is broken on kubuntu 15.10 beta1
** Summary changed: - syslinux install is broken on kubuntu 15.10 alpha2 + syslinux install is broken on kubuntu 15.10 beta1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1489790 Title: syslinux install is broken on kubuntu 15.10 beta1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489855] [NEW] kubuntu 15.10 beta1 live usb drops to busybox with persistence PARTITION
Public bug reported: the system boots fine when using a casper-rw FILE but drops to a busybox when using a partition the short log would be: ___ Begin: Running /scripts/casper-premount ... done. done. umount: can't umount /cdrom: Device or resource busy Warning: Unable to find the persistent home medium umount: can't umount /cdrom: Device or resource busy Warning: Impossible to include the casper-sn Snapshot umount: can't umount /cdrom: Device or resource busy Warning: Impossible to include the home-sn Snapshot done. ___ removing the persistence keyword from the syslinux.cfg works and the live usb drive boots just fine. using a persistence file instead of the partition and the usb drive boots just fine. i found older bug reports concerning the same problem but the fix proposed in 2010 is already integrated into the script casper. so i started the flashdrive with the casper debug= option and i see the following (after probing several other devices it finally finds the right device and partition (sdb3) ___ + cow_backing_mp=/cdrom + [ -e /cdrom/casper-rw ] + umount /cdrom + sys2dev /sys/block/sdb/sdb3 + sysdev=/block/sdb/sdb3 + udevadm info -q name -p /block/sdb/sdb3 + echo /dev/sdb3 + devname=/dev/sdb3 + /sbin/blkid -s LABEL -o value /dev/sdb3 + [ casper-rw = casper-rw ] + echo /dev/sdb3 + return + cowprobe=/dev/sdb3 + [ -b /dev/sdb3 ] + cowdevice=/dev/sdb3 + get_fstype /dev/sdb3 + local FSTYPE + local FSSIZE + fstype + eval FSTYPE=ext4 FSSIZE=8458862592 + FSTYPE=ext4 FSSIZE=8458862592 + [ ext4 != unknown ] + echo ext4 + return 0 + cow_fstype=ext4 + cow_mountopt=rw,noatime + mount -t ext4 -o rw,noatime /dev/sdb3 /cow + [ ! -d /cow/upper ] + mkdir -p /cow/upper + continue + continue + mkdir -p /cow/work + [ -f /cow/format ] + [ DEFAULT = DEFAULT ] + modprobe -q -b overlay + grep -q ^overlay$ + cut -f2 /proc/filesystems + UNIONFS=overlay + break ___ this looks fine to me.. it looks like it recognizes everything .. it's ext4 .. label casper-rw.. it's mounting it... a little bit further down in the lng log file it states the following: __ + cow_backing_mp=/home-rw-backing + [ -e /home-rw-backing/home-rw ] + umount /home-rw-backing + sys2dev /sys/block/sdb/sdb3 + sysdev=/block/sdb/sdb3 + udevadm info -q name -p /block/sdb/sdb3 + echo /dev/sdb3 + devname=/dev/sdb3 + /sbin/blkid -s LABEL -o value /dev/sdb3 + [ casper-rw = home-rw ] + get_fstype /dev/sdb3 + local FSTYPE + local FSSIZE + fstype + eval FSTYPE=ext4 FSSIZE=8458862592 + FSTYPE=ext4 FSSIZE=8458862592 + [ ext4 != unknown ] + echo ext4 + return 0 + [ ext4 = vfat ] + homecow= + [ -b ] + [ n != y ] + log_warning_msg Unable to find the persistent home medium + _log_msg Warning: Unable to find the persistent home medium\n + [ n = y ] + printf Warning: Unable to find the persistent home medium\n Warning: Unable to find the persistent home medium __ a warning about the home medium is shown in both cases (file and partition) but the persistence file works never the less.. my system: kubuntu linux 15.10 beta1 uname -a Linux wald 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:25:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ** Affects: casper (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/1489855 Title: kubuntu 15.10 beta1 live usb drops to busybox with persistence PARTITION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384347] Re: _netdev not working
_netdev is not respected in fstab for cifs mounts in 13.04 raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/384347 Title: _netdev not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/384347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577302] Re: ubiquity crashes with error: InstallStepError: Plugin usersetup failed with code 32
unfortunately the patch fails on all my installations ob kubuntu 12.04 .. 1 out of 3 hunks failed to apply... is it possible to fix this somehow on a live usb installaiton .. tell the system to mount /dev/ first.. or use the /preseed/custom.seed file to seed those random numbers ?? this error totally blocks the bootprocess on some machines for up to 5 minutes.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/577302 Title: ubiquity crashes with error: InstallStepError: Plugin usersetup failed with code 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/577302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
