Description of problem: Back/Next buttons off bottom of screen. GDM and normal X are fine, nothing chopped off the bottom of them. Am running rawhide from 12/9, with modesetting ati. Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. When it loads on first boot 2. Or... touch /etc/reconfigSys, edit /etc/sysconfig/firstboot, chkconfig firstboot on Actual results: Next/Back buttons off bottom of screen Expected results: Able to see Next/Back buttons Additional info:
adding to blocker... new F10 feature
Does this machine run at some unusual resolution? Can you attach a picture of the display?
Laptop screen, 1920x1200 native resolution. Any tips on getting a screenshot from firstboot?
*** Bug 463943 has been marked as a duplicate of this bug. ***
I'm getting the same behaviour on a Thinkpad T60p with a 1600x1200 resolution screen. If you mean a real photo, I might be able to get one tonight.
A real photo would be fine.
Created attachment 317725 [details] Screenshot Screenshot from firstboot
As you can see from the screenshot, it thinks my screen is square! xdpyinfo agrees: screen #0: dimensions: 1920x1920 pixels (508x508 millimeters) For some reason gdm and gnome run fine, not off the bottom of the screen?!
Yes, that would definitely be the problem. I'm not doing anything special in firstboot to start up X anymore, so this shouldn't be my bug. The /tmp/firstbootX.log file might be helpful in debugging what's going wrong here.
Created attachment 317729 [details] /tmp/firstbootX.log
Created attachment 317783 [details] photo of firstboot screen on T60p (screen 1600x1200) Here is a photo of one of the first boot screens on my T60p (screen size 1600x1200). I have a couple other photos, but they all are missing the bottom buttons, just like this one.
However... looking at the logfile although initially it thinks the screen is 1920x1920, it then resizes it to 1920x1200 (correct). GDM & GNOME seems to be fine with this... but firstboot not.
Seems to be fixed in the Snap1 version, although the graphical experience is not always first rate. I'm getting a ... Assuming cache write through message that interrupts the graphical sequence.
Fixed for me in snap1 too, closing...