Loading Profile...
Hires images gone after updating from 2.0 to 2.1.1
After the updating process (almost) all the hires images are gone:
The Library only shows scaled lores images (very ugly, LARGE pixels). In the sidebar there are no images at all.
My 2.0-library-file is about 70 MB, the new 2.1.1-file is only about 9 MB. So these images definitely went missing!
Back to 2.0 for now.
The Library only shows scaled lores images (very ugly, LARGE pixels). In the sidebar there are no images at all.
My 2.0-library-file is about 70 MB, the new 2.1.1-file is only about 9 MB. So these images definitely went missing!
Back to 2.0 for now.
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
-
Inappropriate?Hi Jan,
I'm sorry you hit this problem. I haven't seen anyone else with this issue, but we have your data file, and I'll be showing it to the Apple CoreData engineers soon.
Your bug id is in our bug tracking system is 137160. I don't think you can get directly to this bug (because we opened it for you, so you don't have permission), but if you send e-mail to "support@delicious-monster.com" you'll get a new case number that you can monitor (and we'll be able to write you when you solve the problem), and we'll merge your current bug with the new case.
-Wil -
Inappropriate?Hi Jan,
I took your problem to the CoreData team at Apple, and it turns out your database is corrupt in a subtle way - the row that contains one of the hi-res images is corrupt, which doesn't trip up Delicious Library during normal use (I just skip the corrupted row), but does make the upgrade process abort.
You can verify this corruptness using the sqlite3 command-line tool if you'd like - we ran a verify command and sqlite3 told us exactly where the corruption lay.
Database corruption like this is most often caused by the machine being forcibly rebooted or shut down without warning, and so the operating system doesn't have a chance to write out its remaining buffers to disk, which leaves the database in a bad state.
I found a simple way to read the remaining good parts out of your database and create a new, non-corrupted file, which works great (but is obviously missing the one cover that was corrupted) in 2.0 and 2.1 and beyond.
Contact me directly and I'll e-mail it to you or put it someplace that you can download it.
Yours,
-Wil Shipley
Chief Monster, Delicious Monster Software
I’m happy
The company says
this solves the problem
EMPLOYEE
EMPLOYEE
