Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.ubuntu    |    I preferred Xubuntu, seemed a bit faster    |    134,474 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 132,972 of 134,474    |
|    Paul to wAYNE    |
|    Re: some images black in Shotwell deskto    |
|    23 Sep 22 02:58:53    |
      From: nospam@needed.invalid              On 9/22/2022 9:13 PM, wAYNE wrote:       > On 9/21/22 6:37 PM, Paul wrote:       >> On 9/21/2022 2:12 PM, wAYNE wrote:       >>> Been using Shotwell as control for desktop slideshow. Once every 3 min,       image changes. I noticed today, however, that after I deleted some existing       images from the background folder and then reuploaded to Shotwell, it's like       it's still trying to        display the missing images. Even tried copying existing images to a new       folder, background1, then deleting prior folder and all images from Shotwell       and it's still showing black occasionally. Any ideas welcome. Perhaps       there's a Shotwell config        cached that I need to delete?       >>>       >>       >> /home/wayne/.local/share/shotwell/data/photo.db # sqlite database       >>       >> Library: Missing Files # shows thumbnails sitting in       the thumbnail directory       >> # for       files that no longer exist. Hard to say what would       >> # happen       if the thumbnails got deleted. Probably "anarchy".       >> #       ~/.cache/shotwell contains thumbnails.       >> # The       database is the controlling element, in any case.       >> # It is       worshiped.       >>       >> Select files with mouse # Tell the tool which vacant       files to deal with       >> Orange selection rectangles       >>       >> Right-click, "Remove from Library" # Should remove the vacant files       from photo.db .       >>        # Presumably removing their thumbnail as well.       >>       >> *******       >>       >> sqlite3 /home/wayne/.local/share/shotwell/data/photo.db .dump >       photo_database_text.txt       >>       >> That will show you the current database contents, and likely,       >> what it plans to use for a slideshow. Just a guess.       >>       >> The database has a number of "CREATE INDEX" calls near the end. And       >> somehow, that's how it tells one thumbnail from another. The thumbnail       >> identifiers don't seem to be stored in a table, that I can see. My       understanding       >> of databases is very shaky.       >>       >> There are fewer thumbnails than photos. I have no idea what that means.       >> There are more photos of the .png persuasion, than there are thumbnails.       >>       >> The MD5SUM value in the table, is for the master photograph, not for a       thumb.       >>       >> This appears to be about as much fun as you would expect.       >>       >> Paul       >>       >       > Was going to try this process, but what opens this type of file? I       downloaded and installed "db browser for sqlite" but it wouldn't open it.              Try:               sqlite3 photo.db .dump              and a bunch of text should be dumped into the Terminal.              You can also try               file photo.db              and determine if it is a Berkeley db, a JetBlue, a sqlite, a maria or whatever.              For forensics, I start with the "file" command. Surprisingly, the       "file" command is unable to keep up with modern invention, and       some stuff you would expect to be there, is missing. Still, your       file browsing thingy relies on "file" command, to determine what to do with       a file. The /etc/magic file contains the gubbins that make "file" work.              Only Level 39 Wizards know how to add entries to /etc/magic, and       if those Wizards die... The trick is, the entries in /etc/magic       cannot collide with one another, or bad things happen. There       can be hundreds of detections in there. People who "create"       new file types, are well advised to not be creating file formats       which accidentally match the magic of an existing file type.       I do not know who provides an idiot alerting service, to       stop mischief like that. At one time, there used to be USENET       conversations on the crafting of new /etc/magic entries,       by those Wizards. But I have not seen such a discussion in       a donkeys age.               Paul              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca