Hide Forgot
abrt version: 1.1.17 architecture: i686 component: chm2pdf executable: /usr/bin/chm2pdf kernel: 2.6.35.11-83.fc14.i686 package: chm2pdf-0.9.1-9.fc14 reason: chm2pdf:116:get_objective_urls_list:IOError: [Errno 2] No such file or directory: '/tmp/tmpse2feC/A Practical Guide to Linux Commands, Editors, and Shell Programming - By ____________Mark G. Sobell/urlslist.txt' release: Fedora release 14 (Laughlin) time: 1298028846 uid: 500 backtrace ----- chm2pdf:116:get_objective_urls_list:IOError: [Errno 2] No such file or directory: '/tmp/tmpse2feC/A Practical Guide to Linux Commands, Editors, and Shell Programming - By ____________Mark G. Sobell/urlslist.txt' Traceback (most recent call last): File "/usr/bin/chm2pdf", line 1098, in <module> main(sys.argv) File "/usr/bin/chm2pdf", line 1092, in main convert_to_pdf(cfile, filename, outputfilename, options) File "/usr/bin/chm2pdf", line 318, in convert_to_pdf objective_urls=get_objective_urls_list(filename) File "/usr/bin/chm2pdf", line 116, in get_objective_urls_list flist=open(CHM2PDF_WORK_DIR+'/urlslist.txt','rU') IOError: [Errno 2] No such file or directory: '/tmp/tmpse2feC/A Practical Guide to Linux Commands, Editors, and Shell Programming - By ____________Mark G. Sobell/urlslist.txt' Local variables in innermost frame: filename: 'A Practical Guide to Linux Commands, Editors, and Shell Programming - By ____________Mark G. Sobell.chm' How to reproduce ----- 1.didn't know chm2pdf HAD crashed at all 2. 3.
Created attachment 480965 [details] File: backtrace
I was able to reproduce the issue. A possible workaround is to make a copy/rename the source chm file so that it doesn't have any spaces in between. http://code.google.com/p/chm2pdf/issues/detail?id=24
If the above solution does not work even after renaming, you could try --webpage option. ie., chm2pdf --webpage test.chm test.pdf
This bug 666110 gives the same error and the cause may be the same. I am planning to provide a patch fix that prevents the crash from occuring. Marking this one as duplicate of 666110.
*** This bug has been marked as a duplicate of bug 666110 ***