[krita] [Bug 466640] New: Shaped gradient behaves incorrectly for disconnected shapes
https://bugs.kde.org/show_bug.cgi?id=466640 Bug ID: 466640 Summary: Shaped gradient behaves incorrectly for disconnected shapes Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: vipergraphicsproducti...@gmail.com Target Milestone: --- Created attachment 156854 --> https://bugs.kde.org/attachment.cgi?id=156854=edit Description of the problem As shown in the attachments, I'm using 3 black circles inside each other: The outer 2 circles have borders with no fill, and the inner-most circle is filled. I select the shapes using the Similar Color Selection tool, delete the shapes and replace them with Shaped gradient with black and white colors. The result is that I get the shaped gradient, as well as what appears to be 4 square edges that appear in the outer-most circle (See attachment shaped_gradient_problem.png). STEPS TO REPRODUCE 1. Create 3 circles as shown in the attachment 2. Select all the shapes together 3. Apply the gradient tool with the shape set to "Shaped" OBSERVED RESULT Square, solid colored edges appear on the outer-most circle EXPECTED RESULT The shaped gradient not containing the square edges (See the bottom of the attached image , which was created by applying the gradient on each of the circles separately). SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 466104] aligned_alloc problems, part 1
https://bugs.kde.org/show_bug.cgi?id=466104 --- Comment #8 from Paul Floyd --- Before that, there are a few memalign_args tests failures in the nightlies Fedora 36 s390 gcc110 ppc64 gcc112 ppc64le -> Fixed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463115] [Android] Krita loses detection of mouse events on canvas after S-PEN is in range, and it won't come back
https://bugs.kde.org/show_bug.cgi?id=463115 --- Comment #17 from sh_zam --- Let's try again: https://drive.google.com/file/d/1PCpq92YRzdiEjMsR3TSwWfFv9Rap4zZ5/view?usp=sharing (it's the same url but I've uploaded a different APK). About losing your config, please check ~/Android/data/org.krita.next/files folder to see if there's any of your config present there. Also did you happen to change the resource location (that can make the resources be not found)? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463115] [Android] Krita loses detection of mouse events on canvas after S-PEN is in range, and it won't come back
https://bugs.kde.org/show_bug.cgi?id=463115 --- Comment #16 from Tyson Tan --- The normal Krita Next is APK 114.1MiB. Your APK is 136.3 MiB, which is significantly bigger. Could it be something wrong in the building configuration? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466639] New: settings crash before opening on steam deck
https://bugs.kde.org/show_bug.cgi?id=466639 Bug ID: 466639 Summary: settings crash before opening on steam deck Classification: Applications Product: systemsettings Version: 5.26.1 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: eduardomus...@gmail.com Target Milestone: --- Application: systemsettings (5.26.1) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 5.13.0-valve36-1-neptune x86_64 Windowing System: X11 Distribution: SteamOS DrKonqi: 5.26.1 [KCrashBackend] -- Information about the crash: as i try to open the settings it automatically crashes The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f483ae18e50 in QString::operator=(QString const&) () at /usr/lib/libQt5Core.so.5 #5 0x7f4838d680c6 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f4838dd770e in () at /usr/lib/libQt5Qml.so.5 #7 0x7f4838ddbe25 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f4838e1ea1b in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () at /usr/lib/libQt5Qml.so.5 #9 0x7f4838e1f52a in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () at /usr/lib/libQt5Qml.so.5 #10 0x7f4838e21011 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () at /usr/lib/libQt5Qml.so.5 #11 0x7f4838e214d6 in QQmlTypeLoader::load(QQmlDataBlob*, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 #12 0x7f4838e2189a in QQmlTypeLoader::getType(QUrl const&, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 #13 0x7f4838dda17e in () at /usr/lib/libQt5Qml.so.5 #14 0x7f4838ddb1d8 in () at /usr/lib/libQt5Qml.so.5 #15 0x7f4838e1ecb2 in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () at /usr/lib/libQt5Qml.so.5 #16 0x7f4838e1f52a in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () at /usr/lib/libQt5Qml.so.5 #17 0x7f4838e21011 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () at /usr/lib/libQt5Qml.so.5 #18 0x7f4838e214d6 in QQmlTypeLoader::load(QQmlDataBlob*, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 #19 0x7f4838e2189a in QQmlTypeLoader::getType(QUrl const&, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 #20 0x7f4838dda17e in () at /usr/lib/libQt5Qml.so.5 #21 0x7f4838ddb1d8 in () at /usr/lib/libQt5Qml.so.5 #22 0x7f4838e1ecb2 in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () at /usr/lib/libQt5Qml.so.5 #23 0x7f4838e1f52a in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () at /usr/lib/libQt5Qml.so.5 #24 0x7f4838e21011 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () at /usr/lib/libQt5Qml.so.5 #25 0x7f4838de5772 in () at /usr/lib/libQt5Qml.so.5 #26 0x7f4838e7f92d in () at /usr/lib/libQt5Qml.so.5 #27 0x7f483bad3b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #28 0x7f483af4cb88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #29 0x7f483af4d693 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #30 0x7f483af93728 in () at /usr/lib/libQt5Core.so.5 #31 0x7f48395a181b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #32 0x7f48395f7ec9 in () at /usr/lib/libglib-2.0.so.0 #33 0x7f48395a00d2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #34 0x7f483af9750c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #35 0x7f483af4532c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #36 0x7f483ada749f in QThread::exec() () at /usr/lib/libQt5Core.so.5 #37 0x7f4838e7a300 in () at /usr/lib/libQt5Qml.so.5 #38 0x7f483ada42ba in () at /usr/lib/libQt5Core.so.5 #39 0x7f483a9268fd in () at /usr/lib/libc.so.6 #40 0x7f483a9a8a60 in () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f482cfcf6c0 (LWP 8806) "systemse:shlo0"): #1 0x7f483a925cd0 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f482ec3c86e in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f482ebf0bdc in () at /usr/lib/dri/radeonsi_dri.so #4 0x7f482ec3c79c in () at /usr/lib/dri/radeonsi_dri.so #5 0x7f483a9268fd in () at /usr/lib/libc.so.6 #6 0x7f483a9a8a60 in () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f482d7d06c0 (LWP 8805) "systemsett:sh0"): #1 0x7f483a925cd0 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f482ec3c86e in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f482ebf0bdc in () at /usr/lib/dri/radeonsi_dri.so #4 0x7f482ec3c79c in () at /usr/lib/dri/radeonsi_dri.so #5 0x7f483a9268fd in () at /usr/lib/libc.so.6 #6 0x7f483a9a8a60 in
[krita] [Bug 463115] [Android] Krita loses detection of mouse events on canvas after S-PEN is in range, and it won't come back
https://bugs.kde.org/show_bug.cgi?id=463115 --- Comment #15 from Tyson Tan --- Created attachment 156853 --> https://bugs.kde.org/attachment.cgi?id=156853=edit krita-s-pen-events.apk install failed screen -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463115] [Android] Krita loses detection of mouse events on canvas after S-PEN is in range, and it won't come back
https://bugs.kde.org/show_bug.cgi?id=463115 --- Comment #14 from Tyson Tan --- Created attachment 156852 --> https://bugs.kde.org/attachment.cgi?id=156852=edit krita-s-pen-events.apk pre-install screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466638] Drug and drop artefacts with sliding tooltips effect is enabled
https://bugs.kde.org/show_bug.cgi?id=466638 --- Comment #1 from antonio --- Created attachment 156851 --> https://bugs.kde.org/attachment.cgi?id=156851=edit example -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466638] New: Drug and drop artefacts with sliding tooltips effect is enabled
https://bugs.kde.org/show_bug.cgi?id=466638 Bug ID: 466638 Summary: Drug and drop artefacts with sliding tooltips effect is enabled Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: antde...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY I noticed that "Sliding Tooltips" is enabled, during the move of an object on desktop, artifacts are displayed STEPS TO REPRODUCE 1. Enable sliding tooltips effect 2. Create a desktop element 3. Select and move it (Drag and Drop) OBSERVED RESULT By dragging the object, artifacts are produced SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466637] New: Drug and drop object on the desktop takes place slowly respect to the mouse
https://bugs.kde.org/show_bug.cgi?id=466637 Bug ID: 466637 Summary: Drug and drop object on the desktop takes place slowly respect to the mouse Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: antde...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 156850 --> https://bugs.kde.org/attachment.cgi?id=156850=edit example SUMMARY I noticed that Drag and Drop reacts slowly (see video) Thanks, Antonio STEPS TO REPRODUCE 1. Create a desktop element 2. Select and move it (Drag and Drop) OBSERVED RESULT The move of desktop object is delayed with respect to mouse position EXPECTED RESULT The object should be redesigned in the mouse passage points SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463115] [Android] Krita loses detection of mouse events on canvas after S-PEN is in range, and it won't come back
https://bugs.kde.org/show_bug.cgi?id=463115 --- Comment #13 from Tyson Tan --- No I didn't. I've only installed Krita Next. And I tried to uninstall Krita Next and install yours, but the error remained the same. ...and for some reason this deleted all my settings (I checked the keep all data box) I wanna die right now XD -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] resizing a window leads to malformed decoration under Aurorae
https://bugs.kde.org/show_bug.cgi?id=465790 --- Comment #18 from kdeb...@thismymail.com --- Hello! I just updated to 5.27.2 and my issue, which was marked as a duplicate of this, is not fully fixed. Screenshot: https://atvg.cc/sJNrHXaC Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: TUXEDO Product Name: TUXEDO Aura 15 Gen1 System Version: Not Applicable -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 --- Comment #19 from Artem S. Tashkinov --- (In reply to feature from comment #15) > > And for a smooth transition, the load function can be wrapped with a try > catch clause that would try to load with the prefix, and if it fails look > for the config outside the prefix and move it inside the prefix, living a > symbolic link outside. If you move the config file inside the prefix, there's no need for a symlink. No symlinks please, it will only confuse people. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466577] Feature request: Ability to enter ssh key passphrase when doing a "git push" from Kate's git toolview
https://bugs.kde.org/show_bug.cgi?id=466577 Waqar Ahmed changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/kate/commit/5ccee0783 ||46d53a71044b2343c2e0355518a ||24e8 Status|ASSIGNED|RESOLVED --- Comment #3 from Waqar Ahmed --- Git commit 5ccee078346d53a71044b2343c2e0355518a24e8 by Waqar Ahmed. Committed on 28/02/2023 at 18:33. Pushed by waqar into branch 'master'. Git: set SSH_ASKPASS env var If the user's ssh key has a passphrase, the program set by this env var can be used to ask for password. M +21 -0addons/project/gitwidget.cpp https://invent.kde.org/utilities/kate/commit/5ccee078346d53a71044b2343c2e0355518a24e8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466599] Window decoration icon for Wayland-native electron app shows generic Wayland icon, not actual app icon; Task manager shows correct icon
https://bugs.kde.org/show_bug.cgi?id=466599 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 466605] wayland: gtk apps with drop-down lists are too small or have unneccessary up/down arrows
https://bugs.kde.org/show_bug.cgi?id=466605 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466597] Popup windows sometimes glitch desktop background as content when appearing
https://bugs.kde.org/show_bug.cgi?id=466597 --- Comment #2 from dsyrzm...@mozmail.com --- Thanks for the fast answer. I'm surprised it is not eligible for support anymore. I transitioned my system to kubuntu just a week ago with a freshly downloaded official iso (LTS version) which i later upgraded to 22.10 as i had boot issues that where resolved by upgrading. I also don't know how i can upgrade my plasma version to something else than what's provided to me through the official channels, which i believed to be most up to date. I forgot to mention that i have an nvidia gpu (gtx1060 6gb) and i'm using the proprietary drivers as i've read that these work better and they indeed do with no other glitches or issues so far (UHD 3440x1440px, 120hz monitor). I also read that there currently are known issues with nvidia cards on wayland which i don't want to experiment with as i use my pc for work (i've been burned by that in the past whenever i tried running linux on my pc). This time it works quite stable so far (apart from this glitch) so i don't want to risk needing to reinstall or even revert to windows. As for the applications; i think i made an error when i said vscode is part of the list, i just tried reproducing it and it actually doesn't seem to occur there, but unity3d and jetbrains rider definitely present that issue. I wasn't able to find out what gui toolkits they build on, unfortunately; the best i could manage to find was this about intellij (which is the same base as rider): https://stackoverflow.com/questions/12309569/what-gui-libraries-are-the-jetbrains-using# and that the intellij community edition (source) might tell what's necessary but i'm not experienced in navigating java source code, so i'm a little lost in finding the answer there. As for unity3d, there's very little info and none openly available about what gui toolkit it uses. but i suspect it may even be using its own (like godot); here it only lists the basic system requirements: https://blog.unity.com/technology/announcing-the-unity-editor-for-linux Sorry to be of so little help. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466636] New: Unable to set the value of # higher than 99 when bulk renaming files using Rename Tool provided by Dolphin
https://bugs.kde.org/show_bug.cgi?id=466636 Bug ID: 466636 Summary: Unable to set the value of # higher than 99 when bulk renaming files using Rename Tool provided by Dolphin Classification: Applications Product: dolphin Version: 22.12.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rudrapratapsi...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 156849 --> https://bugs.kde.org/attachment.cgi?id=156849=edit A screenshot of the Rename Tool with the # value set to 99 and '+' button grayed out. SUMMARY *** Unable to set the value of # higher than 99 when bulk renaming files. *** STEPS TO REPRODUCE 1. Select multiple files, press F2 or right click and select Rename 2. Try to set a value higher than 99 by either typing the exact value or using + and - buttons. OBSERVED RESULT The number won't go higher than 99. EXPECTED RESULT The number should go higher than 99. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Kernel: 6.2.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1 Distro: Garuda Linux Base: Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466616] Option to set global overrides in Flatpak KCM
https://bugs.kde.org/show_bug.cgi?id=466616 Alastor Tenebris changed: What|Removed |Added Platform|Flatpak |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465199] App freezes when I use animation docker
https://bugs.kde.org/show_bug.cgi?id=465199 --- Comment #6 from sh_zam --- Odd, I can't reproduce it, it opens for me and the animation runs fine, and I can change frames with much issues. Would it be possible for you to screen record the interaction with Krita? (The number of frames is quite large, and my device is weaker -- so maybe we can rule out the possibility that this is due to weaker device :) ). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466434] Monitor frequently fails to go to sleep and corruption occurs after it attempts to or is shut off.
https://bugs.kde.org/show_bug.cgi?id=466434 C Schell changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from C Schell --- This seems to be a hardware (firmware) issue. It only happens with one monitor and only when connected via HDMI. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466612] Touch Screen Inputs are always Several Pixel Up from where I Touch Them
https://bugs.kde.org/show_bug.cgi?id=466612 sh_zam changed: What|Removed |Added CC||sh...@sdf.org --- Comment #1 from sh_zam --- We had a bug like this on Android, it was due to Qt's implementation of Android plugin. Something similar may be happening with your platform plugin, since it is XWayland. But I'm not fully sure. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466590] kate: darwin/arm64 platform support (Apple Silicon)
https://bugs.kde.org/show_bug.cgi?id=466590 0xc...@gmail.com changed: What|Removed |Added CC||0xc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463115] [Android] Krita loses detection of mouse events on canvas after S-PEN is in range, and it won't come back
https://bugs.kde.org/show_bug.cgi?id=463115 --- Comment #12 from sh_zam --- It will be named "Krita Debug", if it is "Krita Next" or the one from Play Store they shouldn't conflict with this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463115] [Android] Krita loses detection of mouse events on canvas after S-PEN is in range, and it won't come back
https://bugs.kde.org/show_bug.cgi?id=463115 --- Comment #11 from sh_zam --- That's strange. Can you please check if you have some other version of Krita Debug installed? If yes, you may have to uninstall it. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466428] Power Settings Not Applied/Enforced
https://bugs.kde.org/show_bug.cgi?id=466428 --- Comment #2 from Myc --- The problem has been intermittent to about one in ten boots power setting work as intended. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466635] Notifications still pop up on main screen when Do Not Disturb is checked on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=466635 voncl...@gmail.com changed: What|Removed |Added Target Milestone|--- |1.0 Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Component|general |Notifications Version|unspecified |5.27.2 CC||k...@privat.broulik.de Product|kde |plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466635] New: Notifications still pop up on main screen when Do Not Disturb is checked on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=466635 Bug ID: 466635 Summary: Notifications still pop up on main screen when Do Not Disturb is checked on multi monitor setup Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: voncl...@gmail.com Target Milestone: --- SUMMARY I have a tripple monitor setup and when I have Do Not Disturb enabled for all 3 monitors only my Default Monitor (the middle one) will show the notifications even with the do not disturb setting enabled. NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Enable Do Not Disturb mode for notifications on all monitors 2. "Go On" with using the system 3. Get a message via thunderbird, kdeconnect, etc and a message appears on the middle main monitor OBSERVED RESULT Get messages when disabled EXPECTED RESULT Dont get a notification SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This has been happening for about 7 months -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466634] New: When the desktop is running, even at idle, plasmashell will consume all of my 32GB of memory resulting in a system freeze.
https://bugs.kde.org/show_bug.cgi?id=466634 Bug ID: 466634 Summary: When the desktop is running, even at idle, plasmashell will consume all of my 32GB of memory resulting in a system freeze. Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-performance Assignee: plasma-b...@kde.org Reporter: kevin.david.h...@gmail.com Target Milestone: 1.0 Created attachment 156848 --> https://bugs.kde.org/attachment.cgi?id=156848=edit plasmsashell memory usage after 1 hour 40 minutes of uptime SUMMARY SYSTEM INFO. Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Boot computer and log into a desktop session (same result if using X11 or Wayland) 2. Wait...initial plasmashell memory footprint is ~2GB, over the course of several hours, it will grow occupy all memory. OBSERVED RESULT Computer hard locks and requires a reboot. EXPECTED RESULT Computer runs normally. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION This behavior was first observed ~18 hours ago after a system update. Before that, I could go weeks without issue. System is fully up to date as of this report. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466442] Searching terms like "video", "audio", "game", "torrent", etc crashes discover.
https://bugs.kde.org/show_bug.cgi?id=466442 --- Comment #7 from rosh206...@gmail.com --- (In reply to Nate Graham from comment #6) > Hmm, fedora should have debuginfod set up so that debug packages are > automatically downloaded as needed. This is working for me FWIW. > > We can try to do it manually. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl. > > Once you get to the step where you type, "bt", let me know if you get clear > and obvious output in your terminal window that it's downloading debug > packages. If this works, it's a sign that automatic debug package > downloading isn't working in the GUI crash reporting wizard for you. Thanks! I used this gdb thing, downloaded some stuffs it told me to download and its(https://pastebin.com/eDGg46n9) the output. It's everything I got in terminal. It's (https://pastebin.com/8TJJ7BzQ) the "bt" part. This time when I launched discover using gdb plasma-discover and searched "firefox" everything was fine as expected but when I searched those crashing term like "game" or "video" instead of closing discover like it used to, it froze discover. I hope it is useful. I don't know about these things so it's confusing for me. I will try my best to make a proper bug report. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 466148] Dolphin, "Open with" dialog doesn't work
https://bugs.kde.org/show_bug.cgi?id=466148 David Geiger changed: What|Removed |Added CC||geiger.david68...@gmail.com --- Comment #9 from David Geiger --- Hi, For me it is not completely fixed as any files/packages provides "cmake(XDGDesktopPortalKDE)" or a XDGDesktopPortalKDEConfig.cmake: Could not find a package configuration file provided by "XDGDesktopPortalKDE" with any of the following names: XDGDesktopPortalKDEConfig.cmake xdgdesktopportalkde-config.cmake Regards, David -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464824] GTK don't follow global font configuration
https://bugs.kde.org/show_bug.cgi?id=464824 --- Comment #2 from glewik --- (In reply to David from comment #0) > SUMMARY > After the last update of plasma/frameworks/qt/don't know what else, GTK apps > no longer use the fonts that I have configured in the system settings. > > STEPS TO REPRODUCE > 1. Go to System Settings -> Appearance -> Global Theme -> Fonts -> Adjust > All Fonts, and set some non-default font like "Noto-Sans" to be used for > everything. > 2. Update KDE-related packages to the latest version. > 3. Open some GTK app. > > OBSERVED RESULT > GTK apps now use a different font family than the one I have configured in > my system (don't know which one exactly, but looks different from QT apps > and from how they used to look before the last update). > > EXPECTED RESULT > Fonts in GTK apps should follow the settings that I have configuted for them. > > SOFTWARE/OS VERSIONS > Operating System: Debian GNU/Linux > KDE Plasma Version: 5.26.5 > KDE Frameworks Version: 5.101.0 > Qt Version: 5.15.8 > Kernel Version: 5.18.0-4-amd64 (64-bit) > Graphics Platform: X11 > Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor > Memory: 15.5 GiB of RAM > Graphics Processor: AMD Radeon RX Vega > Manufacturer: Acer > Product Name: Predator PH517-61 > System Version: V1.09 > > ADDITIONAL INFORMATION I found resolve our problem on this site "https://bugs.kde.org/show_bug.cgi?id=466463;. When you remove this package "xsettingsd", font-s will be display OK. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 443046] KDE Crash Handler crashes at login
https://bugs.kde.org/show_bug.cgi?id=443046 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 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.
[pimsettingexporter] [Bug 386209] pimsettingexporter-5.6.2 doesn’t save actual emails in ZIP backup
https://bugs.kde.org/show_bug.cgi?id=386209 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 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.
[filelight] [Bug 465697] Filelight crashes instantly upon opening
https://bugs.kde.org/show_bug.cgi?id=465697 --- 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.
[skrooge] [Bug 463322] The Dashboard and accounts screen are showing the £ at the end instead of the beginning of the amount ie:- 100£ instead of £100 for every column.
https://bugs.kde.org/show_bug.cgi?id=463322 --- Comment #7 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.
[kwin] [Bug 466633] Black lines or bands flickered horizontally when using Plasma 5.27.1 on Wayland with nomodeset on the kernel command line in VMs
https://bugs.kde.org/show_bug.cgi?id=466633 --- Comment #1 from Matt Fagnani --- Created attachment 156847 --> https://bugs.kde.org/attachment.cgi?id=156847=edit Journal for boot of Plasma 5.27.1 showing horizontal black bands flickering -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 466632] [Request] [Design] Some changes to the right-click menu
https://bugs.kde.org/show_bug.cgi?id=466632 Bug Janitor Service changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466633] New: Black lines or bands flickered horizontally when using Plasma 5.27.1 on Wayland with nomodeset on the kernel command line in VMs
https://bugs.kde.org/show_bug.cgi?id=466633 Bug ID: 466633 Summary: Black lines or bands flickered horizontally when using Plasma 5.27.1 on Wayland with nomodeset on the kernel command line in VMs Classification: Plasma Product: kwin Version: 5.27.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matt.fagn...@bell.net Target Milestone: --- Created attachment 156846 --> https://bugs.kde.org/attachment.cgi?id=156846=edit Recording of the black bands flickering when using Konsole in Plasma 5.27.1 on Wayland with nomodeset, llvmpipe, and simpledrm in a VM SUMMARY I booted the Fedora 38 KDE Plasma live image Fedora-KDE-Live-x86_64-38-20230224.n.0.iso in a QEMU/KVM VM using GNOME Boxes with 3D acceleration disabled by selecting Troubleshooting > Start Fedora-KDE-Live 38 in basic graphics mode in grub which puts nomodeset on the kernel command line and uses the llvmpipe driver from mesa-dri-drivers-23.0.0~rc4-3.fc38.x86_64 and the simpledrm driver from the 6.2.0 kernel. Plasma 5.27.1 on Wayland started. I started Konsole. I ran programs such as sudo dnf upgrade in Konsole. Black lines or bands flickered horizontally starting at the top of the Konsole window. When I moved the cursor over the black lines/bands, the path of the cursor showed up as no longer being black. The black lines/bands showed up lower on the screen sometimes and also when using other programs or when the background was shown. I'm attaching a recording of this problem. The problem usually appeared after a few seconds to a minute of using Konsole. There were many repeated journal errors like the following when the black lines/bands were shown. Feb 28 21:39:45 kwin_wayland[1442]: kwin_wayland_drm: Failed to create AR24 framebuffer: Invalid argument This problem didn't happen when using the same image with basic graphics mode with nomodeset, llvmpipe and simpledrm on bare metal, or with llvmpipe and virtio_gpu, llvmpipe and virgl in VMs, or radeonsi and amdgpu drivers on bare metal. The problem might be specific to the combination of using nomodeset, llvmpipe, and simpledrm in VMs. STEPS TO REPRODUCE 1. Boot a Fedora 37 KDE Plasma installation updated to 2023-2-28 with updates-testing enabled 2. Log in to Plasma 5.27.1 on Wayland from sddm 3. Download Fedora-KDE-Live-x86_64-38-20230224.n.0.iso from https://koji.fedoraproject.org/koji/buildinfo?buildID=2159238 4. Install GNOME Boxes if it isn't already with sudo dnf install gnome-boxes 5. Start GNOME Boxes 6. boot the Fedora 38 KDE Plasma live image Fedora-KDE-Live-x86_64-38-20230224.n.0.iso in a QEMU/KVM VM using GNOME Boxes with 3D acceleration disabled using the llvmpipe driver 7. In grub, Select Troubleshooting > Start Fedora-KDE-Live 38 in basic graphics mode 8. Start Konsole in Plasma 5.27.1 on Wayland in the VM 9. Run sudo dnf upgrade in Konsole 10. Move the mouse cursor around over the top of Konsole until the black lines/bands flicker OBSERVED RESULT Black lines or bands flickered horizontally when using Plasma 5.27.1 on Wayland with nomodeset on the kernel command line in VMs EXPECTED RESULT No black lines or bands would appear on the screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION The mouse cursor in the VM seemed to be lagging behind the cursor of the host when using the nomodeset, llvmpipe, simpledrm combination with the problem, but not otherwise. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466506] With two different DPI monitors, to achieve the same font sizes as 5.26.*, I have to disable the GNOME/GTK Settings Synchronisations Service.
https://bugs.kde.org/show_bug.cgi?id=466506 --- Comment #2 from Michael Hamilton --- (In reply to Nate Graham from comment #1) > Can you try again with Plasma 5.27.2? We removed some unnecessary font size > handling stuff in that bugfix release. Will do when 5.27.2 makes in to Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #252 from Joe --- I still get horizontal lines (again) in Konsole on 5.27.2 on Wayland w/ fractional scaling. Should I open a new bug report? -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 336936] Okteta's window is too tall in windowed mode
https://bugs.kde.org/show_bug.cgi?id=336936 k...@i509.me changed: What|Removed |Added CC||k...@i509.me --- Comment #6 from k...@i509.me --- This still occurs in 0.26.10 on Arch Linux. Qt Version: 5.18.8 KDE Frameworks 5.103.0 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 466632] New: [Request] [Design] Some changes to the right-click menu
https://bugs.kde.org/show_bug.cgi?id=466632 Bug ID: 466632 Summary: [Request] [Design] Some changes to the right-click menu Classification: Plasma Product: Breeze Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: yasu...@gmail.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- Created attachment 156845 --> https://bugs.kde.org/attachment.cgi?id=156845=edit comparison Since design is visual I added an attachment. Here's some elaboration on the "fewer icons" part. With the fewer icons I know instantly where things are. I think it's easier for me to orient myself faster because these fewer icons act as landmarks on a map, having few landmarks makes them standout and helps you know where things are in relation to them. I consider it an accessibility feature. This was posted on Reddit to see reactions, I think people liked the changes, however many didn't agree with having fewer icons. A user named SaltyBalty98 provided their take ( https://i.imgur.com/Daed1Dq.png ) which included 3 presets, first has all the icons, second has some icons, 3rd has no icons. I think having this as an option is ideal. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466586] System tray disappeared after screen size change, reboot did not recover
https://bugs.kde.org/show_bug.cgi?id=466586 --- Comment #3 from James Harkins --- Hm, it seems it's not possible in 22.04 (https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports -- "This PPA will NOT currently receive Plasma 5.26 for Jammy 22.04, as this would break subsequent upgrades to Kinetic 22.10"). I'd have to upgrade my OS to 22.10... where I hesitate to do an OS upgrade during the semester. I'll think about it. In any case, this issue should be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466586] System tray disappeared after screen size change, reboot did not recover
https://bugs.kde.org/show_bug.cgi?id=466586 --- Comment #2 from James Harkins --- (In reply to Nate Graham from comment #1) > This is one of the reasons why multi-monitor handling was completely re-done > in Plasma 5.27 to fix issues such as this one. Please update to 5.27 as soon > as your distro offers it to you. It's an LTS, release so hopefully Kubuntu > 22.04 will ship it as an update. Sure, I understand. I'm on Ubuntu Studio (which I need for the audio setup). They're unlikely to upgrade Plasma directly... poking around now to try to find a ppa for it. Glad to hear this type of problem has received some attention. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 353874] Baloo does not remove deleted files from index
https://bugs.kde.org/show_bug.cgi?id=353874 Bug Janitor Service changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #20 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/baloo/-/merge_requests/113 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 153165] Piwigo export cannot create new albums
https://bugs.kde.org/show_bug.cgi?id=153165 --- Comment #9 from caulier.gil...@gmail.com --- @Ashutosh Jha : the ''assignee" peopertie must be set to a special value to CC automatically to all team member. You are in CC list in all cases -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 153165] Piwigo export cannot create new albums
https://bugs.kde.org/show_bug.cgi?id=153165 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|ashutoshj...@gmail.com |digikam-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 466630] "Switch user" icon in Kickoff is too detailed/small at high resolutions
https://bugs.kde.org/show_bug.cgi?id=466630 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- What scale factor (if any) are you using? Or have you changed the font DPI? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466299] Window previews for task manager icons showed the wrong colours when using the llvmpipe driver
https://bugs.kde.org/show_bug.cgi?id=466299 --- Comment #3 from Matt Fagnani --- Created attachment 156844 --> https://bugs.kde.org/attachment.cgi?id=156844=edit Recording of window previews with wrong colours with kwin 5.27.1 plus the patches I built kwin 5.27.1 plus the patches for this problem and https://bugs.kde.org/show_bug.cgi?id=466302 I booted Fedora-KDE-Live-x86_64-38-20230224.n.0.iso in a QEMU/KVM VM in GNOME Boxes with 3D acceleration disabled using the llvmpipe and virtio_gpu drivers. Plasma 5.27.1 on Wayland started. I copied and pasted the kwin rpms I built into the VM. I disabled automatic login from sddm in System Settings. I logged out of Plasma. I switched to VT2 and updated to the kwin rpms I built. I logged into Plasma 5.27.1. I started Konsole, Firefox, Dolphin, and System Settings. The window previews had darker purple where there was purple before in Konsole and other previews where there was actually black. The window previews had darker blue instead of light blue where the real programs had light grey. The patch might not be enough to fix this problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466631] New: Switching between different display configurations crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=466631 Bug ID: 466631 Summary: Switching between different display configurations crashes plasmashell Classification: Plasma Product: plasmashell Version: 5.27.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ashton.ack...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.1) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.19.0-32-generic x86_64 Windowing System: Wayland Distribution: KDE neon 5.27 DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: I've tried switching between display configurations using the built in "For only this specific display arrangement" in the display configuration by powering off one of my monitors and it will sometimes crash the plasmashell. It seems like changing the latency in the compositor causes it to crash a lot less. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fd58125b0bf in QQuickItemPrivate::addToDirtyList() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fd58125fc9e in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fd58126185a in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fd5812618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fd5812618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fd5812618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7fd5812618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7fd5812618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7fd5812618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7fd5812618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7fd5812618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7fd5812619f7 in QQuickItemPrivate::setVisible(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7fd58126f6f3 in QQuickItem::qt_metacall(QMetaObject::Call, int, void**) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x7fd581bdb06a in PlasmaQuick::AppletQuickItem::qt_metacall(QMetaObject::Call, int, void**) () at /lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5 #18 0x7fd5611baada in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #19 0x7fd5611c84ea in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #20 0x7fd580c8af87 in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7fd580bade72 in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7fd580bae412 in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7fd580bae5b5 in QV4::QObjectWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7fd580b35677 in QV4::Lookup::setterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value&, QV4::Value const&) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7fd580bc87f2 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7fd580bccb9f in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #27 0x7fd580b5eaee in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #28 0x7fd580ceb3a5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7fd580c9bf3b in QQmlBoundSignalExpression::evaluate(void**) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #30 0x7fd580c9d678 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #31 0x7fd580cd0165 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #32 0x7fd57f4f3c5b in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fd580c770e4
[Breeze] [Bug 466630] New: "Switch user" icon in Kickoff is too detailed/small at high resolutions
https://bugs.kde.org/show_bug.cgi?id=466630 Bug ID: 466630 Summary: "Switch user" icon in Kickoff is too detailed/small at high resolutions Classification: Plasma Product: Breeze Version: 5.27.1 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: f.alexander.wi...@gmail.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- Created attachment 156843 --> https://bugs.kde.org/attachment.cgi?id=156843=edit A screenshot showing the symbolic icons used in Kickoff SUMMARY The "Switch user" icon is too detailed/small at high resolutions to be easily recognizable compared to the other symbolic icons in Kickoff. STEPS TO REPRODUCE 1. Use high resolution monitor (e.g. 1440p) 2. Open Kickoff 3. Open the session menu OBSERVED RESULT The "switch user" icon is very detailed compared to the "lock screen" and "log out" icons in the menu or the slightly bigger icons for standby, hibernation etc. EXPECTED RESULT A slightly less detailed icon that is as easily recognizable as the others. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230227 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466629] New: kscreen-doctor crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=466629 Bug ID: 466629 Summary: kscreen-doctor crashes plasmashell Classification: Plasma Product: plasmashell Version: 5.27.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ashton.ack...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.1) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.19.0-32-generic x86_64 Windowing System: Wayland Distribution: KDE neon 5.27 DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: Switching between display setups with kscreen-doctor seems to crash plasmashell. It's not something that happens consistently though it always seems like on the second try of switching my displays back and forth I get greeted by my screens being completely black as plasmashell has crashed. Bear in mind I'm not switching between them rapidly but in 5 to 10 second intervals. Here's the command I use to switch to my big screen. kscreen-doctor output.DP-3.enable output.DP-3.primary output.DP-2.disable output.HDMI-A-1.disable And here's what I use to switch back to my main setup. kscreen-doctor output.DP-3.disable output.DP-2.enable output.DP-2.primary output.HDMI-A-1.enable The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f5e33079874 in QQuickWindow::maybeUpdate() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f5e3305fc9e in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f5e3306185a in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f5e330618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f5e330618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f5e330618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f5e330618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f5e330618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f5e330618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f5e330618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f5e330618cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7f5e330619f7 in QQuickItemPrivate::setVisible(bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f5e3306f6f3 in QQuickItem::qt_metacall(QMetaObject::Call, int, void**) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x7f5e339b906a in PlasmaQuick::AppletQuickItem::qt_metacall(QMetaObject::Call, int, void**) () at /lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5 #18 0x7f5e1471eada in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #19 0x7f5e1472c4ea in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #20 0x7f5e32a8af87 in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7f5e329ade72 in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7f5e329ae412 in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7f5e329ae5b5 in QV4::QObjectWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7f5e32935677 in QV4::Lookup::setterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value&, QV4::Value const&) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7f5e329c87f2 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7f5e329ccb9f in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #27 0x7f5e3295eaee in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #28 0x7f5e32aeb3a5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7f5e32a9bf3b in QQmlBoundSignalExpression::evaluate(void**) () at
[Bluedevil] [Bug 464929] "Process org.bluez.obex exited with status 1" Obex exits whenever attempting to send a file, bonking file transfer
https://bugs.kde.org/show_bug.cgi?id=464929 --- Comment #4 from hurricanepoo...@protonmail.com --- I made an Arch Issue, and a breakthrough: https://bugs.archlinux.org/task/77681 Bluez's dbus service uses the systemd service to start obex, and it doesn't work. I discovered that changing Blue'z dbus service to call obex directly solves all my woes, and I have submitted an Arch bug report. I don't know how to work with git-email since I'm a bit on the younger side, so I don't know if bluez upstream will see this. I hope you find my findings useful! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466618] Powering on receiver disables secondary monitor
https://bugs.kde.org/show_bug.cgi?id=466618 --- Comment #2 from wevah29...@wifame.com --- Below is the requested output. However I did not run into the problem this time. I had been running 5.27.1 and updated to 5.27.2 today but had not rebooted until just before this last test. So it's possible 2.27.2 corrected the problem. BEFORE: --- Output: 444 HDMI-0 disabled connected priority 0 HDMI Modes: 445:1920x1080@60! 446:1920x1080@50 447:1280x720@60 448:1280x720@60 449:1280x720@50 450:720x576@50 451:720x480@60 452:640x480@60 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 453 DP-0 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 454 DP-1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 455 DP-2 enabled connected priority 1 DisplayPort Modes: 445:1920x1080@60 446:1920x1080@50 448:1280x720@60 449:1280x720@50 450:720x576@50 451:720x480@60 452:640x480@60 456:2560x1440@60! 457:2560x1440@165* 458:2560x1440@144 459:2560x1440@120 460:1920x1200@60 461:1920x1080@165 462:1920x1080@144 463:1920x1080@120 464:1920x1080@60 465:1680x1050@60 466:1600x1200@60 467:1600x900@60 468:1280x1024@75 469:1280x1024@60 470:1152x864@75 471:1024x768@75 472:1024x768@60 473:800x600@75 474:800x600@60 475:640x480@75 476:640x480@60 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 477 DP-3 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 478 DP-4 enabled connected priority 2 DisplayPort Modes: 445:1920x1080@60 446:1920x1080@50 447:1280x720@60 448:1280x720@60 449:1280x720@50 450:720x576@50 451:720x480@60 459:2560x1440@120 463:1920x1080@120 464:1920x1080@60 465:1680x1050@60 468:1280x1024@75 469:1280x1024@60 470:1152x864@75 471:1024x768@75 472:1024x768@60 473:800x600@75 474:800x600@60 475:640x480@75 476:640x480@60 479:2560x1440@60! 480:2560x1440@165* 481:2560x1440@144 482:1920x1080@165 483:1440x900@60 484:1440x576@50 485:1440x480@60 486:1280x960@60 487:1280x720@120 488:1280x720@100 489:1024x768@70 490:800x600@72 491:800x600@56 492:640x480@73 Geometry: 2560,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 493 DP-5 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown AFTER: --- Output: 444 HDMI-0 disabled connected priority 0 HDMI Modes: 445:1920x1080@60 446:1920x1080@50 448:1280x720@60 449:1280x720@50 450:720x576@50 451:720x480@60 452:640x480@60 464:1920x1080@60! 476:640x480@60 484:1440x576@50 485:1440x480@60 543:1920x1080@24 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 453 DP-0 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 454 DP-1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 455 DP-2 enabled connected priority 1 DisplayPort Modes: 445:1920x1080@60 446:1920x1080@50 448:1280x720@60 449:1280x720@50 450:720x576@50 451:720x480@60 452:640x480@60 456:2560x1440@60! 457:2560x1440@165* 458:2560x1440@144 459:2560x1440@120 460:1920x1200@60 461:1920x1080@165 462:1920x1080@144 463:1920x1080@120 464:1920x1080@60 465:1680x1050@60 466:1600x1200@60 467:1600x900@60 468:1280x1024@75 469:1280x1024@60 470:1152x864@75 471:1024x768@75 472:1024x768@60 473:800x600@75 474:800x600@60 475:640x480@75 476:640x480@60 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 477 DP-3 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 478 DP-4 enabled connected priority 2 DisplayPort Modes: 445:1920x1080@60 446:1920x1080@50 447:1280x720@60 448:1280x720@60 449:1280x720@50 450:720x576@50 451:720x480@60 459:2560x1440@120 463:1920x1080@120 464:1920x1080@60 465:1680x1050@60 468:1280x1024@75 469:1280x1024@60 470:1152x864@75 471:1024x768@75 472:1024x768@60 473:800x600@75 474:800x600@60 475:640x480@75 476:640x480@60 479:2560x1440@60! 480:2560x1440@165* 481:2560x1440@144 482:1920x1080@165 483:1440x900@60 484:1440x576@50 485:1440x480@60 486:1280x960@60 487:1280x720@120 488:1280x720@100 489:1024x768@70 490:800x600@72 491:800x600@56 492:640x480@73 Geometry: 2560,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 493 DP-5 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466425] Okular crashes when opening a faulty file
https://bugs.kde.org/show_bug.cgi?id=466425 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Please give us the faulty file :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455526] Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 Amélien changed: What|Removed |Added CC||amelien.meulemans@protonmai ||l.com --- Comment #25 from Amélien --- Created attachment 156842 --> https://bugs.kde.org/attachment.cgi?id=156842=edit The mouse leave a trail on blur konsole and contexte menu but not on the context menu if obs is recording on foreground -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466430] Wayland does not remember my monitor arrangement and crashes when I try to move a window into the second monitor.
https://bugs.kde.org/show_bug.cgi?id=466430 juuso.maen...@tutanota.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from juuso.maen...@tutanota.com --- Got fixed in Plasma 5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 458130] Fingerprint authentication sometimes fails to activate immediately; sometimes activates after a few seconds, and sometimes only activates once you try to enter an incorrec
https://bugs.kde.org/show_bug.cgi?id=458130 marav changed: What|Removed |Added CC||mar...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 436456] "Change Appearance" does not fit on mobile screen
https://bugs.kde.org/show_bug.cgi?id=436456 --- Comment #3 from israel --- On 2/28/23 17:19, Albert Astals Cid wrote: > https://bugs.kde.org/show_bug.cgi?id=436456 > > Albert Astals Cid changed: > > What|Removed |Added > > CC||aa...@kde.org > > --- Comment #2 from Albert Astals Cid --- > I don't think that "sending it away into a blackhole" is the right thing to do > here. > Thanks!!! KDE Plasma mobile should be some sort of priority in the calculation. As it could replace Android on old things. (pinephone specs do suck, like old things) All programs can be configured to work on all display sizes. someone invented tabs, etc.. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 466628] New: gwenview crashes everytime I rotate any photo image
https://bugs.kde.org/show_bug.cgi?id=466628 Bug ID: 466628 Summary: gwenview crashes everytime I rotate any photo image Classification: Applications Product: gwenview Version: 22.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: angelo...@protonmail.com Target Milestone: --- Application: gwenview (22.12.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.13-200.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 37 (KDE Plasma) DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: clicked on show controls and rotate left or right and it crashes everytime The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault [KCrash Handler] #4 0x7f39e2b75b24 in __memmove_avx_unaligned_erms () from /lib64/libc.so.6 #5 0x7f39e37b1c32 in QImage::copy(QRect const&) const () from /lib64/libQt5Gui.so.5 #6 0x7f39e506989a in Gwenview::RasterImageItem::paint(QPainter*, QStyleOptionGraphicsItem const*, QWidget*) () from /lib64/libgwenviewlib.so.5 #7 0x7f39e42fab61 in QGraphicsScenePrivate::draw(QGraphicsItem*, QPainter*, QTransform const*, QTransform const*, QRegion*, QWidget*, double, QTransform const*, bool, bool) () from /lib64/libQt5Widgets.so.5 #8 0x7f39e42fb3ba in QGraphicsScenePrivate::drawSubtreeRecursive(QGraphicsItem*, QPainter*, QTransform const*, QRegion*, QWidget*, double, QTransform const*) () from /lib64/libQt5Widgets.so.5 #9 0x7f39e42fa8b3 in QGraphicsScenePrivate::draw(QGraphicsItem*, QPainter*, QTransform const*, QTransform const*, QRegion*, QWidget*, double, QTransform const*, bool, bool) () from /lib64/libQt5Widgets.so.5 #10 0x7f39e42fb3ba in QGraphicsScenePrivate::drawSubtreeRecursive(QGraphicsItem*, QPainter*, QTransform const*, QRegion*, QWidget*, double, QTransform const*) () from /lib64/libQt5Widgets.so.5 #11 0x7f39e42fa8b3 in QGraphicsScenePrivate::draw(QGraphicsItem*, QPainter*, QTransform const*, QTransform const*, QRegion*, QWidget*, double, QTransform const*, bool, bool) () from /lib64/libQt5Widgets.so.5 #12 0x7f39e42be834 in QGraphicsItemEffectSourcePrivate::draw(QPainter*) () from /lib64/libQt5Widgets.so.5 #13 0x7f39e4366838 in QGraphicsEffectSource::draw(QPainter*) () from /lib64/libQt5Widgets.so.5 #14 0x7f39e42fb7b3 in QGraphicsScenePrivate::drawSubtreeRecursive(QGraphicsItem*, QPainter*, QTransform const*, QRegion*, QWidget*, double, QTransform const*) () from /lib64/libQt5Widgets.so.5 #15 0x7f39e42fbde2 in QGraphicsScenePrivate::drawItems(QPainter*, QTransform const*, QRegion*, QWidget*) () from /lib64/libQt5Widgets.so.5 #16 0x7f39e4320627 in QGraphicsView::paintEvent(QPaintEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f39e3ff1938 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7f39e409e622 in QFrame::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7f39e329d2b1 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #20 0x7f39e3faed52 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #21 0x7f39e329d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #22 0x7f39e3fe9b29 in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /lib64/libQt5Widgets.so.5 #23 0x7f39e3fea8d1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #24 0x7f39e3fbfff9 in QWidgetRepaintManager::paintAndFlush() () from /lib64/libQt5Widgets.so.5 #25 0x7f39e3ff1bf8 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #26 0x7f39e48d1d9d in KXmlGuiWindow::event(QEvent*) () from /lib64/libKF5XmlGui.so.5 #27 0x7f39e3faed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #28 0x7f39e329d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #29 0x7f39e32a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #30 0x7f39e42ed3f3 in QGraphicsScenePrivate::_q_processDirtyItems() () from /lib64/libQt5Widgets.so.5 #31 0x7f39e32c8134 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #32 0x7f39e3faed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #33 0x7f39e329d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #34 0x7f39e32a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #35
[Elisa] [Bug 466627] New: Navigation does not respect the global animation speed setting anymore in Elisa
https://bugs.kde.org/show_bug.cgi?id=466627 Bug ID: 466627 Summary: Navigation does not respect the global animation speed setting anymore in Elisa Classification: Applications Product: Elisa Version: 22.12.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: xnagyti...@gmail.com Target Milestone: --- Created attachment 156841 --> https://bugs.kde.org/attachment.cgi?id=156841=edit Screen capture SUMMARY When navigating in Elisa, the page transition animations that used to respect the global animation speed setting now seems to use a hardcoded duration. These hardcoded crossfading transitions are rather nauseating, at least for me. Would be great if they could be turned off with setting global animation speed setting to "Instant", as before. STEPS TO REPRODUCE 1. Set the global animation speed to "Instant" at "System Settings"->"Workspace Behavior"->"General Behavior"->"Animation speed". 2. Open Elisa. 3. Switch between the pages at the left sidebar. OBSERVED RESULT A hardcoded around ~250ms crossfading transition when switching between the pages. EXPECTED RESULT Page transitions respecting the global animation speed setting as before. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics Platform: X11 Graphics Processor: NVIDIA GeForce 920M/PCIe/SSE2 ADDITIONAL INFORMATION This regression was introduced somewhere between the Plasma 5.26 -> 5.27 update. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 436456] "Change Appearance" does not fit on mobile screen
https://bugs.kde.org/show_bug.cgi?id=436456 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #2 from Albert Astals Cid --- I don't think that "sending it away into a blackhole" is the right thing to do here. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 325062] Can not undo winning move
https://bugs.kde.org/show_bug.cgi?id=325062 --- Comment #2 from BryanFRitt --- (In reply to Stephan Kulow from comment #1) > That would make many things way more difficult to track - I don't think it's > feasible. Instead of "Undoing the last move should also revert the winning statistics to what it was before the move, and count as a win after a redo, or somehow getting the game back to a winning state." For simplicity, just add it to the winning statistics when 1st win, and after that don't update any statistics for this deal, even if re-won or quit. The last move should be able to be undone(, or even, if possible, continued from?). Although I suppose there could be an issue in doing so with the winning animations. Reverse them? p.s. Wish there was a "RESOLVED" "DON'T FEEL LIKE CHANGING IT" or something like that. Which I'm guessing would probably make more since in this case at least. I doubt having this request somehow being done and bug free would be a bad thing that someone would prefer it not to have had been done, like the current status of "RESOLVED" "INTENTIONAL" implies. Even if you for some reason disagree with me on it being done as a good thing in this case, there still should be a "RESOLVED" "DON'T FEEL LIKE CHANGING IT"(, or something like that, ) option available for this, and for other issues. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466449] Discover crashes when manually installing RPM.
https://bugs.kde.org/show_bug.cgi?id=466449 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Component|discover|PackageKit Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Can you point to a URL of an RPM that makes Discover crash for you so I can test with it as well? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466618] Powering on receiver disables secondary monitor
https://bugs.kde.org/show_bug.cgi?id=466618 Nate Graham changed: What|Removed |Added Summary|Powering on addition|Powering on receiver |display causes an existing |disables secondary monitor |display to be disabled. | -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466618] Powering on addition display causes an existing display to be disabled.
https://bugs.kde.org/show_bug.cgi?id=466618 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Assignee|plasma-b...@kde.org |kscreen-bugs-n...@kde.org Status|REPORTED|NEEDSINFO Product|plasmashell |KScreen Component|Multi-screen support|common --- Comment #1 from Nate Graham --- We have other reports of high memory usage when a new screen is plugged in or otherwise connected from a source that isn't KScreen; those are tracked with Bug 466362 and Bug 465994. For this one, let's focus on the issue with the external display being inappropriately disabled when you turn on the receiver. Can you paste the output of `kscreen-doctor -o` both before you power on the receiver (when everything is fine) and again afterwards (when the external screen is inappropriately disabled? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465850] Effective desktop size is wrong for certain scale values
https://bugs.kde.org/show_bug.cgi?id=465850 --- Comment #14 from David Edmundson --- Git commit 43481ac90728ade84643dc83da108462e9951830 by David Edmundson. Committed on 28/02/2023 at 23:02. Pushed by davidedmundson into branch 'Plasma/5.27'. backends/wayland: Round passed scale Converting to wl_fixed is lossy. Especially for non-round values like 1.15. This causes various visual glitches and off sizes. Given we're using units of 120ths for the fractional scale protocol it makes sense to fix the passed values for anything else over the wayland protocol. (cherry picked from commit 3b7b173ada8152df9160506ab14c396ca230c1d9) M +6-1backends/kwayland/waylandoutputdevice.cpp https://invent.kde.org/plasma/libkscreen/commit/43481ac90728ade84643dc83da108462e9951830 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465850] Effective desktop size is wrong for certain scale values
https://bugs.kde.org/show_bug.cgi?id=465850 --- Comment #13 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/libkscreen/-/merge_requests/110 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 464929] "Process org.bluez.obex exited with status 1" Obex exits whenever attempting to send a file, bonking file transfer
https://bugs.kde.org/show_bug.cgi?id=464929 hurricanepoo...@protonmail.com changed: What|Removed |Added Version|5.26.5 |5.27.2 --- Comment #3 from hurricanepoo...@protonmail.com --- Hey, I don't know if you're still keeping up with this, but with KDE 5.27.2, and bluez 5.66 on Arch, the bug error has updated. Now, whenver dolphin or anything else goes to start obex, I get this error: 'Failed to start org.bluez.obex service: Process org.bluez.obex exite` In the Arch's PKGBUILD, /usr/lib/systemd/user/dbus-org.bluez.obex.service is systemlinked to /usr/lib/systemd/user/obex.service, and org.bluez.obex.service lives at /usr/share/dbus-1/services/org.bluez.org.service So, like, is this even a KDE issue at this point, or an Arch issue? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466408] Plasma Shell glitches out after waking from sleep when external display is set as primary - on wayland
https://bugs.kde.org/show_bug.cgi?id=466408 --- Comment #7 from Damiano --- (In reply to Nate Graham from comment #6) > No, to be honest it's not very fun. I appreciate the appreciation! > > If the issue goes away when you set both of your screens to have the same > refresh rate, it's almost certainly the same issue despite the slightly > different symptoms. If not, it's probably something else and not a duplicate. > > Can you check? I checked and I can't reproduce the issue at all, no matter the refresh rate of my displays. Plasma version is still 5.27.1, maybe some updates to some other software have fixed the issue? Update: before publishing this post, I noticed that Plasma 5.27.2 was available. I installed it and I confirm that somehow the issue has been solved. In the end, I guess that's what matters. Thank you again for the support -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 alexmatee...@yahoo.com changed: What|Removed |Added CC||alexmatee...@yahoo.com --- Comment #18 from alexmatee...@yahoo.com --- (In reply to Joe from comment #17) > Also chiming in that I never thought dumping everything in ~/.config was > ideal and would love more organization, too, of config files. I had thought > maybe a ~/.config/plasma for all core plasma/Plasma Desktop configs and a > ~/.config/.kde-apps as default for any app configs - basically follow the > current release bundling process and nomenclature. I believe having more than one folder under .config defeats the purpose. The purpose being having the ability to backup/restore/delete KDE/Plasma config by changing just one folder. This is even beneficial for developers, because if users have an easy way to remove all settings, they can test cleanly a system that may have otherwise been migrated for years. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 466528] "Automatisch zur Gegenseite navigieren" is not an ideal translation for "Navigation wraps around"
https://bugs.kde.org/show_bug.cgi?id=466528 --- Comment #5 from Nate Graham --- Das ist viel besser, danke! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 466372] Selection menu sometimes does not appear right under cursor
https://bugs.kde.org/show_bug.cgi?id=466372 Nate Graham changed: What|Removed |Added CC||kdelibs-b...@kde.org Version|5.27.1 |5.103.0 Assignee|plasma-b...@kde.org |kio-bugs-n...@kde.org Target Milestone|1.0 |--- Summary|Selection menu does not |Selection menu sometimes |appear under cursor |does not appear right under ||cursor Component|general |general Product|plasmashell |frameworks-kio -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466372] Selection menu does not appear under cursor
https://bugs.kde.org/show_bug.cgi?id=466372 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|UNMAINTAINED|--- --- Comment #3 from Nate Graham --- That was intended for a different bug report, so sorry! Too many tabs... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466371] The taskbar randomly disappears and then automatically restarts several times throughout the day when you mouse over the taskbar icons
https://bugs.kde.org/show_bug.cgi?id=466371 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 447717 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447717] plasmashell crashes when hovering or clicking items on the Panel due to "zwp_linux_buffer_params_v1.add" protocol error
https://bugs.kde.org/show_bug.cgi?id=447717 Nate Graham changed: What|Removed |Added CC||rondo...@gmail.com --- Comment #82 from Nate Graham --- *** Bug 466371 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466370] Unable to create a Libre Office Calc file via the desktop right click context menu
https://bugs.kde.org/show_bug.cgi?id=466370 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- Does it work if you create it from within Dolphin? Or does it also fail? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465850] Effective desktop size is wrong for certain scale values
https://bugs.kde.org/show_bug.cgi?id=465850 --- Comment #12 from David Edmundson --- Git commit 3b7b173ada8152df9160506ab14c396ca230c1d9 by David Edmundson. Committed on 28/02/2023 at 22:44. Pushed by davidedmundson into branch 'master'. backends/wayland: Round passed scale Converting to wl_fixed is lossy. Especially for non-round values like 1.15. This causes various visual glitches and off sizes. Given we're using units of 120ths for the fractional scale protocol it makes sense to fix the passed values for anything else over the wayland protocol. M +6-1backends/kwayland/waylandoutputdevice.cpp https://invent.kde.org/plasma/libkscreen/commit/3b7b173ada8152df9160506ab14c396ca230c1d9 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466474] Windows decoration changed since last update, can't change them due to immediate crash when trying to open the settings app
https://bugs.kde.org/show_bug.cgi?id=466474 Nate Graham changed: What|Removed |Added Resolution|UNMAINTAINED|FIXED Version Fixed In||5.27 --- Comment #4 from Nate Graham --- You're welcome! -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 466528] "Automatisch zur Gegenseite navigieren" is not an ideal translation for "Navigation wraps around"
https://bugs.kde.org/show_bug.cgi?id=466528 Frederik Schwarzer changed: What|Removed |Added CC||schwar...@kde.org --- Comment #4 from Frederik Schwarzer --- I changed it to "Navigation rotiert an Anfang/Ende" for now but will also ask for a better translation on our mailing list. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466589] plasmashell memory usage grows rapidly and consumes all available RAM
https://bugs.kde.org/show_bug.cgi?id=466589 Pawel changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466320 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466320] kpipewire_logging: Window not available PipeWireSourceItem_QML_1025
https://bugs.kde.org/show_bug.cgi?id=466320 Pawel changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466589 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466626] New: Add an (on-by-default) option to auto-convert text emoticons to emoji
https://bugs.kde.org/show_bug.cgi?id=466626 Bug ID: 466626 Summary: Add an (on-by-default) option to auto-convert text emoticons to emoji Classification: Applications Product: NeoChat Version: 23.01.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: ngomp...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Most contemporary popular chat clients (Discord, Slack, Telegram, etc.) automatically convert text emoticons into emoji characters (for example, ";)" -> ""). NeoChat does not currently offer this capability. Please add the ability to do this, and for those who don't like it, have an option to toggle off the behavior. STEPS TO REPRODUCE 1. Open NeoChat and enter a room 2. Type a text emoticon (like ";)", ":D", "^^;", etc.) OBSERVED RESULT It does nothing. EXPECTED RESULT It should automatically change to the corresponding emoji character. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 38 (KDE Plasma) (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION This is apparently supported in KMail, so some code for doing this exists elsewhere. It might be worth lifting that for NeoChat. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466625] New: Cursor is too red in X11 session
https://bugs.kde.org/show_bug.cgi?id=466625 Bug ID: 466625 Summary: Cursor is too red in X11 session Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Night Color Assignee: plasma-b...@kde.org Reporter: gudvinr+...@gmail.com Target Milestone: 1.0 SUMMARY In X11 session, when night mode is active, white breeze cursor looks way redder than every other white object on the screen, it's basically like ripe orange. STEPS TO REPRODUCE 1. Select breeze cursor theme 2. enable night mode OBSERVED RESULT Red cursor EXPECTED RESULT Tinted white cursor SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-zen1-1-zen (64-bit) Graphics Platform: X11 Graphics Processor: AMD Radeon RX Vega M GL Graphics ADDITIONAL INFORMATION I can't really make screenshot because it turns white when you do screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466589] plasmashell memory usage grows rapidly and consumes all available RAM
https://bugs.kde.org/show_bug.cgi?id=466589 Pawel changed: What|Removed |Added Version|5.27.1 |5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466624] Power profiles of the placeholder driver are ignored
https://bugs.kde.org/show_bug.cgi?id=466624 --- Comment #1 from Ilya Fedin --- Oops, swap the observed and expected results -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 466587] Wrong German translation "Aktualisierung ausgewählt"
https://bugs.kde.org/show_bug.cgi?id=466587 --- Comment #2 from Nate Graham --- Fair. I can do that. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466624] New: Power profiles of the placeholder driver are ignored
https://bugs.kde.org/show_bug.cgi?id=466624 Bug ID: 466624 Summary: Power profiles of the placeholder driver are ignored Classification: Plasma Product: Powerdevil Version: 5.27.1 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: fedin-ilja2...@ya.ru CC: m...@ratijas.tk Target Milestone: --- SUMMARY This driver exists for a reason: it allows applications to query system-wide energy saving mode even if there's no hardware support. Since Plasma ignores these profiles, it's not possible to set power-saver mode so applications consume less battery. STEPS TO REPRODUCE 1. Have hardware without power-profiles-daemon special driver 2. Try to enable energy saving mode OBSERVED RESULT Plasma lets me to do so EXPECTED RESULT Plasma hides the option from the UI SOFTWARE/OS VERSIONS Operating System: NixOS 23.05 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-zen1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 5.7 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466589] plasmashell memory usage grows rapidly and consumes all available RAM
https://bugs.kde.org/show_bug.cgi?id=466589 --- Comment #3 from Pawel --- Hi Nate, I only have 1 screen and I am not aware of anything changing my screen settings. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] resizing a window leads to malformed decoration under Aurorae
https://bugs.kde.org/show_bug.cgi?id=465790 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464707] System Settings crashed in KScreen::Config::outputs() when changing settings and then saving or reverting
https://bugs.kde.org/show_bug.cgi?id=464707 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466589] plasmashell memory usage grows rapidly and consumes all available RAM
https://bugs.kde.org/show_bug.cgi?id=466589 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #2 from Nate Graham --- Do you have multiple screens? If so does this stop when you use `xrandr` to manually enforce a particular configuration? And do you have anything automatically changing screen settings outside of KScreen? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466551] Increased CPU consumption when you scroll through task applet
https://bugs.kde.org/show_bug.cgi?id=466551 --- Comment #3 from gudvinr+...@gmail.com --- I also checked out X11 session and well, if you do this there, CPU usage for all processes is less than 10-12%. >From that, Xorg and plasmashell processes consume more than half. So I am pretty sure that this is quite significant issue when same actions now take 5x more CPU time than old times. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466616] Option to set global overrides in Flatpak KCM
https://bugs.kde.org/show_bug.cgi?id=466616 Nate Graham changed: What|Removed |Added Summary|No option to set global |Option to set global |overrides in Flatpak KCM|overrides in Flatpak KCM Ever confirmed|0 |1 CC||n...@kde.org Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 466528] "Automatisch zur Gegenseite navigieren" is not an ideal translation for "Navigation wraps around"
https://bugs.kde.org/show_bug.cgi?id=466528 Nate Graham changed: What|Removed |Added Summary|Regression: "Switch to next |"Automatisch zur Gegenseite |desktop" shortcut doesn't |navigieren" is not an ideal |cycle through the desktops |translation for "Navigation |anynmore|wraps around" Version|5.27.1 |unspecified Product|systemsettings |i18n Status|REPORTED|CONFIRMED Component|kcm_keys|de CC||n...@kde.org Assignee|plasma-b...@kde.org |kde-i18n...@kde.org Ever confirmed|0 |1 --- Comment #3 from Nate Graham --- Yep, let's. In particular the presence of the word "Automatisch" seems a bit misleading. There's nothing automatic about this behavior. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466475] Welcome Center shows on every boot
https://bugs.kde.org/show_bug.cgi?id=466475 aron...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from aron...@gmail.com --- (In reply to Nate Graham from comment #5) > It will appear once on the login after the package is first installed. The > intention is that quitting the app in in any way will write > "ShouldShow=false" to the config file and prevent autostart in the future. > This is working for me. So we need to figure out why it's not working for > you, and under which circumstances it happens. > > Can you open the config file in a text editor, manually open the app, and > see if "ShouldShow=false" gets written to the config file in any of the > following circumstances: > - Clicking the "Skip" button on the first page > - Clicking the "Finish" button on the last page > - Clicking the close button on the titlebar > - Clicking the close button on the Task manager tooltip for the window > - Hitting Ctrl+Q on the keyboard > - Hitting Alt+F4 on the keyboard > > After testing each one, if it *does* write "ShouldShow=false" into the > config file, you can remove it from the file before testing the next method. Skip or Finish writes the line but closing in other ways doesn't. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466408] Plasma Shell glitches out after waking from sleep when external display is set as primary - on wayland
https://bugs.kde.org/show_bug.cgi?id=466408 --- Comment #6 from Nate Graham --- No, to be honest it's not very fun. I appreciate the appreciation! If the issue goes away when you set both of your screens to have the same refresh rate, it's almost certainly the same issue despite the slightly different symptoms. If not, it's probably something else and not a duplicate. Can you check? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466608] Transparency bug when using Aurorae window decorations
https://bugs.kde.org/show_bug.cgi?id=466608 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
