[Bug 194950] New: Digikam endlessly spewing text to stderr

https://bugs.kde.org/show_bug.cgi?id=194950

           Summary: Digikam endlessly spewing text to stderr
           Product: digikam
           Version: 0.10.0
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]


Version:           0.10.0 (using KDE 4.2.3)
OS:                Linux
Installed from:    Unlisted Binary Package

The moment I modify the first photo after starting digikam, it starts throwing
the following lines into stderr every second or so:

digikam(8503)/digikam (core) Digikam::AlbumManager::slotDirWatchDirty:
KDirWatch detected change at "/multimedia/foto/digikam4.db-journal"
digikam(8503)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder does
not exist or is not readable:  "/multimedia/foto/digikam4.db-journal"

I don't know if it's relevant, but I keep my photo collection in a FAT32
filesystem. The only impact of this bug is that after some time of working with
digikam, the konsole window history file becomes several dozens MiB in size.
The entries just before this starts are as follows:

digikam(1536)/digikam (core) Digikam::DMetadata::setImageComment:
"/multimedia/foto/todo/new/2009-05-03/dsc_0419.jpg"  ==> Comment:  ""  
digikam(1536)/digikam (core) Digikam::DMetadata::setImageRating: Rating value
to write is out of range!                                  
digikam(1536)/digikam (core) Digikam::AlbumManager::slotDirWatchDirty:
KDirWatch detected change at "/multimedia/foto/digikam4.db"        
digikam(1536)/digikam (core) Digikam::AlbumManager::slotDirWatchDirty:
KDirWatch detected change at "/multimedia/foto/digikam4.db-journal"
digikam(1536)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder does
not exist or is not readable:  "/multimedia/foto/digikam4.db"                  

digikam(1536)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder does
not exist or is not readable:  "/multimedia/foto/digikam4.db-journal"

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=194950


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #1 from Gilles Caulier <caulier gilles gmail com>  2009-06-19 11:59:15 ---
Pawel,

Sound like a mounting problem with your FAT32 partition.

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

https://bugs.kde.org/show_bug.cgi?id=194950


Daniel Svärd <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #2 from Daniel Svärd <daniel svard gmail com>  2009-07-04 00:01:49 ---
I have the same problem and I am not using FAT32, I am using ReiserFS.

I can edit the photo in the image editor, but when I edit the metadata and
apply it, that is when it starts spewing out those messages.

I use Archlinux (kdemod) and Digikam gives me the following in the component
information dialog:

digiKam version 0.10.0
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 support XMP metadata: Yes
LibCImg: 130
LibExiv2: 0.18
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.2.4 (KDE 4.2.4)
LibKExiv2: 0.5.0
LibKdcraw: 0.4.2
LibLCMS: 117
LibPNG: 1.2.35
LibQt: 4.5.1
LibRaw: 0.6.15-Release
LibTIFF: LIBTIFF, Version 3.8.2 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
LibGphoto2: 2.4.6
LibKipi: 0.3.0

I don't know if it was smart or not, but I tried creating the directory
digikam4.db-journal in my collection directroy. It stopped the messages, but it
also stopped displaying all of my albums and images in Digikam's main view with
the following console output:

digikam(29381)/digikam (core) Digikam::AlbumManager::slotDirWatchDirty:
KDirWatch detected change at "/home/atod/Pictures/digikam4.db-journal"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "SELECT value
FROM Settings WHERE keyword=?;"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:
(QVariant(QString, "databaseImageFormats") )
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "SELECT value
FROM Settings WHERE keyword=?;"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:
(QVariant(QString, "databaseUserImageFormats") )
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "SELECT value
FROM Settings WHERE keyword=?;"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:
(QVariant(QString, "databaseVideoFormats") )
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "SELECT value
FROM Settings WHERE keyword=?;"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:
(QVariant(QString, "databaseUserVideoFormats") )
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "SELECT value
FROM Settings WHERE keyword=?;"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:
(QVariant(QString, "databaseAudioFormats") )
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "SELECT value
FROM Settings WHERE keyword=?;"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:
(QVariant(QString, "databaseUserAudioFormats") )
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "DELETE FROM
Albums WHERE albumRoot=0;"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:  ()
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "SELECT
Albums.id, Albums.relativePath, Albums.albumRoot from Albums; "
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:  ()
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "SELECT id FROM
Albums WHERE albumRoot=? AND relativePath=?;"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:
(QVariant(int, 1) ,  QVariant(QString, "/digikam4.db-journal") )
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "REPLACE INTO
Albums (albumRoot, relativePath, date, caption, collection) VALUES(?, ?, ?, ?,
?);"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:
(QVariant(int, 1) ,  QVariant(QString, "/digikam4.db-journal") ,
QVariant(QString, "2009-07-03") ,  QVariant(QString, "") ,  QVariant(QString,
"") )
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "SELECT id,
album, name, status, category, modificationDate, uniqueHash FROM Images WHERE
album=?;"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:
(QVariant(int, 0) )
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Failure executing
query:
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "SELECT
A.albumRoot, A.id, A.relativePath, A.date, A.caption, A.collection,
B.albumRoot, B.relativePath, I.name
 FROM Albums AS A
   LEFT OUTER JOIN Images AS I ON A.icon=I.id
  LEFT OUTER JOIN Albums AS B ON B.id=I.album
 WHERE A.albumRoot != 0;"
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: "disk I/O error
Unable to fetch row" 10
digikam(29381)/digikam (core) Digikam::DatabaseBackend::exec: Bound values:  ()
digikam(29381)/kio (Slave) KIO::Slave::createSlave: createSlave "digikamalbums"
for
KUrl("digikamalbums:?databaseType=QSQLITE&databaseName=/home/atod/Pictures/digikam4.db")
digikam(29381)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote:
Listening on  "local:/tmp/ksocket-atod/digikamP29381.slave-socket"

Exiting Digikam, removing the directory and starting Digikam again brought
everything back though.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=194950


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Database




--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=194950


Marcel Wiesweg <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[hidden email]
         Resolution|                            |FIXED




--- Comment #3 from Marcel Wiesweg <marcel wiesweg gmx de>  2009-07-04 11:46:30 ---
This happens to you since a change from KDE 4.2.2 to 4.2.3 changed drastically
the behavior of KDirWatch. One can argue that the behavior improved,
nevertheless it changed between bugfix releases which it shouldnt.

The problem is fixed in current trunk.

@2: No it was not smart to create this directory ;-) It's the name of sqlite's
journal file.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

https://bugs.kde.org/show_bug.cgi?id=194950


Paweł Marciniak <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |VERIFIED




--- Comment #4 from Paweł Marciniak <pave o2 pl>  2009-08-29 20:53:24 ---
I confirm that this looks like fixed now. Thanks guys!

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Francesco Riosa-2]

https://bugs.kde.org/show_bug.cgi?id=194950


Francesco Riosa <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|VERIFIED                    |RESOLVED
                 CC|                            |[hidden email]




--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=194950

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Version Fixed In|                            |2.0.0

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=194950

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Database                    |Database-Scan

--
You are receiving this mail because:
You are the assignee for the bug.