Closed GoogleCodeExporter closed 9 years ago
how to roll-back to previous version? (not available in repository)
Original comment by angel.ba...@gmail.com
on 26 Apr 2008 at 9:27
Same problem here, I'm afraid. 1.1.4 firmware
Original comment by michael@tyson.id.au
on 26 Apr 2008 at 2:13
I'm rather loath to admit this, but I honestly have no clue what's going wrong
with
this dialog issue. None of Books' developers have been able to reproduce this.
Assuming you're starting with a fresh preferences file and all rights are
correct on
the EBooks directory, this has never happened for us.
As kind of a last ditch appeal, is there anyone experiencing this problem who's
geographically near Albany, NY, USA? I think it's at the point that I need to
see a
malfunctioning device to have any prayer of fixing the problem. Failing that,
if
anyone's willing and able to give me remote SSH to their device and chat via
phone or
IM, that might work as well. Any volunteers, please email pendorbound at gmail.
Original comment by pendorbo...@gmail.com
on 26 Apr 2008 at 3:01
Previous version worked fine on a fresh OOB 1.1.4, so no reason to suspect the
firmware. In case this could
be of any help, recently upgraded the BSD subsystem which broke the terminal
application (fixed later via a
patched version). Maybe this problem has a similar cause outside the Books
application
Original comment by angel.ba...@gmail.com
on 26 Apr 2008 at 3:40
Additional information in case it is of any use:
Books, version 1.4-r469
iPhone: 1.1.4 (4A102
screenshot attached
Original comment by angel.ba...@gmail.com
on 26 Apr 2008 at 3:52
Attachments:
Thanks for the screen shot. That is exactly like what I've seen other users
report.
On the few phones I've had access to that showed this problem, deleting Books'
preferences file and fixing file rights as described in
http://code.google.com/p/iphoneebooks/wiki/Troubleshooting113 has always fixed
it.
If users are still seeing this problem AFTER following those steps, then I'm
stumped.
Honestly, I suspect either the original preferences file hasn't been deleted or
rights have not been repaired as described in that wiki page.
Original comment by pendorbo...@gmail.com
on 26 Apr 2008 at 4:17
I have changed the permissions as explained in the page you mentioned and the
program
runs fine again Thanks very much!
I would be useful to check for this problem automatically while installing
program
new versions and either a) fix it or b) warning the user.
Original comment by angel.ba...@gmail.com
on 26 Apr 2008 at 5:18
I've discovered the the root of the problem. If the books folder is not owned
by 'mobile' it will cause this
erreor. Running chown -R mobile /var/mobile fixes it (check the path, running
from memory).
Original comment by weboluti...@gmail.com
on 27 Apr 2008 at 12:08
chown -R mobile /var/mobile didn't fix the problem for me. Also, looks like
instead of actually loading the
interface it loads a picture of the interface which has poor compression as is
evident by the compression
artifacts around the gear icon that controls preferences on the top right. If
you double tap the screen you
can see the interface try to slide down over the image of the interface but it
is as if it is pushed to a lowe
layer because before the top bar actually finishes sliding out from the top it
disappears. I managed to get
the. preferences to come up once, by tapping in the upper right but it was
completely an accident and can't
get it to do it again.
Original comment by dexter.n...@gmail.com
on 28 Apr 2008 at 5:00
same problem here.
1.1.3 firmware
if i press home to force quit books, on the next startup a dialog appears
asking me to delete some startup stuff,
but no joy.
Original comment by domagoj....@gmail.com
on 4 May 2008 at 8:05
same problem here.
1.1.3 firmware
if i press home to force quit books, on the next startup a dialog appears
asking me to delete some startup
stuff, but no joy.
edit:
this fixes the problem:
http://code.google.com/p/iphoneebooks/wiki/Troubleshooting113
Original comment by domagoj....@gmail.com
on 4 May 2008 at 8:11
Further exchanges with several users having similar problems confirm that this
is
nothing more than a rights issue. The Troubleshooting113 wiki page explains
how to
fix the problem.
I'm closing this issue as invalid. For the record, any further reports that
complain
of similar issues without giving a very convincing report of having correctly
run the
fixes in Troubleshooting113 will be closed without comment. Not that anyone
will
bother searching closed issues to find this note, but whatever...
Original comment by pendorbo...@gmail.com
on 4 May 2008 at 9:54
This is fixed in r518. You'll still have to fix the underlying file access
issue,
but the error dialog will at least display correctly.
Original comment by pendorbo...@gmail.com
on 14 May 2008 at 3:02
Original issue reported on code.google.com by
weboluti...@gmail.com
on 10 Apr 2008 at 10:24