[dolphin] [Bug 426299] New: archive.so does not unload after exiting an archive
https://bugs.kde.org/show_bug.cgi?id=426299 Bug ID: 426299 Summary: archive.so does not unload after exiting an archive Product: dolphin Version: 20.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: martin.tlus...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY when viewing an archive file (a .zip file in my case) on an usb stick, the stick cannot be unmounted even after exiting the archive file as the archive.so does not get unloaded. STEPS TO REPRODUCE 1. put an archive file (like a .zip) file on an ust stick 2. open the .zip file from within dolphin 3. exit the zip file again 4. try to unmount OBSERVED RESULT usb stick cannot be unmounted EXPECTED RESULT stick should be unmounted without problems Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 Kernel Version: 5.4.0-45-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7.6 GiB of RAM Graphics Processor: GeForce 940MX/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426185] digiKam starts more slowly than previous versions
https://bugs.kde.org/show_bug.cgi?id=426185 --- Comment #5 from Maik Qualmann --- Yes, great, the problem is fixed. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #99 from Maik Qualmann --- @Nghia, do you have a backtrace? Maik -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 387951] Tabbing to navigate in list of results is broken
https://bugs.kde.org/show_bug.cgi?id=387951 --- Comment #7 from Kishore Gopalakrishnan --- You are all right about tab vs arrow keys. However, there is one instance of buggy behaviour that persists: Steps to reproduce: 1. Make sure the 'terminate applications' and 'command line' runners are enabled. (Just to make this example work) 2. Type 'kill krun' 3. you will see a result to terminate krunner (the first highlighted result) and another one below it to runn the command 'kill krun' 4. Press tab repeatedly. OBSERVED RESULTS: Tabbing only between the settings button, the textbox, the close button, and the currently highlighted result (terminate krunner). EXPECTED BEHAVIOUR: Tabbing should also iterate over the other returned results, in addition to the close button, secondary actions, etc. PS: Sorry, I accidentally pressed 'save changes' before completing the comment. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 387951] Tabbing to navigate in list of results is broken
https://bugs.kde.org/show_bug.cgi?id=387951 --- Comment #6 from Kishore Gopalakrishnan --- You are all right about tab vs arrow keys. However, there is one instance of buggy behaviour that persists: Steps to reproduce: 1. Make sure the 'terminate applications' and 'command line' runners are enabled. (Just to make this example work) 2. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426157] Translation for "Default settings for window decoration" too long to fit in German
https://bugs.kde.org/show_bug.cgi?id=426157 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 CC||n...@kde.org Status|REPORTED|CONFIRMED Severity|minor |normal --- Comment #2 from Nate Graham --- It's even too long for English. This layout needs a bit of re-thinking so that long strings can fit, or else the string needs to be shortened. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426165] Side bar tabs title has big font and hard to hide/close by mouse
https://bugs.kde.org/show_bug.cgi?id=426165 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #3 from Nate Graham --- I'm sorry you don't like the new style. The title text does indeed respect your font size, but it's a bit bigger than whatever the general size is because it's, well, a title. :) We use larger fonts for titles all over the place. This is a common paradigm. It's true that the new view takes up a bit more vertical space, but it takes up much less horizontal space. Space has to come from somewhere. :) No free lunch, I'm afraid. There is in fact a button to hide the whole sidebar which looks like it didn't get added due to a different issue, which David alludes to. We're working on fixing that. Sorry for the breakage. In the meantime you can add it yourself to your toolbar. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425687] Anytime something is done within the animation workspace whether that is moving or creating a frame, Krita will stop responding and then close with no warning and without saving t
https://bugs.kde.org/show_bug.cgi?id=425687 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425729] Krita keeps crashing when I create a new file.
https://bugs.kde.org/show_bug.cgi?id=425729 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 396182] manual filter wheel or filter drawer option
https://bugs.kde.org/show_bug.cgi?id=396182 --- Comment #12 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 392266] Error in the thumbnail cache subsystem for files with international characters in names
https://bugs.kde.org/show_bug.cgi?id=392266 --- Comment #8 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425153] Many of the tools, such as the brush, line and selection tools, don't work.
https://bugs.kde.org/show_bug.cgi?id=425153 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425146] When opening tabs it glitches and disappears.
https://bugs.kde.org/show_bug.cgi?id=425146 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 419644] kdeinit 5 crashes when using dolphin
https://bugs.kde.org/show_bug.cgi?id=419644 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #30 from Nate Graham --- ...Because it's already been fixed. :) This bug report was correctly marked as a duplicate of Bug 421329 which was fixed in KDE Frameworks 5.74. Please don't re-open bugs if they're still affecting you because you don't have the fixed version yet. *** This bug has been marked as a duplicate of bug 421329 *** -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421329] New Global Shortcuts KCM: shortcuts to launch 3rd-party apps don't work
https://bugs.kde.org/show_bug.cgi?id=421329 --- Comment #37 from Nate Graham --- *** Bug 417495 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #98 from Minh Nghia Duong --- (In reply to caulier.gilles from comment #97) > Marcel, > > See my comment: > > https://bugs.kde.org/show_bug.cgi?id=426185#c4 > > The huge memory allocation at startup is now fixed by Nghia commit: > > https://invent.kde.org/graphics/digikam/-/commit/ > 28027b21d9fa4368eb2f2ad26dbb1cb33e274cce > > It still to check if the OpenCL memory leak from OpenCV is fixed with my > commit: > > https://invent.kde.org/graphics/digikam/commit/ > b5e3c5987a7380fdc5ce9a59ee5e62e6acbaf51b > > And if the another memory glitch is fixed by Maik commit: > > https://invent.kde.org/graphics/digikam/commit/ > 5102e32b4e9e308df760a45624832caa204d82c0 > > I will rebuild AppImage 64 bits this morning. > > Gilles Hi Gilles, Even with this version, the crash during face detection still occurs on my machine Nghia -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 Matt McDonald changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #29 from Matt McDonald --- How is this not confirmed yet? -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 --- Comment #28 from Matt McDonald --- Actually I've now discovered that this bug is even present on window actions. For example, the default KDE shortcut for "Close" is CTRL+W, which I kept, and added Meta+Shift+Q as an alternate. Neither work (and I tested the CTRL+W before I touched anything, and it doesn't work either). It seems that the majority of all of KDE's global shortcuts are broken. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425723] Digikam crashes after a while when detecting faces using multiple CPU cores
https://bugs.kde.org/show_bug.cgi?id=425723 --- Comment #23 from caulier.gil...@gmail.com --- Hi Simon, Please read also the story form this bug: https://bugs.kde.org/show_bug.cgi?id=426175 This touch code from git/master, for next 7.2.0 release. Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #97 from caulier.gil...@gmail.com --- Marcel, See my comment: https://bugs.kde.org/show_bug.cgi?id=426185#c4 The huge memory allocation at startup is now fixed by Nghia commit: https://invent.kde.org/graphics/digikam/-/commit/28027b21d9fa4368eb2f2ad26dbb1cb33e274cce It still to check if the OpenCL memory leak from OpenCV is fixed with my commit: https://invent.kde.org/graphics/digikam/commit/b5e3c5987a7380fdc5ce9a59ee5e62e6acbaf51b And if the another memory glitch is fixed by Maik commit: https://invent.kde.org/graphics/digikam/commit/5102e32b4e9e308df760a45624832caa204d82c0 I will rebuild AppImage 64 bits this morning. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426185] digiKam starts more slowly than previous versions
https://bugs.kde.org/show_bug.cgi?id=426185 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.2.0 --- Comment #4 from caulier.gil...@gmail.com --- Nghia, I confirm the fix about memory allocation at startup: https://i.imgur.com/lQ8DcFw.png As you can see, memory allocation at startup is really lower than before. Look also the amount of RAM available on this other VM that i use to test digiKam: only 4 Gb maximum. digiKam start fine as expected here. Maik, did you confirm ? Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426185] digiKam starts more slowly than previous versions
https://bugs.kde.org/show_bug.cgi?id=426185 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|7.2.0 | -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 426298] New: Display match count when searching text
https://bugs.kde.org/show_bug.cgi?id=426298 Bug ID: 426298 Summary: Display match count when searching text Product: kate Version: 20.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: search Assignee: kwrite-bugs-n...@kde.org Reporter: aobi10...@hotmail.com Target Milestone: --- Created attachment 131487 --> https://bugs.kde.org/attachment.cgi?id=131487=edit Preview of wishing feature I think it would be useful if kate displays match count when searching/finding text in a document. For instance, on the attachment picture, the window on the right side is an opening window of Sublime Text 3, I would like to request a similar feature like the 1 of 4 matches displayed at the bottom left corner of that window. STEPS TO REPRODUCE 1. Open a empty tab. 2. Type some text on text area. 3. press `Ctrl + F` and search for matches. OBSERVED RESULT Kate highlighting all the matches. EXPECTED RESULT Kate highlighting all the matches and Show the number of matches somewhere. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.4.60-2-MANJARO KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426185] digiKam starts more slowly than previous versions
https://bugs.kde.org/show_bug.cgi?id=426185 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- Thanks Nghia for your investigations and fixes. It's very appreciate. Note: look like you can auto comments a file in bugzilla directly when you commit using "CCBUGS: _bug _number_" macro include in your commit comment. Look for ex mine: https://invent.kde.org/graphics/digikam/commit/b5e3c5987a7380fdc5ce9a59ee5e62e6acbaf51b Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426185] digiKam starts more slowly than previous versions
https://bugs.kde.org/show_bug.cgi?id=426185 --- Comment #2 from Minh Nghia Duong --- Hi Maik, This issue has been fixed by implementing a shared private static pointer, under commit https://invent.kde.org/graphics/digikam/-/commit/28027b21d9fa4368eb2f2ad26dbb1cb33e274cce Nghia -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #96 from caulier.gil...@gmail.com --- Git commit b5e3c5987a7380fdc5ce9a59ee5e62e6acbaf51b by Gilles Caulier. Committed on 08/09/2020 at 03:11. Pushed by cgilles into branch 'master'. Fix typo with OpenCV environnement variable value used to disable OpenCL device for 3D accelerations Related: bug 423632 M +2-1core/app/main/main.cpp https://invent.kde.org/graphics/digikam/commit/b5e3c5987a7380fdc5ce9a59ee5e62e6acbaf51b -- 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 #11 from caulier.gil...@gmail.com --- Git commit b5e3c5987a7380fdc5ce9a59ee5e62e6acbaf51b by Gilles Caulier. Committed on 08/09/2020 at 03:11. Pushed by cgilles into branch 'master'. Fix typo with OpenCV environnement variable value used to disable OpenCL device for 3D accelerations Related: bug 426175 M +2-1core/app/main/main.cpp https://invent.kde.org/graphics/digikam/commit/b5e3c5987a7380fdc5ce9a59ee5e62e6acbaf51b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #95 from caulier.gil...@gmail.com --- Maik, Setting the 2nd environment variable OPENCV_OPENCL_RUNTIME=disabled is fine: https://github.com/opencv/opencv/blob/master/modules/core/src/ocl.cpp#L1151 For this one it's really "disabled" where the other one is "disable". Take a care to the typo with ending by 'd' or not. This is clearly an error prone syntax... Gilles -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 Hazmil Azis changed: What|Removed |Added Resolution|DUPLICATE |--- Version|5.18.3 |5.18.5 CC||hazmil.abda...@gmail.com Status|RESOLVED|REPORTED Ever confirmed|1 |0 Platform|openSUSE RPMs |Kubuntu Packages --- Comment #27 from Hazmil Azis --- I confirm this bug also appears on my new and updated Kubuntu 20.04.1 installation. I heavily use the shortcuts to quickly open apps. This works well in my previous Kubuntu 18.04 installation, my workflow is quite impaired without this functionality. Hopefully this can be resolved soon. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426266] hotkeys remapping with tab
https://bugs.kde.org/show_bug.cgi?id=426266 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 424947 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 424947] Can't create shortcuts with the Tab key
https://bugs.kde.org/show_bug.cgi?id=424947 Patrick Silva changed: What|Removed |Added CC||simon.sylvai...@gmail.com --- Comment #3 from Patrick Silva --- *** Bug 426266 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426294] Desktop background is desaturated on startup under Wayland
https://bugs.kde.org/show_bug.cgi?id=426294 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 399021 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399021] [Wayland] "Desaturate unresponsive applications..." effect remains even when the window is no longer frozen
https://bugs.kde.org/show_bug.cgi?id=399021 Patrick Silva changed: What|Removed |Added CC||v...@veqz.net --- Comment #13 from Patrick Silva --- *** Bug 426294 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #94 from caulier.gil...@gmail.com --- To Maik comment #89: Reading OpenCV source code give the solution: https://github.com/opencv/opencv/blob/master/modules/core/src/ocl.cpp#L2068 OPENCV_OPENCL_DEVICE=null has no effect. OPENCV_OPENCL_DEVICE=disable must work. OPENCV_OPENCL_DEVICE=:CPU: must work (see the parser https://github.com/opencv/opencv/blob/master/modules/core/src/ocl.cpp#L2034) Gilles -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426297] New: Okular crashinging when opening PDF
https://bugs.kde.org/show_bug.cgi?id=426297 Bug ID: 426297 Summary: Okular crashinging when opening PDF Product: okular Version: 1.10.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kct...@juno.com Target Milestone: --- Application: okular (1.10.2) Qt Version: 5.12.7 Frameworks Version: 5.71.0 Operating System: Linux 5.3.18-lp152.36-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.2" -- Information about the crash: Opening a pdf from Thunderbird that was dounloaded using Thunderbird. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb3b1f96f80 (LWP 13223))] Thread 7 (Thread 0x7fb385218700 (LWP 13229)): #0 0x7fb3aab4287d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb38708cfbb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7fb38708cba7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fb37700 (LWP 13228)): #0 0x7fb3aab4287d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb38708cfbb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7fb38708cba7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fb385a19700 (LWP 13227)): #0 0x7fb3aab4287d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb38708cfbb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7fb38708cba7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fb38621a700 (LWP 13226)): #0 0x7fb3aab4287d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb38708cfbb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7fb38708cba7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fb3979ad700 (LWP 13225)): #0 0x7fb3adb771d8 in read () from /lib64/libc.so.6 #1 0x7fb3a851d9a0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb3a84d6298 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb3a84d6720 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fb3a84d688c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fb3ae51119b in QEventDispatcherGlib::processEvents (this=0x7fb39b10, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fb3ae4b232a in QEventLoop::exec (this=this@entry=0x7fb3979acc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fb3ae2d810a in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7fb3ae981cd5 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7fb3ae2d98b2 in QThreadPrivate::start (arg=0x7fb3aebf9d80) at thread/qthread_unix.cpp:361 #10 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #11 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fb39fff2700 (LWP 13224)): #0 0x7fb3adb7b6db in poll () from /lib64/libc.so.6 #1 0x7fb3ab3b6307 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fb3ab3b7f3a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fb3a2de7300 in QXcbEventQueue::run (this=0x5569bd363e10) at qxcbeventqueue.cpp:228 #4 0x7fb3ae2d98b2 in QThreadPrivate::start (arg=0x5569bd363e10) at thread/qthread_unix.cpp:361 #5 0x7fb3aab3c4f9 in start_thread () from /lib64/libpthread.so.0 #6 0x7fb3adb85fbf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb3b1f96f80 (LWP 13223)): [KCrash Handler] #4 QScopedPointer >::operator-> (this=0x30008) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 #5 qGetPtrHelper > > (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1038 #6 QScreen::d_func (this=this@entry=0x3) at kernel/qscreen.h:69 #7 QScreen::size (this=this@entry=0x3) at kernel/qscreen.cpp:215 #8 0x7fb3aed4c6dd in QScreen::physicalDotsPerInchY (this=this@entry=0x3) at kernel/qscreen.cpp:246 #9 0x7fb3af8d7ce8 in QScrollerPrivate::setDpiFromWidget (this=this@entry=0x5569bd73c840, widget=) at util/qscroller.cpp:1035 #10 0x7fb3af8db0c8 in QScrollerPrivate::prepareScrolling (this=this@entry=0x5569bd73c840, position=...) at util/qscroller.cpp:1430 #11 0x7fb3af8dc56f in
[lattedock] [Bug 426268] System Tray Applet in Panel not working correctly
https://bugs.kde.org/show_bug.cgi?id=426268 --- Comment #4 from roger.guti.ra...@gmail.com --- Created attachment 131486 --> https://bugs.kde.org/attachment.cgi?id=131486=edit plasma_layout_2 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426268] System Tray Applet in Panel not working correctly
https://bugs.kde.org/show_bug.cgi?id=426268 --- Comment #3 from roger.guti.ra...@gmail.com --- Thank you for the quick answer. It was fixed by creating a new latte panel or just deleting the old System Tray applet from the old panel and adding it again later. Now both right-click and configuration work perfectly. I imported my layouts from the older version where I had the problem, so I guess it persisted in the new one too. I will leave the information here just in case: 1. It does work well with a new latte-panel. 2. I actually attach the old backup files I used when I imported them, before fixing it, in case it is useful if you want to look more into it. 3. I am not using Latte Systray Tweaks. 4. My Latte plasma version is 0.9.86 Again, thank you for the prompt response and the great work you do with latte-dock, and sorry for making you check what was a stupid error on my part! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426268] System Tray Applet in Panel not working correctly
https://bugs.kde.org/show_bug.cgi?id=426268 --- Comment #2 from roger.guti.ra...@gmail.com --- Created attachment 131485 --> https://bugs.kde.org/attachment.cgi?id=131485=edit plasma_layouts -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 426296] New: Astropy Install Failure
https://bugs.kde.org/show_bug.cgi?id=426296 Bug ID: 426296 Summary: Astropy Install Failure Product: kstars Version: 3.4.3 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: gary.jo...@bigpond.com Target Milestone: --- SUMMARY Polar Alignment and Plate Solving Work Initially, then fail STEPS TO REPRODUCE 1. Run in Simulator mode 2. Try to run Polar Alignment or Plate-Solving 3. Tested using Online & Offline Solver OBSERVED RESULT Error message : Python 3 and Astropy not installed. EXPECTED RESULT PA and Plate solving work as expected - no error message SOFTWARE/OS VERSIONS macOS: 10.14.6 ADDITIONAL INFORMATION When running'Options .../Astronomy.net/Setup':- - Homebrew installed - Python3 installed - Astropy will install when you click Ok But when I press OK I get the message 'Astropy install failure'. I have run the manual installer using Terminal : pip3 install astropy That seemed to work. PA seemed to work OK (on the simulator) the first time. Subsequent attempts did not work. I reinstalled OSX (for other reasons) and tried again. PA and plate solving worked OK - but only the FIRST TIE. Subsequent attempts failed. Attempting to re-install Astropy using 'pip3 install astropy' gives this message :- Requirement already satisfied: astropy in /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages (4.0.1.post1) Requirement already satisfied: numpy>=1.16 in /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages (from astropy) (1.19.1) Restarting KStars then trying to do a PA online, KStars seems to TRY to connect to astronomy.net to solve the first image :- "Upload complete. Waiting for astrometry.net solver to complete..." But it never completes - spinning wheel adjacent to "Stop" button just keeps spinning. After several minutes, the responder says 'Solver timed out', but the icon next to the 'Stop' button keeps spinning and KStars appears to keep waiting. If I stop the process and try again offline, I get this message :- "Astrometry.net uses python3 and the astropy package for plate solving images offline. These were not detected on your system." Same if I try again using Online. So there appears to be an issue with the way KStars accesses the resources needed to run Solver. Gary -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426245] Android emulator crashed on start
https://bugs.kde.org/show_bug.cgi?id=426245 --- Comment #3 from Damjan --- (In reply to Damjan from comment #2) > (In reply to Vlad Zahorodnii from comment #1) > > Are you using the dim inactive effect? > > Yes, I am... is it a common issue? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 425968] [Neon unstable] Starting some applications shows "ambiguous shortcut" window
https://bugs.kde.org/show_bug.cgi?id=425968 --- Comment #6 from Oded Arbel --- (In reply to andreas.sturmlechner from comment #5) > Related to recent changes in plasma-integration, see linked bug. I'm not sure why you think that issue is related - it has nothing to do with the "Donate" shortcut, and it is also not recent: that work has gone into master 4 months ago while the issue of conflicting "Donate" and "show hidden files" shortcut is less than a week old. I do thank you for pointing out the Standard Shortcuts module - I wasn't aware of it and it is likely the culprit of this new issue as well as the original. I'll investigate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426245] Android emulator crashed on start
https://bugs.kde.org/show_bug.cgi?id=426245 --- Comment #2 from Damjan --- (In reply to Vlad Zahorodnii from comment #1) > Are you using the dim inactive effect? Yes, I am... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426281] Energy Saving: show applications that inhibit power saving functionalities
https://bugs.kde.org/show_bug.cgi?id=426281 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- The battery Plasmoid shows this informatiom -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422050] Scrolling issues with PageDown/PageUp navigation
https://bugs.kde.org/show_bug.cgi?id=422050 --- Comment #13 from Keziolio --- Just to remind everyone, there's already !194 that was addressing this bug two months ago, by reverting to the old behavior. I can understand why you wouldn't want that patch given the circumstances, but really, the fix is sound, I shouldn't be still hearing people complain about this bug -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 426295] New: [Wayland] KRunner does not open on pressing global keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=426295 Bug ID: 426295 Summary: [Wayland] KRunner does not open on pressing global keyboard shortcut Product: krunner Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: aspotas...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY KRunner does not open on pressing global keyboard shortcut. STEPS TO REPRODUCE 1. Start a Plasma Wayland session 2. Run krunner on command line. e.g. in Konsole. I do this to make sure krunner doesn't crash. 3. Press Alt+F2 or Alt+Space OBSERVED RESULT Nothing happens. Konsole handles the pressed key combination, this indicates that the global shortcut hadn't been recognized. EXPECTED RESULT KRunner should open its search/run input line. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 32 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426294] New: Desktop background is desaturated on startup under Wayland
https://bugs.kde.org/show_bug.cgi?id=426294 Bug ID: 426294 Summary: Desktop background is desaturated on startup under Wayland Product: kwin Version: 5.19.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: v...@veqz.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Start and log in on Wayland. OBSERVED RESULT Desktop background is or immediately gets desaturated, showing a black-and-white background. EXPECTED RESULT Desktop background should not be desaturated. SOFTWARE/OS VERSIONS Linux/KDE Plasma: neon Stable KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION >From what I understand this is caused by a Kwin feature to desaturate unresponsive windows. Seems it's extra aggressive towards the desktop background in the beginning. As soon as one interacts with the desktop (right click on it), it returns to normal. -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 409795] KRunner Crashed At Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409795 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 410155] KRunner Doesn't Show/Keep Command History Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410155 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 421680] Krunner doesn't find any window on Wayland
https://bugs.kde.org/show_bug.cgi?id=421680 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422050] Scrolling issues with PageDown/PageUp navigation
https://bugs.kde.org/show_bug.cgi?id=422050 --- Comment #12 from Harrison Smith --- I'm running Debian Bullseye so my versions may be a little behind. I have Dolphin 20.04.3 and I thought there was no animation, though it may actually be there but much faster. I don't really mind it at that speed, though I would still prefer no animation. It is noticeable browsing the web in Konqueror 5.0.97. The touchpad scroll speed may have to do with the fact that I changed the libinput Coordinate Transformation Matrix to speed up the cursor. I'll do some more testing. Thanks for the invite to the session! I love to see a project that encourages collaboration, and I have to say I'm more satisfied overall with KDE than any other desktop since making the switch several months ago. Really an exemplar for FOSS project management. I'll see if I can make it. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 426292] kdevelop-python crash while parsing projects
https://bugs.kde.org/show_bug.cgi?id=426292 Sven Brauch changed: What|Removed |Added CC||m...@svenbrauch.de --- Comment #1 from Sven Brauch --- Hi, thank you for the report! Does your project happen to be open-source? That would help a lot in reproducing the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426293] New: All my Qt clients die when I disconnect my display
https://bugs.kde.org/show_bug.cgi?id=426293 Bug ID: 426293 Summary: All my Qt clients die when I disconnect my display Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: aleix...@kde.org Target Milestone: --- Might be a bug in QtWayland/client, used to bring the whole session down, now it's just Qt clients. Firefox and XWayland clients survive it. Here's a backtrace for kwrite, but I'm pretty sure all other QtGui processes crashed (I get like ~20 drkonqi SNI wanting attention). Application: KWrite (kwrite), signal: Aborted Content of s_kcrashErrorMessage: (null) [New LWP 33411] [New LWP 33412] [New LWP 33413] [New LWP 33414] [New LWP 33415] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". 0x7fd14e36a46f in poll () from /usr/lib/libc.so.6 [Current thread is 1 (Thread 0x7fd14a3e7d40 (LWP 33408))] Thread 6 (Thread 0x7fd13b159640 (LWP 33415)): #0 0x7fd14d73a6a2 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd141d7290c in ?? () from /usr/lib/dri/iris_dri.so #2 0x7fd141d71308 in ?? () from /usr/lib/dri/iris_dri.so #3 0x7fd14d7343e9 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd14e375293 in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7fd133159640 (LWP 33414)): #0 0x7fd14d73a6a2 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd141d7290c in ?? () from /usr/lib/dri/iris_dri.so #2 0x7fd141d71308 in ?? () from /usr/lib/dri/iris_dri.so #3 0x7fd14d7343e9 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd14e375293 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fd13b95a640 (LWP 33413)): #0 0x7fd14d73a6a2 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd141d7290c in ?? () from /usr/lib/dri/iris_dri.so #2 0x7fd141d71308 in ?? () from /usr/lib/dri/iris_dri.so #3 0x7fd14d7343e9 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd14e375293 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fd13c15b640 (LWP 33412)): #0 0x7fd14d73a6a2 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd141d7290c in ?? () from /usr/lib/dri/iris_dri.so #2 0x7fd141d71308 in ?? () from /usr/lib/dri/iris_dri.so #3 0x7fd14d7343e9 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd14e375293 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fd148dab640 (LWP 33411)): #0 0x7fd14e36a46f in poll () from /usr/lib/libc.so.6 #1 0x7fd14af60168 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fd14af11221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fd14eaafa9b in QEventDispatcherGlib::processEvents (this=0x7fd144000b60, flags=...) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #4 0x7fd14ea56eeb in QEventLoop::exec (this=this@entry=0x7fd148daabf0, flags=..., flags@entry=...) at ../../include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/global/qflags.h:141 #5 0x7fd14e877b8e in QThread::exec (this=) at ../../include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/global/qflags.h:121 #6 0x7fd14ed48a27 in QDBusConnectionManager::run (this=0x7fd14edb5d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /home/apol/devel/frameworks/qt5/qtbase/src/dbus/qdbusconnection.cpp:179 #7 0x7fd14e878cd1 in QThreadPrivate::start (arg=0x7fd14edb5d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:329 #8 0x7fd14d7343e9 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fd14e375293 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fd14a3e7d40 (LWP 33408)): [KCrash Handler] #5 0x7fd14e2b2615 in raise () from /usr/lib/libc.so.6 #6 0x7fd14e29b862 in abort () from /usr/lib/libc.so.6 #7 0x7fd14e83dc41 in qt_message_fatal (message=..., context=...) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.cpp:1914 #8 QMessageLogger::fatal (this=this@entry=0x7ffd81cbcf60, msg=msg@entry=0x7fd149e3a0f8 "The Wayland connection experienced a fatal error: %s") at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.cpp:893 #9 0x7fd149dc3d80 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /home/apol/build-devel/qt5/qtbase/include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.h:90 #10 0x7fd149dc3dce in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x5609c7b87860) at /home/apol/devel/frameworks/qt5/qtwayland/src/client/qwaylanddisplay.cpp:222 #11
[kdevelop] [Bug 426292] New: kdevelop-python crash while parsing projects
https://bugs.kde.org/show_bug.cgi?id=426292 Bug ID: 426292 Summary: kdevelop-python crash while parsing projects Product: kdevelop Version: 5.6.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: haagch.christ...@googlemail.com Target Milestone: --- Application: kdevelop (5.6.0) (Compiled from sources) Qt Version: 5.15.0 Frameworks Version: 5.73.0 Operating System: Linux 5.8.3-zen1-1-zen x86_64 Windowing system: X11 Distribution: "Arch Linux" -- Information about the crash: This crash happens every time while parsing my projects. They are mostly C/C++ with some python scripts. Haven't looked which file exactly causes it. kdevelop 5.6.0-1 and kdevelop-python 5.6.0-1 compiled from source with RelWithDebInfo. This crash did not happen with previous versions. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f64f5f77d13 in Python::PythonAstTransformer::visitNode(_expr*) (this=this@entry=0x7f64557f8c40, node=0x2005ef) at /usr/src/debug/kdev-python-5.6.0/parser/generated.h:164 #5 0x7f64f5f79aeb in Python::PythonAstTransformer::visitNodeList<_expr, Python::ExpressionAst>(asdl_seq*) (this=0x7f64557f8c40, node=0x7f6439002458) at /usr/src/debug/kdev-python-5.6.0/parser/generated.h:38 #6 0x7f64f5f78d90 in Python::PythonAstTransformer::visitNode(_expr*) (this=this@entry=0x7f64557f8c40, node=0x7f64390024b8) at /usr/src/debug/kdev-python-5.6.0/parser/generated.h:179 #7 0x7f64f5f7ac1b in Python::PythonAstTransformer::visitNodeList<_expr, Python::ExpressionAst>(asdl_seq*) (node=0x7f6439002390, this=0x7f64557f8c40) at /usr/src/debug/kdev-python-5.6.0/parser/generated.h:38 #8 Python::PythonAstTransformer::visitNode(_slice*) (this=this@entry=0x7f64557f8c40, node=) at /usr/src/debug/kdev-python-5.6.0/parser/generated.h:513 #9 0x7f64f5f78673 in Python::PythonAstTransformer::visitNode(_expr*) (this=this@entry=0x7f64557f8c40, node=0x7f64390024f8) at /usr/src/debug/kdev-python-5.6.0/parser/generated.h:354 #10 0x7f64f5f7bbec in Python::PythonAstTransformer::visitNode(_stmt*) (this=this@entry=0x7f64557f8c40, node=0x7f6439002528) at /usr/src/debug/kdev-python-5.6.0/parser/generated.h:729 #11 0x7f64f5f7d39b in Python::PythonAstTransformer::visitNodeList<_stmt, Python::Ast>(asdl_seq*) (this=0x7f64557f8c40, node=0x7f6439001a88) at /usr/src/debug/kdev-python-5.6.0/parser/generated.h:38 #12 0x7f64f5f7cc6e in Python::PythonAstTransformer::visitNode(_stmt*) (this=this@entry=0x7f64557f8c40, node=0x7f6439002b48) at /usr/src/debug/kdev-python-5.6.0/parser/generated.h:580 #13 0x7f64f5f7478b in Python::PythonAstTransformer::visitNodeList<_stmt, Python::Ast>(asdl_seq*) (node=0x7f6439023c80, this=0x7f64557f8c40) at /usr/src/debug/kdev-python-5.6.0/parser/generated.h:38 #14 Python::PythonAstTransformer::run(_mod*, QString) (moduleName=..., syntaxtree=, this=0x7f64557f8c40) at /usr/src/debug/kdev-python-5.6.0/parser/generated.h:16 #15 Python::AstBuilder::parse(QUrl const&, QString&) (this=this@entry=0x7f64557f8cf8, filename=..., contents=...) at /usr/src/debug/kdev-python-5.6.0/parser/astbuilder.cpp:275 #16 0x7f64f5f6f090 in Python::ParseSession::parse() (this=0x7f649c267420) at /usr/src/debug/kdev-python-5.6.0/parser/parsesession.cpp:76 #17 0x7f64c409ffdc in Python::ParseJob::run(QSharedPointer, ThreadWeaver::Thread*) (this=) at /usr/include/qt/QtCore/qshareddata.h:160 #18 0x7f65cfc6d13c in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7f65cfc6d749 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7f65cfc6c752 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7f65cfc6bfe1 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7f65d338ae0f in () at /usr/lib/libQt5Core.so.5 #23 0x7f65d06f73e9 in start_thread () at /usr/lib/libpthread.so.0 #24 0x7f65d3016293 in clone () at /usr/lib/libc.so.6 #1 0x7f65d3390e84 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f65cfc6a7e1 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f65cfc6e479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f65cfc698c3 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f65cfc6bf41 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f65d338ae0f in () at
[KSystemLog] [Bug 414971] ksystemlog cannot start from the menu
https://bugs.kde.org/show_bug.cgi?id=414971 Tore Havn changed: What|Removed |Added CC||v...@veqz.net --- Comment #4 from Tore Havn --- I can confirm this issue. Still happens on neon with Plasma 5.19.5. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426286] Untranslatable spinbox suffix " MB"
https://bugs.kde.org/show_bug.cgi?id=426286 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/system/dolphin/-/merge_requests/54 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426286] Untranslatable spinbox suffix " MB"
https://bugs.kde.org/show_bug.cgi?id=426286 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385768] segfault on parsing project: in clang::Decl::setInvalidDecl(bool) () from /usr/lib64/llvm/5/lib64/../lib64/libclangAST.so.5
https://bugs.kde.org/show_bug.cgi?id=385768 Aaron Puchert changed: What|Removed |Added CC||aaronpuch...@alice-dsl.net Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Aaron Puchert --- The bug has been fixed, and the fix will be in Clang 11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #353 from loaco...@gmail.com --- I'm for the return of this feature but I have to agree with the previous comment on this. That was not smart, and not doing anyone a favor... Anyhow, I get that this is no easy task, but I think that it's a widely requested request at that point, and I think it's pretty obvious that KDE would be nothing without users so, maybe taking this demand into consideration would already be something. Because right now you devs make it seem like a trivial thing no one cares about... Maybe you don't but a lot of users do. Don't take it badly but I sometimes wonder it KDE devs actually do use KDE... (that doesn't apply only for KDE to be fair) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #352 from Nate Graham --- You asked, I answered. BTW, here's a communication tip: don't bring up politics when you're trying to make a non-political point--especially not a political position that is likely to bring you into conflict with the people who you are asking to do work for you. Most KDE developers I know believe that climate change is an existential threat to the human race, and knowing that you are a climate change denier will probably make KDE developers who believe that the preservation of the human race is a worthy goal less likely to want to work on this. That was an unforced error on your part. The more negativity gets expressed, the less likely people are going to want to do free work for you. I mean, that's obvious, right? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396546] Mouse remote control causes KDE Plasma (Wayland) to Crash
https://bugs.kde.org/show_bug.cgi?id=396546 twinshadows...@gmail.com changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||twinshadows...@gmail.com Status|REOPENED|NEEDSINFO --- Comment #8 from twinshadows...@gmail.com --- On plasma 5.19.5, KDE Connect App 1.14.2 I am unable to reproduce this. Remote keyboard input is unavailable on Wayland. Can this be closed since the keyboard input is a different bug? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426291] UI Options Bar improvement
https://bugs.kde.org/show_bug.cgi?id=426291 --- Comment #1 from stephen --- (In reply to stephen from comment #0) > SUMMARY > This feedback is to suggest an improvement for the Krita interface. > The main elements targeted here are the options bars. > > I want to suggest merging the option bar with the Windows bar. > [url=https://ibb.co/gZKkctp][img]https://i.ibb.co/SwCFZV8/BUI-suggestions. > png[/img][/url] > > It would be kinda like in the following reference image : > [url=https://ibb.co/BCRZr7f][img]https://i.ibb.co/JsP7ybc/BetterUI.png[/ > img][/url] Sorry. Link for the suggesive image : https://ibb.co/gZKkctp Link for an idea of the suggestive image of what it would look like : https://ibb.co/BCRZr7f -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417378] Context menu and submenu of context menu opened while a window is focused appear in wrong position and have window decoration
https://bugs.kde.org/show_bug.cgi?id=417378 --- Comment #5 from Alexander Potashev --- Created attachment 131484 --> https://bugs.kde.org/attachment.cgi?id=131484=edit Yakuake screenshot -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425723] Digikam crashes after a while when detecting faces using multiple CPU cores
https://bugs.kde.org/show_bug.cgi?id=425723 --- Comment #22 from Simon Westersund --- Created attachment 131483 --> https://bugs.kde.org/attachment.cgi?id=131483=edit gdb backtrace with latest gsoc20 branch c1861ba Thank you for the information Maik! I read your comment too late, so I tested it anyway. The backtrace was quite different from the other ones. Apparently there was a malloc() error this time. The crash came at around 58% completion of my collection. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417378] Context menu and submenu of context menu opened while a window is focused appear in wrong position and have window decoration
https://bugs.kde.org/show_bug.cgi?id=417378 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com --- Comment #4 from Alexander Potashev --- Similar problem here on Fedora 32 (Plasma Wayland 5.18.5, KF 5.70.0, Qt 5.14.2): 1. Run Yakuake 2. Also run another app, e.g. Konsole 3. Press F12 to bring up Yakuake 4. Click on the Konsole window to transfer focus to it (Yakuake should be configured to stay on screen when losing focus.) 5. Right-click inside the Yakuake window OBSERVED RESULT As we can see in the attached screenshot, context menu opens in wrong position and has window decoration. EXPECTED RESULT context menu should open in correct position without window decoration -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390079] System tray layout indicator does not show chosen layout under Wayland
https://bugs.kde.org/show_bug.cgi?id=390079 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426291] New: UI Options Bar improvement
https://bugs.kde.org/show_bug.cgi?id=426291 Bug ID: 426291 Summary: UI Options Bar improvement Product: krita Version: 4.3.0-beta2 Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tgdev...@gmail.com Target Milestone: --- SUMMARY This feedback is to suggest an improvement for the Krita interface. The main elements targeted here are the options bars. I want to suggest merging the option bar with the Windows bar. [url=https://ibb.co/gZKkctp][img]https://i.ibb.co/SwCFZV8/BUI-suggestions.png[/img][/url] It would be kinda like in the following reference image : [url=https://ibb.co/BCRZr7f][img]https://i.ibb.co/JsP7ybc/BetterUI.png[/img][/url] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370198] [multiscreen] context menus are not correctly positioned
https://bugs.kde.org/show_bug.cgi?id=370198 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #351 from Ernie --- Nate Graham, I read the comments at the link you provided. I was particularly astounded by: "*other things were deemed either more important or more feasible to fix by the people doing the work*". My question is deemed by WHO? Certainly in the YEARS since developers removed a useful and sorely missed feature, someone has had time to address the issue. I realize that developers have decided that the wishes of the community are less important than Anthropological Global Warming, but like AGW, the fact that different wall papers on virtual desktops are unimportant to users is a myth. Yeah. I know that users sending bitches about a feature they want returned to KDE is unproductive as far as fixing the situation, but it does surely indicate the importance in the work flow of users. I recommend users who are still interested in seeing the issue resolved keep asking for progress reports and confirming that for the average user, this is not a trivial matter. " On Mon, Sep 7, 2020 at 9:18 AM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=341143 > > --- Comment #350 from Nate Graham --- > We've still done nothing. :) > > This blog post I wrote is pretty relevant: > https://pointieststick.com/2020/05/18/why-dont-you-just-fix-thing-already/ > > TL;DR: people capable of doing this are all working on other things which > can > also only be done by them which are more important and impactful, such as > making the Wayland session usable. Ultimately we need more developers to > keep > doing stuff like that and also this. > > I know that's not what people want to hear, but it's what I've got for you, > sorry. > > -- > 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.
[elisa] [Bug 406467] Option to sort artists' albums by year
https://bugs.kde.org/show_bug.cgi?id=406467 --- Comment #8 from Matthieu Gallien --- (In reply to Matthieu Gallien from comment #7) > https://invent.kde.org/multimedia/elisa/-/merge_requests/130 is ready for a > new review round. > > Sort by year is implemented in all views showing tracks and albums. This MR has been closed. The devs where a dead end. Following what I have learnt, I am working on https://invent.kde.org/multimedia/elisa/-/merge_requests/162 . -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 426290] New: [patch] syntax-highlighting: Correção de inconsistência na tradução dos esquemas "Solarized"
https://bugs.kde.org/show_bug.cgi?id=426290 Bug ID: 426290 Summary: [patch] syntax-highlighting: Correção de inconsistência na tradução dos esquemas "Solarized" Product: i18n Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: pt-BR Assignee: kde-i18n-pt...@kde.org Reporter: thiago.bauerm...@kolabnow.com Target Milestone: --- Created attachment 131481 --> https://bugs.kde.org/attachment.cgi?id=131481=edit [patch] syntax-highlighting: Correção de inconsistência na tradução dos esquemas "Solarized" SUMMARY Nas traduções pt e pt_BR do Konsole, e também na tradução pt do syntax-highlighting, os esquemas de cor "Solarized" são traduzidos como "Solar". O patch em anexo harmoniza a tradução pt_BR do syntax-highlighting com as outras traduções. Linux/KDE Plasma: KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Ubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426289] [Wayland] systemsettings crashed when I was switching between the sections of "Desktop behavior"
https://bugs.kde.org/show_bug.cgi?id=426289 --- Comment #3 from Alexander Potashev --- (In reply to Alexander Potashev from comment #2) > Created attachment 131480 [details] > output of "WAYLAND_DEBUG=1 systemsettings5" Btw the debug messages kept coming out even after the crash. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426289] [Wayland] systemsettings crashed when I was switching between the sections of "Desktop behavior"
https://bugs.kde.org/show_bug.cgi?id=426289 --- Comment #2 from Alexander Potashev --- Created attachment 131480 --> https://bugs.kde.org/attachment.cgi?id=131480=edit output of "WAYLAND_DEBUG=1 systemsettings5" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426256] [Wayland] systemsettings froze when switching tabs
https://bugs.kde.org/show_bug.cgi?id=426256 --- Comment #4 from Alexander Potashev --- (In reply to Vlad Zahorodnii from comment #3) > Can you please run systemsettings with WAYLAND_DEBUG=1 and post the debug > output here? I tried to, but it didn't freeze this time. Filed another report: https://bugs.kde.org/show_bug.cgi?id=426289 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426289] [Wayland] systemsettings crashed when I was switching between the sections of "Desktop behavior"
https://bugs.kde.org/show_bug.cgi?id=426289 Alexander Potashev changed: What|Removed |Added Summary|[Wayland ] systemsettings |[Wayland] systemsettings |crashed when I was |crashed when I was |switching between the |switching between the |sections of "Desktop|sections of "Desktop |behavior" |behavior" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426289] [Wayland ] systemsettings crashed when I was switching between the sections of "Desktop behavior"
https://bugs.kde.org/show_bug.cgi?id=426289 --- Comment #1 from Alexander Potashev --- Might be a duplicate of bug #408709, however I file this new ticket because 1. That existing ticket is now closed 2. I can't check if it's indeed a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426289] New: [Wayland ] systemsettings crashed when I was switching between the sections of "Desktop behavior"
https://bugs.kde.org/show_bug.cgi?id=426289 Bug ID: 426289 Summary: [Wayland ] systemsettings crashed when I was switching between the sections of "Desktop behavior" Product: systemsettings Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aspotas...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.8.4-200.fc32.x86_64 x86_64 Windowing system: Wayland Distribution: "Fedora release 32 (Thirty Two)" -- Information about the crash: - What I was doing when the application crashed: 1. Start a Plasma Wayland session 2. Run "WAYLAND_DEBUG=1 systemsettings5" on command line (e.g. in Yakuake) 3. Open "plasma behaviour" section 4. Click and hold LMB on the tabbar on the left and move the mouse between multiple tabs The crash can be reproduced every time. -- Backtrace: Application: Параметры системы (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". futex_wait_cancelable (private=0, expected=0, futex_word=0x55bad5d4d200) at ../sysdeps/nptl/futex-internal.h:183 183 int err = lll_futex_timed_wait (futex_word, expected, NULL, private); [Current thread is 1 (Thread 0x7f7cad26af80 (LWP 47098))] Thread 12 (Thread 0x7f7c5e47e700 (LWP 47127)): [KCrash Handler] #6 wl_surface_damage (height=30, width=1084, y=0, x=0, wl_surface=) at ../../include/QtWaylandClient/5.14.2/QtWaylandClient/private/../../../../../src/client/wayland-wayland-client-protocol.h:3490 #7 QtWayland::wl_surface::damage (this=0x10, x=0, y=0, width=1084, height=30) at qwayland-wayland.cpp:1319 #8 0x7f7ca0188d1c in QtWaylandClient::QWaylandWindow::damage (this=, rect=...) at /usr/include/qt5/QtCore/qrect.h:218 #9 0x7f7ca0193151 in QtWaylandClient::QWaylandAbstractDecoration::contentImage (this=0x7f7c50086290) at qwaylandabstractdecoration.cpp:135 #10 0x7f7c9e5ba1db in QtWaylandClient::DecorationsBlitter::blit (this=0x55bad5f35f00, window=window@entry=0x55bad639fe10) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:204 #11 0x7f7c9e5b9b6b in QtWaylandClient::QWaylandGLContext::swapBuffers (this=0x55bad6a68ae0, surface=) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:470 #12 0x7f7cb104f894 in QSGRenderThread::syncAndRender (this=0x55bad6cc6900, grabImage=0x0) at scenegraph/qsgthreadedrenderloop.cpp:841 #13 0x7f7cb10500c7 in QSGRenderThread::run (this=0x55bad6cc6900) at scenegraph/qsgthreadedrenderloop.cpp:980 #14 0x7f7cb1a12690 in QThreadPrivate::start (arg=0x55bad6cc6900) at thread/qthread_unix.cpp:342 #15 0x7f7cb0351432 in start_thread (arg=) at pthread_create.c:477 #16 0x7f7cb1693913 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f7c6d35c700 (LWP 47114)): #0 0x7f7cb1688aaf in __GI___poll (fds=0x7f7c64004a60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7caf9d5aae in g_main_context_poll (priority=, n_fds=1, fds=0x7f7c64004a60, timeout=, context=0x7f7c64000c20) at ../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7f7c64000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7f7caf9d5be3 in g_main_context_iteration (context=0x7f7c64000c20, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #4 0x7f7cb1bf2b8b in QEventDispatcherGlib::processEvents (this=0x7f7c64000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f7cb1ba591b in QEventLoop::exec (this=this@entry=0x7f7c6d35bc80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f7cb1a11427 in QThread::exec (this=this@entry=0x55bad59950b0) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f7cb0cf31e9 in QQmlThreadPrivate::run (this=0x55bad59950b0) at qml/ftw/qqmlthread.cpp:155 #8 0x7f7cb1a12690 in QThreadPrivate::start (arg=0x55bad59950b0) at thread/qthread_unix.cpp:342 #9 0x7f7cb0351432 in start_thread (arg=) at pthread_create.c:477 #10 0x7f7cb1693913 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f7c6e67a700 (LWP 47113)): #0 __GI___libc_read (nbytes=16, buf=0x7f7c6e679a50, fd=22) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=22, buf=buf@entry=0x7f7c6e679a50, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f7cafa1f53f in read (__nbytes=16, __buf=0x7f7c6e679a50, __fd=) at /usr/include/bits/unistd.h:44 #3 g_wakeup_acknowledge (wakeup=0x7f7c68003ea0) at ../glib/gwakeup.c:210 #4 0x7f7caf9d55ee in g_main_context_check (context=context@entry=0x7f7c6000c110,
[i18n] [Bug 426287] [patch] Konsole: Melhoria na tradução do esquema "Solarized Light"
https://bugs.kde.org/show_bug.cgi?id=426287 --- Comment #1 from Thiago Jung Bauermann --- (In reply to Thiago Jung Bauermann from comment #0) > O patch em anexo muda a tradução de "Solarized Light" para "Solar escuro" Ops, leia-se "Solar claro" ao invés de "Solar escuro". Errei na descrição do bug, mas o patch está correto. O bug 426288 contém a versão pt deste patch. A diferença entre as duas versões é a capitalização de "claro", que segue as diferentes convenções usadas entre pt e pt_BR. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 426288] New: [patch] Konsole: Melhoria na tradução do esquema "Solarized Light"
https://bugs.kde.org/show_bug.cgi?id=426288 Bug ID: 426288 Summary: [patch] Konsole: Melhoria na tradução do esquema "Solarized Light" Product: i18n Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: pt Assignee: j...@netcabo.pt Reporter: thiago.bauerm...@kolabnow.com Target Milestone: --- Created attachment 131479 --> https://bugs.kde.org/attachment.cgi?id=131479=edit [patch] Konsole: Melhoria na tradução do esquema "Solarized Light" SUMMARY No Konsole os esquemas de cor "Solarized" e "Solarized Light" formam um par onde o 1º é a versão escura e o 2º é a versão clara. Essa relação não é preservada na tradução dos nomes desses esquemas. O patch em anexo muda a tradução de "Solarized Light" para "Solar Claro", o que traz dois benefícios: 1. Fica clara a relação entre os esquemas. 2. Os dois esquemas ficam juntos na lista de esquemas de cores e fontes da aba de aparência do Konsole. O bug 426287 contém a versão pt_BR deste patch. A diferença entre as duas versões é a capitalização de "claro", que segue as diferentes convenções usadas entre pt e pt_BR. Linux/KDE Plasma: KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Ubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 426287] New: [patch] Konsole: Melhoria na tradução do esquema "Solarized Light"
https://bugs.kde.org/show_bug.cgi?id=426287 Bug ID: 426287 Summary: [patch] Konsole: Melhoria na tradução do esquema "Solarized Light" Product: i18n Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: pt-BR Assignee: kde-i18n-pt...@kde.org Reporter: thiago.bauerm...@kolabnow.com Target Milestone: --- Created attachment 131478 --> https://bugs.kde.org/attachment.cgi?id=131478=edit Melhoria na tradução do esquema "Solarized Light" SUMMARY No Konsole os esquemas de cor "Solarized" e "Solarized Light" formam um par onde o 1º é a versão escura e o 2º é a versão clara. Essa relação não é preservada na tradução dos nomes desses esquemas. O patch em anexo muda a tradução de "Solarized Light" para "Solar escuro", o que traz dois benefícios: 1. Fica clara a relação entre os esquemas. 2. Os dois esquemas ficam juntos na lista de esquemas de cores e fontes da aba de aparência do Konsole. Linux/KDE Plasma: KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Ubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 425968] [Neon unstable] Starting some applications shows "ambiguous shortcut" window
https://bugs.kde.org/show_bug.cgi?id=425968 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=262551 --- Comment #5 from andreas.sturmlech...@gmail.com --- Related to recent changes in plasma-integration, see linked bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 262551] Changing the keyboard shortcut to view hidden files in Dolphin does not affect the file/open dialogs
https://bugs.kde.org/show_bug.cgi?id=262551 andreas.sturmlech...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=425968 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425388] System Settings crash
https://bugs.kde.org/show_bug.cgi?id=425388 Christoph Feck changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- Error message is: "The Wayland connection broke. Did the Wayland compositor die?". Qt cannot recover from this error. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425723] Digikam crashes after a while when detecting faces using multiple CPU cores
https://bugs.kde.org/show_bug.cgi?id=425723 --- Comment #21 from Maik Qualmann --- Git commit 7619d77c98e3b3f955274805ba6720cd88fd714d by Maik Qualmann. Committed on 07/09/2020 at 20:06. Pushed by mqualmann into branch 'master'. disable for a test ImageMagick M +4-0core/dplugins/dimg/imagemagick/dimgimagemagickplugin.cpp https://invent.kde.org/graphics/digikam/commit/7619d77c98e3b3f955274805ba6720cd88fd714d -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426284] Cannot build digikam using Craft on Windows 10. "ninja: error: 'opencv_imgcodecs-NOTFOUND'"
https://bugs.kde.org/show_bug.cgi?id=426284 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Portability -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425338] One pixel border is always on the sides of a window, even with borders disabled
https://bugs.kde.org/show_bug.cgi?id=425338 --- Comment #2 from Christoph Feck --- Probably a duplicate of bug 387775. Please confirm if it only affects the left edge. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 424848] "Cannot Initiate the konq Protocol" message when konqueror starts with blank url
https://bugs.kde.org/show_bug.cgi?id=424848 --- Comment #10 from Alan Prescott --- Installed from package -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425723] Digikam crashes after a while when detecting faces using multiple CPU cores
https://bugs.kde.org/show_bug.cgi?id=425723 --- Comment #20 from Maik Qualmann --- In the gsoc20-facesengine-recognition branch there is no more development, everything has been added to the master branch. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425723] Digikam crashes after a while when detecting faces using multiple CPU cores
https://bugs.kde.org/show_bug.cgi?id=425723 --- Comment #19 from Simon Westersund --- Created attachment 131477 --> https://bugs.kde.org/attachment.cgi?id=131477=edit gdb backtrace with latest master 5102e32 I retested the master branch. This time my collection was processed until 26% and then crashed, so some improvements can definitely be seen compared to the earlier crashes :) I'll also test the latest gsoc20-facesengine-recognition branch. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 398803] "Kwin scripts" KCM window is too small
https://bugs.kde.org/show_bug.cgi?id=398803 --- Comment #5 from Patrick Silva --- (In reply to Harald Sitter from comment #3) > How did you make the shortcut? open kikcoff, search for "kwin scripts", right-click on "kwin scripts" search result, choose "Add to desktop". -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426286] New: Untranslatable spinbox suffix " MB"
https://bugs.kde.org/show_bug.cgi?id=426286
Bug ID: 426286
Summary: Untranslatable spinbox suffix " MB"
Product: dolphin
Version: 20.04.1
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: aspotas...@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
SUMMARY
Untranslatable suffix " MB" at
dolphin/src/settings/general/previewssettingspage.cpp:64:
m_localFileSizeBox->setSuffix(QStringLiteral(" MB"));
Please add a i18n*() call or use relevant wrappers for file size conversion.
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
Git master at 576a97d8eb9601f4ad74def6528cc90fffe97b1c.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-knewstuff] [Bug 417510] Update of icons set doesn't work
https://bugs.kde.org/show_bug.cgi?id=417510 --- Comment #20 from Alexander Lohnau --- I can reproduce this. From the logs it seems like the entry got downloaded. This will need some more debugging (have not that time right now to do this, sorry). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426285] New: [Wayland] Bogus square displayed along with OSD when switching keyboard layout in lockscreen
https://bugs.kde.org/show_bug.cgi?id=426285 Bug ID: 426285 Summary: [Wayland] Bogus square displayed along with OSD when switching keyboard layout in lockscreen Product: kwin Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: aspotas...@gmail.com Target Milestone: --- Created attachment 131476 --> https://bugs.kde.org/attachment.cgi?id=131476=edit photo of the screen SUMMARY [Wayland] Bogus square displayed along with OSD when switching keyboard layout in lockscreen. STEPS TO REPRODUCE 1. Have multiple keyboard layouts configured (I have English and Russian) 1. Start Plasma Wayland session 2. Lock screen (Ctrl+Alt+L) 3. Switch keyboard layout by either pressing a global keyboard shortcut or clicking on the layout indicator in the bottom left corner of the screen locker OBSERVED RESULT Two OSD displayed: one is an empty square, another one with the named of the new keyboard layout. EXPECTED RESULT Only one OSD should be displayed. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 32 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION The same OSD looks good when the screen is not locked, i.e. inside an unlocked Plasma Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426280] Animation speed in System Settings has no effect
https://bugs.kde.org/show_bug.cgi?id=426280 --- Comment #7 from k...@trummer.xyz --- Created attachment 131475 --> https://bugs.kde.org/attachment.cgi?id=131475=edit systemsettings - display - compositor -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426280] Animation speed in System Settings has no effect
https://bugs.kde.org/show_bug.cgi?id=426280 --- Comment #6 from k...@trummer.xyz --- Maybe it's a deprecated setting that somehow wasn't deleted? Can I delete the [KDE] line too? On my other machines with KDE Plasma that config block isn't there at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426122] redundant OSD indication when switching keyboard layout with Policy other than Global
https://bugs.kde.org/show_bug.cgi?id=426122 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425590] no OSD indication when switching keyboard layout with Application Policy
https://bugs.kde.org/show_bug.cgi?id=425590 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423617] Keyboard layout OSD does not appear when using keyboard-specific hotkeys
https://bugs.kde.org/show_bug.cgi?id=423617 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 296526] Dolphin is too slow when upload a file on a SSH server
https://bugs.kde.org/show_bug.cgi?id=296526 Harald Sitter changed: What|Removed |Added Status|REOPENED|NEEDSINFO CC||sit...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #19 from Harald Sitter --- (In reply to Scott Deagan from comment #16) > Reply to comment #14: > > If libssh was the cause of this issue, then using > SFTP from the terminal would also suffer from the same performance issue Alas, it wouldn't. sftp, the terminal application, is based on openssh, not libssh. > We would also see similar performance issues in other > file managers (that also use the same version of libssh). I do not know of any other file managers that use libssh. I'm honestly not sure what you want to happen here. I, personally, haven't seen libssh perform on the same level as openssh, so I figure the biggest fixes need to be made in libssh. Having a bug open here will not make that happen. I'm seeing comparisons being made with scp, which is a completely different protocol to begin with. Apples and oranges. We can't really use openssh because openssh has no library interface to build integrated GUIs on top of. So what's to be done here exactly? -- You are receiving this mail because: You are watching all bug changes.
