I took some notes where I had to deviate from the release notes which might be helpful to both me and you.
GeneralI accepted the default for any prompts that were given.
Note that the upgrade created new configuration files. After the upgrade, I replaced configuration files with the new ones and merged my changes into them. Here's what I ran to identify them:
sudo find /etc -name '*.dpkg-*' -o -name '*.ucf-*'
In the spirit of keeping a minimal server, the last step after the reboot, configuration file cleanup, and performing the tasks in section 4.10, Obsolete packages, was to remove any packages that had been installed as part of the upgrade that aren't necessary.
One way to do that is to run one or both of the following commands. The first that lists the packages you have explicitly installed while the latter lists all packages which have been installed. Do this before and after the upgrade, diff, and remove any packages you don't want.
aptitude search '!(!~i|~M)' -F %p
dpkg --get-selections |grep install
Since I maintain my system files with Subversion, I also
ran svn diff / (which might not be useful on your
system). This identified new files that seemed suspicious. For
example, /etc/cups, I don't print from my server
:-). I used dpkg --search file to identify
the package that referred to these suspicious files.
Finally, use deborphan --guess-all to identify
additional packages that can be removed. If it lists packages
you installed, use
deborphan -A package to tell deborphan that
you need it.
The release notes don't give an example, but here is what they meant:
Package: *
Pin: release a=stable
Pin-Priority: 1001
If you don't have /etc/apt/preferences, consider
adding it with this for its sole contents. Comment it out after
the upgrade for next time. The comment character is
"Explanation:" :-).
Here is the /etc/apt/sources.list file that I used
for the upgrade.
deb http://mirrors.xmission.com/debian/ lenny main non-free contrib
deb-src http://mirrors.xmission.com/debian/ lenny main non-free contrib
deb http://security.debian.org/ lenny/updates main contrib non-free
deb-src http://security.debian.org/ lenny/updates main contrib non-free
Please don't use as is; rather use an example of what is described in the release notes. In particular, your mirror might be different. Note that I changed etch to lenny and commented out the non-critical sources to make the upgrade go as smoothly as possible. I'll leave the other sources commented-out until needed since lenny has the stuff I was getting from backports and sid.
Release Notes: 4.5.6. Minimal system upgrade
The sudo aptitude safe-upgrade command issued the
following errors:
The following packages have unmet dependencies:
libgl1-mesa-swx11: Conflicts: libgl1 which is a virtual package.
libgl1-mesa-glx: Conflicts: libgl1 which is a virtual package.
I resolved this by running:
sudo aptitude purge libgl1-mesa-swx11 libgl1-mesa-glx xbase-clients
I reinstalled xbase-clients after the upgrade.
Release Notes: 4.5.7. Upgrading the rest of the systemThis went swimmingly!
After running sudo aptitude dist-upgrade, I ran the
following (mentioned at the end of this section) to ensure things were
clean.
sudo aptitude -f install
This removed the now-unused libio-zlib-perl package.
Release Notes: 4.8.1. How to avoid the problem before upgradingI didn't want to take the chance of a hanging reboot. Since UUIDs are the wave of the future, I opted to follow the instructions in the section "To implement the UUID approach:."
The instructions aren't correct. I got an error when I ran update-grub
after updating menu.lst. After replacing /dev/hda* with
UUIDs for / and /boot
in /etc/fstab, update-grub ran fine.
In addition, I also the following commands to do the same thing with
swap (where /dev/hda5 is the device associated with swap
in /etc/fstab). First I disabled some low priority
processes to avoid using swap.
sudo swapoff -a
sudo mkswap /dev/hda5
The output of the mkswap command provided a UUID that I could use for
the swap entry in /etc/fstab. I then ran the following to
turn swap on:
sudo swapon -a
I then pulled the trigger and rebooted. It worked!
After the reboot, my devices where still /dev/hda{1,5,6} so I would have been OK had I not done this. However, you have newer hardware, so perhaps the problem described might be an issue for you. Or not. It's possible that the problem described might have only been a problem from someone upgrading from, say, a 2.4 kernel.
This can be done completely in XSane. In XSane, select the Multipage mode. Select a working directory and press Create project (the PDF will be written in the directory containing this working directory). Use XSane as usual, including using Acquire Preview to select your scan area and pressing Scan to initiate the scan(s). Press the Save multipage file button in the multipage project dialog when you're done to create the PDF.
Setting the Scansource choice to Automatic Document Feeder can be very helpful. In this case, setting the ADF-Pages item to the number of pages in your hopper (or larger) makes XSane scan the pages automatically. Once XSane stopped when it was done scanning; another time it honored my ADF-Pages setting (and dutifully scanned dozens of blank images) so it is prudent not to make this number too large.
The links below describe some pretty fancy ways to turn scans into PDF documents, which are useful for bulk scanning of books and magazines. However, if you aren't scanning that much, creating PNGs (for text) or JPGs (for images) from the scans and running the following command is sufficient:
convert *.png *.jpg document.pdf
I'd suggest using 300 DPI if you plan to print the document. If you're only going to view the document on the screen, you can create smaller documents by scanning at 150 DPI and/or by choosing a Scanmode of Gray.
References:
Creating multi-page PDF documents from scanned images in
Linux
How to create ebooks with Linux
How to scan printed papers and to create Metadata
I recently tried to put together a few videos taken on an iPhone in cinelerra, but the sound in the exported video was corrupted. Kino, however, exported useful video and audio.
And today, I wanted to remove some bits of a video. Again kino made it easy to do. I loaded the video, selected the edit mode, used the cursor and arrow keys to pick frames, pressed the Split scene button at the beginning and end of each scene that I wanted to delete, and then pressed the Cut scene button. Note that the Split scene button creates the split before the selected frame. I then exported the video using H.264 MP4 Dual Pass Tool (Export button, Other tab). According to Optimizing your video uploads, this is a preferred YouTube format.
Please refer to Scott Hanselman's How to rotate an AVI or MPEG file taken in Portrait to see how to rotate a video.
My references include Robbie Ferguson's YouTube video and Kevin Andle's page on creating an envelope in OpenOffice.
The following update to GNOME's select-by-word characters setting in the Edit profile command lets you select an entire email address or URL (including Subversion svn+ssh URL) by simply double-clicking on it.
-A-Za-z0-9,./?%&#:_@+
I got the following message when I tried to load a Subversion dump:
svnadmin: Unable to parse unordered revision ranges '9414-9445' and '7044-8971'
I discovered that I had some uncommitted transactions from years
past using the svnadmin lstxns command. I cleaned
them up with the following command, but this did not fix the
problem.
sudo svnadmin rmtxns /repos/main $(svnadmin lstxns /repos/main)
I then performed svn info file:///var/tmp/foo on
the temporary repository I was loading and observed that the
last revision was 9547. I then went into the dump file and
looked for the next revision, 9548, to see what may have caused
the problem. I found the smoking gun!
K 13
svn:mergeinfo
V 177
/home/wohler/branches/common:6912-7042
/home/wohler/branches/tassie:6913-7043
/home/wohler/common:7043-9259
/home/wohler/sydney:8972-9413
/home/wohler/tassie:9414-9445,7044-8971
PROPS-END
Ah ha! Note how the revisions for the tassie branch are swapped. I fixed this by editing the Subversion database. Note that I use FSFS. I'm not sure if this would be possible with BDB.
$ diff db/revs/9548.orig db/revs/9548
--- db/revs/9548.orig 2008-11-15 14:03:54.000000000 -0800
+++ db/revs/9548 2009-04-25 12:08:43.000000000 -0700
@@ -181,7 +181,7 @@
/home/wohler/branches/tassie:6913-7043
/home/wohler/common:7043-9259
/home/wohler/sydney:8972-9413
-/home/wohler/tassie:9414-9445,7044-8971
+/home/wohler/tassie:7044-8971,9414-9445
END
ENDREP
id: 3zl.x0.r9548/2049
I grepped for that same string and found it in revision 9590 as well. I performed a similar fix.
I verified the fix with the following:
$ svnadmin create foo
$ svnadmin dump --quiet /REPO | svnadmin load --quiet foo
$ svn log -v file:///REPO > repository.log
$ svn log -v file:///var/tmp/foo > temp.log
$ diff repository.log temp.log
$
I vaguely remember having similar troubles in the past after I converted from the svnmerge properties to the built-in Subversion 1.5 svn:mergeinfo property. At the time, I think I made a similar change to the svn:mergeinfo property manually and checked in the change. I am not sure if the problem was caused by the svnmerge conversion script or by Subversion 1.5 itself.
It's also possible that the svn:mergeinfo property was munged by the bug described in svn: Working copy path 'foo' does not exist in repository.
The moral of the story is that after you convert from svnmerge to Subversion's built-in merge tracking, do inspect the svn:mergeinfo property after the svnmerge conversion. If you see that the revision numbers are not in order, fix them as described above. Also inspect the svn:mergeinfo property after subsequent merges--particularly if you hit any Subversion bugs--before you commit the changes. If you see that the revision numbers are not in order, simply edit the svn:mergeinfo property before you check it in.
My Canon G9 can shoot AVI movies. I recently shot a video that I wanted to edit. I just needed to chop bits out at the beginning and end. However, it might be useful to be dub in audio in the future. A quick Google search and apt-cache search turned up the following:
I was able to run GoogleEarth, a 32-bit binary, on my system by
first performing the actions described
in Running 32-bit binaries on a
64-bit Debian system. I then ran the following commands as
described
in Debian
bug #514122. Note that it isn't necessary to link
libcrypto.so.0.9.8 to the installed copy.
$ cd /usr/lib/googleearth/
$ sudo mv libcrypto.so.0.9.8 libcrypto.so.0.9.8-
If GoogleEarth freezes up your system, as it did to mine, ensure
that lib32nss-mdns is installed. Then
remove .googleearth and rerun
make-googleearth-package --force (like many others,
I got lots of warnings about shared libraries not being
available when I ran this command; I ignored them). Move
libcrypto.so out of the way as described above and try again.
Since then GoogleEarth has frozen up my system once or twice so you might just try restarting GoogleEarth without bothering to follow the instructions in the previous paragraph. I've since found that GoogleEarth works fine for a period of time after a reboot (without repeating the above steps). I'm hoping that a real 64-bit version will clear this up for good.
Not sure why GoogleEarth continues to complain about not being
able to create .googleearth after it creates it!
I was able to run GoogleEarth, a 32-bit binary, on my 64-bit system after running the following.
$ sudo aptitude install ia32-libs ia32-libs-gtk lib32nss-mdns
I've also read that you have to install Skype as follows (although I have not yet done this).
$ sudo dpkg -i --force-architecture skype-debian_2.0.0.72-1_i386.deb
This error is described in Debian bug #490395. Until the patch contained within is applied to Debian, apply the patch yourself. It's really easy.
There are two ways to enable Emacs keybindings in Iceweasel
(Firefox). The first is the GNOME way. Run gconf-editor,
edit the /desktop/gnome/interface/gtk_key_theme
key, and change it from Default
to Emacs.
The GTK way is to append the following
to ~/.gtkrc-2.0 and restart Iceweasel.
include "/usr/share/themes/Emacs/gtk-2.0-key/gtkrc"
gtk-key-theme-name = "Emacs"
The error listed in the title is due to a Subversion bug, which has been fixed in 1.6. The bug was triggered for me when I moved a file in the trunk, merged the renamed file into a branch, and then later tried to merge the branch back into the trunk.
I found a workaround that can be used if you still have 1.5. For me, the renamed file was merged into the branch in revision 9739. Normally, I'd issue the following command to merge the branch back into the trunk:
$svn merge branch-URL
However, this doesn't work in this scenario. The workaround is to avoid including the revision of when the trunk was merged into the branch. This is fine because the trunk already has the changes. In the example, revision 9688 is the last revision merged into the trunk, and 9750 is the HEAD version on the branch (or simply the largest revision in your repository).
$svn merge -c9739 --record-only branch-URL
$svn merge -r9688:9738 -r9739:9750
Although Eclipse seemed to be well-behaved on a 64-bit etch system with Java 6, after upgrading to lenny, it started crashing all the time. I found that the crashes went away after uninstalling Subclipse. But I found a better workaround. My crashes had the following signature:
# SIGSEGV (0xb) at pc=0x00007f762d5c225a, pid=2534, tid=1091451216
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b23 mixed mode
linux-amd64)
# Problematic frame:
# V [libjvm.so+0x1f125a]
...
Current CompileTask:
C2:715
org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith(
[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;
[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;
Lorg/eclipse/core/internal/dtree/IComparator;)
[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;
(469 bytes)
I was able to work around this problem by not compiling the
method listed above. I launch eclipse from a script, so I added
-XX:CompileCommandFile to eclipse's args as follows:
exec ./eclipse "$@" -vmargs -Xmx1500M -XX:MaxPermSize=256M \
-XX:CompileCommandFile=/usr/local/etc/hotspot
The file /usr/local/etc/hotspot contains:
exclude org/eclipse/core/internal/dtree/DataTreeNode forwardDeltaWith
This file is handy if you have several methods to list. If you only have one, you can do this instead:
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
Finally, you can add either of these arguments to
your eclipse.ini in Eclipse's installation
directory.
Earthlink, and some other knaves who maintain root nameservers, have a really annoying "feature" in which they return the IP address of one of their search pages if you enter a bogus hostname in your browser's location bar.
The problem is that this breaks the feature in browsers like Firefox which try prepending a www if the host lookup fails. This is also annoying to the user since instead of fixing a simple typo, the user has to clear the bogus URL provided by Earthlink and re-enter the URL.
I found a way to subvert Earthlink's subversion:
the dnsmasq program is a caching-only nameserver which
has a feature which translates bogus IP addresses to NXDOMAIN
DNS records. I configured /etc/dnsmasq.conf as
follows (note that I do not have any programs that
update /etc/resolv.conf):
no-resolv
server=192.168.1.1
bogus-nxdomain=207.69.131.10
bogus-nxdomain=207.69.131.9
I then edited /etc/resolv.conf as follows:
search newt.com
#nameserver 192.168.1.1
nameserver 127.0.0.l
Here is what the host command on a bogus host
returned before I made this change:
$ host lskjdflkdsjf.com
lskjdflkdsjf.com has address 207.69.131.10
lskjdflkdsjf.com has address 207.69.131.9
Host lskjdflkdsjf.com not found: 3(NXDOMAIN)
;; connection timed out; no servers could be reached
And here is what it looks like now, and how it should have looked like in the first place!
$ host lskjdflkdsjf.com
Host lskjdflkdsjf.com not found: 3(NXDOMAIN)
As a nice side-effect, the dnsmasq server also insulates me from transient DNS outages to Earthlink which was seen in the previous example.
I had a problem whereby the host in the URL would randomly be rewritten with www.newt.com, my domain. I suspected that Firefox wasn't getting to DNS and had some sort of "feature" for rewriting the host part. I was partially right.
I suspect that when there was a transient DNS error,
the search newt.com directive
in /etc/resolv.conf would cause the host in the URL
to be rewritten with my domain appended. Because of the wildcard
entry in my zone file, my web server's address would be
returned. My web server then rewrote the address with
www.newt.com as the host.
I deleted the wildcard entry and the problem disappeared as soon as the change propagated down to my local nameservers.
After a recent upgrade or something, I noticed that my Bluetooth
light on my ThinkPad was out and Fn-F5 didn't turn it on. I was
able to enable Bluetooth manually with the following command
(which should have been executed
by /etc/acpi/ibm-wireless.sh):
sudo sh -c 'echo "enabled" >| /proc/acpi/ibm/bluetooth'
So, why didn't this script run when Fn-F5 was pressed?
With the help of HOWTO Dual Monitors, I was able to simply add the three Option lines to my xorg.conf as shown below, restart my X server, and be on my way.
Section "Device"
Identifier "nVidia Corporation NV44 [Quadro NVS 285]"
Driver "nvidia"
Option "TwinView"
Option "MetaModes" "1920x1200,1680x1050; 1920x1200,1280x1024; \
1600x1200,1600x1200; 1280x1024,1280x1024; 1152x864,1152x864; \
1024x768,1024x768; 800x600,800x600; 640x480,640x480"
Option "TwinViewOrientation" "RightOf"
EndSection
The MetaModes line is actually all on a single
line.
Although I could print, I could not longer scan, and the HP Device Manager from the system tray couldn't communicate with my printer either. I was seeing the following error message in syslog:
python: hp-toolbox(UI)[6561]: error: Unable to communicate with device
(code=12): hp:/usb/OfficeJet_G85?serial=SGG16E0ZRVVL
python: hp-toolbox(UI)[6561]: warning: Device not found
As of version 2.8.2 of hplip, all communications to the hp:
device is now confined to members of the scanner group.
Therefore, the fix was to run sudo adduser wohler
scanner, log out, and log back in.
After installing a new system, man started emitting these ugly
<80><90> escapes all over the place. I finally found the cause.
I had LC_ALL set to en_US.utf8
but LESSCHARSET was still set
to latin1. The fix was to
change LESSCHARSET to utf-8.
I finally got around to configuring SMTP AUTH (SASL) in postfix.
pwcheck_method: saslauthd
mech_list: plain login
# TLS parameters.
smtpd_tls_security_level = may
smtpd_tls_auth_only = yes
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache
# SMTP AUTH parameters.
smtpd_sasl_auth_enable = yes
smtp_sasl_security_options = noanonymous
START=yes
OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd"
# aptitude install sasl2-bin libsasl2-modules
# dpkg-statoverride --add root sasl 710 /var/spool/postfix/var/run/saslauthd
# adduser postfix sasl
[mail.your-domain.com]:smtp your-login:your-password
[mail.your-domain.com]:submission your-login:your-password
# SASL
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl/sasl_passwd
smtp_sasl_security_options = noanonymous
# TLS
smtp_tls_security_level = encrypt
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
postmap /etc/postfix/sasl/sasl_passwd and
restart postfix.
See the following references for the whys and wherefores:
James Turnbull, Hardening Linux, 2005, p. 395-400.
Luca Gibelli
<nervous at nervous.it>, http://www.nervous.it/txt/Postfix-SMTP-AUTH-4-DUMMIES.html.
Fabian Fagerholm <fabbe at debian.org>, /usr/share/doc/sasl2-bin/README.Debian.
http://www.postfix.org/SASL_README.html.
I was trying to use a feature at Bank of America's Homebanking
(SafePass) and it didn't work for me. First I had to install
Flash 9. But I also discovered that the site was also not
recognizing my Iceweasel browser. I was able to fix this and
enable SafePass by navigating to the
URL about:config, filtering on
"agent", and changing
the general.useragent.extra.firefox setting from
Iceweasel/2.0.0.14 to Firefox/2.0.
The ath5k driver for the Atheros wireless chipset is built into kernel 2.6.24. Remove madwifi-tools, or switch blacklist in /etc/modprobe.d/madwifi. modprobe -r ath* wlan*. modprobe ath5k. http://linuxwireless.org/en/users/Drivers/ath5k. http://madwifi.org/wiki/About/ath5k
I wanted a list of packages on my current system so just in case I needed to recreate my entire system, I could just say
aptitude install $(cat packages)
Of course I don't want automatically installed packages
in packages. Thanks to Scott Wegner on
the Ubuuntu
forums, here's how I created the packages file:
aptitude search '!(!~i|~M)' -F %p > packages
I installed 2.6.25 from sid since it didn't pull in anything else.
A while ago I installed 2.4.24. While it fixed the problem where gpsbabel could not talk to the usb: device, I found that my wireless (Atheros) connection would drop after a while. The network with 2.6.22 was fine. A second 2.4.24 update fixed the network problem, but a third 2.4.24 update broke it again.
Against my better judgment, I remotely interrupted an aptitude
session so that I could continue with the installation at my
current location. This put the package that was being installed
into the half-installed state. After this, aptitude
responded with:
Writing extended state information... Error!
E: I wasn't able to locate a file for the sun-java6-bin package.
This might mean you need to manually fix this package. (due to missing arch)
E: Couldn't lock list directory..are you root?
After a bit of investigation, I discovered how to fix the dpkg database:
sudo dpkg --force-remove-reinstreq --remove sun-java6-bin
When I last installed lenny, I opted for the encrypted LVM
filesystems. I recently ran out of room in /usr so
I now had the opportunity to use LVM! I was apprehensive that
the LUKS (Linux Unified Key Setup) encryption might get in the way,
but since I wasn't dealing with the root filesystem, it wasn't
an issue since I was able to work with the running system.
I learned that changes must be done in 4 MB increments, the size of the physical extent. In my ignorance and inexperience, I was nervous that the size given to resize2fs might round up and the same size given to lvreduce would round down which would mean that the end of the filesystem would get guillotined. I picked even gigabyte values mostly because resize2fs doesn't accept fractional values, but a gigabyte is divisable by the 4 MB extent size and the 512 byte disk sector size as well as any other unit the system might throw at me. If you choose megabytes as your unit, ensure the value is divisible by four. At any rate, I threw in an extra fsck at the end of each operation for paranoia and all seemed to go well.
I first had to decide how much space to transfer. I'm running
out of space on my laptop, so I didn't want to steal much
from /home. I
ran lvs, df, and df -h to
get some numbers. I decided that 500 MB would be enough, so I
first needed to reduce /home from 44.5 GB to 44 GB.
# lsof
# kill [any processes still running out of /home]
# umount /home
# fsck -f /dev/mapper/olgas-home
# resize2fs -p /dev/mapper/olgas-home 44G
# lvreduce [--test] -L 44G olgas/home
# fsck -f /dev/mapper/olgas-home
# mount /home
Note the --test lvreduce argument above. I used
that first to see what lvreduce would do. It's more useful when
you aren't using gigabytes as a unit. You'll see what I mean
when you run lvextend in the next example.
I then ran vgs (and vgdisplay) to see
the Free Size which should now be around 500 MB. It was 788 MB
in this case and that's the number I used to
grow /usr in the lvextend command below.
# shutdown now "Resizing filesystems"
# lsof /usr
# kill [any /usr processes still hanging around]
# umount /usr
# fsck -f /dev/mapper/olgas-usr
# lvextend [--test] -L +788M olgas/usr
# resize2fs -p /dev/mapper/olgas-usr
# fsck -f /dev/mapper/olgas-usr
# mount /usr
I then opted for a quick reboot so that if that caused trouble,
it would be now rather than when I least expected it. When the
system returned, df showed that I once again had breathing room
in /usr. While it took a while this time around for
me to think I knew what I was doing, the next time, it'll go
quickly. Unless it's the root filesystem, in which case I'll
have to learn how to turn on LUKS when running with a Live CD.
References:
AJ Lewis, LVM HOWTO,
http://www.tldp.org/HOWTO/LVM-HOWTO/
.
Bodhi Zazen, How to Resize a LUKS Encrypted File System,
http://ubuntuforums.org/showthread.php?t=726724
.
Martti Kuparinen, Hard Drive Encryption in My Ubuntu
Installation,
http://users.piuha.net/martti/comp/ubuntu/en/cryptolvm.html
.
I just learned the difference between /dev/random
and /dev/urandom. Use the former when you need
strong randomness for keys; use the latter when you need speed
and don't expect the bits to be broken (like when scattering
random bits on a cleaned disk partition or when preparing the
partition for encryption).
This morning, ssh worked without having to run ssh-add, which is
strange because I expire my passphrase. I then ran ssh-add and
got a SSH_AGENT_FAILURE message. Apparently,
gnome-keyring usurped ssh-agent as reported
in BTS
#473864.
Until I learn more about gnome-keyring, I've disabled the ssh
component as Josh Triplett suggested by unsetting the gconf key
/apps/gnome-keyring/daemon-components/ssh. You can
do this in gconf-editor, or run the following
command:
gconftool-2 --set /apps/gnome-keyring/daemon-components/ssh false --type=bool
I was spurred on by Tommy Trussell to enable syncing over USB so that I could take advantage of the sync button on the cradle and because it's much, much faster than using net: over Bluetooth.
When I plugged in the Treo and hit the button on the cradle,
there wasn't a single message in the syslog and lsusb didn't
list the device either. I found that if you
unload ehci_hcd, then the system recognizes the
Treo. However, after a reboot, I found that my system recognized
the Treo (under uhci_hcd) even though
the ehci_hcd module was still loaded, so all is
well.
I also found that pilot-xfer -l -p usb: didn't
connect initially. It seems that the first time you HotSync, you
need to run the pilot-xfer command before starting HotSync on
the Treo. After that first time, the order doesn't matter.
I've updated Using the Palm Treo 650 with Debian GNU/Linux accordingly.
In order to get the usb: filename to work with gpsbabel,
follow the directions
in Hotplug
vs. Garmin USB on Linux, namely, add the following
to /etc/modprobe.d/local:
blacklist garmin_gps
And add the following
to /etc/udev/rules.d/51-garmin.rules:
SYSFS{idVendor}=="091e", SYSFS{idProduct}=="0003", MODE="0666"
However, while this worked for kernel 2.6.18, later kernel versions broke it! It is still not working as of 2.6.22.
Newsflash! I inserted the garmin_gps module and
tried using /dev/ttyUSB0 instead
of usb: and I was able to back up the Garmin! It
appears that this driver has been repaired--somewhat--along the
way. I still had some errors uploading routes, although with
persistence, they eventually all arrived. I wasn't brave (or
stupid) enough to try uploading large tracks or waypoint files
though. So, I'll probably still try the usb: file
again once 2.6.24 is installed.
My router's DHCP table was showing a blank where my laptop's
hostname should be. I fixed this by uncommenting the send
host-name line in /etc/dhcp3/.
I just made a donation to the Software Freedom Law Center. Consider making a donation yourself.
I was getting errors like dund[31782]: Failed to connect to the local SDP server. Connection refused(111) in my syslog and HotSyncs that were failing with Faulty modem. I worked around this problem by running the following commands:
$ sudo killall dund
$ sudo /usr/bin/dund --listen --persist --auth call treo
I've reported the bug as BTS #452869.
The AIDE that comes with etch is very hard to keep quiet. Marc Huber suggested that the lenny version might be a bit quieter, so I ran the following to get the latest and greatest on my etch system:
apt-get source aide
aptitude install dpatch libmhash-dev flex libgcrypt-dev
(cd aide-0.13.1 && fakeroot dpkg-buildpackage -b -uc)
sudo dpkg -i aide_0.13.1-8_i386.deb aide-common_0.13.1-8_all.deb
These commands are listed here mostly so that I can clean up if aide 0.13.1-8 hits backports.
I could mount data CDs, play DVDs with totem, and play audio CDs with gnome-cd. However, I was not getting the usual CD icon in rhythmbox when an audio CD was inserted, and sound-juicer produced a No CD-ROM drives found--Sound Juicer could not find any CD-ROM drives to read message and exited.
Both rhythmbox and sound-juicer played CDs just fine a week before my disk crashed and I reinstalled lenny from scratch.
I found that rebooting cleared this problem.
My disk crashed on Friday so I bought a new one and installed lenny from scratch. One problem I encountered is that the top of the PDF printed from Gnucash was truncated. It seems that this was observed by others in the gmane.linux.debian.user thread entitled Text on printed pages truncated with Message-ID 45A2C319.8020400@heard.name.
Interestingly, after I configured my printer in CUPS, this problem went away. This was confirmed by one of the installation gurus:
Jim Paris <jim@jtan.com> wrote:
> Interestingly, the top of Gnucash reports printed to PDF were truncated
> until I installed a printer in CUPS, and then the problem disappeared.
> Is a CUPS installation default suboptimal?
Maybe it was a paper size issue, and installing a printer changed your
default papersize? You can change the current setting with
"dpkg-reconfigure libpaper1". I noticed in your system information:
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
If LC_ALL was set to C during installation, I think libpaper1 would
have defaulted to A4 (because "locale width" and "locale height"
return A4 size in that case)
On one of my etch systems, I got this error message after a
recent upgrade. (I did not get it on my etch server, nor my
lenny laptop.) I fixed this by adding the following
to /etc/apt/apt.conf:
Cache-Limit "20000000";
I installed Linux kernel version 2.6.22 and found that
the ibm_acpi module was renamed
to thinkpad_acpi. Unfortunately, this broke the
Fn-F4 hotkey combination used to suspend my laptop. I'm assuming
that Debian
Bug report #434845: acpi-support: ibm_acpi module renamed
thinkpad_acpi in kernel 2.6.22 is related, but the suggested
fix didn't work for me. The GNOME Shut Down menu item does work
however.
Gpsbabel still doesn't work--I'm keeping a version of 2.6.18 around for it. This might be related to the CONFIG_USB_SUSPEND problems that have been reported. But then, it could be CONFIG_USB_SUSPEND which fixed suspending under ACPI on my ThinkPad.
If your ISP (such as Earthlink) blocks port 25, and someone else in your household controls the authentication credentials and understandably does not want to share them with you, how do you send mail?
I got my hosting company to poke a hole in port 587 (submission) and then updated postfix on my laptop and on the server as follows:
master.cf (on server my.relayhost.com)
submission inet n - - - - smtpd
main.cf (client)
relayhost = [my.relayhost.com]:587
Note that I use pop-before-smtp for authentication.
Thanks to a post on gmane.linux.debian.user.laptop from Stefan
Monnier, I installed the hibernate package, and created a file
called
/etc/hibernate/scriptlets.d/local which contains
the following code which turns off the Ultrabay LED. If you want
to use it, replace my initials (BW) with your own since the
hibernate namespace is global.
# -*- sh -*-
# vim:ft=sh:ts=8:sw=4:noet
# Ideas from /usr/share/hibernate/scriptlets.d/hardware_tweaks.
# ibm_acpi proc directory
BW_IBM_ACPI_PROC=/proc/acpi/ibm
BwIbmAcpiStartSuspend() {
# Turn off Ultrabay LED.
IbmAcpiLed 4 off
return 0 # this shouldn't stop suspending
}
BwIbmAcpiEndResume() {
# Turn on Ultrabay LED.
IbmAcpiLed 4 on
return 0
}
BwIbmAcpiOptions() {
if [ -d "$BW_IBM_ACPI_PROC" -a -z "$BW_IBM_ACPI_HOOKED" ]; then
AddSuspendHook 12 BwIbmAcpiStartSuspend
AddResumeHook 12 BwIbmAcpiEndResume
BW_IBM_ACPI_HOOKED=1
fi
return 0
}
BwIbmAcpiOptions
I had found that with lenny and 2.6.21 kernel, ACPI suspend was
finally working. Yay! Further, I felt that the built-in power
management stuff might be working as well and I could remove
the acpid package dispense with
the /etc/acpi scripts since I was seeing some
gnome-power-management warnings in the syslog.
When I pressed Fn-F4 however, I got the message:
gnome-power-manager: (wohler) A security policy in place
prevents this sender from sending this message to this
recipient, see message bus configuration file (rejected message
had interface "org.freedesktop.Hal.Device.
SystemPowerManagement" member "Suspend" error name "(unset)"
destination ":1.22") code='9' quark='dbus-glib-error-quark'
After a little digging, I discovered that I had to add myself to
the powerdev group. Then I got this message:
gnome-power-manager: (wohler) Doing nothing because the suspend
button has been pressed
This was fixed by going into the gconf-editor and changing the
value
for /apps/gnome-power-manager/action_button_suspend
to suspend.
|
Copyright © 2007, 2008, 2009, 2010 Bill Wohler Last modified: 2010-02-15 18:20:18 -0800 About photos |
|