Differences between revisions 34 and 102 (spanning 68 versions)
Revision 34 as of 2006-05-14 17:36:42
Size: 4837
Editor: ?FransPop
Comment: No it does not. That's nonsense.
Revision 102 as of 2009-09-14 14:23:54
Size: 8076
Editor: GeoffSimmons
Comment: DebianBug, DebianPkg. sdljump is now gnujump.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Overview of open issues and things to be done for the ["DebianInstaller/GUI"]. == Introduction ==
This is an overview of some of the bugs and issues left open or workarounded only in Etch and that i hope will be fixed later in a point release.
Line 3: Line 4:
See also open [http://bugs.debian.org/cdebconf-gtk-udeb bug reports against cdebconf-gtk-udeb]. Items tagged as '''''pointrelease''''' are desiderata for next Etch pointrelease (mainly bugfixes), all other items refer to issues which will be addressed in Lenny only.
Line 5: Line 6:
= Issues = This is no way meant to be an exhaustive list of every bug somehow related to the graphical installer: for a complete buglist see packages DebianBug:cdebconf-gtk-udeb, DebianBug:directfb, [[DebianBug:libdirectfb-1.0-0-udeb]], [[DebianBug:libgtk-directfb-2.0-0]], [[DebianBug:libgtk-directfb-2.0-0-udeb]], DebianBug:rootskel, DebianBug:rootskel-gtk.
Line 7: Line 8:
The main issues left are:
 * use of official font packages instead of tarballs
 * solve the console switching problem on AMD64
 * inventory of which powerpc systems are supported and which are not; some could maybe be supported with special boot options or rootskel scripts; rootskel scripts could also be udes to disable the gtk frontend for non-compatible systems
 * endianness color issue for powerpc
<<TableOfContents(3)>>
Line 13: Line 10:
== udeb dependency resolution == == Architecture independent issues ==
 * Develop real graphical interfaces for components where that adds value. Main example is partitioning.
  * For partitioning one option is porting gparted to C. Work on this was already started by [[http://lists.debian.org/debian-boot/2006/06/msg01358.html|Xavier Oswald]]. Current code is available [[http://svn.debian.org/wsvn/parted/gdisktool/trunk/?rev=0&sc=0|on alioth]].
 * Try to find a way to present information in columns despite using a proportional font. This may require extensions to the debconf protocol. This should also be generally useful for frontends used in the installed system for configuring packages. '''done'''
 * Input is not handled in UTF-8 mode, some letters cannot be correctly typed. DebianBug:401296 - '''done'''
 * Support for dead keys was added in DFB post 0.9.25, but GTKDFB does not handle deadkeys anyway, so backporting the DrectFB patch is useless ATM DebianBug:394871 - '''done'''
 * Plans for Lenny are having cdebconf (C implementation of debconf used in the d-i) replacing debconf (DebianBug:328498) in regular debian systems: this will require cdebconf's building system and the GTK frontend being able to build atop of both gtk/directfb nad gtk/x11, see also DebianBug:402127 - '''done'''
Line 15: Line 18:
During a build, not all dependencies between udebs can be resolved if all udebs are taken from the official mirrors. The current workaround is to copy some udebs to "localudebs", but this is not acceptable for the main build infrastructure (see also [http://lists.debian.org/debian-boot/2005/10/msg00955.html this thread]). == Per-architecture issues ==
We're trying to inventory bugs affecting the g-i on a per-architecture base, architectures considered here are i386, PowerPC, AMD64 .
Line 17: Line 21:
The problem occurs if some udebs depend on a normal library package (libfoo.deb) while other udebs depend on the corresponding udeb (libfoo.udeb). === i386 specific ===
 * For historical reasons the vga16fb module is still loaded even if a framebuffer device is already provided by vesafb: this forced us to check that DirectFB actually accesses the framebuffer device provided by vesafb , better would be not starting at all two fb devices concurrently (this also wastes little memory). DebianBug:401685 - '''done'''
 * Some popular video chips, like intel i810, are not supported by the vesafb framebuffer module and hw-specific modules are not available in the installer, so we cannot currently support those chips. We need to either build into the kernel or provide as loadable modules hw specific framebuffer modules, and load them on the base of the found hardware DebianBug:405737.
Line 19: Line 25:
There are two known solutions for this issue.
 1. Change dependencies in udebs in such a way that they all depend in the same manner. This is what currently happens for the main installer. Problem with this solution is that the udebs involved are not maintained by the d-i team. Also, this would be ignoring the structural problem.
 1. Fix the toolchain (mainly dpkg-dev) to improve automatic dependency determination when udebs are build. A [http://lists.debian.org/debian-dpkg/2005/06/msg00198.html patch] for this has been proposed but has not yet been implemented.
=== AMD64 specific ===
 * '''pointrelease''' The console switching problem on AMD64 DebianBug:373253 was worked around by adding libgcc1.so.1 via the EXTRAFILES option available in the installer, proper fix requires adding that library via an udeb.
Line 23: Line 28:
'''Update'''
 * udeb dependency resolution is now supported in dpkg-dev and debhelper
 * all (library) udebs relevant for the graphical installer now have correct dependencies
=== PowerPC specific ===
Line 27: Line 30:
== Other issues ==
 * Option in the main menu to exit to a shell does not work ([http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339855 #339855]).
 * DirectFB linux_input input module cannot correctly detect the keyboard on most PowerMacintosh models, so we had to disable it relying on the legacy ps2mouse and keyboard input dr.<<BR>>This required the inclusion into rootskel and rootskel-gtk packages of some ad hoc startup scripts that take care of picking the correct DirectFB input driver depending on the host architecture.<<BR>>A prper addressing of this issue requires fixing the linux_input module so that we can switch to linux_input input module for all supported architectures and drop some startup scripts.<<BR>><<BR>>
 * Another issue is related to the fact that apparently DirectFB cannot run on top of the nvidia framebuffer: no more information are available because not much light was made on this problem yet.<<BR>><<BR>> This thread (DebianBug:422146) is about the two above mentioned issues, while a g-i on PowerPC compatibility list can be found here [[DebianInstaller/GUIPowerPC]]: feel free to add entries for any configuration that's not yet listed.<<BR>><<BR>>
 * The framebuffer device has a fixed size that cannot be set at boot like it's done on i386, so the GTK frontend should adapt itself to go "fullscreen". DebianBug:401693
Line 30: Line 34:
= TODO = == Ideas for future development ==
Line 32: Line 36:
== Porting ==
The graphical version of the installer is currently available for Intel x86, AMD64 and PowerPC. The PowerPC port [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341597 needs work] to get different types of system correctly supported. Other architectures the graphical installer could be ported to include Sparc, Alpha and HPPA.
=== Porting ===
Line 35: Line 38:
== Fonts == The graphical version of the installer is currently available for Intel x86, AMD64 and PowerPC. The PowerPC port needs work (DebianBug:341597) to get different types of system correctly supported. Other architectures the graphical installer could be ported to include Sparc, Alpha and HPPA.
Line 37: Line 40:
For font information, please see ["DebianInstaller/GUIFonts"] === Fonts ===
Line 39: Line 42:
== Usability ==
 * Screen resolution.
   * Currently fixed at 800x600. Should be made flexible (adapt to resolution set by system or user).
   * Interface should adapt itself so that text blocks are never too wide for optimal readability.
 * Improve accessability (for the visually handicapped). One way to do this is to [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339735 support different themes] (color schemes). (Note: should not lead to a major increase in initrd size.)
 * Progress bar in separate window.
 * Alternative (graphical) ways to start a shell or browse log files.
For font information, please see [[DebianInstaller/GUIFonts]]

=== Usability ===

 * Interface should adapt itself so that text blocks are never too wide for optimal readability.
 * Improve accessability (for the visually handicapped). One way to do this is to support different themes (DebianBug:339735) (color schemes). (Note: should not lead to a major increase in initrd size.)
 * Alternative (graphical) ways to start a shell or browse log files - '''done'''
 * Logfile-viewer (in split window) in expert mode as default, if screen resolution permits
Line 50: Line 54:
Most of the work on the graphical side has been done by Eduardo Silva. He has set up a [http://www.geocities.com/jobezone/d-i_gtk.html webpage] with images he designed and some comments about possible future changes.
Line 52: Line 55:
Most of the work on the graphical side has been done by Eduardo Silva. He has set up a [[http://www.geocities.com/jobezone/d-i_gtk.html|webpage]] with images he designed and some comments about possible future changes.
Line 53: Line 57:
== Reduce size of initrds ==
The initrds are currently very large which also results in fairly high memory requirements to run the graphical installer. Size has thus far not been a major concern, our focus has been on getting things working.
=== Games ===
Line 56: Line 59:
Options to reduce initrd size.
 * Library reduction for graphical libraries.
 * Remove unused files from udebs.
 * Reduction of space used by fonts (see above).
It would be nice for g-i to have some games to help kill time during lengthy install sessions.
Line 61: Line 61:
'''Update'''
The size of the initrds is now down to around 10MB. Further reduction would be nice, but it is no longer a major issue.
The [[http://lists.debian.org/debian-boot/2007/08/msg00560.html|cdebconf-gtk-tetris]] udeb is a start, but having a separate entry in the menu does not seem the best way to do it.
Line 64: Line 63:
== Migrate from gtk+-directfb-2.0.9 to more recent version of GTK+ ) ==
The udebs for gtk+-directfb are based on a [http://www.directfb.org/downloads/Libs/gtk+-directfb-2.0.9-2.tar.gz set of sources]
released in Apr 2003; it's now possible to build a set of libraries based on gtk+2.8.10
which was released around Jan 2006. The main problem is that [http://wiki.debian.org/DebianInstaller/GUIBuild building] is rather tricky, and there are no pre-patched sources available from upstream.
Recently the Direct Frame Buffer backend was merged into GTK+ mainline and will be part of the upcoming GTK+ libraries version 2.10, whose release date is set around May 2006.
Once upstream libraries will be ready to be used, they'll have to be packaged into udebs before we can use them in the installer.
Other candidates for inclusion need to have a limited set of dependencies, preferable only those that are already included in g-i, use directfb for graphics, eventually using SDL, sound should be optional, and not need more input device than already detected by g-i.

This excludes c++ implemented games linked against libstdc++, or other language whose runtime is not-available in g-i, as well as all those that link with the gnome libs or other such. A preliminary list follows, out of them, icebreaker sounds like a very good candidate. It is only depending on libsdl, easy to understand, using only the mouse and not the keyboard, and not controversial in any way.

 * [[DebianPkg:unstable/games/airstrike|airstrike]] - 2d dogfight game in the tradition of 'Biplanes' and 'BIP'
 * [[DebianPkg:unstable/games/atris|atris]] - tetris-like game with a twist for Unix
 * [[DebianPkg:unstable/games/barrage|barrage]] - Rather violent action game
 * [[DebianPkg:unstable/games/black-box|black-box]] - Find the crystals
 * [[DebianPkg:unstable/games/bomberclone|bomberclone]] - free Bomberman-like game
 * [[DebianPkg:unstable/games/bugsquish|bugsquish]] - Bugs are trying to suck blood out of your arm!
 * [[DebianPkg:unstable/games/bumprace|bumprace]] - 1 or 2 players race through a multi-level maze
 * [[DebianPkg:unstable/games/bygfoot|bygfoot]] - soccer (football) manager game featuring the most important European leagues
 * [[DebianPkg:unstable/games/circuslinux|circuslinux]] - The clowns are trying to pop balloons to score points!
 * [[DebianPkg:unstable/games/dangen|dangen]] - shoot 'em up game where accurate shooting matters
 * [[DebianPkg:unstable/games/gnujump|gnujump]] - (formerly sdljump) Jump up in a sinking tower (a first [[http://lists.alioth.debian.org/pipermail/pkg-games-devel/2006-February/000349.html|unofficial (and untested) udeb]] was already made by Bas Wijnen <shevek at fmf.nl> )
 * [[DebianPkg:unstable/games/icebreaker|icebreaker]] - Break the iceberg

Introduction

This is an overview of some of the bugs and issues left open or workarounded only in Etch and that i hope will be fixed later in a point release.

Items tagged as pointrelease are desiderata for next Etch pointrelease (mainly bugfixes), all other items refer to issues which will be addressed in Lenny only.

This is no way meant to be an exhaustive list of every bug somehow related to the graphical installer: for a complete buglist see packages cdebconf-gtk-udeb, directfb, libdirectfb-1.0-0-udeb, libgtk-directfb-2.0-0, libgtk-directfb-2.0-0-udeb, rootskel, rootskel-gtk.

Architecture independent issues

  • Develop real graphical interfaces for components where that adds value. Main example is partitioning.
    • For partitioning one option is porting gparted to C. Work on this was already started by Xavier Oswald. Current code is available on alioth.

  • Try to find a way to present information in columns despite using a proportional font. This may require extensions to the debconf protocol. This should also be generally useful for frontends used in the installed system for configuring packages. done

  • Input is not handled in UTF-8 mode, some letters cannot be correctly typed. 401296 - done

  • Support for dead keys was added in DFB post 0.9.25, but GTKDFB does not handle deadkeys anyway, so backporting the DrectFB patch is useless ATM 394871 - done

  • Plans for Lenny are having cdebconf (C implementation of debconf used in the d-i) replacing debconf (328498) in regular debian systems: this will require cdebconf's building system and the GTK frontend being able to build atop of both gtk/directfb nad gtk/x11, see also 402127 - done

Per-architecture issues

We're trying to inventory bugs affecting the g-i on a per-architecture base, architectures considered here are i386, PowerPC, AMD64 .

i386 specific

  • For historical reasons the vga16fb module is still loaded even if a framebuffer device is already provided by vesafb: this forced us to check that DirectFB actually accesses the framebuffer device provided by vesafb , better would be not starting at all two fb devices concurrently (this also wastes little memory). 401685 - done

  • Some popular video chips, like intel i810, are not supported by the vesafb framebuffer module and hw-specific modules are not available in the installer, so we cannot currently support those chips. We need to either build into the kernel or provide as loadable modules hw specific framebuffer modules, and load them on the base of the found hardware 405737.

AMD64 specific

  • pointrelease The console switching problem on AMD64 373253 was worked around by adding libgcc1.so.1 via the EXTRAFILES option available in the installer, proper fix requires adding that library via an udeb.

PowerPC specific

  • DirectFB linux_input input module cannot correctly detect the keyboard on most ?PowerMacintosh models, so we had to disable it relying on the legacy ps2mouse and keyboard input dr.
    This required the inclusion into rootskel and rootskel-gtk packages of some ad hoc startup scripts that take care of picking the correct DirectFB input driver depending on the host architecture.
    A prper addressing of this issue requires fixing the linux_input module so that we can switch to linux_input input module for all supported architectures and drop some startup scripts.

  • Another issue is related to the fact that apparently DirectFB cannot run on top of the nvidia framebuffer: no more information are available because not much light was made on this problem yet.

    This thread (422146) is about the two above mentioned issues, while a g-i on PowerPC compatibility list can be found here DebianInstaller/GUIPowerPC: feel free to add entries for any configuration that's not yet listed.

  • The framebuffer device has a fixed size that cannot be set at boot like it's done on i386, so the GTK frontend should adapt itself to go "fullscreen". 401693

Ideas for future development

Porting

The graphical version of the installer is currently available for Intel x86, AMD64 and PowerPC. The PowerPC port needs work (341597) to get different types of system correctly supported. Other architectures the graphical installer could be ported to include Sparc, Alpha and HPPA.

Fonts

For font information, please see DebianInstaller/GUIFonts

Usability

  • Interface should adapt itself so that text blocks are never too wide for optimal readability.
  • Improve accessability (for the visually handicapped). One way to do this is to support different themes (339735) (color schemes). (Note: should not lead to a major increase in initrd size.)

  • Alternative (graphical) ways to start a shell or browse log files - done

  • Logfile-viewer (in split window) in expert mode as default, if screen resolution permits
  • Interface design.
  • Create custom plug-ins for cdebconf to improve handling of some dialogs and make optimal use of possibilities offered by the graphical environment.

Interface design

Most of the work on the graphical side has been done by Eduardo Silva. He has set up a webpage with images he designed and some comments about possible future changes.

Games

It would be nice for g-i to have some games to help kill time during lengthy install sessions.

The cdebconf-gtk-tetris udeb is a start, but having a separate entry in the menu does not seem the best way to do it.

Other candidates for inclusion need to have a limited set of dependencies, preferable only those that are already included in g-i, use directfb for graphics, eventually using SDL, sound should be optional, and not need more input device than already detected by g-i.

This excludes c++ implemented games linked against libstdc++, or other language whose runtime is not-available in g-i, as well as all those that link with the gnome libs or other such. A preliminary list follows, out of them, icebreaker sounds like a very good candidate. It is only depending on libsdl, easy to understand, using only the mouse and not the keyboard, and not controversial in any way.

  • airstrike - 2d dogfight game in the tradition of 'Biplanes' and 'BIP'

  • atris - tetris-like game with a twist for Unix

  • barrage - Rather violent action game

  • black-box - Find the crystals

  • bomberclone - free Bomberman-like game

  • bugsquish - Bugs are trying to suck blood out of your arm!

  • bumprace - 1 or 2 players race through a multi-level maze

  • bygfoot - soccer (football) manager game featuring the most important European leagues

  • circuslinux - The clowns are trying to pop balloons to score points!

  • dangen - shoot 'em up game where accurate shooting matters

  • gnujump - (formerly sdljump) Jump up in a sinking tower (a first unofficial (and untested) udeb was already made by Bas Wijnen <shevek at fmf.nl> )

  • icebreaker - Break the iceberg