Category: Software

I’m not the only person affected by upgrade issues with dash /bin/sh diversion, but I thought I would document the behavior and quick fix for upgrading, since I just got bitten (again) by this on armel upgrading my sheevaplug this morning. See http://bugs.debian.org/538822 for lots of detail.

mshuler@sheeva:~$ sudo apt-get upgrade -V
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
   dash (0.5.5.1-6 => 0.5.5.1-7.2)
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/101 kB of archives.
After this operation, 4,096 B of additional disk space will be used.
Do you want to continue [Y/n]? 
Preconfiguring packages ...
(Reading database ... 19484 files and directories currently installed.)
Preparing to replace dash 0.5.5.1-6 (using .../dash_0.5.5.1-7.2_armel.deb) ...
Unpacking replacement dash ...
dpkg: error processing /var/cache/apt/archives/dash_0.5.5.1-7.2_armel.deb (--unpack):
 trying to overwrite '/bin/sh', which is also in package bash 4.1-3
configured to not write apport reports
                                      Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/dash_0.5.5.1-7.2_armel.deb
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB

Total disk space freed by localepurge: 0 KiB

E: Sub-process /usr/bin/dpkg returned an error code (1)

mshuler@sheeva:~$ dpkg-divert --list /bin/sh
local diversion of /bin/sh to /bin/sh.distrib
mshuler@sheeva:~$ readlink -f /bin/sh
/bin/dash
mshuler@sheeva:~$ ls -l /bin/sh.distrib
lrwxrwxrwx 1 root root 4 Sep 29 17:37 /bin/sh.distrib -> bash

remove the /bin/sh diversion and upgrade goes smoothly:

dpkg-divert --remove /bin/sh

mshuler@sheeva:~$ sudo dpkg-divert --remove /bin/sh
Removing 'local diversion of /bin/sh to /bin/sh.distrib'
mshuler@sheeva:~$ dpkg-divert --list /bin/sh
mshuler@sheeva:~$ readlink -f /bin/sh
/bin/dash
mshuler@sheeva:~$ sudo apt-get upgrade -V
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
   dash (0.5.5.1-6 => 0.5.5.1-7.2)
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/101 kB of archives.
After this operation, 4,096 B of additional disk space will be used.
Do you want to continue [Y/n]? 
Preconfiguring packages ...
(Reading database ... 19483 files and directories currently installed.)
Preparing to replace dash 0.5.5.1-6 (using .../dash_0.5.5.1-7.2_armel.deb) ...
Adding 'diversion of /bin/sh to /bin/sh.distrib by dash'
Unpacking replacement dash ...
Processing triggers for man-db ...
Setting up dash (0.5.5.1-7.2) ...
Removing 'diversion of /bin/sh to /bin/sh.distrib by dash'
Adding 'diversion of /bin/sh to /bin/sh.distrib by bash'
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB

Total disk space freed by localepurge: 0 KiB

mshuler@sheeva:~$

I’ve been using the Mozilla Thunderbird email client for many years and found a few annoyances upgrading from v2 to v3 – here are my gotchas and fixes for it to fit my email habits.

While I’m sure it’s great for most people and cases, if you have the slightest bit of complexity in how you might connect to your mail server(s), the auto-account-creation wizard blows.. With one personal email account (on my own mail server), the account setup wizard worked out most of the settings pretty closely, however, my work account and a couple others went haywire and set up everything completely wrong. If you let the wizard run for any amount of time, it attempts to find servers by DNS and writes the account profile to disk in the wrong place just because some DNS name exists. The trick is to enter your Name and Email account in the very first window, then get ready to mash Stop immediately after continuing on to the next window. Then you can hit Manual Setup and add all the settings correctly and things are written to disk in the correct locations, etc.. There really needs to be a Manual Setup option on that first account creation window that bypasses the auto-account discovery, or a config setting to disable the discovery altogether. I like automagic things, but there always needs to be a sane manual option. Period.

Next up is the thread pane headers (thread, starred, sender, date, etc.).. In TB2, you set the headers in one view, and all folder views are the same. I can understand people wanting to have different views, but there is no option to set all views the same, so every single folder has to be modified.. This sucks when you have lots of folders and I have tons of them. There is a workaround – do not log into the account on the first prompt – set the thread pane headers you want on the Inbox, and most (not all) will inherit the Inbox view. Then log in later and fix the few incorrect views that remain (Drafts, Trash, etc.).

While you have the account created and have not logged in the first time, yet, you might want to dig through the account settings and decide if you want a few things changed – particularly under Synchronization & Storage.. no, I don’t want to keep all messages locally – I use IMAP – uncheck that box. I really don’t want to store gigs of messages locally by default – the whole point of IMAP is to keep the messages on the server. I also read some notes from people that use POP3 and (used to) “keep messages on server” – the default TB3 POP3 account creation pops all the messages off the server and deletes them from the server – be aware.. (and you should really be using IMAP, if you want this behavior anyway)

As of writing, the GPG/OpenPGP plugin, Enigmail, does not have a functional x86_64 Linux port for TB3 in the Add-Ons widget.. sigh.. There is a contributed port built on Arch Linux on the Enigmail download page that works for me. This should be fixed soon in the official Add-Ons widget, I suppose.

Some of my about:config modifications for sane behavior (Edit – Preferences – Advanced – Config Editor):

• mail.check_all_imap_folders_for_new; true
• mail.operate_on_msgs_in_collapsed_threads; false
• mail.tabs.autoHide; true
• mailnews.display.prefer_plaintext; true
• mailnews.nav_crosses_folders; 0

OK, it’s just about time to actually log in and fetch mail! A bit of IMAP header fetching and on to reading some mail, changing the toolbar buttons to small, and then I found the message header collapse is gone.. Ah, there is a nicely working add-on for that: CompactHeader by jmozmoz Thank you, thank you!

And on restart of TB3, I end up in whatever folder I was last viewing on shutdown.. and very odd behavior of password prompting, if it was a nested folder (duplicate login prompts..). And no where is there an option to configure “Start in my f’ing Inbox”. This is retarded, in my opinion – who asked for this “feature” anyway? Once again, there looks to be a sort-of-working plugin for this (and once again, this is a manual download/install, at the moment): Select Inbox by Bogdan Rechi This works ok in starting up in the default account Inbox, but the weird password prompts still remain – looking at the plugin code, this is run at start time – my suggestion for TB3 is for the plugin to switch to the default Inbox at shutdown, and let TB3 just start normally. When I start up TB3 after hitting my Inbox prior to shutdown, I don’t get the strange duplicate login prompts at startup.

The default “New Messages in Folder” text color (they dumped the little star..) and the basic highlighting on folder pane, thread pane, message pane selections and focus are crap – almost unreadable blue text on blue background for “New Messages” on the default Debian Gnome theme – blue selected folders look nearly identical to the blue selected+focus folders. The colors are essentially just pulled from the OS color theme, which is fine, but it is very difficult to differentiate where the focus is – I use this visual queue a lot when scrolling up/down with the keyboard while drilling through folders or message threads. The only way to configure this is by setting up custom CSS rules via userChrome.css. My ideas came from the Mozilla Folder Pane Color for New Mail notes and from this killer resource for TB mods – here is my custom userChrome.css:

/*  Tree Text Highlighting (folders, thread pane, address pane, etc.)
    Highlight focused items, but use black on lightgrey when not in focus */
    treechildren::-moz-tree-cell-text(selected) {
        background-color: lightgrey !important;
        color: black !important;
    }
    treechildren::-moz-tree-cell-text(selected, focus) {
        background-color: Highlight !important;
        color: white !important;
    }
    tree[selstyle="primary"] > treechildren::-moz-tree-row {
        border: none !important;
        background-color: transparent !important;
    }
    treechildren::-moz-tree-row(selected) {
        background-color: lightgrey !important;
    }
    treechildren::-moz-tree-row(selected, focus) {
        background-color: Highlight !important;
    }
/*  Folder Pane Color for New Mail */
    treechildren::-moz-tree-cell-text(folderNameCol, newMessages-true) {
        color: black !important;
    }
    treechildren::-moz-tree-cell-text(folderNameCol, newMessages-true, selected) {
        color: black !important;
    }
    treechildren::-moz-tree-cell-text(folderNameCol, newMessages-true, selected, focus) {
        color: white !important;
    }

That about covers my fixes for my Thunderbird 3 sanity – if I need to set it up again and remember any other changes, I’ll add them in.

Update: I added in the config option to disable the new brain-dead collapsed thread display – nice try, Mozilla, but you can’t actually expand it and navigate with the keyboard, so FAIL.. mail.operate_on_msgs_in_collapsed_threads; false