I’m a computer and open source enthusiast from Toronto, Ontario, Canada.

  • 1 Post
  • 131 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle

  • The error sounds like your sqlite database file is borked, misplaced or not named correctly. Make sure to shut down Plex on the source Windows machine fully before copying it over. Also make sure the path to the database file is valid - not sure where Plex stores that. Also keep in mind that Linux paths and file names are cAsE SenSiTiVE, so if your db file was named “Plex.db” on Windows, and the Linux version of Plex expects “plex.db” - you will get an error.

    Other issues to anticipate related to file/directory naming: library/metadata paths. You may need to redefine/rescan all your media libraries to fix that depending on how Plex handles transitions between platforms that use different path separators (Windows = \ and Linux/macOS = /) and case sensitivity (Windows and macOS = case INsensitive and Linux = case sensitive).

    Also consider a DB backup/restore (feature built into Plex) may be a better way to transition vs. just copying the DB file over.

    If you’re feeling adventurous, you can download a SQLite browser and take a peek at the Plex DB file. See if there are any red flags like paths to libraries that include Windows specific stuff like drive letters. That will probably break in Linux if just copied over. The backup/restore feature may account for that and actually try to take care of the differences… but that’s just a guess; I never tried this and have no experience with it.

    Note: I never bothered to run Plex on anything other than Linux.

    P.S. some here suggested using Docker (or Podman - probably better in the long run) to deploy Plex. I strongly recommend that option as well, since it abstracts a lot of the nuts and bolts that you no longer need to care about.












  • My guess is that some businesses get tax breaks from municipalities in exchange for filling office spaces with warm bodies. The idea is that people in office buildings support local businesses by buying lunch, and sometimes grabbing a pint after work.

    I’m not trying to excuse this trend, in fact as an IT person myself I 100% agree with the sentiment, I’m just trying to share what I’ve been told.




  • If it is indeed a boneheaded mistake, then it’s probably because of over reliance on RPC-type calls from the front-end that displays the data, to the back-end that actually handles the data. User deletes photo, and the front-end, instead of actually deleting it, tells the backend to do it… and then hides the photo from view, maybe updates its index of photos marking them as “deleted” regardless of whether the backend actually deleted the photo.

    Then an OS update comes along, and rescans the filesystem, and report a bunch of new photos to the front-end, that then happily add them to the GUI to the user’s surprise.

    Modern APIs and software architectures are a bloated, unnecessarily complex mess, and this is the result.






OSZAR »