Me too see the same problem with 64-bit Jaunty (9.04). usplash comes up
with stretched graphics on widescreen display.
--
(Widescreen) 16:9 themes not being selected
https://bugs.launchpad.net/bugs/125690
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am having this issue too in Jaunty (9.04) and have been seeing it
since 8.04, so it obviously haven't been fixed! My screen is a 1280x800
screen (laptop) but there is no option for that resolution in StartUp-
manager. I then tried forcing the resolution by manually altering the
/etc/usplash.conf
This is now fixed, we have plenty of themes for different resolutions:
usplash-theme-ubuntu (0.22) jaunty; urgency=low
* debian/control: Add Vcs-Bzr: header.
* Merge from ubuntu-art-pkg branch:
- Final artwork for Jaunty.
- Ship the logo in three sizes only, instead of one full
tonic, is this bug a duplicate of #258999 or #64147? There seems to be
some confusion over the stretched logo issue, the main problem seems to
be that many resolutions are neither 4:3 or 16:9.
What is your resolution. Are you sure it is a theme selection issue?
--
(Widescreen) 16:9 themes not
If I make a usplash theme with only a 16:9 option and a screen setup for
a 16:9 resolution (I have a crt which works with any resolution put to
it) the usplash does not display. I add a 4:3 option and the usplash
then displays with stretched graphics.
--
(Widescreen) 16:9 themes not being
It is still a problem. I've been running intrepid for a while and only
just gotten usplash working again, v86d issues, anyway...
I have set my resolution in /etc/usplash.conf to the widescreen option
1680x1050, and have also tried 1920x1200, 1920x1080 and 640x400. I then
modified the ubuntustudio
Still a problem
** Changed in: usplash (Ubuntu)
Status: Invalid = New
--
(Widescreen) 16:9 themes not being selected
https://bugs.launchpad.net/bugs/125690
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
** Changed in:
