[plasmashell] [Bug 408247] [Dual monitor, powersave] taskbar showing windows from the wrong screen
https://bugs.kde.org/show_bug.cgi?id=408247 sparhawk changed: What|Removed |Added CC||kdeb...@plast.id.au --- Comment #3 from sparhawk --- I only just came across this bug now. I've been running Plasma for years, but this is the first occurrence, perhaps after a Plasma upgrade yesterday to 5.19.4? I ran into this bug after a reboot. For me, it was enough to restart Plasma to fix it, i.e. `kbuildsycoca5; kquitapp5 plasmashell; plasmashell` Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 Kernel Version: 5.4.53-1-lts OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700 CPU @ 3.60GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424817] New: Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 Bug ID: 424817 Summary: Ugly rendering of images containing text in PDF files Product: okular Version: 1.9.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: --- Created attachment 130504 --> https://bugs.kde.org/attachment.cgi?id=130504&action=edit Example pdf illustrating the bug (generated with 'img2pdf -o test.pdf test.png') SUMMARY Hello, I have observed that unfortunately in Okular PDF files that contain images with text (e.g. scanned pages) are rendered in a relatively "ugly" way at certain zoom levels when compared with other open source PDF readers. STEPS TO REPRODUCE 1. Open attached file "test.pdf" with Okular. 2. Set zoom level to 75%. OBSERVED RESULT Text looks "rather ugly". (See also attached screenshot.) EXPECTED RESULT Text looks "clearly readable". (Compare screenshot from same document opened in Evince.) I have compared the rendering of other open source PDF viewers with Okular (at same zoom level): Evince, MuPDF, Firefox embedded PDF viewer, Chromium embedded PDF viewer The rendering looks fine on all of them with Okular being the only exception. When I check/uncheck "Enable Graphics Antialias" in Okular, this makes no difference for me. I'm using Kubuntu 20.04 as my main system, but I also verified that I see the same result in the current KDE Neon live image (neon-unstable-20200726-1102.iso). SOFTWARE/OS VERSIONS Linux: 5.4.0-42-generic (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kind regards, Jan -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 --- Comment #1 from Jan Rathmann --- Created attachment 130505 --> https://bugs.kde.org/attachment.cgi?id=130505&action=edit Source image file from which the test example was generated. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 --- Comment #3 from Jan Rathmann --- Created attachment 130507 --> https://bugs.kde.org/attachment.cgi?id=130507&action=edit Screenshot rendering of test.pdf with Evince (zoom level 75%) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 --- Comment #2 from Jan Rathmann --- Created attachment 130506 --> https://bugs.kde.org/attachment.cgi?id=130506&action=edit Screenshot rendering of test.pdf with Okular (zoom level 75%) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424818] New: Chaos bei Datum-Übernahme im Metadaten-Editor
https://bugs.kde.org/show_bug.cgi?id=424818 Bug ID: 424818 Summary: Chaos bei Datum-Übernahme im Metadaten-Editor Product: digikam Version: 7.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Date Assignee: digikam-bugs-n...@kde.org Reporter: thaqe9rd...@temp.mailbox.org Target Milestone: --- Created attachment 130508 --> https://bugs.kde.org/attachment.cgi?id=130508&action=edit Resultate der Eingaben SUMMARY Bei Eingabe im Metadaten-Editor werden die Daten nicht wie erwartet übernommen. Die Ereignisse "Wann wurde das Foto aufgenommen" (was sieht man auf dem Foto) und "Wann wurde das Foto digitalisiert" werden gleich behandelt. Bei Digitalkameras stimmt das, beim Scannen alter analoger Fotos (z.B. Negative oder Dias) sind das jedoch zwei verschiedene Daten. STEPS TO REPRODUCE 1. Foto ohne Metadaten erzeugen 2. in Digikam im Metadaten-Editor ein Feld ausfüllen z.B. Exif(!)-Digitaliserungsdatum 3. die Daten "in Datei schreiben" (mit Sidecar .xmp) 4. Werte in Sidecar überprüfen OBSERVED RESULT Das Digitalisierungsdatum wird ins Feld u.a. exif:DateTimeOriginal geschrieben - nicht in das Feld exif:DateTimeDigitized (existiert nicht). EXPECTED RESULT Das Datum wird in exif:DateTimeDigitized (u.a. Digitized-Felder) gespeichert. Andere Felder (exif:DateTimeOriginal etc.) bleiben leer SOFTWARE/OS VERSIONS Windows: Windows 10 DigiKam: 7.0.0 ADDITIONAL INFORMATION Die Eingabe in den Felder (Metadaten-Editor) Exif-Originaldatum und Exif-Erstellungsdatum (Wo ist der Unterschied?) hat die identischen Ergebnisse in der Anzeige der Metadaten und in der Sidecar-Datei. Das Digitalisierungsdatum wird nur in das Feld exif:DateTimeDigitized übernommen, wenn es im Editor unter XMP(!)-Digitaliserungsdatum eingegeben wird. Wenn nur das XMP-Digitalsierungsdatum eingegeben wird (weil z.B. das reale Aufnahmedatum unbekannt ist) wird das Datum trotzdem in alle "Erstellungsdatum"-Felder übernommen z.B. exif:DateTimeOriginal. Das ist falsch, da ich das Original-Datum nicht kenne. Nur bei Eingabe von XMP_Erstellungsdatum und XMP-Digitalisierungdatum werden die Felder exif:DateTimeOriginal und exif:DateTimeDigitized richtig gefüllt. (Sorry, falls ich den Fehler hier im Hinweissystem übersehen habe.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 --- Comment #4 from Vlad Zahorodnii --- Can you please run kwin as `env KWIN_GL_DEBUG=1 QT_LOGGING_RULES="kwin_scene_opengl.debug=true" kwin_x11 --replace` from terminal and post the output here? Please make sure that the provided output contains no sensitive or confidential data. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424818] Chaos bei Datum-Übernahme im Metadaten-Editor
https://bugs.kde.org/show_bug.cgi?id=424818 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Bitte in English schreiben, damit alle Entwickler es verstehen. Nun, Du kannst EXIF Metadaten nicht 100% prozentig in Seitenwagen abbilden, denn Seitenwagen spiegeln nur den XMP Namensraum wieder. Dein Problem haben wir hier schon öfter behandelt. Es wird ein Mapping durchgeführt, damit EXIF Metadaten in XMP abgebildet werden können. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420710] Shouldn't 'Exif.Image.DateTimeOriginal' be the equivalent of 'XMP Creation date' and 'IPTC Creation date', instead of Exif.Image.DateTime?
https://bugs.kde.org/show_bug.cgi?id=420710 Maik Qualmann changed: What|Removed |Added CC||thaqe9rd...@temp.mailbox.or ||g --- Comment #15 from Maik Qualmann --- *** Bug 424818 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424818] Chaos bei Datum-Übernahme im Metadaten-Editor
https://bugs.kde.org/show_bug.cgi?id=424818 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 420710 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424818] Chaos bei Datum-Übernahme im Metadaten-Editor
https://bugs.kde.org/show_bug.cgi?id=424818 --- Comment #3 from Maik Qualmann --- https://www.exiv2.org/conversion.html Maik -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421434] smb4k crashed in Breeze::ShadowHelper::~ShadowHelper() when closed with ctrl+q
https://bugs.kde.org/show_bug.cgi?id=421434 --- Comment #13 from Vlad Zahorodnii --- @Patrick so should we close the bug report? or are you still able to reproduce the crash? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424818] Confusing with date transfer in the metadata editor
https://bugs.kde.org/show_bug.cgi?id=424818 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Summary|Chaos bei Datum-Übernahme |Confusing with date |im Metadaten-Editor |transfer in the metadata ||editor -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 424493] Gimp crashes and closes when I copy a big image and past it in another software (like LibreOffice)
https://bugs.kde.org/show_bug.cgi?id=424493 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Vlad Zahorodnii --- KWindowSystem is not involved in the process of copy/pasting images. It sounds to me like GIMP exceeds the maximum X11 request size limit. However, if GIMP uses Xlib, then the image data should be chopped into multiple chunks behinds the scenes. We had a similar bug in the screenshot service in kwin long time ago. The root cause of the bug was that libxcb doesn't split big images in chunks, the caller must do it manually. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 David Tschumperlé changed: What|Removed |Added CC||david.tschumpe...@gmail.com --- Comment #5 from David Tschumperlé --- Maybe a useful note about G'MIC on MacOSX : A few years ago, when trying to make G'MIC work on MacOSX (but the CLI tool, not the G'MIC-Qt plug-in), we experienced a lot of random crashes, happening when new threads were created by the G'MIC interpreter (it looked similar to what your log shows). The reason was that the default stack size allocated when creating a new thread on MacOSX is ridiculously low (512Kb, while it's several MB on Windows/Linux), and thus, the G'MIC interpreter (which is a pretty complex function) was running out of stack memory. We added a work-around in the G'MIC interpreter code, specifically to solve this for MacOSX, file 'gmic.cpp', l.10324 : https://github.com/dtschump/gmic/blob/master/src/gmic.cpp#L10324 Anyway, I'm not sure we did the same for the threads created by the G'MIC-Qt plug-in, and in that case, it would mean that the main G'MIC instance is run with a 512Kb stack (as it's run in a thread created by G'MIC-Qt). Maybe something to investigate. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 424819] New: Unwanted blur
https://bugs.kde.org/show_bug.cgi?id=424819 Bug ID: 424819 Summary: Unwanted blur Product: frameworks-kwindowsystem Version: 5.71.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kokok...@gmail.com Target Milestone: --- Created attachment 130509 --> https://bugs.kde.org/attachment.cgi?id=130509&action=edit screenshot SUMMARY Since recently blur started to apper even when it is not supposed to show. STEPS TO REPRODUCE 1. Activate blur effect 2. change the opacity of a window OBSERVED RESULT There is blur under the window EXPECTED RESULT To see what's under the window, as it always appened in the past SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.19.3 (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION In the attached screenshot, you can see how blur appears under any semitrransparent windows. In the top/center, you can see another application, it is a launcher developed by me. It uses a 100% transparent window and draws a transparent png over it to render a shadow. As you can see, it is blurred as well, leading to a bad appaerance. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #6 from David Tschumperlé --- After checking, it seems we already have taken care of it : https://github.com/c-koi/gmic-qt/blob/master/src/FilterThread.cpp#L44 But maybe the condition `#ifdef _IS_MACOS_` does not hold ? We cannot check here, as we don't have a machine with MacOSX. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 424819] Unwanted blur
https://bugs.kde.org/show_bug.cgi?id=424819 --- Comment #1 from Vlad Zahorodnii --- Have you installed any kwin script that forces blur? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422548] Cursors do not respect scale factor on X11
https://bugs.kde.org/show_bug.cgi?id=422548 --- Comment #4 from Vlad Zahorodnii --- The problem is that kwin ignores the scale factor on X11. Not sure how we can fix this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366024] Instant preview interferes with making quick, short strokes with a small pen
https://bugs.kde.org/show_bug.cgi?id=366024 --- Comment #2 from Dmitry Kazakov --- Git commit a45686584349c43e2712cc515fa38db7b6618e37 by Dmitry Kazakov. Committed on 30/07/2020 at 08:10. Pushed by dkazakov into branch 'krita/4.3'. Fix Overview Docker resetting Instant Preview caches Basically, each generation of Overview thumbnail used to reset the Instant Preview caches, which could cause some minor delays when painting. M +15 -0plugins/dockers/overview/OverviewThumbnailStrokeStrategy.cpp M +2-0plugins/dockers/overview/OverviewThumbnailStrokeStrategy.h https://invent.kde.org/graphics/krita/commit/a45686584349c43e2712cc515fa38db7b6618e37 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 424819] Unwanted blur
https://bugs.kde.org/show_bug.cgi?id=424819 Antonio Orefice changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Antonio Orefice --- Oh my, you're right. For some reason i ignore, it started to misbehave blurring everything, instead of the app i told him to blur. I even tried disabling it, it continued. But after your suggestion i restarted the whole plasma with the script disabled and all is fine. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 424807] Build with clang++ fails
https://bugs.kde.org/show_bug.cgi?id=424807 Jazeix Johnny changed: What|Removed |Added CC||jaz...@gmail.com Assignee|bruno.coud...@gcompris.net |jaz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 424807] Build with clang++ fails
https://bugs.kde.org/show_bug.cgi?id=424807 --- Comment #1 from Jazeix Johnny --- Can you compile with only "make", no "-j4"? It seems to be an issue with box2d compilation, but as a lot of logs are mixed, it's harder to check: Project ERROR: failed to parse default search paths from compiler output make[2]: *** [CMakeFiles/qml_box2d.dir/build.make:107: qml_box2d-prefix/src/qml_box2d-stamp/qml_box2d-configure] Error 3 Clang is already used by jenkins on FreeBSD (https://build.kde.org/job/Extragear/job/gcompris/job/kf5-qt5%20FreeBSDQt5.15/83/console) and build is fine. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 424807] Build with clang++ fails
https://bugs.kde.org/show_bug.cgi?id=424807 --- Comment #2 from Avinash Sonawane --- Yes, indeed it looks like an issue with box2d compile. $ make Scanning dependencies of target createShareFolders [ 0%] Generating shareFolders [ 0%] Built target createShareFolders Scanning dependencies of target BuildTranslations [ 0%] Built target BuildTranslations Scanning dependencies of target qml_box2d [ 0%] Creating directories for 'qml_box2d' [ 0%] No download step for 'qml_box2d' [ 1%] No patch step for 'qml_box2d' [ 1%] No update step for 'qml_box2d' [ 1%] Performing configure step for 'qml_box2d' Info: creating stash file /home/rootmonk/Downloads/todo/hacking/gcompris/build/qml_box2d-prefix/src/qml_box2d-build/.qmake.stash Project ERROR: failed to parse default search paths from compiler output make[2]: *** [CMakeFiles/qml_box2d.dir/build.make:107: qml_box2d-prefix/src/qml_box2d-stamp/qml_box2d-configure] Error 3 make[1]: *** [CMakeFiles/Makefile2:3766: CMakeFiles/qml_box2d.dir/all] Error 2 make: *** [Makefile:152: all] Error 2 $ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415872] kwin_wayland random segfault libQt5Qml.so.5.14.0[7fe09a171000+307000]
https://bugs.kde.org/show_bug.cgi?id=415872 Milian Wolff changed: What|Removed |Added CC||josep.m.pe...@gmail.com --- Comment #20 from Milian Wolff --- *** Bug 424762 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 424762] Crash while editing C++ code
https://bugs.kde.org/show_bug.cgi?id=424762 Milian Wolff changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Milian Wolff --- crash is upstream in Qt Declarative *** This bug has been marked as a duplicate of bug 415872 *** -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 424807] Build with clang++ fails
https://bugs.kde.org/show_bug.cgi?id=424807 --- Comment #3 from Avinash Sonawane --- BTW, $ uname -a Linux optimus 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal $ -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 424703] KDevelop keeps crashing while parsing a (C++) file
https://bugs.kde.org/show_bug.cgi?id=424703 Milian Wolff changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Milian Wolff --- can you attach the backtrace that you get when it crashes? also note that it doesn't crash for me when I just load the file - so how do I reproduce it? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 Bug Janitor Service changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #31 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/pim/messagelib/-/merge_requests/3 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 417189] Drag and Drop doesn't work in file open dialog
https://bugs.kde.org/show_bug.cgi?id=417189 --- Comment #11 from Attila --- Hi, thank you for the fix. I can't wait to test it. Still one question. Did you make a "pull request" to the Fedora packagers (maintainers) to update KDiff3? There is no "rpm" in "testing" at the moment. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-karchive] [Bug 424820] New: Tests are failing: missing #include
https://bugs.kde.org/show_bug.cgi?id=424820 Bug ID: 424820 Summary: Tests are failing: missing #include Product: frameworks-karchive Version: unspecified Platform: Compiled Sources OS: All Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: fa...@kde.org Reporter: gm...@ratijas.tk CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Tests are failing (compile-time) on qDebug() because QDebug is not #included. As far as I can tell, there are many commented out lines of //qDebug() in the code, but this particular one is un-commented, and #include is missing. https://invent.kde.org/frameworks/karchive/-/blob/f83a898885391308ba59306c42daf74cb3f26296/autotests/karchivetest.cpp#L364 STEPS TO REPRODUCE 1. Compile from source 2. Run tests OBSERVED RESULT > /home/travis/build/labsquare/FastQt/karchive/autotests/karchivetest.cpp: In > member function ‘void KArchiveTest::initTestCase()’: > /home/travis/build/labsquare/FastQt/karchive/autotests/karchivetest.cpp:364:16: > error: invalid use of incomplete type ‘class QDebug’ > qDebug() << errno; https://cdn.travis-ci.org/github/labsquare/FastQt/builds/713213447#L751 EXPECTED RESULT Tests compile and pass. SOFTWARE/OS VERSIONS TravisCI / irrelevant ADDITIONAL INFORMATION Affected GitHub issue: https://github.com/labsquare/FastQt/issues/98 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402346] The digikamrc file is not recorded into the digikam directory
https://bugs.kde.org/show_bug.cgi?id=402346 --- Comment #10 from chasa.im...@xs4all.nl --- https://bugs.kde.org/show_bug.cgi?id=413489 Just adding this info. Did a fresh installation of digikam 7.0.0. And the location of the digikamrc file is still there, where it always was, in the 'wrong' location. ☻ ! C:\Users\[user name]\Appdata\Local ! And not in something like: C:\Users\[user name]\AppData\Local\digikam or C:\Users\[user name]\AppData\Roaming\digikam OBSERVED RESULT wrong location EXPECTED RESULT To reside in the logical and expected directory. SOFTWARE/OS VERSIONS Windows: Microsoft Windows [Version 10 Pro 2004 19041.388] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424821] New: Starting new application on second desktop adds another virtual desktop
https://bugs.kde.org/show_bug.cgi?id=424821 Bug ID: 424821 Summary: Starting new application on second desktop adds another virtual desktop Product: plasmashell Version: 5.19.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: piotr.mierzwin...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Maybe subject sounds funny, but issue is really annoying. I have two virtual desktops. When I switch into the second and just start new application (by click on icon present in task bar or just selecting any one in Kicker). Note, the way of starting doesn't matter, the matter is when appears new instance of any application then new virtual desktop appears. Worth mention this is happen _only_ on second desktop, on first one all is fine. Second strange thing in this issue is that, having 3 virtual desktops (after this unintentional adding), when I start another application then new 4th virtual desktop doesn't appear. It stops on three. BTW. Sometime also is turned on 'Do not disturb mode' in Notification system. I didn't discover yet what depends on this unintentional switching. Currently I'm working with Plasma 5.19.4, but issue happened before update. I tested it, running: Thunderbird, Opera, Dolphin, KWrite, System Settings. Always the same behavior - third virtual desktop appears. STEPS TO REPRODUCE 1. Set two virtual desktops 2. Switch to second one 3. Start any application OBSERVED RESULT New virtual desktop appears EXPECTED RESULT Should not appears any new virtual desktop if I didn't add it intentionally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72 Qt Version: 5.15.0 ADDITIONAL INFORMATION Kernel Version: 5.7.10-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #7 from caulier.gil...@gmail.com --- Thanks David. I use a Macbook pro here, so i will check this pre-processor condition. It's interesting to see the huge limitation of stack under OSX. I know that we needs to fix in the pass all local class allocations in function with new operator to prevent memory allocation error (using LibRaw class in digiKam for ex.). Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424818] Confusing with date transfer in the metadata editor
https://bugs.kde.org/show_bug.cgi?id=424818 --- Comment #4 from Stefan --- (Deepl-Übersetzung) So I probably did not enter the right search terms if the "problem" is known. I'm sorry. Too bad it still exists. Because the mapping doesn't seem to work properly - independent of the storage functions in a sidecar file. When I enter a date in the Metadata Editor under XMP Digitized - it appears correctly in the Metadata Display in DigiKam under "XMP-Exif Properties-Date Digitized". But then why is the date from the "XMP-Date (original)" field in the "Exif-Photo Information-Date (digitized)" field there? The input (metadata editor) in the field EXIF Digitized Date has then no effect on "Exif-Photoinformation-Date (digitized)" or "XMP-Exif-Properties-Date Digitized" ... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408247] [Dual monitor, powersave] taskbar showing windows from the wrong screen
https://bugs.kde.org/show_bug.cgi?id=408247 --- Comment #4 from Johannes Pfrang --- This might be a duplicate of bug 394532, which was fixed for Plasma 5.20, but unfortunately wasn't backported (yet?): https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/36 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 321884] crashed while sending photos to vkontakte
https://bugs.kde.org/show_bug.cgi?id=321884 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 caulier.gil...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 404510] Option for storing print scale setting
https://bugs.kde.org/show_bug.cgi?id=404510 Frank Steiner changed: What|Removed |Added CC||fsteiner-bo...@bio.ifi.lmu. ||de --- Comment #1 from Frank Steiner --- Just got okular 20.04.2 with opensuse leap 15.2 which has the rasterization patch included, so we don't have to compile okular with the patch again. But indeed, it is tedious to activate it again and again for every print, so there should be a setting for rasterization and the fittings setting, or okular should default to the last setting. It doesn't even keep the setting for a session, i.e. on every call of the print dialog rasterization is off again. Would be great to have config option here... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 367979] Crashes when scanning directories on network drive
https://bugs.kde.org/show_bug.cgi?id=367979 --- Comment #10 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 345391] digikam does not find the album when there is a bind mount
https://bugs.kde.org/show_bug.cgi?id=345391 --- Comment #16 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368468] digiKam hanging at start up with a collection that has >100000 sub folders
https://bugs.kde.org/show_bug.cgi?id=368468 --- Comment #22 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370029] black and white low resolution print only
https://bugs.kde.org/show_bug.cgi?id=370029 caulier.gil...@gmail.com changed: What|Removed |Added Severity|major |normal --- Comment #9 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376891] Digikam becomes unusable with many Metatags
https://bugs.kde.org/show_bug.cgi?id=376891 --- Comment #16 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376401] Crash with MariaDB-Database
https://bugs.kde.org/show_bug.cgi?id=376401 --- Comment #12 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382013] Crash during or after adding a new remote collection
https://bugs.kde.org/show_bug.cgi?id=382013 --- Comment #9 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 378971] Incorrect handling of DateTimeOriginal tags when editing NEF (Nikon RAW)
https://bugs.kde.org/show_bug.cgi?id=378971 --- Comment #9 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382482] Digikam can not connect to the database
https://bugs.kde.org/show_bug.cgi?id=382482 --- Comment #9 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382706] Assigning tag to NEF-file results in crash + config disappearing
https://bugs.kde.org/show_bug.cgi?id=382706 --- Comment #8 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422345] libQT5WebEngine crash
https://bugs.kde.org/show_bug.cgi?id=422345 --- Comment #13 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417027] Digikam does not start
https://bugs.kde.org/show_bug.cgi?id=417027 --- Comment #9 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420868] Random crashes, no error messages. Windows event report follows, suspect TIFF plugin
https://bugs.kde.org/show_bug.cgi?id=420868 --- Comment #29 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414737] DigiKam becomes unresponsive when clicking on NFS-mounted photos
https://bugs.kde.org/show_bug.cgi?id=414737 --- Comment #5 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424619] kbuildsycoca5 hangs / digikam also hangs - profile specific problem
https://bugs.kde.org/show_bug.cgi?id=424619 --- Comment #6 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406961] Video with geo tags is filtered as non-geotagged
https://bugs.kde.org/show_bug.cgi?id=406961 --- Comment #7 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423632] Segfault when scanning faces
https://bugs.kde.org/show_bug.cgi?id=423632 --- Comment #9 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414148] Database error on upgrade. Digikam now won't open.
https://bugs.kde.org/show_bug.cgi?id=414148 --- Comment #5 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417896] Crash while converting RAW (Canon cr2) files (V 7 Beta 2)
https://bugs.kde.org/show_bug.cgi?id=417896 --- Comment #6 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402714] DigiKam crash using "create stacked images" several times on 25 images from the same folder
https://bugs.kde.org/show_bug.cgi?id=402714 --- Comment #5 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401941] Beta3 / beta2 launches but hangs... Now fear for DB!
https://bugs.kde.org/show_bug.cgi?id=401941 --- Comment #7 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400941] Crash with segmentation fault when writing a large amount of metadata to images
https://bugs.kde.org/show_bug.cgi?id=400941 --- Comment #5 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419079] Star rating on TIFF images destroys the image
https://bugs.kde.org/show_bug.cgi?id=419079 --- Comment #4 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403073] Can't remove a removable media when digikam run
https://bugs.kde.org/show_bug.cgi?id=403073 --- Comment #7 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412113] Permanent error
https://bugs.kde.org/show_bug.cgi?id=412113 --- Comment #9 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422208] digiKam sporadically becomes totally unresponsive (freezes up) when editing Tags
https://bugs.kde.org/show_bug.cgi?id=422208 --- Comment #8 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 --- Comment #9 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391044] digikam crashed when trying to open a Dir on an iPad via usb
https://bugs.kde.org/show_bug.cgi?id=391044 --- Comment #6 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403164] Crash while trying to download videos from camera
https://bugs.kde.org/show_bug.cgi?id=403164 --- Comment #6 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420411] digiKam Crash on detect faces 7.0.0 beta3 debug build
https://bugs.kde.org/show_bug.cgi?id=420411 --- Comment #5 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424618] When clicking on maps digiKam crash
https://bugs.kde.org/show_bug.cgi?id=424618 --- Comment #10 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414114] Gphoto2 I/O error -7 when importing photos from iphone 7+
https://bugs.kde.org/show_bug.cgi?id=414114 --- Comment #11 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398831] digiKam DB maintenance can not tell difference between two external drives (same type and size)
https://bugs.kde.org/show_bug.cgi?id=398831 --- Comment #12 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411388] Digikam froze and crash after downloading photos.
https://bugs.kde.org/show_bug.cgi?id=411388 --- Comment #3 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416266] digikam crashes during face detection
https://bugs.kde.org/show_bug.cgi?id=416266 --- Comment #16 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396766] Can't add collection on removable disk
https://bugs.kde.org/show_bug.cgi?id=396766 --- Comment #7 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400103] Feature Request remember last used directory in places (Save as dialog)
https://bugs.kde.org/show_bug.cgi?id=400103 --- Comment #10 from Frank Steiner --- Any chance we get that feature? :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366024] Instant preview interferes with making quick, short strokes with a small pen
https://bugs.kde.org/show_bug.cgi?id=366024 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424489] systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 --- Comment #7 from Gabor --- I just noticed, that my calendar widget (org.kde.plasma.calendar.wl) also opens the calendar on the left, while the clock widget opens on the right place on the right. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418939] Crash when search faces
https://bugs.kde.org/show_bug.cgi?id=418939 --- Comment #18 from caulier.gil...@gmail.com --- digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424818] Confusing with date transfer in the metadata editor
https://bugs.kde.org/show_bug.cgi?id=424818 --- Comment #5 from Maik Qualmann --- Look in the conversion table. XMP metadata is also interpreted backwards as EXIF metadata. Exiv2 carries out this mapping, we have only limited influence on it. Perhaps it will help to ask which metadata standard it corresponds to. I don't think it's flawed. https://www.exiv2.org/conversion.html Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424797] Alpha calculations on alpha masked layers with opacity is 'wrong'?
https://bugs.kde.org/show_bug.cgi?id=424797 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422909] New Local selection is collapsed in Layers Docker
https://bugs.kde.org/show_bug.cgi?id=422909 Dmitry Kazakov changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com CC||dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424638] Crash when using move tool on the transform mask
https://bugs.kde.org/show_bug.cgi?id=424638 Dmitry Kazakov changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com CC||dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424233] Moving layers while using the wrap around tool cuts off the image/distorts it
https://bugs.kde.org/show_bug.cgi?id=424233 Dmitry Kazakov changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com CC||dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422375] File layer is not being synchronized properly under Windows 10
https://bugs.kde.org/show_bug.cgi?id=422375 Dmitry Kazakov changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com CC||dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422525] 'New From Visible' creates an animated layer if the document has an animated layer
https://bugs.kde.org/show_bug.cgi?id=422525 Dmitry Kazakov changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com CC||dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424573] Sensors search stops working after I reopen the widget settings
https://bugs.kde.org/show_bug.cgi?id=424573 --- Comment #4 from David Redondo --- In plasma 5.20 this has a new ui without this text field. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420033] New layer number always starts from 1 when editing present PSD files
https://bugs.kde.org/show_bug.cgi?id=420033 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424489] systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 Ben Cooksley changed: What|Removed |Added CC|sysad...@kde.org| -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421744] Preserve the color of the layer label in layers docker when merging others to it
https://bugs.kde.org/show_bug.cgi?id=421744 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411790] File layers don't refresh if they are created from the convert context menu in layer stack.
https://bugs.kde.org/show_bug.cgi?id=411790 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424489] systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 --- Comment #8 from Gabor --- (In reply to Gabor from comment #7) > I just noticed, that my calendar widget (org.kde.plasma.calendar.wl) also > opens the calendar on the left, while the clock widget opens on the right > place on the right. And now it's not. My widgets are in vertical order but it seems the opening panels try to go from left to right. And I can't reproduce the state when the clock opened in right. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424797] Alpha calculations on alpha masked layers with opacity is 'wrong'?
https://bugs.kde.org/show_bug.cgi?id=424797 Dmitry Kazakov changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=424525 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424525] Wrong behavior of blending modes in CMYK
https://bugs.kde.org/show_bug.cgi?id=424525 Dmitry Kazakov changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=424797 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424797] Alpha calculations on alpha masked layers with opacity is 'wrong'?
https://bugs.kde.org/show_bug.cgi?id=424797 --- Comment #2 from Dmitry Kazakov --- This bug is related to bug 424525 in some way. I will investigate further. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424775] It will NOT go out to a bank or ANY institution and retrieve any data!, I have USED Quicken for years. I printed the connection data, tested each by hand with a browser. and m
https://bugs.kde.org/show_bug.cgi?id=424775 Thomas Baumgart changed: What|Removed |Added Summary|I will NOT go out to a bank |It will NOT go out to a |or ANY institution and |bank or ANY institution and |retrieve any data!, I |retrieve any data!, I have |have USED Quicken for |USED Quicken for years. I |years. I printed the |printed the connection |connection data, tested |data, tested each by hand |each by hand with a |with a browser. and |browser. and manually enter |manually enter all. They |all. They all appear nice |all appear nice on the |on the opening |opening screen.watched |screen.watched YouTubea |YouTube --- Comment #7 from Thomas Baumgart --- Guys, I am glad that things calmed down here and the initial steam has settled. As Jack already pointed out, we should better use the mailing list (see https://mail.kde.org/mailman/listinfo/kmymoney) or the forum at https://forum.kde.org/viewforum.php?f=69 for further discussion of the subject. I am sure, we will get you going. BTW: I added that missing T to the subject of this ticket for historical reasons. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424536] Docker becomes smaller vertically for every Tab
https://bugs.kde.org/show_bug.cgi?id=424536 --- Comment #4 from coodlesmood...@gmail.com --- @Tymond It also happens with the appimage for me -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 424781] When you copy something in Spectacle, it copies the image directory to your clipboard, and not the image.
https://bugs.kde.org/show_bug.cgi?id=424781 --- Comment #2 from ber...@codewiz.org --- I'm not the original reporter, but I have the same issue: > Configure -> General -> What is set within "After taking screenshot" ? Copy image to clipboard: checked Autosave the image to the default location: unchecked > Configure -> Save -> Do you have the "Copy file location to clipboard after > saving" set? Yes, it's checked (it's the default setting). With these settings: 1. I take a screenshot with the hotkey 2. I paste the clipboard in the desktop or in Dolphin 3. The file appears, but it contains the pathname This other workflow used to be broken, but now it works with plasma built from git: 1. I take a screenshot with the hotkey 2. Open hamburger menu in the notification 3. Select "Copy" from the menu 4. Paste on the desktop or in Dolphin using ctrl-v or "Paste One File" in the context menu -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424818] Confusing with date transfer in the metadata editor
https://bugs.kde.org/show_bug.cgi?id=424818 --- Comment #6 from Stefan --- (Deepl-Übersetzung) Ok, a bit difficult to judge, because I don't know which meta fields are actually displayed in digicam or filled in the metadata editor. It would be helpful to understand if the technical metadata name was visible in the editor (e.g. as a mouse overlay). Or also, at which time and in which direction data are / must be converted. I understand the exiv2 table in such a way that the fields Exif.Photo.DateTimeDigitized <-> Xmp.xmp.CreateDate should be identical - namely the digitization date! The creation date would be the combination: Exif.Photo.DateTimeOriginal <-> Xmp.photoshop.DateCreated. Is it like that in digicam? Why then (in the .xmp file)? exif:DateTimeDigitized="2020-02-02T02:02:02+00:00" xmp:CreateDate="2020-01-01T01:01:01" The right one would be after exiv2: exif:DateTimeDigitized="2020-02-02T02:02:02+00:00" xmp:CreateDate="2020-02-02T02:02:02" and exif:DateTimeOriginal="2020-01-01T01:01:01" photoshop:DateCreated="2020-01-01T01:01:01" Thanks for your efforts and answers so far :-) And a big praise to the developers of Digikam. Despite some shortcomings and possibilities for improvement, it fulfills my ideas best, even in contrast to commercial programs. -- You are receiving this mail because: You are watching all bug changes.
