Comment 4 for bug 1031567

Apparently, reinstall doesn't remove the ~/.pypar2 directory...
I had to manually delete ~/.pypar2 before reinstall.

re-reinstalled pypar2 --
--
~$ df -BG
Filesystem 1G-blocks Used Available Use% Mounted on
/dev/loop0 29G 9G 20G 32% /
udev 3G 1G 3G 1% /dev
tmpfs 2G 1G 2G 1% /run
none 1G 0G 1G 0% /run/lock
none 3G 1G 3G 2% /run/shm
/dev/sda2 907G 728G 179G 81% /host
/dev/sdc1 150G 146G 4G 98% /media/...snip...
/dev/sdb1 1864G 1861G 3G 100% /media/...snip...
~$ sudo apt-get --reinstall install pypar2
[sudo] password for user:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  ...snip...
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/47.1 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 193199 files and directories currently installed.)
Preparing to replace pypar2 1.4-6 (using .../archives/pypar2_1.4-6_all.deb) ...
Unpacking replacement pypar2 ...
Processing triggers for man-db ...
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Setting up pypar2 (1.4-6) ...
---
When reinstall finished, there still was no ~/.pypar2 directory.
So, I loaded pypar2 from the Laucher on a whim.
The ~/.pypar2 got created as PyPar2 FINALLY started, after a week of working on this problem.

Attached is the new ~/.pypar2/prefs.xml file which has 995 bytes (not 0 bytes).