Bug 967156

Summary: [abrt] calibre-0.9.31-1.fc19: worker.py:92:do_read_metadata:IOError: [Errno 2] No such file or directory: u'/var/tmp/calibre_0.9.31_tmp_SAFYQi/OtO2Jt_rm_worker/0.error'
Product: [Fedora] Fedora Reporter: M. Edward (Ed) Borasky <znmeb>
Component: calibreAssignee: Kevin Fenzi <kevin>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: chkr, frankly3d, kevin, mbacovsk, nushio
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:78a58124dcc6782199ef01dc4677d0d63f3e2700
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-25 19:27:43 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: backtrace
File: core_backtrace
File: environ none

Description M. Edward (Ed) Borasky 2013-05-24 22:36:01 EDT
Description of problem:
Closed Calibre window

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.1.4
cmdline:        python2 /usr/bin/calibre-parallel
executable:     /usr/bin/calibre-parallel
kernel:         3.9.3-301.fc19.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
worker.py:92:do_read_metadata:IOError: [Errno 2] No such file or directory: u'/var/tmp/calibre_0.9.31_tmp_SAFYQi/OtO2Jt_rm_worker/0.error'

Traceback (most recent call last):
  File "/usr/bin/calibre-parallel", line 20, in <module>
  File "/usr/lib64/calibre/calibre/utils/ipc/worker.py", line 188, in main
    result = func(*args, **kwargs)
  File "/usr/lib64/calibre/calibre/ebooks/metadata/worker.py", line 42, in read_metadata_
    do_read_metadata(task, tdir, mdir, notification)
  File "/usr/lib64/calibre/calibre/ebooks/metadata/worker.py", line 92, in do_read_metadata
    with open(os.path.join(tdir, '%s.error'%id_), 'wb') as f:
IOError: [Errno 2] No such file or directory: u'/var/tmp/calibre_0.9.31_tmp_SAFYQi/OtO2Jt_rm_worker/0.error'

Local variables in innermost frame:
id_: 0
run_plugins_on_import: <functools.partial object at 0x1aadd08>
formats: [u'/var/tmp/BigData.pdf']
name: u'BigData'
format: u'/var/tmp/BigData.pdf'
notification: <Progress(Thread-1, started daemon 140663277700864)>
traceback: <module 'traceback' from '/usr/lib64/python2.7/traceback.pyc'>
fmts: [None]
ext: u'.pdf'
task: [(0, [u'/var/tmp/BigData.pdf'])]
tdir: u'/var/tmp/calibre_0.9.31_tmp_SAFYQi/OtO2Jt_rm_worker'
mdir: u'/var/tmp/calibre_0.9.31_tmp_SAFYQi/mcw8v4'
nfp: None
x: (0, [u'/var/tmp/BigData.pdf'])
mfmt: u'/var/tmp/BigData.pdf'
import_map: {}
metadata_fmts: [u'/var/tmp/BigData.pdf']
Comment 1 M. Edward (Ed) Borasky 2013-05-24 22:36:05 EDT
Created attachment 752923 [details]
File: backtrace
Comment 2 M. Edward (Ed) Borasky 2013-05-24 22:36:08 EDT
Created attachment 752924 [details]
File: core_backtrace
Comment 3 M. Edward (Ed) Borasky 2013-05-24 22:36:11 EDT
Created attachment 752925 [details]
File: environ
Comment 4 Kevin Fenzi 2013-05-25 13:57:05 EDT
Did you have it processing on a file at the time? 

Can you duplicate the crash?
Comment 5 M. Edward (Ed) Borasky 2013-05-25 15:33:22 EDT
I don't think it was processing a file at the time - I have a pretty big 'Calibre Library' and it was probably displaying that when I closed it. 

The system was installed from a Fedora Jam nightly for Fedora 19:

I'll try to duplicate it - most likely I had emailed some files to myself from Calibre before closing it and may have had a PDF open in Okular as well. But I think I closed the Okular windows before closing Calibre.
Comment 6 M. Edward (Ed) Borasky 2013-05-25 16:57:03 EDT
I have the machine up now and can't seem to recreate it. From looking at the backtrace, it looks like it was trying to get metadata from a file called 'BigData.pdf' that wasn't in /var/tmp where it was supposed to be. I don't think I was accessing that file in the session that crashed, and I can open that file, email it to myself, close it and close Calibre without getting a crash.

So I'm guessing I closed some *previous* Calibre session incorrectly and it was trying to clean up its database. There are a bunch of files in /var/tmp that have clearly been placed there by Calibre. Removing them didn't cause a crash either. So I think you can close this as 'unable to reproduce' - Calibre gets updated frequently.
Comment 7 Kevin Fenzi 2013-05-25 19:27:43 EDT
Thanks. Please do reopen if you find more info.