calibre fails to start: progress_indicator wrong version

Bug #826835 reported by Steve Beattie
36
This bug affects 8 people
Affects Status Importance Assigned to Milestone
calibre
Won't Fix
Undecided
Unassigned
calibre (Ubuntu)
Fix Released
Undecided
Fabrice Coutadeur

Bug Description

Calibre in oneiric fails to start with the following traceback:

Traceback (most recent call last):
  File "/usr/bin/calibre", line 19, in <module>
    sys.exit(main())
  File "/usr/lib/calibre/calibre/gui2/main.py", line 372, in main
    app, opts, args, actions = init_qt(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 51, in init_qt
    from calibre.gui2.ui import Main
  File "/usr/lib/calibre/calibre/gui2/ui.py", line 31, in <module>
    from calibre.gui2.widgets import ProgressIndicator
  File "/usr/lib/calibre/calibre/gui2/widgets.py", line 23, in <module>
    from calibre.gui2.progress_indicator import ProgressIndicator as _ProgressIndicator
  File "/usr/lib/calibre/calibre/gui2/progress_indicator/__init__.py", line 15, in <module>
    pi_error)
RuntimeError: Failed to load the Progress Indicator plugin: the PyQt4.QtCore module is version 1 but the progress_indicator module requires version -1

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: calibre 0.8.8+dfsg-1
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
CheckboxSubmission: 9c15077a0ca11678d04e060687c26674
CheckboxSystem: 5dc75472945f57d094b84e90feb97396
Date: Mon Aug 15 09:09:03 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: calibre
UpgradeStatus: Upgraded to oneiric on 2011-07-17 (28 days ago)

Related branches

Revision history for this message
Steve Beattie (sbeattie) wrote :
Changed in calibre (Ubuntu):
status: New → Confirmed
Changed in calibre (Ubuntu):
assignee: nobody → Fabrice Coutadeur (fabricesp)
status: Confirmed → In Progress
Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

calibre FTBFS with a strange error in libindicator (see #828304). Once the build will be fixed, I'll check if this fixes this bug too.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package calibre - 0.8.8+dfsg-1ubuntu1

---------------
calibre (0.8.8+dfsg-1ubuntu1) oneiric; urgency=low

  * fix_ftbfs_as-needed.patch: add missing QtGui lib when linking
    progress_indicator with --as-needed. This fixes a FTBFS (LP: #828304) and
    allow calibre to run (LP: #826835). Thanks Jason Conti for the help!
 -- Fabrice Coutadeur <email address hidden> Thu, 18 Aug 2011 22:12:26 +0200

Changed in calibre (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Markus Birth (mbirth) wrote :

This bug seems to have re-appeared in 0.8.21+dfsg-1~ppa1 from n-muench's PPA.

x86_64 package under oneiric ocelot as of today.

Changed in calibre:
status: New → Won't Fix
Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

@Markus,

if you are using the software from a ppa, please report the bug to the owner of the ppa, not to the distribution.

thanks,
Fabrice

Revision history for this message
Nate Muench (Mink) (n-muench) wrote :

The calibre in my PPA already has the patch that was added to the main Oneiric packaging (in the main repo), in fact the patch file as copied from the main Oneiric branch.

And if you have a major bug like this coming from a package from one of my repos, contact me directly, don't create a bug report (on launchpad or with the developer). Anything with a "-0" hasn't been touched by Debian or Ubuntu (and it's been built on existing packaging). In the current case, the packaging is backported from Debian's repo, the only things changed are some added dependencies and the patch from Oneiric.

I'm going to add versioning explanations shortly to all my PPA (it's my mistake I didn't do it sooner). It's kind of confusing because I can't bold anything in the PPA description.

Revision history for this message
Heiner Valverde (dylian17-deactivatedaccount) wrote :

Hello, I am having that same issue with Calibre version calibre 0.8.8+dfsg-1ubuntu1 and it started happening after I upgraded from Natty to Oneiric, I can confirm the bug is still present on the 64 bit version of Ubuntu.

Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

Hi Heiner,

I upgraded my main amd64 system to Oneiric some days ago, and calibre works fine here.

Could you post the results of the following commands:
apt-cache policy calibre
apt-cache policy python-qt4

thanks,
Fabrice

Revision history for this message
Heiner Valverde (dylian17-deactivatedaccount) wrote :

Hi Fabrice,

Here's the output of those commands:

----------------------------------------------------------------------- 07:11:04
heiner@heiner-desktop:~$ apt-cache policy calibre
calibre:
  Installed: 0.8.8+dfsg-1ubuntu1
  Candidate: 0.8.8+dfsg-1ubuntu1
  Version table:
 *** 0.8.8+dfsg-1ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages
        100 /var/lib/dpkg/status
----------------------------------------------------------------------- 07:11:17
heiner@heiner-desktop:~$ apt-cache policy python-qt4
python-qt4:
  Installed: 4.8.5-0ubuntu2
  Candidate: 4.8.5-0ubuntu2
  Version table:
 *** 4.8.5-0ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status
----------------------------------------------------------------------- 07:11:38

Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

Seems ok so far.
Could you run calibre from the command line and attach here the full run log?
Also, could you paste the output of the following command:
type calibre

Thanks,
Fabrice

Revision history for this message
Heiner Valverde (dylian17-deactivatedaccount) wrote :

This is what I got from calibre:

heiner@heiner-desktop:~$ calibre
Traceback (most recent call last):
  File "/usr/bin/calibre", line 19, in <module>
    sys.exit(main())
  File "/usr/lib/calibre/calibre/gui2/main.py", line 372, in main
    app, opts, args, actions = init_qt(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 51, in init_qt
    from calibre.gui2.ui import Main
  File "/usr/lib/calibre/calibre/gui2/ui.py", line 31, in <module>
    from calibre.gui2.widgets import ProgressIndicator
  File "/usr/lib/calibre/calibre/gui2/widgets.py", line 23, in <module>
    from calibre.gui2.progress_indicator import ProgressIndicator as _ProgressIndicator
  File "/usr/lib/calibre/calibre/gui2/progress_indicator/__init__.py", line 15, in <module>
    pi_error)
RuntimeError: Failed to load the Progress Indicator plugin: the PyQt4.QtCore module is version 1 but the progress_indicator module requires version -1
----------------------------------------------------------------------- 07:33:01
heiner@heiner-desktop:~$ type calibre
calibre is hashed (/usr/bin/calibre)

Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :

Hi,

What is the version of qt4 on your system? This can be checked with:
apt-cache policy libqtcore4

If you have the official one (4:4.7.4-0ubuntu8), could you please update your system with:
sudo apt-get update
sudo apt-get dist-upgrade

If it still fails, could you try reinstalling the 2 calibre packages (calibre and calibre-bin) and python-qt4 ?

thanks,
Fabrice

Revision history for this message
Heiner Valverde (dylian17-deactivatedaccount) wrote :

I have great news :) Calibre is now running after uninstall it and reinstall it but also I removed the configuration files at /.config for Calibre and it opened and it's working like a charm.

BTW, this is the policy for libqtcore4:

heiner@heiner-desktop:~$ apt-cache policy libqtcore4
libqtcore4:
  Installed: 4:4.7.4-0ubuntu8
  Candidate: 4:4.7.4-0ubuntu8
  Version table:
 *** 4:4.7.4-0ubuntu8 0
        500 http://archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status

My system was up to date at the moment I ran the command.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.