Summary: | gensplash / fbsplash / splashutils freezes init in silent mode | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daniel Osborne <gentoo> |
Component: | Current packages | Assignee: | Michal Januszewski (RETIRED) <spock> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
.config
splash profile or successful case splash profile of unsuccessful case |
Description
Daniel Osborne
2009-01-04 18:57:08 UTC
Created attachment 177378 [details]
.config
Kernel config.
Created attachment 177381 [details]
splash profile or successful case
Created attachment 177383 [details]
splash profile of unsuccessful case
Forgot to mention: The splash always fades out, even though fadeout is not in /etc/conf.d/splash However, splash_manager doesn't ever fade, regardless of conf setting. Testing by using: splash_manager --cmd=demo -tnatural_gentoo Works correctly. If you can ssh to the machine while it appears to be frozen, could you please post the full process list (output of `ps axjH` or similar)? (In reply to comment #5) > If you can ssh to the machine while it appears to be frozen, could you please > post the full process list (output of `ps axjH` or similar)? > Odd. I reinstalled it and rebuilt the initramfs, and now it appears to be working correctly. I originally commented out the call to the fade function, since it was always calling it (to work around this issue). However I reinstalled it today, to reproduce the issue, and now it works. I did notice before that fbsplashd didn't exit afterwards. If X loaded, then hitting any key combination with F2 (ie, CTRL+F2) in it, switched to the splash screen. I'd also get errors during shutdown about the splash daemon already running. I added: echo exit > /lib/splash/cache/.splash to my /etc/conf.d/local, and that solved all my problems (didn't test with fade enabled though). I have since removed that line. I'll do some more testing tonight after work and let you know. Well, I'm not sure what changed on my system, but I'm not able to reproduce the issue anymore. Thanks for looking into it. Sorry I can't be more helpful. I'll post something if I can reproduce it again. I'm glad it's working properly for you now. Closing the bug as WORKSFORME. We can reopen it when someone comes up with a way to reproduce the problem. |