[marble] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]
https://bugs.kde.org/show_bug.cgi?id=368167 --- Comment #8 from Jens B. Benecke --- It's in digikamrc, either in $HOME/.kde/config or in .config/digikam (I think). -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]
https://bugs.kde.org/show_bug.cgi?id=368167 --- Comment #6 from Jens B. Benecke --- Marble with OSM map works perfectly. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]
https://bugs.kde.org/show_bug.cgi?id=368167 --- Comment #2 from Jens B. Benecke --- IIRC it was Marble with OSM. I don't remember ... is there any way to track it (eg. by activating more console debug output)? Which Marble standalone app should I try out? I still have the old config so I can try more debugging ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]
https://bugs.kde.org/show_bug.cgi?id=368167 --- Comment #3 from Jens B. Benecke --- IIRC it was Marble with OSM. I don't remember ... is there any way to track it (eg. by activating more console debug output)? Which Marble standalone app should I try out? I still have the old config so I can try more debugging ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368167] New: crash on startup in geoiface QMutex::lock [cause: digikamrc]
https://bugs.kde.org/show_bug.cgi?id=368167 Bug ID: 368167 Summary: crash on startup in geoiface QMutex::lock [cause: digikamrc] Product: digikam Version: 5.1.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Geolocation-Editor Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Digikam crashes right on startup after the console messages as follows: (... lots of kipi.plugins loading ...) kipi.library: Loaded plugin "Smug" kipi.plugins: Reading data from kipirc file.. Could not resolve property : XMLID_8_ Could not resolve property : XMLID_12_ Could not resolve property : XMLID_13_ Could not resolve property : XMLID_14_ Could not resolve property : XMLID_8_ Could not resolve property : XMLID_12_ Could not resolve property : XMLID_13_ Could not resolve property : XMLID_14_ Could not resolve property : XMLID_8_ Could not resolve property : XMLID_12_ Could not resolve property : XMLID_13_ Could not resolve property : XMLID_14_ digikam.geoiface: Speicherzugriffsfehler (Speicherabzug geschrieben) This happens exactly when in digikamrc, the following section is present: [Digikam Right Sidebar] Removing this section allows Digikam to start again. After closing it, the section changes as follows: [Digikam Right Sidebar] -ActiveTab=3 +ActiveTab=0 DigikamProperties Expanded=true FileProperties Expanded=true ItemProperties Expanded=true -Minimized=false +Minimized=true PhotographProperties Expanded=true -RestoreSize=-1 +RestoreSize=209 VideoProperties Expanded=true and subsequent starts are successful again. This file was written by Digikam upon exit, I did not modify it by myself. Partial backtrace: Thread 1 (Thread 0x7f3822ac7b80 (LWP 7551)): #0 0x7f384f7d81d1 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f384a64c397 in ?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23 #2 0x7f384a64cd30 in ?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23 #3 0x7f384f805ea1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 StacktraceTop: QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23 ?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23 QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366286] feature request: improved reverse geolocation
https://bugs.kde.org/show_bug.cgi?id=366286 Jens B. Benecke changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #1 from Jens B. Benecke --- See also #351987. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored
https://bugs.kde.org/show_bug.cgi?id=364258 --- Comment #14 from Jens B. Benecke --- Also which bug report is about these crashes? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored
https://bugs.kde.org/show_bug.cgi?id=364258 --- Comment #13 from Jens B. Benecke --- Backups are a must anyway. (IMHO: Just install deja-dup and setup some remote storage (a NAS or a cloud service) and stop thinking about it.) Specifically, did you narrow down your search about 4.x settings digikam 5 so that I can help doing some bisect testing? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 349924] Videos (mp4, mov, avi) do not play under OS X Yosemite when using Digikam.
https://bugs.kde.org/show_bug.cgi?id=349924 --- Comment #27 from Jens B. Benecke --- Caulier, sorry to reply so late. The link above redirects to Perian, which is a software that extended Quicktime 7 to work with other codecs. But Quicktime 7 has long ago been retired and QuickTime X (used in macOS >= 10.8 I think) is no longer extensible like that. So the link doesn't really help, sorry. If Digikam5 relies on Qt5-Multimedia and Qt5/Mac relies on Quicktime, Digikam might never be able to show or play other codecs like AVI files ... I just tested it anyway: Viewing mp4 and MJPEG-AVI files (from a digital camera) works fine on my OS X 10.11.5 machine (no thumbnails are created though, just as the README said). Great work, thank you! For the thumbnails I get this error on the console: digikam.metaengine: Cannot load metadata from file (Error # 11 : /Users/Jens/Pictures/20141106_172159.mp4: The file contains data of an unknown image type digikam.general: Trying to load Embedded preview with libraw digikam.rawengine: Failed to load embedded RAW preview digikam.general: Trying to load half preview with libraw digikam.general: Trying to load Embedded preview with Exiv2 digikam.metaengine: Cannot load metadata using Exiv2 (Error # 11 : /Users/Jens/Pictures/20141106_172159.mp4: The file contains data of an unknown image type digikam.dimg: "/Users/Jens/Pictures/20141106_172159.mp4" : QIMAGE file identified digikam.dimg.qimage: Can not load " "/Users/Jens/Pictures/20141106_172159.mp4" " using DImg::QImageLoader! digikam.general: mimetype = "" ext = "MP4" digikam.general: Cannot create thumbnail for "/Users/Jens/Pictures/20141106_172159.mp4" digikam.general: Thumbnail is null for "/Users/Jens/Pictures/20141106_172159.mp4" digikam.general: Request to get thumbnail for "/Users/Jens/Pictures/20141106_172159.mp4" digikam.general: Video monitoring is not available. digikam.general: Failed to extract video thumbnail for "/Users/Jens/Pictures/20141106_172159.mp4" Also, the above digikam package crashed on quit on my machine. I'll try again and open another bug report for the crash if it is repeatable. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 363913] Improve export menu structure
https://bugs.kde.org/show_bug.cgi?id=363913 Jens B. Benecke changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED |--- --- Comment #2 from Jens B. Benecke --- Hm. I seem to have a different Digikam5 (beta7) than you. I see less export options as in 4.14, but * it is still a flat menu without (obvious) sorting or grouping of services * exporting (optionally compressed & converted) images to a local folder is still not there (right? Or did I miss something?) Also, I would remove the "Export to" string from all exports, just list the name like I did above. This is shorter and easier to read. I can do this for you (just give me a link to the strings and the translations) if you like. If these things will be "finalized later" then please keep the bug open for reference until the commit. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364258] Upgrade to 5.0 (beta6) : tags and location data of photos are lost
https://bugs.kde.org/show_bug.cgi?id=364258 --- Comment #6 from Jens B. Benecke --- > If you copy this file at this place all will start as expected. Do you expect a normal user (= non-geek, non-programmer) to know that? Then this is a usability issue, not a technical one. But an important one. Or is Digikam not meant to be used by non-geeks? > In all cases, the migration option is not the right way to process. How should a user know? He can't. So prevent the migration from being abused in this case. Users should not be able to perform tasks that destroy data, otherwise they lose their trust in the application. > But, starting with a new fresh DK setup and configure the collections and the > place where the database is stored will normally not touch the DB content and > all will be available as with 4.x release. OK, but - again - (how) do you expect a normal user (= non-geek, non-programmer) to know that? From a usability perspective, Digikam5 should proactively offer to import all Digikam4 settings, collections and so on - no matter where they were saved previously. Nobody wants to research how to do this manually, even if it is possible. Please don't get me wrong, I like Digikam a lot and I want it to be successful. This is why these things are so important to me. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364258] Upgrade to 5.0 (beta6) : tags and location data of photos are lost
https://bugs.kde.org/show_bug.cgi?id=364258 --- Comment #4 from Jens B. Benecke --- Let me explain. Digikam 5 (beta6), when started first, did not recognize my existing albums and collections from Digikam 4.14 (on Ubuntu Linux) and just showed me a welcome and setup screen. So I logically assumed there must be a migration procedure. (This I would consider a bug - if there are previous existing collections, a new version of Digikam should just open them or offer to import them.) I found the migration option and selected my digikam4.db (the target was already preselected) and started the migration. This destroyed the digikam4.db tables as described below so subsequent starts of Digikam 4.14 wouldn't show tags etc. any more. Starting the migration might have been my mistake but a user friendly application should prevent users from doing something stupid (like starting a migration when it isn't required or possible) so I consider this a bug too. The solution is simple: upon start, just load the digikam4 config (if available) and - if required - copy it to a digikam5 config. And when a user starts the Migration task from the maintenance menu and selects database files or formats which cannot be migrated, show an appropriate error message and refuse the migration. Do you agree? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364258] Upgrade to 5.0 (beta6) : tags and location data of photos are lost
https://bugs.kde.org/show_bug.cgi?id=364258 --- Comment #2 from Jens B. Benecke --- "My Computer Settings" - a.k.a. Digikam 5 - permit overwriting digikam4.db with the exact same file (digikam4.db) in the migration dialog. I think this is the problem. Can you please verify and if so, add a check that the migration database files must be different. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364258] New: Upgrade to 5.0 (beta6) and "Migrate Database" destroys tags and location data of ALL photos
https://bugs.kde.org/show_bug.cgi?id=364258 Bug ID: 364258 Summary: Upgrade to 5.0 (beta6) and "Migrate Database" destroys tags and location data of ALL photos Product: digikam Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: Database-Migration Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de So I upgraded to Ubuntu 16.04 to be able to test Digikam 5beta6. After the upgrade, I started Digikam 5 and was a little surprised that it did not offer to import / migrate / update the Digikam 4 database I already had, but behaved like a new installation. (Is this intentional during the beta phase so that production (Digikam 4.14) and testing (Digikam 5) can be kept separate?) Since digikam did not detect my Digikam4 library I went to Settings > Database Migration and clicked "Migrate" with the default settings (SQlite format and the same path on both sides, after all, Digikam 5 did not find my library, so it probably uses another file name!) But it didn't work, even afterwards Digikam did not find my library. What's more, after closing and reopening Digikam 4.14, it did not display any photos - and all my locations, tags, album comments and so on were gone!!! It seems they were deleted from digikam4.db; the "Tags" table was empty, so was the "Settings" table and some others. IMHO there should be no way of doing this. Digikam should warn before overwriting data or modifying it so that an old version cannot read it any more. (Was this even the right procedure to get Digikam 5 set up?) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364153] New: Crash during geotagging (repetable 100%)
https://bugs.kde.org/show_bug.cgi?id=364153 Bug ID: 364153 Summary: Crash during geotagging (repetable 100%) Product: digikam Version: 4.14.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Geolocation-Editor Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Application: digikam (4.14.0) KDE Platform Version: 4.13.3 Qt Version: 4.8.6 Operating System: Linux 3.19.0-59-generic x86_64 Distribution: Ubuntu 14.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: geotagging images and browsing around in the MArble (Openstreetmap) map. It seems Digikam always crashes when browsing a certain location OR trying to tag a certain image (I can't tell which). The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), 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 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f539535cac0 (LWP 6833))] Thread 15 (Thread 0x7f536a2f1700 (LWP 6837)): #0 0x7f538df13fdd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f536fdfe248 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x7f538ab41184 in start_thread (arg=0x7f536a2f1700) at pthread_create.c:312 #3 0x7f538df2137d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 14 (Thread 0x7f536621b700 (LWP 6838)): #0 0x7f538df13fdd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f5385b3efe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5385b3f0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f53662231ad in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #4 0x7f5385b63f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f538ab41184 in start_thread (arg=0x7f536621b700) at pthread_create.c:312 #6 0x7f538df2137d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 13 (Thread 0x7f5365a1a700 (LWP 6839)): #0 0x7f538df13fdd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f5385b3efe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5385b3f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f537160e336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f5385b63f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f538ab41184 in start_thread (arg=0x7f5365a1a700) at pthread_create.c:312 #6 0x7f538df2137d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 12 (Thread 0x7f535e195700 (LWP 6840)): #0 0x7f538df13fdd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f5385b3efe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5385b3f0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5385b3f129 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5385b63f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f538ab41184 in start_thread (arg=0x7f535e195700) at pthread_create.c:312 #6 0x7f538df2137d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 11 (Thread 0x7f53494ce700 (LWP 6843)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f538e9fc816 in wait (time=18446744073709551615, this=0x2d50ec0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x2d50dd0, mutex=mutex@entry=0x2d50dc8, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x005db06e in Digikam::ScanController::run (this=0x2d50b40) at /build/digikam-Oa9XB6/digikam-4.14.0/core/app/database/scancontroller.cpp:725 #4 0x7f538e9fc32f in QThreadPrivate::start (arg=0x2d50b40) at thread/qthread_unix.cpp:349 #5 0x7f538ab41184 in start_thread (arg=0x7f53494ce700) at pthread_create.c:312 #6 0x7f538df2137d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 10 (Thread 0x7f5348ccd700 (LWP 6844)): #0 0x7f538df13fdd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f5385b3efe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5385b3f0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f538eb2b7be in QEventDispatcherGlib::processEvents (this=0x7f533c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7f538eafd0af in QEventLoop::processEvents (this=this@entry=0x7f5348cccae0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f538eafd3a5 in QEventLoop::exec (this=this@entry=0x7f5348cccae0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f538e9f9c5f in
[digikam] [Bug 364153] Crash during geotagging (repeatable 100%)
https://bugs.kde.org/show_bug.cgi?id=364153 Jens B. Benecke changed: What|Removed |Added Summary|Crash during geotagging |Crash during geotagging |(repetable 100%)|(repeatable 100%) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363913] Improve export menu structure and add "Export to folder"
https://bugs.kde.org/show_bug.cgi?id=363913 Jens B. Benecke changed: What|Removed |Added Summary|Export menu is a mess (and |Improve export menu |is missing useful options) |structure and add "Export ||to folder" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363913] Improve export menu structure and add "Export to folder" [PATCH]
https://bugs.kde.org/show_bug.cgi?id=363913 Jens B. Benecke changed: What|Removed |Added Summary|Improve export menu |Improve export menu |structure and add "Export |structure and add "Export |to folder" |to folder" [PATCH] -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363913] Improve export menu structure and add "Export to folder"
https://bugs.kde.org/show_bug.cgi?id=363913 Jens B. Benecke changed: What|Removed |Added Summary|Improve export menu |Improve export menu |structure and add "Export |structure and add "Export |to folder" [PATCH] |to folder" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363913] New: Export menu is a mess (and is missing useful options)
https://bugs.kde.org/show_bug.cgi?id=363913 Bug ID: 363913 Summary: Export menu is a mess (and is missing useful options) Product: digikam Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Export Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de The Export menu is a mess (IMHO). It is littered with options that are probably only useful for a very small group of people (e.g. "Export to Debian Screenshots", "Export to Yandex.RU") and mixes web service with local folders and scripts (e.g. "export to HTML"). Plus, it isn't sorted (by any obvious criteria) so you can't quickly find the options you are looking for. Also a simple "Export to folder ..." option with resize / convert possibility doesn't even exist. (Right?) Suggestion: Create a hierarchy of menu options with (alphabetically sorted) entries like Export Folder... (this export option will have to be created) HTML ... KML ... EMail ... (here I would like an option to just recompress JPEG, without resizing to <=1600px) Flash ... Local network DLNA Remote computer ... Devices iPod ... Commercial web services 23 Dropbox Facebook Flickr Google Drive Google Photos / Picasaweb Imageshack imgur Piwigo Rajce.net Shwup Smugmug VKontakte Yandex.Fotki Zmr Other web services Debian Screenshots Gallery jAlbum MediaWiki Instant messaging contact The "Export to Folder" option does the same as the "EMail ..." option (regarding export options) except that the images are actually kept in the folder instead of being only copied to a temporary folder. Also, I would like to have an "Export to WebDAV" option (for Owncloud). :-) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363522] New: import: use UUID from XMP sidecar / metadata instead of creating another one
https://bugs.kde.org/show_bug.cgi?id=363522 Bug ID: 363522 Summary: import: use UUID from XMP sidecar / metadata instead of creating another one Product: digikam Version: 4.14.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de When I import images that have existing XMP sidecar files Digikam reads those files and uses the metadata in them. But it creates its own UUID for the database although there already is one supplied in the XMP sidecar, as This is important if you reimport files again so they are uniquely identifiable even from an external script. The UUID is the only *safe* way of uniquely identifying an image after the import (after all, it might have been renamed, moved, etc). I suppose the UUID really is just a unique random string of any length (right?). Duplicate UUIDs, if present, should be handled just like duplicate files, by prompting the user to replace the file or create a new UUID when first reading the image file's metadata. But in reality this should never happen - it is just important that Digikam doesn't crash with a duplicate UUID. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #49 from Jens B. Benecke --- Right now, I do not have the chance to compile KDE or Digikam, but I will happily review and comment any screenshots. Sorry ... maybe in two weeks time. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #40 from Jens B. Benecke --- Some comments from my side since I opened the original bug: I like the progress and I am really thankful that there is so much effort invested in this feature! I think the size of the additional border should scale with the size of the thumbnail and not be a fixed amount of pixels. In the screenshots mentioned above the size of the group border is (IMHO) too small and not really well visible. Look at iPhoto's borders (e.g. https://www.apple.com/de/mac/iphoto/, scroll down to the screenshot titled "Share.") for example. Also, the background for an expanded group should have a little less contrast, the current dark yellow (is this fixed, configurable or depending on the theme?) is a little too drastic for my taste. But apart from that, very good work! Thank you to all involved! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #27 from Jens B. Benecke --- Hmmm. I still like iPhoto's visualization of an image "stack" better: https://www.apple.com/de/mac/iphoto/ (scroll down to the screenshot labeled "Share.") It looks less technical, it is easy to spot among many images, and there is nothing to translate. Of course a number in the corner indicating the number of images in addition (!) is also good. :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 362108] crash when moving images to newly created album
https://bugs.kde.org/show_bug.cgi?id=362108 --- Comment #2 from Jens B. Benecke --- I have all debug symbols installed but still do not see more than one single line "segmentation fault (core dumped)" when DrKonqi shows me the crash details. I don't know why. Maybe Ubuntu's Apport is getting in the way? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #13 from Jens B. Benecke --- This looks great! Thank you for implementing! One little request .. can you make the grouped border a little darker? I think it would be better visible. Or does it depend on the KDE theme? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 362108] New: crash when moving images to newly created album
https://bugs.kde.org/show_bug.cgi?id=362108 Bug ID: 362108 Summary: crash when moving images to newly created album Product: digikam Version: 4.14.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Thumbnails Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Digikam crashes when moving images to newly created album in one step. Reproducible: Always Steps to Reproduce: 1. select images 2. right click "move to album..." 3. click "create album" 4. enter name, category and click on "earliest" date of images for album date 5. click ok 6. click ok Actual Results: Crash. (segfault) Expected Results: Album should be created (it is) and images should be moved (they are not). Happens every time. I tried three times with different albums. My album was called "2016.04.02f bla bla bla" but it does not seem to depend on the name. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361829] rotated mp4 videos ("Orientation" flag) are not played back in the correct rotation angle
https://bugs.kde.org/show_bug.cgi?id=361829 --- Comment #2 from Jens B. Benecke --- Thank you! How can I check whether it already works in 5.0beta5, what packages do I need to install for video playback and thumbs to work? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361829] New: rotated mp4 videos ("Orientation" flag) are not played back in the correct rotation angle
https://bugs.kde.org/show_bug.cgi?id=361829
Bug ID: 361829
Summary: rotated mp4 videos ("Orientation" flag) are not played
back in the correct rotation angle
Product: digikam
Version: 4.14.0
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Preview
Assignee: digikam-de...@kde.org
Reporter: jens-bugs.kde@spamfreemail.de
I have a lot of videos shot on iPhones or iPads in portrait mode. These are MOV
(or MP4) files which have an "Orientation" metadata flag set. In iPhoto they
are displayed correctly rotated, but in Digikam 4.14 they are not. (I can't
test Digikam 5 because even on my Virtualbox Kubuntu 15.10, Digikam 5beta5
packages by philip5 flatly refuse to preview or show videos at all right now.)
I would wish for Digikam's player (phonon, gstreamer, ...) to correctly respect
the "Orientation" flag in MOV and MP4 files (I don't know about other video
formats) and to display the videos correctly.
If required, please reassign this bug to the correct project if Digikam itself
cannot do anything about this.
Thank you!
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #5 from Jens B. Benecke --- I have looked into the source but I'm not good enough in C++ to do the actual programming. Sorry ... What I did in GIMP was to copy the current thumbnail border and clone it rotated around the image center three times -10°, 5°, and 10°. Then combine the resulting images. Of course, the perfect solution ;) would be to display the actual thumbnails of the "other" grouped images so their borders are a little visible (much brighter than default so the front image is still prominent) - but I don't think this is really necessary for a start. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361467] New: indicate (shade?) drop target when copying or moving images
https://bugs.kde.org/show_bug.cgi?id=361467 Bug ID: 361467 Summary: indicate (shade?) drop target when copying or moving images Product: digikam Version: 4.14.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Albums View Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de A small usability issue: When dropping a list of images onto an album / tag / ... and using small album icons (16x16), it is not often easy to see which the drop target is - depending on the mouse cursor and icon size. During a drop operation (while the mouse button is still pressed) the drop target (e.g. album name) currently below the mouse cursor should be shaded (or otherwise highlighted). Is this maybe possible for 5.x? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361137] New: Inconsistent timestamp display (only for MP4 files?) in Album View after adjusting date/time
https://bugs.kde.org/show_bug.cgi?id=361137 Bug ID: 361137 Summary: Inconsistent timestamp display (only for MP4 files?) in Album View after adjusting date/time Product: digikam Version: 4.14.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Albums View Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de I have a MP4 file (created using HandBrakeCLI) in one of my albums that I created before remembering to set daylight saving time on my camera. So I used "Image > Adjust date and time" to take one hour off the timestamp of the video file. I chose to modify XMP, file timestamp and Digikam database timestamp since videos have no EXIF information. (Right?) Result: "Properties" tab shows the new timestamp value. "Metadata" tab shows the old value. Value below thumbnail shows the old value. Only after doing the same again and checking all fields (EXIF dates as well) was the timestamp and sort order in Albums View correctly updated. This seems inconsistent to me. All tabs should show the same value. Or there should be a hint which value is used for the Album view. Strangely, for other MP4 video files (several at once) this was not necessary, there it worked without having to selecting to modify the EXIF dates. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #3 from Jens B. Benecke --- Thank you! :-) I'd be happy to create a border / backdrop for grouped images, I'll be happy to do it - just tell me what formats you need (probably SVG to zoom it, or are you going to draw it in software?). IMHO: The colored background for expanded groups should be very slight and adhere to the theme that is currently set in KDE. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #1 from Jens B. Benecke --- Created attachment 98114 --> https://bugs.kde.org/attachment.cgi?id=98114&action=edit mockup to better recognize groups of images -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] New: Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 Bug ID: 361047 Summary: Wishlist: make grouped images more prominently visible [MOCKUP] Product: digikam Version: 4.14.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Hello, I have three requests regarding grouped images. Maybe they can make it into 5.0. 1. Display a different kind of border around grouped images so it is at once visible that there are multiple images "behind" the displayed one. Also, when opened, maybe the group can be visualized by using a different background color. See attachment. 2. In a set of grouped images, make it possible to choose which image is the visible thumbnail, i.e. "at the top". 3. When a group is closed, and the front image's properties are modified, apply the changes to all grouped images *unless* this would overwrite previous settings (perhaps with a confirmation dialog). 4. What do you think? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 286529] Face tag rectangles not adjusted after to apply aspect ratio crop tool
https://bugs.kde.org/show_bug.cgi?id=286529 Jens B. Benecke changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #8 from Jens B. Benecke --- I am witnessing a similar issue on Linux (Ubuntu LTS 14.04) and Digikam 4.14 (from PPA). A RAW (RW2 Panasonic) file which has been rotated into portrait mode during import has two face rectangles. When I rotate this image using the buttons in the previewer, the face rectangles are (once) moved to a different location on the image - and after this first incorrect displacement they stick to the location on the image even with further rotations. Can you please double check whether this issue exists in 5.x? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358081] New: Various small issues creating, editing and deleting Tags
https://bugs.kde.org/show_bug.cgi?id=358081 Bug ID: 358081 Summary: Various small issues creating, editing and deleting Tags Product: digikam Version: 4.14.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tags Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de 1. When I create a tag, I can set an icon for this tag. But when I edit a tag in the right sidebar panel, I cannot change that icon - selecting one works but the new icon is not saved upon clicking "save" and resets when I select another tag. 2. When I delete an icon using the context menu, the confirmation dialog says "Delete tag ''?" (in German "Stichwort '' löschen?" ie. an empty string instead of the tag name. When I use the "-" toolbar icon to delete, the tag name is correctly inserted. Wishlist: 3. In the tag editor sidebar, F2 (if one tag is selected) should open the editor dialog and focus the tag name field, and "ENTER" in any text entry field (eg. name) should save and close the editor sidebar and focus the tag list so that I can select the next tag to be edited. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 295334] Add some way to tag a face result as "ignore this one" in database for future scans
https://bugs.kde.org/show_bug.cgi?id=295334 Jens B. Benecke changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #6 from Jens B. Benecke --- +1 from my side too. I want to be able to ignore (for all future face scans) - faces that I do not want to be recognized (eg. complete strangers which only appear on one photo anyway) - stuff that is not a face or animal faces that are accidentally recognized. I also would like to be able to search pictures that have these flags set (e.g. "images with ignored faces"). Thank you! -- You are receiving this mail because: You are watching all bug changes.
