[Bug 801888] New: systemd-udev-trigger.service on boot kills plymouth
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c0 Summary: systemd-udev-trigger.service on boot kills plymouth Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: arvidjaar@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=523126) --> (http://bugzilla.novell.com/attachment.cgi?id=523126) debug log of plymouth User-Agent: Mozilla/5.0 (X11; Linux i686; rv:18.0) Gecko/20100101 Firefox/18.0 12.3 net install using build 0370 in qemu-kvm (default config, no hardware explicitly specified), using nomodeset. Booting in run-level 3 reliably leaves plymouth screen with half-finished anymation visible. Alt-F1 at this point works and shows login prompt. In plymouth debug log (attached) is seen that shortly after starting systemd-udev-trigger plymouth loses /dev/tty7. This is timing dependent, enabling plymouth tracing to terminal never shows this problem and different logs may show different systemd unit as the last one (and once using plymouth debug stream to memory I was able to boot normally). Unfortunately without systemd-udev-trigger systemd does not boot at all (/dev/disk/by-id missing) so I cannot verify it by disabling this service. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c Michal Hrusecky <mhrusecky@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com AssignedTo|bnc-team-screening@forge.pr |meissner@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c1 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com AssignedTo|meissner@suse.com |fcrozat@suse.com --- Comment #1 from Marcus Meissner <meissner@suse.com> 2013-02-21 14:14:03 UTC --- Why me? I did not do any of this code -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #523126|text/x-log |text/plain mime type| | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |rmilasan@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c2 Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |arvidjaar@gmail.com --- Comment #2 from Robert Milasan <rmilasan@suse.com> 2013-02-21 14:28:14 UTC ---
From where did you get build 0370?
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c3 Andrey Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|arvidjaar@gmail.com | --- Comment #3 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-02-21 15:29:42 UTC --- (In reply to comment #2)
From where did you get build 0370?
http://download.opensuse.org/factory/iso/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c4 Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #4 from Robert Milasan <rmilasan@suse.com> 2013-02-21 17:28:03 UTC --- Don't believe this is udev issue: linux-ivrs:~ # systemctl status plymouth-start.service plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static) Active: failed (Result: exit-code) since Thu, 2013-02-21 18:24:19 CET; 43s ago Process: 419 ExecStartPost=/usr/bin/plymouth --debug show-splash (code=exited, status=1/FAILURE) Process: 416 ExecStartPost=/sbin/udevadm settle --timeout=30 --exit-if-exists=/sys/class/graphics/fb0/dev (code=exited, status=0/SUCCESS) Process: 273 ExecStartPost=/sbin/udevadm settle --timeout=30 --exit-if-exists=/sys/class/drm/card0/dev (code=exited, status=0/SUCCESS) Process: 272 ExecStart=/usr/sbin/plymouthd --debug --mode=boot --pid-file=/run/plymouth/pid --no-daemon --attach-to-session (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/plymouth-start.service Feb 21 18:24:18 linux-ivrs.site plymouthd[272]: [main.c:1927] check_logging:logging will be enabled! Feb 21 18:24:18 linux-ivrs.site plymouthd[272]: [main.c:2224] initialize_environment:source built on 2013-02-06 15:34:47.000000000 +0000 Feb 21 18:24:18 linux-ivrs.site plymouthd[272]: [main.c:2243] initialize_environment:checking if '/dev/tty7' exists Feb 21 18:24:18 linux-ivrs.site plymouthd[272]: [main.c:2095] check_for_consoles:checking for consoles Feb 21 18:24:18 linux-ivrs.site plymouthd[272]: [main.c:1959] add_consoles_from_file:opening /sys/class/tty/console/active Feb 21 18:24:18 linux-ivrs.site plymouthd[272]: [main.c:1968] add_consoles_from_file:reading file Feb 21 18:24:18 linux-ivrs.site plymouthd[272]: [main.c:2015] add_consoles_from_file:console /dev/tty0 found! Feb 21 18:24:18 linux-ivrs.site plymouthd[272]: [main.c:2160] check_for_consoles:After processing serial consoles there are now 0 text displays Feb 21 18:24:18 linux-ivrs.site plymouthd[272]: [main.c:2169] redirect_standard_io_to_device:redirecting stdio to /dev/tty7 Feb 21 18:24:19 linux-ivrs.site plymouth[419]: [./ply-boot-client.c:189] ply_boot_client_connect:trying old fallback path /ply-boot-protocol Feb 21 18:24:19 linux-ivrs.site plymouth[419]: [./ply-boot-client.c:196] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused Feb 21 18:24:19 linux-ivrs.site plymouth[419]: [./plymouth.c:1195] main:daemon not running Feb 21 18:24:19 linux-ivrs.site plymouth[419]: [./ply-boot-client.c:830] ply_boot_client_detach_from_event_loop:detaching from event loop linux-ivrs:~ # systemctl status plymouth-read-write.service plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data Loaded: loaded (/usr/lib/systemd/system/plymouth-read-write.service; static) Active: inactive (dead) since Thu, 2013-02-21 18:24:19 CET; 57s ago Process: 336 ExecStart=/usr/bin/plymouth --debug update-root-fs --read-write (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/plymouth-read-write.service Feb 21 18:24:19 linux-ivrs.site plymouth[336]: [./ply-boot-client.c:188] ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: Connection refused Feb 21 18:24:19 linux-ivrs.site plymouth[336]: [./ply-boot-client.c:189] ply_boot_client_connect:trying old fallback path /ply-boot-protocol Feb 21 18:24:19 linux-ivrs.site plymouth[336]: [./ply-boot-client.c:196] ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection refused Feb 21 18:24:19 linux-ivrs.site plymouth[336]: [./plymouth.c:1195] main:daemon not running Feb 21 18:24:19 linux-ivrs.site plymouth[336]: [./ply-boot-client.c:830] ply_boot_client_detach_from_event_loop:detaching from event loop To be honest, don't really know what it means, but /dev/tty7 is there so no complains about that. @Frederic: do you know who suppose to maintain plymouth? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c5 --- Comment #5 from Robert Milasan <rmilasan@suse.com> 2013-02-21 20:44:14 UTC --- OK, found the issue: In /usr/lib/systemd/system/plymouth-start.service line: ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --no-daemon --attach-to-session should be: ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --no-daemon --attach-to-session meaning dropping option '--no-daemon'. Also, the /var/run issue that we have with systemd, is from plymouth, and the plymouth package is a totally disaster (meaning need cleaning). Will try to clean it up. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tittiatcoke@gmail.com InfoProvider|fcrozat@suse.com |tittiatcoke@gmail.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c6 --- Comment #6 from Robert Milasan <rmilasan@suse.com> 2013-02-22 10:07:40 UTC --- Already pushed the fixes in Base:System, someone should accept them: https://build.opensuse.org/request/show/156075 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c7 --- Comment #7 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-02-22 10:15:14 UTC --- (In reply to comment #6)
If you remove --no-daemon, you have to set service type to forking. Due to KillMode=none systemd ignores this instead of killing plymouthd right away, so I suspect this simply changes event timing without fixing the root cause. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c8 --- Comment #8 from Robert Milasan <rmilasan@suse.com> 2013-02-22 10:18:24 UTC --- I don't know, but tested this and works well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c9 --- Comment #9 from Robert Milasan <rmilasan@suse.com> 2013-02-22 10:26:53 UTC --- OK, modified the patch and set KillMode=process: https://build.opensuse.org/request/show/156078 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c10 --- Comment #10 from Robert Milasan <rmilasan@suse.com> 2013-02-22 10:39:36 UTC --- Sorry, wrong one: https://build.opensuse.org/request/show/156083 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|tittiatcoke@gmail.com | AssignedTo|rmilasan@suse.com |tittiatcoke@gmail.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c11 Raymond Wooninck <tittiatcoke@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |arvidjaar@gmail.com --- Comment #11 from Raymond Wooninck <tittiatcoke@gmail.com> 2013-02-24 11:33:48 UTC --- Did anybody tried this on a normal PC ? I mean not with a virtual machine ? At this moment I have adjusted the Plymouth packages in Base:System to get ride of /var/run/plymouth and move this to /run/plymouth. I have been trying to reproduce this issue on my own laptop with booting with "nomodeset init 3" specified on the kernel parameter line in grub, but then I see a non graphical plymouth splash (with the three green colored bars at the bottom of the screen and after a while I see automatically the login prompt appearing on tty1. And no trace of plymouth on tty7. Removing the nomodeset delivers the same end situation, but then with the graphical plymouth splash. @Andrey, maybe you could update your virtual machine with the plymouth packages from Base:System and see if this is already sufficient to resolve the issue ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c12 --- Comment #12 from Raymond Wooninck <tittiatcoke@gmail.com> 2013-02-24 11:38:44 UTC --- I also tried the same with the 12.3 RC1 Live CD and to boot there with nomodeset and init 3. The result is again the same. Bootsplash ends correctly and I am in a login prompt on tty1. I am using qemu-kvm as virtual machine. Am downloading now the KDE live CD build 370 to see what happens there. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c13 Andrey Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|arvidjaar@gmail.com | --- Comment #13 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-02-24 13:22:47 UTC --- (In reply to comment #11)
Did anybody tried this on a normal PC ? I mean not with a virtual machine ?
Nope. I will probably update my primary system after RC2 is out.
I have been trying to reproduce this issue on my own laptop with booting with "nomodeset init 3" specified on the kernel parameter line in grub, but then I see a non graphical plymouth splash
Then you do something differently because I see graphical splash. I just tested with pure text mode and indeed it boots correctly.
@Andrey, maybe you could update your virtual machine with the plymouth packages from Base:System and see if this is already sufficient to resolve the issue ?
Just tested and have the same problem 1. Install i586 12.3 RC1 NET ISO on 5GB qemu image using command qemu-img create /datastore/kvm/plymouth/hda.img 5g qemu-kvm -hda /datastore/kvm/plymouth/hda.img -m 768 -hdc /datastore/iso/openSUSE-12.3-NET-Build0024-i586.iso -boot d 2. On initial screen select 800x600 resolution, add "nomodeset" to kernel parameters, select LXDE graphical desktop. Accept everything else as default. 3. System is installed and rebooted into run-level 5. 4. Add "3" to kernel command line in grub.cfg, reboot. Stuck on splash screen. 5. Fetch current packages from Base:System (0.8.8_git201211022126-110.1), rpm -F, edit grub.cfg to add "3", reboot. Stuck on splash screen. 6. Edit grub.cfg to disable gfxterm entirely, boot with terminal in pure text mode console - boots OK. So the problem happens when you do have framebuffer console and use graphical pymouth slash screen. Still happens using up to day 12.3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c14 --- Comment #14 from Raymond Wooninck <tittiatcoke@gmail.com> 2013-02-24 14:11:51 UTC --- (In reply to comment #13)
(In reply to comment #11)
Then you do something differently because I see graphical splash. I just tested with pure text mode and indeed it boots correctly.
I have been using nomodeset and with everthing else default. It seems that choosing a graphic sizes somehow initializes the chip different and a graphical bootsplash is shown. What do you mean with pure text mode ? There is no pure text mode with plymouth. Plymouth can show details or can show a non-graphical bootsplash (the tri-colored green bar at the bottom of the screen). But in each case Plymouth is running in the background.
1. Install i586 12.3 RC1 NET ISO on 5GB qemu image using command
qemu-img create /datastore/kvm/plymouth/hda.img 5g qemu-kvm -hda /datastore/kvm/plymouth/hda.img -m 768 -hdc /datastore/iso/openSUSE-12.3-NET-Build0024-i586.iso -boot d
2. On initial screen select 800x600 resolution, add "nomodeset" to kernel parameters, select LXDE graphical desktop. Accept everything else as default.
3. System is installed and rebooted into run-level 5.
4. Add "3" to kernel command line in grub.cfg, reboot. Stuck on splash screen.
5. Fetch current packages from Base:System (0.8.8_git201211022126-110.1), rpm -F, edit grub.cfg to add "3", reboot. Stuck on splash screen.
6. Edit grub.cfg to disable gfxterm entirely, boot with terminal in pure text mode console - boots OK.
I am currently running these instructions to see where it will bring me. I will let you know what happens after these steps have completed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c15 --- Comment #15 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-02-24 14:33:24 UTC --- (In reply to comment #14)
I have been using nomodeset and with everthing else default. It seems that choosing a graphic sizes somehow initializes the chip different and a graphical bootsplash is shown.
Are you using grub or grub2?
What do you mean with pure text mode ? There is no pure text mode with plymouth. Plymouth can show details or can show a non-graphical bootsplash (the tri-colored green bar at the bottom of the screen). But in each case Plymouth is running in the background.
I mean non-graphical bootsplash. It *is* text mode as opposed to graphical framebuffer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c16 --- Comment #16 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-02-24 14:42:40 UTC --- (In reply to comment #13)
qemu-kvm -hda /datastore/kvm/plymouth/hda.img -m 768 -hdc /datastore/iso/openSUSE-12.3-NET-Build0024-i586.iso -boot d
Sorry, it should have been "-cdrom /datastore/iso/openSUSE-12.3-NET-Build0024-i586.iso", not -hdc. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c17 --- Comment #17 from Raymond Wooninck <tittiatcoke@gmail.com> 2013-02-24 14:54:31 UTC --- (In reply to comment #15)
(In reply to comment #14)
I have been using nomodeset and with everthing else default. It seems that choosing a graphic sizes somehow initializes the chip different and a graphical bootsplash is shown.
Are you using grub or grub2?
I am using the standard delivered, which means grub2. What are you using ? the old Grub ?
What do you mean with pure text mode ? There is no pure text mode with plymouth. Plymouth can show details or can show a non-graphical bootsplash (the tri-colored green bar at the bottom of the screen). But in each case Plymouth is running in the background.
I mean non-graphical bootsplash. It *is* text mode as opposed to graphical framebuffer.
Ok. Clear :-) Then we are talking about the same. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c18 --- Comment #18 from Raymond Wooninck <tittiatcoke@gmail.com> 2013-02-24 14:55:17 UTC --- (In reply to comment #16)
(In reply to comment #13)
qemu-kvm -hda /datastore/kvm/plymouth/hda.img -m 768 -hdc /datastore/iso/openSUSE-12.3-NET-Build0024-i586.iso -boot d
Sorry, it should have been "-cdrom /datastore/iso/openSUSE-12.3-NET-Build0024-i586.iso", not -hdc.
Ok, After the installation the bootloader failed to write its configuration, etc. I will retry the installation. Am normally using Virtualbox and not qemu :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c19 --- Comment #19 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-02-24 15:00:40 UTC --- (In reply to comment #17)
I am using the standard delivered, which means grub2. What are you using ? the old Grub ?
Nope, grub2. May be VB makes difference here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c20 --- Comment #20 from Raymond Wooninck <tittiatcoke@gmail.com> 2013-02-24 15:53:40 UTC --- Ok, I got now the same situation as you described with qemu. However it is not stuck as the splash-screen. Pressing Alt-F1 transfers me to the tty1 login prompt and then returning to tty7 shows no sign of the splash. I will try now to see if running without --no-daemon from within the initrd resolves this situation. Because that is where plymouth is started and not from systemd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c21 --- Comment #21 from Raymond Wooninck <tittiatcoke@gmail.com> 2013-02-24 15:56:23 UTC --- This is getting strange. If I now boot the virtual system again (after closing it) with qemu-kvm -hda /sources/kvm/plymouth/hda.img -m 768 -boot d then everything works fine. I am booting into runlevel 3 without issue -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c22 Raymond Wooninck <tittiatcoke@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |arvidjaar@gmail.com --- Comment #22 from Raymond Wooninck <tittiatcoke@gmail.com> 2013-02-25 07:00:18 UTC --- You might wonder what exactly I did that I now have the correct behavior. I guess that normally people would shutdown the virtual machine by issuing a shutdown from within. I didn't do this, but once the machine was in the login prompt, I closed the window by using the X in the top right. At this moment I don't know what this causes to the virtual machine, but plymouth is working now as it should. Grub.cfg in /boot/grub2.cfg contains the "3" and the machine boots into runlevel 3 and ends up nicely with the login prompt on tty1. It would be great if you could check this and see if this would make the virtual machine also work for you. If so, then I would assume that the bug is more caused by the virtual machine (and maybe related to the bugs that the images don't work in VirtualBox). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c23 Andrey Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|arvidjaar@gmail.com | --- Comment #23 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-02-25 17:31:39 UTC --- Yes, I cannot reproduce it now as well and recalling what I had done, I did close VM window instead of doing proper shutdown. I guess as long as it happens only in very special configuration it can be left alone. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c24 --- Comment #24 from Robert Milasan <rmilasan@suse.com> 2013-02-26 09:20:26 UTC --- OK, on physical machine there is no problem, plymouth behaves as it should, but in VirtualBox doesn't and in VirtualBox you can't do the same as in KVM, but I guess it might not be that important. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=801888 https://bugzilla.novell.com/show_bug.cgi?id=801888#c Raymond Wooninck <tittiatcoke@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|tittiatcoke@gmail.com |kigurame@opensuse.org -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com