FS#49461 - [calibre] fails to start with python2-pyqt5-5.6-1

Attached to Project: Community Packages
Opened by George Angelopoulos (l4than-d3vers) - Wednesday, 25 May 2016, 06:53 GMT
Last edited by Jelle van der Waa (jelly) - Wednesday, 25 May 2016, 18:38 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
[calibre] fails to start with python2-pyqt5-5.6-1
Works fine with python2-pyqt5-5.5.1-2

Steps to reproduce:
run calibre

Result:

$ calibre
Traceback (most recent call last):
File "/usr/bin/calibre", line 20, in <module>
sys.exit(calibre())
File "/usr/lib/calibre/calibre/gui_launch.py", line 63, in calibre
main(args)
File "/usr/lib/calibre/calibre/gui2/main.py", line 495, in main
app, opts, args = init_qt(args)
File "/usr/lib/calibre/calibre/gui2/main.py", line 101, in init_qt
app = Application(args, override_program_name=override)
File "/usr/lib/calibre/calibre/gui2/__init__.py", line 872, in __init__
self.load_calibre_style()
File "/usr/lib/calibre/calibre/gui2/__init__.py", line 983, in load_calibre_style
self.pi.load_style(icon_map)
TypeError: a dict value has type 'unicode' but 'QString' is expected

This task depends upon

Closed by  Jelle van der Waa (jelly)
Wednesday, 25 May 2016, 18:38 GMT
Reason for closing:  Fixed
Additional comments about closing:  2.57.1-2 is in the repos now
Comment by andya (andya) - Wednesday, 25 May 2016, 11:23 GMT
I can reproduce this on my system too.
Comment by Doug Newgard (Scimmia) - Wednesday, 25 May 2016, 13:55 GMT
It's strange, I can't reproduce it and i know one of the Devs can't, either. This has to be some setting or missing dep or something.
Comment by Thor (ekkelett) - Wednesday, 25 May 2016, 14:55 GMT
Chipping in here: I could reproduce the same issue, and I *cough* believe jelle experienced the same issue after upgrading to python2-pyqt5-5.6-1.

Rebuilding Calibre solved the issue; could it be related to the python2 bytecode compilation as part of the build process?
Comment by George Angelopoulos (l4than-d3vers) - Wednesday, 25 May 2016, 15:25 GMT
indeed! I rebuilt from ABS, and it works!
Repo version still doesn't work. The broken repo version that I have has this hash:

$ md5sum /var/cache/pacman/pkg/calibre-2.57.1-1-x86_64.pkg.tar.xz
5f76205c2188792fa5eb1f42e05c9a7f /var/cache/pacman/pkg/calibre-2.57.1-1-x86_64.pkg.tar.xz


By the way, we're talking about calibre-2.57.1-1, right? Just to be clear and sorry for not specifying in the initial report.

Loading...