calibre does not start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
calibre |
Invalid
|
Undecided
|
Unassigned | ||
calibre (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: calibre
Traceback (most recent call last):
File "/usr/bin/calibre", line 18, in <module>
from calibre.gui2.main import main
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from lxml import etree
File "lxml.etree.pyx", line 183, in init lxml.etree (src/lxml/
LookupError: unknown encoding: ASCII

John C Hatch (henwyn) wrote : | #1 |

Fabrice Coutadeur (fabricesp) wrote : | #2 |
Hi,
I'm not able to reproduce the bug in Maverick or Natty. Could you please post the output of the following command:
apt-cache policy calibre
Thanks,
Fabrice
Changed in calibre (Ubuntu): | |
status: | New → Incomplete |

lipstick (sinanaykut-gmail) wrote : Re: [Bug 691608] Re: calibre does not start | #3 |
sinan@sinan-
calibre:
Kurulu: 0.7.43+dfsg-1
Aday: 0.7.43+dfsg-1
Sürüm tablosu:
*** 0.7.43+dfsg-1 0
500 http://
100 /var/lib/
2011/2/6 Fabrice Coutadeur <email address hidden>:
> Hi,
>
> I'm not able to reproduce the bug in Maverick or Natty. Could you please post the output of the following command:
> apt-cache policy calibre
>
> Thanks,
> Fabrice
>
> ** Changed in: calibre (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https:/
>
> Title:
> calibre does not start
>
> Status in “calibre” package in Ubuntu:
> Incomplete
>
> Bug description:
> Binary package hint: calibre
>
> Traceback (most recent call last):
> File "/usr/bin/calibre", line 18, in <module>
> from calibre.gui2.main import main
> File "/usr/lib/
> from calibre.
> File "/usr/lib/
> from calibre.
> File "/usr/lib/
> from lxml import etree
> File "lxml.etree.pyx", line 183, in init lxml.etree (src/lxml/
> LookupError: unknown encoding: ASCII
>
> To unsubscribe from this bug, go to:
> https:/
>
--
twitter.

Fabrice Coutadeur (fabricesp) wrote : | #4 |
Hi,
Sorry for the late answer: could you also please post the output of the following command:
apt-cache policy python-sip
It seems that there is a ppa with a newer version of python-sip that may be the root cause of the problem.
thanks,
Fabrice

lipstick (sinanaykut-gmail) wrote : | #5 |
python-sip:
Kurulu: 4.12.1-0ubuntu1
Aday: 4.12.1-0ubuntu1
Sürüm tablosu:
*** 4.12.1-0ubuntu1 0
500 http://
100 /var/lib/
2011/3/3 Fabrice Coutadeur <email address hidden>:
> Hi,
>
> Sorry for the late answer: could you also please post the output of the following command:
> apt-cache policy python-sip
>
> It seems that there is a ppa with a newer version of python-sip that may
> be the root cause of the problem.
>
> thanks,
> Fabrice
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https:/
>
> Title:
> calibre does not start
>
> Status in “calibre” package in Ubuntu:
> Incomplete
>
> Bug description:
> Binary package hint: calibre
>
> Traceback (most recent call last):
> File "/usr/bin/calibre", line 18, in <module>
> from calibre.gui2.main import main
> File "/usr/lib/
> from calibre.
> File "/usr/lib/
> from calibre.
> File "/usr/lib/
> from lxml import etree
> File "lxml.etree.pyx", line 183, in init lxml.etree (src/lxml/
> LookupError: unknown encoding: ASCII
>
> To unsubscribe from this bug, go to:
> https:/
>
--
twitter.

Fabrice Coutadeur (fabricesp) wrote : | #6 |
Hi,
calibre has been updated 3 weeks ago to 0.7.44. Could you check that you are using the latest version of calibre and still have the issue?
Thanks,
Fabrice

S.Rey (s.rey) wrote : | #7 |
Hi,
I've just upgraded from maverick to natty, and now calibre doesn't open. It's 0.7.44 here.
calibre 0.7.44+dfsg-1build1
python-sip 4.12.1-1

lipstick (sinanaykut-gmail) wrote : | #8 |
No, I have got this error.
sinan@sinan-
Traceback (most recent call last):
File "/usr/bin/calibre", line 18, in <module>
from calibre.gui2.main import main
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from lxml import etree
File "lxml.etree.pyx", line 239, in init lxml.etree
(src/lxml/
File "lxml.etree.pyx", line 201, in lxml.etree.
(src/lxml/
LookupError: unknown encoding: ASCII
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/
94, in apport_excepthook
if pr.check_ignored():
File "/usr/lib/
in check_ignored
dom = self._get_
File "/usr/lib/
in _get_ignore_dom
dom = xml.dom.
File "/usr/lib/
160, in createDocument
raise NotImplementedError
NotImplementedError
Original exception was:
Traceback (most recent call last):
File "/usr/bin/calibre", line 18, in <module>
from calibre.gui2.main import main
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from lxml import etree
File "lxml.etree.pyx", line 239, in init lxml.etree
(src/lxml/
File "lxml.etree.pyx", line 201, in lxml.etree.
(src/lxml/
LookupError: unknown encoding: ASCII
2011/4/10 S.Rey <email address hidden>:
> Hi,
> I've just upgraded from maverick to natty, and now calibre doesn't open. It's 0.7.44 here.
>
> calibre 0.7.44+dfsg-1build1
> python-sip 4.12.1-1
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https:/
>
> Title:
> calibre does not start
>
> Status in “calibre” package in Ubuntu:
> Incomplete
>
> Bug description:
> Binary package hint: calibre
>
> Traceback (most recent call last):
> File "/usr/bin/calibre", line 18, in <module>
> from calibre.gui2.main import main
> File "/usr/lib/
> from calibre.
> File "/usr/lib/
> from calibre.
> File "/usr/lib/
> from lxml import etree
> File "lxml.etree....

Fabrice Coutadeur (fabricesp) wrote : | #9 |
Hi,
@S.Rey: what is the error you're getting if you start calibre from the command line?. If this is different than the one that there is in the Description, please open a new bug report.
@lipstick: I'm still unable to reproduce the bug report. What is the version of calibre-bin and the version of python-lxml ?
Thanks,
Fabrice

lipstick (sinanaykut-gmail) wrote : | #10 |
sinan@sinan-
calibre-bin:
Kurulu: 0.7.44+dfsg-1build1
Aday: 0.7.44+dfsg-1build1
Sürüm tablosu:
*** 0.7.44+dfsg-1build1 0
500 http://
100 /var/lib/
python-lxml:
Kurulu: 2.3-0.1
Aday: 2.3-0.1
Sürüm tablosu:
*** 2.3-0.1 0
500 http://
100 /var/lib/
2011/4/10 Fabrice Coutadeur <email address hidden>:
> Hi,
>
> @S.Rey: what is the error you're getting if you start calibre from the
> command line?. If this is different than the one that there is in the
> Description, please open a new bug report.
>
> @lipstick: I'm still unable to reproduce the bug report. What is the
> version of calibre-bin and the version of python-lxml ?
>
> Thanks,
> Fabrice
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https:/
>
> Title:
> calibre does not start
>
> Status in “calibre” package in Ubuntu:
> Incomplete
>
> Bug description:
> Binary package hint: calibre
>
> Traceback (most recent call last):
> File "/usr/bin/calibre", line 18, in <module>
> from calibre.gui2.main import main
> File "/usr/lib/
> from calibre.
> File "/usr/lib/
> from calibre.
> File "/usr/lib/
> from lxml import etree
> File "lxml.etree.pyx", line 183, in init lxml.etree (src/lxml/
> LookupError: unknown encoding: ASCII
>
> To unsubscribe from this bug, go to:
> https:/
>
--
twitter.

S.Rey (s.rey) wrote : | #11 |
I get this. I thought it was the same, but i've noticed now the "bad magic number" at the end. Could it be something went bad on updating the python version on system upgrade?
srey@computer:~$ calibre
Traceback (most recent call last):
File "/usr/bin/calibre", line 18, in <module>
from calibre.gui2.main import main
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from pyparsing import CaselessKeyword, Group, Forward, \
ImportError: Bad magic number in /usr/lib/
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/
if pr.check_ignored():
File "/usr/lib/
dom = self._get_
File "/usr/lib/
dom = xml.dom.
File "/usr/lib/
raise NotImplementedError
NotImplementedError
Original exception was:
Traceback (most recent call last):
File "/usr/bin/calibre", line 18, in <module>
from calibre.gui2.main import main
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from pyparsing import CaselessKeyword, Group, Forward, \
ImportError: Bad magic number in /usr/lib/

windracer (windracer) wrote : | #12 |
I'm seeing a similar 'magic number' error when trying to start Calibre after the upgrade from Maverick to Natty:
Traceback (most recent call last):
File "/usr/bin/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from pyparsing import CaselessKeyword, Group, Forward, \
ImportError: Bad magic number in /usr/lib/

S.Rey (s.rey) wrote : | #13 |
Hi,
@windracer
If your problem is the same as mine, It seems to be caused by the upgrade. At least in my case, after a fresh install of natty final, calibre works as expected.
Anyway, it seems to be completely unrelated to this bug report, so if you can't afford a fresh installation, you might want to open a new bug.

windracer (windracer) wrote : | #14 |
Ugh, I'd rather not have to do a fresh install of Natty. I'll keep digging ...

windracer (windracer) wrote : | #15 |
Hey hey! Removing calibre and re-installing it fixed the problem, no need to re-install Natty. Phew!

Bob Blanchett (bobblanchett) wrote : | #16 |
same problem after upgrade to natty:
still get the error after remove/install of calibre via apt
==
bob@grytpype:~$ calibre
Traceback (most recent call last):
File "/usr/bin/calibre", line 18, in <module>
from calibre.gui2.main import main
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
File "/usr/lib/
from pyparsing import CaselessKeyword, Group, Forward, \
ImportError: Bad magic number in /usr/lib/
bob@grytpype:~$ sudo apt-cache policy calibre
calibre:
Installed: 0.7.44+dfsg-1build1
Candidate: 0.7.44+dfsg-1build1
Version table:
*** 0.7.44+dfsg-1build1 0
500 http://
100 /var/lib/
bob@grytpype:~$ sudo apt-cache policy python-sip
python-sip:
Installed: 4.12.1-1
Candidate: 4.12.1-1
Version table:
*** 4.12.1-1 0
500 http://
100 /var/lib/
bob@grytpype:~$

lipstick (sinanaykut-gmail) wrote : LinkedIn'e bağlanma daveti | #17 |
LinkedIn
------------
Bug,
Sizi LinkedIn'deki profesyonel profilime eklemek istiyorum.
- Sinan
Sinan Aykut
Şu okulda öğrenci: Afyon Kocatepe Üniversitesi
Türkiye
Sinan Aykut adlı kişiyi tanıdığınızı onaylayın
https:/
--
(c) 2011, LinkedIn Corporation

Jason (themacster) wrote : | #18 |
I am running 11.10 on an amd x4 processor with ati fglrx graphics driver.
Calibre was running fine on natty 11.04, but since upgrading to 11.10, calibre fails to start and kills compiz-decorator at the same time.
After uninstalling & reinstalling, calibre ran at first launch, but now fails with the original fault.

Kovid Goyal (kovid) wrote : Re: calibre bug 691608 | #19 |
I do not provide support for people using distro provided packages. If you are using a distro provided package, uninstall it and install the official calibre binary from http://
status invalid
Changed in calibre: | |
status: | New → Invalid |

Fabrice Coutadeur (fabricesp) wrote : | #20 |
@Jason: this is a known issue in Oneiric, that is not linked to the issue described here.
Please check bug 805303
thanks,
Fabrice

Horst Seeger (horstseeger) wrote : | #21 |
This is the output if I start calibre. It stays caught in an endless loop:
horst@horst-
Connected to accessibility bus at: "unix:abstract=
Registered DEC: true
Invalid parent: 0xb0c6f48 Application(
Creating accessible with different object than the original interface!
show QSplashScreen(
Creating accessible with different object than the original interface!
Requesting child objects for an interface that is a virtual child itself.
Requesting child objects for an interface that is a virtual child itself.
Requesting child objects for an interface that is a virtual child itself.
Requesting child objects for an interface that is a virtual child itself.
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Requesting child objects for an interface that is a virtual child itself.
Requesting child objects for an interface that is a virtual child itself.
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
Creating accessible with differen...

Fabrice Coutadeur (fabricesp) wrote : | #22 |
Hi,
@Horst Seeger: your bug is totally different (and I'm not able to reproduce it anyway). Could you please open a separate bug report? Thanks,
Fabrice

Launchpad Janitor (janitor) wrote : | #23 |
[Expired for calibre (Ubuntu) because there has been no activity for 60 days.]
Changed in calibre (Ubuntu): | |
status: | Incomplete → Expired |

Peta (peta-v-s) wrote : | #24 |
The "package" isn't complete....
Traceback (most recent call last):
File "site.py", line 51, in main
File "site-packages/
File "site-packages/
File "site-packages/
File "site-packages/
File "site-packages/
File "site-packages/
File "site-packages/
File "site-packages/
File "site-packages/
File "site-packages/
ImportError: /usr/lib64/
The latest downloaded version from the developer does not have this bug but the Ubuntu distro package does. I tried reinstalling the package and had the same results. Traceback from attempting to open Calibre from a terminal:
Traceback (most recent call last): exit(main( )) calibre/ calibre/ gui2/main. py", line 321, in main calibre/ calibre/ gui2/main. py", line 40, in init_qt calibre/ calibre/ gui2/ui. py", line 31, in <module> gui2.widgets import ProgressIndicator calibre/ calibre/ gui2/widgets. py", line 26, in <module> gui2.progress_ indicator import ProgressIndicator as calibre/ calibre/ gui2/progress_ indicator/ __init_ _.py",
File "/usr/bin/calibre", line 19, in <module>
sys.
File "/usr/lib/
app, opts, args, actions = init_qt(args)
File "/usr/lib/
from calibre.gui2.ui import Main
File "/usr/lib/
from calibre.
File "/usr/lib/
from calibre.
_ProgressIndicator
File "/usr/lib/
line 15, in <module>
pi_error)
RuntimeError: Failed to load the Progress Indicator plugin: the sip module
implements API v8.0 but the progress_indicator module requires API v7.1