Custom Query (1145 matches)
Results (313 - 315 of 1145)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#465 | fixed | come up with a coherent plan for debathena-printing-config | geofft | |
Description |
Right now our lpr wrapper is a descendant of a descendant of a hack, solving lots of little use cases but with no particular overarching intention about what it's doing. While we shouldn't forget about the edge cases we're supporting and break them in a rewrite (cf. #455), it's about time to have a clear design and spec for what it's doing rather than continuing its descent into feature creep. As I see it the two main issues with the current setup is that user-visible behavior depends on users being aware of whether a queue is CUPS and LPRng and that answering questions about the behavior usually requires looking at the source. This includes: (some of the following are inspired by TODOs in the current printing-config lpr wrapper)
|
|||
#468 | fixed | Can we drop a force-update and reconfigure-network script in /usr/share/recovery-mode/options/ ? | jdreed | jdreed |
Description |
/usr/share/recovery-mode/options is what gets presented to the user when they choose "recovery mode" at the grub menu. Hotline notes there's no way to force an update now. Can we dump a shell script in /usr/share/recover-mode/options that forces an update and then a "real" reboot? (a kexec reboot occasionally will end up back in recovery mode, which is not what we want) And when we have our debathena-change-the-ip-address-of-this-cluster-machine pony, that should go in the recovery-mode menu too. I'll note that naming them "athena-update" and "athena-network" will cause them to appear at the top of the list (it's sorted alphabetically) which is desirable. |
|||
#470 | fixed | clear login screen state after a few minutes | geofft | |
Description |
This may be a bit unrealistic, but then again, it might be trivial to implement. I've seen users get confused when someone had previously (probably out of curiosity) picked a nonstandard window manager at the login screen and not logged in, so the next user ended up using that WM. Especially with WMs like twm or xmonad that default to a blank screen, this can be a pretty bad user experience. kchen also reports that the same thing is possible with languages -- someone can set a session language at the login screen and not log in, and the next user to log in will get prompted if they want that as their default language. It would be nice, if possible, to cause that state to disappear if you haven't logged in after a minute or so; equivalently, that state should be made visible on the login screen, a la Athena 9's xlogin, and it should mention some easy way to clear it. (Does "Esc" work?) This is probably not worth putting effort on for pre-Karmic gdm (i.e., <= 2.20). |