update (05/05/08)
i guess a lot of people are looking for mythbuntu + nxserver because this post is getting tons of search traffic. one thing that bugged me forever about mythbuntu + nxserver/nxclient was trying to get xfce or even kde4 to start. to make your life easier if you can spare the space, install ubuntu-desktop (#) in mythbuntu to use nxclient like you normally would on a ubuntu desktop.

i’ve really gotten used to using nxclient to connect to my linux server vs vnc. it’s about as simple to setup nxclient as it is to setup passworded X11 vnc, but nxserver uses encryption (ssh) out of the box. vnc doesn’t. you can also disconnect from a nx session and reconnect later, almost like screen but for X11 and not just a console.

how to install nxserver on (mythb)ubuntu 8.10

1. download the nxclient, nxnode, and nxserver debs from nomachine. [here]
2. install the packages w/ `sudo dpkg -i nx*.deb`
3. ssh to your server from your client
   to make sure your keys are setup properly. ssh w/ authorized_keys is optional, nxclient will remember your password if you want.
4. connect to your server using an nxclient for your client machine. [here]

(more…)

i’m still not happy with the way avahi or NetworkManager start networking in gutsy. i was having an issue with an nm connecting to an open access point instead of my access point, quick look at the NetworkManager faq and i found how to remove essids from NetworkManager.

How do I remove networks I no longer wish to connect to?
From the command line run the following replacing <SSID> with the SSID of the network you wish to remove:

    $gconftool-2 –recursive-unset /system/networking/wireless/networks/<SSID>

You can use the “Configuration Editor” (gconf-editor) to browse the networks listed in that configuration directory, but you cannot remove the SSID’s folder using the GUI tool.
[here]

arg. everytime i have to play with ‘gconf’ and ‘tool’ in it reminds me of a windows registry. unix/linux is supposed to use flatfiles for config files! eh, atleast i can remove the unwanted networks/access points now. oh, and if you’re working how nm picks networks….

How does NetworkManager select which wireless network to connect to?
NetworkManager only attempts to automatically connect to networks you have previously told it to connect to. If it finds multiple wireless networks that you have connected to in the past, NetworkManager selects the network one you connected to. If NetworkManager isn’t connecting to the network you want, try to force it to connect to the network you wish to be connected, and NetworkManager will remember that setting next time.
[here]

even better, it looks like debian/ubuntu modified NetworkManager for their distos.

My Card is not recognized by NetworkManager and I am running Debian or Ubuntu:
Debian and Ubuntu modified NetworkManager so that it would not manage any devices listed in /etc/network/interfaces. If you open this file and comment out the lines for the interfaces you want to manage and reboot NetworkManager will see them. **Do not comment out l0**
[here]

bleh. not sure whether to try a new NetworkManager build or just remove it completely and use something else to manage my wifi.

hrm. the current version of pidgin on borked is 2.2.1, but getdebs has pidgin 2.3.1. the .debs installed just fine and pidgin is off and running. haven’t had any issues with 2.3.1 locking up or blank screening like it was with the 2.2.1 version. we’ll see if pidgin is finally issue-free again for me.