[kmymoney] [Bug 395965] Il se produit lorsque je veux lancer un rapport opérations
https://bugs.kde.org/show_bug.cgi?id=395965 Jack changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||ostroffjh@users.sourceforge ||.net Resolution|--- |WAITINGFORINFO --- Comment #2 from Jack --- Does this still happen? If so, please provide more details, French is OK. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393635] Segfault when saving TIFF after modifying RAW
https://bugs.kde.org/show_bug.cgi?id=393635 --- Comment #16 from caulier.gil...@gmail.com --- Exiv2 team is serious ? The crash backtrace is clear : #0 0x7fec1165e186 in Exiv2::IptcData::printStructure(std::ostream&, unsigned char const*, unsigned long, unsigned int) () from /usr/lib/libexiv2.so.26 [Current thread is 1 (Thread 0x7feae8ff9700 (LWP 2696))] (gdb) #0 0x7fec1165e186 in Exiv2::IptcData::printStructure(std::ostream&, unsigned char const*, unsigned long, unsigned int) () at /usr/lib/libexiv2.so.26 #1 0x7fec11658a20 in Exiv2::Image::printIFDStructure(Exiv2::BasicIo&, std::ostream&, Exiv2::PrintStructureOption, unsigned int, bool, char, int) () at /usr/lib/libexiv2.so.26 #2 0x7fec1165a558 in Exiv2::Image::printTiffStructure(Exiv2::BasicIo&, std::ostream&, Exiv2::PrintStructureOption, int, unsigned long) () at /usr/lib/libexiv2.so.26 #3 0x7fec116d7115 in Exiv2::TiffImage::printStructure(std::ostream&, Exiv2::PrintStructureOption, int) () at /usr/lib/libexiv2.so.26 #4 0x7fec116d8bdb in Exiv2::TiffImage::readMetadata() () at /usr/lib/libexiv2.so.26 #5 0x7fec1b23e771 in Digikam::MetaEngine::load(QString const&) const () at It's in Exiv2 code, not digiKam. The tiff parser and after the IPTC metadata parser do something wrong with the image. digiKam ask to Exiv2 to extract the image from standard IPTC preview tag (typically a JPEG image). That all. The action is delegate to Exiv2, and digiKam wait the data. The crash appear in the internal process from Exiv2. It's not so far a digiKam crash. Note: the warning come from Exiv2 and is just informative that some tags structure cannot be handled properly. Exiv2 format the metadata container accordingly and pass as well the data to the client application. That all... In other word, this warning is not important for digiKam. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398965] Kwin won't start with 100% CPU
https://bugs.kde.org/show_bug.cgi?id=398965 Niccolo Brogi changed: What|Removed |Added Platform|Other |Ubuntu Packages Version|unspecified |5.12.6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398965] Kwin won't start with 100% CPU
https://bugs.kde.org/show_bug.cgi?id=398965 Niccolo Brogi changed: What|Removed |Added CC||m...@nbrogi.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398968] New: crash on using move tool during document open
https://bugs.kde.org/show_bug.cgi?id=398968 Bug ID: 398968 Summary: crash on using move tool during document open Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Tools/Move Assignee: krita-bugs-n...@kde.org Reporter: b...@fastmail.com Target Milestone: --- Created attachment 115170 --> https://bugs.kde.org/attachment.cgi?id=115170=edit gdb backtrace of appimage SUMMARY krita-4.1.1-5 (Arch Linux) krita-4.2.0-pre-alpha-127857b-x86_64.appimage Tested with fresh configuration (removing existing ~/.local/share/krita, ~/.config/krita*) STEPS TO REPRODUCE 1. Have other .kra files to open (only tested format) 2. Create new document (ctrl+n) 3. Fill canvas with black, Edit > Fill (shift+backspace) you need something for the move tool to easily grab 4. Switch to move tool (t) 5. File > Open (ctrl+o), select another document to open (larger = easier) 6. While file is loading, click repeatedly on canvas of original document EXPECTED RESULT Nothing? ACTUAL RESULT SIGSEGV SOFTWARE VERSIONS KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION May not be related entirely with move tool, that was just the used method of easily reproducing crash. Seems to depend on size of file opened, the amount of time required/things it has to load. Happens consistently with 20+ MB .kra files, may vary based on processor. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 361836] High CPU usage when I open the applications launcher
https://bugs.kde.org/show_bug.cgi?id=361836 --- Comment #3 from Gerard --- Yes, it's ok if you close this bug. It still persists on my parents computer, under Ubuntu 14.04. However it's not a problem, because here in my home I switched my computers to i3wm under Debian 9. Not because of bugs --actually, i3wm also has bugs--, it's because I get used to minimalistic Window Managers. If I have a moment to test Plasma 5 and reproduce this bug, I will report it. I follow your job and you are doing things very well. I enjoyed a lot with KDE4. Keep up the good work! Regards. -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 360653] KCM systemd does not handle window maximize event
https://bugs.kde.org/show_bug.cgi?id=360653 Alexander Potashev changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Alexander Potashev --- Not reproducible anymore with systemd-kcm 1.2.1, KF 5.48.0, Plasma 5.13.4, Qt 5.11.1. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 398876] [mapping] Couldn't map a Cintiq13HD to a single screen.
https://bugs.kde.org/show_bug.cgi?id=398876 Valeriy Malov changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Valeriy Malov --- Can you please produce and share the following debug info: 1) Run kdebugsettings, type "wacom" in search bar and set logging for wacomtablet components to "All" 2) Restart KDE session or restart kded5 (press Alt+Space and run "kquitapp5 kded5 && kded5"), go to the mapping config, set mapping to full screen, click OK and Apply 3) Open mapping configuration again, run calibration This should generate some calibration debug info in standard output, this is probably in ~/.local/share/sddm/xorg-session.log or ~/.xession-errors (this seems to be distribution specific). Run "cat ~/.local/share/sddm/xorg-session.log | grep Calibration" (or ~/.xession-errors), and share the output here As a temporary workaround for now I can only suggest either manually trying to tweak the numbers in "fine tuning" area or calibrating it with some other tool and using area numbers from it. You can get the "Wacom Tablet Area" property by running "xinput list-props 111" where 111 is your device number from "xinput list". -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 398963] Background disappears instead of blurring
https://bugs.kde.org/show_bug.cgi?id=398963 --- Comment #1 from beojan --- It appears this only happens with dark backgrounds, because the blur is very strong and has a grey overlay. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 392223] segmentation fault
https://bugs.kde.org/show_bug.cgi?id=392223 Sergio Martins changed: What|Removed |Added Latest Commit||https://commits.kde.org/cla ||zy/d6cb7569816ce11160a2eeeb ||d58a92a345b59f70 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #11 from Sergio Martins --- Git commit d6cb7569816ce11160a2eeebd58a92a345b59f70 by Sergio Martins. Committed on 22/09/2018 at 19:25. Pushed by smartins into branch '1.3'. Workaround crash with LLVM 7 If clazy is compiled with clang instead of gcc it might crash with: ==10637== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==10637== Access not within mapped region at address 0x8 ==10637==at 0x19CDD8C: clang::ast_matchers::MatchFinder::MatchFinder(clang::ast_matchers::MatchFinder::MatchFinderOptions) (in /usr/lib/llvm-7/bin/clang) ==10637==by 0x9D75670: ClazyASTConsumer (Clazy.cpp:62) ==10637==by 0x9D75670: ClazyASTAction::CreateASTConsumer(clang::CompilerInstance&, llvm::StringRef) (Clazy.cpp:183) ==10637==by 0x9E29ED: clang::FrontendAction::CreateWrappedASTConsumer(clang::CompilerInstance&, llvm::StringRef) (in /usr/lib/llvm-7/bin/clang) ==10637==by 0x9E8FCA: clang::FrontendAction::BeginSourceFile(clang::CompilerInstance&, clang::FrontendInputFile const&) (in /usr/lib/llvm-7/bin/clang) ==10637==by 0x9AE3D5: clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) (in /usr/lib/llvm-7/bin/clang) ==10637==by 0xA8C9FA: clang::ExecuteCompilerInvocation(clang::CompilerInstance*) (in /usr/lib/llvm-7/bin/clang) ==10637==by 0x5822C7: cc1_main(llvm::ArrayRef, char const*, void*) (in /usr/lib/llvm-7/bin/clang) ==10637==by 0x571ACC: main (in /usr/lib/llvm-7/bin/clang) After debugging clazy and clang's code I couldn't find anything wrong with it. Valgrind's output doesn't make much sense, and simply compiling the Clazy.cpp translation unit with gcc instead of clang makes the crash go away and valgrind's output is clean. I'm assuming debian's LLVM was built with gcc and building clazy with clang will have some sort of incompatibility, or maybe it's simply a clang bug. The downside of this workaround is that qcolor-literal check will be disabled. Next step will be producing a minimal test case and reporting to LLVM. CCMAIL: woebbek...@kde.org M +6-0CMakeLists.txt M +7-0src/Clazy.cpp https://commits.kde.org/clazy/d6cb7569816ce11160a2eeebd58a92a345b59f70 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398409] KMyMoney does not prompt for password when connecting to database
https://bugs.kde.org/show_bug.cgi?id=398409 Eleazar changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #14 from Eleazar --- Did as instructed and all files were removed. Thanks for the fix. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398410] KMyMoney crashes when trying to save entries back to DB Backend
https://bugs.kde.org/show_bug.cgi?id=398410 --- Comment #5 from Eleazar --- Moving comment from 393839 to here as instructed by Jack. Since I was having trouble saving entries to my Database I figured I would save my DB to a File and then try to save it as SQL back into my Database Server under a different Database. It crashed everytime tried to save it to the Database Server STEPS TO REPRODUCE 1. Save Database Entries to file (via File -> Save As) 2. Close KMM 3. Open KMM and Load saved file 4. Save File to Database (via File -> Save As "SQL") EXPECTED RESULT New Database get populated with current File ACTUAL RESULT KMM Crashes ADDITIONAL INFORMATION OS: KUbuntu 18.04.1 Kernel: 4.15.0-34-generic Build from source Branch 5.0 (pulled on 09/21/2018 @ 20:43 MDT) KMM Version 5.0.2-cc670b1a Core Dump/Backtrace: https://drive.google.com/open?id=1bulb9NpxXpKYpfOiliJeLH-tlHv3mtXV -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398624] Cannot edit Date in XMP video metadata
https://bugs.kde.org/show_bug.cgi?id=398624 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dig ||ikam/5c2fece9bf2dcb5aec198c ||65a37dfb324c908490 Status|REPORTED|RESOLVED Version Fixed In||6.0.0 --- Comment #6 from Maik Qualmann --- Git commit 5c2fece9bf2dcb5aec198c65a37dfb324c908490 by Maik Qualmann. Committed on 22/09/2018 at 20:17. Pushed by mqualmann into branch 'master'. add Xmp:Video section to remove with the BQM tool FIXED-IN: 6.0.0 M +32 -18 core/utilities/queuemanager/tools/metadata/removemetadata.cpp M +1-0core/utilities/queuemanager/tools/metadata/removemetadata.h https://commits.kde.org/digikam/5c2fece9bf2dcb5aec198c65a37dfb324c908490 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397688] Zoom effect lags before decreasing icon
https://bugs.kde.org/show_bug.cgi?id=397688 Christos changed: What|Removed |Added CC||aligatortur...@gmail.com --- Comment #6 from Christos --- Perhaps not exactly the same issue (?), I was just checking the zoom effect and it has improved quite a lot since the last time I tried latte-dock. Two things I wanted to note: 1. would it be possible to set the zoom effect to more than 100% zoom? 2. here's a [video](https://www.youtube.com/watch?v=OvQwhS09_v4=youtu.be) of the zoom effect on latte-dock on my desktop, and here's a [video of plank](https://www.youtube.com/watch?v=N0dQwrRwe8o=youtu.be) zoom effect. I think the effect on plank is a bit quicker, but apart from that it looks much better when the mouse leaves the dock altogether. Would it be possible to replicate that effect? Thanks for the awesome dock, and sorry if I'm not using the bug report correctly. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 398969] New: Show previews not working in Ubuntu 18.04, XFCE 4
https://bugs.kde.org/show_bug.cgi?id=398969 Bug ID: 398969 Summary: Show previews not working in Ubuntu 18.04, XFCE 4 Product: krusader Version: 2.6.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: krviewer Assignee: krusader-bugs-n...@kde.org Reporter: viktor.mastori...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. navigate to a folder with images 2. menu: View > Show previews EXPECTED RESULT preview images, show thumbnails ACTUAL RESULT no thumbnails SOFTWARE VERSIONS (available in About System) KDE Plasma Version: n.a. KDE Frameworks Version: n.a. Qt Version: XFCE version 4.12 OS: Ubuntu Studio 18.04 ADDITIONAL INFORMATION The 'show previews' worked just fine in 16.04 I just upgraded to 18.04 and there's no preview of images. although, when pressing F3, images are properly displayed in KrViewer -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 397611] [ERR-5]: Format de date non pris en charge importation boobank
https://bugs.kde.org/show_bug.cgi?id=397611 --- Comment #23 from chos...@laposte.net --- (In reply to Stephane MANKOWSKI from comment #22) > Essayez ceci depuis la console: > export SKGTRACE=5et pas 10 > skrooge 2>&1 > traces.txt > Faites l'import > Ctrl+C quand ça bloque. > Poster les traces. J'ai posté à l'adresse ...@mankoswski.fr, j'étais un peu gêné de publier toutes ces infos en ligne. (-: -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397022] kmy do not recognise my schedule transaction when I import a qif file
https://bugs.kde.org/show_bug.cgi?id=397022 antoine changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #16 from antoine --- I chose "Not a bug", I was not using KMM in the right way -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 398858] kdesrc-build should use HTTPS instead of SSH for anonymous git clones
https://bugs.kde.org/show_bug.cgi?id=398858 Michael Pyne changed: What|Removed |Added Version Fixed In||18.09 Latest Commit||2c09ca0d8bc469d9860fc293b3e ||1eae2814dd4cb Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Michael Pyne --- Hmm, I'd added the magic "close the bug" tag on Johan's commit but I forget he needs to be a dev for that to actually work. Closing manually, a separate patch review won't be needed, this was committed as 2c09ca0d8bc469d9860fc293b3e1eae2814dd4cb -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 398501] data type of decimal number is missing
https://bugs.kde.org/show_bug.cgi?id=398501 --- Comment #1 from Robby Stephenson --- The simple text field is what Tellico uses for pricing for all the default collections. Between the different currency symbols and so on, there isn't much sense for a custom field type. I'm not sure what a decimal type would benefit. Perhaps you're also looking for Tellico to be able to some sort of reporting for collection value and so on? -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398914] [feature request] - add option for dock/panel of highest shortcuts priority
https://bugs.kde.org/show_bug.cgi?id=398914 --- Comment #3 from Michail Vourlakos --- Created attachment 115166 --> https://bugs.kde.org/attachment.cgi?id=115166=edit Option for shortcuts highest preference -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398962] New: Window thumbnails with media buttons disappear when I hover the mouse over the buttons
https://bugs.kde.org/show_bug.cgi?id=398962 Bug ID: 398962 Summary: Window thumbnails with media buttons disappear when I hover the mouse over the buttons Product: latte-dock Version: git (master) Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: tr...@yandex.com Target Milestone: --- SUMMARY Window thumbnails with media buttons disappear when I hover the mouse over the buttons STEPS TO REPRODUCE 1. Play a song in Cantata 2. Hover the mouse over the Cantata icon to show the window thumbnail 3. Hover the mouse over the media buttons EXPECTED RESULT The window thumbnail keep displaying. Plasma Taskmanager behavior: https://streamable.com/cvwui ACTUAL RESULT The window thumbnail disappears. Latte-dock behavior: https://streamable.com/4upyj SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.49.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398962] Window thumbnails with media buttons disappear when I hover the mouse over the buttons
https://bugs.kde.org/show_bug.cgi?id=398962 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 398963] New: Background disappears instead of blurring
https://bugs.kde.org/show_bug.cgi?id=398963 Bug ID: 398963 Summary: Background disappears instead of blurring Product: kscreenlocker Version: 5.10.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: breeze-theme Assignee: plasma-b...@kde.org Reporter: beo...@gmail.com CC: bhus...@gmail.com Target Milestone: --- When the mouse is moved to activate the controls on the lock screen, instead of blurring, the background fades to black. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398962] Window thumbnails with media buttons disappear when I hover the mouse over the buttons
https://bugs.kde.org/show_bug.cgi?id=398962 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||0.8.2 Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/lat ||te-dock/beb28b1a9fa5e451b0e ||898d6ed7882b7cc184f82 --- Comment #1 from Michail Vourlakos --- Git commit beb28b1a9fa5e451b0e898d6ed7882b7cc184f82 by Michail Vourlakos. Committed on 22/09/2018 at 17:59. Pushed by mvourlakos into branch 'master'. dont hide preview when hovering player buttons --when the user was hovering the preview player buttons the preview was hiding itself. This patch fixes the situation in order to identify properly that the mouse is still in the preview in such case. FIXED-IN: 0.8.2 M +16 -6plasmoid/package/contents/ui/ToolTipInstance.qml https://commits.kde.org/latte-dock/beb28b1a9fa5e451b0e898d6ed7882b7cc184f82 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368287] Dolphin crashed while moving files
https://bugs.kde.org/show_bug.cgi?id=368287 --- Comment #20 from Pavel --- Created attachment 115169 --> https://bugs.kde.org/attachment.cgi?id=115169=edit New crash information added by DrKonqi dolphin (18.08.1) using Qt 5.11.1 - What I was doing when the application crashed: Moving a few files from my home folder (ext4) to ntfs partition. -- Backtrace (Reduced): #6 0x7f7aaf25da84 in KJob::isAutoDelete() const () from /usr/lib64/libKF5CoreAddons.so.5 #7 0x7f7aaf25daeb in KJob::finishJob(bool) () from /usr/lib64/libKF5CoreAddons.so.5 #8 0x7f7aafab6fe9 in KIO::FileCopyJob::slotResult(KJob*) () from /usr/lib64/libKF5KIOCore.so.5 [...] #10 0x7f7aaf25d01c in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib64/libKF5CoreAddons.so.5 #11 0x7f7aaf25dae3 in KJob::finishJob(bool) () from /usr/lib64/libKF5CoreAddons.so.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368287] Dolphin crashed while moving files
https://bugs.kde.org/show_bug.cgi?id=368287 Pavel changed: What|Removed |Added CC||a...@pavel.bz -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398957] 5.0.2 KDE Neon
https://bugs.kde.org/show_bug.cgi?id=398957 --- Comment #1 from Thomas Baumgart --- Git commit 5c8cbc29a0807bd0dd76c8b5e22411a098ee12d8 by Thomas Baumgart. Committed on 22/09/2018 at 18:30. Pushed by tbaumgart into branch '5.0'. Fix the start with last selected view feature Closing the file switches to the home view and that was stored last so the feature was not working properly. This has now been fixed by not storing the view change when no file/db is opened. Also, the switch to the default view is postponed until the event loop is running. Otherwise, the view was not displayed properly. FIXED-IN: 5.0.2 M +5-4kmymoney/kmymoney.cpp M +3-1kmymoney/views/kmymoneyview.cpp M +1-1kmymoney/views/kmymoneyview.h https://commits.kde.org/kmymoney/5c8cbc29a0807bd0dd76c8b5e22411a098ee12d8 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 398927] ‘folder-open’ icon looks identical to ‘document-open’ icon at small sizes
https://bugs.kde.org/show_bug.cgi?id=398927 Andres Betts changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #3 from Andres Betts --- I would be in favor of using different icons in this case, or adding labels to the buttons. Either way would make it more clear. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393635] Segfault when saving TIFF after modifying RAW
https://bugs.kde.org/show_bug.cgi?id=393635 --- Comment #15 from Victor Engmark --- I have reported this to the Exiv2 project at https://dev.exiv2.org/issues/1347 and they say it's not an Exiv2 issue. When I run `exiv2 [offending file]` the first line printed is > Warning: Directory Image3, entry 0x0111: Strip 0 is outside of the data area; > ignored. Could it be that Digikam does not handle this warning? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 339370] Add support for using The Unarchiver for CBR files
https://bugs.kde.org/show_bug.cgi?id=339370 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 367700] It should be possible to search for more, if not all metadata fields.
https://bugs.kde.org/show_bug.cgi?id=367700 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- Can you provide a test image with metadata to get an idea of which tags are not processed. DigiKam already supports "Xmp.mediapro.CatalogSets". Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398965] New: Kwin won't start with 100% CPU
https://bugs.kde.org/show_bug.cgi?id=398965 Bug ID: 398965 Summary: Kwin won't start with 100% CPU Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m...@nbrogi.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE Try to launch Wwin via terminal EXPECTED RESULT Kwin should start ACTUAL RESULT Kwin doesn't start, doesn't report errors, and uses 100% CPU SOFTWARE VERSIONS (available in About System) KDE Plasma Version: N/A (running on Xfce) KDE Frameworks Version: Kwin v. 5.12.6 Qt Version: 5.9.5 ADDITIONAL INFORMATION Following no particular event or configuration that I can remember, I am all of a sudden unable to run Kwin. When I try to start it, it starts using 100% CPU and hangs with me having no window manager. In addition, I'm unable to kill the process with "killall kwin", and I actually have to look up the pid and do "kill -9". I tried purging and re-installing, to no avail, even after removing ~/.kde/. What could be the cause, or a way to figure out what it's doing..? The terminal doesn't print ANYTHING, it just hangs. The same thing happens if I create a brand-new user and try to start Kwin from a brand-new session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398967] New: Media player hides itself in the system tray after the player to start the next video playback
https://bugs.kde.org/show_bug.cgi?id=398967 Bug ID: 398967 Summary: Media player hides itself in the system tray after the player to start the next video playback Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Media Player Assignee: k...@privat.broulik.de Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. open dolphin, select two or more video files, right click any selected file 2. select "open with vlc" 3. in vlc player, play the next video from the playlist by clicking the button aside the stop button EXPECTED RESULT media player applet remains visible in the system tray ACTUAL RESULT ~2 seconds after vlc to start the next video playback, media player applet hides itself in the system tray, it appears in "notifications and status" together other hidden icons. Both progress bar and play/pause button of the applet stop working. SOFTWARE VERSIONS Sistema operacional: KDE neon Developer Edition Versão do KDE Plasma: 5.14.80 Versão da Qt: 5.11.1 Versão do KDE Frameworks: 5.51.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398624] Cannot edit Date in XMP video metadata
https://bugs.kde.org/show_bug.cgi?id=398624 --- Comment #8 from IWBR --- Thank you all, you're the best! -- You are receiving this mail because: You are watching all bug changes.
