Re: [darktable-user] Corrupted installation of darktable on Linux Mint 21
On 12/15/22 18:10, Willy Williams wrote: I've run into a challenge on my one Linux Mint 21 computer. Since yesterday, when I start darktable, I get the message below. I've deleted the lock files repeatedly, to no avail. I've uninstalled and reinstalled darktable, but get the same message every time. I am NOT a Linux wizard and haven't a good idea of how to resolve this issue. Anyone got some good advice? I'm hoping to come to a successful resolution before darktable 4.2 springs out later this month. Willy Williams -- "When a photo of a person looks deep into your spirit and tells you a thousand stories ... stories from your past even before you existed, then the photo is way above any description." - Sameh Elsayed -- I am not a Mint user (I use Ubuntu), but you should have an application named "System Monitor". You need to open that and make sure you are on the Processes tab. If you see one called 'darktable', press End Process on the lower right border of the System Monitor window, then press End Process on the pop-up. Check to make sure you do not have multiple darktable processes. Cecil Carpenter darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Darktable will not convert database after upgrade to 3.6.1
On 11/6/21 9:39 PM, Patrick Shanahan wrote: > * Butch Carpenter [11-06-21 18:35]: >> On 11/6/21 4:48 PM, Tony Arnold wrote: >>> >>> On Sat, 6 Nov 2021 at 18:23, Butch Carpenter >> <mailto:csc...@gmail.com>> wrote: >>> >>> >>> On 11/6/21 12:27 PM, Patrick Shanahan wrote: >>>> * Butch Carpenter <mailto:csc...@gmail.com> >>>> [11-06-21 12:12]: >>>>> Here's what I get from the integrity check: >>>>> >>>>> sqlite3 ~/.config/darktable/library.db "PRAGMA integrity_check" >>>>> ok >>>>> >>>>> Then when I start darktable from a terminal and respond with "upgrade >>>>> database", here's the results: >>>>> >>>>> /usr/bin/darktable %U >>>>> [init] can't drop table images_old >>>>> [init] FOREIGN KEY constraint failed >>>>> [init] database `library.db' couldn't be upgraded from version 32 to >>>>> 34. >>>>> aborting >>>>> ERROR : cannot open database >>> >>> My concern here would be the table 'images_old' and why it can't be >>> dropped. I don't think such a table is normally present. I'd take a >>> look at the db with a suitable sqlite browser and see if it's there >>> and what the foreign key constraints are on it. Possibly try and drop >>> the table manually (take a back up first!) >>> >>> Just a thought. >>> >>> Regards, >>> Tony. >>> >> There is no image_ old object anywhere within my entire system. That >> includes / and all connected media. So that is a mystery that the >> developers would need to investigate. In any case, I have deleted >> library.db and begun importing my collection. Only 1200 or so more to go. > fwiw: I have no table, images_old in my library.db > removing that table from library.db might solve your problem > > just for what-ever reason, you might move your new library.db and replace > it with the old library.db and use something like sqlitebrowser to remove > the table images_old. then try to use dt as when you did before. but > when you start dt from the command-line, use: > /usr/bin/darktable > w/o the %U I inadvertently left off the s from the table. It should have read "images_old". There is no table named images_old in my old library.db. Therefore I cannot remove that table since it does not exist.. In fact, there are no data elements named images_old in my old library.db. I checked the entire schema. I also checked foreign keys. Since there is no images_old, there is no issue with FK constraints. Yes, I am using the library.db that failed in the above statements. Darktable is running just fine since I renamed my old library.db and imported all the directories. Perhaps the developers can determine what happened here. > > darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Darktable will not convert database after upgrade to 3.6.1
On 11/6/21 4:48 PM, Tony Arnold wrote: > > > On Sat, 6 Nov 2021 at 18:23, Butch Carpenter <mailto:csc...@gmail.com>> wrote: > > > On 11/6/21 12:27 PM, Patrick Shanahan wrote: >> * Butch Carpenter <mailto:csc...@gmail.com> [11-06-21 >> 12:12]: >>> Here's what I get from the integrity check: >>> >>> sqlite3 ~/.config/darktable/library.db "PRAGMA integrity_check" >>> ok >>> >>> Then when I start darktable from a terminal and respond with "upgrade >>> database", here's the results: >>> >>> /usr/bin/darktable %U >>> [init] can't drop table images_old >>> [init] FOREIGN KEY constraint failed >>> [init] database `library.db' couldn't be upgraded from version 32 to 34. >>> aborting >>> ERROR : cannot open database > > > My concern here would be the table 'images_old' and why it can't be > dropped. I don't think such a table is normally present. I'd take a > look at the db with a suitable sqlite browser and see if it's there > and what the foreign key constraints are on it. Possibly try and drop > the table manually (take a back up first!) > > Just a thought. > > Regards, > Tony. > There is no image_ old object anywhere within my entire system. That includes / and all connected media. So that is a mystery that the developers would need to investigate. In any case, I have deleted library.db and begun importing my collection. Only 1200 or so more to go. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Darktable will not convert database after upgrade to 3.6.1
On 11/6/21 3:59 PM, Patrick Shanahan wrote: > * Butch Carpenter [11-06-21 14:25]: >> On 11/6/21 12:27 PM, Patrick Shanahan wrote: >>> * Butch Carpenter [11-06-21 12:12]: >>>> Here's what I get from the integrity check: >>>> >>>> sqlite3 ~/.config/darktable/library.db "PRAGMA integrity_check" >>>> ok >>>> >>>> Then when I start darktable from a terminal and respond with "upgrade >>>> database", here's the results: >>>> >>>> /usr/bin/darktable %U >>>> [init] can't drop table images_old >>>> [init] FOREIGN KEY constraint failed >>>> [init] database `library.db' couldn't be upgraded from version 32 to 34. >>>> aborting >>>> ERROR : cannot open database >>>> >>>> On 11/6/21 10:01 AM, Patrick Shanahan wrote: >>>>> sqlite3 ~/.config/darktable/library.db "PRAGMA integrity_check" >>> 1. normally when one asks asks a question "on list", the conversation >>> should continue on the list as others may be interested or may have better >>> answers to the question. I have cc'd this to the list. >>> >>> 2. did you do the VACUUM step >>> >>> 3. why start darktable with "%U"? >>> >>> 4. are there still instances of darktable running (ERROR : cannot open >>> database) >>>ps aux | grep darktable >>>ps aux | library.db >>> >>>if either show an existing instance, kill that instance (darktable >>>first) >> 1. Sorry about the last reply. I accidentally hit Reply instead of >> Reply All. >> >> 2. I did the Vacuum step with no change. >> >> 3. The install created a Menu item with that command to launch darktable. >> >> 4. Both processes were running. I killed them in the order you recommended. >> >> I still get >> >> /usr/bin/darktable >> [init] can't drop table images_old >> [init] FOREIGN KEY constraint failed >> [init] database `library.db' couldn't be upgraded from version 32 to 34. >> aborting >> ERROR : cannot open database > what are the permissions on your db > ls -la /home//.config/darktable/library.db do you have a great number of photos in your library? > do you save the xmp files along side your images? > > you might remove the library.db and reimport your images, if you have the > xmp files, they contain your editing history. Permissions are -rw-r--r-- ~32,000 images Yes, I have the xmp files in the same directories as my images, one directory per shooting session darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Darktable will not convert database after upgrade to 3.6.1
On 11/6/21 12:27 PM, Patrick Shanahan wrote: > * Butch Carpenter [11-06-21 12:12]: >> Here's what I get from the integrity check: >> >> sqlite3 ~/.config/darktable/library.db "PRAGMA integrity_check" >> ok >> >> Then when I start darktable from a terminal and respond with "upgrade >> database", here's the results: >> >> /usr/bin/darktable %U >> [init] can't drop table images_old >> [init] FOREIGN KEY constraint failed >> [init] database `library.db' couldn't be upgraded from version 32 to 34. >> aborting >> ERROR : cannot open database >> >> On 11/6/21 10:01 AM, Patrick Shanahan wrote: >>> sqlite3 ~/.config/darktable/library.db "PRAGMA integrity_check" > 1. normally when one asks asks a question "on list", the conversation > should continue on the list as others may be interested or may have better > answers to the question. I have cc'd this to the list. > > 2. did you do the VACUUM step > > 3. why start darktable with "%U"? > > 4. are there still instances of darktable running (ERROR : cannot open > database) >ps aux | grep darktable >ps aux | library.db > >if either show an existing instance, kill that instance (darktable >first) 1. Sorry about the last reply. I accidentally hit Reply instead of Reply All. 2. I did the Vacuum step with no change. 3. The install created a Menu item with that command to launch darktable. 4. Both processes were running. I killed them in the order you recommended. I still get /usr/bin/darktable [init] can't drop table images_old [init] FOREIGN KEY constraint failed [init] database `library.db' couldn't be upgraded from version 32 to 34. aborting ERROR : cannot open database > > > darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
