Ticket #505 (closed enhancement: fixed)
Identify Debathena on the login screen
| Reported by: | geofft | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Summer 2010 (Lucid Deploy) |
| Component: | -- | Keywords: | |
| Cc: | Fixed in version: | ||
| Upstream bug: |
Description (last modified by broder) (diff)
This is vaguely a repeat of #158 for new-style GDM
In particular, we should have a big block of text saying "Welcome to Debathena" or something on the login screen, as well as identifying which metapackage and Debian/Ubuntu? release the person is running.
rbasch already written code to make applications work correctly when running with GDM for the debathena-kiosk launcher. We should pull that out into a common parent class and use it for both the kiosk launcher and this "Welcome to Debathena" message.
Attachments
-
debathena-branding
(3.6 KB) -
added by jdreed 14 years ago.
Change History
comment:2 Changed 14 years ago by broder
For new-style GDMs, we can abuse the same technique we're using to pull off the kiosk browse button. If we write a Gtk app that just prints "$(machtype -L) on $(machtype -E)" on top of everything else, and drop a .desktop file in /usr/share/gdm/autostart/LoginWindow, we don't even need the complexity of the debathena-foo-branding packages.
Before deploying this, though, we need to find the fix for #548 and apply it to this application as well.
Who says you can't do arbitrary skinning on new-style GDM?
comment:3 Changed 14 years ago by broder
- Description modified (diff)
- Summary changed from distinguish cluster from workstation machine on login screen, take 2 to Identify Debathena on the login screen
comment:4 Changed 14 years ago by jdreed
Here, have some code (mostly blatantly stolen from Bob's kiosk code)
comment:5 Changed 14 years ago by jdreed
I'll add another window that says "Welcome to Debathena" or something, and then push this to proposed. This should probably go into gdm-config where the branding packages live now, but that package scares me.
comment:6 Changed 14 years ago by jdreed
- Status changed from new to committed
Committed in r24816.
I have not added anything to a .install file yet, because I'm not sure which package it goes into and how this interacts with the existing -branding packages.
I also have not yet moved the session management code into a common class.
Also, it's ugly.
comment:7 Changed 14 years ago by jdreed
- Status changed from committed to development
After fixing a typo in the rules file (r2482{0,1}), I have uploaded this to development, and tested it.
I used the Trebuchet font to keep some visual cues the same for users who might be transitioning.
I vaguely feel like having the workstation info in the bottom right makes it look ugly, but we can bikeshed about it once Lucid has been released to the clusters.
