On os2.org someone reported a similiar issue. Deleting .dooble folder solved this issue and download was possible.
Profiles certainly seem to be fragile - sqlite issues?
Could be, have to be both the version that Qt5 uses as well as Qt6.
Playing with wal (write ahead logging,
https://www.sqlite.org/wal.html, while things work, I get no wal files, do get shm files.
4-10-23 8:15a 4,907,008 124 a--- dooble_accepted_or_blocked_domains.db
4-14-23 7:29a 32,768 124 a--- dooble_accepted_or_blocked_domains.db-shm
3-05-23 9:32a 4,096 124 a--- dooble_certificate_exceptions.db
4-14-23 7:29a 32,768 124 a--- dooble_certificate_exceptions.db-shm
4-14-23 7:41a 114,688 124 a--- dooble_cookies.db
4-14-23 7:41a 32,768 124 a--- dooble_cookies.db-shm
shm never worked for Mozilla as we were lacking the mmap support. We also had to get Ihle to add the wal support to sqlite for OS/2 when Mozilla started using it. That was before sqlite removed OS/2 support.
Thing is really how we're maintaining our fork by maintaining the old code isn't ideal. What should have been done was someone writing a vfs for us.
https://www.sqlite.org/vfs.htmlAs our wal support was added at a time when mmap shared memory wasn't available, perhaps it has introduced a bug now that the build process finds it.
I will note that sqlite seems fine here with wal turned on.
sh script to enable wal when run in .dooble,
ls *.db | while read filename;
do sqlite3 $filename 'PRAGMA journal_mode=WAL;';
done;
change the WAL to delete in the PRAGMA line to turn it off.
