| Summary: | booting up Mageia 6 and 7 RC spits out OK boot message lines twice, duplicated | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dieter Rogiest <dieter.rogiest> |
| Component: | RPM Packages | Assignee: | Base system maintainers <basesystem> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | gm2.asp, lewyssmith, marja11, nicolas.bachelet1, ouaurelien |
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | sytemd (, plymouth?) | CVE: | |
| Status comment: | |||
| Attachments: |
output as root of journalctl -ab after a clean boot
duplicated OK line messages.jpg duplicated OK line messages2.jpg |
||
Created attachment 11122 [details]
output as root of journalctl -ab after a clean boot
Dieter > when I boot up Mageia I see it spit out all OK boot message lines twice, > duplicated. Where do you see these duplicated messages? In a normal bootup, they are 'hidden' by the splash screen. Are you making them visible explicitly? Are you talking of what you see on the screen? For in the journal output you attach (thank you for this) I see at first sight nothing duplicated there. When booting Mageia, different versions over many years, I have never seen duplicated [OK] console lines. Are you saying that each and every one of those is duplicated? If not, what exactly? > Am I the only one annoyed by that? > I can't find a bug report on it on bugzilla. This does suggest it is not a common problem. Whiteboard:
(none) =>
NEEDINFO [marja@cldrn64 ~]$ grep OK attachment.cgi\?id\=11122 Jun 22 19:13:39 vat.bier.somewhere fedora-storage-init[717]: Setting up Logical Volume Management: [ OK ] Jun 22 19:13:39 vat.bier.somewhere fedora-storage-init[748]: Setting up Logical Volume Management: [ OK ] Jun 22 19:13:45 vat.bier.somewhere partmon[1011]: Checking if partitions have enough free diskspace: [ OK ] Jun 22 19:13:46 vat.bier.somewhere resolvconf[996]: Starting resolvconf: [ OK ] Jun 22 19:13:49 vat.bier.somewhere network[1165]: Bringing up loopback interface: [ OK ] Jun 22 19:13:49 vat.bier.somewhere network[1165]: Bringing up interface enp0s8: [ OK ] Jun 22 19:13:51 vat.bier.somewhere network-up[953]: Waiting for network to be up[ OK ] Jun 22 19:13:51 vat.bier.somewhere routed[1631]: Starting routed (RIP) services: [ OK ] Jun 22 19:13:53 vat.bier.somewhere ifplugd(enp0s8)[1404]: client: [ OK ] Jun 22 19:14:33 vat.bier.somewhere postfix[1948]: Starting postfix: [ OK ] [marja@cldrn64 ~]$ Lewis is right, there are no duplicated OK lines in the log. Even the first two OKs aren't the same, because the process ID is different. It would be nice to have a screenshot or a video if you see real duplicates during boot up. CC:
(none) =>
marja11 Lewis, Marja,
yes the boot line messages are normally hidden, but regularly I hit 'ESC' to show them because in the past (a few years ago) I had some failures I needed to investigate and sometimes when it takes too long I want to see if it's busy fscking one of my partitions.
In Attachment 2 [details] pictures of my monitor while booting.
On "duplicated OK line messages2.jpg" you will see that they get duplicated: sometimes the second line is a few lines below the first one like "Started Update UTMP about System Boot/Shutdown."Whiteboard:
NEEDINFO =>
(none) Created attachment 11132 [details]
duplicated OK line messages.jpg
Created attachment 11133 [details]
duplicated OK line messages2.jpg
(In reply to my own comment from comment #4) > In Attachment 2 [details] pictures of my monitor while booting. Funny, if you put the words "Attachment" and "2" after each other they show a link to the second attachment on this bugzilla. I meant to say In Attachment there are 2 pictures of my monitor while booting. Thank you for these screenshots; they certainly prove your point. The second one (messages2.jpg) is interesting in that it shows the reversion from duplicated to single [OK] messages; this might help pin in down. Because you are the first person to bug this, it does imply something special about your system. @Marja: Needs your greater wisdom where to push this. My guess is that Dieter is using the proprietary nvidia driver. I have seen this duplication of lines since at least MGA5. I don't see it with Nouveau and Intel drivers. CC:
(none) =>
gm2.asp Arne, nope, I changed today from proprietary nvidia driver to nouveau (via MCC > Hardware > Set up the graphical server) and rebooted (had to do reboot in konsole) and booted with nouveau: the duplicate boot message lines were still there. I used commands lspci -nnk | grep -iA2 vga and glxinfo to verify I was using nouveau. So I have now changed back to nvidia display driver. Don't pressure yourselve into solving this. I have no problem living with the idea that I have a rare issue with my computer that has only a minor severity. I've got other itches to scratch (from the venomous hairs of oak processionary moths) I wasted my Sunday afternoon on this but I did find a solution (sort of): I am not the only one: Fedora 25: https://forums.fedoraforum.org/showthread.php?313020-Each-service-runs-twice-while-booting-Fedora-25 but someone's solution there I don't think will work for me as I don't have sp5100_tco in the output of lsmod Then there is https://forums.opensuse.org/showthread.php/533190-Boot-statements-twice/page2?s=b846fffa01cebbfc3b9ee163bb5b178e There I found how to get non duplicated OK boot lines: set your kernel options without "splash". Then it boots up without duplicate OK lines, but also without the splash screen. So it seems that with splash as a kernel option, when you hit ESC the boot messages appear but the OK ones show up duplicated. I guess there must be a bug in the splash section in the source code of plymouth. That thread on opensuse forum first states to remove a symlink plymouth-start.service from /usr/lib/systemd/system/sysinit.target.wants because there is already such a symlink in /usr/lib/systemd/system/initrd-switch-root.target.wants but that is an unnecessary chicken dance. So the only thing I know how to get non duplicated OK boot lines is: in MCC > Boot > Set up boot system > on the append options, remove the "splash", reboot and there you have it. But also no splash screen. (or maybe follow https://wiki.mageia.org/en/How_to_set_up_kernel_options#With_Grub_2_boot_Loader_3 : remove splash from etc/default/grub and run update-grub (I didn 't try this)) HI Dieter, Thanks for the workaround and for the links. Good luck recovering from nature's recent gift to you. @ Lewis I'll assign to the base system maintainers. It might be an upstream issue, though. Source RPM:
(none) =>
sytemd (, plymouth?) Hi, I confirm the same behavior in both versions 6 and 7: double boot messages when hitting the ESC key in thé splash screen. Tried the nosplash workaround in MagieIA7 successfully. Thanks CC:
(none) =>
nicolas.bachelet1 As Dieter pointed out, my guess that duplicated lines occurred only with the proprietary nvidia driver was wrong. It turned out that the difference between an installation (using proprietary driver) that did have duplicated lines and another installation (on the same machine, but using Nouveau) that didn't was the installation media used. The former was installed from the MGA 6 classical ISO (and kept up to date), while the latter was installed from the MGA 6.1 Live Plasma ISO. Installations made from the MGA 6.1 Live ISO apparently do not have duplicated lines. Unfortunately, the same does not apply to the MGA 7 Live Plasma ISO. On my side, I have an Intel Mobile 4 Series Chipset (integrated one on a laptop) using Intel 810 and later module. Regarding installation, as far as I can remember (so I can be wrong), I installed a fresh 6.0 from the DVD ISO, then updated the distribution and upgraded yesterday to 7.0 from the network within the OS loaded. Hope this helps. As this sounds like a cosmetic issue, it is not a priority, fortunately, services are not started twice at once (as I have seen for a user of another distribution). This message is a reminder that Mageia 6 is end of life. Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL). Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 6's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot be able to fix it before Mageia 6 was end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad Status:
NEW =>
RESOLVED |
Since ages (I think since first Mageia's) when I boot up Mageia I see it spit out all OK boot message lines twice, duplicated. Even Mag7 RC does this. Am I the only one annoyed by that? I can't find a bug report on it on bugzilla. I guess there are of course much more urgent boot bugs than this. inxi -b System: Host: vat.bier.somewhere Kernel: 4.18.20-desktop-1.mga6 x86_64 (64 bit) Desktop: KDE Plasma 5.12.2 Distro: Mageia 6 mga6 Machine: Device: desktop Mobo: Gigabyte model: M55S-S3 v: x.x BIOS: Award v: F6 date: 03/20/2007 CPU: Dual core AMD Athlon 64 X2 5600+ (-MCP-) speed: 2800 MHz (max) Graphics: Card: NVIDIA G80 [GeForce 8800 GTS] Display Server: Mageia X.org 119.5 drivers: nvidia,v4l Resolution: 1920x1080@60.00hz GLX Renderer: GeForce 8800 GTS/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 340.106 Network: Card: NVIDIA MCP55 Ethernet driver: forcedeth Drives: HDD Total Size: 1900.4GB (75.5% used) Info: Processes: 232 Uptime: 9 min Memory: 2282.6/3946.1MB Client: Shell (bash) inxi: 2.3.11 Also attached the output as root of journalctl -ab after a clean boot.