| Summary: | Tagging in Album View deletes picture (Rygel NAS server relevant) | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Arne <arneklindt> |
| Component: | Tags-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | critical | CC: | caulier.gilles, denisq |
| Priority: | NOR | ||
| Version: | 3.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.1.0 | |
| Sentry Crash Report: | |||
|
Description
Arne
2014-04-18 05:29:19 UTC
Switching to the english GUI I see that the two views I can reproduce the bug on are called "thumbnails" and "preview" There seems to be a connection to a running instance of Rygel on my system. When Rygel is stopped, tagging works as usual. Rygel ??? what is that ? Gilles Caulier This is it : http://www.collabora.com/projects/rygel/ ??? There is no relation with digiKam... Gilles Caulier 2014-06-12 9:51 GMT+02:00 Arne Klindt <arneklindt@gmail.com>: > I found that "Rygel" outputs this, when I tag a file in DigiKam: > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > file:///home/arne/Bilder/digikam4.db-journal konnte nicht erhalten werden > > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > file:///home/arne/Bilder/thumbnails-digikam.db-journal konnte nicht erhalten > werden > > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > file:///home/arne/Bilder/digikam4.db-journal konnte nicht erhalten werden > > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > file:///home/arne/Bilder/2014-06/2014-06-08/jpg/IMG_6468.JPG2135 konnte > nicht erhalten werden > > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > file:///home/arne/Bilder/digikam4.db-journal konnte nicht erhalten werden > > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > file:///home/arne/Bilder/digikam4.db-journal konnte nicht erhalten werden > > sorry for the german installation. Should mean: Fileinformation for xxx > could not be retrieved. So it definitely does something in file-operations > like tagging. > Why this should be a problem I obviously don't know and understand. Fact is: > Whenever I stop Rygel I can tag files as I used to (with or without > sidecars), with Rygel running the file is lost during tagging if I don't use > sidecar-files. I have no idea. Rygel use Mysql database. Do you use Mysql database with digiKam ? Gilles Caulier Using SQLite... 2014-06-12 10:20 GMT+02:00 Gilles Caulier <caulier.gilles@gmail.com>: > https://bugs.kde.org/show_bug.cgi?id=333565 > > --- Comment #5 from Gilles Caulier <caulier.gilles@gmail.com> --- > 2014-06-12 9:51 GMT+02:00 Arne Klindt <arneklindt@gmail.com>: > > I found that "Rygel" outputs this, when I tag a file in DigiKam: > > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > > file:///home/arne/Bilder/digikam4.db-journal konnte nicht erhalten werden > > > > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > > file:///home/arne/Bilder/thumbnails-digikam.db-journal konnte nicht > erhalten > > werden > > > > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > > file:///home/arne/Bilder/digikam4.db-journal konnte nicht erhalten werden > > > > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > > file:///home/arne/Bilder/2014-06/2014-06-08/jpg/IMG_6468.JPG2135 konnte > > nicht erhalten werden > > > > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > > file:///home/arne/Bilder/digikam4.db-journal konnte nicht erhalten werden > > > > (rygel:5850): MediaExport-WARNING **: Dateiinformation für > > file:///home/arne/Bilder/digikam4.db-journal konnte nicht erhalten werden > > > > sorry for the german installation. Should mean: Fileinformation for xxx > > could not be retrieved. So it definitely does something in > file-operations > > like tagging. > > Why this should be a problem I obviously don't know and understand. Fact > is: > > Whenever I stop Rygel I can tag files as I used to (with or without > > sidecars), with Rygel running the file is lost during tagging if I don't > use > > sidecar-files. > > I have no idea. > > Rygel use Mysql database. Do you use Mysql database with digiKam ? > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > Well, no idea why Rygel open digiKam database files which lock of course digiKam features relevant of database (file are read only). So it's an important dysfunction provided by this application. This is not a digiKam problem. Please report this to Ubuntu bugzilla as UPSTREAM bug... Gilles Caulier Sorry I'm rather new to this bug reporting stuff (thanks to Fedora, KDE and DigiKam) so should I really use Ubuntu Bugzilla when my system is a fedora 20? Because they are the maintainers of Rygel? 2014-06-12 11:56 GMT+02:00 Gilles Caulier <caulier.gilles@gmail.com>: > https://bugs.kde.org/show_bug.cgi?id=333565 > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution|--- |UPSTREAM > > --- Comment #7 from Gilles Caulier <caulier.gilles@gmail.com> --- > Well, no idea why Rygel open digiKam database files which lock of course > digiKam features relevant of database (file are read only). > > So it's an important dysfunction provided by this application. This is not > a > digiKam problem. Please report this to Ubuntu bugzilla as UPSTREAM bug... > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > No, sorry, my mistake... Use Fedora bugzilla of course (:=))) Gilles Caulier Hi, I get the same porblem under openbox LXDE on Fedora 20. digiKam versió 3.5.0 S'utilitza la «KDE Development Platform» 4.12.5 I notice that it depends of where in the file tree are the pictures you are working on. But I have no idea of what. Arne, I did not find your bug report in Fedora ... https://bugzilla.redhat.com/show_bug.cgi?id=1108637 It should be there... 2014-06-18 14:28 GMT+02:00 Denis <denisq@free.fr>: > https://bugs.kde.org/show_bug.cgi?id=333565 > > Denis <denisq@free.fr> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |denisq@free.fr > > --- Comment #10 from Denis <denisq@free.fr> --- > Hi, > > I get the same porblem under openbox LXDE on Fedora 20. > digiKam > versió 3.5.0 > S'utilitza la «KDE Development Platform» 4.12.5 > > I notice that it depends of where in the file tree are the pictures you are > working on. But I have no idea of what. > > Arne, I did not find your bug report in Fedora ... > > -- > You are receiving this mail because: > You reported the bug. > Hi, I have some doubts about rygel guilty. I had desable rygel on my system by systemctl desable rygel However, does not change that problem. I should had to my last comment yesterday that it is not upon the directory that its hapen. It is more a random event wherever in the directory tree is the picture. Since I had changed the option to "settings/metadata/writing only in anexed files" , everything seeems to be normal (I continue to test it) - before the option was : writing in RAW, noticed as experimental. Arne could you try it confirm ? And if Rygel has open digiKam database in writing mode and corrupted table ??? Do you see what i mean ? Gilles Caulier Yes, I see what you mean. I had done a copy of the database the first time it happened and asked digikam to rebuild it. The problem happened again. The clue is that I do not have an other computer/system to test this database with another digikam under kde for example. Now, the question that digikam developers can answer is the following : does a corrupted data in the database can lead digikam to eradicate the relevant file ? If it does, this is definitely a bug to my opinion. Digikam does not attempt to delete a file unless you tell it to do so via the Delete dialog. |