[kontact] [Bug 400401] - character starts bullet point but is removed on reopening the note
https://bugs.kde.org/show_bug.cgi?id=400401 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I can't reproduce it. Do you have test on last version ? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 406201] Calculating space of all directories at once
https://bugs.kde.org/show_bug.cgi?id=406201 Davide Gianforte changed: What|Removed |Added CC||dav...@gengisdave.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Davide Gianforte --- You can press SPACE on ".." at the top of the list; a popup will show the total and every will get its size. Does it solves you need? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405434] KMail crashes when trying to switch on add-blocker
https://bugs.kde.org/show_bug.cgi?id=405434 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Do you still have a crash with new version ? I can"t reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405585] Somewhere between Kate 17.12.3 and 18.12.2 code folding changed
https://bugs.kde.org/show_bug.cgi?id=405585 --- Comment #14 from Nibaldo G. --- Also here (they are grouped according to the KDE Frameworks version): https://kate-editor.org/syntax/ -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 398705] Help menu is disabled.
https://bugs.kde.org/show_bug.cgi?id=398705 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Laurent Montel --- Fixed -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405585] Somewhere between Kate 17.12.3 and 18.12.2 code folding changed
https://bugs.kde.org/show_bug.cgi?id=405585 --- Comment #13 from Nibaldo G. --- The KSyntaxHighlighting library (part of KDE Frameworks) is used for the syntax highlighting engine in Kate and KDevelop: https://kate-editor.org/2016/11/15/ksyntaxhighlighting-a-new-syntax-highlighting-framework/ The repository is located at: https://phabricator.kde.org/source/syntax-highlighting/ Or in GitHub (mirror): https://github.com/KDE/syntax-highlighting In the folder "data/syntax/" there are the XML files. Also in "data/schema/" there is a script to validate the XML files -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 406176] add kdeconnect as app to send sms
https://bugs.kde.org/show_bug.cgi?id=406176 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #4 from Laurent Montel --- yep. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405585] Somewhere between Kate 17.12.3 and 18.12.2 code folding changed
https://bugs.kde.org/show_bug.cgi?id=405585 --- Comment #12 from prusselltechgr...@gmail.com --- I tested neon-unstable-20190401-1143 in a VM. And the patch fixed it. Kate syntax highlighting works as it has since KDE 4: View > Code Folding > Fold Top Level Nodes and View > Code Folding > Unfold Top Level Nodes I'll definitely look into opensuse tumbleweed repos for testing. A couple of cleanup items: 1. I had a typo in my first entry. The current directory location for a user's own or override syntax highlight definition file, on linux, is: $HOME/.local/share/org.kde.syntax-highlighting/syntax/ The documentation is located here: https://docs.kde.org/trunk5/en/applications/katepart/highlight.html#idm45858413298848 The documentation says to use the command below to find your user folder ($HOME/.local/share): qtpaths --paths GenericDataLocation When I ran the command on neon-unstable, I got: qtpaths: could not find a QT installation of '' It did not prevent Kate from finding the syntax highlight definition file. 2. During the learning process, it was very helpful to read, grep/sed the system syntax highlight definition xml files. I read alert.xml to find which elements were available. I searched neon-unstable and didn't find any syntax highlight definition files. Doing an Internet search, I found the link below, which describes that they are now compiled into the KSyntaxHighlighting library. https://kate-editor.org/2018/03/10/improving-syntax-highlighting-files/ For myself and folks coming along, where would we find the xml source for the syntax highlight definition files? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 404832] Create Folder & Crashed
https://bugs.kde.org/show_bug.cgi?id=404832 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #4 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.
[Discover] [Bug 405642] No possible duplicates found
https://bugs.kde.org/show_bug.cgi?id=405642 --- 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.
[telepathy] [Bug 399352] text-ui crashes on start
https://bugs.kde.org/show_bug.cgi?id=399352 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 406204] Shift and Snap in Assistant Tools do not work
https://bugs.kde.org/show_bug.cgi?id=406204 --- Comment #1 from Tyson Tan --- This happens with both Krita from the distro and Krita appimage. I'm under Manjaro KDE 18.0.4, It's Qt 5.12 and KDE 5.15. I hope it is not another one or those Qt bugs... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406204] New: Shift and Snap in Assistant Tools do not work
https://bugs.kde.org/show_bug.cgi?id=406204 Bug ID: 406204 Summary: Shift and Snap in Assistant Tools do not work Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- Shift key and Snap do not work as they are supposed to in Krita's assistant tools. For Ellipse Assistant, our manual says: "If you press Shift while holding the first two handles, they will snap to perfectly horizontal or vertical lines. Press Shift while holding the third handle, and it’ll snap to a perfect circle." But when I was holding down Shift, Krita wouldn't recognize my clicks, and it clearly doesn't snap whether I hold Shift or not. Concentric Ellipse assistant is broken. It does not do the concentric thing because it cannot snap. Am I doing it wrong, or they are actually broken right now? I'm translating "Painting with Assistants" chapter in our user manual, and nothing works. I don't know whether it is safe to assume I understand the documentation correctly and just roll with a blind translation... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406039] Cannot apply transform tool to a Group Layer
https://bugs.kde.org/show_bug.cgi?id=406039 Scott Petrovic changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Scott Petrovic --- This is fixed. Group layers should allow you to transform again if you check the next nightly build...or wait for Krita 4.2 to come out. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 406036] plantage au démarrage
https://bugs.kde.org/show_bug.cgi?id=406036 Scott Petrovic changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/c05b3acde68f9dcc7bd2f0c5 ||cf8b7c520cb3dc60 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Scott Petrovic --- Git commit c05b3acde68f9dcc7bd2f0c5cf8b7c520cb3dc60 by Scott Petrovic. Committed on 04/04/2019 at 02:23. Pushed by scottpetrovic into branch 'master'. M +32 -36 plugins/tools/tool_transform2/kis_tool_transform.cc https://commits.kde.org/krita/c05b3acde68f9dcc7bd2f0c5cf8b7c520cb3dc60 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #61 from caulier.gil...@gmail.com --- This one installed too of course : [gilles@localhost ~]$ rpm -q --list --info lib64openssl1.1 Name: lib64openssl1.1 Version : 1.1.0j Release : 1.mga7 Architecture: x86_64 Install Date: sam. 02 mars 2019 09:10:42 CET Group : System/Libraries Size: 3409170 License : BSD-like Signature : RSA/SHA256, jeu. 22 nov. 2018 14:21:54 CET, Key ID b742fa8b80420f66 Source RPM : openssl-1.1.0j-1.mga7.src.rpm Build Date : jeu. 22 nov. 2018 13:54:39 CET Build Host : localhost Relocations : (not relocatable) Packager: ns80 Vendor : Mageia.Org URL : http://www.openssl.org/ Summary : Secure Sockets Layer communications libs Description : The libraries files are needed for various cryptographic algorithms and protocols, including DES, RC4, RSA and SSL. /usr/lib/.build-id /usr/lib/.build-id/00 /usr/lib/.build-id/00/241b2605709cc38b92b95aede01653c851e443 /usr/lib/.build-id/3e /usr/lib/.build-id/3e/4877960eb451d0eafbb6eca4e4e289155941d3 /usr/lib/.build-id/43 /usr/lib/.build-id/43/1ae76805210387861795865966e906053d9cb1 /usr/lib/.build-id/a8 /usr/lib/.build-id/a8/afd7fcc887448c68d775e26b942821d5c0a639 /usr/lib/.build-id/ba /usr/lib/.build-id/ba/89f8e56c59392a3780be8932a348dda31b0ed2 /usr/lib64/engines-1.1 /usr/lib64/engines-1.1/afalg.so /usr/lib64/engines-1.1/capi.so /usr/lib64/engines-1.1/padlock.so /usr/lib64/libcrypto.so.1.1 /usr/lib64/libssl.so.1.1 /usr/share/doc/lib64openssl1.1 /usr/share/doc/lib64openssl1.1/FAQ /usr/share/doc/lib64openssl1.1/LICENSE /usr/share/doc/lib64openssl1.1/NEWS /usr/share/doc/lib64openssl1.1/README /usr/share/doc/lib64openssl1.1/README.ECC /usr/share/doc/lib64openssl1.1/README.ENGINE /usr/share/doc/lib64openssl1.1/README.FIPS -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #60 from caulier.gil...@gmail.com --- This one is also installed : [gilles@localhost ~]$ rpm -q --list --info lib64compat-openssl10_1.0.0 Name: lib64compat-openssl10_1.0.0 Epoch : 1 Version : 1.0.2r Release : 1.mga7 Architecture: x86_64 Install Date: jeu. 28 mars 2019 05:45:28 CET Group : System/Libraries Size: 2905691 License : OpenSSL Signature : RSA/SHA256, mer. 27 févr. 2019 04:21:53 CET, Key ID b742fa8b80420f66 Source RPM : compat-openssl10-1.0.2r-1.mga7.src.rpm Build Date : mer. 27 févr. 2019 04:02:24 CET Build Host : localhost Relocations : (not relocatable) Packager: luigiwalser Vendor : Mageia.Org URL : http://www.openssl.org/ Summary : Secure Sockets Layer communications libs Description : The OpenSSL toolkit provides support for secure communications between machines. This version of OpenSSL package contains only the libraries and is provided for compatibility with previous releases and software that does not support compilation with OpenSSL-1.1. /usr/lib/.build-id /usr/lib/.build-id/2a /usr/lib/.build-id/2a/3567880860314616f0d8bbaf0cd194da13fcc1 /usr/lib/.build-id/f3 /usr/lib/.build-id/f3/9e6e595dbb3897b6b917d2926ff71ee6088ae6 /usr/lib64/libcrypto.so.1.0.0 /usr/lib64/libssl.so.1.0.0 /usr/share/doc/lib64compat-openssl10_1.0.0 /usr/share/doc/lib64compat-openssl10_1.0.0/FAQ /usr/share/doc/lib64compat-openssl10_1.0.0/LICENSE /usr/share/doc/lib64compat-openssl10_1.0.0/NEWS /usr/share/doc/lib64compat-openssl10_1.0.0/README /usr/share/doc/lib64compat-openssl10_1.0.0/README.ASN1 /usr/share/doc/lib64compat-openssl10_1.0.0/README.ENGINE /usr/share/doc/lib64compat-openssl10_1.0.0/README.warning -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #59 from caulier.gil...@gmail.com --- With rpm --list --info, it's better : [gilles@localhost ~]$ rpm -q --list --info compat-openssl10 Name: compat-openssl10 Epoch : 1 Version : 1.0.2r Release : 1.mga7 Architecture: x86_64 Install Date: jeu. 04 avril 2019 03:49:45 CEST Group : System/Libraries Size: 47666 License : OpenSSL Signature : RSA/SHA256, mer. 27 févr. 2019 04:21:54 CET, Key ID b742fa8b80420f66 Source RPM : compat-openssl10-1.0.2r-1.mga7.src.rpm Build Date : mer. 27 févr. 2019 04:02:24 CET Build Host : localhost Relocations : (not relocatable) Packager: luigiwalser Vendor : Mageia.Org URL : http://www.openssl.org/ Summary : Compatibility version of the OpenSSL library Description : The OpenSSL toolkit provides support for secure communications between machines. This version of OpenSSL package contains only the libraries and is provided for compatibility with previous releases and software that does not support compilation with OpenSSL-1.1. /usr/share/doc/compat-openssl10 /usr/share/doc/compat-openssl10/FAQ /usr/share/doc/compat-openssl10/NEWS /usr/share/doc/compat-openssl10/README /usr/share/licenses/compat-openssl10 /usr/share/licenses/compat-openssl10/LICENSE -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #58 from caulier.gil...@gmail.com --- [gilles@localhost ~]$ rpm -q compat-openssl10 compat-openssl10-1.0.2r-1.mga7 [gilles@localhost ~]$ rpm -q --list compat-openssl10 /usr/share/doc/compat-openssl10 /usr/share/doc/compat-openssl10/FAQ /usr/share/doc/compat-openssl10/NEWS /usr/share/doc/compat-openssl10/README /usr/share/licenses/compat-openssl10 /usr/share/licenses/compat-openssl10/LICENSE -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #57 from caulier.gil...@gmail.com --- [gilles@localhost ~]$ rpm -q openssl openssl-1.1.0j-1.mga7 [gilles@localhost ~]$ rpm -q --list openssl /etc/pki /etc/pki/tls /etc/pki/tls/certs /etc/pki/tls/certs/Makefile /etc/pki/tls/misc /etc/pki/tls/openssl.cnf /etc/pki/tls/private /etc/pki/tls/rootcerts /usr/bin/make-dummy-cert /usr/bin/openssl /usr/bin/renew-dummy-cert /usr/lib/.build-id /usr/lib/.build-id/df /usr/lib/.build-id/df/a7eaf828f8be565b68fb242b414202b0a9c05c /usr/share/doc/openssl /usr/share/doc/openssl/FAQ /usr/share/doc/openssl/INSTALL /usr/share/doc/openssl/LICENSE /usr/share/doc/openssl/NEWS /usr/share/doc/openssl/README /usr/share/doc/openssl/README.ECC /usr/share/doc/openssl/README.ENGINE /usr/share/doc/openssl/README.FIPS /usr/share/man/man1/asn1parse.1.xz /usr/share/man/man1/blake2b.1.xz /usr/share/man/man1/blake2s.1.xz /usr/share/man/man1/ca.1.xz /usr/share/man/man1/ciphers.1.xz /usr/share/man/man1/cms.1.xz /usr/share/man/man1/crl.1.xz /usr/share/man/man1/crl2pkcs7.1.xz /usr/share/man/man1/dgst.1.xz /usr/share/man/man1/dhparam.1.xz /usr/share/man/man1/dsa.1.xz /usr/share/man/man1/dsaparam.1.xz /usr/share/man/man1/ec.1.xz /usr/share/man/man1/ecparam.1.xz /usr/share/man/man1/enc.1.xz /usr/share/man/man1/engine.1.xz /usr/share/man/man1/errstr.1.xz /usr/share/man/man1/gendsa.1.xz /usr/share/man/man1/genpkey.1.xz /usr/share/man/man1/genrsa.1.xz /usr/share/man/man1/list.1.xz /usr/share/man/man1/md4.1.xz /usr/share/man/man1/md5.1.xz /usr/share/man/man1/mdc2.1.xz /usr/share/man/man1/nseq.1.xz /usr/share/man/man1/ocsp.1.xz /usr/share/man/man1/openssl-asn1parse.1.xz /usr/share/man/man1/openssl-ca.1.xz /usr/share/man/man1/openssl-ciphers.1.xz /usr/share/man/man1/openssl-cms.1.xz /usr/share/man/man1/openssl-crl.1.xz /usr/share/man/man1/openssl-crl2pkcs7.1.xz /usr/share/man/man1/openssl-dgst.1.xz /usr/share/man/man1/openssl-dhparam.1.xz /usr/share/man/man1/openssl-dsa.1.xz /usr/share/man/man1/openssl-dsaparam.1.xz /usr/share/man/man1/openssl-ec.1.xz /usr/share/man/man1/openssl-ecparam.1.xz /usr/share/man/man1/openssl-enc.1.xz /usr/share/man/man1/openssl-engine.1.xz /usr/share/man/man1/openssl-errstr.1.xz /usr/share/man/man1/openssl-gendsa.1.xz /usr/share/man/man1/openssl-genpkey.1.xz /usr/share/man/man1/openssl-genrsa.1.xz /usr/share/man/man1/openssl-list.1.xz /usr/share/man/man1/openssl-nseq.1.xz /usr/share/man/man1/openssl-ocsp.1.xz /usr/share/man/man1/openssl-pkcs12.1.xz /usr/share/man/man1/openssl-pkcs7.1.xz /usr/share/man/man1/openssl-pkcs8.1.xz /usr/share/man/man1/openssl-pkey.1.xz /usr/share/man/man1/openssl-pkeyparam.1.xz /usr/share/man/man1/openssl-pkeyutl.1.xz /usr/share/man/man1/openssl-req.1.xz /usr/share/man/man1/openssl-rsa.1.xz /usr/share/man/man1/openssl-rsautl.1.xz /usr/share/man/man1/openssl-s_client.1.xz /usr/share/man/man1/openssl-s_server.1.xz /usr/share/man/man1/openssl-s_time.1.xz /usr/share/man/man1/openssl-sess_id.1.xz /usr/share/man/man1/openssl-smime.1.xz /usr/share/man/man1/openssl-speed.1.xz /usr/share/man/man1/openssl-spkac.1.xz /usr/share/man/man1/openssl-ts.1.xz /usr/share/man/man1/openssl-verify.1.xz /usr/share/man/man1/openssl-version.1.xz /usr/share/man/man1/openssl-x509.1.xz /usr/share/man/man1/openssl.1.xz /usr/share/man/man1/pkcs12.1.xz /usr/share/man/man1/pkcs7.1.xz /usr/share/man/man1/pkcs8.1.xz /usr/share/man/man1/pkey.1.xz /usr/share/man/man1/pkeyparam.1.xz /usr/share/man/man1/pkeyutl.1.xz /usr/share/man/man1/req.1.xz /usr/share/man/man1/ripemd160.1.xz /usr/share/man/man1/rsa.1.xz /usr/share/man/man1/rsautl.1.xz /usr/share/man/man1/s_client.1.xz /usr/share/man/man1/s_server.1.xz /usr/share/man/man1/s_time.1.xz /usr/share/man/man1/sess_id.1.xz /usr/share/man/man1/sha.1.xz /usr/share/man/man1/sha1.1.xz /usr/share/man/man1/sha224.1.xz /usr/share/man/man1/sha256.1.xz /usr/share/man/man1/sha384.1.xz /usr/share/man/man1/sha512.1.xz /usr/share/man/man1/smime.1.xz /usr/share/man/man1/speed.1.xz /usr/share/man/man1/spkac.1.xz /usr/share/man/man1/ssl-passwd.1.xz /usr/share/man/man1/ssl-rand.1.xz /usr/share/man/man1/ts.1.xz /usr/share/man/man1/verify.1.xz /usr/share/man/man1/version.1.xz /usr/share/man/man1/x509.1.xz /usr/share/man/man5/config.5.xz /usr/share/man/man5/x509v3_config.5.xz /usr/share/man/man7/crypto.7.xz /usr/share/man/man7/ct.7.xz /usr/share/man/man7/des_modes.7.xz /usr/share/man/man7/evp.7.xz /usr/share/man/man7/ssl.7.xz /usr/share/man/man7/x509.7.xz [gilles@localhost ~]$ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #56 from caulier.gil...@gmail.com --- Created attachment 119235 --> https://bugs.kde.org/attachment.cgi?id=119235=edit openssl.conf from Mageia7 beta2 (openssl version 1.1) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #55 from caulier.gil...@gmail.com --- [gilles@localhost ~]$ rpm -q --whatprovides /etc/pki/tls/openssl.cnf openssl-1.1.0j-1.mga7 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 406164] control screen magnify- and invert-effect in lock-screen
https://bugs.kde.org/show_bug.cgi?id=406164 David Edmundson changed: What|Removed |Added Keywords||junior-jobs Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Product|kwin|kscreenlocker Component|effects-various |greeter Version|5.13.5 |unspecified CC||bhus...@gmail.com, ||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Lets focus on one task at a time. Zooming seems like a legit accessibility use-case. If someone wants to whitelist the shortcut. kscreenlocker/globalaccel.cpp extend the s_shortcutWhitelist with the component names from kwin Would be a good first contribution by someone. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405667] Plasmashell Leaks Relating To Pixmaps
https://bugs.kde.org/show_bug.cgi?id=405667 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #6 from David Edmundson --- The last Qt graphic leak was indirectly caused by the tooltip. The tooltip created a new window, which gets hidden. A hidden window meant it never rendered, because a window was marked as not being rendered yet texture deletion was deferred. Qt: 839f09c65523fb5c419b62e078f72bb39285449a But I fixed that in Qt5.11 - unless someones broken it again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406195] If QT_SCALE_FACTOR is set to 2, Kwin doesn't start and runs at 100% CPU forever
https://bugs.kde.org/show_bug.cgi?id=406195 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kwi ||n/79ce5dac9a2af0823c16f80df ||ff19ef3494d08c3 --- Comment #4 from David Edmundson --- Git commit 79ce5dac9a2af0823c16f80dfff19ef3494d08c3 by David Edmundson. Committed on 04/04/2019 at 01:03. Pushed by davidedmundson into branch 'Plasma/5.15'. Also unset QT_SCALE_FACTOR Summary: Qt scaling and kwin on X11 is never going to work so it is disabled. However, Qt uses multiple environment variables for subtly different internal things. We don't set QT_SCALE_FACTOR in Plasma, using different ones. An XFCE user was setting this, which kinda makes sense if your DE doesn't have an appropriate UI. I don't think it's relevant for main_wayland as wl_output.scale should trump the environment variable. Reviewers: zzag Reviewed By: zzag Subscribers: zzag, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D20234 M +1-0main_x11.cpp https://commits.kde.org/kwin/79ce5dac9a2af0823c16f80dfff19ef3494d08c3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406203] New: Task Manager displays wrong windows on dual-monitor setup after random time.
https://bugs.kde.org/show_bug.cgi?id=406203 Bug ID: 406203 Summary: Task Manager displays wrong windows on dual-monitor setup after random time. Product: plasmashell Version: 5.15.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: aaronbotte...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Use dual monitors, configed to show only current screen and current desktop windows. 2. Eventually, task manager will match the other monitor. Is random for how long it takes, usually. OBSERVED RESULT Task manager on desktop will show windows for opposite monitor. EXPECTED RESULT Task manager only shows windows in that monitor and virtual desktop. Sometimes, I always notice it when the desktop crashes. Messing with widget and such often leads to crashes and KDE restarting, but I do believe this is a different issue as this issue will not always be followed by a plasma crash or instability, and happens without editing widgets, panels, etc. Has happened rarely for a few versions, finally got tired of it to submit this report. This issue is not new to this version, but sadly can't remember when this started exactly. Also do not believe it to be GPU-driver related, either. It happened on Mesa 18, also. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel Version: 5.0.4-1-ck OS Type: 64-bit Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor Memory: 31.4 GiB of RAM $glxinfo | grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 580 Series (POLARIS10, DRM 3.27.0, 5.0.4-1-ck, LLVM 8.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.1.0-devel (git-d4e0fbc92f) OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.0-devel (git-d4e0fbc92f) OpenGL shading language version string: 4.50 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.1.0-devel (git-d4e0fbc92f) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 406202] New: Kontact crashes on exit
https://bugs.kde.org/show_bug.cgi?id=406202 Bug ID: 406202 Summary: Kontact crashes on exit Product: kontact Version: 5.10.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: matth...@heizmann.name Target Milestone: --- Application: kontact (5.10.3) (Compiled from sources) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.27-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: Not a new problem, occurred in preceding versions of Kontact The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe2e4c30980 (LWP 5847))] Thread 29 (Thread 0x7fe15e0bd700 (LWP 5967)): #0 0x7fe2e16950a3 in poll () from /lib64/libc.so.6 #1 0x7fe2db4ff436 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe2db4ff55c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe2e2213f1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fe2e21c4653 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe2e203e016 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fe2e2046f5a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7fe178b97700 (LWP 5950)): #0 0x7fe2dd415169 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe2d2ac38d7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fe2d2ac4e37 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fe2d2ac4f22 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fe2d2ac9fa1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fe2d2acb529 in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fe2d2ad5f41 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7fe19285c700 (LWP 5894)): #0 0x7fe2e16950a3 in poll () from /lib64/libc.so.6 #1 0x7fe2db4ff436 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe2db4ff55c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe2e2213f1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fe2e21c4653 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe2e203e016 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fe2e2046f5a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7fe193cbc700 (LWP 5892)): #0 0x7fe2e1690990 in read () from /lib64/libc.so.6 #1 0x7fe2db544af0 in g_wakeup_acknowledge () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe2db4fef0f in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe2db4ff3e0 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe2db4ff55c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fe2e2213f1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fe2e21c4653 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe2e203e016 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7fe2e2046f5a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #9 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #10 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7fe1a67c8700 (LWP 5876)): #0 0x7fe2e16b057b in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7fe2e16b274c in __fprintf_chk () from /lib64/libc.so.6 #2 0x7fe2c8e62ff0 in event_logv_.part () from /usr/lib64/libevent-2.1.so.6 #3 0x7fe2c8e631dc in event_warn () from /usr/lib64/libevent-2.1.so.6 #4 0x7fe2c8e648e4 in epoll_dispatch () from /usr/lib64/libevent-2.1.so.6 #5 0x7fe2c8e5a6d5 in event_base_loop () from /usr/lib64/libevent-2.1.so.6 #6
[krusader] [Bug 406201] New: Calculating space of all directories at once
https://bugs.kde.org/show_bug.cgi?id=406201 Bug ID: 406201 Summary: Calculating space of all directories at once Product: krusader Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: aalexand...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- it would be very useful to be able to calculate all sizes of all subdirs with one click, like it happens in Total Commander with ALT+SHIFT+ENTER. Without pressing SPACE on all subdirs in the panel. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 390776] Dictionary does not work
https://bugs.kde.org/show_bug.cgi?id=390776 Matt changed: What|Removed |Added CC||mat...@matteog.xyz --- Comment #5 from Matt --- Can confirm still an issue with the following system: Operating System: Arch Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel Version: 5.0.5-arch1-1-ARCH OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.5 GiB of RAM Hate to bump an old thread/bug, but its definitely still an issue for me. hspell and aspell are installed, and the Dictionary widget is installed as well -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405667] Plasmashell And Google Chrome Freeze
https://bugs.kde.org/show_bug.cgi?id=405667 --- Comment #5 from naroyce --- Because the pixmaps had climbed to 200MB in less than 1 day, I thought I'd try something else... "Configure Task Manager" "Show tooltips": Uncheck "Highlight windows": Uncheck "Show progress bar and status information in task buttons": Uncheck "Mark applications that play audio": Uncheck My main thought was really all about the "tooltips" part. I ran "plasmashell --replace", and with 25 hours having elapsed, the pixmaps had only increased to 22MB (from 16.7MB), compared to the over 200MB in less than 1 day. Can someone at least provide thoughts on this observation? I'm going to edit the title of this bug from "Plasmashell And Google Chrome Freeze", since it now appears to be all about pixmaps and plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405667] Plasmashell Leaks Relating To Pixmaps
https://bugs.kde.org/show_bug.cgi?id=405667 naroyce changed: What|Removed |Added Summary|Plasmashell And Google |Plasmashell Leaks Relating |Chrome Freeze |To Pixmaps -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406056] Kwin no longer compiles against Qt 5.13 after changes
https://bugs.kde.org/show_bug.cgi?id=406056 andreas.sturmlech...@gmail.com changed: What|Removed |Added Latest Commit||https://commits.kde.org/kwi ||n/3cc39ba35eb2afa9a39925daf ||58354e500e4da2b Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from andreas.sturmlech...@gmail.com --- Git commit 3cc39ba35eb2afa9a39925daf58354e500e4da2b by Andreas Sturmlechner, on behalf of Jimi Huotari. Committed on 03/04/2019 at 23:17. Pushed by asturmlechner into branch 'master'. Fix plugins/qpa build with Qt 5.13 Summary: Upstream moved screen maintenance functions from QPlatformIntegration to QWSI. See also: https://code.qt.io/cgit/qt/qtbase.git/commit/?h=5.13=01e1df90 Test Plan: Built fine with Qt 5.12.2 and Qt 5.13 stable branch. Reviewers: #kwin, zzag Reviewed By: #kwin, zzag Subscribers: zzag, arojas, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D20239 M +16 -0plugins/qpa/integration.cpp https://commits.kde.org/kwin/3cc39ba35eb2afa9a39925daf58354e500e4da2b -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 405945] [Wayland] Zoom adjustment with a touch screen is slower than with the slider in staus bar
https://bugs.kde.org/show_bug.cgi?id=405945 Patrick Silva changed: What|Removed |Added Summary|Zoom adjustment with a |[Wayland] Zoom adjustment |touch screen is slower than |with a touch screen is |with the slider in staus|slower than with the slider |bar |in staus bar --- Comment #4 from Patrick Silva --- Here is the video. The problem only occurs on Wayland. https://www.youtube.com/watch?v=jJWvHenL3mc -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 406200] New: Limit Scope Types
https://bugs.kde.org/show_bug.cgi?id=406200 Bug ID: 406200 Summary: Limit Scope Types Product: kstars Version: 3.1.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aradoblitz...@gmail.com Target Milestone: --- SUMMARY Telescope type Ritchey-Chretien STEPS TO REPRODUCE 1. Equipment wizard. 2. 3. OBSERVED RESULT Limited scope types when an RC OTA 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 406056] Kwin no longer compiles against Qt 5.13 after changes
https://bugs.kde.org/show_bug.cgi?id=406056 --- Comment #3 from andreas.sturmlech...@gmail.com --- Diff added on behalf of Chiitoo: https://phabricator.kde.org/D20239 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405724] multi-screen to single screen slideshow memory leak
https://bugs.kde.org/show_bug.cgi?id=405724 --- Comment #5 from rtver...@gmail.com --- Is there anything additional I can be doing to see a resolution to this memory leak? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 175051] mount .iso option in context menu
https://bugs.kde.org/show_bug.cgi?id=175051 --- Comment #20 from Luca Carlon --- I had a look at smb4k: what about using KAuth? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406199] New: Icons have large grid width in desktop
https://bugs.kde.org/show_bug.cgi?id=406199 Bug ID: 406199 Summary: Icons have large grid width in desktop Product: plasmashell Version: 5.15.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: m...@abv.bg CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY After every upgrade the icons on my desktop have large grid width. I can easy return them to normal from /usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderView.qml, setting "var minIconWidth = Math.max(iconWidth, units.iconSizes.small * 8);" from 8 to 5 but it brokes again after every Plasma update. Here how it looks: https://i.imgur.com/LZxYu1A.png STEPS TO REPRODUCE 1. Upgrade Plasma to a new version 2. Restart 3. OBSERVED RESULT Large icon grid width. EXPECTED RESULT Normal grid. SOFTWARE/OS VERSIONS Arch Linux/KDE Plasma: KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION I tried to get another FolderView.qml file from a new installation and overwrite mine to no avail. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406198] none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output
https://bugs.kde.org/show_bug.cgi?id=406198 --- Comment #2 from Will Schmidt --- Created attachment 119234 --> https://bugs.kde.org/attachment.cgi?id=119234=edit proposed patch to suppress CA bit display first-blush proposed patch. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406198] none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output
https://bugs.kde.org/show_bug.cgi?id=406198 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com, ||will_schm...@vnet.ibm.com --- Comment #1 from Will Schmidt --- This is actually a valgrind testcase issue, not a problem with valgrind itself. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406198] New: none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output
https://bugs.kde.org/show_bug.cgi?id=406198 Bug ID: 406198 Summary: none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: will_schm...@vnet.ibm.com Target Milestone: --- SUMMARY It was pointed out to me that valgrind attempts to display ALL bits of the XER, but our tests only set or clear a few of the bits. In particular, we sometimes (not always) are seeing the CA bit show up in the test results. This is noticed with the addex test, as illustrated below. --- test_isa_3_0_other.stdout.exp-LE2019-03-25 15:44:12.283983772 -0500 +++ test_isa_3_0_other.stdout.out 2019-04-03 14:18:47.072441960 -0500 @@ -40,15 +40,15 @@ modud , 001cbe991def => 00043eb0c0b2 () modud , => () -addex , => () -addex , 001cbe991def => 001cbe991def () -addex , => () -addex 001cbe991def, => 001cbe991def () -addex 001cbe991def, 001cbe991def => 00397d323bde () OV32 -addex 001cbe991def, => 001cbe991dee () OV OV32 -addex , => () OV OV32 -addex , 001cbe991def => 001cbe991def () OV OV32 -addex , => () OV OV32 +addex , => () CA +addex , 001cbe991def => 001cbe991def () CA +addex , => () CA +addex 001cbe991def, => 001cbe991def () CA +addex 001cbe991def, 001cbe991def => 00397d323bde () CA OV32 +addex 001cbe991def, => 001cbe991dee () OV CA OV32 +addex , => () OV CA OV32 +addex , 001cbe991def => 001cbe991def () OV CA OV32 +addex , => () OV CA OV32 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 406197] Crash when opening a menu
https://bugs.kde.org/show_bug.cgi?id=406197 --- Comment #1 from David Edmundson --- What Qt version? -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 406176] add kdeconnect as app to send sms
https://bugs.kde.org/show_bug.cgi?id=406176 --- Comment #3 from Christoph Feck --- Correct. 19.04 (KDEPIM 5.11) is feature-frozen since March 21. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406028] Folder right-click menu is missing items in the folder panel
https://bugs.kde.org/show_bug.cgi?id=406028 Nate Graham changed: What|Removed |Added CC||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Keywords||junior-jobs, usability --- Comment #1 from Nate Graham --- Yep, looks like it. Probably not a hard patch to write, either. Wanna try your hand at it? I can help! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406102] Can't open or save projects
https://bugs.kde.org/show_bug.cgi?id=406102 Corey O'Connor changed: What|Removed |Added CC||coreyocon...@gmail.com --- Comment #5 from Corey O'Connor --- Hi hardcoreburnz, Thanks for the report! There appears to be two issues here: 1. The open and save dialogs do not open when using the flatpack version. 2. The ffmpeg hardware acceleration decoding is not working with the AppImage version. Presumably due to an old version of FFMPEG. Is that correct? We'll keep this ticket for issue 1. A second ticket for issue 2. If you have not already created a ticket then feel free to reply here and I'll split the tickets. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828 --- Comment #17 from Julian Seward --- Looks good to me. Land! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406197] New: Crash when opening a menu
https://bugs.kde.org/show_bug.cgi?id=406197 Bug ID: 406197 Summary: Crash when opening a menu Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: aleix...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 I can reproduce it quite easily by showing the menus on the pulseaudio plasmoid. e #0 0x7f9bc289cd7f in raise () at /usr/lib/libc.so.6 #1 0x7f9bc7319c90 in KCrash::defaultCrashHandler(int) (sig=7) at /home/apol/devel/frameworks/kcrash/src/kcrash.cpp:439 #2 0x7f9bc289ce00 in () at /usr/lib/libc.so.6 #3 0x7f9ba02e46d8 in QtWaylandClient::QWaylandXdgSurface::setGrabPopup(QtWaylandClient::QWaylandWindow*, QtWaylandClient::QWaylandInputDevice*, int) (this=this@entry=0x55f75ce2e020, parent=parent@entry=0x55f75d310730, device=0x55f75c374f00, serial=52272) at /home/apol/devel/frameworks/qt5/qtwayland/src/plugins/shellintegration/xdg-shell/qwaylandxdgshell.cpp:371 #4 0x7f9ba02e4e16 in QtWaylandClient::QWaylandXdgSurface::QWaylandXdgSurface(QtWaylandClient::QWaylandXdgShell*, xdg_surface*, QtWaylandClient::QWaylandWindow*) (this=0x55f75ce2e020, shell=, surface=, window=) at ../../../../include/QtWaylandClient/5.12.2/QtWaylandClient/private/../../../../../../../../devel/frameworks/qt5/qtwayland/src/client/qwaylanddisplay_p.h:175 #5 0x7f9ba02e503a in QtWaylandClient::QWaylandXdgShell::getXdgSurface(QtWaylandClient::QWaylandWindow*) (this=0x55f75c7658f0, window=0x55f7665b0190) at ../../../../include/QtWaylandClient/5.12.2/QtWaylandClient/private/../../../../../src/client/qwayland-wayland.h:566 #6 0x7f9ba02e5055 in QtWaylandClient::QWaylandXdgShellIntegration::createShellSurface(QtWaylandClient::QWaylandWindow*) (this=, window=) at /home/apol/build-devel/qt5/qtbase/include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/tools/qscopedpointer.h:116 #7 0x7f9bbce86f25 in QtWaylandClient::QWaylandDisplay::createShellSurface(QtWaylandClient::QWaylandWindow*) (this=0x55f75c375f70, window=window@entry=0x55f7665b0190) at /home/apol/devel/frameworks/qt5/qtwayland/src/client/qwaylanddisplay.cpp:95 #8 0x7f9bbce9009c in QtWaylandClient::QWaylandWindow::initWindow() (this=this@entry=0x55f7665b0190) at /home/apol/devel/frameworks/qt5/qtwayland/src/client/qwaylandwindow.cpp:142 #9 0x7f9bbce90826 in QtWaylandClient::QWaylandWindow::setVisible(bool) (this=this@entry=0x55f7665b0190, visible=) at /home/apol/devel/frameworks/qt5/qtwayland/src/client/qwaylandwindow.cpp:389 #10 0x7f9bb1b7d520 in QtWaylandClient::QWaylandEglWindow::setVisible(bool) (this=0x55f7665b0190, visible=) at /home/apol/devel/frameworks/qt5/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandeglwindow.cpp:168 #11 0x7f9bc35d1011 in QWindowPrivate::setVisible(bool) (this=0x55f764e74b50, visible=visible@entry=true) at /home/apol/devel/frameworks/qt5/qtbase/src/gui/kernel/qwindow.cpp:402 #12 0x7f9bc4c4bedb in QWidgetWindow::setNativeWindowVisibility(bool) (this=this@entry=0x55f7619fe8f0, visible=visible@entry=true) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qwidgetwindow.cpp:205 #13 0x7f9bc4c27005 in QWidgetPrivate::show_sys() (this=this@entry=0x55f761a6a380) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qwidget.cpp:8151 #14 0x7f9bc4c2efbb in QWidgetPrivate::show_helper() (this=this@entry=0x55f761a6a380) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qwidget.cpp:8074 #15 0x7f9bc4c32168 in QWidgetPrivate::setVisible(bool) (this=0x55f761a6a380, visible=visible@entry=true) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qwidget.cpp:8376 #16 0x7f9bc4c3230e in QWidget::setVisible(bool) (this=0x55f761ad42f0, visible=) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qwidget.cpp:8308 #17 0x7f9bc4c2ec74 in QWidget::show() (this=this@entry=0x55f761ad42f0) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qwidget.cpp:7920 #18 0x7f9bc4d8ba55 in QMenu::popup(QPoint const&, QAction*) (this=0x55f761ad42f0, p=..., atAction=) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/widgets/qmenu.cpp:2580 #19 0x7f9ba75e7948 in QMenuProxy::openInternal(QPoint) (this=0x55f761af3970, pos=...) at /home/apol/devel/frameworks/plasma-framework/src/declarativeimports/plasmacomponents/qmenu.cpp:460 #20 0x7f9ba75e83bd in QMenuProxy::openRelative() (this=0x55f761af3970) at /home/apol/devel/frameworks/plasma-framework/src/declarativeimports/plasmacomponents/qmenu.cpp:430 #21 0x7f9ba75da846 in QMenuProxy::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x55f761af3970, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x7ffc2fde7050) at
[okular] [Bug 403914] Crash when closing okular trying to show file accessed via sftp
https://bugs.kde.org/show_bug.cgi?id=403914 Albert Astals Cid changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Albert Astals Cid --- Ok thanks. If you can reproduce it again please reopen the bug. Thanks for caring about okular :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #54 from Nicofo --- OK, so you have only one config file. Provided by openssl I suppose (not compat-openssl10 ?) (what returns "rpm -q --whatprovides /etc/pki/tls/openssl.cnf" ?) And in your file, do you have also an "ssl_conf" directive ? (the culprit in my case: if I comment that line -> no more problem) I don't know how the "compat" is supposed to work, but in Fedora it does not work automatically ... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 403914] Crash when closing okular trying to show file accessed via sftp
https://bugs.kde.org/show_bug.cgi?id=403914 --- Comment #2 from Erik Quaeghebeur --- (In reply to Albert Astals Cid from comment #1) > can you reproduce this crash? No, currently not (on 1.6.3). Feel free to close. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 403914] Crash when closing okular trying to show file accessed via sftp
https://bugs.kde.org/show_bug.cgi?id=403914 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- can you reproduce this crash? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 405959] Provide ability to set narration (text to speech) rate
https://bugs.kde.org/show_bug.cgi?id=405959 Albert Astals Cid changed: What|Removed |Added Severity|normal |wishlist CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828 --- Comment #16 from Will Schmidt --- Created attachment 119233 --> https://bugs.kde.org/attachment.cgi?id=119233=edit proposed patch (v4) Updated per feedback received. tested OK on P7,P8LE,P8BE,P9 (LE). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405232] digiKam crashes in Slideshow and Presentation
https://bugs.kde.org/show_bug.cgi?id=405232 --- Comment #31 from Maik Qualmann --- Yes, at the moment I have no idea why the memory allocation fails. We use a C++ function Type* reserved = new Type[size] (Type can be unsigned char*). After the digiKam-6.1.0 release I will test it with the C function malloc(). For me, the only explanation is that your storage is fragmented and that there are not 60MB available. But as you already write, other programs would then have also problems. But this problem has not been reported a second time. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406196] On Intel GPU's, when Angle is enabled, images painted by QPainter have Red and Blue channels swapped
https://bugs.kde.org/show_bug.cgi?id=406196 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com --- Comment #1 from wolthera --- thanks for reporting this, we were wondering if you were going to during the meeting :) Now to find someone to confirm :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406196] New: On Intel GPU's, when Angle is enabled, images painted by QPainter have Red and Blue channels swapped
https://bugs.kde.org/show_bug.cgi?id=406196 Bug ID: 406196 Summary: On Intel GPU's, when Angle is enabled, images painted by QPainter have Red and Blue channels swapped Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: b...@valdyas.org Target Milestone: --- I'm not sure whether this is a Qt 5.12 issue or something that started happening with the HDR patches, but when using an Intel GPU on Windows 10 with Angle, any image that is painted through QPainter on the OpenGL canvas has the R and B channels swapped, like the transform tool preview or the reference images. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406195] If QT_SCALE_FACTOR is set to 2, Kwin doesn't start and runs at 100% CPU forever
https://bugs.kde.org/show_bug.cgi?id=406195 --- Comment #3 from David Edmundson --- Use this instead: QT_SCREEN_SCALE_FACTORS -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406195] If QT_SCALE_FACTOR is set to 2, Kwin doesn't start and runs at 100% CPU forever
https://bugs.kde.org/show_bug.cgi?id=406195 --- Comment #2 from Vlad Zagorodniy --- Why do you set this environment variable anyway? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406194] KDE Connect reply window
https://bugs.kde.org/show_bug.cgi?id=406194 --- Comment #1 from clivejo --- Created attachment 119232 --> https://bugs.kde.org/attachment.cgi?id=119232=edit Multiple reply windows -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406056] Kwin no longer compiles against Qt 5.13 after changes
https://bugs.kde.org/show_bug.cgi?id=406056 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 405582] Incorrect hardware button mapping for Express Keys - Wacom Intuos BT S
https://bugs.kde.org/show_bug.cgi?id=405582 --- Comment #5 from MILAS Robin --- *And I wasn't able to run Kubuntu 19.04 beta :/ -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 405582] Incorrect hardware button mapping for Express Keys - Wacom Intuos BT S
https://bugs.kde.org/show_bug.cgi?id=405582 --- Comment #4 from MILAS Robin --- I'm sorry but I'm unable to try the latest version of libwacom with KDE. Under KDE neon a lot of package depend upon 0.29 installing 0.32 by forcing broke my X Server. I was able to run Kubuntu 19.04 beta :/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406192] Touchscreen input doesn't always work when laptop is not converted
https://bugs.kde.org/show_bug.cgi?id=406192 --- Comment #3 from Michael D --- Since you say "on X11", I should mention that the problem is the same on wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406195] If QT_SCALE_FACTOR is set to 2, Kwin doesn't start and runs at 100% CPU forever
https://bugs.kde.org/show_bug.cgi?id=406195 Niccolo Brogi changed: What|Removed |Added CC||m...@nbrogi.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406195] If QT_SCALE_FACTOR is set to 2, Kwin doesn't start and runs at 100% CPU forever
https://bugs.kde.org/show_bug.cgi?id=406195 --- Comment #1 from Niccolo Brogi --- Ops, nevermind--image was too big to attach. I uploaded it here: https://i.imgur.com/ElQEOe6.jpg -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406192] Touchscreen input doesn't always work when laptop is not converted
https://bugs.kde.org/show_bug.cgi?id=406192 --- Comment #2 from Michael D --- Sorry, I may have even filed a bug about this before to Kwin. What is the right product and component to file this under? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406195] New: If QT_SCALE_FACTOR is set to 2, Kwin doesn't start and runs at 100% CPU forever
https://bugs.kde.org/show_bug.cgi?id=406195 Bug ID: 406195 Summary: If QT_SCALE_FACTOR is set to 2, Kwin doesn't start and runs at 100% CPU forever Product: kwin Version: 5.12.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m...@nbrogi.com Target Milestone: --- SUMMARY If QT_SCALE_FACTOR is set to 2, Kwin doesn't start and runs at 100% CPU forever. Running with QT_SCALE_FACTOR set to 1 works. STEPS TO REPRODUCE Start Kwin with "QT_SCALE_FACTOR" set to 2, for instance like so: "(export QT_SCALE_FACTOR=2; kwin --replace &)" OBSERVED RESULT Kwin kills the current window manager, but then doesn't start and runs at 100% CPU forever. Can only be killed with "kill -9". EXPECTED RESULT Kwin should start normally SOFTWARE/OS VERSIONS Linux/KDE Plasma: Xfce on Ubuntu Bionic KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION This problem seems to be caused by a combination of environmental variables that I'm running. If I create a brand new user, Kwin can start correctly even with QT_SCALE_FACTOR set to 2. Which variables are causing the problem, I cannot figure out. I actually figured out that I had originally opened another bug at https://bugs.kde.org/show_bug.cgi?id=398965, but last time I failed to figure out how to get a backtrace of the process. This time, I'm also attaching backtrace (sorry, don't know how to output to file so it's an image). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406194] New: KDE Connect reply window
https://bugs.kde.org/show_bug.cgi?id=406194 Bug ID: 406194 Summary: KDE Connect reply window Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: cliv...@protonmail.com Target Milestone: --- When I receive a message (ie via WhatsApp etc) and click on reply, the window seems to always pop up BEHIND other windows on my desktop. It also produces multiple windows apparently at random, sometimes it's 2, others it's 5 or 6! STEPS TO REPRODUCE 1. Receive a message via WhatsApp on my device 2. Click on Reply button on the notification popup on Plasma Desktop OBSERVED RESULT One or more windows pop up behind the currently open windows on desktop. EXPECTED RESULT One window should pop up in the foreground, with the focus on it so I can type my reply. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Solus Linux v5.0.5 (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Git master build of KDE Connect running on Desktop and v1.12.6 on Lineage 16 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406056] Kwin no longer compiles against Qt 5.13 after changes
https://bugs.kde.org/show_bug.cgi?id=406056 David Edmundson changed: What|Removed |Added Ever confirmed|0 |1 CC||k...@davidedmundson.co.uk Status|REPORTED|CONFIRMED --- Comment #2 from David Edmundson --- Given you have already looked and have 5.13 already if you could make a patch I would happily accept it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406056] Kwin no longer compiles against Qt 5.13 after changes
https://bugs.kde.org/show_bug.cgi?id=406056 Arfrever Frehtes Taifersar Arahesis changed: What|Removed |Added CC||arfrever@gmail.com --- Comment #1 from Arfrever Frehtes Taifersar Arahesis --- Relevant changes in Qt: In 5.12 and 5.13: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=01e1df90a7debd14720fdd5cf6cd9964d796 In 5.13: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7a64ffb7738dc975b5008800901c8cd8ab238a0f Summary of needed replacements: screenAdded => QWindowSystemInterface::handleScreenAdded removeScreen => QWindowSystemInterface::handleScreenRemoved destroyScreen => QWindowSystemInterface::handleScreenRemoved setPrimaryScreen => QWindowSystemInterface::handlePrimaryScreenChanged -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406191] Tools stop working after passing over panels.
https://bugs.kde.org/show_bug.cgi?id=406191 --- Comment #3 from Boudewijn Rempt --- These are all important when builing Krita against Qt 5.12: 0010-Fix-tablet-jitter-on-X11.patch 0011-Add-an-ID-for-recognition-of-UGEE-tablets.patch 0012-Synthesize-Enter-LeaveEvent-for-accepted-QTabletEven.patch 0013-Poison-Qt-s-headers-with-a-mark-about-presence-of-En.patch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406192] Touchscreen input doesn't always work when laptop is not converted
https://bugs.kde.org/show_bug.cgi?id=406192 Martin Flöser changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Martin Flöser --- KWin has nothing to do with touch input on X11. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 406193] New: Group publications
https://bugs.kde.org/show_bug.cgi?id=406193 Bug ID: 406193 Summary: Group publications Product: KBibTeX Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User interface Assignee: fisc...@unix-ag.uni-kl.de Reporter: sten.hei...@gmx.de Target Milestone: --- I would like to have a way to group publications based on keywords, tags, colors, or any other filter criteria. I cannot find any way to do this, so I am proposing it as a wishlist item. Grouping/filtering would only act on a particular file, so I'd suggest to display it with the open files list, e.g. as sub-elements or tree. (Also can we move the statistics, file settings, and list of variables to be file-specific elements, too?) Thanks for a great KBibTex! SOFTWARE/OS VERSIONS KBibTex: master (24ab5143) Linux: Debian/testing KDE Frameworks Version: 5.54 Qt Version: 5.11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406192] Touchscreen input doesn't always work when laptop is not converted
https://bugs.kde.org/show_bug.cgi?id=406192 Michael D changed: What|Removed |Added Version|5.14.5 |5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406192] New: Touchscreen input doesn't always work when laptop is not converted
https://bugs.kde.org/show_bug.cgi?id=406192 Bug ID: 406192 Summary: Touchscreen input doesn't always work when laptop is not converted Product: kwin Version: 5.14.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: nortex...@gmail.com Target Milestone: --- When my Lenovo YOGA 710-15IKB is not converted into tablet mode, often touch input doesn't work. Rarely it does work, but I can't detect a pattern. However, when I convert the laptop by folding it all the way back into tablet mode, touch input works. On a default install of Fedora 29 gnome, touch input always worked. It didn't on Fedora 29 KDE spin, so it seems to be a KDE issue. (I'm now on Manjaro with kernel 5.0.5.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406191] Tools stop working after passing over panels.
https://bugs.kde.org/show_bug.cgi?id=406191 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #2 from Antonio Rojas --- Which of the patches in https://cgit.kde.org/krita.git/tree/3rdparty/ext_qt are relevant for this issue? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406191] Tools stop working after passing over panels.
https://bugs.kde.org/show_bug.cgi?id=406191 lygamin...@gmail.com changed: What|Removed |Added Component|Brush engines |Tools -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406191] Tools stop working after passing over panels.
https://bugs.kde.org/show_bug.cgi?id=406191 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@valdyas.org Resolution|--- |UPSTREAM --- Comment #1 from Boudewijn Rempt --- This is caused by bugs in Qt 5.12. Our appimages have patches to Qt that fix that; you can ask the Arch maintainers to use those patches until Qt integrates them. They have been submitted upstream. We cannot fix that in Krita. If you want to actually use Krita, use the stable appimages. In the daily appimage builds, Python scripting is currently broken, also because of Qt 5.12. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406191] New: Tools stop working after passing over panels.
https://bugs.kde.org/show_bug.cgi?id=406191 Bug ID: 406191 Summary: Tools stop working after passing over panels. Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: lygamin...@gmail.com Target Milestone: --- SUMMARY: Every tool stops working after going out of the canvas. It ONLY happens when you use pen-table. The bug is not present in mouse. Even pen-table in mouse mode triggers the same problem STEPS TO REPRODUCE 1. Make sure that "cursor shape" in option is set to "No cursor" for a better observation. 2. In the canvas, and without the cursor, the tools should be working as usual. 3. Move the cursor to any panels (out of the canvas) and then back to the working space. OBSERVED RESULT 1. The cursor will stuck with it's last state in the panels (resizing, arrow, etc.) 2. Tools would stop working. 3. Change to another windows and then back to Krita has 2 results: - If the cursor was in the panel when Krita becomes the active window again --> The tools won't be stop working again, unless you change the windows again. But the cursor will ALWAYS be present: it won't hide. - If the cursor was in the canvas when Krita becomes the active window again --> The state resets and the bug can be triggered again EXPECTED RESULT The cursor should not display when it's set to no-display. The tools should be working at any time SOFTWARE/OS VERSIONS Linux/Archlinux Kernel: x86_64 Linux 5.0.5-arch1-1-ARCH ADDITIONAL INFORMATION Wacom-tablet with lib-wacom driver Krita version: 4.1.8 video: https://drive.google.com/file/d/15azUsiFRMXABCyclfrJfqOAsmST1A6um/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406155] Flattening the image resets background color and opacity
https://bugs.kde.org/show_bug.cgi?id=406155 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369430] QQmlDelegateModel::_q_itemsChanged - kickoff version
https://bugs.kde.org/show_bug.cgi?id=369430 David Edmundson changed: What|Removed |Added CC||dmitriy.nikitin...@gmail.co ||m --- Comment #48 from David Edmundson --- *** Bug 406190 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406190] Crash of a KDE Panel
https://bugs.kde.org/show_bug.cgi?id=406190 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 369430 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 360821] Gimp 2.10 xcf files cannot be loaded
https://bugs.kde.org/show_bug.cgi?id=360821 --- Comment #42 from Boudewijn Rempt --- No, kimageformats (and qimagio) is only suitable as a fallback for formats we haven't implemented yet, it's not possible to offer image format specific options for export, or multiple layers of different kinds for import. For xcf we use xcftools, the first "library" created for loading xcf files (not saving), which stopped being maintainted donkeys years ago. In fact, the gimp people a) are of the opinion that nothing bug gimp should load or save xcf since it's their internal format and b) don't want to add a rendered image somewhere in the xcf file like Photoshop or Krita does, because that would take extra space and c) don't want to document their format other than in the source code, because of a). Porting kimageformats to ImageMagick would be more work than just fixing the xcf filter, I'm pretty sure of that. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 360821] Gimp 2.10 xcf files cannot be loaded
https://bugs.kde.org/show_bug.cgi?id=360821 --- Comment #41 from Holger --- (In reply to Boudewijn Rempt from comment #33) > That used to be the way Krita imported/exported images. It was not a huge > success, and we moved away to using libpng etc. directly. But libpng is png only, right? OTH Krita has xcf support ... so how does Krita do it? Are they also using KImageFormats? Are they using selfwritten code? Is Krita already compatible with 2.9 and 2.10 of Gimp? Looking at the impressive long list of supported fileformats, I'd say it could still be worthwhile to follow ImageMagick despite API changes ... I mean, how often do they overthrow it? Maybe they also learned from last time, that their changes were met with mixed reactions? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406190] New: Crash of a KDE Panel
https://bugs.kde.org/show_bug.cgi?id=406190 Bug ID: 406190 Summary: Crash of a KDE Panel Product: plasmashell Version: 5.14.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dmitriy.nikitin...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.55.0 Operating System: Linux 5.0.6-303.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: Open/close several applications --> seach application in "Application Menu" --> Crash The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb60da16e00 (LWP 4098))] Thread 27 (Thread 0x7fb573fff700 (LWP 5403)): #0 0x7fb60b5c673c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb60befa923 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fb5de976ba0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fb5de97accc in () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fb5de975c31 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fb5de97ad2a in () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fb5de975c31 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7fb5de97ad2a in () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7fb5de975c31 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #9 0x7fb5de978bb1 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #10 0x7fb60befa2fb in () at /lib64/libQt5Core.so.5 #11 0x7fb60b5c058e in start_thread () at /lib64/libpthread.so.0 #12 0x7fb60ba2d6a3 in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fb588ff9700 (LWP 5402)): #0 0x7fb60b5c673c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb60befa923 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fb5de976ba0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fb5de97accc in () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fb5de975c31 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fb5de97ad2a in () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fb5de975c31 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7fb5de97ad2a in () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7fb5de975c31 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #9 0x7fb5de978bb1 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #10 0x7fb60befa2fb in () at /lib64/libQt5Core.so.5 #11 0x7fb60b5c058e in start_thread () at /lib64/libpthread.so.0 #12 0x7fb60ba2d6a3 in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fb5897fa700 (LWP 5401)): #0 0x7fb60b5c673c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb60befa923 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fb5de976ba0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fb5de97accc in () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fb5de975c31 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fb5de97ad2a in () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fb5de975c31 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7fb5de97ad2a in () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7fb5de975c31 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #9 0x7fb5de97ad2a in () at /lib64/libKF5ThreadWeaver.so.5 #10 0x7fb5de975c31 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #11 0x7fb5de978bb1 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #12 0x7fb60befa2fb in () at /lib64/libQt5Core.so.5 #13 0x7fb60b5c058e in start_thread () at /lib64/libpthread.so.0 #14 0x7fb60ba2d6a3 in clone () at /lib64/libc.so.6 Thread 24 (Thread
[lattedock] [Bug 406184] Dodge all windows calculation is off by a few pixels
https://bugs.kde.org/show_bug.cgi?id=406184 --- Comment #3 from Michail Vourlakos --- nice -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406157] Krita hangs on converting color space
https://bugs.kde.org/show_bug.cgi?id=406157 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/d8abbc50a7c2f8032760fe5f ||5ed150b1f00ad11f Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Dmitry Kazakov --- Git commit d8abbc50a7c2f8032760fe5f5ed150b1f00ad11f by Dmitry Kazakov. Committed on 03/04/2019 at 16:29. Pushed by dkazakov into branch 'master'. Fix hangup on changing image's color space One day we will finally convert color space conversion actions into the strokes and then we will not need these queues (though there is nothing bad in them, even with strokes). M +15 -2libs/image/kis_image_signal_router.cpp https://commits.kde.org/krita/d8abbc50a7c2f8032760fe5f5ed150b1f00ad11f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404597] Jumpy, unpredictable zoom behavior right after canvas rotation
https://bugs.kde.org/show_bug.cgi?id=404597 --- Comment #3 from Storm Engineer --- Created attachment 119231 --> https://bugs.kde.org/attachment.cgi?id=119231=edit Tablet event logs I have created tablet event logs, I hope they can be of some use. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406157] Krita hangs on converting color space
https://bugs.kde.org/show_bug.cgi?id=406157 --- Comment #2 from Storm Engineer --- I can't reproduce anymore with current master. Fixed? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406155] Flattening the image resets background color and opacity
https://bugs.kde.org/show_bug.cgi?id=406155 --- Comment #2 from Storm Engineer --- Just built master fresh again. At the moment I can't reproduce either. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406184] Dodge all windows calculation is off by a few pixels
https://bugs.kde.org/show_bug.cgi?id=406184 --- Comment #2 from Christian Muehlhaeuser --- Will do when I'm back at the machine later. I can also first try and see if it still persists in master, if you believe it may be fixed there. Less work for you. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405975] Crash when changing Mail Folder name in KMail
https://bugs.kde.org/show_bug.cgi?id=405975 Daniel Vrátil changed: What|Removed |Added Latest Commit||https://commits.kde.org/pim ||common/6a91923b8a9f31b75b52 ||0725f4b310203fbfb13b Version Fixed In||5.11 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Daniel Vrátil --- Git commit 6a91923b8a9f31b75b520725f4b310203fbfb13b by Daniel Vrátil. Committed on 03/04/2019 at 15:58. Pushed by dvratil into branch 'Applications/19.04'. Fix crash when applying collection ACL changes Summary: Another regression caused by switch to const/non-const attributes. FIXED-IN: 5.11 Test Plan: Couldn't reproduce the crash described in the bug report, but the backtrace is fairly obvious. Reviewers: #kde_pim, lbeltrame Reviewed By: lbeltrame Subscribers: lbeltrame, kde-pim, winterz Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D20159 M +2-2src/pimcommonakonadi/acl/collectionaclpage.cpp https://commits.kde.org/pimcommon/6a91923b8a9f31b75b520725f4b310203fbfb13b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405802] Export metadata to csv file
https://bugs.kde.org/show_bug.cgi?id=405802 --- Comment #21 from Maurizio --- I noticed that in the MP4 movie files the METADATA> XMP and IPTC tab does not show the KEYWORD and TAG fields. The contents of the TAG field do not even appear in the Sidecar file. Is it possible to make the contents of these fields appear? Thank you -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 alt-tab hang regression on nvidia
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #7 from Pieter-Jan Briers --- Oh I just noticed something else. I downgraded back to KWin 5.15.3 to try the render loop basic thing on there, and it seems like KWin 5.15.3 has the exact same behavior as KWin 5.15.4 when render loop is set to basic. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405494] Problems with Qt's Windows Ink implementation
https://bugs.kde.org/show_bug.cgi?id=405494 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/13181cd88e1314b43fb48be4 ||ee2147e1e24129a4 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #19 from Dmitry Kazakov --- Git commit 13181cd88e1314b43fb48be4ee2147e1e24129a4 by Dmitry Kazakov. Committed on 03/04/2019 at 15:53. Pushed by dkazakov into branch 'master'. Implement a switch for Tablet API in Qt The patch allows switching of the Tablet API when we use Qt's own implementation. The patch is added to our build system, so the fix should appear in nightlies very soon. The patch has also been proposed to Qt: https://codereview.qt-project.org/#/c/258067/ A +73 -0 3rdparty/ext_qt/0023-Implement-a-switch-for-tablet-API-on-Windows.patch M +1-03rdparty/ext_qt/CMakeLists.txt M +15 -0CMakeLists.txt M +1-0config_use_qt_tablet_windows.h.cmake M +14 -0krita/main.cc M +25 -14 libs/ui/dialogs/kis_dlg_preferences.cc M +32 -1libs/ui/kis_config.cc M +4-1libs/ui/kis_config.h https://commits.kde.org/krita/13181cd88e1314b43fb48be4ee2147e1e24129a4 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 406189] New: Random KDevelop crash
https://bugs.kde.org/show_bug.cgi?id=406189 Bug ID: 406189 Summary: Random KDevelop crash Product: kdevelop Version: 5.3.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: ricardo@hotmail.com Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: Writing some code while the background parser was running - Reproducibility: 2 times in a full day - Please take a look at the stacktrace The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef65de6bc0 (LWP 2794))] Thread 10 (Thread 0x7feeebfff700 (LWP 2970)): #0 0x7fef0d355140 in clang::TypedefType::desugar() const () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #1 0x7fef0d355790 in clang::Type::getUnqualifiedDesugaredType() const () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #2 0x7fef0d35d16b in clang::Type::getAsTagDecl() const () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #3 0x7fef0d35d1d9 in clang::Type::getAsCXXRecordDecl() const () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #4 0x7fef0d69a683 in clang::Sema::IsDerivedFrom(clang::SourceLocation, clang::QualType, clang::QualType) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #5 0x7fef0d8d2bb2 in TryObjectArgumentInitialization(clang::Sema&, clang::SourceLocation, clang::QualType, clang::Expr::Classification, clang::CXXMethodDecl*, clang::CXXRecordDecl*) [clone .isra.754] () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #6 0x7fef0d8eb200 in clang::Sema::AddMethodCandidate(clang::CXXMethodDecl*, clang::DeclAccessPair, clang::CXXRecordDecl*, clang::QualType, clang::Expr::Classification, llvm::ArrayRef, clang::OverloadCandidateSet&, bool, bool, llvm::MutableArrayRef) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #7 0x7fef0d8ebdc8 in clang::Sema::AddMethodCandidate(clang::DeclAccessPair, clang::QualType, clang::Expr::Classification, llvm::ArrayRef, clang::OverloadCandidateSet&, bool) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #8 0x7fef0d8ec024 in clang::Sema::AddMemberOperatorCandidates(clang::OverloadedOperatorKind, clang::SourceLocation, llvm::ArrayRef, clang::OverloadCandidateSet&, clang::SourceRange) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #9 0x7fef0d8fa00a in clang::Sema::CreateOverloadedBinOp(clang::SourceLocation, clang::BinaryOperatorKind, clang::UnresolvedSetImpl const&, clang::Expr*, clang::Expr*, bool) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #10 0x7fef0d9fbbc0 in clang::TreeTransform<(anonymous namespace)::TemplateInstantiator>::TransformCXXOperatorCallExpr(clang::CXXOperatorCallExpr*) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #11 0x7fef0d9e22cb in clang::TreeTransform<(anonymous namespace)::TemplateInstantiator>::TransformExpr(clang::Expr*) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #12 0x7fef0d9fced3 in clang::TreeTransform<(anonymous namespace)::TemplateInstantiator>::TransformStmt(clang::Stmt*) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #13 0x7fef0d9fe23d in clang::TreeTransform<(anonymous namespace)::TemplateInstantiator>::TransformCompoundStmt(clang::CompoundStmt*, bool) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #14 0x7fef0da01ad8 in clang::Sema::SubstStmt(clang::Stmt*, clang::MultiLevelTemplateArgumentList const&) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #15 0x7fef0da1920a in clang::Sema::InstantiateFunctionDefinition(clang::SourceLocation, clang::FunctionDecl*, bool, bool, bool) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #16 0x7fef0da18304 in clang::Sema::PerformPendingInstantiations(bool) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #17 0x7fef0da18fe6 in clang::Sema::InstantiateFunctionDefinition(clang::SourceLocation, clang::FunctionDecl*, bool, bool, bool) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #18 0x7fef0da18304 in clang::Sema::PerformPendingInstantiations(bool) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #19 0x7fef0da18fe6 in clang::Sema::InstantiateFunctionDefinition(clang::SourceLocation, clang::FunctionDecl*, bool, bool, bool) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #20 0x7fef0da18304 in clang::Sema::PerformPendingInstantiations(bool) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #21 0x7fef0da18fe6 in clang::Sema::InstantiateFunctionDefinition(clang::SourceLocation, clang::FunctionDecl*, bool, bool, bool) () at /usr/lib/llvm-6.0/lib/libclang-6.0.so.1 #22 0x7fef0da18304 in
[systemsettings] [Bug 406182] System Settings - Desktop Effects missing vertical scrollbar.
https://bugs.kde.org/show_bug.cgi?id=406182 --- Comment #1 from Paul --- Created attachment 119230 --> https://bugs.kde.org/attachment.cgi?id=119230=edit Screen-shot of System Settings - Desktop Effects showing no vertical scrollbar for a fresh default user. Just to eliminate my own user setup. The scrollbar is also missing on a freshly created new default user. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406188] New: Infinite Recursion in MessageList when moving folders
https://bugs.kde.org/show_bug.cgi?id=406188
Bug ID: 406188
Summary: Infinite Recursion in MessageList when moving folders
Product: kmail2
Version: Git (master)
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: folders
Assignee: kdepim-b...@kde.org
Reporter: win...@kde.org
Target Milestone: ---
SUMMARY
Sometimes when moving a subfolder into another parent folder kmail will crash
with this infinite recursion
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f58721c9477 in QBasicAtomicInteger::load (this=0x1100fa20) at
/usr/include/qt5/QtCore/qbasicatomic.h:103
103 T load() const Q_DECL_NOTHROW { return Ops::load(_q_value); }
[Current thread is 1 (Thread 0x7f58fbdb7980 (LWP 18221))]
#0 0x7f58721c9477 in QBasicAtomicInteger::load() const
(this=0x1100fa20) at /usr/include/qt5/QtCore/qbasicatomic.h:103
#1 0x7f58721c9052 in QtPrivate::RefCount::isShared() const
(this=0x1100fa20) at /usr/include/qt5/QtCore/qrefcount.h:101
#2 0x7f58721de70a in
QList::append(MessageList::Core::MessageItem*
const&) (this=0x7ffe02012b20, t=@0x7ffe018150c0: 0xe0bf540) at
/usr/include/qt5/QtCore/qlist.h:581
#3 0x7f58721dbdab in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0xe0bf540, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:587
#4 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x724a9a0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#5 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0xeddcb20, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#6 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0xe0bf540, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#7 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x724a9a0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#8 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0xeddcb20, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#9 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0xe0bf540, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#10 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x724a9a0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#11 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0xeddcb20, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#12 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0xe0bf540, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#13 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0x724a9a0, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#14 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0xeddcb20, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
#15 0x7f58721dbe62 in
MessageList::Core::MessageItem::subTreeToList(QList&)
(this=0xe0bf540, list=...) at
/data/kde/src/5/kde/pim/messagelib/messagelist/src/core/messageitem.cpp:594
etcc, etc
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 alt-tab hang regression on nvidia
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #6 from Pieter-Jan Briers --- Setting render loop to basic seemed to have helped slightly but it's still unusable. That said, this time if I hold down alt until it stops hanging on its own, KWin seems to get a graphics reset which at the very least breaks rendering of blur until I kwin_x11 --replace it. I did notice something odd though. I mentioned how the mouse cursor going over a panel unstuck it? I think it seems to happen with entering windows with the mouse too, at least now that rendering loop is set to basic. So I have firefox maximized behind everything else, and I have say konsole and discord open above that. I have konsole focused and my mouse outside its window. I hit alt tab and hold alt, this hangs KWin, then I move my mouse into Konsole and it mostly reliably stops hanging. Seems to work for any window too. Oh I guess it can't hurt to mention this too: if I open a preview of the selected task switcher in system settings that has absolutely no problem. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406184] Dodge all windows calculation is off by a few pixels
https://bugs.kde.org/show_bug.cgi?id=406184 --- Comment #1 from Michail Vourlakos --- Send me your layout file please in order to check if this is reproducible in master version... For v0.8 branch I don't think I can fix this -- You are receiving this mail because: You are watching all bug changes.
