I have to admit that this bug has annoyed me: it should have been easy to either apply the patch or package Bibletime 2.9.2, which fixes this problem. So I decided to do so myself.
I have taken the Debian package of Bibletime 2.9.2-1 (in sid) and back-ported to Debian Wheezy, Ubuntu Precise and Ubuntu Raring, both i386 and amd64. No changes were needed to the package itself. I can confirm that it solves this bug; I have tested on Kubuntu Raring i386.
If you would like to use this package, add ONE of the following lines to /etc/apt/sources.list, depending on your distribution:
I have to admit that this bug has annoyed me: it should have been easy to either apply the patch or package Bibletime 2.9.2, which fixes this problem. So I decided to do so myself.
I have taken the Debian package of Bibletime 2.9.2-1 (in sid) and back-ported to Debian Wheezy, Ubuntu Precise and Ubuntu Raring, both i386 and amd64. No changes were needed to the package itself. I can confirm that it solves this bug; I have tested on Kubuntu Raring i386.
If you would like to use this package, add ONE of the following lines to /etc/apt/ sources. list, depending on your distribution:
deb ftp://ftp. zap.org. au/pub/ debian zapgroup-wheezy main contrib non-free zap.org. au/pub/ debian zapgroup-sid main contrib non-free zap.org. au/pub/ ubuntu zapgroup-precise main restricted zap.org. au/pub/ ubuntu zapgroup-raring main restricted
deb ftp://ftp.
deb ftp://ftp.
deb ftp://ftp.
For more information on this repository, please see ftp://ftp. zap.org. au/pub/ debian/ README . I hope this helps others get around this annoying bug!