This bug was assigned to usplash, but from the description I think this must be a bug in xsplash; usplash is run before X starts, and I think is incapable of interacting with TwinView settings whatsoever since that pertains to X settings - usplash simply starts full screen on the primary kernel framebuffer.
This bug was assigned to usplash, but from the description I think this must be a bug in xsplash; usplash is run before X starts, and I think is incapable of interacting with TwinView settings whatsoever since that pertains to X settings - usplash simply starts full screen on the primary kernel framebuffer.