[kmymoney] [Bug 415519] AppImage - aqbanking Update (All) Accounts not working
https://bugs.kde.org/show_bug.cgi?id=415519 Thomas Baumgart changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #5 from Thomas Baumgart --- That is really weird as things work for me just perfectly. Do you see any output on the console when running the update after starting the AppImage with the following command: AQHBCI_LOGLEVEL=debug ./KMyMoney-5.0.7-3227834-x86_64.AppImage -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415571] New: Mouse freezes and Kwin crashes while using Firefox
https://bugs.kde.org/show_bug.cgi?id=415571 Bug ID: 415571 Summary: Mouse freezes and Kwin crashes while using Firefox Product: kwin Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: goyoregal...@gmail.com Target Milestone: --- Application: kwin_x11 (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.0.0-1030-oem-osp1 x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I have been working in a embedded Jupyter notebook into a Mozilla Firefox Tab. - Unusual behavior I noticed: Mouse Freezes, I go to a terminal pressing ctrl+alt+F2 there weren't any error messages. I came back to the graphical interface and press left button and simultaneously, the mouse begin to work and there's a notification about kwin crash. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f47ac741d00 (LWP 2976))] Thread 7 (Thread 0x7f476f817700 (LWP 19874)): #0 0x7f47ac0a8cf6 in __GI_ppoll (fds=0x7f477c030708, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f47a95e58a1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f47a95e7038 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f47a958a06a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f47a93a53aa in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f47a3a02815 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f47a93a6b52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f47a4ff66db in start_thread (arg=0x7f476f817700) at pthread_create.c:463 #8 0x7f47ac0b588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f4775305700 (LWP 4108)): #0 0x7f47a4ffc9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55af45648bb4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f47a4ffc9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55af45648b60, cond=0x55af45648b88) at pthread_cond_wait.c:502 #2 0x7f47a4ffc9f3 in __pthread_cond_wait (cond=0x55af45648b88, mutex=0x55af45648b60) at pthread_cond_wait.c:655 #3 0x7f47a93adaeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f47a93addf9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f47a4186ec8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f47a41872fa in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f47a93a6b52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f47a4ff66db in start_thread (arg=0x7f4775305700) at pthread_create.c:463 #9 0x7f47ac0b588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f478b3dd700 (LWP 3911)): #0 0x7f47ac0a8cf6 in __GI_ppoll (fds=0x7f478000f8d8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f47a95e58a1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f47a95e7038 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f47a958a06a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f47a93a53aa in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f47a93a6b52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f47a4ff66db in start_thread (arg=0x7f478b3dd700) at pthread_create.c:463 #7 0x7f47ac0b588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f47890ce700 (LWP 3008)): #0 0x7f47a4ffc9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f47a87f6fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f47a4ffc9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f47a87f6f68, cond=0x7f47a87f6f90) at pthread_cond_wait.c:502 #2 0x7f47a4ffc9f3 in __pthread_cond_wait (cond=0x7f47a87f6f90, mutex=0x7f47a87f6f68) at pthread_cond_wait.c:655 #3 0x7f47a8501874 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f47a85018b9 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f47a4ff66db in start_thread (arg=0x7f47890ce700) at pthread_create.c:463 #6 0x7f47ac0b588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f478a538700 (LWP 3005)): #0
[frameworks-knewstuff] [Bug 415541] i18n: downloadNewWhat text used in different contexts, cannot be translated correctly
https://bugs.kde.org/show_bug.cgi?id=415541 --- Comment #3 from Victor Ryzhykh --- Created attachment 124721 --> https://bugs.kde.org/attachment.cgi?id=124721=edit Fix translations (In reply to Victor Ryzhykh from comment #2) > Created attachment 124720 [details] > plasma-desktop-5.17.80-tr.patch > > And package plasma-desktop change with this patch > plasma-desktop-5.17.80-tr.patch, > then the translation starts to display correctly on all locales. I will attach a picture in Russian. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 415541] i18n: downloadNewWhat text used in different contexts, cannot be translated correctly
https://bugs.kde.org/show_bug.cgi?id=415541 --- Comment #2 from Victor Ryzhykh --- Created attachment 124720 --> https://bugs.kde.org/attachment.cgi?id=124720=edit plasma-desktop-5.17.80-tr.patch And package plasma-desktop change with this patch plasma-desktop-5.17.80-tr.patch, then the translation starts to display correctly on all locales. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 415541] i18n: downloadNewWhat text used in different contexts, cannot be translated correctly
https://bugs.kde.org/show_bug.cgi?id=415541 Victor Ryzhykh changed: What|Removed |Added CC||victorr2...@yandex.ru --- Comment #1 from Victor Ryzhykh --- Created attachment 124719 --> https://bugs.kde.org/attachment.cgi?id=124719=edit knewstuff-5.65.0-tr.patch If knewstuff is changed using this patch knewstuff-5.65.0-tr.patch, -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 414248] Kmines sometimes doesn't record new highscore
https://bugs.kde.org/show_bug.cgi?id=414248 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369158] Breeze sddm theme broken on dual monitor setup (no cursor)
https://bugs.kde.org/show_bug.cgi?id=369158 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411682] Copy-paste doesn't work in firefox
https://bugs.kde.org/show_bug.cgi?id=411682 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 413497] Parallel font size in main editor
https://bugs.kde.org/show_bug.cgi?id=413497 Simon Depiets changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/lok ||alize/84bc05739235637f58a52 ||e3f555209786aec9bd9 --- Comment #1 from Simon Depiets --- Git commit 84bc05739235637f58a52e3f555209786aec9bd9 by Simon Depiets. Committed on 25/12/2019 at 12:20. Pushed by sdepiets into branch 'master'. Link zoom in source and target panels Linking the zoom in source and target panels by setting the same fontPointSize. M +2-0src/editorview.cpp M +18 -0src/xlifftextedit.cpp M +2-0src/xlifftextedit.h https://commits.kde.org/lokalize/84bc05739235637f58a52e3f555209786aec9bd9 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415570] Print > Selection omits some text
https://bugs.kde.org/show_bug.cgi?id=415570 Nicolás Adamo changed: What|Removed |Added CC||nicoad...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415570] New: Print > Selection omits some text
https://bugs.kde.org/show_bug.cgi?id=415570 Bug ID: 415570 Summary: Print > Selection omits some text Product: kate Version: 19.12.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: nicoad...@gmail.com Target Milestone: --- Created attachment 124718 --> https://bugs.kde.org/attachment.cgi?id=124718=edit The result of the bug I'm trying to describe. SUMMARY The Print menu, with option "Selection" triggers the printer, but one line in the paper is trimmed. It's wired. No special characters other than " (quotes), Spanish accents like 'ú' and one '!'. STEPS TO REPRODUCE 1. Open a text file in Kate with final line as the following: -Lo anterior va de la mano con el comentario de Nicole Jeldres "Eres súper exigente contigo mismo, y con los demás!". 2. Select the final line and then File > Print or Ctrl+P. 3. Selection. 4. Print button. OBSERVED RESULT It's on a paper. I could show some photo if you require, but the attached PDF was generated with the same result. EXPECTED RESULT The full line printed. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 415569] New: calendar manager unreadable
https://bugs.kde.org/show_bug.cgi?id=415569 Bug ID: 415569 Summary: calendar manager unreadable Product: korganizer Version: 5.13.40 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: otherviews Assignee: kdepim-b...@kde.org Reporter: tr...@psha.us Target Milestone: --- SUMMARY Calendar manager list all crammed up into one text line unusable STEPS TO REPRODUCE 1.Settings> Side Bar> Show Calendar Manager 2.Check the box 3. OBSERVED RESULT All listed items jammed up into top, no way of adjusting font sizes, spacing between listed items, cant manage the calendar manager view, unusable. EXPECTED RESULT The one shown in the picture SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora-30 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415568] New: The "Always use empty screen gap..." option does not work
https://bugs.kde.org/show_bug.cgi?id=415568 Bug ID: 415568 Summary: The "Always use empty screen gap..." option does not work Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tr...@yandex.com Target Milestone: --- Just tried the new Floating dock feature, when I try checking/unchecking that option in the Behavior > Item section, nothing changes, the gap is always used by items. (e.g. clicking on the gap is like clicking on items) -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 412836] Checkboxes under "Searchable column" act like radiobuttons
https://bugs.kde.org/show_bug.cgi?id=412836 Simon Depiets changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413021] systemtray doesn't show battery widget
https://bugs.kde.org/show_bug.cgi?id=413021 prettyvani...@posteo.at changed: What|Removed |Added Version|5.17.0 |5.17.4 CC||prettyvani...@posteo.at -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 145181] Cannot define a system boundary for an use case
https://bugs.kde.org/show_bug.cgi?id=145181 Ralf Habacker changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 145181] Cannot define a system boundary for an use case
https://bugs.kde.org/show_bug.cgi?id=145181 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #5 from Ralf Habacker --- https://sparxsystems.com/enterprise_architect_user_guide/14.0/model_domains/systemboundary.html mentions a definition of a system boundary. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415460] JFIF files have APP0 marker after SOI where there should be APP1
https://bugs.kde.org/show_bug.cgi?id=415460 --- Comment #11 from Anselm Lingnau --- That's nice but is not what the current Exif standard document says. As long as we don't have an actual standards-level document that says that the APP1 section doesn't have to come immediately after the SOI, the libjpeg-turbo people are unlikely to budge (and they're technically correct, which as we all know is the best kind of correct). They are opposed to the “robustness principle”, which the idea of deliberately writing a file that doesn't conform to the standard in order to accommodate “old JFIF readers” is all about, and it is not an unreasonable position to take if you're a purist rather than a pragmatist, and believe that bugs should be fixed in the software that actually has the bug, rather than worked around elsewhere. In any case you should fix the broken Exif orientation marker in the exported attachment image files, because that's wrong no matter what the situation is about APP0 and APP1, and it bites especially those people with software that DOES look for APP1 in places other than immediately after the SOI. Getting that right would solve much of the original problem already. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 143634] parameter datatypes not updating in class & sequence diagram
https://bugs.kde.org/show_bug.cgi?id=143634 Ralf Habacker changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Ralf Habacker --- The version in which this behavior was fixed is currently unknown. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 143634] parameter datatypes not updating in class & sequence diagram
https://bugs.kde.org/show_bug.cgi?id=143634 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #3 from Ralf Habacker --- Created attachment 124717 --> https://bugs.kde.org/attachment.cgi?id=124717=edit test case The mentioned issue could not be reproduced with the recent version. A method located in a base class is not copied into a derived class. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 118906] aligning objects in a triangle results in overlapping actors
https://bugs.kde.org/show_bug.cgi?id=118906 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Ralf Habacker --- The function "Align vertical middle" is only useful for widgets in a row that are to be aligned vertically. A better-aligned alternative is to use the "Apply Layout" function from the use case diagram context menu. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415546] Cannot scroll horizontally with mousewheel
https://bugs.kde.org/show_bug.cgi?id=415546 --- Comment #7 from Fabian Vogt --- I can confirm that it's broken with Dolphin 19.12 + Qt 5.14.0, but works with Dolphin 19.12 + Qt 5.13.1. So likely a change/bug in Qt indeed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402322] During face detection, the "People" / "Unconfirmed" (or "Unknown") tab content keeps jumping around
https://bugs.kde.org/show_bug.cgi?id=402322 --- Comment #4 from MarcP --- I have narrowed it down a bit. When tagging people in the Unknown category, it is fine unless digikam is actively writing metadata to files. For instance, when you select a few faces and enter their name, it will write the changes to these files, which takes a few seconds. If meanwhile you try to select and write someone else's name, digikam will move the selected face around and it will lose the focus, so you cannot finish entering its name. But it's much more pronounced while face recognition is in process. Either in the Unknown or Unconfirmed categories, it is impossible to type any name. Faces flicker and they are selected and deselected very fast (several times a second). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 415567] New: "Could not find the program" dialog when program is found but malformed
https://bugs.kde.org/show_bug.cgi?id=415567 Bug ID: 415567 Summary: "Could not find the program" dialog when program is found but malformed Product: frameworks-kio Version: 5.65.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: fa...@kde.org Reporter: agram...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY I discovered this when one of my programs that I have a shortcut to in Kickoff needed to be rebuilt to link with a new version of a library. Running the executable directly resulted in an error code of 127: error while loading shared libraries: libMagickWand-7.Q16HDRI.so.6: cannot open shared object file: No such file or directory When attempting to launch in Kickoff I got a popup with the message "Could not find the program", even though that wasn't the error. Other variants I tried were to replace the executable with an empty file and to remove the executable bit from the executable. STEPS TO REPRODUCE 1. Create a shortcut to an executable in Kickoff (or Krunner, etc.) 2. Make the executable somehow throw an error instead of loading. For example, use `sudo chmod -x `. 3. Try to launch the program through the shortcut. OBSERVED RESULT "Could not find the program" dialog pops up. EXPECTED RESULT A pop up dialog that states the actual reason why the program did not launch. SOFTWARE VERSIONS KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION The message is produced in kio/kio/krun.cpp in KProcessRunner::slotProcessExited. It would be nice if the exact error message/code was passed through to give the user the precise information. Perhaps it could be hidden, but expandable in an "Additional Information" field? -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 116113] change max line length to 75 or 80 chars in predefined headings
https://bugs.kde.org/show_bug.cgi?id=116113 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #2 from Ralf Habacker --- A tab could be added to the code generator options dialog with post-processing option. This could contain an input field and a browse button to specify an external script which is called after the code export and receives the generated files via standard input. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 116113] change max line length to 75 or 80 chars in predefined headings
https://bugs.kde.org/show_bug.cgi?id=116113 Ralf Habacker changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Target Milestone|--- |2.31 (KDE Applications ||20.04) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415566] New: Use existing face rectangles to improve recognition
https://bugs.kde.org/show_bug.cgi?id=415566 Bug ID: 415566 Summary: Use existing face rectangles to improve recognition Product: digikam Version: 7.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY I have been testing the new face recognition capabilities from the last 7.0 beta. I know that a few faces need to be manually identified for each person before the recognition can work, but I have noticed that only faces which have manually identified after the installation of the 7.0.0 version are used for recognition. All other existing people are ignored. It would be optimal if the algorithm would also used pre-tagged face rectangles to train each person's dataset. That way, it would benefit from faces tagged in previous digikam versions and faces tagged in other picture software. STEPS TO REPRODUCE 1. Start from a digikam library where people are already tagged with faces. 2. Detect new faces. Make sure it detects faces of already existing people. 3. Recognize new faces. OBSERVED RESULT No faces could be recognized. EXPECTED RESULT Existing face rectangles should be used for training face recognition. SOFTWARE/OS VERSIONS Ubuntu 18.04LTS with Digikam 7.0.0Beta1 (appimage) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415566] Use existing face rectangles to improve recognition
https://bugs.kde.org/show_bug.cgi?id=415566 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 359509] Umbrello Theme when popups or menus are open, white background and white font color.
https://bugs.kde.org/show_bug.cgi?id=359509 Ralf Habacker changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415411] No support for check forms with split protocol
https://bugs.kde.org/show_bug.cgi?id=415411 Ralf Habacker changed: What|Removed |Added Version Fixed In|4.8.5,5.0.7 |4.8.5,5.0.8 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 413555] Reconciliation of Credit Card
https://bugs.kde.org/show_bug.cgi?id=413555 Ralf Habacker changed: What|Removed |Added Version Fixed In|4.8.5 |4.8.5,5.0.8 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP transfer corrupts all files
https://bugs.kde.org/show_bug.cgi?id=405847 --- Comment #47 from Yuriy Vidineev --- Looks like it depends on Android version. I've just checked on an older phone and it works like a charm! Works: Galaxy Note 3, Android 5.0 KDE Connect 1.13.5 from Google Play KDE Connect 1.4-0xneon+18.04+bionic+build23 on laptop with KDE Neon Doesn't work Galaxy Note 10, Android 9 KDE Connect 1.13.5 from F-Droid KDE Connect 1.4-0xneon+18.04+bionic+build23 on laptop with KDE Neon -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415317] click on an entry of the context menu of systray icons has no effect on Wayland
https://bugs.kde.org/show_bug.cgi?id=415317
--- Comment #5 from David Edmundson ---
Found it!
>void XdgShellClient::handleWindowGeometryChanged(const QRect )
{
qDebug() << this << "handleWindowGeometryChanged" << windowGeometry;
const QRect boundingRect = subSurfaceTreeRect(surface());
m_windowGeometry = windowGeometry & boundingRect; <--- HERE!!!
m_hasWindowGeometry = true;
Bounding rect is null as we don't have a surface at the time of doing initial
placement. We just have a pending initial size.
This gets us in a messed up state, where we think the window is 1x1 with just a
really massive giant animating frame.
Also the cause of the weird "ghost" notifications that you can't interact with.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 --- Comment #6 from Maik Qualmann --- Are you really using the latest Windows version of files.kde.org? With all Windows versions before, the DNN face detection did not work. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 --- Comment #5 from Alexandre Belz --- (i enabled the checked box that erases learning database, just above the selection of the deep learning algorith. was it a mistake ?) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 --- Comment #4 from Alexandre Belz --- Strange... please can you point me to the right procedure to test successfully deep learning face recog nition ? i may have my digikam misconfigured... or miss a step ! Is the DNN pre-learnt ? or is it blank and i should first manually add some people before it get used to detect other peoples ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415491] Unable to create a keyframe on existing layer
https://bugs.kde.org/show_bug.cgi?id=415491 Ahab Greybeard changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- You need to provide more information and a detailed description of what you do and what happens. Which version of krita are you using? If you 'draw anything' in a layer, then that layer is obviously the selected layer. If a layer is selected then it will be in the Timeline docker. So, what do you mean by 'Open the layer in the timeline'? Where exactly do you right-click in the timeline? Which layer line? Which frame number? If you right-click in frame-n of any layer in the timeline and select 'Create Blank Keyframe', it should indicate this by the timeline frame-n square having a hollow blue rectangle around it and the canvas will be blank (a blank keyframe) and the layer artwork will be pulled into frame-0. What do you mean by 'literally nothing'? What changes (if any) do you see? If you want to make existing (non animated) layer artwork into frame-0 of an animated layer, you can do 'Create Duplicate Frame' in frame-0 of the timeline for that layer, which will make it an animated layer -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415565] Show face as icon for each person in the People panel.
https://bugs.kde.org/show_bug.cgi?id=415565 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415565] New: Show face as icon for each person in the People panel.
https://bugs.kde.org/show_bug.cgi?id=415565 Bug ID: 415565 Summary: Show face as icon for each person in the People panel. Product: digikam Version: 7.0.0 Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- Created attachment 124716 --> https://bugs.kde.org/attachment.cgi?id=124716=edit Faces as icons for people panel, mockup. SUMMARY I am not sure if I already submitted a wishlist for this, but I can't find anything similar in the bugtracker now. It was discussed during the gsoc2019, but it was not implemented due to lack of time. Basically, the Person list is just a text list. This is not optimal if we consider we are dealing with faces. It should be more visual. What I propose is to automatically display that person's face in the list, and making the icon size a bit larger (hardcode it to 64), separately from the rest of the panels with tree-views. It would look like the mockup I have attached. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415559] Standard Face Detection does not work on LowRes pictures
https://bugs.kde.org/show_bug.cgi?id=415559 --- Comment #3 from Alexandre Belz --- Hi Maik and Gilles, do you mean that Face detection (only placing rectangle on faces) is now also Neuronal in digikam ? i'm fine with that, it's just to understand... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415559] Standard Face Detection does not work on LowRes pictures
https://bugs.kde.org/show_bug.cgi?id=415559 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- Yes, i thinking about that too. Current model must still the default one. Large model must be optional. Downloader can be used also later for other models, as to detect/recognize animals, plans, monuments. In fact the neural network code is ready for that. The missing is data, not code. I'm not sure if file.kde.org is the right place. Perhaps digiKam.org will be better... Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415560] No default selection for Scan Collection
https://bugs.kde.org/show_bug.cgi?id=415560 --- Comment #2 from Alexandre Belz --- Thank you Maik ! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 380336] Suggested improvements of Face Tagging
https://bugs.kde.org/show_bug.cgi?id=380336 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 415564] New: Default and used audio device switches automatically when the display configuration changes
https://bugs.kde.org/show_bug.cgi?id=415564 Bug ID: 415564 Summary: Default and used audio device switches automatically when the display configuration changes Product: plasma-pa Version: 5.17.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: minecraftle...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY (First : i hope this is the right section i'm not really sure) After switching to Kubuntu 19.10 i have the issue that when, most of the time, something get changed in the display configuration the default and used audio device changes from anything to the HDMI 2 output. I have my monitors connected threw display port and DVI. I tried disabling the HDMI output completely in the system options but it get turned on again everytime. This hhappens even if i only switch the refreshrate of one monitor. I have two monitors connected, one with Display Port that runs on 1440p and 144hz and one with DVI that runs on 1600 x 900 and 60hz. I have a NVidia GTX 1070ti with the proprietary nvidia drivers, version 440.44 STEPS TO REPRODUCE Change the some display setting like refresh rate or resolution or turn one monitor of threw software OBSERVED RESULT Default and currently used sound device changes to HDMI 2, even when it's disabled EXPECTED RESULT Sound should not be affected SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.3.0-24-generic (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402322] During face detection, the "People" / "Unconfirmed" (or "Unknown") tab content keeps jumping around
https://bugs.kde.org/show_bug.cgi?id=402322 caulier.gil...@gmail.com changed: What|Removed |Added Version|6.0.0 |7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395236] Allow face detection for selected images / albums and automatically during import
https://bugs.kde.org/show_bug.cgi?id=395236 --- Comment #7 from MarcP --- I think that this wish is specially relevant now, since the options to detect and to recognize faces cannot be run simultaneously. Detecting faces as pictures are imported would really simplify the process (the user would only need to recognize them). Moreover, face detection seems to be quite fast, so I guess it wouldn't add much time to the initial scan. Although I would made that feature optional, as some people may have no interest in faces (e.g. someone focused on nature photography). Maybe an option in the settings to enable/disable it? Also during the initial configuration wizard that appears after installing digikam. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415562] About screen "Getting Started" links to 404 page not found
https://bugs.kde.org/show_bug.cgi?id=415562 Ahab Greybeard changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- Version 4.0.1 is very old and the link it gives is the old (now invalid) manual location. It would be a good idea to update your repository or get the latest 4.2.8 appimage from the krita download site. That link is now: https://docs.krita.org/en/user_manual/getting_started.html?pk_campaign=startup-sceen_kwd=getting-started and it works. Please reply to confirm this and that it works for you and set the Status to Resolved Not a bug if it does. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402322] During face detection, the "People" / "Unconfirmed" (or "Unknown") tab content keeps jumping around
https://bugs.kde.org/show_bug.cgi?id=402322 --- Comment #3 from MarcP --- I can confirm this bug is still present in 7.0.0beta1. While digikam is working detecting or recognising faces, the face list moves constantly (I guess faces are being added or removed), and it is impossible to type a name, since the text box loses focus every second or so. This sometimes leads to accidentally tagging the wrong face. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402322] During face detection, the "People" / "Unconfirmed" (or "Unknown") tab content keeps jumping around
https://bugs.kde.org/show_bug.cgi?id=402322 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415563] New: SMS notifications persist despite countdown
https://bugs.kde.org/show_bug.cgi?id=415563 Bug ID: 415563 Summary: SMS notifications persist despite countdown Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: dja...@gmail.com Target Milestone: --- SUMMARY When receiving an SMS, a popup notification appears on the desktop and does not hide after the notification countdown is over STEPS TO REPRODUCE 1. Connect your phone with kde connect sms notifications enabled and receive an SMS. 2. A popup appears with the content of the SMS 3. Despite setting the 'hide notification after' 3seconds (in my case)in kde settings, the SMS popup persist and can only be closed by clicking the cross icon on the popup OBSERVED RESULT Sms notifications do not respect kde settings. EXPECTED RESULT Popup should auto-disappear after the number of seconds set in system settings for hiding notifications SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 19.10 (available in About System) KDE Plasma Version: 5.12 KDE Frameworks Version: Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404167] improve confirmation process
https://bugs.kde.org/show_bug.cgi?id=404167 --- Comment #2 from MarcP --- The process is much easier now that unconfirmed faces are surrounded with a green frame. However, the unconfirmed faces still use the sort order like any other album, so they usually appear in between already confirmed faces, and sometimes they are not easy to find if a person already has thousands of confirmed faces. It would still be useful to have a button to toggle between all faces and just unconfirmed faces, making the confirmation process easier. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415559] Standard Face Detection does not work on LowRes pictures
https://bugs.kde.org/show_bug.cgi?id=415559 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- We have 2 pre-learned DNN data models. The simple model we are using at the moment cannot find faces in this image. The yolo DNN model would find all faces. However, digiKam would grow by almost 300MB. In any case, it has nothing to do with the image size. Gilles, I would suggest that we program a downloader for this model in digiKam and download it from files.kde.org/digikam if necessary. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- I tested here under Linux, no problem : faces are detected properly. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415562] New: About screen "Getting Started" links to 404 page not found
https://bugs.kde.org/show_bug.cgi?id=415562 Bug ID: 415562 Summary: About screen "Getting Started" links to 404 page not found Product: krita Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tessmaste...@yahoo.com Target Milestone: --- VERSION 4.0.1 SUMMARY Help -> About Krita -> Getting Started link opens https://docs.krita.org/en/Category:Getting_Started which shows "File Not Found (404)" STEPS TO REPRODUCE 1. Install krita on Ubuntu 18.04 via apt: `sudo apt install krita` 2. Click on "Getting Started" from the welcome screen, or Help -> About Krita 3. In Firefox web browser, https://docs.krita.org/en/Category:Getting_Started shows File Not Found (404) EXPECTED RESULT Expected a web page with instructions for getting started. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- The faces are detected on both images, even with the Windows version. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415560] No default selection for Scan Collection
https://bugs.kde.org/show_bug.cgi?id=415560 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||7.0.0 Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/a6103e38cb49 ||f4792f984e3e376a8c6afa760a2 ||c --- Comment #1 from Maik Qualmann --- Git commit a6103e38cb49f4792f984e3e376a8c6afa760a2c by Maik Qualmann. Committed on 25/12/2019 at 21:00. Pushed by mqualmann into branch 'master'. set detection button if we have old config FIXED-IN: 7.0.0 M +2-1core/utilities/facemanagement/widgets/facescandialog.cpp https://invent.kde.org/kde/digikam/commit/a6103e38cb49f4792f984e3e376a8c6afa760a2c -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 382365] kdeconnect does not connect automatically
https://bugs.kde.org/show_bug.cgi?id=382365 Pivert changed: What|Removed |Added CC||k...@pivert.org --- Comment #10 from Pivert --- Same problem on Android 9, one OnePlus. This Kdeconnect stops working some minutes after the phone locks... I removed any battery optimisation for the app, but this does not help. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411711] Curve Module : Drops do not behave correctly
https://bugs.kde.org/show_bug.cgi?id=411711 --- Comment #14 from Alexandre Belz --- Hi, please can you update me on this one ? And in "Luminosity" graph, the grey drop should affect only the luminance, without changing the chrominance ! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 --- Comment #1 from Alexandre Belz --- Created attachment 124715 --> https://bugs.kde.org/attachment.cgi?id=124715=edit Test File 02 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 Alexandre Belz changed: What|Removed |Added OS|Linux |MS Windows Platform|Other |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415561] New: Deep Learning face recognition leads to no result
https://bugs.kde.org/show_bug.cgi?id=415561 Bug ID: 415561 Summary: Deep Learning face recognition leads to no result Product: digikam Version: 7.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: alexandre.b...@live.fr Target Milestone: --- Created attachment 124714 --> https://bugs.kde.org/attachment.cgi?id=124714=edit Test File 01 SUMMARY Attached pictures leads to no a Face detection with the standard module, but to no detection at all with the DeepLearning algorithm. STEPS TO REPRODUCE 1. Open the attached pictures, and make it the only collection. 2. Scan the whole collection, with Deep Learning 3. OBSERVED RESULT No face detected EXPECTED RESULT Scan Collection + Deep Learning should detect and suggest people group/faces SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411970] Extract and save zone not working
https://bugs.kde.org/show_bug.cgi?id=411970
--- Comment #2 from scu...@yahoo.de ---
(In reply to scubbx from comment #1)
> I also get this error. The language of my OS is "German".
> The reason might be that the decimal separator value for SS used by Kdenlive
> is a comma and not a dot as expected by ffmpeg.
I looked around a bit and found the following in the source:
In the file src/jobs/cutclipjob.cpp the variable "startString" (used for
extraction of the clip) is created by "m_in.seconds()" :
QString startString = locale.toString(m_in.seconds());
The same is true for the "durationString" in src/jobs/cutclipjob.cpp :
QString durationString = locale.toString((m_out - m_in).seconds());
Both of these variables are used to create the FFMPEG call for clipping in the
file src/jobs/cutclipjob.cpp:
QStringList params =
{QStringLiteral("-y"),QStringLiteral("-stats"),QStringLiteral("-i"),m_sourceUrl,QStringLiteral("-v"),QStringLiteral("error"),QStringLiteral("-ss"),startString,
QStringLiteral("-t"), durationString};
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 415560] No default selection for Scan Collection
https://bugs.kde.org/show_bug.cgi?id=415560 Alexandre Belz changed: What|Removed |Added Platform|Other |MS Windows OS|Linux |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415560] New: No default selection for Scan Collection
https://bugs.kde.org/show_bug.cgi?id=415560 Bug ID: 415560 Summary: No default selection for Scan Collection Product: digikam Version: 7.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: alexandre.b...@live.fr Target Milestone: --- Created attachment 124713 --> https://bugs.kde.org/attachment.cgi?id=124713=edit Screen capture of the bug. SUMMARY No default selection for Scan Collection STEPS TO REPRODUCE 1. Open People Windows 2. Click on "Scan collection for faces" 3. Look at the top area of the popup. There are 2 radio buttons ; giving us a choice between "Detect" or "Recognize". OBSERVED RESULT No choice is selected. See attached screen capture. EXPECTED RESULT One choice should be always selected. SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415559] New: Standard Face Detection does not work on LowRes pictures
https://bugs.kde.org/show_bug.cgi?id=415559 Bug ID: 415559 Summary: Standard Face Detection does not work on LowRes pictures Product: digikam Version: 7.0.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: alexandre.b...@live.fr Target Milestone: --- Created attachment 124712 --> https://bugs.kde.org/attachment.cgi?id=124712=edit Test JPG file SUMMARY Standard Face Detection does not work on LowRes pictures STEPS TO REPRODUCE 1. Open picture enclosed 2. Right click on it, Scan for faces 3. OBSERVED RESULT There is no face detected. EXPECTED RESULT All people should be detected SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411970] Extract and save zone not working
https://bugs.kde.org/show_bug.cgi?id=411970 scu...@yahoo.de changed: What|Removed |Added CC||scu...@yahoo.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from scu...@yahoo.de --- I also get this error. The language of my OS is "German". The reason might be that the decimal separator value for SS used by Kdenlive is a comma and not a dot as expected by ffmpeg. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415558] New: Used effects that appeared on the result screen, but after rendered the clip was in black and grey
https://bugs.kde.org/show_bug.cgi?id=415558 Bug ID: 415558 Summary: Used effects that appeared on the result screen, but after rendered the clip was in black and grey Product: kdenlive Version: 19.12.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: lil.py.soundcl...@gmail.com Target Milestone: --- SUMMARY After adding saturation and contraste fliters to a clip, the preview window applies the correct settings. After being rendered, the clip was a plain neutral grey, as if saturation and contrast were both set to 0. STEPS TO REPRODUCE 1.Add a saturation filter set to 175, and contrast to 390 2.The Project monitor previews the effects correctly 3.Render the clips OBSERVED RESULT The rendered clip is plain grey, but the audio is ok. EXPECTED RESULT The clip with the right saturation and contrast level. SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404167] improve confirmation process
https://bugs.kde.org/show_bug.cgi?id=404167 Niyaz changed: What|Removed |Added CC|niyaz.batyrs...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415460] JFIF files have APP0 marker after SOI where there should be APP1
https://bugs.kde.org/show_bug.cgi?id=415460
--- Comment #10 from Maik Qualmann ---
I just stumbled across this interesting site because Exiv2 referred to it. For
me, jpegexiforient is faulty because it only wants to process APP1.
From: https://www.codeproject.com/Articles/43665/ExifLibrary-for-NET
---
JPEG ("Joint Photographic Experts Group") is the committee that created the
JPEG standard. It is also the name of the compression method (the codec)
defined by the JPEG committee. JPEG is not a file format. (Actually, there is a
"pure" file format – JPEG Interchange Format, JIF – described in the original
JPEG specification. But it is rarely used.) The most widely used file formats
containing JPEG compression are JFIF (JPEG File Interchange Format) and Exif
(Exchangeable Image File Format). In everyday use, JPEG usually means a JFIF or
an Exif image file.
The difference between JFIF and Exif file formats is that JFIF files use
Application Marker 0 (APP0) sections to store metadata, whereas Exif files use
Application Marker 1 (APP1) sections. The two file formats are incompatible
because they both specify that their sections (APP0 and APP1) must be the first
in the image file. In practice, however, Exif files usually include an APP0
section at the start of the image file. This does not comply with the Exif
standard, but allows old JFIF readers to read the image file.
A modern JFIF or Exif reader must not assume a particular order for APPn
sections. It should read the entire file and process APPn sections as it
encounters them. Additionally, APPn sections might not be unique. For example,
there might be more than one APP1 section in a JPEG/Exif file.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 415546] Cannot scroll horizontally with mousewheel
https://bugs.kde.org/show_bug.cgi?id=415546 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- CC||aro...@archlinux.org, ||fab...@ritter-vogt.de --- Comment #6 from Nate Graham --- Weird, this works fine for me when using Compact mode with Dolphin from 19.12 or git master, with Qt 5.13.1. A regular scroll goes horizontally without needing to hold down the Alt key. I wonder if this is a Qt 5.14 regression. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 415537] Syntax highlighter fails on C++17 if-statement with initializer
https://bugs.kde.org/show_bug.cgi?id=415537
--- Comment #2 from Matt Whitlock ---
Analogous concerns apply for switch-statement with initializer.
/* BEGIN example2.cpp */
#include
#include
#include
unsigned parse_uint_clamp(const char *begin, const char *end) {
unsigned v;
switch (auto [ptr, ec] = std::from_chars(begin, end, v); ec) { // broken
case std::errc { }:
if (ptr != end) { // broken
return 0;
}
return v;
case std::errc::result_out_of_range:
return std::numeric_limits::max();
default:
throw std::system_error(std::make_error_code(ec)); // broken
}
}
/* END example2.cpp */
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 415546] Cannot scroll horizontally with mousewheel
https://bugs.kde.org/show_bug.cgi?id=415546 --- Comment #5 from Martin Droessler --- Compact view mode in the main view - just as the issue opener described. In the other view modes, the content is aligned in a downward fashion, so horizontal scrolling is not required. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392008] Inconsistent behavior of "People" Tag
https://bugs.kde.org/show_bug.cgi?id=392008 --- Comment #8 from caulier.gil...@gmail.com --- Maik, Did you try the Marc photo shared in comment #6 Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388649] Face tag rectangle cursor sometimes disappear
https://bugs.kde.org/show_bug.cgi?id=388649 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from caulier.gil...@gmail.com --- Using digiKam 7.0.0-beta1, this problem is not reproducible here. I close this file now. Don't hesitate to re-open if necessary... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 326034] Allow to add "unknown" face tags in Preview mode
https://bugs.kde.org/show_bug.cgi?id=326034 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from caulier.gil...@gmail.com --- Comment #4 from Frank is right and still valid with 7.0.0-beta1. I close this file now. Re-ope it if necessary... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413923] The peoples list shows just one line of height (one name) when expanded for the first time
https://bugs.kde.org/show_bug.cgi?id=413923 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #7 from caulier.gil...@gmail.com --- I cannot reproduce this problem using 7.0.0-beta1. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411732] UI for assigning people tag is very fragile
https://bugs.kde.org/show_bug.cgi?id=411732 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365668] Face tagger allows text input when hovered over, then does crazy stuff
https://bugs.kde.org/show_bug.cgi?id=365668 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||7.0.0 --- Comment #6 from caulier.gil...@gmail.com --- Definitively, this problem is not reproducible with 7.0.0-beta1. I close this file now. Feel free to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401458] Rename file name with recognized faces-tags
https://bugs.kde.org/show_bug.cgi?id=401458 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Summary|Recognized faces to file|Rename file name with |names |recognized faces-tags -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401458] Rename file name with recognized faces-tags
https://bugs.kde.org/show_bug.cgi?id=401458 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |5.9.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411732] UI for assigning people tag is very fragile
https://bugs.kde.org/show_bug.cgi?id=411732 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 --- Comment #4 from caulier.gil...@gmail.com --- Point 12: See the Neural Network example from digiKam 7.0.0-beta1 performing faces recognition with 2 items face-tagged in first. https://i.imgur.com/HHF4T9X.png 1 new item is recognized, name-tagged, highlighted with green frame, and linked in "unconfirmed" virtual tag for confirmation. Recognition work well using Deep Learning and give 97% of true positive results. Look well my comments on the screenshot. Point 13 : Not reproducible here with 7.0.0-beta1 I close this file now. Merry Christmas and Happy new year. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395241] Faces in the "People" panel load slowly, and only when you scroll through them
https://bugs.kde.org/show_bug.cgi?id=395241 caulier.gil...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Version|6.0.0 |7.0.0 --- Comment #4 from caulier.gil...@gmail.com --- This problem is fully reproducible here, and not only under Windows. Amount of people faces detected and not assigned is around 8000 and loading virtual album contents take age... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415476] ctrl+click on canvas doesn't always disable eraser mode
https://bugs.kde.org/show_bug.cgi?id=415476 --- Comment #3 from Rebecca Breu --- I can reproduce this in my compiled-in-docker build on current master. Interestingly enough, while I still didn't get this in the 4.1.7 appimage even once despite trying spending quite some time on it over several sessions, I do get it in my 4.1.7 compiled-in-docker build, albeit a lot less frequently than in more recent versions. So I guess this isn't just a matter of finding a bad commit between 4.1.7 and now, but rather an issue that seems to get more or less exposed depending on various circumstances, and which is hard to quantify, so I gave up on the bisecting idea. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415557] Face detection - Advanced settings : restricted folder scope not taken into account
https://bugs.kde.org/show_bug.cgi?id=415557 --- Comment #1 from Alexandre Belz --- Created attachment 124711 --> https://bugs.kde.org/attachment.cgi?id=124711=edit Files out of scope nevertheless beeing scanned. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415557] New: Face detection - Advanced settings : restricted folder scope not taken into account
https://bugs.kde.org/show_bug.cgi?id=415557 Bug ID: 415557 Summary: Face detection - Advanced settings : restricted folder scope not taken into account Product: digikam Version: 7.0.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: alexandre.b...@live.fr Target Milestone: --- Created attachment 124710 --> https://bugs.kde.org/attachment.cgi?id=124710=edit Settings SUMMARY I'm testing the new 7.0 Deep Learning feature. I can't scan only a portion/folder of my collection. adhoc Setting is not taken into account. STEPS TO REPRODUCE 1. Open digikam with plenty of pictures 2. Go to people / Scan collection for faces / Options 3. in Albums setting tab, disable "Whole Album collection" and select only a small subfolder . See screen capture attached. 4. in Advanced setting tab, enable "Clear an rebuild database" Note : upper choice (detection/recognition) becomes greyed. I don't understand why. 5. Click "Scan" OBSERVED RESULT It takes a long time to scan a small folder with just 3 pictures. Windows Performance manager (HDD tab) confirms that digikam scans ALL pictures in my collections, and not just the subfolder I did select. See screen capture attached. EXPECTED RESULT The Deep Learning face scan should be possible on a subfolder. SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 286452] No way to scan untagged photos for faces, or scan ALL folders
https://bugs.kde.org/show_bug.cgi?id=286452 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #12 from caulier.gil...@gmail.com --- Following the comments #1 and #2 there is no more to do in this file. I close it now. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392016] Confirmed and unconfirmed faces look the same in a person's face list.
https://bugs.kde.org/show_bug.cgi?id=392016 caulier.gil...@gmail.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||7.0.0 --- Comment #4 from caulier.gil...@gmail.com --- See the Neural Network example from digiKam 7.0.0-beta1 performing faces recognition with 2 items face-tagged in first. https://i.imgur.com/HHF4T9X.png 1 new item is recognized, name-tagged, highlighted with green frame, and linked in "unconfirmed" virtual tag for confirmation. Recognition work well using Deep Learning and give 97% of true positive results. Look well my comments on the screenshot: The unconfirmed face has a green frame around thumbnail. I close this file now. Merry Christmas and Happy new year. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399108] Add new "People" panel on the right to see faces in selected picture
https://bugs.kde.org/show_bug.cgi?id=399108 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Feature request: add new|Add new "People" panel on |"People" panel on the right |the right to see faces in |to see faces in selected|selected picture |picture | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392023] Add "Ignored" group of faces
https://bugs.kde.org/show_bug.cgi?id=392023 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Feature request: add|Add "Ignored" group of |"Ignored" group of faces|faces Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407866] Sync People with true Keywords
https://bugs.kde.org/show_bug.cgi?id=407866 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Feature request: sync |Sync People with true |People with true Keywords |Keywords CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382179] Keep in Add a Face Tag mode after adding a face tag
https://bugs.kde.org/show_bug.cgi?id=382179 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Wishlist: Keep in Add a |Keep in Add a Face Tag mode |Face Tag mode after adding |after adding a face tag |a face tag | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384396] Display faces sorted by similarity (pre-grouped) instead of album/time/..
https://bugs.kde.org/show_bug.cgi?id=384396 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Wish: display faces sorted |Display faces sorted by |by similarity (pre-grouped) |similarity (pre-grouped) |instead of album/time/..|instead of album/time/.. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412168] Add feedback after scanning for faces
https://bugs.kde.org/show_bug.cgi?id=412168 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Wishlist: Feedback after|Add feedback after scanning |scanning for faces |for faces CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 338171] When automatic recognition guesses the same name for multiple faces in one picture, assigning a different name deletes all the face boxes except one
https://bugs.kde.org/show_bug.cgi?id=338171 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from caulier.gil...@gmail.com --- I tested with 7.0.-beta1 and Depp Learning face recognition and i connot reproduce the problem here. I close this file now. Don't hesisae to re-open if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 261624] Moving an album from one collection to another doesn't update the source collection
https://bugs.kde.org/show_bug.cgi?id=261624 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Resolution|DUPLICATE |FIXED --- Comment #4 from caulier.gil...@gmail.com --- Not reproducible using digiKam 7.0.0 beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 250418] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=250418 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Resolution|DUPLICATE |FIXED --- Comment #2 from caulier.gil...@gmail.com --- Not reproducible using digiKam 7.0.0 beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 246534] Digikam crashes at every start
https://bugs.kde.org/show_bug.cgi?id=246534 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 CC||caulier.gil...@gmail.com Resolution|DUPLICATE |FIXED --- Comment #2 from caulier.gil...@gmail.com --- Not reproducible using digiKam 7.0.0 beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 242818] digikam crash at startup
https://bugs.kde.org/show_bug.cgi?id=242818 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Resolution|DUPLICATE |FIXED --- Comment #3 from caulier.gil...@gmail.com --- Not reproducible using digiKam 7.0.0 beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 246065] digikam crashes at startup
https://bugs.kde.org/show_bug.cgi?id=246065 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Resolution|DUPLICATE |FIXED --- Comment #5 from caulier.gil...@gmail.com --- Not reproducible using digiKam 7.0.0 beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 242305] Digikam Crash
https://bugs.kde.org/show_bug.cgi?id=242305 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||7.0.0 --- Comment #5 from caulier.gil...@gmail.com --- Not reproducible using digiKam 7.0.0 beta1. -- You are receiving this mail because: You are watching all bug changes.
