adjusting this in ubiquity wont be possible in all different possible
frontends. the noninteractive frontend for example cant query the
current resolution in all cases.
On 3/30/08, Saïvann Carignan <email address hidden> wrote:
> The answer to this question is in the bug description, according to
> Matthew Garrett, the usplash maintainer, the best way to fix this
> temporary is through ubiquity. I let the bug open in both ubiquity and
> usplash so developers can take their decision about which solution will
> be applied. Automatic usplash detection won't happen in Hardy, but might
> be implemented for Intrepid. Colin Watson started to work on this in bug
> 150930.
>
> --
> [hardy]640x480 usplash on all computers
> https://bugs.launchpad.net/bugs/188764
> You received this bug notification because you are a member of Ubuntu
> Installer Team, which is subscribed to ubiquity in ubuntu.
>
adjusting this in ubiquity wont be possible in all different possible
frontends. the noninteractive frontend for example cant query the
current resolution in all cases.
On 3/30/08, Saïvann Carignan <email address hidden> wrote: /bugs.launchpad .net/bugs/ 188764
> The answer to this question is in the bug description, according to
> Matthew Garrett, the usplash maintainer, the best way to fix this
> temporary is through ubiquity. I let the bug open in both ubiquity and
> usplash so developers can take their decision about which solution will
> be applied. Automatic usplash detection won't happen in Hardy, but might
> be implemented for Intrepid. Colin Watson started to work on this in bug
> 150930.
>
> --
> [hardy]640x480 usplash on all computers
> https:/
> You received this bug notification because you are a member of Ubuntu
> Installer Team, which is subscribed to ubiquity in ubuntu.
>
--
Sent from Gmail for mobile | mobile.google.com
Mario Limonciello
<email address hidden>