[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 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 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 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.
[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 #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.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 --- Comment #28 from Anders Lund --- This is idiotic. Digikam deletes my files, dolphin does not, because it have functional file management. Digikam does not, and unlinks files without ensuring that they are actually written. But hey, I have decided not to use digikam any longer, for this specific reason. torsdag den 30. juli 2020 11.34.57 CEST skrev du: > 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 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 2wxsy5823...@opayq.com changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from 2wxsy5823...@opayq.com --- Maybe it is related to the image downscaling algorithm of Okular? I can reproduce the issue by comparing the image side-by-side with Okular and Gwenview: 1. Open the source image in Gwenview. 2. Resize the Gwenview window so that the image is displayed at 75% zoom. 3. Pay attention to the letter "d" in "Wir durften" and you will notice the difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424064] Show a notification count in the tray icon
https://bugs.kde.org/show_bug.cgi?id=424064 Claudius Ellsel changed: What|Removed |Added Resolution|INTENTIONAL |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #6 from Claudius Ellsel --- I reopen since there hasn't been activity for over one week after my announcement in comment #5. -- 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 #4 from Jazeix Johnny --- Maybe https://bugreports.qt.io/browse/QTBUG-68139. It is not an issue specific to GCompris, I'll still try to check this week-end if I can reproduce. -- 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 #7 from Peter Eilers --- Hi there, probably: yes; but I'm sorry: not from me until mid of August since I'm moving at the time; likely to be September... Greets,Peter *Gesendet:* Donnerstag, 30. Juli 2020 um 11:45 Uhr *Von:* bugzilla_nore...@kde.org *An:* peter.eil...@gmx.net *Betreff:* [digikam] [Bug 391044] digikam crashed when trying to open a Dir on an iPad via usbhttps://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 on the CC list for the bug. -- 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.
[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.
[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 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.
[okular] [Bug 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 2wxsy5823...@opayq.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=408222 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408222] Okular is bad in displaying of scanned PDF ! Please fix this !
https://bugs.kde.org/show_bug.cgi?id=408222 2wxsy5823...@opayq.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=424817 -- 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 #14 from Patrick Silva --- The crash is still happening on both X11 and Wayland sessions. 1. set application style to Oxygen in system settings > application style 2. open smb4k 3. click on "File" menu, choose "Quit" -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 424794] Cannot build on Ubuntu 18.04 (#include is not found)
https://bugs.kde.org/show_bug.cgi?id=424794
Ralf Habacker changed:
What|Removed |Added
CC||ralf.habac...@freenet.de
--- Comment #2 from Ralf Habacker ---
(In reply to Robert Hairgrove from comment #1)
> Seems like CMake is creating an extra ThreadWeaver subdirectory under
> /usr/include/KF5/ThreadWeaver?
which is provided by the threadewever development package
$ rpm -q -f /usr/include/KF5/ThreadWeaver/
threadweaver-devel-5.55.0-lp151.1.1.x86_64
This package also provides the associated cmake config files to support
find_package().
grep -rn INCLUDE /usr/lib64/cmake/KF5ThreadWeaver/KF5ThreadWeaverTargets.cmake
66: INTERFACE_INCLUDE_DIRECTORIES
"${_IMPORT_PREFIX}/include/KF5/ThreadWeaver;${_IMPORT_PREFIX}/include/KF5"
At least on opensuse leap 15.1 it includes the initial mentioned directoy and
should be added to the compile line by default.
running
make VERBOSE=1
gives some more hints which directories are included.
--
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 #4 from Dmitry Kazakov --- Hi, Aaron! Could you please test this package: https://yadi.sk/d/LwK1uXxECb5k4w This package should fix the halo effect. But most importantly I need to know if it causes some other unexpected regressions. There is a detailed explanation of what testing is needed in this merge request: https://invent.kde.org/graphics/krita/-/merge_requests/452 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 424592] Sidebarview does not render after suspend
https://bugs.kde.org/show_bug.cgi?id=424592 --- Comment #7 from Sergey --- I confirm the relevance to https://bugs.kde.org/show_bug.cgi?id=424311 After downgrading nvdia-driver to 440.100 I don't see the black sidebar after resume anymore. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424844] "Detach canvas" still toggled in View menu after closing detached canvas
https://bugs.kde.org/show_bug.cgi?id=424844 Tymond changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- Checked and confirmed. Interestingly, when closing the window with detached canvas, it just returns to undetached state, which seems quite nice. But yeah, the checkbox is wrong then. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424846] Krita crashes on closing [Solus OS]
https://bugs.kde.org/show_bug.cgi?id=424846 Tymond changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- Does it always crash on close? Then it seems to be a duplicate of bug 417465. If you mean something else, I'm sorry, but the crash report doesn't contain any information and your steps to reproduce are too broad. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424846] New: Krita crashes on closing [Solus OS]
https://bugs.kde.org/show_bug.cgi?id=424846 Bug ID: 424846 Summary: Krita crashes on closing [Solus OS] Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: arnaud...@vivaldi.net Target Milestone: --- Created attachment 130528 --> https://bugs.kde.org/attachment.cgi?id=130528=edit Crash report SUMMARY STEPS TO REPRODUCE 1. Launch krita 2. Do some work or not 3. close krita OBSERVED RESULT krita crashes straight EXPECTED RESULT krita should close normally and crash not SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION For system info see attached document (crash report) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424847] New: "Detach canvas" setting isn't remembered after closing Krita
https://bugs.kde.org/show_bug.cgi?id=424847 Bug ID: 424847 Summary: "Detach canvas" setting isn't remembered after closing Krita Product: krita Version: 4.3.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- SUMMARY Having a detached canvas isn't remembered by Krita after closing it. Starting Krita always uses an attached canvas. STEPS TO REPRODUCE 1. Detach canvas 2. Close Krita 3. Open Krita OBSERVED RESULT Canvas is attached. EXPECTED RESULT Canvas is detached. SOFTWARE/OS VERSIONS I'm using the appimage so I'm not sure if it matters, but: Linux/KDE Plasma: Debian sid (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Combined with https://bugs.kde.org/show_bug.cgi?id=424845, this makes it difficult for someone to implement the detached canvas into their workflow, since both of these have to be configured every time. -- 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 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.1.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #9 from caulier.gil...@gmail.com --- Thanks for your feebacks. I close this file now. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418083] Discover does not list Snap apps when we browse through the apps nor when we search for their names. But Discover lists them when we search for "snap".
https://bugs.kde.org/show_bug.cgi?id=418083 --- Comment #1 from Aleix Pol --- Last I checked, snap didn't have the concept of a category. Maybe that's changed now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424843] New: Constantly glitching when just drawing lines or doing dots or anything really. It gets extremely frustrating and time consuming. Also the zoom effect is very glitchy as well
https://bugs.kde.org/show_bug.cgi?id=424843 Bug ID: 424843 Summary: Constantly glitching when just drawing lines or doing dots or anything really. It gets extremely frustrating and time consuming. Also the zoom effect is very glitchy as well Product: krita Version: 4.3.0 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: al3x2...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 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.
[krita] [Bug 424844] New: "Detach canvas" still toggled in View menu after closing detached canvas
https://bugs.kde.org/show_bug.cgi?id=424844 Bug ID: 424844 Summary: "Detach canvas" still toggled in View menu after closing detached canvas Product: krita Version: 4.3.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- SUMMARY After closing a detached canvas, the "Detach canvas" setting listed under View is still toggled, and requires clicking twice to detach the canvas again. STEPS TO REPRODUCE 1. Detach the canvas 2. Close the detached canvas 3. Attempt to detach the canvas again OBSERVED RESULT "Detach canvas" is still toggled. Untoggling it does nothing. Have to click it again to actually detach the canvas. EXPECTED RESULT "Detached canvas" should be untoggled. Clicking it should have detached it the first time. SOFTWARE/OS VERSIONS I'm using the appimage so I'm not sure if it matters, but: Linux/KDE Plasma: Debian sid (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Detaching the canvas through Window layouts produces the same problem in reverse. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424845] Detaching the canvas annoyingly resizes the dockers to much larger sizes
https://bugs.kde.org/show_bug.cgi?id=424845 --- Comment #2 from tomtomtomreportin...@gmail.com --- Combined with https://bugs.kde.org/show_bug.cgi?id=424847, this makes it difficult for someone to implement the detached canvas into their workflow, since both of these have to be configured every time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420612] Krita: Segmentation fault when closing
https://bugs.kde.org/show_bug.cgi?id=420612 Lynx3d changed: What|Removed |Added CC||d...@dccathome.com --- Comment #9 from Lynx3d --- *** Bug 424840 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424847] "Detach canvas" setting isn't remembered after closing Krita
https://bugs.kde.org/show_bug.cgi?id=424847 --- Comment #2 from tomtomtomreportin...@gmail.com --- I can understand how it would be intentional, especially since I can forsee potential problems with the Start screen, but it would be nice to have as an option at least. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424840] krita
https://bugs.kde.org/show_bug.cgi?id=424840 Lynx3d changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||lynx.mw+...@gmail.com --- Comment #1 from Lynx3d --- That stack trace looks pretty familiar by now... *** This bug has been marked as a duplicate of bug 420612 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424843] Constantly glitching when just drawing lines or doing dots or anything really. It gets extremely frustrating and time consuming. Also the zoom effect is very glitchy as well
https://bugs.kde.org/show_bug.cgi?id=424843 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Tymond --- Hi, this is way too little information for us to be able to help you, and the issue you mentioned is unlikely to be a problem in Krita's code because issues like that can often be fixed or mitigated with different configuration. In any case, it'd be much better if you could please go to krita-artists.org and ask for help there. This website here - bugs.kde.org - is strictly development-oriented, not user support-oriented; while krita-artists.org is user-oriented and much more user-friendly than here. Someone will help you investigate the issue and find a remedy. If there is in fact a bug found, and the user supporter confirms there is a bug, they will help you describe it to make the bug report helpful for developers. You can read more here for details: https://docs.krita.org/en/untranslatable_pages/reporting_bugs.html It's generally recommended that if you feel like you've found a bug, go to the user forum and ask about it, because sometimes there is already bug report made, or maybe it's already fixed, or maybe there are other solutions you could try first. But thanks for taking an active role and trying to report. That's important for the community. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 417987] Discover should update addons installed via GHNS windows
https://bugs.kde.org/show_bug.cgi?id=417987 --- Comment #1 from Aleix Pol --- Probably related to https://bugs.kde.org/show_bug.cgi?id=421924. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 421924] Discover doesn't find updates for plasma addons unless I open their respective "Get new " windows in system settings before
https://bugs.kde.org/show_bug.cgi?id=421924 --- Comment #1 from Aleix Pol --- Probably related to #417987. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400701] plasma crash on QXcbConnection::getSelectionOwner
https://bugs.kde.org/show_bug.cgi?id=400701 Tony changed: What|Removed |Added CC||jodr...@live.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424845] Detaching the canvas annoyingly resizes the dockers to much larger sizes
https://bugs.kde.org/show_bug.cgi?id=424845 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Tymond --- Yes :( -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424596] Double clicking on a 'recent' open file will open 2 copies of the file.
https://bugs.kde.org/show_bug.cgi?id=424596 tomtomtomreportin...@gmail.com changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com --- Comment #3 from tomtomtomreportin...@gmail.com --- This report led me to finding a related trick: If you click multiple different recent files in quick succession, you can open multiple files at once. Likely unintended, but likely not worth fixing either. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367524] Auto Keyframe: Blank & Duplicate Frame Modes
https://bugs.kde.org/show_bug.cgi?id=367524 Emmet O'Neill changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/7eb7e0db9 ||697772d32945580d03d4c7fae27 ||54d2 Resolution|--- |FIXED --- Comment #3 from Emmet O'Neill --- Git commit 7eb7e0db9697772d32945580d03d4c7fae2754d2 by Emmet O'Neill. Committed on 31/07/2020 at 03:49. Pushed by emmetoneill into branch 'master'. Feature: Blank and Duplicate AutoKey Modes. AutoKey (a.k.a. "lazy frame") now has two selectable modes, blank and duplicate. Blank mode creates a new blank keyframe automatically each time the animator draws on an empty frame, while duplicate mode keeps the old functionality by creating a duplicate frame. M +10 -0libs/image/kis_image_config.cpp M +3-0libs/image/kis_image_config.h M +7-4libs/image/kis_transaction_data.cpp M +41 -8plugins/dockers/animation/timeline_docker.cpp M +6-2plugins/dockers/animation/timeline_docker.h https://invent.kde.org/graphics/krita/commit/7eb7e0db9697772d32945580d03d4c7fae2754d2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418038] search bar is cut in compact/mobile view
https://bugs.kde.org/show_bug.cgi?id=418038 Aleix Pol changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Aleix Pol --- I don't see it now, maybe it got fixed meanwhile? -- 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 #8 from Cengiz Gunay --- (In reply to caulier.gilles from comment #1) > Which kind of database type do you use ? Mysql or sqlte ? > > Where are stored your database file ? On the NFS mount path, in local, or in > a remote server ? Sorry for not replying to this earlier. I didn't know how to look it up. It's a QSQLITE backend, but it's saved on a local drive, not the NFS drive. (In reply to caulier.gilles from comment #7) > Try to start Appimage bundle with a preload a library like this : > > LD_PRELOAD=/usr/lib64/libxcb-dri3.so.0 ./digikam-7.0.0-x86-64.appimage > > Name and path to libxcb can change in different system. > > Gilles Caulier This worked, and I can confirm that I'm no longer getting crashes in the 7.0.0 version while browsing the NFS folders. Actually, I tried to track the crash down by running the system-installed version of DigiKam, but apparently it's already upgraded to 6.4.0, which also doesn't exhibit any crashes. It's quite slow because it's constantly scanning the files (it's a large database), but still functions. Also tried ShowFoto 6.4.0 because I wasn't sure if the crash was from there, but it also works. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424845] New: Detaching the canvas annoyingly resizes the dockers to much larger sizes
https://bugs.kde.org/show_bug.cgi?id=424845 Bug ID: 424845 Summary: Detaching the canvas annoyingly resizes the dockers to much larger sizes Product: krita Version: 4.3.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- SUMMARY Detaching the canvas will resize the dockers (I would assume in order to match the previous window size), which one might not expect. STEPS TO REPRODUCE 1. Observe current docker sizes 2. Detach canvas 3. Observe new docker sizes OBSERVED RESULT Dockers are enlargened. EXPECTED RESULT Docker sizes should stay the same after detaching the canvas. SOFTWARE/OS VERSIONS I'm using the appimage so I'm not sure if it matters, but: Linux/KDE Plasma: Debian sid (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION The dockers stay huge after reattaching the canvas. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424847] "Detach canvas" setting isn't remembered after closing Krita
https://bugs.kde.org/show_bug.cgi?id=424847 Tymond changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- I'm confirming that it happens, though I cannot tell if it's intentional or not. And even then, it could be considered a wish... -- 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 #10 from Cengiz Gunay --- You're welcome. Thanks for working on this nice tool! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 424832] New: The site won't open
https://bugs.kde.org/show_bug.cgi?id=424832 Bug ID: 424832 Summary: The site won't open Product: amarok Version: kf5 Platform: Snap URL: http://newtours.demoaut.com/ OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Collection Browser Assignee: lambertsenecadevelo...@gmail.com Reporter: profstanleysen...@gmail.com Target Milestone: kf5 SUMMARY STEPS TO REPRODUCE 1. I checked in different browswers 2. I waited for 24 hours and tried many times 3. I contacted my team members to check as well OBSERVED RESULT The system did not open EXPECTED RESULT The newtours website should have opened SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Please we have a deadline try and be fast and effective. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 424832] The site won't open
https://bugs.kde.org/show_bug.cgi?id=424832 Professor Stanley changed: What|Removed |Added Status|RESOLVED|VERIFIED -- 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 Avinash Sonawane changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #10 from Avinash Sonawane --- `export QMAKESPEC="linux-clang"` fixed the issue since `qml_box2d` uses `qmake` and that's how one changes the compiler used by `qmake`. -- 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 Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/4a50d2f59 |hics/krita/commit/b9df04d61 |31b5a414c9e48b23000e3d9212c |453401db48152ca84c6936990c1 |f145|7552 --- Comment #5 from Dmitry Kazakov --- Git commit b9df04d61453401db48152ca84c6936990c17552 by Dmitry Kazakov. Committed on 30/07/2020 at 14:08. Pushed by dkazakov into branch 'master'. Fix layer index generation algorithm Now the index is assigned to a layer dynamically. We just iterate over all the existing layers, find ones with index in the end of the name, choose the maximum one and create a new layer with index (maxIndex + 1). # Conflicts: # libs/image/kis_image.cc M +18 -14 libs/image/kis_image.cc M +0-5libs/image/kis_image.h M +0-1plugins/impex/libkra/kis_kra_loader.cpp https://invent.kde.org/graphics/krita/commit/b9df04d61453401db48152ca84c6936990c17552 -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 424832] The site won't open
https://bugs.kde.org/show_bug.cgi?id=424832 Christoph Feck changed: What|Removed |Added Target Milestone|kf5 |--- Version|kf5 |unspecified Product|amarok |unknown Component|Collection Browser |general --- Comment #5 from Christoph Feck --- Please stop (ab)using our bug tracker for your lessons. If you are not responsible for selecting it, please ask your mentor. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 408310] Restarting plasmashell breaks Task Manager keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=408310 --- Comment #4 from Thiago Sueto --- Hello, I noticed another thing: plasmashell --replace == breaks task manager shortcuts killall plasmashell ; plasmashell == doesn't break task manager shortcuts Can you reproduce this? -- 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 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|FIXED |--- --- Comment #11 from Christoph Feck --- (resetting status) -- 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 #12 from Bryson --- Created attachment 130519 --> https://bugs.kde.org/attachment.cgi?id=130519=edit Screenshot of compositor working under same Nvidia graphics driver, whereas before reboot it did not work. This is a screenshot of the settings screens in Plasma showing data whereas before there was only a black box. I simply ran the command `env KWIN_GL_DEBUG=1 QT_LOGGING_RULES="kwin_scene_opengl.debug=true" kwin_x11 --replace`and restarted the system and now it works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424725] Clipboard not clearing items anymore, reboot doesn't solve the problem
https://bugs.kde.org/show_bug.cgi?id=424725 --- Comment #6 from Lua --- It didn't work. I attach a video showing that it didn't solve. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424725] Clipboard not clearing items anymore, reboot doesn't solve the problem
https://bugs.kde.org/show_bug.cgi?id=424725 --- Comment #5 from Lua --- Created attachment 130520 --> https://bugs.kde.org/attachment.cgi?id=130520=edit plasmashell --replace doesn't solve -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424834] New: Segfault in libwayland-server.so after upgrading to 5.19.4
https://bugs.kde.org/show_bug.cgi?id=424834 Bug ID: 424834 Summary: Segfault in libwayland-server.so after upgrading to 5.19.4 Product: kwin Version: 5.19.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- SUMMARY Following an update of my system to 5.19.4 plasma package I can't open a wayland session anymore. Instead I receive the following segfault after entering my password on the login screen: kwin_wayland[170551]: segfault at 0 ip 7f8cf8fc1027 sp 7ffd4c683788 error 4 in libwayland-server.so.0.1.0[7f8cf8fbc000+8000] SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION The following updates were performed prior to the problem occurring: Thu Jul 30 06:29:51 2020 >>> kde-plasma/breeze-grub-5.19.4 Thu Jul 30 06:30:41 2020 >>> net-misc/rsync-3.2.2-r1 Thu Jul 30 06:31:55 2020 >>> sys-kernel/gentoo-sources-5.7.11 Thu Jul 30 06:32:15 2020 >>> dev-python/pip-20.2 Thu Jul 30 06:39:37 2020 >>> sys-devel/gdb-9.2 Thu Jul 30 06:44:07 2020 >>> dev-python/pandas-1.1.0 Thu Jul 30 06:50:57 2020 >>> sys-apps/systemd-245.5 Thu Jul 30 06:51:09 2020 >>> kde-plasma/kwallet-pam-5.19.4 Thu Jul 30 06:51:26 2020 >>> kde-plasma/plasma-workspace-wallpapers-5.19.4 Thu Jul 30 07:59:40 2020 >>> www-client/chromium-84.0.4147.105 Thu Jul 30 07:59:53 2020 >>> kde-plasma/breeze-plymouth-5.19.4 Thu Jul 30 08:00:12 2020 >>> kde-plasma/kdecoration-5.19.4 Thu Jul 30 08:01:12 2020 >>> kde-plasma/libkscreen-5.19.4 Thu Jul 30 08:02:17 2020 >>> kde-plasma/kwayland-server-5.19.4 Thu Jul 30 08:02:36 2020 >>> kde-plasma/kgamma-5.19.4 Thu Jul 30 08:02:55 2020 >>> kde-plasma/kwayland-integration-5.19.4 Thu Jul 30 08:03:14 2020 >>> kde-plasma/xembed-sni-proxy-5.19.4 Thu Jul 30 08:03:32 2020 >>> kde-plasma/polkit-kde-agent-5.19.4 Thu Jul 30 08:03:45 2020 >>> kde-plasma/ksshaskpass-5.19.4 Thu Jul 30 08:04:58 2020 >>> kde-plasma/drkonqi-5.19.4 Thu Jul 30 08:05:12 2020 >>> kde-plasma/kwrited-5.19.4 Thu Jul 30 08:06:11 2020 >>> kde-plasma/kactivitymanagerd-5.19.4 Thu Jul 30 08:06:40 2020 >>> kde-plasma/kmenuedit-5.19.4 Thu Jul 30 08:07:05 2020 >>> kde-plasma/user-manager-5.19.4 Thu Jul 30 08:08:08 2020 >>> kde-plasma/libksysguard-5.19.4 Thu Jul 30 08:09:14 2020 >>> kde-plasma/discover-5.19.4 Thu Jul 30 08:10:14 2020 >>> kde-plasma/ksysguard-5.19.4 Thu Jul 30 08:10:50 2020 >>> kde-plasma/xdg-desktop-portal-kde-5.19.4 Thu Jul 30 08:11:35 2020 >>> kde-plasma/plasma-vault-5.19.4 Thu Jul 30 08:12:13 2020 >>> kde-plasma/plasma-pa-5.19.4 Thu Jul 30 08:12:52 2020 >>> kde-plasma/plasma-sdk-5.19.4 Thu Jul 30 08:13:15 2020 >>> kde-plasma/milou-5.19.4 Thu Jul 30 08:13:45 2020 >>> kde-plasma/plasma-browser-integration-5.19.4 Thu Jul 30 08:14:51 2020 >>> kde-plasma/breeze-5.19.4 Thu Jul 30 08:15:18 2020 >>> kde-plasma/plasma-integration-5.19.4 Thu Jul 30 08:15:33 2020 >>> kde-plasma/breeze-gtk-5.19.4 Thu Jul 30 08:16:13 2020 >>> kde-plasma/kscreenlocker-5.19.4 Thu Jul 30 08:25:01 2020 >>> kde-plasma/kwin-5.19.4 Thu Jul 30 08:25:26 2020 >>> kde-plasma/libkworkspace-5.19.4 Thu Jul 30 08:26:21 2020 >>> kde-plasma/kde-cli-tools-5.19.4 Thu Jul 30 08:34:47 2020 >>> kde-plasma/plasma-workspace-5.19.4 Thu Jul 30 08:36:29 2020 >>> kde-plasma/oxygen-5.19.4 Thu Jul 30 08:36:50 2020 >>> kde-plasma/kde-gtk-config-5.19.4 Thu Jul 30 08:39:43 2020 >>> kde-plasma/plasma-nm-5.19.4 Thu Jul 30 08:40:05 2020 >>> kde-plasma/sddm-kcm-5.19.4 Thu Jul 30 08:41:21 2020 >>> kde-plasma/khotkeys-5.19.4 Thu Jul 30 08:42:30 2020 >>> kde-plasma/kinfocenter-5.19.4 Thu Jul 30 08:43:10 2020 >>> kde-plasma/kscreen-5.19.4 Thu Jul 30 08:44:45 2020 >>> kde-plasma/powerdevil-5.19.4 Thu Jul 30 08:45:19 2020 >>> kde-plasma/systemsettings-5.19.4 Thu Jul 30 08:46:27 2020 >>> kde-plasma/bluedevil-5.19.4 Thu Jul 30 08:46:47 2020 >>> kde-plasma/plymouth-kcm-5.19.4 Thu Jul 30 08:54:25 2020 >>> kde-plasma/plasma-desktop-5.19.4 Thu Jul 30 08:56:31 2020 >>> kde-plasma/kdeplasma-addons-5.19.4 Thu Jul 30 08:56:41 2020 >>> kde-plasma/plasma-meta-5.19.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424725] Clipboard not clearing items anymore, reboot doesn't solve the problem
https://bugs.kde.org/show_bug.cgi?id=424725 --- Comment #7 from Nate Graham --- That wasn't supposed to solve the problem but rather provide logging information that might help me debug the issue. Can you provide the logging that I requested? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424725] Clipboard not clearing items anymore, reboot doesn't solve the problem
https://bugs.kde.org/show_bug.cgi?id=424725 --- Comment #9 from Nate Graham --- No. :) -- 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 #17 from Thomas Beckler --- Pardon for the late reply. Tested on the official release 7.0.0 and Digikam is not crashing. Thank you very much for the fix and the new release. It is working like a charm. I am looking forward to the new announced features! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 415150] Save window positions
https://bugs.kde.org/show_bug.cgi?id=415150 --- Comment #9 from Nate Graham --- So I've run into a bit of a conceptual issue here. I've created new functions KWindowConfig::saveWindowPosition() and KWindowConfig::restoreWindowPosition() in KConfig. We can automatically save the position of apps' main windows by calling the new saveWindowPosition() function from kxmlgui in KMainWindow, but to save the position of *every* window, we'd need to add a new KWindowConfig::saveWindowPosition() function call to every individual KDE app that calls KWindowConfig::saveWindowSize() for sub-windows, dialog windows, settings windows, etc. grep shows 92 such instances throughout the KDE apps I have source checkouts for. So this would be possible and feels most conceptually correct, but it would be a lot of work and in practice the roll-out would probably take months or years. An alternative you be to make KWindowConfig::saveWindowSize() automatically save the window's position as well. This would provide the feature for free for basically all KDE apps that already save the sizes of their windows. However doing this would make the function name inaccurate, and would represent a behavioral change that might be undesirable. Perhaps there are apps that manually save their window positions, though this is speculative and theoretical. Though in practice those would probably be exceptions and we could make them stop manually saving window positions when we find them. The other alternative is to abandon this idea and put work into making KWin do it instead (Bug 15329), which would fix this issue for all KDE app windows as well as all other 3rd-party app windows as well. Apparently that will eventually be possible on Wayland once some protocol is merged upstream, but we don't have enough information on X11 to do it. However perhaps that's something that can be overcome. If I had a nickel for every time a developer told me that something was technically impossible only for someone else to figure out how to get it done, I'd be a rich man! Comments welcome. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 424832] The site won't open
https://bugs.kde.org/show_bug.cgi?id=424832 Lambert Developer changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Lambert Developer --- Hi Prof Stanley, please check again we have fixed the problem -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 424832] The site won't open
https://bugs.kde.org/show_bug.cgi?id=424832 Lambert Developer changed: What|Removed |Added Status|VERIFIED|CLOSED --- Comment #3 from Lambert Developer --- Thanks -- 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 #3 from Dmitry Kazakov --- Git commit bbe18fad05e5b1796b80dccde901405b1369a8d8 by Dmitry Kazakov. Committed on 30/07/2020 at 14:06. Pushed by dkazakov into branch 'master'. 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/bbe18fad05e5b1796b80dccde901405b1369a8d8 -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 424833] New: The web page is showing error
https://bugs.kde.org/show_bug.cgi?id=424833 Bug ID: 424833 Summary: The web page is showing error Product: abakus Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: lambertsenecadevelo...@gmail.com Reporter: profstanleysen...@gmail.com Target Milestone: --- Created attachment 130518 --> https://bugs.kde.org/attachment.cgi?id=130518=edit The web error message SUMMARY The bug is on web error STEPS TO REPRODUCE 1. I check two times 2. My friend helped me 3. We worked with the PM 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.
[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 Sergey changed: What|Removed |Added CC||rion...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 408310] Restarting plasmashell breaks Task Manager keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=408310 --- Comment #5 from Patrick Silva --- (In reply to Thiago Sueto from comment #4) > Hello, I noticed another thing: > plasmashell --replace == breaks task manager shortcuts > killall plasmashell ; plasmashell == doesn't break task manager shortcuts > > Can you reproduce this? I can confirm on Arch Linux. Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424725] Clipboard not clearing items anymore, reboot doesn't solve the problem
https://bugs.kde.org/show_bug.cgi?id=424725 --- Comment #8 from Lua --- Oops, I recorded 2 videos, one of them was with terminal, but I got worried. Does the output include personal info? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424725] Clipboard not clearing items anymore, reboot doesn't solve the problem
https://bugs.kde.org/show_bug.cgi?id=424725 --- Comment #10 from Lua --- Created attachment 130521 --> https://bugs.kde.org/attachment.cgi?id=130521=edit plasma-shell --replace on terminal -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424725] Clipboard not clearing items anymore, reboot doesn't solve the problem
https://bugs.kde.org/show_bug.cgi?id=424725 --- Comment #11 from Lua --- Done! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424725] Clipboard not clearing items anymore, reboot doesn't solve the problem
https://bugs.kde.org/show_bug.cgi?id=424725 --- Comment #12 from Nate Graham --- I need to see the terminal output when you press the "clear history" button. :) -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 424835] New: Logic errors and some trivial errors as reported by scan-build
https://bugs.kde.org/show_bug.cgi?id=424835 Bug ID: 424835 Summary: Logic errors and some trivial errors as reported by scan-build Product: gcompris Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: bruno.coud...@gcompris.net Reporter: root...@gmail.com Target Milestone: --- Hello! Scan-build[0] reported 3 logic errors along with other trivial errors. Here is the report: https://rootkea.gitlab.io/gcompris/scan-build/ Please take a look at them. And here is the .gitlab-ci.yml which generated above report: https://gitlab.com/rootkea/gcompris/-/blob/gitlab-scan-build/.gitlab-ci.yml Thanks! [0] https://clang-analyzer.llvm.org/scan-build.html -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 417108] Command line operation fails
https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #20 from dolge...@informatik.uni-erlangen.de --- Having my KDE Neon dist-upgraded to Ubuntu20.04 and installed the latest Updates, I've got Kalarm now in "Version 2.14.3 (KDE Apps 20.04.3)", and finally commandline works™ again! Therefore, thank you very much for troubleshooting and fixing! -- 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 #5 from Aaron Lavarnway --- Hey Dmitri, Unfortunately I'm not primarily a painter so normal use for me and previous artworks likely won't produce any undesired effects. The one use case in which this bug was bothering me (coloring lineart non-destructively by overlaying the color on top of the lineart) works great in this build. That said I do understand that this is a core change to how the program processes the layer stack and will inherently change the output of some older files for others. While I'm unsure of how I can rigorously test the change myself, I'll be using this build for the next week or two just to see if anything very obvious sticks out to me during my usual workflow. As for the questions posed in the merge request, I'll give my personal opinion on. Keep in mind I'm likely not the kind of artist who would be most affected by this change. > The patch changes the behavior of "Normal" blending mode in "Inherit Alpha" > mode. Is this change acceptable? This behavior is acceptable as far as I can see. > May it cause harm to any existing files that painters own? While it may change how previous artwork is rendered, I have a hard time believing the changes will be considered a regression by artists. > Should we implement any backward compatibility mode? (It can only technically > be a global switch with Krita restart) I personally don't think backwards compatibility is necessary unless this change gets pushed and artists begin to ask for it. Which is something I don't see happening, in my opinion. > The patch may theoretically change how brushes in BuildUp mode (or > ColorSmudge engine) work in "Locked Alpha" mode. Can you reproduce any > changes in existing presets? I don't notice any changes to build-up mode or color smudge mode on Inherit Alpha layers, but painterly-style is not my area of expertise. Color Smudge engine does not work on 'Alpha-locked' layers or inside specific lasso selections, but that's a different bug entirely. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 424832] The site won't open
https://bugs.kde.org/show_bug.cgi?id=424832 Lambert Developer changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Lambert Developer --- I will look into this -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 424832] The site won't open
https://bugs.kde.org/show_bug.cgi?id=424832 --- Comment #4 from Professor Stanley --- Please check it again, it is still having the same problem -- 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 brys...@email.com changed: What|Removed |Added CC||brys...@email.com Resolution|--- |FIXED Status|CONFIRMED |NEEDSINFO --- Comment #10 from brys...@email.com --- Just wanted to confirm the issue and provide another data point for the requested command from Vlad: env KWIN_GL_DEBUG=1 QT_LOGGING_RULES="kwin_scene_opengl.debug=true" kwin_x11 --replace Icon theme "gnome" not found. kwin_scene_opengl: Initializing OpenGL compositing QGLXContext: Failed to create dummy context OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX TITAN X/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 450.57 OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 450.57 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.20.8 Linux kernel version: 5.6.18 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_scene_opengl: Initializing fences for synchronization with the X command stream kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) will use SYSTEM HEAP memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast). kwin_scene_opengl: OpenGL 2 compositing successfully initialized kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 2 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20092: Program/shader state performance warning: Vertex shader in program 1 is being recompiled based on GL state. Also, running the above command broke my session and I had to reboot :(. -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 424833] The web page is showing error
https://bugs.kde.org/show_bug.cgi?id=424833 Christoph Feck changed: What|Removed |Added Product|abakus |unknown Component|general |general Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Christoph Feck --- Please stop (ab)using our bug tracker for your lessons. If you are not responsible for selecting it, please ask your mentor. -- 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 #13 from Bryson --- Looks like the behavior was temporary. I'm having the issue once again as the original bug post. The navigation pane of my Plasma settings apps are now solid black. I apologize for bumping this bug so many times. -- 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 #16 from Wolfgang Bauer --- (In reply to Patrick Silva from comment #14) > The crash is still happening on both X11 and Wayland sessions. > > 1. set application style to Oxygen in system settings > application style > 2. open smb4k > 3. click on "File" menu, choose "Quit" Hm, that doesn't crash here anymore. (with Plasma 5.19.4) AFAICS, the fix (https://invent.kde.org/plasma/oxygen/-/merge_requests/1) has only been merged into the 5.19 branch though, not into master (that explains why it still crashes for you). -- 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 #5 from Nate Graham --- Unhelpful comment: by making it respect the scale factor on X11! :D I'm here all week, folks... -- 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 #17 from Wolfgang Bauer --- (In reply to Nate Graham from comment #15) > If it's crashing only when using Oxygen, should this be moved to Oxygen? This bug was originally reported for Breeze though. So it's probably better to open a new one for Oxygen. But see my previous comment, the only problem seems to be that the fix is missing in the master branch, i.e. 5.19 needs to be merged to master. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 424816] Cant copy files from Nikon via bluetooth
https://bugs.kde.org/show_bug.cgi?id=424816 Nate Graham changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |now...@gmail.com Component|general |general Product|dolphin |Bluedevil CC||n...@kde.org, ||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 424826] New: Krusader Mint 19.3 root mode login fails
https://bugs.kde.org/show_bug.cgi?id=424826 Bug ID: 424826 Summary: Krusader Mint 19.3 root mode login fails Product: krusader Version: 2.6.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: gh...@mail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY Krusader Mint 19.3 root mode login fails to login with correct password. STEPS TO REPRODUCE 1. 2. 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.
[plasmashell] [Bug 424573] Sensors search stops working after I reopen the widget settings
https://bugs.kde.org/show_bug.cgi?id=424573 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.20 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 424592] Sidebarview does not render after suspend
https://bugs.kde.org/show_bug.cgi?id=424592 --- Comment #9 from David Edmundson --- I'll try and upgrade and hope I can hit it -- 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 #9 from br1ghtc...@gmail.com --- (In reply to Vlad Zahorodnii from comment #4) > 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. kwin_scene_opengl: Initializing OpenGL compositing QGLXContext: Failed to create dummy context No provider of glXCreateContextAttribsARB found. Requires one of: GLX_ARB_create_context Application::crashHandler() called with signal 6; recent crashes: 1 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kwin_x11 path = /usr/bin pid = 1247424 KCrash: Arguments: /usr/bin/kwin_x11 --replace KCrash: Attempting to start /usr/lib/drkonqi kwin_core: Compositing is not possible [1]+ Stopped env KWIN_GL_DEBUG=1 QT_LOGGING_RULES="kwin_scene_opengl.debug=true" kwin_x11 --replace Sorry didn't see there's actually a 'Reply' button. -- You are receiving this mail because: You are watching all bug changes.
[kdf] [Bug 424827] New: Secondary partitions mounted on boot are listed twice in "Storage devices" kcm
https://bugs.kde.org/show_bug.cgi?id=424827 Bug ID: 424827 Summary: Secondary partitions mounted on boot are listed twice in "Storage devices" kcm Product: kdf Version: 20.04 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 130514 --> https://bugs.kde.org/attachment.cgi?id=130514=edit partitions listed twice SUMMARY When we install kdf, "Storage devices" kcm is created in System Settings, it lists partitions mounted on boot twice. Compare the attached screenshots please. STEPS TO REPRODUCE 1. use a system with more than one partition 2. set secondary partitions to be mounted on boot 3. reboot 4. open System Settings > Storage Devices OBSERVED RESULT secondary partitions mounted on boot are listed twice EXPECTED RESULT all partitions should be listed once SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION My fstab file: # UUID=4c1b8d88-ae03-4daa-9733-103cfeffdd81 /dev/sda3 / ext4rw,relatime 0 1 LABEL=SEAGATE /mnt/SEAGATE auto nosuid,nodev,nofail,x-gvfs-show 0 0 LABEL=2TB /mnt/2TB auto nosuid,nodev,nofail,x-gvfs-show 0 0 LABEL=WD /mnt/WD auto nosuid,nodev,nofail,x-gvfs-show 0 0 LABEL=WIN7 /mnt/WIN7 auto nosuid,nodev,nofail,x-gvfs-show 0 0 -- You are receiving this mail because: You are watching all bug changes.
[kdf] [Bug 424827] Secondary partitions mounted on boot are listed twice in "Storage devices" kcm
https://bugs.kde.org/show_bug.cgi?id=424827 --- Comment #2 from Patrick Silva --- *** Bug 405118 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
