Custom Query (1145 matches)
Results (91 - 93 of 1145)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#180 | fixed | athinfo manpage out of date | geofft | broder |
Description |
We should update for the queries we currently support |
|||
#212 | fixed | wireless LAN doesn't start at graphical login screen | geofft | geofft |
Description |
Ubuntu doesn't start the wireless network until a user has logged in, ostensibly so that it can pick up the list of preferred networks, and if they need encryption, grab the password out of the login keyring. This interacts poorly with debathena-login-graphical. In particular, you need the wireless LAN to be working before a user logs in, so you can authenticate their network login. If you have no local users, the machine is basically useless. This mostly affects laptops, although desktops with wireless-only connections are common in places like dorm rooms that don't have many Ethernet drops. When I heard about this problem last fall, I wrote http://geofft.mit.edu/p/start-network.py , a simple Python script to ask NetworkManager over D-Bus to enumerate all wireless networks on all interfaces and connect to the first one named "MIT". I haven't tested it with Ubuntu 8.10 or 9.04 -- the interfaces may well have changed. It also needs to be packaged better; two options are to run this out of an initscript at boot time, and to make this a "custom command" in the GDM greeter that you can choose from the login screen. It would be nice if you could also specify what network to connect to. To be useful, though, this functionality probably depends on running GUI applications at the login screen, which we haven't yet figured out how to do. Maybe we can use the same setup as the Firefox kiosk mode will, and create a special local user that can only choose a wireless network to log in to (via the built-in GUI applet to do this). Ticket #208 is also relevant for this configuration, since the wireless connection is prone to disconnecting. |
|||
#250 | wontfix | zwgc fonts are too big | geofft | jhawk |
Description |
Under debathena, zwgc uses fonts that are too large. /etc/zwgc_resources defines the default medium font as: *fontfamily.default.medium.roman: -adobe-courier-medium-r-*-120-*-m-* And under Debathena, this can be any of these eight fonts: [kid-icarus!jhawk] ~> xlsfonts -fn '-adobe-courier-medium-r-*-120-*-m-*' -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso10646-1 -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso10646-1 -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso8859-1 -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso8859-1 -adobe-courier-medium-r-normal--17-120-100-100-m-100-iso10646-1 -adobe-courier-medium-r-normal--17-120-100-100-m-100-iso10646-1 -adobe-courier-medium-r-normal--17-120-100-100-m-100-iso8859-1 -adobe-courier-medium-r-normal--17-120-100-100-m-100-iso8859-1 The 17 pxlsz fonts are unreasonably large. The 12 pxlsz fonts match the size of windowgrams under Athena 9. I'm not sure if there is a larger problem (why do fonts get bigger under DebAthena?? Are other applications broken?); I'm also not sure what the right fix is (change zwgc's font specification to be more specific? Reorder the font path? Something more clever?) Thanks. p.s.: reminder, the fontspec is fndry-fmly-wght-slant-sWdth-adstyl-pxlsz-ptSz-resx-resy-spc-avgWdth-rgstry-encdng, per xfontsel. |