Custom Query (1145 matches)

Reported by geofft, 15 years ago.

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.

Reported by geofft, 15 years ago.

My .bash_environment contains in part:

add windowmanagers
export WINDOW_MANAGER=ratpoison
skip_panel=1
skip_nautilus=1
skip_initial_xterm=1

This suffices to get me ratpoison on -cluster and below on Intrepid (and on Athena 9), but not on Jaunty. I've also heard reports from others that WINDOW_MANAGER doesn't work for them.

Since it works on up-to-date Intrepid systems, this is something Ubuntu changed; we should figure out what it is and work around it.

Reported by amu, 13 years ago.

Now that  Python 2.7 is the default version in wheezy, the squeeze repository is no longer an adequate stand-in; in particular, its python-hesiod depends on python (<< 2.7). Could you please add a separate wheezy build?

Thanks!