[Bug 985481] New: home:embar-:Lietukas/systemd-check-x-failed-service: interferes with 1st boot process after installation
http://bugzilla.opensuse.org/show_bug.cgi?id=985481 Bug ID: 985481 Summary: home:embar-:Lietukas/systemd-check-x-failed-service: interferes with 1st boot process after installation Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: opensuse.lietuviu.kalba@gmail.com Reporter: sb56637@gmail.com QA Contact: opensuse-communityscreening@forge.provo.novell.com Found By: --- Blocker: --- Hello, I use your excellent systemd-check-x-failed.service on many openSUSE spins that I generate with SuseStudio. It always works for all hardware that I've tried with the live USB. However, after system installation, it appears to interfere with the YaST 1st boot configuration screen, causing an infinite loop of checking for failed X. After a hard power-off and reboot, X comes up correctly. Is there a way to make systemd-check-x-failed.service only run from the live session and then de-activate it on the installed system? Thanks a lot! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=985481 http://bugzilla.opensuse.org/show_bug.cgi?id=985481#c1 --- Comment #1 from Mindaugas Baranauskas <opensuse.lietuviu.kalba@gmail.com> --- I did not noticed this behavior. What openSUSE version (as bese for appliance) you use? Does loop exist with every hardware or only some graphics cards? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=985481 http://bugzilla.opensuse.org/show_bug.cgi?id=985481#c2 --- Comment #2 from S. B. <sb56637@gmail.com> --- It appears to be more common with Radeon graphics, but I have also experienced it with Intel integrated graphics. Please let me know if there's anything else I can do to help debug. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=985481 http://bugzilla.opensuse.org/show_bug.cgi?id=985481#c3 --- Comment #3 from Mindaugas Baranauskas <opensuse.lietuviu.kalba@gmail.com> --- Does this bug exist for openSUSE Tumbleweed based appliances? Or also for Leap / 13.*? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=985481 http://bugzilla.opensuse.org/show_bug.cgi?id=985481#c4 --- Comment #4 from Mindaugas Baranauskas <opensuse.lietuviu.kalba@gmail.com> --- How do you know, that it is caused by this package? (e.g. removing it fixed problem?) If this is TW, see https://lists.opensuse.org/opensuse-factory/2016-06/msg00306.html : since some persons with one of recent TW saw something similar... Maybe there is too low disk space? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=985481 http://bugzilla.opensuse.org/show_bug.cgi?id=985481#c5 --- Comment #5 from S. B. <sb56637@gmail.com> --- It is kind of a random occurrence. I assumed it was systemd-check-x-failed-service because it was alternating in an infinite loop between "Checking to see if X failed to start" (something like that) and other services. I'll try to take better notes the next time I see it happen. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com