[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 --- Comment #4 from Jens Ramke --- (In reply to caulier.gilles from comment #2) > Note : the AppImage bundle is compiled with QtWebEngine. Can you reproduce > this problem ? Cannot reproduce with AppImage bundle. It starts normally. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 --- Comment #3 from Jens Ramke --- (In reply to Maik Qualmann from comment #1) > It crashes in QWebEngine. Your digiKam version is compiled with QWebEngine > support instead of QWebKit. We currently recommend QWebKit. For QWebEngine > you need a working and stable support of OpenGL. I also use QWebEngine in my > developer version. Which graphics card and drivers do you use? > > Maik GPU: NVIDIA GeForce RTX 2080 GPU driver: nvidia-dkms 435.21-4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] New: Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 Bug ID: 411891 Summary: Digikam crashes on startup Product: digikam Version: 6.3.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: jens.ra...@gmail.com Target Milestone: --- Application: digikam (6.3.0) Qt Version: 5.13.1 Frameworks Version: 5.61.0 Operating System: Linux 5.2.14-zen2-1-zen x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Fresh reboot, started Digikam. It opened on a secondary screen and crashed as the splash screen was visible. The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdadb280800 (LWP 1540))] Thread 21 (Thread 0x7fdab849d700 (LWP 1583)): #0 0x7fdb617ded16 in do_futex_wait.constprop () at /usr/lib/libpthread.so.0 #1 0x7fdb617dee18 in __new_sem_wait_slow.constprop.0 () at /usr/lib/libpthread.so.0 #2 0x7fdaec73c45a in () at /usr/lib/libopenal.so.1 #3 0x7fdaec6ea63f in () at /usr/lib/libopenal.so.1 #4 0x7fdaec73bfa8 in () at /usr/lib/libopenal.so.1 #5 0x7fdb617d657f in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdb618ef0e3 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7fdab869e700 (LWP 1582)): #0 0x7fdb5a05e0e3 in () at /usr/lib/libm.so.6 #1 0x7fdaec70860d in () at /usr/lib/libopenal.so.1 #2 0x7fdaec6ffb1d in () at /usr/lib/libopenal.so.1 #3 0x7fdaec7353c2 in () at /usr/lib/libopenal.so.1 #4 0x7fdaec73bfa8 in () at /usr/lib/libopenal.so.1 #5 0x7fdb617d657f in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdb618ef0e3 in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7fdaba7e2700 (LWP 1581)): #0 0x7fdb617d880b in __pthread_mutex_lock_full () at /usr/lib/libpthread.so.0 #1 0x7fdadc122dff in pa_mutex_lock () at /usr/lib/pulseaudio/libpulsecommon-12.99.so #2 0x7fdaec684c20 in () at /usr/lib/libpulse.so.0 #3 0x7fdaec692059 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #4 0x7fdaec69c301 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #5 0x7fdaec69c3b1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #6 0x7fdaec68c61e in () at /usr/lib/libpulse.so.0 #7 0x7fdadc112d1c in () at /usr/lib/pulseaudio/libpulsecommon-12.99.so #8 0x7fdb617d657f in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fdb618ef0e3 in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7fda7bfff700 (LWP 1576)): #0 0x7fdb618e4667 in poll () at /usr/lib/libc.so.6 #1 0x7fdaec684c14 in () at /usr/lib/libpulse.so.0 #2 0x7fdaec692059 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7fdaec69c301 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fdaec69c3b1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fdaec68c61e in () at /usr/lib/libpulse.so.0 #6 0x7fdadc112d1c in () at /usr/lib/pulseaudio/libpulsecommon-12.99.so #7 0x7fdb617d657f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fdb618ef0e3 in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7fdaa0ff9700 (LWP 1575)): #0 0x7fdb618fc5cb in __lll_lock_wait_private () at /usr/lib/libc.so.6 #1 0x7fdb6185e514 in buffered_vfprintf () at /usr/lib/libc.so.6 #2 0x7fdb6185b764 in __vfprintf_internal () at /usr/lib/libc.so.6 #3 0x7fdb618fe123 in __fprintf_chk () at /usr/lib/libc.so.6 #4 0x7fdade0a4daf in event_logv_ () at /usr/lib/libevent-2.1.so.7 #5 0x7fdade0a4f78 in event_warn () at /usr/lib/libevent-2.1.so.7 #6 0x7fdade0a6a12 in () at /usr/lib/libevent-2.1.so.7 #7 0x7fdade09c915 in event_base_loop () at /usr/lib/libevent-2.1.so.7 #8 0x7fdaf0530548 in () at /usr/lib/libQt5WebEngineCore.so.5 #9 0x7fdaf04b9967 in () at /usr/lib/libQt5WebEngineCore.so.5 #10 0x7fdaf04fa9cf in () at /usr/lib/libQt5WebEngineCore.so.5 #11 0x7fdaf052c5f5 in () at /usr/lib/libQt5WebEngineCore.so.5 #12 0x7fdb617d657f in start_thread () at /usr/lib/libpthread.so.0 #13 0x7fdb618ef0e3 in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fdaa17fa700 (LWP 1574)): [KCrash Handler] #6 0x7fdb6182d755 in raise () at /usr/lib/libc.so.6 #7 0x7fdb61818851 in abort () at /usr/lib/libc.so.6 #8 0x7fdb6186fa38 in __libc_message () at /usr/lib/libc.so.6 #9 0x7fdb618ffa85 in __fortify_fail_abort () at /usr/lib/libc.so.6 #10 0x7fdb618ffa36 in () at /usr/lib/libc.so.6 #11 0x7fdaee9d8594 in () at /usr/lib/libQt5WebEngineCore.so.5 #12 0x7fdaee9d85f6 in () at /usr/lib/libQt5WebEngineCore.so.5 #13 0x7fdaee9d9de2 in () at /usr/lib/libQt5WebEngineCore.so.5 #14
[dolphin] [Bug 411489] New: USB (MTP) connection to Android fails if Dolphin was running before plugging in
https://bugs.kde.org/show_bug.cgi?id=411489 Bug ID: 411489 Summary: USB (MTP) connection to Android fails if Dolphin was running before plugging in Product: dolphin Version: 19.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY On two computers, both running up to date KDE Neon 19.08.0, we have this situation. STEPS TO REPRODUCE 1. With one or more Dolphin windows opened, plug your Android smartphone via USB (Samsung Galaxy S7 in our case). 2. Allow access on the device and click "Browse Files with File Manager" in the popup window. 3. Dolphin opens, but shows an error like "No media found. Check if the device is unlocked and MTP is enabled." OTOH, if I close *all* Dolphin windows before plugging the USB cable in the smartphone and then plug it in and allow access *before* opening the next Dolphin window, access works fine and I can browse the SD card and the internal memory of the phone. This may be libmtp related too, but I think the fact that Dolphin must not be running before plugging in the USB cable is a Dolphin issue, thus reporting to Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411442] New: German translation incorrect in Dolphin's context menu
https://bugs.kde.org/show_bug.cgi?id=411442 Bug ID: 411442 Summary: German translation incorrect in Dolphin's context menu Product: dolphin Version: 19.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY This is totally trivial but it annoys me. :-) The correct translation for "Copy to ... / Move to ..." in Dolphin's context menu for files (if enabled) is not "Kopieren/Verschieben *zu* ..." but "Kopieren/Verschieben *nach* ...". (Just as "Welcome to..." translates to "Willkommen *bei* ..." and not to"Willkommen *zu*".) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384396] Wish: display faces sorted by similarity (pre-grouped) instead of album/time/..
https://bugs.kde.org/show_bug.cgi?id=384396 --- Comment #5 from Jens --- Can we please revisit this feature request? It would help enormously when assigning face tags, even if face recognition is not (yet) perfect. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407777] Wrong icons for hibernate/suspend actions in the Favourites bar
https://bugs.kde.org/show_bug.cgi?id=40
--- Comment #3 from Jens Lallensack ---
Thanks, Nate Graham. I now noticed that the bug only occurs when using the
"Breath" Plasma Theme ("Breeze" works fine for me as well!).
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 408549] New: Many crashes on MacOS with current git appimage
https://bugs.kde.org/show_bug.cgi?id=408549 Bug ID: 408549 Summary: Many crashes on MacOS with current git appimage Product: digikam Version: 6.2.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Bundle-MacOS Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Created attachment 120763 --> https://bugs.kde.org/attachment.cgi?id=120763=edit crash log SUMMARY Digikam crashes frequently when resuming from sleep on Macbook Pro, or when exiting. See example trace attached. STEPS TO REPRODUCE 1. start digikam 2. enter sleep 3. resume OBSERVED RESULT crash EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Windows: macOS: 10.14.0 Qt Version: appimage ADDITIONAL INFORMATION digiKam-6.2.0-git-20190606T214155-MacOS-x86-64.pkg -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407777] New: Wrong icons for hibernate/suspend actions in the Favourites bar
https://bugs.kde.org/show_bug.cgi?id=40 Bug ID: 40 Summary: Wrong icons for hibernate/suspend actions in the Favourites bar Product: plasmashell Version: 5.15.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: i...@dinospuren.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When adding the leave actions "suspend" and/or "hibernate" to the favourites in Kicker, these will appear under Favourites but with different icons (the old geometric icons instead of the new stylized moon (for suspend) and snow flake (for hibernate)). STEPS TO REPRODUCE 1. Switch from the default "Kickoff" application launcher to the "Application menu" (Kicker) 2. Open Kicker -> Power/ Session; right-click on "Suspend" or "Hibernate", check "Add to Favourites". OBSERVED RESULT The checked leave actions (hibernate/suspend) appear in the Favourites, but with a different icon, respectively. EXPECTED RESULT The default icons should be shown (the moon for "suspend" and the snow flake for "hibernate"). SOFTWARE/OS VERSIONS Linux: Manjaro KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION This is a regression that was introduced when the icons for the "suspend" and "hibernate" actions where changed. The "Favourites" still shows the old icons. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407775] New: Leave actions not showing up under "Favourites"
https://bugs.kde.org/show_bug.cgi?id=407775 Bug ID: 407775 Summary: Leave actions not showing up under "Favourites" Product: plasmashell Version: 5.15.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: i...@dinospuren.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When marking leave actions (shut down, logout, suspend, hibernate, …), as "Favourites" using the default Kickoff application launcher, these will not appear in the "Favourites" tab. STEPS TO REPRODUCE 1. Right click on an entry in the "Leave" tab (e.g., "suspend", and check "Show in Favourites" -> "On all actvities". OBSERVED RESULT Nothing shows up in the Favourites tab, even after reboot. EXPECTED RESULT The entry is expected to be shown in the Favourites tab. SOFTWARE/OS VERSIONS Linux: Manjaro KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION This actually works fine with the alternative Kicker application menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392047] No/inconsistent search results for Power/Session/Leave menu section entries upon searching for them in Application Launcher/Menu/Dashboard
https://bugs.kde.org/show_bug.cgi?id=392047 Jens Lallensack changed: What|Removed |Added CC||i...@dinospuren.de --- Comment #4 from Jens Lallensack --- This works for me now, at least with the default Kickoff starter. All those entries show up. However, none of these entries shows up when searching using the alternative "Application menu" (based on cascading popup menus). Manjaro, Plasma 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407699] Text format for "add tag" and "remove tag" is inconsistent
https://bugs.kde.org/show_bug.cgi?id=407699 --- Comment #2 from Jens --- Nevertheless, Assign Tag and Remove Tag should use the same format, whichever this is. Users adding tags will search for the same format under "Remove tag" to remove the tag. IMHO, of course. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407699] New: Text format for "add tag" and "remove tag" is inconsistent
https://bugs.kde.org/show_bug.cgi?id=407699 Bug ID: 407699 Summary: Text format for "add tag" and "remove tag" is inconsistent Product: digikam Version: 6.2.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-IconView Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY This should be easy to resolve. "Assign tag" context menu has entries like "Name (Root / Parent)", while "Remove tag" context menu has entries like "Root / Parent / Name". The formats should be identical, everything else is needlessly confusing. I would prefer "Root / Parent / Name" for both. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407684] New: Wish: icon view (like thumbnails) & three column view for geolocation editor
https://bugs.kde.org/show_bug.cgi?id=407684 Bug ID: 407684 Summary: Wish: icon view (like thumbnails) & three column view for geolocation editor Product: digikam Version: 6.2.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Geolocation-Editor Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Created attachment 120160 --> https://bugs.kde.org/attachment.cgi?id=120160=edit mockup geolocation editor with thumbnails view SUMMARY When sorting images into locations, filename and date are usually not as important as the actual content of the images. Currently, the tabular view in the geolocation editor wastes a lot of screen space. I would like to have the same (or at least a similar) view as the thumbnails view for the geolocation editor, with selected metadata being displayed below the thumbnails (or none at all). Maybe we can even reuse the thumbnails view altogether? Also, since most displays are 16:9 widescreen nowadays, IMHO it makes a lot of sense to offer at least one three-column view: map, images (icons or tabular) and tags tree beside each other. Screenshot mockup attached. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407680] New: Cannot hear sound with video files
https://bugs.kde.org/show_bug.cgi?id=407680 Bug ID: 407680 Summary: Cannot hear sound with video files Product: digikam Version: 6.2.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Preview-Video Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. open Digikam 2. preview mp4 file (e.g. as produced by HandBrake or Samsung mobile phones) 3. turn on speakers or headphones OBSERVED RESULT No audio EXPECTED RESULT Audio mp4 files play fine with VLC and other players (and on smartphones). SOFTWARE/OS VERSIONS: Linux KDE Neon 18.04 (all updates applied), Digikam 6.2 git-20190509. This problem has existed since 6.0 release as far as I remember. It is not new. I was hoping it would go away with 6.1 but it did not. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 --- Comment #15 from Jens Mueller --- @David: This would mean if you attach a non-encrypted image to an encrypted... Absolutely, such an email could not be decrypted anymore if you follow our suggestions (or had to be manually decrypted on the command line). While this may seem a bit harsh, we have not seen any mail client that allows to send such "partially encrypted" emails (e.g., with unencrypted attachments), and I think handling such edge cases can become a security nightmare. Either the whole mail is encrypted or it's not, everything else gives a false sense of security, imho. However, I see the developer's perspective and the and the fear of potentially breaking things, too. I guess a rule like "in case of an encrypted, multipart email, reply only with the first part" *should* be fine too. @Sandro: We originally tested in version 5.2.3 on Debian 9.8 (stretch). This version is probably outdated by now. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 Jens Mueller changed: What|Removed |Added Version|5.10.3 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404697] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404697 --- Comment #7 from Jens Mueller --- Update: Here's a full (public) report on the issue: https://arxiv.org/ftp/arxiv/papers/1904/1904.07550.pdf For Trojitá, CVE-2019-10734 was assigned for reply-based `decryption oracles`. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 --- Comment #10 from Jens Mueller --- Update: Here's a full (public) report on the issue: https://arxiv.org/ftp/arxiv/papers/1904/1904.07550.pdf For KMail, CVE-2019-10732 was assigned for reply-based `decryption oracles`. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 --- Comment #9 from Jens Mueller --- Imho, there are no legitimate use cases for `partial encryption` in S/MIME and PGP/MIME, but it's hard to measure if such emails do exist in the wild. In case of PGP/Inline, unfortunately, every part is encrypted separately. Note that a captured PGP/MIME message can be `downgraded` to be interpreted in the context of PGP/INLINE. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 --- Comment #7 from Jens Mueller --- Exactly that's the problem. Note that not only one message, but hundreds of captured messages can be wrapped and leaked with one single reply. Traditional message takeover attacks under a new identity (C) are considered as an acceptable risk in email e2e encryption because it is assumed that given the context of the message (e.g.,“Hi A, [...] Yours, B”) B can tell that this message is not originally from C and could easily discover the deception. However, using MIME wrapping, C can make a different content being displayed to B (if B does not carefully scroll down the whole message conversation) and therefore potentially trick B into replying to C. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 --- Comment #4 from Jens Mueller --- Things may have changed in the meantime, but for the version we tested (v5.2.3), there is no need to click on "Decrypt Message". While the plaintext is not shown to the user, if he does not explicitly click "Decrypt Message", the plaintext is still included in replies -- just re-tested for S/MIME and PGP/MIME. Note that KMail was tested in the default settings (the option "Attempt decryption of encrypted messages when viewing" was *not* set). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406309] New: Tags reappear after being merged when several merge processes overlap(?)
https://bugs.kde.org/show_bug.cgi?id=406309 Bug ID: 406309 Summary: Tags reappear after being merged when several merge processes overlap(?) Product: digikam Version: 6.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Engine Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. create tags with lots of photos on them on a slow disk with XMP sidecars enabled and lazy sync off (?) 2. merge these tags 3. while the sync process is running, merge two other tags OBSERVED RESULT Merged tags sometimes reappear with a couple of photos. EXPECTED RESULT Synced tags should never reappear. It is possible that the sync process updating the XMP sidecars is "overtaken" by a DB update process re-reading the XMP sidecars when the second merge process starts, and so ready old data? Maybe digikam should pause/postpone sync processes if conflicting reads/writes to not-yet-synced metadata can occur. But I can't prove that this is actually the root cause of what I observed, it's just a guess. ADDITIONAL INFORMATION KDE Neon 18.04 with all updates applied, Digikam appimage 6.1.0-git as of 20190403. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377857] Ideas to improve usability of metadata sidebar
https://bugs.kde.org/show_bug.cgi?id=377857 --- Comment #14 from Jens --- How about this idea, any chances of implementing it in Digikam 6.x? I am here to help designing, I just need some help with the code. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406066] Cannot parse date string YYYY-MM-DDTHH:MM:SS.ssss and YYYY:MM:DD HH:MM:SS in EXIF and XMP
https://bugs.kde.org/show_bug.cgi?id=406066 --- Comment #3 from Jens --- Created attachment 119202 --> https://bugs.kde.org/attachment.cgi?id=119202=edit exiftool JSON export of example image Here is an exiftool JSON export which you can reapply to any image. It's the original image exported from Apple iPhoto without modifications (at least the file size and the mtime did not change). IMHO: Date strings like ":MM:DD HH:MM:SS" with an optional "+" or "+NN:00" timezone string appended (without or with space delimited) could be parseable by Digikam without harm even if they are not standard. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406066] New: Cannot parse date string YYYY-MM-DDTHH:MM:SS.ssss and YYYY:MM:DD HH:MM:SS in EXIF and XMP
https://bugs.kde.org/show_bug.cgi?id=406066
Bug ID: 406066
Summary: Cannot parse date string -MM-DDTHH:MM:SS. and
:MM:DD HH:MM:SS in EXIF and XMP
Product: digikam
Version: 6.1.0
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Metadata-Date
Assignee: digikam-bugs-n...@kde.org
Reporter: jens-bugs.kde@spamfreemail.de
Target Milestone: ---
SUMMARY
see $SUBJECT
STEPS TO REPRODUCE
1. import photo with this date string in EXIF metadata or XMP sidecar metadata
2. watch console output
OBSERVED RESULT
Digikam::MetaEngine::Private::printExiv2MessageHandler: Exiv2 ( 2 ) : Failed
to convert Xmp.xmp.ModifyDate to Exif.Image.DateTime (Invalid date string,
after day)
Digikam::MetaEngine::Private::printExiv2MessageHandler: Exiv2 ( 2 ) : Failed
to convert Xmp.photoshop.DateCreated to Exif.Photo.DateTimeOriginal (Invalid
date string, after day)
Digikam::MetaEngine::Private::printExiv2MessageHandler: Exiv2 ( 2 ) : Failed
to convert Xmp.xmp.CreateDate to Exif.Photo.DateTimeDigitized (Invalid date
string, after day)
EXPECTED RESULT
No errors. These dates (":MM:DD HH:MM:SS" and "-MM-DDTHH:MM:SS",
optionally with . sub-seconds appended) were created with a CANON IXUS 330
camera (old, but was widely used).
Using most current Git appimage on KDE Neon 18.04 with all current updates
applied.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 375375] Various bugs detecting and tagging faces in current 5.4.0 Digikam appimage
https://bugs.kde.org/show_bug.cgi?id=375375 --- Comment #29 from Jens --- Yes agreed. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404538] akonadi fails with "multiple merge candidates" after failed IMAP sync
https://bugs.kde.org/show_bug.cgi?id=404538 --- Comment #2 from Jens --- >> Akonadi is not clever enough to fix it > Yes, it's very complex and not easy to debug. Developers that use Akonadi > seem to never get those issues. But they need to reproduce those to be able > to fix them. This is why I kept my database and logs and am waiting for a request from a developer to help in debugging. I know it's hard to get an application into a "known broken state" for debugging. > Additionally, the choice of the desktop does not limit the choice for the > applications you use. I know. I am using Thunderbird for now and it works fine. But I liked the better integration into the rest of the desktop that Kontact/KMail/... offered. >> Please close this bug only after Akonadi has been made either significantly >> more robust > Sorry, but we do not keep duplicates open just because someone thinks it's > their private ticket. That's completely fine if there is a real duplicate. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen
https://bugs.kde.org/show_bug.cgi?id=392798 Jens Rutschmann changed: What|Removed |Added CC||jens.rutschm...@gmx.info -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404761] Settings and other dialogs should have a minimum default size of 800x600 (at least)
https://bugs.kde.org/show_bug.cgi?id=404761 --- Comment #2 from Jens --- First impressions count. At least if you want to attract non-geeks to Digikam. It's probably a one-liner (for the settings dialog and the initial settings wizard). I know a lot of people who never resize (or even maximize) windows, even browser windows, and resort to scrolling all the time - and some then think the application is "confusing". Not in a bad way, they just never get the idea they can resize windows. Maybe because they come from smartphones where this problem simply doesn't exist. Just my 2 cents though. ;) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404761] New: Settings and other dialogs should have a minimum default size of 800x600 (at least)
https://bugs.kde.org/show_bug.cgi?id=404761 Bug ID: 404761 Summary: Settings and other dialogs should have a minimum default size of 800x600 (at least) Product: digikam Version: 6.0.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT When opening Digikam for the first time, many dialog windows have the minimum size allowed by the current window manager. This is awkward since users always have to resize these windows first. Please make the minimum dialog window size to be at least 800x600 (to fit on as many screens as possible). Ideally, these windows should resize automatically so that there are no scrollbars when opening for the first time - but not exceeding the screen size of course. Example: Settings, EMail export, Lighttable (maybe start maximized), Editor, etc. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404748] New: Default Album rename dialog should be larger (or save its size when changed)
https://bugs.kde.org/show_bug.cgi?id=404748 Bug ID: 404748 Summary: Default Album rename dialog should be larger (or save its size when changed) Product: digikam Version: 6.0.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-TreeView Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. Select album 2. select "rename" from context menu OBSERVED RESULT Default "rename" dialog input field only allows about 20 characters, it's just 204 px wide. Even the window title is compressed / truncated. EXPECTED RESULT Make a larger default size (maybe a minimum of 400 or 500 pixels). And/or save the size when the user changes it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404736] New: Merging tags keeps popping up confirmation dialogs every second
https://bugs.kde.org/show_bug.cgi?id=404736 Bug ID: 404736 Summary: Merging tags keeps popping up confirmation dialogs every second Product: digikam Version: 6.0.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Engine Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY See $SUBJECT STEPS TO REPRODUCE 1. Enable sidecar files (XMP) and write only to sidecar files. Do not enable lazy sync. 2. Merge two tags with at least 1000 images inside of them, or move a tag hierarchy to a subhierarchy with >>1000 images tagged. OBSERVED RESULT Tag manager asks me about "this can take a lot of time in the background" about every second. Nevertheless, the operation finishes within ten seconds. EXPECTED RESULT Either put a "Do not ask again" checkbox in this dialog, or measure the time and only put up a single confirmation dialog during the merge/move process, asking the user *once* if they want to do this even if it takes a long time. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404735] New: F2 should edit tag name when tag name has focus
https://bugs.kde.org/show_bug.cgi?id=404735 Bug ID: 404735 Summary: F2 should edit tag name when tag name has focus Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Manager Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Currently, when the tag manager (sidebar) has focus, i.e. cursor movements move the tag selection, instead of the image selection, F2 still edits the image name currently selected. This is confusing. F2 should edit the tag name. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 --- Comment #1 from Jens Mueller --- Created attachment 118288 --> https://bugs.kde.org/attachment.cgi?id=118288=edit Proof-of-concept PGP -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404698] New: Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 Bug ID: 404698 Summary: Decryption Oracle based on replying to PGP or S/MIME encrypted emails Product: kmail2 Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: jens.a.mueller+...@rub.de Target Milestone: --- In the scope of academic research in cooperation with Ruhr-Uni Bochum and FH Münster, Germany we discovered a security issue in KMail: An attacker who is in possession of PGP or S/MIME encrypted messages can embed them into a multipart message and re-send them to the intended receiver. When the message is read and decrypted by the receiver, the attacker's content is shown. If the victim replies, the plaintext is leaked to an attacker's email address. The root cause for these vulnerabilities lies in the way KMail (and many other mail clients) handle partially encrypted multipart messages. - *Leaking plaintext through reply/forward* - /Attacker model/: Attacker is in possession of PGP or S/MIME encrypted messages, which she may have obtained as passive man-in-the-middle or by actively hacking into the victim's mail server or gateway /Attacker's goal/: Leak the plaintext by wrapping the ciphertext part within a benign-looking MIME mail sent to and decrypted+replied to by the victim /Attack outline:/ If KMail receives a multipart email, as depicted below, it decrypt the ciphertext part(s), together with the attacker-controlled text (which may be prepended and/or appended). multipart/mixed |--- Attacker's part |--- [encrypted part to leak] +--- [Attacker's encrypted part] A benign-looking attacker's text may lure the victim into replying. Because the decrypted part is also quoted in the reply, the user unintentionally acts as a decryption oracle. To obfuscate the existence of the encrypted part(s), the attacker may add a lot of newlines or hide it within a long conversation history. A user replying to such a ‘mixed content’ conversation thereby leaks the plaintext of encrypted messages wrapped within attacker-controlled text. Please find attached a raw .eml file which depicts the issue. --- Countermeasures --- Do not decrypt emails unless the PGP or S/MIME encrypted part is the root node -- and therefore the only part -- in the MIME tree (exception: multipart/signed for encrypted-then-signed S/MIME messages). Another, potentially less secure, option would be to quote only the very first MIME part in replies. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 --- Comment #2 from Jens Mueller --- Created attachment 118289 --> https://bugs.kde.org/attachment.cgi?id=118289=edit Proof-of-concept S/MIME -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404697] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404697 --- Comment #2 from Jens Mueller --- Created attachment 118287 --> https://bugs.kde.org/attachment.cgi?id=118287=edit Proof-of-concept S/MIME Please find attached a raw .eml file which depicts the issue for S/MIME. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404697] New: Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404697 Bug ID: 404697 Summary: Decryption Oracle based on replying to PGP or S/MIME encrypted emails Product: trojita Version: 0.7 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Cryptography Assignee: trojita-b...@kde.org Reporter: jens.a.mueller+...@rub.de Target Milestone: --- In the scope of academic research in cooperation with Ruhr-Uni Bochum and FH Münster, Germany we discovered a security issue in Trojitá: An attacker who is in possession of PGP or S/MIME encrypted messages can embed them into a multipart message and re-send them to the intended receiver. When the message is read and decrypted by the receiver, the attacker's content is shown. If the victim replies, the plaintext is leaked to an attacker's email address. The root cause for these vulnerabilities lies in the way Trojitá (and many other mail clients) handle partially encrypted multipart messages. - *Leaking plaintext through reply/forward* - /Attacker model/: Attacker is in possession of PGP or S/MIME encrypted messages, which she may have obtained as passive man-in-the-middle or by actively hacking into the victim's mail server or gateway /Attacker's goal/: Leak the plaintext by wrapping the ciphertext part within a benign-looking MIME mail sent to and decrypted+replied to by the victim /Attack outline:/ If Trojitá receives a multipart email, as depicted below, it decrypt the ciphertext part(s), together with the attacker-controlled text (which may be prepended and/or appended). multipart/mixed |--- Attacker's part |--- [encrypted part] +--- Attacker's part A benign-looking attacker's text may lure the victim into replying. Because the decrypted part is also quoted in the reply, the user unintentionally acts as a decryption oracle. To obfuscate the existence of the encrypted part(s), the attacker may add a lot of newlines or hide it within a long conversation history. A user replying to such a ‘mixed content’ conversation thereby leaks the plaintext of encrypted messages wrapped within attacker-controlled text. --- Countermeasures --- Do not decrypt emails unless the PGP or S/MIME encrypted part is the root node -- and therefore the only part -- in the MIME tree (exception: multipart/signed for encrypted-then-signed S/MIME messages). Another, potentially less secure, option would be to quote only the very first MIME part in replies. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 404697] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404697 --- Comment #1 from Jens Mueller --- Created attachment 118286 --> https://bugs.kde.org/attachment.cgi?id=118286=edit Proof-of-concept PGP Please find attached a raw .eml file which depicts the issue for PGP. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 404440] Giving up on Kontakt/Akonadi: too many crashes and mails lost
https://bugs.kde.org/show_bug.cgi?id=404440 --- Comment #3 from Jens --- Thanks. I created a new bug against akonadi. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404538] New: akonadi fails with "multiple merge candidates" after failed IMAP sync
https://bugs.kde.org/show_bug.cgi?id=404538 Bug ID: 404538 Summary: akonadi fails with "multiple merge candidates" after failed IMAP sync Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Using KDE Neon with all updates applied, based on Ubuntu 18.04. For the last few weeks, Kontact has not been updating its mails any more and I only see "retrieving folder contents ..." in the messages window. I tracked this down to an Akonadi issue where - it seems - an IMAP remotely stored mail was deleted twice. Something in the mail database has gotten out of sync, and Akonadi is not clever enough to fix it. I'm going back to Thunderbird for now. Despite KMail definitively being the better mail app. Sorry, gals 'n' guys. I went from Ubuntu to KDE Neon because I found KDE is by far the better desktop experience now that Unity is going (I liked Unity). I tried Kontact/KDE and was surprised what features it had compared to my Thunderbird/Lightning/SOGO setup with Caldav and Carddav. It worked great at first, maybe except for the weak HTML support in the mail editor (especially when replying). Then KMail started stalling when fetching mail, mostly after resuming from sleep mode, or when cleaning up inboxes with a lot of moving and deleting email. Some research pointed me to the Akonadi framework running in the background, and a ~2GB MySQL database in .local/share/akonadi acting as "cache" for all my mails. And this "cache" kept breaking on me. "akonadictl restart" on the console spew thousands of "multiple merge candidates" and "lock time exceeded" errors, which appeared again and again regardless how often I deleted my whole KDE setup and configured everything from scratch. Thunderbird is clunkier, not as nice, not as fast. But it *works*. I have never lost email. It can find the right email quickly with the global search feature and "drill down" options. Whatever local database it has, it doesn't break on me and doesn't create duplicate or missing emails. It uses about a third of the memory that Kontact + Akonadi + the mandatory MySQL server uses, and does not create *yet* another cache copy of my emails. Please close this bug only after Akonadi has been made either significantly more robust or replaced by something more robust. I will stay with KDE, and I will keep my Akonadi configuration, so if there are follow-up questions, I'm happy to answer and do some research to help fix this. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 404440] Giving up on Kontakt/Akonadi: too many crashes and mails lost
https://bugs.kde.org/show_bug.cgi?id=404440 --- Comment #1 from Jens --- Also, memory usage. Before the switch, I had - ~250MB mysqld process - ~200MB akonadi-server - ~200MB .. 300MB Kontact Now I have just ~250MB Thunderbird memory usage. I'm sure this is a sound technical solution and I applaud the effort - after all, this worked beautifully for some weeks. But it really needs to be more robust against race conditions and the like. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 404440] New: Giving up on Kontakt/Akonadi: too many crashes and mails lost
https://bugs.kde.org/show_bug.cgi?id=404440 Bug ID: 404440 Summary: Giving up on Kontakt/Akonadi: too many crashes and mails lost Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Application: kontact (5.10.1) Qt Version: 5.12.0 Frameworks Version: 5.55.0 Operating System: Linux 4.15.0-45-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: I'm going back to thunderbird. Despite KMail definitively being the better mail app. Sorry, gals 'n' guys. I went from Ubuntu to KDE Neon because I found KDE is by far the better desktop experience now that Unity is going (I liked Unity). I tried Kontact/KDE and was surprised what features it had compared to my Thunderbird/Lightning/SOGO setup with Caldav and Carddav. It worked great at first, maybe except for the weak HTML support in the mail editor (especially when replying). Then KMail started stalling when fetching mail, mostly after resuming from sleep mode, or when cleaning up inboxes with a lot of moving and deleting email. Some research pointed me to the Akonadi framework running in the background, and a ~2GB MySQL database in .local/share/akonadi acting as "cache" for all my mails. And this "cache" kept breaking on me. "akonadictl restart" on the console spew thousands of "multiple merge candidates" and "lock time exceeded" errors, which appeared again and again regardless how often I deleted my whole KDE setup and configured everything from scratch. Thunderbird is clunkier, not as nice, not as fast. But it *works*. I have never lost email. It can find the right email quickly with the global search feature and "drill down" options. Whatever local database it has, it doesn't break on me and doesn't create duplicate or missing emails. Please close this bug only after Akonadi has been made either significantly more robust or replaced by something more robust. I will stay with KDE, and I will keep my Akonadi configuration, so if there are follow-up questions, I'm happy to answer and do some research to help fix this. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f766c4f7080 (LWP 9566))] Thread 29 (Thread 0x7f74e2b92700 (LWP 16169)): #0 0x7f7664713ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f74e2b91750, expected=0, futex_word=0x7f74e2b91938) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f74e2b917f0, mutex=0x7f74e2b918e8, cond=0x7f74e2b91910) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f74e2b91910, mutex=0x7f74e2b918e8, abstime=0x7f74e2b917f0) at pthread_cond_wait.c:667 #3 0x7f7659f74177 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7659f74ada in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7659f74bc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7659f32851 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7659f35387 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7659f35974 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f7659f76cd1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f766470d6db in start_thread (arg=0x7f74e2b92700) at pthread_create.c:463 #11 0x7f7668e1688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7f74e4395700 (LWP 16168)): #0 0x7f7664713ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f74e4394750, expected=0, futex_word=0x7f74e4394938) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f74e43947f0, mutex=0x7f74e43948e8, cond=0x7f74e4394910) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f74e4394910, mutex=0x7f74e43948e8, abstime=0x7f74e43947f0) at pthread_cond_wait.c:667 #3 0x7f7659f74177 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7659f74ada in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7659f74bc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7659f32851 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7659f356b6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7659f35974 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCo
[kontact] [Bug 403604] New: kmail does not update main message body area when showing empty email (keeps previous email body)
https://bugs.kde.org/show_bug.cgi?id=403604 Bug ID: 403604 Summary: kmail does not update main message body area when showing empty email (keeps previous email body) Product: kontact Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY kmail does not display mail (at all) when it has no content, even if attachments exist. STEPS TO REPRODUCE 1. create empty plain text mail with attachment (7z file in my case) from MS Outlook 2016 (in my case, I don't know if this matters) 2. send this to kmail account 3. view with kmail OBSERVED RESULT kmail does not display, but also does not empty, the message body area. It just keeps displaying the previously displayed message EXPECTED RESULT kmail should show an empty message body and the attachment area (or an icon for the attachment(s)). SOFTWARE/OS VERSIONS Windows: - MacOS: - Linux/KDE Plasma: KDE Neon 18.04 with all updates applied, KMail 5.10.1 (available in About System) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403350] After rotating video, when changing video date time, rotation flag is reset
https://bugs.kde.org/show_bug.cgi?id=403350 --- Comment #7 from Jens --- Good point. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403350] After rotating video, when changing video date time, rotation flag is reset
https://bugs.kde.org/show_bug.cgi?id=403350 --- Comment #5 from Jens --- Yes, and only in Sidecar files. Originals are not modified. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403350] After rotating video, when changing video date time, rotation flag is reset
https://bugs.kde.org/show_bug.cgi?id=403350 --- Comment #2 from Jens --- I understand, but it is still a bug since it violates the principle of least surprise for the user. https://en.wikipedia.org/wiki/Principle_of_least_astonishment To a user, a connection between mtime and properties is not apparent and should not exist. The mtime is simply another property of the image. So changing the mtime should not have an effect on any other properties. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403350] New: After rotating video, when changing video date time, rotation flag is reset
https://bugs.kde.org/show_bug.cgi?id=403350 Bug ID: 403350 Summary: After rotating video, when changing video date time, rotation flag is reset Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbs-Video Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- 1. Rotate a video (Ctrl-Shift-Left/right) - THANK YOU this finally works! 2. Change the video's timestamp (not with BQM, but with the separate tool) Expected: Rotation flag (and all other attributes) should be kept Actual: Rotation is reset, thumbnail is updated -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #19 from Jens --- 5.9 on new user account with clean KDE Neon installation: - after first startup, 370MB - more than 6.0-beta3, actually - after previewing images: 376MB, 400MB, ... up to 531MB - after detecting faces: 514MB Don't get me wrong. If Digikam temporarily needs 2GB of RAM to do some task, that's fine. But after that task the memory should be freed again, otherwise there's a bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #17 from Jens --- 20180930_161217.jpg is indeed broken - no thumbnail and no preview. I actually didn't notice that at all. So this image is probably not part of the problem. I installed Virtualbox, KDE Neon 18.04 and Digikam appimage and started Digikam with a new and empty user account, went through the wizard, accepted all defaults and then imported about 20 JPG images of ~5MB each. Results: - after startup, RSS=192MB - after showing the first image, RSS=256MB - after the second image, 285MB, after the third, 312MB - after browsing all images once, ~420MB - Running face detection on *just* this folder (context menu) makes RES go up to 550MB temporarily, then dropping back to ~360MB So it's less, but still a lot for an application that "just" displays some JPEG files. For KDE Neon, digikam 5.9 is available in the repos. Can I jump back and forth between 5.9 and 6.0 without destroying the database to check whether this makes any difference? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402871] Import: Show message when no new files are available and the "New files" filter is active
https://bugs.kde.org/show_bug.cgi?id=402871 --- Comment #2 from Jens --- True. The same issue is valid for Dolphin. But still: I've had my fair share of "WTF" moments when Digikam showed no files although I *knew* there were new images on the medium or camera. I just want Digikam to avoid confusion especially for new users. And I think the change is trivial enough (just add a text box and translations). But maybe I'm wrong ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #13 from Jens --- Will do. For now, I cleaned all databases, started Digikam (~160MB RSS), then looked at a single image (preview) and RSS went up to ~312MB. Just because of a single image. Look at another one, RSS jumps to 512MB. Very strange. I looked at the console output from before clicking on a thumbnail and after, and saw multiple "invalid memory allocation request" errors: Do you think this could be part of the reason? Digikam::DImg::load: "/home/jens/Bilder/Digikam/2018/2018.09.30/20180930_184649.jpg" : JPEG file identified Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile. Digikam::StackedView::setViewMode: Stacked View Mode : 1 Digikam::DImg::load: "/home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg" : JPEG file identified Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot load metadata from file /home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg (Error # 57 : invalid memory allocation request Digikam::DImg::load: "/home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg" : QIMAGE file identified Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot load metadata from file /home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg (Error # 57 : invalid memory allocation request Digikam::QImageLoader::load: Can not load " "/home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg" " using DImg::QImageLoader! Digikam::PreviewLoadingTask::execute: Cannot extract preview for "/home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg" Digikam::StackedView::setViewMode: Stacked View Mode : 1 Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot load metadata from file /home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg (Error # 57 : invalid memory allocation request Digikam::JPEGUtils::isJpegImage: mimetype = "" ext = "JPG" Digikam::ThumbnailCreator::createThumbnail: Trying to load Embedded preview with libraw Digikam::DRawDecoder::loadEmbeddedPreview: Failed to load embedded RAW preview Digikam::ThumbnailCreator::createThumbnail: Trying to load half preview with libraw Digikam::ThumbnailCreator::createThumbnail: Trying to load Embedded preview with Exiv2 Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot load metadata using Exiv2 (Error # 57 : invalid memory allocation request Digikam::DImg::load: "/home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg" : JPEG file identified Digikam::DImg::load: "/home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg" : QIMAGE file identified Digikam::QImageLoader::load: Can not load " "/home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg" " using DImg::QImageLoader! Digikam::ThumbnailCreator::createThumbnail: Trying to load video preview with FFmpeg Digikam::VideoDecoder::initialize: Could not open input file: "/home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg" Digikam::ThumbnailCreator::createThumbnail: Cannot create thumbnail for "/home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg" Digikam::ThumbnailCreator::load: Thumbnail is null for "/home/jens/Bilder/Digikam/2018/2018.09.30/20180930_161217.jpg" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #11 from Jens --- Anything I can enable using kdebugdialog5 to help track this? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #10 from Jens --- Basically, this started after Linux's OOM killer went on a rampage on my system a few times. I have 8GB of RAM. After the initial shock I started looking more closely and it *always* happened when digikam had been running for a while. Then I started the KDE system monitor and htop (RSS column) and watched the digikam processes (htop shows about 15 PIDs, all of which are called 'digikam'). Initial startup size is ~200MB (~2G virtual). When looking at a few images, it jumps to ~650MB (~4G virtual). When running the face detection on a few images (via context menu) RAM usage jumps to ~1.5G temporarily, then settles at ~1.2GB. I never experienced this on previous releases and never with my old Ubuntu 16.04 system. This is a new phenomenon on KDE Neon. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #8 from Jens --- KDE Neon (based on Ubuntu 18.04) with all updates applied. 64bit. I have about 180GB of images and videos, ~33000 files. If you want we can debug this together, using Teamviewer or something. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #6 from Jens --- I should add I am using Digikam on a dual screen setup, one 1920x1080 FullHD monitor and one 2560x1440 QHD-Monitor to the left (secondary screen). Just in case this makes a difference ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402872] New: Hide geolocation tags below images in thumbnail view
https://bugs.kde.org/show_bug.cgi?id=402872 Bug ID: 402872 Summary: Hide geolocation tags below images in thumbnail view Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-IconView Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- In thumbnail view, geolocation tags (if tag display is enabled) tend to spam the tag views, preventing other tags from fitting onto the available space. Face tags also might do this. It would be beneficial to have an option to show only the names of "non-geo" tags below the image thumbnails. Or separate geo tags and face tags from "other" tags and let users choose which ones to put below the image thumbnails. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377099] Hightlight certain albums / tags in tree view
https://bugs.kde.org/show_bug.cgi?id=377099 --- Comment #1 from Jens --- Is there any chance of this getting into 6.x? Thanks! :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #5 from Jens --- I am now using the appimage from 20181228 and the memory hole has even become worse. The digikam process now has 2GB resident memory without using face detection at all, just for having Digikam hang around in the background for half a day. When I restart it, it's back to ~200MB at the start. How can I further help debug this? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402871] New: Import: Show message when no new files are available and the "New files" filter is active
https://bugs.kde.org/show_bug.cgi?id=402871 Bug ID: 402871 Summary: Import: Show message when no new files are available and the "New files" filter is active Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import-MainView Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT In the import view, if no new files are available and the "New Files" filter is activated, Digikam should show a message in the center of the main view saying something like "No *new* images are available for import. If you want to see all available images, select 'All Files' instead of 'New Files' in the bottom toolbar." This should not be a dialog window you have to dismiss, just a text box in the center of the main part of the Digikam window where otherwise thumbnails would be shown. I think this is better than showing nothing at all (which might also be due to slow reading from the medium, or read errors, or a medium missing, or ...) and much less confusing for new users. Empty screens should always be avoided - even an empty Album (or tag, in tag view) in Digikam should have a message in the main view saying "This album is empty" / "This tag has not been used on any images yet." or something similar. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402809] Clicking on "Import" toolbar button in import preview does nothing
https://bugs.kde.org/show_bug.cgi?id=402809 --- Comment #1 from Jens --- PS: This bug is old, I also witnessed it on Digikam 4.14 already. It survived multiple Digikam and even system upgrades and new installations so I expect it's not a config issue. I just never got around to reporting it. :-/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402812] New: Use RED "recycle bin" icon from Albums context menus in all other 'delete' context menu items too
https://bugs.kde.org/show_bug.cgi?id=402812 Bug ID: 402812 Summary: Use RED "recycle bin" icon from Albums context menus in all other 'delete' context menu items too Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-IconView Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT The current Digikam version sports a red (!) trashcan icon in the Albums context menu for deleting. Can we have this red icon in all context menus where stuff is being deleted? Maybe even color the text itself red ... this makes it much easier to find (and maybe avoid) the "Delete" context menu item. Examples include Image delete and Tag delete context menu items. This would (IMHO) greatly improve the usability. Especially since the image delete menu item says "5 Dateien in den Papierkorb werfen" and thus doesn't start with a "delete-like" keyword, at least in the German translation, which makes it harder to find. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402809] New: Clicking on "Import" toolbar button in import preview does nothing
https://bugs.kde.org/show_bug.cgi?id=402809 Bug ID: 402809 Summary: Clicking on "Import" toolbar button in import preview does nothing Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import-Albums Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. insert USB device with images on it, select Import in Digikam 2. preview appears with thumbnails 3. select some images, or select all, or select none, and press "Import" in the toolbar OBSERVED RESULT Nothing happens EXPECTED RESULT The import button (which is actually a dropdown menu with three choices) should automatically select the most appropriate action: if some images are selected, clicking on it should "Import selected", if all or none are selected, it should start "Import new". "Import all" should only be used if explicitly all images are displayed, and also selected. Or, at least, the button should cause the menu to open, so the users are not confused as to why nothing happens. Using the most current appimage on KDE-Neon 18.04 with all updates applied. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388386] Time adjustment tool is misleading and potentially leads to data loss
https://bugs.kde.org/show_bug.cgi?id=388386 --- Comment #10 from Jens --- Will this make it into 6.0-final? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402800] New: Main album view does not update when moving images between albums
https://bugs.kde.org/show_bug.cgi?id=402800 Bug ID: 402800 Summary: Main album view does not update when moving images between albums Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-MainView Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. Open an album that has sub-albums, so that the main view displays multiple albums. 2. move an image from one of the sub-albums into another sub-album OBSERVED RESULT The image is moved, the count of images in the tree view (if enabled) is updated, but the main view isn't updated to reflect the new position of the moved image. When deleting an image, the main view is updated as expected. EXPECTED RESULT The main view should be updated, while keeping the scrolling position and the selected image(s) (if any) the same. Optionally, there should be a way to automatically delete albums which become empty due to a move or delete operation. Or an option "delete all empty albums" (hotkey, button, etc). SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE-Neon 18.04 with KDE 5.14.1 (available in About System) KDE Frameworks 5.51.0 Qt 5.9.7 (kompiliert gegen 5.9.7) Das xcb Fenstersystem -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385148] Form fields are almost invisible using most "dark" shipped themes
https://bugs.kde.org/show_bug.cgi?id=385148 --- Comment #13 from Jens --- Created attachment 117208 --> https://bugs.kde.org/attachment.cgi?id=117208=edit breeze dark color scheme I tried the new color scheme and the form fields are much better now. But - of course - the colors are different from other apps when using "Breeze Dark" color scheme. I tried to get the checkbox border colors to be white (just like the text) in the Breeze Dark colorscheme (attached) but I could no find a way to *only* modify the checkbox borders. The color (38,42,46) that the checkbox borders have is nowhere in the colorscheme file and seems to be autogenerated from other colors. But which ones? Can you give me a hint which setting to modify? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402693] New: Error "This device is already mounted at /media/user/XXXX" when mounting encrypted LUKS partitions
https://bugs.kde.org/show_bug.cgi?id=402693 Bug ID: 402693 Summary: Error "This device is already mounted at /media/user/" when mounting encrypted LUKS partitions Product: dolphin Version: 18.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- I get "This device is already mounted at /media/jens/" error messages frequently. Please check that you are not mounting stuff repeatedly when handling encrypted LUKS partitions. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400682] Separate network shares (eg. CIFS) from "Devices" sidebar; remove duplicate entries
https://bugs.kde.org/show_bug.cgi?id=400682 --- Comment #6 from Jens --- 1. https://bugs.kde.org/show_bug.cgi?id=402690 2. https://bugs.kde.org/show_bug.cgi?id=402691 3. https://bugs.kde.org/show_bug.cgi?id=402692 4. https://bugs.kde.org/show_bug.cgi?id=402693 Thank you! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402692] New: Unable to *re*mount encrypted removable volumes with Dolphin after unmounting
https://bugs.kde.org/show_bug.cgi?id=402692 Bug ID: 402692 Summary: Unable to *re*mount encrypted removable volumes with Dolphin after unmounting Product: dolphin Version: 18.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- KDE / Dolphin / the underlying framework does not call "dmsetup remove /dev/mapper/luks-$UUID" or an equivalent API call after umounting the last partition in the LUKS container. This causes KDE to be unable to mount this device ever again until the next reboot. This works when directly ejecting the USB disk, but not when umounting the encrypted partition first. => Mounting and umounting encrypted partitions on removable media repeatedly should be possible. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402691] New: Encrypted partitions on removable media appear under "Devices" instead of under "Removable media"
https://bugs.kde.org/show_bug.cgi?id=402691 Bug ID: 402691 Summary: Encrypted partitions on removable media appear under "Devices" instead of under "Removable media" Product: dolphin Version: 18.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Encrypted partitions on removable media appear under "Devices" instead of under "Removable media". => They should replace(!) the "X GB encrypted partition" entry under "Removable media" instead, when mounted. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402690] New: Duplicate entries in Location sidebar for encrypted volumes
https://bugs.kde.org/show_bug.cgi?id=402690 Bug ID: 402690 Summary: Duplicate entries in Location sidebar for encrypted volumes Product: dolphin Version: 18.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Copied from #400682 Encrypted partitions still show as duplicates (one "XGB encrypted partition" entry and, if mounted, one "$LABEL" entry). => If a LUKS device is opened, it should not show up any more. If all partitions in a LUKS device are umounted, it should appear again. This is - I think - how Nemo, Nautilus etc. do it, these file managers do not have that kind of issue and never had (since Ubuntu 12.04 at least). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #4 from Jens --- Main dialog: - select "search again and merge results" in dropdown menu - select "detect and recognize faces" Options: - Albums: choose some albums (in my case, 10..56) - all keywords (default) - Parameters: 80% precision - Use all cores - Deep Learning or LBP algorighm (doesn't make a difference) All this on an i5-4750 with 8G RAM, KDE Neon 5.14.4 with all updates applied and Digikam appimage as mentioned before. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402322] New: During face detection, the "People" / "Unconfirmed" (or "Unknown") tab content keeps jumping around
https://bugs.kde.org/show_bug.cgi?id=402322 Bug ID: 402322 Summary: During face detection, the "People" / "Unconfirmed" (or "Unknown") tab content keeps jumping around Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $subject STEPS TO REPRODUCE 1. Start face detection, watch new faces appear in the "unknown" (or "unconfirmed") area. 2. try to confirm or change face names while detection is running OBSERVED RESULT When a new face is detected, the screen scrolls suddenly or the content jumps around. EXPECTED RESULT The content should not move, at least while the mouse cursor is inside the main area, or the user is editing a name field. Otherwise users run the risk of deleting or modifying the wrong face, and it is very hard to find it again and correct the mistake (usability hell). Running most current KDE 5.14.4 Plasma on KDE Neon, with Digikam 6.0-beta3 appimage as of 20181215. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #2 from Jens --- Update 2: With appimage 20181208, memory usage also spikes, but not as high (up to ~900MB, instead of 1.5GB). Same database, same settings, etc. Also, with both engines, the speed for detection has become RREEAALLYY SSLLOOWW ... I was used to ten times this speed with Digikam 5.x. But 20181208 is still noticeably faster than 20181215, too. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #1 from Jens --- Update: this also happens when using the other engine (not the deep learning engine), and the memory usage stays at >1GB after using face detection, and memory usage was <200MB before using face detection. So there is a leak somewhere, it seems. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] New: Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 Bug ID: 402320 Summary: Memory hole (>1.5GB resident after 2 minutes) when detecting faces Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Engine Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. have database with >40.000 images 2. Select many (>30) albums with new images 3. start OBSERVED RESULT memory usage jumps to >1GB and keeps growing slowly to ~1.5GB after a few minutes EXPECTED RESULT Memory usage should not grow significantly. Using neural network enginge for detecting faces. Using KDE Neon 5.14.4, and most current appimage from files.kde.org. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385148] Form fields are almost invisible using most "dark" shipped themes
https://bugs.kde.org/show_bug.cgi?id=385148 --- Comment #6 from Jens --- Created attachment 116948 --> https://bugs.kde.org/attachment.cgi?id=116948=edit screenshot with checkboxes in KDE dark theme -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385148] Form fields are almost invisible using most "dark" shipped themes
https://bugs.kde.org/show_bug.cgi?id=385148 --- Comment #5 from Jens --- Any news on this bug? I switched to KDE Neon (based on Ubuntu 18.04) and have all updates applied, even with the "Breeze Dark" theme applied in KDE and elsewhere, this doesn't really improve the situation. See attached screenshot. All other KDE apps have a clearly visible border around checkboxes and form fields, Digikam does not. Can we update the digikam appimage themes with the ones available in KDE? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted
https://bugs.kde.org/show_bug.cgi?id=402017 --- Comment #3 from Jens --- This is true. I can, however, "Print" to a new PDF file. This is bad because it loses quality and embedded text and comments / annotations, but it proves the file is still available in memory and *could* be saved. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402017] New: Cannot save PDF when loaded file has been deleted
https://bugs.kde.org/show_bug.cgi?id=402017 Bug ID: 402017 Summary: Cannot save PDF when loaded file has been deleted Product: okular Version: 1.5.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY I opened a PDF from a mail (i.e. it was downloaded to /tmp/messageviewer_XYZfoobar/whatever.pdf and then opened), and did some commenting and annotating. In the meantime, some cron job (I suppose) removed this folder from /tmp. Now I cannot "Save as ..." and I cannot "save" any more because Okular complains the file was "modified by another program". I think since the PDF is still in memory (since I can see it and browse it and continue modifying it) it should be possible to write it to disk? Using KDE Neon 18.04 with all updates applied. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400682] Separate network shares (eg. CIFS) from "Devices" sidebar; remove duplicate entries
https://bugs.kde.org/show_bug.cgi?id=400682 Jens changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #4 from Jens --- I actually went the whole way and installed KDE Neon based on Ubuntu 18.04 which I quite like! However, Dolphin's behaviour in the sidebar is, while improved, not fully consistent yet: 1. Encrypted partitions still show as duplicates (one "XGB encrypted partition" entry and, if mounted, one "$LABEL" entry). => If a LUKS device is opened, it should not show up any more. If all partitions in a LUKS device are umounted, it should appear again. This is how Nemo, Nautilus etc. do it. 2. Encrypted partitions on removable media appear under "Devices" instead of under "Removable media". => They should replace(!) the "X GB encrypted partition" entry under "Removable media" instead, when mounted. 3. KDE / Dolphin / the underlying framework does not call "dmsetup remove /dev/mapper/luks-$UUID" or an equivalent API call after umounting the last partition in the LUKS container. This causes KDE to be unable to mount this device ever again until the next reboot. This works when directly ejecting the USB disk, but not when umounting the encrypted partition first. => Mounting and umounting encrypted partitions on removable media repeatedly should be possible. 4. I get "This device is already mounted at /media/jens/" error messages frequently. Please check that you are not mounting stuff repeatedly when handling encrypted LUKS partitions. I'd be really happy to support fixing these issues. :-) Thank you! -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 321705] Server Authenticity check dialog pops up on startup, even though the certificate is saved forever.
https://bugs.kde.org/show_bug.cgi?id=321705 --- Comment #5 from Jens Jorgensen --- (In reply to Andrew Crouthamel from comment #2) > Dear Bug Submitter, > > This bug has been stagnant for a long time. Could you help us out and > re-test if the bug is valid in the latest version? I am setting the status > to NEEDSINFO pending your response, please change the Status back to > REPORTED when you respond. > > Thank you for helping us make KDE software even better for everyone! freenode uses proper certificates now, so I don't have a means to test the problem as it existed before. So, the problem may or may not exist, but I don't have an easily accessible means of testing it myself--I'd have to setup my own XMPP server and use a self-signed cert. I'm a bit busy to take that on right now. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen
https://bugs.kde.org/show_bug.cgi?id=392798 Jens changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #10 from Jens --- Yes, please (pretty please) add an option to shutdown, logout, suspend etc. from the lock screen. It's fine to have an option to hide those buttons but this should not be the default. Any security considerations are invalid if the machine is physically accessible (since a user could just pull the plug to "shut down", or press the power button a little longer). And I just switched from Unity on Ubuntu 16.04 to KDE (Neon) and I am sorely missing this feature too. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400682] Separate network shares (eg. CIFS) from "Devices" sidebar; remove duplicate entries
https://bugs.kde.org/show_bug.cgi?id=400682 --- Comment #2 from Jens --- That's great to hear. How do I get this on my Ubuntu 18.04 system while keeping the "LTS" stamp on it, i.e. not having to upgrade half the system to an unsupported state? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400691] A folder called $HOME/.cache/kioexec/krun/xxxxxx_xx/ already exists.
https://bugs.kde.org/show_bug.cgi?id=400691 Jens changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Jens --- Changing state. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400691] A folder called $HOME/.cache/kioexec/krun/xxxxxx_xx/ already exists.
https://bugs.kde.org/show_bug.cgi?id=400691 --- Comment #2 from Jens --- No, all files and folders beneth .cache/kioexec/krun are owned by me and mode 0755 (dirs) and 0664 (files). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400691] A folder called $HOME/.cache/kioexec/krun/xxxxxx_xx/ already exists.
https://bugs.kde.org/show_bug.cgi?id=400691 Jens changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400691] New: A folder called $HOME/.cache/kioexec/krun/xxxxxx_xx/ already exists.
https://bugs.kde.org/show_bug.cgi?id=400691 Bug ID: 400691 Summary: A folder called $HOME/.cache/kioexec/krun/xx_xx/ already exists. Product: kdeconnect Version: 1.3.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. Click on the "folder" icon in the KDE connect taskbar area (next to the "Ring phone" icon) 2. above error appears 3. OBSERVED RESULT see #2 EXPECTED RESULT Dolphin should open with the phone mounted and files on the phone visible SOFTWARE VERSIONS (available in About System) KDE Plasma Version: Kubuntu 18.04 standard KDE version shipped by default, all updates applied -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400682] New: Separate network shares (eg. CIFS) from "Devices" sidebar; remove duplicate entries
https://bugs.kde.org/show_bug.cgi?id=400682 Bug ID: 400682 Summary: Separate network shares (eg. CIFS) from "Devices" sidebar; remove duplicate entries Product: dolphin Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Not running the most recent release but I could not find evidence in KDE's changelogs that this has been addressed, so I'm reporting it anyway. SUMMARY 1. Dolphin's "Places" sidebar does not keep local devices (partitions, USB media, etc.) separate from remote mounts (e.g. CIFS). I think having a separate group with CIFS mounts, this would clean up the sidebar a lot. 2. Dolphin duplicates LUKS partition entries. I have a LUKS partition on my system which is not automounted (I don't use it very often, it's a long term archive). With Nemo and Nautilus, I can click on the "1TB Encrypted Disk", enter a password and the entry is replaced(!) with an entry with the partition label as its name. With Dolphin, the entry with the partition label is added(!), so I now have to items pointing to the same location, which is confusing. Also, since my root is also LUKS encrypted (Ubuntu installation default), I also have (1) an entry "480GB Disk" for "/" (which should not be needed) and an entry "480GB Encrypted Disk" which causes an error "No such interface 'org.freedesktop.UDisks2.Filesystem' on object at path /org/freedesktop/UDisks2/block_devices/dm_2d0" when clicking on it. Both entries do not exist in Nemo or Nautilus. I would suggest: 1. To hide any items pointing to file systems that users cannot (un)mount, e.g. the root file system 2. To hide "X.XG encrypted disk" entries for disks that have been opened by LUKS 3. To add a group "Network" for network mounts (e.g. a configurable list of specified file systems, e.g. cifs,smbfs,nfs,afs) to the "Places" sidebar, and for remote file systems, group these entries by remote hostname. STEPS TO REPRODUCE 1. Install Ubuntu 18.04 LTS with KDE 2. compare sidebare entries of Nemo, Nautilus and Dolphin -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 364357] muon seems not to load the software list and stops
https://bugs.kde.org/show_bug.cgi?id=364357 --- Comment #4 from Jens --- Hello Andrew Crouthamel, I already could handle this faulty behaviour by using apt-get update and upgrade in the terminal. I'm sorry not to be able to remember the exact cause of this former error, but in the meantime I could figure out that muon ***always*** behaves like this when any kind of error happens on updating/upgrading system components and with kept back packages either by error or by intention. I guess at least an error message would be quite helpful on this issue to have a clue, what this error is about so the user can do a workaround with the terminal and maybe get help from the package sources that failed to update/upgrade. The muon version is still the same as there is no version upgrade available for Kubuntu 14 LTS. Thanks for the reminder! Jens PS: I'm not sure about the status selection as though I found a work around the issue itself still isn't solved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400493] New: Filter 'Desaturate' calculates average wrong
https://bugs.kde.org/show_bug.cgi?id=400493
Bug ID: 400493
Summary: Filter 'Desaturate' calculates average wrong
Product: krita
Version: unspecified
Platform: Other
OS: MS Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: Filters
Assignee: krita-bugs-n...@kde.org
Reporter: j...@campi3d.com
Target Milestone: ---
'Average' mode on Desaturate Filter calculated average wrong.
In the code it says:
case 3: // average
{
gray = (r + g + b) / 2;
break;
}
As you can see it divides by 2. Not by 3.
This results in a lot brighter result.
STEPS TO REPRODUCE
1. Use Desaturate Filter, set to Average
2. Observe the 'blooming' of values way above what the average really is for
the 3 channels.
EXPECTED RESULT
It should calculate the average value of Red, Green and Blue channel by adding
them together and dividing by 3.
SOFTWARE VERSIONS
Krita
Version: 4.1.1
OS Information
Build ABI: x86_64-little_endian-llp64
Build CPU: x86_64
CPU: x86_64
Kernel Type: winnt
Kernel Version: 10.0.17134
Pretty Productname: Windows 10 (10.0)
Product Type: windows
Product Version: 10
OpenGL Info
**OpenGL not initialized**
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 399665] Breeze drawing tool tool icons need improvement
https://bugs.kde.org/show_bug.cgi?id=399665 --- Comment #3 from Jens Reuterberg --- So looking around this bug using Cuttlefish there are some really easy fixes Textfield: replacing the tool-text icon with the draw-text icon would fix for example the "text" symbol in Kolourpaint as it actually as a large T in it or better yet something like xml-text-new, the icon Kolourpaint uses is inherited from document editors which isn't ideal for a drawing app since there you don't really automatically assume its going to be "text" there) To moderately complex ones Selection Symbols: Improving sizeing of the lassoo symbol in tool_free_form_selection with its too narrow dots that blend together. bigger dots to emphasize it COMBINED with adding dots to the selections fields in tool_elliptical_selection and select-rectangular icons would make it more clear that, yes this is selection - the dotted border is basically shorthand for it anyway so might be worth while in general. (select-rectangular should be looked into a bit more, the added complexity with the pen is not useful in most scenarios and could be replaced with a dotted rectangle and the handles (like tool_elliptical_selection)) Polygon: The polygon symbol is filled in, the circle, the square and the rounder corners square (which should be slightly more square in my eyes to be readable) are not making them look unrelated. Swapping the polygon one for the "connected lines one" would make them look related and make more sense over all Connected Lines: This needs a completely new icon, preferrably based off of "Curve" - something like lines-connector might work but with more "zigzag" to it. ' The the damn fiddly things... Zoom: We need a better zoom symbol language or at least some kind of fallback for simpler applications - the current ones we have are made for professional apps and often miss the mark even if they are relevant and critical in those apps. A simple "search" symbol with a plus connected as per icon specs would fit nicely. (this is a bigger issue as the dotted lines appear in many zoom icons which makes sense based on what apps they where made for but as those icons are often fairly wide in range they tend to be used badly and looking at replacing zoom might be worth while) I think color selector (the drop) should stay as that is used in a lot of different apps and work as intended there. It's a skip and a jump for new users who use Kolourpaint perhaps but not that complex -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399665] Breeze drawing tool tool icons need improvement
https://bugs.kde.org/show_bug.cgi?id=399665 Jens Reuterberg changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #2 from Jens Reuterberg --- I think improving the icons as is for Kolorpaint might be a good thing, removing an entire icon language (with clear and well known benefits) would be bad (for a wealth of other applications). Perhaps check out how apps like Inkscape work with Breeze (which it does expertly) and mimic that for Kolorpaint would be a way forward? Just adding colour in this scenario would be taking the easiest path forward and instead of improving something - wrecking it. So I suggest looking at improvements for those icons - and if that is impossible - accept that we will destroy a complete icon language for one app. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399050] Signature spoofing in PGP encrypted email (ID layer)
https://bugs.kde.org/show_bug.cgi?id=399050 --- Comment #9 from Jens Mueller --- Hi Jan, > You might see different results from what I see because > different servers parse garbage input in a different way. That's interesting, however I'd not rely on the config of the IMAP server for end-to-end security (which PGP is assumed to provide). > As a side note, I do not think that *that* would be a > security issue because e-mail headers are forgeable Absolutely, but a lot of users assume that PGP can exactly counter the problem of forgeable email headers using digital signatures (even though a binding between the From:/Sender: address and the email address in the matching PGP has never been defined in the OpenPGP standard). > Trojita always unconditionally shows both Sender and > From fields if they are present. Yes, but only the display name, not the actual email address. For me, the testcases look as shown in attachment 115532. > Do you see a security problem in here? Depends on your point of view. I would not say those issues are super-bad. However, if we really want to rely on PGP for critical tasks I'd say there is still room for improvement in the UI of mail clients. Assume you receive a signed email from you employer with testcase #2 which includes a task-to-be-done-immediately (e.g. "The President: >>launch missiles<<") -- you may be stressed and not look into the signature details and just do it... > What we could do is to always show the e-mail address > which was matched. Would that make sense from your > point of view? Yes, I think it's a good practice to explicitly show the email address of the matching key (if available) and therefore answer the signed-by-whom question (or at least deligate it back to the user). Greetings Jens -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399050] Signature spoofing in PGP encrypted email (ID layer)
https://bugs.kde.org/show_bug.cgi?id=399050 --- Comment #8 from Jens Mueller --- Created attachment 115532 --> https://bugs.kde.org/attachment.cgi?id=115532=edit Screenshots of testcases -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399292] Video file datetime not shown correctly after editing
https://bugs.kde.org/show_bug.cgi?id=399292 --- Comment #4 from Jens --- The datetime wasn't correct. I edited it using the right sidebar (Descriptions tab) and it was corrected in thumbnail view, but not in the geolocation editor tabular view. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399305] When browsing images in preview mode, videos are often not shown (black preview area), only sound is heard
https://bugs.kde.org/show_bug.cgi?id=399305 --- Comment #3 from Jens --- So what can we do about it? Move the bug to QtAV? It is quite annoying and a bad user experience ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399305] New: When browsing images in preview mode, videos are often not shown (black preview area), only sound is heard
https://bugs.kde.org/show_bug.cgi?id=399305 Bug ID: 399305 Summary: When browsing images in preview mode, videos are often not shown (black preview area), only sound is heard Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Preview-Video Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. open Digikam with album where there are multiple (mp4) video files 2. Enter preview mode with the thumbnail dock at the top 3. browse through images and videos OBSERVED RESULT When a video file is reached, it should play back (or at least optionally play back.) EXPECTED RESULT Sometimes, videos are played, but no video is shown. If I then go to the next image, view a few images, and then go back, the video plays normally. Maybe there is a race condition with multiple consecutive video files? This happened with Digikam 4.x, 5.x and 6.0-beta, under Ubuntu 14.04 (Unity), 16.04 (Unity) and 18.04 (KDE), on an Intel Haswell i915 graphics system. Maybe it also depends on the hardware (driver). Currently, using Kubuntu 18.04 with KDE 5.12 and Digikam 6.0-beta 20180926. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399292] Video file datetime not shown correctly after editing
https://bugs.kde.org/show_bug.cgi?id=399292 --- Comment #2 from Jens --- Yes, I am using sidecars. And I have switched off updating the file metadata, I want my images to stay pristine. -- You are receiving this mail because: You are watching all bug changes.
