| Summary: | plymouth with option --wait does not unlock the termios structure | ||
|---|---|---|---|
| Product: | plymouth | Reporter: | Raymond Wooninck <tittiatcoke> |
| Component: | general | Assignee: | Ray Strode [halfline] <rstrode> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | a.mv, bigon, david, matthias, rstrode |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | Fix boot_vga problem with framebuffer devices | ||
|
Description
Raymond Wooninck
2014-01-14 04:04:54 UTC
I was running into this bug as well as some others. After reading over bug 80553 comment 8, I patched ply-device-manager.c so that it does not call device_is_for_local_console() and always assigns a terminal. Once I did that, this is no longer an issue. So, I think it is safe to say that the root cause of this bug is plymouth not having a terminal assigned to the seat that it uses. *** Bug 66260 has been marked as a duplicate of this bug. *** Created attachment 110567 [details] [review] Fix boot_vga problem with framebuffer devices Hi!
We also ran into that bug recently at Tanglu, and the attached patch fixes this issue by detecting VGA framebuffers correctly.
The same patch is applied by OpenSUSE as well, the original author seems to be Stephan Kulow (per OpenSUSE change history).
Maybe this is something to be considered for upstream inclusion?
Cheers,
Matthias
that patch isn't going to work as it, because it's going to make devices that aren't being used, show up as being for the local console (will break optimus, multi-seat, etc) I agree this issue is serious and needs to be fixed soon, though. Ah, thanks for(In reply to Ray Strode [halfline] from comment #5) > that patch isn't going to work as it, because it's going to make devices > that aren't being used, show up as being for the local console (will break > optimus, multi-seat, etc) I agree this issue is serious and needs to be > fixed soon, though. Ah, thanks for that information - it's could to know that we fixed a problem by creating new problems for different users :-/ Unfortunately, I lack the knowledge to correctly fix this problem for all users, but if there's anything I can help with, just tell me. Cheers, Matthias -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/plymouth/plymouth/issues/8. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.