Everytime I was using my wireless USB keyboard with my laptop while the power cable was not connected, the keyboard behaviour was lousy, and keystrokes tend to be delayed by several seconds. The kernel logs said something like Read more…
Apparently the combination of a WLAN router that blocks IPv6 DNS queries of type AAAA (in my case, it was a Siemens S1621-Z220-A sold as Alice Modem 1121 WLAN) and the current version of Google Earth for Linux (I am using 5.1.3533.1731 from Medibuntu) do not work well together. The problem is that the router simply throws away AAAA queries (or generally, any type it does not know), so the DNS query times out. However, Google Earth does not seem to fall back to IPv4 queries (type A) in this case, and shows a message about network connectivity errors. I don’t know if it’s Google Earth’s fault or if the underlying eglibc resolver of my Linux system does something wrong, anyhow there is a fairly well-commented bug report on Launchpad for Ubuntu Karmic and Lucid which explains the issue.
Anyway, I got rid of the problem by manually configuring a nameserver on my local machine (for example the nameserver(s) of your internet provider, or the ones of OpenDNS), and not using the WLAN router as a resolver. NetworkManager allows you to do this by editing a connection and choosing “Automatic DHCP (Addresses only)” on the IPv4 register tab; or you can write the settings directly to your /etc/resolv.conf (here for the OpenDNS servers):
nameserver 22.214.171.124 nameserver 126.96.36.199
I was on the train today, needed some of the Boost manuals, and had no internet connection. So I wanted to use my phone (an old HTC Prophet with Windows Mobile 6.1) as a network access point to browse over GPRS/EDGE. As I found out, it is fairly simple with Blueman and it even provides NetworkManager integration, so all NetworkManager-capable applications can be notified about the connectivity. Windows Mobile 6.1 allows tethering over a Bluetooth PAN (Personal Area Network); but there is another method called DUN (Dial Up Networking), which I will not describe here. So here is a step-by-step tutorial what I did for my PAN approach, with a few (german) screenshots, tested on Ubuntu 10.04 Lucid:
- Since my laptop was running on Ubuntu Lucid, there was already a recent Blueman version in the Ubuntu repos available. On older systems, you may want to add the Blueman Launchpad PPA.
sudo apt-add-repository ppa:blueman/ppa # only necessary on pre-lucid systems sudo aptitude update sudo aptitude install blueman
Note that this also removes possibly installed gnome-bluetooth packages since Blueman is an adequate replacement for the GNOME Bluetooth UI.
- After the installation has finished, I had to enable the NMPANSupport plugin for NetworkManager 0.8 by right-clicking on the Blueman icon in the GNOME notification area and selecting “Plugins”. For older NetworkManager versions, there is also a plugin for NetworkManager 0.7, called NMIntegration.
- Then I activated tethering on my phone (“Programs” → “Internet Sharing” on my Windows Mobile 6.1, but YMMV). Apparently this was neccesary with my model, because without tethering enabled I could not get a Bluetooth PAN connection in the next step.
- I paired the phone and my laptop via Bluetooth, and created a PAN (Personal Area Network) by connecting to the “Network Access Point” service on the phone. In Blueman, all you have to do after pairing is right-click on the device and select “Connect To: Network Access Point”. This creates a new network device bnep0 which is automagically configured through NetworkManager (using a stateless address autoconfiguration).
- However, in my setup, though I was able to ping certain IP adresses on the internet, DNS lookups timed out for some reason. It got better when I explicily set an IP address for the Bluetooth PAN driver on my phone, and did the tethering process all over again.
- And off I went with mobile internet access. Woo-hoo! \o/
I may also add that the NetUsage plugin in Blueman is very reasonable to use 😉 After activated, the network usage can be viewed by right-clicking on the Blueman icon and selecting “Network Usage”.
Yesterday, I ran into an interesting problem: I tried to set up SSH public key authentication between two of my machines, c3po and r2d2, so I could log in from rohieb@r2d2 to rohieb@c3po without a passphrase. However, everytime I tried to login to c3po, I was prompted to enter the passwort for rohieb@c3po, and the debug output mentioned something that thekey could not be verified. More astonishing, when I established a second SSH connection while the first was still running, I was not prompted for a password, and debug output said that key authentication had been sucessful. I googled a bit, and after a while got to this comment on Launchpad, mentioning problems when the user on the remote machine had its home directory encrypted through ecryptfs – which was the case for me. Of course, since ecryptfs only encrypts the user’s home after he has been authenticated, the SSH daemon cannot read his ~/.ssh/authorized_keys at the first time, and falls back to password authentication.
The Launchpad comment proposes to first unmount the ecryptfs filesystem, then store ~/.ssh/authorized_keys unencrypted, and then mount the encrypted home again (note that no program should be running that could try to access your home directory):
$ ecryptfs-umount-private $ cd $HOME $ chmod 700 . $ mkdir -m 700 .ssh $ chmod 500 . $ echo $YOUR_REAL_PUBLIC_KEY > .ssh/authorized_keys $ ecryptfs-mount-private
This works indeed, but has the drawback that key authentication only works for the first login, because ecryptfs hides the unencrypted files when it mounts the encrypted directory on login; and you had to synchronize the encrypted and the unencrypted version of authorized_keys everytime you add a new key. To circumvent that, I simply moved the file to /etc/ssh/authorized_keys/rohieb (with the file only readable and writable by me, and /etc/ssh/authorized_keys writeable for all users) and adjusting /etc/ssh/sshd_config appropriately:
$ sudo vi /etc/ssh/sshd_config # or use gedit instead of vi, or whatever... [... some lines ...] AuthorizedKeysFile /etc/ssh/authorized_keys/%u [... some more lines ...] $ sudo /etc/init.d/ssh restart
There is a better approach instead, which doesn’t need the SSHd config to be edited at all:
- login to the user on the remote machine
- create /home/.ecryptfs/$USER/.ssh and put your authorized_hosts there
- symlink your encrypted version there:
$ ln -s /home/.ecryptfs/$USER/.ssh/authorized_hosts ~/.ssh/authorized_hosts
- symlink your unencrypted version there (as above, make sure no process wants to write to your home directory in the meantime):
$ ecryptf-umount-private $ mkdir ~/.ssh $ ln -s /home/.ecryptfs/$USER/.ssh/authorized_hosts ~/.ssh/authorized_hosts $ ecryptfs-mount-private
The paths are for Ubuntu 9.10 (Karmic Koala) and later. On other systems, you might want to replace /home/.ecryptfs with /var/lib/ecryptfs.
[ Update, 2013-10: This post post is not up to date anymore. On newer Debians (since 7.0/wheezy) and Ubuntus (at least since 12.04, Precise Pangolin), you should be able to install zsnes out of the box: sudo apt-get install zsnes:i386. For details see the MultiArch documentation for Debian and Ubuntu. ]
Before I had bought my current hardware, I was working on a 32-bit-based system, and I really appreciated ZSNES as an SNES emulator. But unfortunately, my new hardware was an AMD64 system, and there is currently no ZSNES package for 64-bit Ubuntu or Debian 😦 So I decided to google a bit about the issue, but it took me until now (a year later) to get ZSNES finally working on my machine. The problem is, if you build ZSNES on a 64-bit machine, all the application does is segfault at start, and if you try to compile for 32-bit systems, you get errors about missing 32-bit libs (in particular, configure does not find a suitable libsdl). Instead, if you just take the binary which was compiled on a 32-bit system, and install ia32-libs everything seems to work—at least I was able to play a few levels of Super Mario World succesfully 🙂
So here was my idea: take the 32-bit package from the Ubuntu repository, and just change the Architecture control field, and by this fool dpkg 😛 And as it turned out, this idea worked great. You can get the Debian package here if you want, it should work for Ubuntu Karmic and Lucid, as well as for Debian testing (but I only tested it on Lucid, so there is no warranty here—but I’m happy to hear if it works :)):
- SHA1: 716bbd37267b477ef02961a7727212619309b83f
- MD5: 452ea5230ad17df1dee649ab4cc6c8c0
For the curious people reading here, here is what I actually did:
- wget http://archive.ubuntu.com/ubuntu/pool/universe/z/zsnes/zsnes_1.510-2.2ubuntu3_i386.deb
- ar x zsnes_1.510-2.2ubuntu3_i386.deb
- tar xzf data.tar.gz
- Edited usr/share/applications/zsnes.desktop and added -ad sdl to the Exec: field, otherwise it would just segfault on the first run:
Exec=zsnes -ad sdl
- Edited usr/share/doc/zsnes/changelog.Debian.gz and added a new changelog entry for the version
- tar xzf control.tar.gz
- Edited the control file, changed the Version: and Architecture: field to amd64, added the ia32-libs dependency, and set myself as maintainer:
Package: zsnes Version: 1.510-2.2ubuntu3~ppa1 Architecture: amd64 Maintainer: Roland Hieber <firstname.lastname@example.org> Installed-Size: 4160 Depends: ia32-libs, libao2 (>= 0.8.8), libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), libgl1-mesa-glx | libgl1, libpng12-0 (>= 1.2.13-4), libsdl1.2debian (>= 1.2.10-1), libstdc++6 (>= 4.1.1), zlib1g (>= 1:188.8.131.52) [...]
- Changed the md5sums file for the right values for usr/share/applications/zsnes.desktop and usr/share/doc/zsnes/changelog.Debian.gz (I used the md5sum command and copy-pasted it)
- tar czf control.tar.gz control md5sums postrm postinst
- tar czf data.tar.gz usr/
- ar r zsnes_1.510-2.2ubuntu3~ppa1_amd64.deb debian-binary control.tar.gz data.tar.gz
I’m afraid that I can’t put the package to PPA, Launchpad only accepts source packages for uploads, and builds the binary packages itself, both for i386 and AMD64. This approach can not be used here, since we needed the i386 binary for AMD64.
…note to myself: Remove a potentially mounted SD card before suspending your SL510, otherwise the kernel gets stuck…
Update: Turned out the SD card was a bit buggy, the driver mostly got a timeout when trying to speak with it.
Thinking of the phrase “never change a running system” I am usually not very keen on updating my Ubuntu system to a new distribution. However, not every new software version is available from the backports, so finally, I saw myself forced to upgrade to Karmic Koala.
I instantly regretted it. Of course, I appreciate all the new software, but as in every upgrade I ever made (and I probably should know by now -.-), there are a few things that were annoying me or are still doing it:
- kaffeine-1.0~pre is not even as useful as 0.8.7 from jaunty: While staying in touch with the main KDE (4) line, the developers seemed to completely remove the Playback -> Video menu, so it is not possible anymore to toggle deinterlacing, or any other video filter, which is very annoying for DVB-T. I filed a bug report on that. Futhermore, my DVB-T channels were lost, so I had to rescan them.
- The notifications displayed by notify-osd somehow have wandered from the upper right edge towards the middle right. This seems to be fixed now, as pointed out in the bug report, but somehow this fix never got onto my system, though the changelog of notify-osd says so… Additionally, the notifications for received messages in Pidgin do not hide anymore if I actually read the messages, they persist until their default timeout has elapsed. And they even show up now when my IM status is on “Do not Disturb” – this was not the case (just as I expected it) in jaunty.
- Icons in GTK menus are now hidden by default, which seemed very unfamiliar to me, since I always used them as an orientation guide, especcially in the Firefox search plugin menu. You can show them again in the System -> Preferences -> Appearance applet on the Interface tab by selecting “Show icons in menus”.
- GDM is no longer custumizable through themes. It just doesn’t support it, as it seems to be a complete rewrite. IMHO just another Unmature Software Thing.
Edit: I just found out that it is also not able to start GDM in Xnest, as I usually did for testing:
$ gdmflexiserver --xnest ** (gdmflexiserver:5916): WARNING **: Not yet implemented
- And finally, my customized GNOME window theme (based on Clearlooks) was broken 😦 I am very confident that the color of selected text was not the same color in the title bar, but now both seem to be the same color. This is really bad, as for the title bar, I used to have a darker shade of orange than for selected text. OK, changing to another theme may be simple, but until now, I haven’t found anything I like best.