View Single Post
Old 05-26-2012, 03:37 PM   #3
BrentP
Junior Member
BrentP can even cheer up an android equipped with a defective Genuine Personality Prototype.BrentP can even cheer up an android equipped with a defective Genuine Personality Prototype.BrentP can even cheer up an android equipped with a defective Genuine Personality Prototype.BrentP can even cheer up an android equipped with a defective Genuine Personality Prototype.BrentP can even cheer up an android equipped with a defective Genuine Personality Prototype.BrentP can even cheer up an android equipped with a defective Genuine Personality Prototype.BrentP can even cheer up an android equipped with a defective Genuine Personality Prototype.BrentP can even cheer up an android equipped with a defective Genuine Personality Prototype.BrentP can even cheer up an android equipped with a defective Genuine Personality Prototype.BrentP can even cheer up an android equipped with a defective Genuine Personality Prototype.BrentP can even cheer up an android equipped with a defective Genuine Personality Prototype.
 
Posts: 1
Karma: 30386
Join Date: May 2012
Location: Washington, DC
Device: Sony PRS-650
I experienced the same issue trying to run the newly installed Reader app (v1.1.05.13310). In my case it turned out to be that: I run my Mac with a case-sensitive filesystem, and the binary is looking for the framework library with a slightly different name than what it installed. It seems to be looking for this:

/Applications/Reader.app/Contents/Frameworks/QtWebKit.framework/Versions/4/QtWebKit

but it actually installed this:

<same path>/QtWebkit

Note final lower-case "k". Simply renaming the framework file as QtWebKit solved the problem for me.

This is clearly just a filename case naming bug in the build, they didn't do testing and QA on a Mac with case-sensitive filesystem. If I can figure out how to file a bug report with Sony, I will do so...
BrentP is offline   Reply With Quote