'disk I/O error'
Report ID: 40729892
I am using Zotero 1.0.10, under Firefox 3.5.5pre, under Ubuntu Karmic 9.10, and I have a database of 100 or so journal articles and associated PDFs.
My collections are listed correctly in the left-hand pane of Zotero, but when I click on any of them (including "My Library"), the central pane simply shows "Loading items list..." and then waits forever.
The "Report Errors..." function gives a long stream of SQL and Javascript, including "[ERROR: disk I/O error]".
The funny thing is, exporting my library to Zotero RDF format seems to work fine. I glanced at the XML output, and it looks okay.
There appear to be nothing wrong with the ondisk zotero.sqlite file, nor any other obvious problem. Any idea what's going on here?
I'm tempted to just delete the whole Zotero directory, upgrade to Zotero 2.0 beta, and then restore everything from the exported library in Zotero RDF format. Any problem with doing this?
I am using Zotero 1.0.10, under Firefox 3.5.5pre, under Ubuntu Karmic 9.10, and I have a database of 100 or so journal articles and associated PDFs.
My collections are listed correctly in the left-hand pane of Zotero, but when I click on any of them (including "My Library"), the central pane simply shows "Loading items list..." and then waits forever.
The "Report Errors..." function gives a long stream of SQL and Javascript, including "[ERROR: disk I/O error]".
The funny thing is, exporting my library to Zotero RDF format seems to work fine. I glanced at the XML output, and it looks okay.
There appear to be nothing wrong with the ondisk zotero.sqlite file, nor any other obvious problem. Any idea what's going on here?
I'm tempted to just delete the whole Zotero directory, upgrade to Zotero 2.0 beta, and then restore everything from the exported library in Zotero RDF format. Any problem with doing this?
Unless the DB integrity check in the Advanced pane of the Zotero prefs indicates a problem (in which case you could use the DB Repair Tool), there's no real reason to think it's a problem with the database.
Exporting and importing is not recommended. If you really thought there was a problem with the file that didn't show up in the integrity check, the DB Repair Tool would be preferable to an export/import.
I also shut down Firefox, moved my Zotero directory to a backup location, and restarted... creating a whole new Zotero directory. The problem still occurs. Really confused :-(
https://bugs.edge.launchpad.net/ubuntu/+source/evince/+bug/449286
Is there some external executable used by Zotero??
So, it turns out that disabling the AppArmor profile for Firefox does fix the problem.
Should I file an Ubuntu bug? I think I ought to figure out some way to gather more info on what's causing the problem with Zotero... The weird thing is my laptop, with a fresh install of Ubuntu Karmic, has no problem with Zotero 2.0 out-of-the-box.
Thanks
When I change the folder were the database is saved (a new folder without any database) Zotero still refuses to run.
dlenski: Did you update to Zotero 2.x to fix the Problem?
Its Firefox 3.5.3 with Zotero 1.0.10 on Ubuntu karmic.
Error ID is 77976681
Eremit7
This is a very bad solution because apparmor is a imported security framework.
As disabling all profiles don't fix the bug it's possible that he is connected to the general apparmor bug:
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/451375
I know this is not your business, but in Bug 449286 (all-ready linked by fcheslack) Jamie Strandboge remarks:
I should point out, that while AppArmor in the kernel is deviating from standard unix semantics by disallowing the access to the deleted file even though the profile allows it, the problem is that zotero seems to have a bug in that it is trying to truncate a file that has already been deleted. If upstream fixes this, then the problem would go away.
https://bugs.edge.launchpad.net/ubuntu/+source/evince/+bug/449286
There may be one remaining case of the error that could occur during a Zotero upgrade. As the explanation from the Ubuntu developer quoted above by eremit7 indicates, this is a kernel bug, though we may be able to work around it in Zotero. We'll look into that, but regardless, you should only need to disable AppArmor in order to upgrade, at which point you should be able to reenable it as long as you have the latest packages installed.
Dan, thanks for the update.
Eremit7