Le dim. 10 nov. 2024 à 18:07, Andreas Rönnquist <gus...@debian.org> a écrit : > Hmmm, that's really weird - I don't see these problems on my system, > and I have an unstable which I update pretty much all the time.
Yes, I was surprised because it had been a while since I had a problem. Feel free to close this issue if you think it's not that common or useful for investigation. > If you find no way to start lollypop, I would probably try to simply > remove the database (the lollypop .db file) - as you probably know this > is just a database for Lollypop, and it doesn't include the actual > music, which is in files of their own, so it should be safe to remove > it, and then regenerate it. Already done while keeping the broken database just in case. Many thanks, Patrice ~/.l/s/lollypop> ls -l lollypop.db* -rw-r--r-- 1 patrice patrice 1150976 10 nov. 18:22 lollypop.db -rw-r--r-- 1 patrice patrice 1138688 6 nov. 19:47 lollypop.db.broken ~/.l/s/lollypop> file lollypop.db* lollypop.db: SQLite 3.x database, user version 48, last written using SQLite version 3046001, file counter 352, database pages 281, cookie 0xe, schema 4, UTF-8, version-valid-for 352 lollypop.db.broken: data
