GdmUpgrade

Differences between revisions 9 and 10
⇤ ← Revision 9 as of 2009-01-19 18:05:56 →
Size: 2704
Editor: ANancy-258-1-10-178
Comment:
← Revision 10 as of 2009-01-19 18:07:20 → ⇥
Size: 2710
Editor: ANancy-258-1-10-178
Comment:
Deletions are marked like this. Additions are marked like this.
Line 31: Line 31:
=== Design ===

The new version has no gdmflexiserver nor configuration tool, that's an upstream choice
Line 47: Line 51:
 * The new version has no gdmflexiserver
 * There is no graphical tool to change the configuration

  • Launchpad Entry: gdm-upgrade

  • Created:

  • Contributors:

  • Packages affected: gdm, gdm-guest-session, fast-user-switch-applet

Summary

Ubuntu is still using the old gdm codebase, this specification describes what is required to upgrade to the current upstream version

Release Note

The new gdm is being used now

Rationale

The current version is what upstream and other distributions are working on. It fixes limitations of the previous version and has cleaner code

Use Cases

  • The desktop team wants to ship the current upstream code and have something easier to work on

Implementation

Changes in jaunty:

  • The new gdm will be packaged in universe as gdm-new (or similar naming) (seb128)
  • The guest session code will be updated to work with the new gdm version (pitti)
  • The new fast-user-switch-applet gdm code will be updated to be similar to the current ubuntu version (tedg)

Design

The new version has no gdmflexiserver nor configuration tool, that's an upstream choice

Code Changes

  • The gdm-guest-session and fast-user-switch-applet codes need to be updated.

Migration

The autologin and timedlogin settings need to be migrated so they are used after upgrade. Other options should not be an issue but if user feedback points some other settings which need to be migrated those will be considered

Test/Demo Plan

Unresolved issues

  • There is some autologin changes which need to be ported to the new codebase?

BoF agenda and discussion

  • How do we edit the gdm settings (which are gconf based but owned by the gdm user)? No GUI for some features (e.g. timed login)
    • Probably easier to do from the login screen (runs as gdm user)
    • Preferably, we'd expose the settings in both the login screen and the user's preferences (requiring some gksu prompting to sudo to gdm)
    • Theme should offer to start any external program which is needed to change the theme
  • New GDM requires running multiple X servers (the gdm-user one which acts as a login / password prompt when screen is locked / fast-user-switch prompt, and the users' ones)
    • This is an issue on e.g. Intel because you can only start one DRI enabled server
    • Perhaps we can use a blacklist to disable DRI on the gdm X server instead of missing it in the user's server
    • Facebrowser uses GL, but it's less critical than being able to run compiz
    • Issues in Intel drivers should be resolved with the 2.6.29 kernel (need fixes in DRM); should land in time for Jaunty +1 anyway

CategorySpec

DesktopTeam/Specs/Jaunty/GdmUpgrade (last edited 2009-01-20 19:46:57 by pd956a57b)