[digikam] [Bug 401010] simple search on one file name crashes the program if there is more than one hit
https://bugs.kde.org/show_bug.cgi?id=401010 --- Comment #4 from Torben --- Hi Sorry for the long response time. Yes I have changed to Windows for good. The reported error cannot be reproduced in Version 6.0.0-beta2 Vänliga hälsningar Torben Christiansen Kastanjevägen 80 462 50 Vänersborg +46 (0)709 673816 christiansen-tor...@hotmail.com<mailto:christiansen-tor...@hotmail.com> Den 13-11-2018 kl. 21:35 skrev Maik Qualmann: https://bugs.kde.org/show_bug.cgi?id=401010 Maik Qualmann <mailto:metzping...@gmail.com> changed: What|Removed |Added CC| |metzping...@gmail.com<mailto:metzping...@gmail.com> --- Comment #2 from Maik Qualmann <mailto:metzping...@gmail.com> --- You write from KphotoAlbum on Ubuntu. Is Windows Platform correct in the bug report? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401010] New: simple search on one file name crashes the program if there is more than one hit
https://bugs.kde.org/show_bug.cgi?id=401010 Bug ID: 401010 Summary: simple search on one file name crashes the program if there is more than one hit Product: digikam Version: 5.9.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: Searches Assignee: digikam-bugs-n...@kde.org Reporter: christiansen-tor...@hotmail.com Target Milestone: --- Created attachment 116285 --> https://bugs.kde.org/attachment.cgi?id=116285=edit search result after restart SUMMARY DigiKam has 'adopted' the file structure of my ealier KphotoAlbum installation on Ubuntu 16.04. I am working on entering missing tags for the pictures. I discovered that a simple search of one picture file name with 2 hits (on different pictures), makes the programme crash. When restarting the programme, the correct search result is shown. STEPS TO REPRODUCE 1. enter a specific file name of a picture ie 'BILLED4.TIF' 2. restart the program 3. OBSERVED RESULT EXPECTED RESULT 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.
[kcalc] [Bug 357824] Decimal point on numpad not working for en_GB and Danish keyboard layout
https://bugs.kde.org/show_bug.cgi?id=357824 --- Comment #5 from Torben Hansen <kde-b...@linhard.dk> --- I have tested the patch against kcalc-16.08.2. Confirmed that it solve the problem. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 357824] Decimal point on numpad not working for en_GB and Danish keyboard layout
https://bugs.kde.org/show_bug.cgi?id=357824 --- Comment #2 from Torben Hansen <kde-b...@linhard.dk> --- This is still an issue with version 16.08.2 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 357824] New: Decimal point on numpad not working for en_GB and Danish keyboard layout
https://bugs.kde.org/show_bug.cgi?id=357824 Bug ID: 357824 Summary: Decimal point on numpad not working for en_GB and Danish keyboard layout Product: kcalc Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: kde-b...@linhard.dk Version 15.08.3 This is similar to, which however is reported fixed https://bugs.kde.org/show_bug.cgi?id=67984 kcalc does nothing when pressing "." on the numpad, while it should result in a decimal separator. xev generates "keysym 0xffac, KP_Separator" when pressing "." on the numpad. Reproducible: Always Steps to Reproduce: 1. Open kcalc 2. Press; KP_1, KP_separator, KP_1 3. Actual Results: "11" in display Expected Results: "1.1" in display LANG=en_GB.UTF-8 All other locale parameters the same xorg.conf.d/00-keyboard.conf: Section "InputClass" Identifier "system-keyboard" MatchIsKeyboard "on" Option "XkbLayout" "dk" Option "XkbModel" "pc105" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection -- You are receiving this mail because: You are watching all bug changes.
