Bug 997052 - when console is rotated splash screen is not
Summary: when console is rotated splash screen is not
Status: REOPENED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Cliff Zhao
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-02 09:53 UTC by Michal Suchanek
Modified: 2019-07-11 12:05 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Suchanek 2016-09-02 09:53:53 UTC
Hello,

I boot with

GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/system/swap splash=silent quiet showopts console fbcon=rotate:3"

This can be detected by parsing the commandline or examining 

/sys/class/graphics/fbcon/rotate (3)
and 
/sys/class/graphics/fb0/rotate (0)

which should be more reliable should the console get rotated automagically by some other script.
Comment 1 Cliff Zhao 2017-02-13 12:14:03 UTC
Michal:

Thanks for the bug report. 
With option "fb=rotate:3", the console will rotate pretty fine.
But I still confuse about Is there anything indicats that plymouth splash will rotate together ?
I mean any fate or some thing shows upstream support this before ?
:-)
Comment 2 Michal Suchanek 2017-02-13 12:26:05 UTC
Does there have to be?

It's stupid that console rotates and plymouth does not.

You even get prompts as part of plymouth so they better be the correct orientation.
Comment 3 Cliff Zhao 2017-02-20 04:42:46 UTC
Yes, It's not the best result, And I also like it to rotate together with the console.
but we should notice, this will depends on kernel's strategy (will always support "fb=rotate" option in future).
At same time, other distribution also have this problem, which means it will not reduce our product competitiveness.
So I will deal with Plymouth crash problems first, after that, I will turn back to this issue.
And for sure, it must be resolved.
Comment 4 Tomáš Chvátal 2018-04-17 13:33:33 UTC
This is automated batch bugzilla cleanup.

The openSUSE 42.2 changed to end-of-life (EOL [1]) status. As such
it is no longer maintained, which means that it will not receive any
further security or bug fix updates.
As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
openSUSE, or you can still observe it under openSUSE Leap 15.0, please
feel free to reopen this bug against that version (see the "Version"
component in the bug fields), or alternatively open
a new ticket.

Thank you for reporting this bug and we are sorry it could not be fixed
during the lifetime of the release.

[1] https://en.opensuse.org/Lifetime
Comment 5 Michal Suchanek 2018-04-17 14:55:27 UTC
no change
Comment 6 Tomáš Chvátal 2019-07-11 11:05:57 UTC
This is automated batch bugzilla cleanup.

The openSUSE 42.3 changed to end-of-life (EOL [1]) status. As such
it is no longer maintained, which means that it will not receive any
further security or bug fix updates.
As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
openSUSE (At this moment openSUSE Leap 15.1, 15.0 and Tumbleweed) please
feel free to reopen this bug against that version (!you must update the
"Version" component in the bug fields, do not just reopen please), or
alternatively create a new ticket.

Thank you for reporting this bug and we are sorry it could not be fixed
during the lifetime of the release.

[1] https://en.opensuse.org/Lifetime
Comment 7 Michal Suchanek 2019-07-11 12:05:17 UTC
Not 42.3 specific