The usplash package has been superseded by plymouth and has been removed
from the Ubuntu archive. Closing all related bugs.
** Changed in: usplash (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Branch linked: lp:ubuntu/ubiquity
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
The splash screen is stretched on my monitor (1280x800)... usplash.conf
values are correctly set, but the splash image is still skewed... is
this a symptom of this problem?
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
You received this bug notification because you are
** Tags added: iso-testing
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
I just want to follow up, are there any status updates on probing
resolution at boot time for Intrepid?
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
** Changed in: usplash (Ubuntu)
Target: None => ubuntu-8.10
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Mike,
In response to your above comment, I am experiencing the same problem as
Åskar with the Hardy release candidate.
I did follow your directions ("sudo rm /etc/usplash.conf && sudo
aptitude reinstall usplash"), which resulted in my /etc/usplash.conf
changing to the following:
-
# Usplash
Hi Åskar, this issue should no longer exist in Hardy. Note the "Fix
Released" status. The patch will work fine for new users but for beta
users, the configuration file needs to be recreated. Have you followed
the instructions? The old configuration file needs to be deleted and
usplash must be reins
I can confirm this problem is still in latest hardy, upgraded yesterday
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Your xdpyinfo bug report seems to be mainly about the physical
dimensions of the screen; this code doesn't rely on that information.
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Alexander: the reason to use X tools is precisely so that we can take
advantage of the probing already done at X server startup. Yes, it does
require an X connection; this is a downside, but not an immediately
fatal one.
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
Yo
This bug was fixed in the package ubiquity - 1.8.2
---
ubiquity (1.8.2) hardy; urgency=low
[ Evan Dandrea ]
* Treat the dbfilter returning nonzero as a fatal error in the
noninteractive frontend.
* Clean up the reboot message in the noninteractive frontend.
* Optimize the
https://bugs.launchpad.net/bugs/201491
I am still unsure of using X tools though, don't these all require an X
connection? If we really have to probe and hardcode at configure time can we
not use non-X tools?
** Attachment added: "unnamed"
http://launchpadlibrarian.net/13193961/unnamed
--
p
Alexander: What's the bug number? That sounds like a serious issue that
should be fixed. There's really no reason why xdpyinfo shouldn't be
workable here - although ideally it might make sense to step through the
resolutions offered by xrandr until we find a VESA mode.
** Changed in: ubiquity (Ubu
On Tue, Apr 1, 2008 at 2:14 PM, Colin Watson <[EMAIL PROTECTED]> wrote:
> You have to be very careful when using ddcprobe; xresprobe used to have
> a slew of hardware-dependent hacks to avoid problems. I'm not
> comfortable with doing that for 8.04. It won't be necessary, either;
> although my f
Actually, according to Colin comments, it does not work correctly yet
when installing the computer with ubiquity, so further work is needed.
However, it won't work for the alternate CD for Hardy. The real solution
to that bug (automatic probing) will have to wait for Intrepid.
--
probe screen res
Thanks Colin, great work so far. After a "sudo rm /etc/usplash.conf &&
sudo aptitude reinstall usplash", it looks great.
I agree that this is probably sufficient for Hardy, however does this
only work with LiveCD installs? What about Wubi? It seems like most of
the people that couldn't fix this ma
You have to be very careful when using ddcprobe; xresprobe used to have
a slew of hardware-dependent hacks to avoid problems. I'm not
comfortable with doing that for 8.04. It won't be necessary, either;
although my first attempt at using xdpyinfo failed I'm confident I can
fix it.
--
probe screen
Is there something wrong with using ddcprobe in postinst (whether X is
running or otherwise)? Seems to work fine for me, and gives me more
information than I can shake a stick at with no interruptions to the
graphical output at all.
** Attachment added: "unnamed"
http://launchpadlibrarian.net/
Hmm, this still seems to fail within ubiquity, because usplash.postinst
doesn't have access to the X authorisation cookie. Drat.
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Cool, great work! Now it looks better, nice to have it centered!
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Warren Dumortier : The update fix the problem completely if you are
using X when installing usplash (so it will not work from the alternate
install CD). To test it, remove your /etc/usplash.conf and reinstall
usplash. You'll see that usplash now creates a /etc/usplash.conf file
that contains the go
I was there was an update but it still looks bad!
If I understeand your solution, it's the same as I said: keep 640x480 and make
the theme look better for 640x480, But could it look smaller/better, but I
think that is the work of the artwork team to make the theme, right?
--
probe screen resolu
Colin Watson : Thank you very much for your work on this. Tested here
and your update works perfectly, we can now keep this bug open for
Intrepid.
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags removed: qa-hardy-platform
--
probe screen resolution at boot
https://bugs.launchpad.net/bugs/188764
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
usplash (0.5.18) hardy; urgency=low
* Let usplash use the minimum mode in the theme if we don't know the
correct modes, rather than forcing 640x480.
* Fetch modes from the current display if we're being configured within X
(works around LP #188764).
-- Colin Watson <[EMAIL PROTECTED]
26 matches
Mail list logo
