Custom Query (1145 matches)
Results (181 - 183 of 1145)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#788 | workaround | (some) printer2 queues are broken | geofft | kaduk |
Description |
Maybe just for cluster printers? We should follow up with Ops and get broken queues removed from the list. geofft was going to poke at this some more |
|||
#286 | wontfix | some equivalent of console in this brave new world | quentin | geofft |
Description |
~/.xsession-errors captures all stdout and stderr from your Athena session. This means that it captures inordinate amounts of GNOME spew, so you don't want that displayed Athena-9-console style. The downside of this is that things that you do want displayed, like output of your .startup.X, output of from, etc., don't show up anywhere. If you want to display things at login, you need to copy the hairy anti-HTML code to invoke zenity that we added today to fix the gmotd. And, that doesn't have the nice features of Athena 9's console that it updates as more info comes in and it can hide until more input arrives. It would be totally spiffy if someone implemented a short python-gtk or whatever app that waited for input on stdin, mapped itself, and displayed data. Then we can run .startup.X with stdout/stderr redirected to this app, and display output the user wants to see iff there is such output. For example, RSI has code in .startup.X to display a motd on stdout, assuming the Athena 9 console. I also have code in .startup.X to display various useful output, and .xsession-errors is a useless place for it to go (it's not an error!). |
|||
#1168 | invalid | Some combination of ConsoleKit, LightDM, or our greeter sucks | jdreed | |
Description |
On Precise, after returning to the login screen after the first login, I can't reboot/shutdown from the greeter, and get a "Authorization is required" error from ConsoleKit?, and CK debug info shows "CkManager?: Unable to lookup cookie for caller - failing". Adding session optional pam_loginuid.so to /etc/pam.d/lightdm fixes this. I don't understand why. In many respects, this is like DebianBug:597937, but not exactly. |