Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52687 - [calibre] segfault at startup
Attached to Project:
Community Packages
Opened by Adam Price (voofre) - Monday, 23 January 2017, 19:34 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 24 January 2017, 00:06 GMT
Opened by Adam Price (voofre) - Monday, 23 January 2017, 19:34 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 24 January 2017, 00:06 GMT
|
DetailsDescription:
After recently upgraded python2-pip (4.19-1) and python2-pyqt5 (5.7.1-1) calibre segfaults at startup. Strace available here http://pastebin.ca/3759567 . Downgrading above python packages fixes problem so maybe rebuilding calibre against new versions is needed. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Tuesday, 24 January 2017, 00:06 GMT
Reason for closing: Fixed
Additional comments about closing: calibre 2.77.0-3
Tuesday, 24 January 2017, 00:06 GMT
Reason for closing: Fixed
Additional comments about closing: calibre 2.77.0-3
Comment by Skottish (skottish) -
Monday, 23 January 2017, 21:11 GMT
A simple rebuild works to allow calibre to start again.