Bug 538331
Summary: | [abrt] 0.6.21-2.fc12 unknown error when sending PDFs to sony PRS | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mario Chacon <the.masch> |
Component: | calibre | Assignee: | Ionuț Arțăriși <ionut> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | 06707731732, afgonzaga, ambijat, amturnip, asaeb, awilliam, biaji.cn, damien, darko.miletic, dennisgdaniels, dlstripes-fedorabugs, dokhebi, ehicks, encipherJ, fedora, frankly3d, ionut, javadieh.msd, jdbramlett, jim, jkunze, josemaria, jwildebo, lats, louis, maskimko, mothlight, occultmastery, ortizsantini, pavel1r, pcfe, regawyte, reggie, towers, walrus |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | abrt_hash:a8b6448c | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-12-04 03:13:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mario Chacon
2009-11-18 09:50:57 UTC
Can you provide more information? A traceback would be nice... I had this bug when sending a PDF also. I can't get abrt to send the traceback since it knows the bug report is a dupe :( I'll see if I can extract it from abrt somehow... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Any more info on this bug? Do you still get this with the latest fedora version of calibre? I can confirm this issue is still present with the latest calibre (.6.40). Each time I send a .pdf to my Sony PRS-600 abrt detects a crash. Calibre, however, keeps running and transfer is always completed. Boricua, could you please try running calibre from the terminal and posting the traceback from when this error happens? Ionut, this is what I got from running from terminal: [Francisco@Hogar Desktop]$ calibre link hasn't been detected! link hasn't been detected! Exception in thread Thread-3 (most likely raised during interpreter shutdown): Traceback (most recent call last): File "/usr/lib64/python2.6/threading.py", line 525, in __bootstrap_inner File "/usr/lib64/calibre/calibre/utils/ipc/server.py", line 166, in run File "/usr/lib64/python2.6/Queue.py", line 177, in get File "/usr/lib64/python2.6/threading.py", line 252, in wait <type 'exceptions.TypeError'>: 'NoneType' object is not callable Exception in thread Thread-9 (most likely raised during interpreter shutdown): Traceback (most recent call last): File "/usr/lib64/python2.6/threading.py", line 525, in __bootstrap_inner File "/usr/lib64/calibre/calibre/utils/ipc/server.py", line 166, in run File "/usr/lib64/python2.6/Queue.py", line 177, in get File "/usr/lib64/python2.6/threading.py", line 252, in wait <type 'exceptions.TypeError'>: 'NoneType' object is not callable Exception in thread Thread-5 (most likely raised during interpreter shutdown): Traceback (most recent call last): File "/usr/lib64/python2.6/threading.py", line 525, in __bootstrap_inner File "/usr/lib64/calibre/calibre/gui2/device.py", line 172, in run File "/usr/lib64/calibre/calibre/gui2/device.py", line 134, in detect_device File "/usr/lib64/calibre/calibre/devices/scanner.py", line 140, in scan File "/usr/lib64/calibre/calibre/devices/scanner.py", line 86, in __call__ <type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'listdir' [Francisco@Hogar Desktop]$ When starting calibre, the first two lines ("link hasn't been detected") are the only ones showing, even when I transfer a document to the ereader and get the bug alert. The remaining lines appear after I quit calibre. Just let me know if you need anything else. Thanks, Boricua There's nothing unusual in here. Those are the messages calibre usually generates on exit. I'm puzzled as to what's causing this, or even what it is that's happening. How to reproduce ----- 1. Start Calibre 2. Add a book to an existing library. 3. How to reproduce ----- 1. Used "Send to device" on the Quick Start guide to send it to my Sony PRS 300 Reader. FWIW, I was able to send a large PDF to my device with the latest F13 build successfully the other day. Calibre seems to generate tracebacks left, right and centre when running, but it doesn't actually crash, and all the operations I tried succeeded. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers How to reproduce ----- 1. Add file ssa-545.pdf (the 02-2010 version) from www.socialsecurity.gov to list of eBooks. Ok, so I think I finally reproduced this bug. Thanks a lot for the broken PDF William! The bad news is that abrt sent the bug report to a different bug: https://bugzilla.redhat.com/show_bug.cgi?id=549261#c4 Anyway, we're waiting for upstream to say they wontfix now: http://bugs.calibre-ebook.com/ticket/5292 Comment ----- Couldn't reproduce error... was converting CBZ file... Package: calibre-0.6.42-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. PRS-505 lost all tags in a crash (nothing to do with calibre) 2. deleted PRS-505 content from within calibre 3. send 151 books to the device at once i. ctrl-A ii. click Send to device Greetings. I have created a test build of the latest calibre version for Fedora 12. Can you please update from: http://koji.fedoraproject.org/koji/taskinfo?taskID=2204259 And see if you can reproduce this bug? I am using Fedora 13, Can I use your version on Fedora 13? salu2... masch... Package: calibre-0.6.42-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Send a PDF to my SONY Reader 505 2. 3. Comment ----- Error when I load a PDF Could you repackage it for Fedora 13, please? Thanks! salu2... masch... For f13, try this update: http://admin.fedoraproject.org/updates/calibre-0.6.55-1.fc13,python-cssutils-0.9.6-1.fc13 Yeah!.. Great!.. It works excellent!! Thank you so much for your help!!.. Package: calibre-0.6.42-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.view Library 2.right click a book and choose Send to Device, then Send to Main Memory; or click the big Send to Device button, whose default action is Send to Main Memory. 3.the animated circular thing in Calibre shows evidence of progress 4.the crash message appears with an invitation to open ABRT Comment ----- The device is Sony Reader Touch. In spite of the error message, the book appears on the reader. My traceback (for comment #21) is as follows. ABRT put my comment into this report, but I am not convinced that it is the same issue... <string>:1:connect:error: [Errno 2] No such file or directory Traceback (most recent call last): File "/usr/bin/calibre-parallel", line 19, in <module> sys.exit(main()) File "/usr/lib/calibre/calibre/utils/ipc/worker.py", line 87, in main with closing(Client(address, authkey=key)) as conn: File "/usr/lib/python2.6/multiprocessing/connection.py", line 134, in Client c = SocketClient(address) File "/usr/lib/python2.6/multiprocessing/connection.py", line 253, in SocketClient s.connect(address) File "<string>", line 1, in connect error: [Errno 2] No such file or directory Local variables in innermost frame: self: <socket._socketobject object at 0x8e8664c> args: ('/tmp/pymp-FPVgII/listener-uAAtcP',) Package: calibre-0.6.42-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Closed calibre using the drop-down menu of the window button in the upper left corner of the calibre window. Package: calibre-0.7.4-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Rawhide) How to reproduce ----- 1. Go into prefrences 2. set new library path 3. Change some values. Can you all try the latest versions? Rawhide http://koji.fedoraproject.org/koji/buildinfo?buildID=182930 The following scratch builds: Fedora 13 http://koji.fedoraproject.org/koji/taskinfo?taskID=2311683 Fedora 12 http://koji.fedoraproject.org/koji/taskinfo?taskID=2311690 Package: calibre-0.6.55-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Select a large number of books 2.Send them to your ebook reader (Kindle DX) 3. Comment ----- I tried to syncronize my ebooks Please upgrade to the latest version here: http://repos.fedorapeople.org/repos/kevin/calibre/ There is a repo files there that can be dropped into /etc/yum.repos.d/ in teminal su cd /etc/yum.repos.d wget http://repos.fedorapeople.org/repos/kevin/calibre/fedora-calibre.repo Let us know how it goes/ Package: calibre-0.6.55-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- Added a .lit book to the library. Clicked Convert E-books (to Epub) and bang Package: calibre-0.6.55-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.converting book 2. 3. Comment ----- converting books plugged in kindle 2 crash Package: calibre-0.6.55-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Run 2.Exit Package: calibre-0.6.55-1.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. I selected and opened an epub file from Project Guttenburg. 2. 3. Comment ----- It did this as soon as I asked it to open. Package: calibre-0.6.55-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.loading new book 2. 3. Comment ----- this "crash" was not really a crash. the book imported fine as I could tell. Package: calibre-0.6.55-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I opened calibre - it told me the database was corrupt. 2. I selected for calibre not to recover, but to create a new database. 3. When presented with the default location, I clicked open. 4. I heard a lot of disk activity, then calibre crashed. Package: calibre-0.6.55-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.I don't know, had completed a number of ops using calibre and then ABRT loaded. 2. 3. Package: calibre-0.6.55-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open book from Firefox Downloads window. 2. 3. Comment ----- Download file from any source in Firefox. Right click on file in Downloads window and select Open. Package: calibre-0.6.55-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Saving updated book to disk. 2. 3. Comment ----- Download file from any source in Firefox. Right click on file in Downloads window and select Open. Package: calibre-0.6.55-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Happens every time I close calibre This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |