[kwin] [Bug 487321] Quick Tile does not size windows equally if there is a panel on screen
https://bugs.kde.org/show_bug.cgi?id=487321 --- Comment #2 from meku --- Do you mean this was an intentional change for Plasma 6? Is there any further information on this? In Plasma 5 the windows are sized equally. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487321] New: Quick Tile does not size windows equally if there is a panel on screen
https://bugs.kde.org/show_bug.cgi?id=487321 Bug ID: 487321 Summary: Quick Tile does not size windows equally if there is a panel on screen Classification: Plasma Product: kwin Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Quick Tiling Assignee: kwin-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- SUMMARY Quick Tiled windows are not sized equally if there is a panel on the screen, windows tiled adjacent to the panel are shorter than other tiled windows. STEPS TO REPRODUCE 1. add panel to top of screen 2. open two windows 3. quick tile windows up and down so that the screen is filled OBSERVED RESULT 1. Top window is sized smaller than half height to account for the panel 2. Bottom window is sized to half the full-screen height EXPECTED RESULT Both tiled windows to have equal height. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240429 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485312] Window appears in task bar of wrong screen in multiscreen setup
https://bugs.kde.org/show_bug.cgi?id=485312 --- Comment #4 from meku --- Not seen in Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485312] Window appears in task bar of wrong screen in multiscreen setup
https://bugs.kde.org/show_bug.cgi?id=485312 meku changed: What|Removed |Added CC||kde.b...@meku.org --- Comment #1 from meku --- I have observed this with a vertical monitor layout. Screen layout: a primary screen and a second screen below it STEPS TO REPRODUCE 1. taskbar and window on the primary screen 2. shrink height of window, in this config the bug triggers when window is less than half the primary screen height. 3. move window towards bottom edge and it will disappear from taskbar before reaching the edge ADDITIONAL INFORMATION 1. the shorter the window, the further away from the bottom edge it will disappear from taskbar 2. this only happens on edges where there is an adjacent screen. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240429 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485836] New: Edit Timezone Offsets in Time & Date Editor
https://bugs.kde.org/show_bug.cgi?id=485836 Bug ID: 485836 Summary: Edit Timezone Offsets in Time & Date Editor Classification: Applications Product: digikam Version: 8.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Date Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- This is a feature request to add the ability to edit the EXIF timezone offset fields. The logical place for this would be in the existing Time & Date Editor. Required abilities: * Add timezone offset to files * Alter timezone offset in files * Remove timezone offset from files Secondarily these abilities would be useful to have in the Batch Queue Manager. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 367700] It should be possible to search for more, if not all metadata fields.
https://bugs.kde.org/show_bug.cgi?id=367700 meku changed: What|Removed |Added CC||kde.b...@meku.org --- Comment #12 from meku --- Created attachment 153069 --> https://bugs.kde.org/attachment.cgi?id=153069=edit Photo with FujiFilm EXIF metadata I would like to amplify this feature request. There are various metadata fields that I find would be very useful to search or filter on, for example (names from exiftool): - ExifIFD.CompositeImage (sometimes used to determine if image is an in-camera HDR) - ExifIFD.LensMake (only the LensModel is currently searchable) Also various maker-specific fields, for example: - FujiFilm.FilmMode - FujiFilm.PictureMode (more reliable than CompositeImage field for determining if image is an in-camera HDR) - FujiFilm.WhiteBalance (more detailed than EXIF WhiteBalance) - FujiFilm.ShutterType (mechanical or electronic) To achieve this will require the bulk image metadata to be indexed to a new DB schema/table to make it searchable. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436345] Renamed FaceTags not written to file metadata
https://bugs.kde.org/show_bug.cgi?id=436345
--- Comment #8 from meku ---
I found the OLD Face names were persisting in the database:
Tags table
id|pid|name|icon|iconkde|
--|---|||---|
19| 18|NEW Name|| |
TagProperties table:
tagid|property |value |
-|--||
19|person|OLD Name|
19|faceEngineId |OLD Name|
19|faceEngineUuid|{uuid..}|
As suspected a previous Tag rename action in Digikam had left the database in
what looks like an inconsistent state. It also appears Digikam is not able to
repair or rectify this inconsistency via Metadata scanning or maintenance.
If I manually rename the OLD values in TagProperties then the correct Face
Regions are now written to the file metadata.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 436345] Renamed FaceTags not written to file metadata
https://bugs.kde.org/show_bug.cgi?id=436345 --- Comment #7 from meku --- Via Menu->Item->Write Metadata to File. In Digikam v7.2.0 there are no errors, the file is modified but the Region names are not changed. In Digikam v7.3.0-20210428T170519 there are no errors, the file is modified bu the Region names are not changed. The console reports some messages: Digikam::ExifToolParser::slotErrorOccurred: ExifTool process for action "Load Metadata" exited with error: QProcess::FailedToStart Digikam::ExifToolProcess::kill: ExifToolProcess::kill(): shutdown ExifTool instance... Digikam::ExifToolParser::Private::prepareProcess: ExifTool process cannot be started ( "././/bin" ) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436345] Renamed FaceTags not written to file metadata
https://bugs.kde.org/show_bug.cgi?id=436345 --- Comment #5 from meku --- This situation is the Face Tags have already been renamed and saved to files in a previous version of Digikam. It seems this step did not write the metadata well. Now in the current Digikam there is no visibility of the OLD tags, they all display as the NEW tags. Yet in the file the XMP Region fields are still using the OLD tags. Here is the issue I am trying to troubleshoot: writing the metadata to files in the current Digikam is still not updating or overwriting the tags in these XMP Region fields. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436345] New: Renamed FaceTags not written to file metadata
https://bugs.kde.org/show_bug.cgi?id=436345 Bug ID: 436345 Summary: Renamed FaceTags not written to file metadata Product: digikam Version: 7.3.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Engine Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- SUMMARY Some Face Tags have been renamed within Digikam and written to files, but the region fields in the XMP are not updated and continue to display the OLD face names. The NEW names display correctly within Digikam: the Faces list, the Tags list, and the Face labels on the preview. The OLD names persist in the files in these XMP fields: [XMP-mwg-rs]RegionName [XMP-MP]RegionPersonDisplayName In the IdentityAttributes table I can see that both the NEW and OLD names are here and they share the same id. EXPECTED OUTCOME: NEW names are written to XMP metadata, replacing OLD names. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435455] Migration cannot drop or create FaceMatrices table [patch]
https://bugs.kde.org/show_bug.cgi?id=435455 --- Comment #7 from meku --- (In reply to Maik Qualmann from comment #6) > New AppImage for testing is available. Has the problem been resolved? Appears to be resolved in digiKam-7.3.0-20210411T170959-x86-64.appimage Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435455] Migration cannot drop or create FaceMatrices table [patch]
https://bugs.kde.org/show_bug.cgi?id=435455 --- Comment #3 from meku --- (In reply to Maik Qualmann from comment #2) > That cannot be the cause, because "identity" is not a reserved keyword in > MySQL. I'm taking a closer look tonight. > > Maik Yeah I think you are right, create statement should work. I must have been looking at the wrong SQL engine list of keywords. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435455] Migration cannot drop or create FaceMatrices table
https://bugs.kde.org/show_bug.cgi?id=435455 --- Comment #1 from meku --- I suspect the DROP TABLE is failing due to a foreign key linking to the FaceMatrices table. Additionally the CREATE TABLE FaceMatrices statement will not run due to missing field escaping: This line: CONSTRAINT FaceEmbedding_Identities FOREIGN KEY (identity) REFERENCES Identities (id) ON DELETE CASCADE ON UPDATE CASCADE) Needs to escape the `identity` field: CONSTRAINT FaceEmbedding_Identities FOREIGN KEY (`identity`) REFERENCES Identities (id) ON DELETE CASCADE ON UPDATE CASCADE) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435455] New: Migration cannot drop or create FaceMatrices table
https://bugs.kde.org/show_bug.cgi?id=435455 Bug ID: 435455 Summary: Migration cannot drop or create FaceMatrices table Product: digikam Version: 7.2.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Mysql Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- SUMMARY Running Digikam with external mysql (using Mariadb) there are failures in the database migration. Debugging output from Digikam: Digikam::FaceDb::setting: FaceDB SelectFaceSetting val ret = 0 Digikam::FaceDb::setting: FaceDB SelectFaceSetting val ret = 0 Digikam::FaceDbSchemaUpdater::startUpdates: Face database: have a structure version "3" Digikam::BdEngineBackendPrivate::debugOutputFailedQuery: Failure executing query: "" Error messages: "QMYSQL: Unable to execute query" "Cannot delete or update a parent row: a foreign key constraint fail s" "1451" 2 Bound values: () Digikam::BdEngineBackend::execDBAction: Error while executing DBAction [ "CreateFaceDBFaceMatrices" ] Statement [ "DRO P TABLE IF EXISTS FaceMatrices;\n" ] Digikam::FaceDbSchemaUpdater::updateV3ToV4: fail to recreate FaceMatrices table -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 428427] Some metadata (tags, captions) not applying to grouped images
https://bugs.kde.org/show_bug.cgi?id=428427 --- Comment #7 from meku --- In Tags manager selecting a group in 7.0.0 would highlight tags from all members, as if you had opened the group and selected all the group members. >From 7.1.0 selecting a group only highlights tags from the top member. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388899] Assigning color labels from right side menu is different than over context menu
https://bugs.kde.org/show_bug.cgi?id=388899 --- Comment #3 from meku --- Testing 7.0.0 - 7.2.0-beta1 I have not found any of these versions use the setting [Miscellaneous >> Grouping >> Metadata >> Perform operations on all group members] when applying the right side Captions widget. In 7.0.0 it always operated on all group members. In 7.1.0 and later it never operates on group members. I had this setting on 'Yes' to silently operate on all group members so did not notice this bug until the behaviour changed in 7.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 428427] Some metadata (tags, captions) not applying to grouped images
https://bugs.kde.org/show_bug.cgi?id=428427 --- Comment #5 from meku --- Sorry I speak too soon. Behaviour has changed between 7.0.0 and 7.1.0 but neither was correct. Neither version respected the setting [Perform operations on all group members]. In 7.0.0 it always operated on all group members. In 7.1.0 and later it never operates on group members. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 428427] Some metadata (tags, captions) not applying to grouped images
https://bugs.kde.org/show_bug.cgi?id=428427 --- Comment #4 from meku --- This bug appeared in 7.1. Tags, captions, and labels were working as expected in 7.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 428427] Some metadata (tags, captions) not applying to grouped images
https://bugs.kde.org/show_bug.cgi?id=428427 --- Comment #1 from meku --- To clarify for the Picks and Labels: Applying Labels to a group of images using the RHS Caption widget _DOES NOT_ work. Assigning Labels using right click menu or keyboard shortcut DOES apply to all members in the group. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 428427] New: Some metadata (tags, captions) not applying to grouped images
https://bugs.kde.org/show_bug.cgi?id=428427 Bug ID: 428427 Summary: Some metadata (tags, captions) not applying to grouped images Product: digikam Version: 7.2.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-Group Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- SUMMARY Applying a tag or caption to a group of images using the Captions widget only updates the top (visible) image. The setting in [Miscellaneous >> Grouping >> Metadata >> Perform operations on all group members] is not respected. Right clicking a group of images and selecting [Assign Tag] DOES work as expected and respects the above settings. Applying Labels to a group of images DOES also work as expected. STEPS TO REPRODUCE 1. Create a group of images, leave group closed 2. Select group 3. Use RHS Caption widget to apply a tag. OBSERVED RESULT Metadata is only applied to visible image of the group. EXPECTED RESULT The setting in [Perform operations on all group members] should be respected, if 'Yes' then metadata should be applied to all images in the group. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP transfer corrupts all files
https://bugs.kde.org/show_bug.cgi?id=405847 meku changed: What|Removed |Added CC|kde.b...@meku.org | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392607] Crash sometimes when applying Tags to images
https://bugs.kde.org/show_bug.cgi?id=392607 --- Comment #19 from meku --- (In reply to caulier.gilles from comment #18) > Meku do you see my comment #16 ? > > Best > > Gilles Caulier Sorry I have not begun using 6.2.0 yet. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408766] New: Corrupted files downloading from KDE Connect
https://bugs.kde.org/show_bug.cgi?id=408766 Bug ID: 408766 Summary: Corrupted files downloading from KDE Connect Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: kde.b...@meku.org Target Milestone: --- SUMMARY Copying files from Android to Linux results in corrupt files. The file size is identical but checksums do not match. STEPS TO REPRODUCE 1. Open KDE Connect in file browser eg. Dolphin 2. Copy file from Android to local file system OBSERVED RESULT File is copied and notification displays transfer is complete. File checksum does not match the source on Android. SOFTWARE Android/KDE Connect 1.12.9 Linux/kdeconnect 1.3.4 OS VERSIONS KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION I have only observed this when copying from Android to Linux. Copying files from Linux to Android appears to work without any noticeable issues. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403269] Stacked image and Panorama tools cannot find required binaries
https://bugs.kde.org/show_bug.cgi?id=403269 --- Comment #25 from meku --- In debug: stacked does not find any required binaries and panorama only finds 'cpfind' and 'make'. Without debug: all the required binaries are successfully detected. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403269] Stacked image and Panorama tools cannot find required binaries
https://bugs.kde.org/show_bug.cgi?id=403269 --- Comment #22 from meku --- Appears to be working again in digikam-6.2.0-git-20190426T172018-qtwebkit-x86-64.appimage Note that running the appimage with 'debug' then the stacked tool cannot find the binaries, though this appears to have been an issue in all versions - including DK 6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403269] Stacked image and Panorama tools cannot find required binaries
https://bugs.kde.org/show_bug.cgi?id=403269 --- Comment #20 from meku --- The mandatory programs do not appear to have changed since my first post. Installed are: hugin-tools v2018.0.0 enfuse v4.2-4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403269] Stacked image and Panorama tools cannot find required binaries
https://bugs.kde.org/show_bug.cgi?id=403269 --- Comment #18 from meku --- Stacked image tool is not working in DK 6.1 or DK 6.2 appimages. The interface now finds the binaries but shows a waiting page with "Pre-processing is under progress, please wait." Looking at running processes there doesn't appear to be any image processing going on. I can confirm it works as expected in final DK 6.0 release. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403269] Stacked image and Panorama tools cannot find required binaries
https://bugs.kde.org/show_bug.cgi?id=403269 --- Comment #13 from meku --- The above commit fails to preload of the shared libs because the lib filenames are not matched. As previously noted, ubuntu paths are: /usr/lib/x86_64-linux-gnu/libfreetype.so.6 /lib/x86_64-linux-gnu/libudev.so.1 Yet this build DOES work for stacking and panorama tools. Is it because $LD_PRELOAD is left unset in this new build? Output from console at startup: -- digiKam AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application -- Preloading shared libs: -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403269] Stacked image and Panorama tools cannot find required binaries
https://bugs.kde.org/show_bug.cgi?id=403269 --- Comment #5 from meku --- On this ubuntu system the libraries are not at the paths that Digikam has hardcoded: libfreetype.so -> /usr/lib/x86_64-linux-gnu/libfreetype.so.6 libudev.so -> /lib/x86_64-linux-gnu/libudev.so.1 If I manually create symlinks to /usr/lib64 then the Stacking/Panorama tools work. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403269] Stacked image and Panorama tools cannot find required binaries
https://bugs.kde.org/show_bug.cgi?id=403269 --- Comment #3 from meku --- Hugin tools appear to be in /usr/bin Console selecting autooptimiser: Digikam::DBinaryIface::checkDir: Testing "/usr/bin/autooptimiser" ... Digikam::adjustedEnvironmentForAppImage: Adjusting environment variables for AppImage bundle Digikam::DBinaryIface::parseHeader: "autooptimiser" help header line: "ERROR: ld.so: object '/usr/lib64/libudev.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored." Digikam::DBinarySearch::slotAreBinariesFound: All Binaries Found : false -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403269] New: Stacked image and Panorama tools cannot find required binaries
https://bugs.kde.org/show_bug.cgi?id=403269 Bug ID: 403269 Summary: Stacked image and Panorama tools cannot find required binaries Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Export-ExpoBlending Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- SUMMARY Stacked images and Panorama tools cannot be used because hugin and enfuse binaries are not found by Digikam. The binaries are in the path and manually selecting their location with 'Find' button does not accept them. Installed packages: hugin-tools v2018.0.0 enfuse v4.2-4 Digikam version: digikam-6.0.0-beta3-20181228T114626-x86-64.appimage SOFTWARE/OS VERSIONS KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392607] Crash sometimes when applying Tags to images
https://bugs.kde.org/show_bug.cgi?id=392607 meku changed: What|Removed |Added Version|5.9.0 |6.0.0 --- Comment #8 from meku --- Latest AppImage (digikam-6.0.0-beta3-20181228T114626-x86-64.appimage) has been crashing frequently while tagging. In this instance the tags were added to all images in the database but only one image file was updated (JPG). Thread 1 "digikam" received signal SIGSEGV, Segmentation fault. 0x0030a1258488 in QSortFilterProxyModel::parent(QModelIndex const&) const () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 (gdb) bt #0 0x0030a1258488 in QSortFilterProxyModel::parent(QModelIndex const&) const () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #1 0x0030a1235253 in QAbstractItemModelPrivate::rowsAboutToBeInserted(QModelIndex const&, int, int) () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #2 0x0030a1239245 in QAbstractItemModel::beginInsertRows(QModelIndex const&, int, int) () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #3 0x0030a1258bfa in ?? () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #4 0x0030a125d261 in ?? () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #5 0x0030a125d537 in ?? () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #6 0x0030a125da51 in QSortFilterProxyModel::invalidateFilter() () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #7 0x778996cd in Digikam::CheckableAlbumFilterModel::setFilterChecked (this=0x12eb390, filter=) at /b/dktemp/digikam-master/core/libs/models/albumfiltermodel.cpp:456 #8 0x777bb49c in Digikam::ItemDescEditTab::slotAssignedTagsToggled (this=0x125eff0, t=true) at /b/dktemp/digikam-master/core/libs/properties/captions/itemdescedittab.cpp:1412 #9 0x777bb64a in Digikam::ItemDescEditTab::updateTagsView (this=this@entry=0x125eff0) at /b/dktemp/digikam-master/core/libs/properties/captions/itemdescedittab.cpp:1109 #10 0x777c0420 in Digikam::ItemDescEditTab::setInfos (this=this@entry=0x125eff0, infos=...) at /b/dktemp/digikam-master/core/libs/properties/captions/itemdescedittab.cpp:802 #11 0x777c07ef in Digikam::ItemDescEditTab::slotReloadForMetadataChange (this=0x125eff0) at /b/dktemp/digikam-master/core/libs/properties/captions/itemdescedittab.cpp:1319 #12 0x777ccc05 in Digikam::ItemDescEditTab::qt_static_metacall (_o=, _c=, _id=, _a=) at /b/dktemp/digikam-master/build/core/libs/properties/moc_itemdescedittab.cpp:253 #13 0x0030a12b9449 in QMetaObject::activate(QObject*, int, int, void**) () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #14 0x0030a12c5c17 in QTimer::timeout(QTimer::QPrivateSignal) () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #15 0x0030a12c5ee8 in QTimer::timerEvent(QTimerEvent*) () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #16 0x0030a12ba35b in QObject::event(QEvent*) () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #17 0x718d028c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Widgets.so.5 #18 0x718d76b7 in QApplication::notify(QObject*, QEvent*) () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Widgets.so.5 #19 0x0030a128ee68 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #20 0x0030a12e0c5e in QTimerInfoList::activateTimers() () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #21 0x0030a12e1441 in ?? () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #22 0x70637c3e in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x70637ed8 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x70637f6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x0030a12e177f in QEventDispatcherGlib::processEvents(QFlags) () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #26 0x0030a128d45a in QEventLoop::exec(QFlags) () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #27 0x0030a1295d34 in QCoreApplication::exec() () from /tmp/.mount_digikajiq4kA/usr/lib/libQt5Core.so.5 #28 0x00405214 in main (argc=1, argv=) at /b/dktemp/digikam-master/core/app/main/main.cpp:290 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402379] Moving location of RAW file causes loss of metadata
https://bugs.kde.org/show_bug.cgi?id=402379 --- Comment #3 from meku --- I have not enabled "Cleanup Database". I am testing with a single collection, on a single partition. I believe there is an additional condition that triggers this bug and it is related to the filesystem timestamps of the photos. Using 'stat' on my system shows nanosecond accuracy. Some files have not been modified for some years and show all zeros for the trailing digits, eg. Modify: 2013-01-29 14:31:22.0 other files have been modified recently and have use all the trailing digits, eg. Modify: 2018-12-23 01:06:52.322555833 This bug appears to be related to the files timestamp has non-zeros in the trailing digits. Furthermore this bug only triggers when a FOLDER is moved, it does not appear to trigger when an individual file is moved. STEPS TO REPRODUCE 1. Create at least 2 test folders with RAW files (include xmp sidecars to test with sidecars enabled) At least one RAW/xmp file should have full resolution timestamp. 'touch' file if necessary to update timestamp and use 'stat' to confirm. 2. Start DK5.9 and add collection with these folders. At this point you can choose whether to test the RAW or xmp timestamps. Select Metadata option 'Read from sidecar files' to test the xmp timestamps. 3. Add some metadata to the file that you 'touched', such as caption or tag. 3. Close DK5.9 4. Open DK6.0 5. Using Digikam album list, move the folder - such as dragging and dropping onto a subfolder. OBSERVED RESULT The metadata added in step 3 will have disappeared. And inspecting the Images database table will show duplicate records with same filename and uniqueHash. ADDITIONAL INFORMATION I have tested this on Ubuntu 18.04.1 with external database MariaDB v10.2.19 Altering the Images table to use DATETIME(3) for 'modificationDate' and then running 'Reread metadata from image' appears to mitigate this bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402380] New: Database schema upgrade to V10 is incomplete
https://bugs.kde.org/show_bug.cgi?id=402380 Bug ID: 402380 Summary: Database schema upgrade to V10 is incomplete Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Mysql Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- SUMMARY Beginning with a DK5.9 database and then running the latest DK6.0b3 (20181215) the database schema is upgraded to v10 but there are many fields that are not updated to the same level as a clean install of DK6.0 For example in v10 many of the INT fields have been changed to BIGINT and DATETIME has been changed to DATETIME(3). STEPS TO REPRODUCE 1. Install DK5.9 with MySQL database 2. Run DK6.0 OBSERVED RESULT Database version is upgraded to v10 but the above fields are not updated. EXPECTED RESULT Database is upgraded to identical structure as a fresh install of DK6.0 ADDITIONAL INFORMATION Having INT instead of BIGINT does not appear to be causing any further issues at this time, however the omission of DATETIME(3) appears to be partly responsible for Bug #402379 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402379] New: Moving location of RAW file causes loss of metadata
https://bugs.kde.org/show_bug.cgi?id=402379 Bug ID: 402379 Summary: Moving location of RAW file causes loss of metadata Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Mysql Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- SUMMARY After upgrading from DK5.9 to DK6.0, moving any RAW file to a new path can cause loss of metadata. Tested with DK6.0b3 (20181215) STEPS TO REPRODUCE 1. Start with DK5.9 or earlier database, with RAW files in database (tested with CR2 and RAF). 2. Enable metadata setting 'read from sidecar' 3. Disable metadata setting 'write to sidecar' 4. Apply any metadata to RAW, such as caption or tags. 5. Run DK6.0, and using DK6.0 interface move the location of any RAW file or folder containing files to a new path within the collection. OBSERVED RESULT RAW files lose any metadata that is not saved to sidecar and lose any other features such as groups. In the database the RAW files at the new path are given new Image IDs even though their uniqueHash is unchanged - the old Image IDs remain unused. EXPECTED RESULT RAW files re-use same Image IDs and keep all metadata and features, even if it is not saved to sidecar. ADDITIONAL INFORMATION When 'read from sidecar' is used the Image records modification date is collected from the sidecar file, not the RAW itself. If this modification date does not match to the millisecond then the file does not match and a new Image ID is created. Coming from DK5.9 the modification date was stored with second accuracy only, so the first time any RAW is moved it will trigger this bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392607] Crash sometimes when applying Tags to images
https://bugs.kde.org/show_bug.cgi?id=392607 --- Comment #7 from meku --- (In reply to caulier.gilles from comment #6) > ... and use the application as usual. when it crash, go back in the console > and enter "bt". the backtrace will appear in the console. Yes, that is what I did previously, the log I posted shows it returned to (gdb) after crashing. Crashed again just now while tagging, no backtrace in GDB Digikam::ActionThreadBase::run: Action Thread run 1 new jobs Digikam::ActionThreadBase::cancel: Cancel Main Thread Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::ActionThreadBase::cancel: Cancel Main Thread /tmp/.mount_digikacGw5gK/AppRun: line 73: 3207 Segmentation fault (core dumped) digikam $@ [Inferior 1 (process 3163) exited with code 0213] (gdb) bt No stack. (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392607] Crash sometimes when applying Tags to images
https://bugs.kde.org/show_bug.cgi?id=392607 --- Comment #5 from meku --- (In reply to caulier.gilles from comment #3) > You can start the AppImage bundle in GDV using the "debug" option from > command line. > > It's explained here : > > http://www-ftp.lip6.fr/pub/X11/kde-applicationdata/digikam/README > > Gilles Caulier Hi, I'm not sure what else I need to do to get a backtrace. I am starting the appimage with "debug" option and the console outputs: Starting digiKam into GDB... Use 'bt' command on debugger prompt to get a crash backtrace. Use 'q' command to quit debugger session. ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392607] Crash sometimes when applying Tags to images
https://bugs.kde.org/show_bug.cgi?id=392607 --- Comment #2 from meku --- I have had some crashes with 'digikam-6.0.0-beta1-20180831T074549-x86-64.appimage' while saving metadata to images (with and without lazy synchronization). Unfortunately there doesn't appear to be any backtrace? Console: /tmp/.mount_digikaEIFCxQ/AppRun: line 73: 10756 Segmentation fault (core dumped) digikam $@ [Inferior 1 (process 10740) exited with code 0213] (gdb) bt No stack. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393728] Reread metadata from Video uses sidecar only
https://bugs.kde.org/show_bug.cgi?id=393728 --- Comment #2 from meku <kde.b...@meku.org> --- (In reply to Maik Qualmann from comment #1) > DigiKam-6.0.0 cleans up the database on a re-read metadata when all 8 > metadata write options are enabled. As a workaround, you could disable a > write option. Reading from image and sidecar I see not as a good option. We > will come up with something. > > Maik Thanks that workaround appears to work for the purpose of updating the sidecar files. It seems if "Read from sidecar" is enabled then the Metadata viewer still does not show certain metadata such as dimensions or GPS, even when this is in the sidecar. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393728] New: Reread metadata from Video uses sidecar only
https://bugs.kde.org/show_bug.cgi?id=393728 Bug ID: 393728 Summary: Reread metadata from Video uses sidecar only Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Video Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- The metadata available for video files has improved significantly in v6.0.0 however the videos saved in older versions of Digikam do not have this metadata in their sidecar files. The action of "Reread metadata" does not read Video metadata if there is sidecar present and "Read from sidecar" setting is enabled. Disabling sidecars will read in the Video metadata but all captions, tags, GPS, or other user data assigned to the video is lost. Ideally "Reread metadata" could read both the Video and Sidecar metadata and combine together. For example: GPS location info can exist in either the Video file or Sidecar and whichever is present will be imported. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368796] Problem with Exif-tags: ImageDescription and UserComment
https://bugs.kde.org/show_bug.cgi?id=368796 meku <kde.b...@meku.org> changed: What|Removed |Added CC||kde.b...@meku.org --- Comment #16 from meku <kde.b...@meku.org> --- Settings>Metadata>Advanced is a flexible way to control which namespaces are read and updated by the Caption(Comment). I wonder if a solution to this issue is to add settings here for controlling the namespaces for the 'Title' field, then the end user could control the result and is not reliant on changes to the software. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393283] Caption not updating Exif.Image.ImageDescription field
https://bugs.kde.org/show_bug.cgi?id=393283 --- Comment #3 from meku <kde.b...@meku.org> --- (In reply to Maik Qualmann from comment #1) > These conflicts with this Bug 368796 where the users want to make different > entries in these fields. The current state is that > Exif.Image.ImageDescription is only set if it is empty and does not always > overwrite with the contents of Exif.Photo.UserComment. What to do? > > Maik I found the problem was with this implementation in DK6 was with images that already had ImageDescription set, for example any image with a caption saved by DK5 or earlier where the default behaviour was to write the caption to this field. Also if you delete the caption and synchronize it will delete all caption metadata except the ImageDescription, then the next time it rescans the file it will find the old ImageDescription and import it to the Caption again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393283] New: Caption not updating Exif.Image.ImageDescription field
https://bugs.kde.org/show_bug.cgi?id=393283 Bug ID: 393283 Summary: Caption not updating Exif.Image.ImageDescription field Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Exif Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- Updating caption does not update the Exif.Image.ImageDescription field. The other Exif/Iptc/Xmp caption fields are updated. Tested with digikam-6.0.0-git-20180418T014824-x86-64.appimage. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392607] New: Crash sometimes when applying Tags to images
https://bugs.kde.org/show_bug.cgi?id=392607 Bug ID: 392607 Summary: Crash sometimes when applying Tags to images Product: digikam Version: 5.9.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tags-Engine Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- On some occasion when applying Tags to a selection of images the application will crash. It appears the Tags may have been applied to only one of the selected images before crashing. Testing with latest AppImage (currently 5.9.0-release) Backtrace: Thread 1 "digikam" received signal SIGSEGV, Segmentation fault. 0x00372a25d2b8 in QSortFilterProxyModel::parent(QModelIndex const&) const () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 (gdb) bt #0 0x00372a25d2b8 in QSortFilterProxyModel::parent(QModelIndex const&) const () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #1 0x00372a23737e in QAbstractItemModelPrivate::rowsAboutToBeRemoved(QModelIndex const&, int, int) () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #2 0x00372a23a775 in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #3 0x00372a25cbfd in ?? () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #4 0x00372a2617ca in ?? () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #5 0x00372a261623 in ?? () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #6 0x00372a262131 in QSortFilterProxyModel::invalidateFilter() () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #7 0x776fc98d in Digikam::CheckableAlbumFilterModel::setFilterChecked (this=0x125f5e0, filter=) at /b/dktemp/digikam-master/core/libs/models/albumfiltermodel.cpp:455 #8 0x7762897c in Digikam::ImageDescEditTab::slotAssignedTagsToggled (this=0x11d3e90, t=true) at /b/dktemp/digikam-master/core/libs/imageproperties/imagedescedittab.cpp:1409 #9 0x77628b32 in Digikam::ImageDescEditTab::updateTagsView (this=this@entry=0x11d3e90) at /b/dktemp/digikam-master/core/libs/imageproperties/imagedescedittab.cpp:1107 #10 0x7762cc95 in Digikam::ImageDescEditTab::setInfos (this=this@entry=0x11d3e90, infos=...) at /b/dktemp/digikam-master/core/libs/imageproperties/imagedescedittab.cpp:800 #11 0x7762ce26 in Digikam::ImageDescEditTab::setItem (this=0x11d3e90, info=...) at /b/dktemp/digikam-master/core/libs/imageproperties/imagedescedittab.cpp:755 #12 0x7761fd92 in Digikam::ImagePropertiesSideBarDB::slotChangedTab (this=this@entry=0x10155e0, tab=0x11d3e90) at /b/dktemp/digikam-master/core/libs/imageproperties/imagepropertiessidebardb.cpp:294 #13 0x7761d69e in Digikam::ImagePropertiesSideBarDB::itemChanged (this=this@entry=0x10155e0, infos=..., rect=..., img=img@entry=0x0, history=...) at /b/dktemp/digikam-master/core/libs/imageproperties/imagepropertiessidebardb.cpp:199 #14 0x7761d752 in Digikam::ImagePropertiesSideBarDB::itemChanged (this=0x10155e0, infos=...) at /b/dktemp/digikam-master/core/libs/imageproperties/imagepropertiessidebardb.cpp:175 #15 0x775e3544 in Digikam::DigikamView::slotDispatchImageSelected (this=0x9619c0) at /b/dktemp/digikam-master/core/app/views/digikamview.cpp:1420 #16 0x775f99c7 in Digikam::DigikamView::qt_static_metacall (_o=0x9619c0, _c=, _id=, _a=) at /b/dktemp/digikam-master/build/core/app/moc_digikamview.cpp:726 #17 0x00372a2b72c8 in QMetaObject::activate(QObject*, int, int, void**) () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #18 0x00372a2c4b67 in QTimer::timeout(QTimer::QPrivateSignal) () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #19 0x00372a2c4e98 in QTimer::timerEvent(QTimerEvent*) () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #20 0x00372a2b8aab in QObject::event(QEvent*) () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #21 0x7fffef468a0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Widgets.so.5 #22 0x7fffef46ff10 in QApplication::notify(QObject*, QEvent*) () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Widgets.so.5 #23 0x00372a28e4b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #24 0x00372a2dd9ae in QTimerInfoList::activateTimers() () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #25 0x00372a2de151 in ?? () from /tmp/.mount_digikaQF3wE9/usr/lib/libQt5Core.so.5 #26 0x7fffecdd8fb7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7fffecdd91f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7fffecdd927c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
[digikam] [Bug 390162] Digikam-5.9.0 appimage fail to start
https://bugs.kde.org/show_bug.cgi?id=390162 meku <kde.b...@meku.org> changed: What|Removed |Added CC||kde.b...@meku.org --- Comment #5 from meku <kde.b...@meku.org> --- Same error on Ubuntu 17.10 with digikam-5.9.0-20180209T014824-x86-64.appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389619] digikam does not read from sidecars for video/mp4
https://bugs.kde.org/show_bug.cgi?id=389619 meku <kde.b...@meku.org> changed: What|Removed |Added CC||kde.b...@meku.org --- Comment #1 from meku <kde.b...@meku.org> --- Duplicate of Bug 375570 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375346] Many tags disappeared from database
https://bugs.kde.org/show_bug.cgi?id=375346 --- Comment #17 from meku <kde.b...@meku.org> --- I inspected the Tags table before and after the crash and the cause of the loss of tags may be related to corrupt lft/rgt fields (related Bug #383326) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383326] Moving a tag does not update the parent tag correctly
https://bugs.kde.org/show_bug.cgi?id=383326 --- Comment #5 from meku <kde.b...@meku.org> --- How can I repair this corrupt lft/rgt data in the Tags table without clearing the database? Re-importing all the metadata would cause loss of details for all the videos in the database due to Bug #375570 (XMP sidecar files are not read for videos when importing metadata). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375570] XMP sidecar files are not read for videos when importing metadata
https://bugs.kde.org/show_bug.cgi?id=375570 meku <kde.b...@meku.org> changed: What|Removed |Added Version|5.7.0 |5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387171] New: Advanced search by lens by single focal length
https://bugs.kde.org/show_bug.cgi?id=387171 Bug ID: 387171 Summary: Advanced search by lens by single focal length Product: digikam Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Searches-Advanced Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- The advanced search GUI will not allow you to search for a single focal length, it enforces a range value search. For example if I enter a single value, eg. 23, it will search for all images >= 23mm. It will not allow searching for exactly 23mm. The minimum range allowed by the search GUI is 1mm, so you can only search for images between 23 to 24mm. By modifying the XML of a saved search I have confirmed the search back-end does allow searching for a single focal length, eg. exactly 23mm, so this is likely just an issue with the GUI. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 228015] Search by lens
https://bugs.kde.org/show_bug.cgi?id=228015 meku <kde.b...@meku.org> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #6 from meku <kde.b...@meku.org> --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387150] New: crash when syncing metadata from images to database
https://bugs.kde.org/show_bug.cgi?id=387150 Bug ID: 387150 Summary: crash when syncing metadata from images to database Product: digikam Version: 5.8.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Database-Mysql Assignee: digikam-bugs-n...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- Attempting to read metadata to rebuild Tags database using the Maintenance tool, digikam crashes every time. Running: digikam-5.8.0-20171119094605-x86-64.appimage external MySQL 5.7 database Ubuntu 17.10 The console fills with repeats the database messages and then crashes: SqlQuery::prepare: database not open QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-140147803221072' is still in use, all queries will cease to work. QSqlDatabasePrivate::addDatabase: duplicate connection name 'digikamDatabase-140147803221072', old connection removed. QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-140147803221072' is still in use, all queries will cease to work. QSqlDatabasePrivate::addDatabase: duplicate connection name 'digikamDatabase-140147803221072', old connection removed. QSqlQuery::prepare: database not open QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-140147937386496' is still in use, all queries will cease to work. QSqlDatabasePrivate::addDatabase: duplicate connection name 'digikamDatabase-140147937386496', old connection removed. QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-140147937386496' is still in use, all queries will cease to work. QSqlDatabasePrivate::addDatabase: duplicate connection name 'digikamDatabase-140147937386496', old connection removed. (process:26680): GLib-ERROR **: Creating pipes for GWakeup: Too many open files /tmp/.mount_gtXgLF/AppRun: line 73: 26680 Trace/breakpoint trap (core dumped) digikam $@ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375346] Many tags disappeared from database
https://bugs.kde.org/show_bug.cgi?id=375346 --- Comment #15 from meku <kde.b...@meku.org> --- (In reply to Maik Qualmann from comment #14) > SQLite or MySQL? > > Maik external MySQL 5.7 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375346] Many tags disappeared from database
https://bugs.kde.org/show_bug.cgi?id=375346 meku <kde.b...@meku.org> changed: What|Removed |Added CC||kde.b...@meku.org --- Comment #13 from meku <kde.b...@meku.org> --- This bug occurred to me in digikam-5.8.0-20171119094605-x86-64.appimage I removed an unused Tag tree from the Tag Manager and digikam crashed. After re-opening digikam some other unrelated Tag trees were completely missing from the tags list. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375570] XMP sidecar files are not read for videos when importing metadata
https://bugs.kde.org/show_bug.cgi?id=375570 meku <kde.b...@meku.org> changed: What|Removed |Added Version|5.5.0 |5.7.0 --- Comment #2 from meku <kde.b...@meku.org> --- Update for 5.7.0-prerelease: Sidecar appears to be written for all sync actions as expected now. Sidecar is read for videos, it loads some metadata such as Ratings but fails to load other metadata such as the Captions or Tags. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383326] Moving a tag does not update the parent tag correctly
https://bugs.kde.org/show_bug.cgi?id=383326 meku <kde.b...@meku.org> changed: What|Removed |Added CC||kde.b...@meku.org --- Comment #2 from meku <kde.b...@meku.org> --- Looking at the trace there are two consecutive MySQL errors: " digikam.dbengine: Prepare failed! digikam.dbengine: Failure executing query: "LOCK TABLE Tags WRITE;" Error messages: "QMYSQL3: Unable to prepare statement" "This command is not supported in the prepared statement protocol yet" 1295 2 Bound values: () digikam.dbengine: Prepare failed! digikam.dbengine: Failure executing query: "UNLOCK TABLES;" Error messages: "QMYSQL3: Unable to prepare statement" "This command is not supported in the prepared statement protocol yet" 1295 2 Bound values: () digikam.general: Delete Shortcut assigned to tag 1272 " -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375570] XMP sidecar files are not read for videos when importing metadata
https://bugs.kde.org/show_bug.cgi?id=375570 --- Comment #1 from meku <kde.b...@meku.org> --- Additional detail from my testing, when is XMP sidecar file used: - YES when modifying the tags or metadata of a video. - NO when selecting "Write metadata to image" - NO when selecting "Reread metadata from image" - NO when using Database maintenance to sync to/from files. This bug only happens for video files, the handling of XMP sidecar for RAW files appears to be correct. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 375833] Flickr export converts all images to JPEG
https://bugs.kde.org/show_bug.cgi?id=375833 --- Comment #2 from meku <kde.b...@meku.org> --- Thanks, that new option is there and I just hadn't noticed it. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 375833] New: Flickr export converts all images to JPEG
https://bugs.kde.org/show_bug.cgi?id=375833 Bug ID: 375833 Summary: Flickr export converts all images to JPEG Product: kipiplugins Version: 5.5.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Flickr Assignee: kde-imag...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- The Flickr exporter converts all images to JPEG before uploading even when [Resize photos before uploading] is unchecked. For every export the Digikam console reports 'resized and saved to a temp file'. This is a problem for Animated GIF which is uploaded as a static JPG. For JPG this is also not ideal because the exported file is no longer bitwise identical to the source file, the checksums and filesizes of the uploaded files will not match the source files. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375600] New: Time Adjust Batch Queue depends on Global Metadata Setting for timestamp
https://bugs.kde.org/show_bug.cgi?id=375600 Bug ID: 375600 Summary: Time Adjust Batch Queue depends on Global Metadata Setting for timestamp Product: digikam Version: 5.5.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: BatchQueueManager-Tool-TimeAdjust Assignee: digikam-de...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- Using Time Adjust tool in Batch Queue Editor, the option to update [File last modified] has no effect if the global setting for [Metadata > Update file timestamp when files are modified] is not checked. I would expect this explicit option in the Time Adjust tool to override the global setting. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375570] XMP sidecar files are not read for videos when importing metadata
https://bugs.kde.org/show_bug.cgi?id=375570 meku <kde.b...@meku.org> changed: What|Removed |Added Platform|Other |Appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375570] New: XMP sidecar files are not read for videos when importing metadata
https://bugs.kde.org/show_bug.cgi?id=375570 Bug ID: 375570 Summary: XMP sidecar files are not read for videos when importing metadata Product: digikam Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata Assignee: digikam-de...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- In settings: - Write information to Metadata is enabled. - Read & Write to sidecar files is enabled. Preparation: Write Tags to Videos using Digikam and XMP sidecar files are written for videos. Bug: Reread metadata does not load from XMP sidecar files for Videos. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374409] New: Export to Flickr ignores EXIF Orientation
https://bugs.kde.org/show_bug.cgi?id=374409 Bug ID: 374409 Summary: Export to Flickr ignores EXIF Orientation Product: kipiplugins Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Flickr Assignee: kde-imag...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- Export to Flickr appears to ignore the EXIF Orientation such that any portrait images are displayed in landscape mode. If the same images are uploaded using Flickr's web page then they are automatically rotated using EXIF detection. Tested using Digikam 5.4.0 appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373954] New: Tags are not written to images in Iptc.Application2.Keywords
https://bugs.kde.org/show_bug.cgi?id=373954 Bug ID: 373954 Summary: Tags are not written to images in Iptc.Application2.Keywords Product: digikam Version: 5.3.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Engine Assignee: digikam-de...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- How to reproduce: Add tag and write metadata to image. View Metadata shows Iptc Keywords are not updated. Other Iptc.Application2 fields are successfully written such as Caption, Program, ProgramVersion etc. Settings > Metadata > Advanced > Tags Write Options: shows Iptc.Application2.Keywords is ticked by default. This is a problem when there are old Keywords saved in images and they are not updated by Digikam as expected. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372628] Crash at startup connecting to MySQL 5.7 database
https://bugs.kde.org/show_bug.cgi?id=372628 --- Comment #2 from meku <kde.b...@meku.org> --- This crash occurs when using the packages from philip5 PPA. I tested the AppImage bundles for Digikam 5.3.0 & 5.4.0 and both work with the database. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372628] Crash at startup connecting to MySQL 5.7 database
https://bugs.kde.org/show_bug.cgi?id=372628 meku <kde.b...@meku.org> changed: What|Removed |Added Component|general |Database-Mysql -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372628] Crash at startup connecting to MySQL 5.7 database
https://bugs.kde.org/show_bug.cgi?id=372628 meku <kde.b...@meku.org> changed: What|Removed |Added Component|general |general Product|kde |digikam Version|unspecified |5.3.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 372628] New: Crash at startup connecting to MySQL 5.7 database
https://bugs.kde.org/show_bug.cgi?id=372628 Bug ID: 372628 Summary: Crash at startup connecting to MySQL 5.7 database Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kde.b...@meku.org Target Milestone: --- Application: digikam5 (5.3.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.8.0-27-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: Digikam5 is configured to use an external database server. It was working with MySQL 5.6 but since upgrading to MySQL 5.7.15 this crash always occurs when Digikam starts. $ digikam5 Digikam.general: AlbumWatch use QFileSystemWatcher digikam.general: Database Parameters: Type: "QMYSQL" DB Core Name: "digikam5_core" DB Thumbs Name: "digikam5_thumb" DB Face Name: "digikam5_face" Connect Options: "" Host Name:"hostname" Host port:3306 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "digikamuser" Password: "" digikam.dbengine: Loading SQL code from config file "/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = digikam5 path = /usr/bin pid = 523 KCrash: Arguments: /usr/bin/digikam5 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 12 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 20 and type 'Exception', disabling... QSocketNotifier: Invalid socket 15 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7fe45969ab40 (LWP 523))] Thread 4 (Thread 0x7fe455226700 (LWP 527)): [KCrash Handler] #6 __GI___pthread_mutex_lock (mutex=0x20) at ../nptl/pthread_mutex_lock.c:67 #7 0x7fe447a76099 in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #8 0x7fe447a4bbf0 in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #9 0x7fe447a225cc in mysql_real_connect () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #10 0x7fe458b8495a in QMYSQLDriver::open (this=0x7fe44c016790, db=..., user=..., password=..., host=..., port=3306, connOpts=...) at ../../../sql/drivers/mysql/qsql_mysql.cpp:1340 #11 0x7fe48741f420 in QSqlDatabase::open (this=this@entry=0x7fe44c002db0) at kernel/qsqldatabase.cpp:835 #12 0x7fe485a9cda8 in Digikam::BdEngineBackendPrivate::databaseForThread (this=this@entry=0x5626f60e6160) at ./core/libs/database/engine/dbenginebackend.cpp:170 #13 0x7fe485a9d530 in Digikam::BdEngineBackend::open (this=0x5626f60e3e00, parameters=...) at ./core/libs/database/engine/dbenginebackend.cpp:763 #14 0x7fe483b05110 in Digikam::CoreDbAccess::checkReadyForUse (observer=observer@entry=0x7fe4872579b0 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder+16>) at ./core/libs/database/coredb/coredbaccess.cpp:295 #15 0x7fe48695885b in Digikam::ScanController::run (this=0x7fe4872579a0 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder>) at ./core/libs/database/utils/scancontroller.cpp:686 #16 0x7fe483ecdc68 in QThreadPrivate::start (arg=0x7fe4872579a0 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder>) at thread/qthread_unix.cpp:341 #17 0x7fe48031d70a in start_thread (arg=0x7fe455226700) at pthread_create.c:333 #18 0x7fe4831f30af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7fe455a27700 (LWP 526)): #0 0x7fe47b606009 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe47b5c0121 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe47b5c0948 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe47b5c0aec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe4840fb4ab in QEventDispatcherGlib::processEvents (this=0x7fe4480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7fe4840a30fa in QEventLoop::exec (this=this@entry=0x7fe455a26a50, flags=..., flags@entry=...) at
