View Single Post
Old 04-15-2016, 01:52 AM   #836
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by dirvine View Post
Oddly enough, in debug mode everything worked fine.

When I exited from debug mode and reopened calibre in regular mode the pipe error returned.

I realized that calibre outputs at least some of the same log messages to the mac console when it is in regular mode, and I hope that this will be of assistance to you. This is what I get from launching calibre then attempting to add one book to my read shelf (which also is supposed to add the rating and date to goodreads, remove a "to-read" tag from the book, and add a "read" tag):
I was expecting that it would work in debug mode. For your two earlier reports, the line number was for a "prints" statement. That was writing to the console. I use these for debugging but usually use a different statement that does nothing if calibre is not running in debug mode. This later example is in a different place, but it might still be triggered by the prints statement.

I'll put up a beta tonight without these lines in it to see if that fixes anything.
davidfor is offline   Reply With Quote