Bug 1149395 - calibre shows python exceptions since installing latest F-21 updates
Summary: calibre shows python exceptions since installing latest F-21 updates
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: calibre
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-04 11:57 UTC by Hans de Goede
Modified: 2014-11-01 17:08 UTC (History)
5 users (show)

Fixed In Version: calibre-2.5.0-1.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-01 17:08:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hans de Goede 2014-10-04 11:57:31 UTC
Hi,

I update my F-21 almost daily, and do not use calibre that often, so I cannot tell exactly which updates has caused this. But with the latest F-21 I get the following:

[hans@shalem ~]$ calibre
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
calibre 2.0  isfrozen: False is64bit: True
Linux-3.17.0-rc6+-x86_64-with-fedora-21-Twenty_One Linux ('64bit', 'ELF')
('Linux', '3.17.0-rc6+', '#29 SMP Wed Oct 1 10:53:46 CEST 2014')
Python 2.7.8
Linux: ('Fedora', '21', 'Twenty One')
Successfully initialized third party plugins: Kindle Collections
Traceback (most recent call last):
  File "/usr/lib64/calibre/calibre/gui2/cover_flow.py", line 107, in reset
    self.beginResetModel(), self.endResetModel()
  File "/usr/lib64/calibre/calibre/gui2/cover_flow.py", line 110, in beginResetModel
    self.dataChanged.emit()
AttributeError: 'DatabaseImages' object has no attribute 'dataChanged'

This happens when just clicking around, and also throws a dialog with the error, that can be clicked away without issues, but this is still annoying.

Regards,

Hans

Comment 1 Kevin Fenzi 2014-10-05 16:11:04 UTC
I'm not seeing this at all with rawhide/calibre-2.5.0... 

Was 2.0.0 doing this always for you? Or it just started happening?

Can you try this 2.5.0 scratch build:

https://koji.fedoraproject.org/koji/taskinfo?taskID=7770443

Comment 2 Hans de Goede 2014-10-12 13:43:45 UTC
(In reply to Kevin Fenzi from comment #1)
> I'm not seeing this at all with rawhide/calibre-2.5.0... 
> 
> Was 2.0.0 doing this always for you? Or it just started happening?
> 
> Can you try this 2.5.0 scratch build:
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=7770443

Note that scratch build actually is for rawhide, despite the f21 in the .src.rpm filename. I had to parallel install libicu from rawhide to be able to install it. With that done, this scratch-build seems to fix the issue I was seeing.

In the mean time I've come up with a more consistent way to reproduce it, with the 2.0.0 build in F-21 if I switch between sorting by Author and sorting by Series I can reliable reproduce.

Regards,

Hans

Comment 3 Kevin Fenzi 2014-10-12 15:23:12 UTC
Oops. Sorry about that... I thought I did f21, but must have mistyped. ;( 

I'll push a update for f21. Will be good to get the newest in before beta freeze anyhow.

Comment 4 Fedora Update System 2014-10-12 15:48:37 UTC
calibre-2.5.0-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/calibre-2.5.0-1.fc21

Comment 5 Fedora Update System 2014-10-14 04:35:03 UTC
Package calibre-2.5.0-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing calibre-2.5.0-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-12773/calibre-2.5.0-1.fc21
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-11-01 17:08:43 UTC
calibre-2.5.0-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.