pages tagged Ubunturohieb.namehttps://rohieb.name/blag/tag/Ubuntu/rohieb.nameikiwiki2019-05-05T21:56:21ZWireless USB keyboards and delayed keystrokeshttps://rohieb.name/blag/post/wireless-usb-keyboards-and-delayed-keystrokes/rohieb
CC-BY-SA 3.0
2013-09-19T05:04:01Z2012-04-28T23:09:00Z
<p>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</p>
<pre><code>[23302.802096] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[23302.842177] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
[23302.842190] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[23302.882145] uhci_hcd 0000:00:1a.2: PCI INT C -> GSI 19 (level, low) -> IRQ 19
[23302.882158] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[23302.929065] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[23302.929079] uhci_hcd 0000:00:1d.1: setting latency timer to 64
</code></pre>
<p>Searching on Google, I found <a href="https://bbs.archlinux.org/viewtopic.php?pid=898114#p898114">a forum post</a> which suggested to
disable USB auto-suspend in the <a href="http://packages.ubuntu.com/laptop-mode">laptop-mode</a> configuration files.
The relevant file on my Ubuntu 12.04 is
<code>/etc/laptop-mode/conf.d/usb-autosuspend.conf</code>, which is fairly well
documented, and has an option <code>AUTOSUSPEND_USBID_BLACKLIST</code> which
allowed me to blacklist my USB keyboard, so the device was no longer put
in auto-suspend mode. (The USB ID needed for
<code>AUTOSUSPEND_USBID_BLACKLIST</code> can be found in the output of <a href="http://packages.ubuntu.com/usbutils">lsusb</a>)</p>
<p>After editing that file, I had to restart the laptop-mode daemon (<code>sudo
/etc/init.d/laptop-mode restart</code>), and keystrokes from my wireless
keyboard arrived again without any delay.</p>
Google Earth and IPv6 DNS lookupshttps://rohieb.name/blag/post/google-earth-and-ipv6-dns-lookups/rohieb
CC-BY-SA 3.0
2013-09-19T05:04:01Z2011-01-22T12:02:00Z
<p>Apparently the combination of a WLAN router that blocks IPv6 DNS queries
of type <code>AAAA</code> (in my case, it was a Siemens S1621-Z220-A sold as <a href="http://www.alice-wiki.de/Alice_Modem_1121_WLAN">Alice
Modem 1121 WLAN</a>) and the current version of Google Earth for Linux (I am
using 5.1.3533.1731 from <a href="http://www.medibuntu.org/">Medibuntu</a>) do not work well together. The
problem is that the router simply throws away <code>AAAA</code> 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
<code>A</code>) 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 <a href="https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/417757">bug report</a> on Launchpad for Ubuntu Karmic and
Lucid which explains the issue.</p>
<p>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 <code>/etc/resolv.conf</code> (here
for the OpenDNS servers):</p>
<pre><code>nameserver 208.67.222.222
nameserver 208.67.220.220
</code></pre>
Bluetooth tethering via PAN with Windows Mobile and Ubuntuhttps://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/rohieb
CC-BY-SA 3.0
2013-11-09T04:11:26Z2010-11-07T23:00:00Z
<p>I was on the train today, needed some of the <a href="http://www.boost.org/">Boost</a> 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 <a href="https://launchpad.net/blueman">Blueman</a> and it
even provides <a href="http://projects.gnome.org/NetworkManager/">NetworkManager</a> integration, so all
NetworkManager-capable applications can be notified about the
connectivity. Windows Mobile 6.1 allows tethering over a Bluetooth PAN
(<a href="http://en.wikipedia.org/wiki/Personal_area_network">Personal Area Network</a>); but there is another method called DUN
(<a href="http://en.wikipedia.org/wiki/Bluetooth_profile#Dial-up_Networking_Profile_.28DUN.29">Dial Up Networking</a>), 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:</p>
<p><ul>
<li><p>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 <a href="https://launchpad.net/~blueman/+archive/ppa">Blueman Launchpad PPA</a>.</p></p>
<pre><code>$ sudo apt-add-repository ppa:blueman/ppa # only necessary on pre-lucid systems
$ sudo aptitude update
$ sudo aptitude install blueman
</code></pre>
<p></li>
<li><p>Note that this also removes possibly installed <code>gnome-bluetooth</code>
packages since Blueman is an adequate replacement for the GNOME
Bluetooth UI.</p></li>
<li><p>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.</p></p>
<div class="gallery">
<a href="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/blueman-menu.png"><img src="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/x200-blueman-menu.png" width="140" height="199" alt="Blueman context menu" class="img" /></a>
<a href="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/blueman-plugins.png"><img src="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/x200-blueman-plugins.png" width="286" height="200" alt="Blueman plugin page" class="img" /></a>
</div>
<p></li>
<li><p>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.</p></p>
<p><p><div class="gallery">
<a href="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/winmo-program-menu.png"><img src="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/x200-winmo-program-menu.png" width="150" height="200" alt="Windows Mobile Program screen" class="img" /></a>
<a href="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/winmo-connection-sharing.png"><img src="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/x200-winmo-connection-sharing.png" width="150" height="200" alt="Windows Mobile Internet
Sharing application" class="img" /></a>
</div ></p></li>
<li><p>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 <code>bnep0</code> which is
automagically configured through NetworkManager (using <a href="http://en.wikipedia.org/wiki/Link-local%20address">stateless
address autoconfiguration</a>).</p></p>
<div class="gallery">
<a href="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/blueman-pan.png"><img src="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/x100-blueman-pan.png" width="219" height="100" alt="Blueman: Context menu for device
“Leia”, menu entry “Network Access Point” is selected" class="img" /></a>
</div>
<p>(Yes, my phone is called <a href="http://en.wikipedia.org/wiki/Leia_Skywalker">Leia</a>… I also have a yet another HTC
Prophet for testing purposes, which is called <a href="http://en.wikipedia.org/wiki/Luke_Skywalker">Luke</a> <img src="https://rohieb.name/smileys/smile.png" alt=":-)" /> )</p>
<p></li>
<li><p>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 explicitly set an IP address for the Bluetooth PAN driver on my
phone, and did the tethering process all over again.</p></p>
<div class="gallery">
<a href="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/winmo-connections.png"><img src="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/x200-winmo-connections.png" width="150" height="200" alt="Windows Mobile System Settings
Screen, with item “Wi-Fi” selected" class="img" /></a>
<a href="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/winmo-networkdrivers.png"><img src="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/x200-winmo-networkdrivers.png" width="150" height="200" alt="Windows Mobile Network Driver
settings screen, with menu item “Bluetooth PAN Driver” selected" class="img" /></a>
<a href="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/winmo-bluetooth-ip.png"><img src="https://rohieb.name/blag/post/bluetooth-tethering-via-pan-with-windows-mobile-and-ubuntu/x200-winmo-bluetooth-ip.png" width="150" height="200" alt="Windows Mobile Bluetooth PAN Driver
settings screen" class="img" /></a>
</div>
<p></li>
<li><p>And off I went with mobile internet access. Woo-hoo! \o/</p></li>
</ul>
I may also add that the NetUsage plugin in Blueman is very reasonable to
use <img src="https://rohieb.name/smileys/smile4.png" alt=";-)" /> After activated, the network usage can be viewed by
right-clicking on the Blueman icon and selecting “Network Usage”.</p>
SSH key authentication with encrypted home directorieshttps://rohieb.name/blag/post/ssh-key-authentication-with-encrypted-home-directories/rohieb
CC-BY-SA 3.0
2019-05-05T21:56:21Z2010-10-08T22:00:00Z
<p>Yesterday, I ran into an interesting problem: I tried to set up <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ssh&sektion=1#AUTHENTICATION">SSH
public key authentication</a> between two of my machines, <code>c3po</code> and
<code>r2d2</code>, so I could log in from <code>rohieb@r2d2</code> to <code>rohieb@c3po</code> without a
passphrase. However, everytime I tried to login to <code>c3po</code>, I was
prompted to enter the passwort for <code>rohieb@c3po</code>, and the debug output
mentioned something that the key could not be verified. More
astonishing, when I established a second SSH connection while the first
was still running, I was <em>not</em> prompted for a password, and debug output
said that key authentication had been sucessful. I googled a bit, and
after a while got to <a href="https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/362427/comments/12">this comment</a> 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 <em>after</em> he has been authenticated, the SSH
daemon cannot read his <code>~/.ssh/authorized_keys</code> at the first time, and
falls back to password authentication.</p>
<p>The Launchpad comment proposes to first unmount the ecryptfs filesystem,
then store <code>~/.ssh/authorized_keys</code> unencrypted, and then mount the
encrypted home again (<strong>note</strong> that no program should be running that
could try to access your home directory):</p>
<pre><code>$ ecryptfs-umount-private
$ cd $HOME
$ chmod 700 .
$ mkdir -m 700 .ssh
$ chmod 500 .
$ echo $YOUR_REAL_PUBLIC_KEY > .ssh/authorized_keys
$ ecryptfs-mount-private
</code></pre>
<p>This works indeed, but has the drawback that key authentication only
works for the <em>first</em> 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
<code>authorized_keys</code> everytime you add a new key. To circumvent that, I
simply moved the file to <code>/etc/ssh/authorized_keys/rohieb</code> (with the
file only readable and writable by me, and <code>/etc/ssh/authorized_keys</code>
writeable for all users) and adjusting <code>/etc/ssh/sshd_config</code>
appropriately:</p>
<pre><code>$ sudo vi /etc/ssh/sshd_config # or use your favorite editor instead of vi
[... some lines ...]
AuthorizedKeysFile /etc/ssh/authorized_keys/%u
[... some more lines ...]
$ sudo /etc/init.d/ssh restart
</code></pre>
<h2 id="update">Update</h2>
<p>There is yet a better approach instead, which doesn’t need the SSHd
config to be edited at all:</p>
<ol>
<li>login to the user on the remote machine</li>
<li>create <code>/home/.ecryptfs/$USER/.ssh</code> and put your <code>authorized_hosts</code> there</li>
<li><p>symlink your encrypted version there:</p>
<pre><code>$ ln -s /home/.ecryptfs/$USER/.ssh/authorized_hosts ~/.ssh/authorized_hosts
</code></pre></li>
<li><p>symlink your unencrypted version there (as above, <strong>make sure</strong> no
process wants to write to your home directory in the meantime):</p>
<pre><code>$ ecryptf-umount-private
$ mkdir ~/.ssh
$ ln -s /home/.ecryptfs/$USER/.ssh/authorized_hosts ~/.ssh/authorized_hosts
$ ecryptfs-mount-private
</code></pre></li>
</ol>
<p>The paths are for Ubuntu 9.10 (Karmic Koala) and later. On other
systems, you might want to replace <code>/home/.ecryptfs</code> with
<code>/var/lib/ecryptfs</code>.</p>
ZSNES on AMD64 Ubuntuhttps://rohieb.name/blag/post/zsnes-on-amd64-ubuntu/rohieb
CC-BY-SA 3.0
2019-05-05T21:56:21Z2010-10-05T22:00:00Z
<p><strong>[ Update, 2013-10:</strong> 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: <code>sudo apt-get install
zsnes:i386</code>. For details see the MultiArch documentation for
<a href="https://wiki.debian.org/Multiarch/">Debian</a> and <a href="https://help.ubuntu.com/community/MultiArch">Ubuntu</a>. <strong>]</strong></p>
<p>Before I 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 <img src="https://rohieb.name/smileys/sad.png" alt=":(" /> 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 <a href="http://board.zsnes.com/phpBB3/viewtopic.php?p=118067&sid=dd9a2a54d9178eb5009c33586aea703c#p118067">try to compile for 32-bit systems</a>, you get errors
about missing 32-bit libs (in particular, configure does not find a
suitable <code>libsdl</code>). Instead, if you just take the binary which was
compiled on a 32-bit system, and install the <code>ia32-libs</code> package,
everything seems to work—at least I was able to play a few levels of
Super Mario World succesfully <img src="https://rohieb.name/smileys/smile.png" alt=":-)" /> </p>
<p>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 :P
And as it turned out, this idea worked great. You can get the Debian
package here if you want, it <em>should</em> work for Ubuntu Karmic and Lucid,
as well as for Debian testing (<strong>but</strong> I only tested it on Lucid, so
there is no warranty here—but I’m happy to hear if it works :-)):</p>
<ul>
<li><a href="http://rohieb.name/stuff/zsnes_1.510-2.2ubuntu3~ppa1_amd64.deb">zsnes_1.510-2.2ubuntu3~ppa1_amd64.deb</a></li>
<li>SHA1: <code>716bbd37267b477ef02961a7727212619309b83f</code></li>
<li>MD5: <code>452ea5230ad17df1dee649ab4cc6c8c0</code></li>
</ul>
<h2 id="howtoreproduceit">How to Reproduce It</h2>
<p>For the curious people reading here, here is what I actually did:</p>
<ol>
<li><code>wget http://archive.ubuntu.com/ubuntu/pool/universe/z/zsnes/zsnes_1.510-2.2ubuntu3_i386.deb</code></li>
<li><code>ar x zsnes_1.510-2.2ubuntu3_i386.deb</code></li>
<li><code>tar xzf data.tar.gz</code></li>
<li><p>Edit <code>usr/share/applications/zsnes.desktop</code> and added <code>-ad sdl</code> to the
<code>Exec:</code> field, otherwise it would just segfault on the first run:</p>
<pre><code>Exec=zsnes -ad sdl
</code></pre></li>
<li><p>Edit <code>usr/share/doc/zsnes/changelog.Debian.gz</code> and added a new
changelog entry for the version (just copy one of the previous
entries and adapt it)</p></li>
<li><code>tar xzf control.tar.gz</code></li>
<li><p>Edit the <code>control</code> file, changed the <code>Version:</code> and <code>Architecture:</code>
field to <code>amd64</code>, added the <code>ia32-libs</code> dependency, and set myself as
maintainer:</p>
<pre><code>Package: zsnes
Version: 1.510-2.2ubuntu3~ppa1
Architecture: amd64
Maintainer: Roland Hieber <foobar@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:1.2.2.3)
[...]
</code></pre></li>
<li><p>Change the <code>md5sums</code> file for the right values for
<code>usr/share/applications/zsnes.desktop</code> and
<code>usr/share/doc/zsnes/changelog.Debian.gz</code> (I used the <code>md5sum</code>
command and copy-pasted it)</p></li>
<li><code>tar czf control.tar.gz control md5sums postrm postinst</code></li>
<li><code>tar czf data.tar.gz usr/</code></li>
<li><code>ar r zsnes_1.510-2.2ubuntu3~ppa1_amd64.deb debian-binary
control.tar.gz data.tar.gz</code></li>
</ol>
<p>I’m afraid that I can’t put the package into <a href="https://launchpad.net/~rohieb/+archive/ppa">my PPA</a>, 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.</p>
Standby with Lenovo Thinkpad SL510 on Ubuntu Lucidhttps://rohieb.name/blag/post/standby-with-lenovo-thinkpad-sl510-on-ubuntu-lucid/rohieb
CC-BY-SA 3.0
2013-09-19T05:04:01Z2010-07-29T22:00:00Z
<p>…note to myself: Remove a potentially mounted SD card before suspending
your SL510, otherwise the kernel gets stuck…</p>
<p><strong>Update:</strong> Turned out the SD card was a bit buggy, the driver mostly
got a timeout when trying to speak with it.</p>
Kaffeine 0.8.7 in Ubuntu Karmichttps://rohieb.name/blag/post/kaffeine-0-8-7-in-ubuntu-karmic/rohieb
CC-BY-SA 3.0
2013-09-19T05:04:01Z2010-03-06T23:00:00Z
<p>As I <a href="https://rohieb.name/blag/post/ubuntu-karmic-upgrade-issues/">recently mentioned</a>, Kaffeine in
Ubuntu Karmic is the (nearly) unusable version 1.0~pre2. I have
backported the Jaunty version 0.8.7 to Karmic and put it into my
<a href="https://launchpad.net/~rohieb/+archive/kaffeine-0.8">Launchpad PPA</a>.</p>
Ubuntu Karmic upgrade issueshttps://rohieb.name/blag/post/ubuntu-karmic-upgrade-issues/rohieb
CC-BY-SA 3.0
2013-11-09T04:11:26Z2010-01-16T23:00:00Z
<p>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.</p>
<p>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:</p>
<ul>
<li><p>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 <a href="https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/499938">bug report</a> on that.
Futhermore, my DVB-T channels were lost, so I had to rescan them.</p></li>
<li><p>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 <a href="https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/419894">bug report</a>, 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.</p></li>
<li><p>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”.</p></li>
<li><p>GDM is no longer customizable through themes. It just doesn’t support
it, as it seems to be a <a href="http://ubuntuforums.org/showthread.php?p=7854130">complete rewrite</a>. IMHO just another
Unmature Software Thing.</p>
<p><strong>Edit:</strong> I just found out that it is also not able to start GDM in
Xnest, as I usually did for testing:</p>
<pre><code>$ gdmflexiserver --xnest
** (gdmflexiserver:5916): WARNING **: Not yet implemented
</code></pre></li>
<li><p>And finally, my customized GNOME window theme (based on Clearlooks)
was broken <img src="https://rohieb.name/smileys/sad.png" alt=":-(" /> 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.</p></li>
</ul>
Greetings from GNOMEhttps://rohieb.name/blag/post/greetings-from-gnome/rohieb
CC-BY-SA 3.0
2013-09-19T05:04:01Z2009-12-26T23:00:00Z
<p>Now this is really useful: there is a <a href="http://www.gnome.org/~seth/gnome-blog/">GNOME panel applet</a> for
writing blog posts (for the Debian/Ubuntu folks: it’s in the package
<code>gnome-blog</code>). Just gotta try it out <img src="https://rohieb.name/smileys/smile.png" alt=":-)" /></p>
<p><strong>Edit:</strong> Unfortunately, there is no possibility to assign tags or
categories this way <img src="https://rohieb.name/smileys/sad.png" alt=":-(" /></p>
Sync your Windows Mobile 5/6 PDA with your Linux PChttps://rohieb.name/blag/post/sync-your-windows-mobile-5-6-pda-with-your-linux-pc/rohieb
CC-BY-SA 3.0
2013-11-09T04:11:26Z2009-10-29T23:00:00Z
<p>I recently bought a new (ok, a rather old ;-)) PDA, and I got used to
the calendar and task features in Windows Mobile. Of course, I also
wanted to synchronise all the tasks, appointments, contacts and files
with my PC, but whatever I tried, it didn’t work somehow on my Ubuntu
9.04 machine… So, I’ve got it now: I had do blacklist the <code>ipaq</code> kernel
module which wrongly handled the PDA when I plugged it in (i. e.
edit <code>/etc/modprobe.d/blacklist.conf</code> and insert the line <code>blacklist
ipaq</code>), and then the <a href="http://wiki.ubuntuusers.de/Archiv/Synchronisation_mit_Windows_Mobile">manual from ubuntuusers.de</a> suddenly worked
like a charm <img src="https://rohieb.name/smileys/smile.png" alt=":-)" /> </p>