[Bug 188764] Re: probe screen resolution at boot

2011-03-23 Thread Phillip Susi
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 Ubuntu.
https://bugs.launchpad.net/bugs/188764

Title:
  probe screen resolution at boot

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2010-02-22 Thread Launchpad Bug Tracker
** 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.com/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2009-04-02 Thread Julian Lam
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-07-08 Thread Ubuntu QA Website
** 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/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-07-07 Thread Mike Rooney
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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-05-07 Thread Saïvann Carignan
** 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.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-04-23 Thread Pete Stephenson
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 configuration file
# These parameters will only apply after running update-initramfs.

xres=1280
yres=800
-

1280x800 is the proper resolution for my monitor. Previously the
/etc/usplash.conf resolution was 1024x768, which resulted in an oddly
stretched splash screen.

However, even with usplash set to that 1280x800 and update-initramfs
being properly updated, the splash screen is now off-center and oddly
distorted. I set it back to 1024x768, as it's at less distorted.

-- 
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/mailman/listinfo/ubuntu-bugs

[Bug 188764] Re: probe screen resolution at boot

2008-04-17 Thread Mike Rooney
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 reinstalled, as stated above. See my previous post for
instructions. Let me know if the issue still persists after following
the instructions.

-- 
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/mailman/listinfo/ubuntu-bugs

[Bug 188764] Re: probe screen resolution at boot

2008-04-17 Thread Åskar
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@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-04-14 Thread Colin Watson
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 subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-04-14 Thread Colin Watson
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
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/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-04-07 Thread Launchpad Bug Tracker
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 md5 check on file copy (LP: #198019).
  * Copy the locale over to the target system when using oem-config.
This was previously fixed for the alternate CD in LP 181291.
  * Use + instead of : for a replacement character for m-a as it is
explicitly allowed by debconf policy.
  * Break out of resizing the partition in cases where partman fed us bad
boundary values (LP: #197838).
  * Don't miscalculate with nested partitions in 03partition_too_small (LP:
#198039).
  * Automatic update of included source packages: apt-setup
1:0.31ubuntu7, choose-mirror 2.19ubuntu5, clock-setup 0.92ubuntu3,
console-setup 1.21ubuntu6, localechooser 1.42ubuntu4, migration-
assistant 0.6.1, partman-auto 73ubuntu7, tzsetup 1:0.20.

  [ Mario Limonciello ]
  * Don't unnecessarily hardcode the return of get_hostname()
in the noninteractive frontend.
  * Turn off console blanking in Ubiquity init script to prevent
confusion on the noninteractive frontend.
  * Update mythbuntu ubiquity icon.

  [ Colin Watson ]
  * Fix crash if partitioning failed when partitioning was automated (see LP
#206113).
  * Remove packages in the restricted section from the installed system if
apt-setup/restricted is false.
  * Fix crash with the "don't use" partitioning option (LP: #132611).
  * Use localised, human-readable names for partitioning methods.
  * Reorganise the wrapper script to cope with kdesu's broken argument
handling.
  * Add a "Format the partition?" checkbox to the partition edit dialog
(LP: #184838).
  * Give reconfigured packages access to our X display, so that
usplash.postinst can check its dimensions (LP: #188764).

 -- Evan Dandrea <[EMAIL PROTECTED]>   Tue, 08 Apr 2008 02:02:23 -0400

** Changed in: ubiquity (Ubuntu)
   Status: In Progress => Fix Released

-- 
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/mailman/listinfo/ubuntu-bugs


Re: [Bug 188764] Re: probe screen resolution at boot

2008-04-07 Thread Alexander Jones
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

-- 
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/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-04-07 Thread Colin Watson
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 (Ubuntu)
 Assignee: (unassigned) => Colin Watson (kamion)
   Status: Won't Fix => In Progress

-- 
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/mailman/listinfo/ubuntu-bugs


Re: [Bug 188764] Re: probe screen resolution at boot

2008-04-01 Thread Alexander Jones
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 first attempt at using xdpyinfo failed I'm confident I can
>  fix it.

xdpyinfo is giving me bogus details about the size of my screen right
now, even though radeon driver detects everything correctly (according
to X log), ddcprobe detects everything correctly and xrandr detects
everything correctly. xdpyinfo is the only one getting it wrong -- I'd
be careful of that, too! (There is a bug open for this.)

-- 
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/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-04-01 Thread Saïvann Carignan
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 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/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-04-01 Thread Mike Rooney
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 manually would be coming from the
LiveCD or Wubi. If not, is there a way to detect the resolution in
Windows and put it in the usplash.conf? It seems relatively safe to
assume the Windows resolution is that user's preferred resolution,
certainly better than assuming 640x480 anyway.

Okay, thanks again, just wondering about Wubi.

-- 
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/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-04-01 Thread Colin Watson
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 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/mailman/listinfo/ubuntu-bugs


Re: [Bug 188764] Re: probe screen resolution at boot

2008-03-31 Thread Alexander Jones
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/13006912/unnamed

-- 
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/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-03-31 Thread Colin Watson
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 subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-03-31 Thread Warren Dumortier
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.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-03-31 Thread Saïvann Carignan
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 good values. That's all we can do from now. The real
solution is to probe automatically the good resolution at each boot and
to stop using static configuration files (/etc/usplash.conf), but this
won't happen for Hardy according to Matthew Garrett.

-- 
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/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-03-31 Thread Warren Dumortier
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 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/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-03-30 Thread Saïvann Carignan
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, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-03-30 Thread Colin Watson
** 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.com/mailman/listinfo/ubuntu-bugs


[Bug 188764] Re: probe screen resolution at boot

2008-03-30 Thread Colin Watson
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]>  Sun, 30 Mar 2008 22:43:16 +0100

I think that should be good enough for 8.04.

-- 
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/mailman/listinfo/ubuntu-bugs