[kwin] [Bug 466708] Alt+shift does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=466708 --- Comment #2 from Ahmed --- (In reply to Nate Graham from comment #1) > Works for me. I thought that it is a common issue with Wayland, because it happens also on GNOME (Wayland). I use a laptop (HP Probook 450 G1), and when I use alt+shift in general, they do not work together for unknown reason, but on KDE from keyboard settings I could switch "alt" with "meta", and that fixed the issue on X11, but on Wayland they register different keys for unknown reason. If it is an issue with the keyboard, why does it only happen under Wayland? -- 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 --- Comment #21 from tagwer...@innerjoin.org --- (In reply to Bug Janitor Service from comment #20) > A possibly relevant merge request was started @ > https://invent.kde.org/frameworks/baloo/-/merge_requests/113 >From the MR: > ... After I applied this patch, killed baloo_file, deleted an indexed file, > and started baloo_file again, > the deleted file didn't appear anymore in the balooseach results. That didn't > happen with the > unpatched baloo, the deleted file was still there and trying to open it with > KRunner did nothing ... So the test sequence is: Create a test file Check that it is indexed (including file content) Kill baloo Delete the file Restart baloo and check whether the file is still in the index. Yes, the file is still in the index, as per baloosearch. This is slightly more specific than comment 0 but consistent with what I've seen when having deleted a large folder and not waiting until baloo has cleared all its entries or if there are too many deletes and notifications "overflow", as mentioned in https://bugs.kde.org/show_bug.cgi?id=437754#c1 It might be worth mentioning a couple of the wraiths in the mist... Where the device number has changed and baloo reindexed the files, deleting the test file even when baloo_file is running will not result in the earlier entry being removed. This is in the cases with BTRFS and multiple subvols, such as with openSUSE, where "baloosearch -i searchstring" shows several hits with different DocIDs, see https://bugs.kde.org/show_bug.cgi?id=402154#c12 There's also the possibility that krunner caches the data from baloo and presents remembered results... Revisited with Neon Unstable: Plasma: 5.27.80 Frameworks: 5.104.0 Qt: 5.15.8 Kernel: 5.19.0-35-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466711] crash when creating 2 concurrent folders/files
https://bugs.kde.org/show_bug.cgi?id=466711 --- Comment #2 from Maksim --- I don't know how to show it, the desktop crashes in such a way that it is not noticeable for the debugger :| The error report appears, but after 10 seconds it disappears without having time to collect the logs This is all I can provide when using dgb some errors poll.o:43 process memory check did not reveal any errors (P.S After this command, now closing the console will turn off and the desktop, this did not happen before and I could freely close the console) At first I thought it was Dbus, but as shown, everything is fine with it ➜ ~ kstart plasmashell Omitting both --window and --windowclass arguments is not recommended kf.plasma.quick: Applet preload policy set to 1 Checking screens: available: (QScreen(0x556aeb942830, name="eDP1"), QScreen(0x556aeb9a4470, name="DP1")) redundant: QHash() fake: QSet() all: (QScreen(0x556aeb942830, name="eDP1"), QScreen(0x556aeb9a4470, name="DP1")) org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl) file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:534:9: QML Label: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:499:13: QML Label: Binding loop detected for property "height" Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:499:13: QML Label: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:534:9: QML Label: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:556:5: QML Label: Binding loop detected for property "height" Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml" Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml" file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95: TypeError: Cannot read property 'airplaneModeAvailable' of null file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95: TypeError: Cannot read property 'airplaneModeAvailable' of null file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:18:1: QML MouseArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout Both point size and pixel size set. Using pixel size. file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/Tooltip.qml:69:9: QML GridLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" Loading Calendar plugin HolidaysEventsPlugin(0x556af5461690) file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0 org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout 13 Both point size and pixel size set. Using pixel size. file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" kde.systemtray: DBusMenu
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 --- Comment #10 from Aleksey Kontsevich --- (In reply to Fabian Vogt from comment #9) > Apparently you use the QML software renderer. That should not be the case, > did you configure that explicitly in kcmshell kcm_qtquicksettings? No, after the crash "kcmshell5 kcm_qtquicksettings" appeared for me so I tried any variants: Program, OpenGL, Automatic - all crashes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427147] Often the background parser causes crashes
https://bugs.kde.org/show_bug.cgi?id=427147 Sven Brauch changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #9 from Sven Brauch --- changing status -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427147] Often the background parser causes crashes
https://bugs.kde.org/show_bug.cgi?id=427147 --- Comment #8 from Sven Brauch --- @anonymous11oneele...@gmail.com, please take your issue to a different report -- it is not the same issue, and 80% of issues are with the background parser, they can not all be tracked in the same repot. Thanks. :) @Mattia Basaglia Sorry for not replying any more after you posted the backtrace, I overlooked it. The libclang you had the issue with is 5 versions old, if you are still using KDevelop, does it still happen with the current libclang? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466236] With NVIDIA GPU, plasmashell crashes in QSGSoftwareRenderableNode::update() when filtering in the Klipper history popup with Cyrillic keyboard layout applied
https://bugs.kde.org/show_bug.cgi?id=466236 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #9 from Fabian Vogt --- Apparently you use the QML software renderer. That should not be the case, did you configure that explicitly in kcmshell kcm_qtquicksettings? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #28 from Aleksey Kontsevich --- (In reply to Fabian Vogt from comment #27) > This bug report is specific to 32bit x86. If you see something on x86_64, > that's a different bug. > > Please do not reopen this bug. Ah sorry, not mine, mine is: https://bugs.kde.org/show_bug.cgi?id=466236 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 Fabian Vogt changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #27 from Fabian Vogt --- This bug report is specific to 32bit x86. If you see something on x86_64, that's a different bug. Please do not reopen this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 Aleksey Kontsevich changed: What|Removed |Added Resolution|DOWNSTREAM |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #26 from Aleksey Kontsevich --- (In reply to Jiri Slaby from comment #25) > (In reply to Jiri Slaby from comment #23) > > Maybe we should continue in downstream (openSUSE miscompilation) or upstream > > (qt bug). > > Resolved downstream by dropping non-sse2 builds of qt libraries (which are > apparently broken), see the downstream bug. > https://bugzilla.suse.com/show_bug.cgi?id=1208188 They said it is a different bug! https://bugzilla.suse.com/show_bug.cgi?id=1208188#c12 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466697] Permanent crashes of Powerdevil at launch in a VNC session
https://bugs.kde.org/show_bug.cgi?id=466697 --- Comment #6 from tagwer...@innerjoin.org --- (In reply to tagwerk19 from comment #2) > ... a couple of 'just updated' F37 systems (KVM guests) ... Crashes (in X11) if the VM has the QXL video. Switch to Virtio and it goes away... I think the crashes are independent of the: ... org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" At least, I get that message whether starting with QXL or Virtio -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458233] In some games, controlling the camera with mouse, camera occasionally snaps into a different position when using Wayland
https://bugs.kde.org/show_bug.cgi?id=458233 --- Comment #14 from Yao Mitachi --- I started using Plasma again to test if this still happens. It does. However, Gamescope (which stopped working for me back in December) is working again for me, so I won't have to use GNOME. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 Jiri Slaby changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM URL||https://bugzilla.suse.com/s ||how_bug.cgi?id=1208188 --- Comment #25 from Jiri Slaby --- (In reply to Jiri Slaby from comment #23) > Maybe we should continue in downstream (openSUSE miscompilation) or upstream > (qt bug). Resolved downstream by dropping non-sse2 builds of qt libraries (which are apparently broken), see the downstream bug. https://bugzilla.suse.com/show_bug.cgi?id=1208188 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 --- Comment #8 from Benjamin Xiao --- @Nate Graham, I think that's a perfect way to do it! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466571] Kate crashes on MacOS when using the "Save Copy As..." menu option
https://bugs.kde.org/show_bug.cgi?id=466571 Waqar Ahmed changed: What|Removed |Added Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/fram |eworks/ktexteditor/commit/7 |eworks/ktexteditor/commit/c |f2dd9de8e2a70496de8275a4c16 |bec4b03ebd467a98f1dff44ad1c |067942926620|e0ee11088950 --- Comment #3 from Waqar Ahmed --- Git commit cbec4b03ebd467a98f1dff44ad1ce0ee11088950 by Waqar Ahmed. Committed on 03/03/2023 at 06:42. Pushed by waqar into branch 'kf5'. documentSaveCopyAs: Use async job api exec can have unintended and hard to understand side effects, and in this case we can just the async api easily as there is no need for blocking M +17 -16 src/document/katedocument.cpp M +1-1src/document/katedocument.h https://invent.kde.org/frameworks/ktexteditor/commit/cbec4b03ebd467a98f1dff44ad1ce0ee11088950 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 436780] Elisa crashes after opening a directory from Files menu.
https://bugs.kde.org/show_bug.cgi?id=436780 BL changed: What|Removed |Added CC||baby-l...@earthling.net -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Rick Scholten changed: What|Removed |Added CC|khr...@proton.me| -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427147] Often the background parser causes crashes
https://bugs.kde.org/show_bug.cgi?id=427147 --- Comment #7 from anonymous11oneele...@gmail.com --- Created attachment 156945 --> https://bugs.kde.org/attachment.cgi?id=156945=edit Backtrace My backtrace running the version from the manjaro repo (version 5.10.221202) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466758] New: KDE agent window keeps popping up when canceling administrator password prompt
https://bugs.kde.org/show_bug.cgi?id=466758 Bug ID: 466758 Summary: KDE agent window keeps popping up when canceling administrator password prompt Classification: Applications Product: dolphin Version: 22.12.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: ananta...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 156944 --> https://bugs.kde.org/attachment.cgi?id=156944=edit Right-clicking on a folder with a padlock in it and selecting "Open as Administrator" in the context menu. When I right-click on a folder with a padlock in it and select "Open as Administrator" in the context menu, a password prompt appears asking me to enter my password. However, if I decide to cancel the prompt by clicking on the "Cancel" button, the KDE agent window keeps popping up repeatedly. I have to click on the "Cancel" button 13 times in order to make the window go away. STEPS TO REPRODUCE 1. Right-click on a folder with a padlock in it. 2. Select "Open as Administrator" in the context menu. 3. Wait for the password prompt to appear. 4. Click on the "Cancel" button to cancel the prompt. OBSERVED RESULT The KDE agent window keeps popping up repeatedly, and I have to click on the "Cancel" button 13 times in order to make it go away. EXPECTED RESULT The KDE agent window should disappear after I click on the "Cancel" button once. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27 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.
[kdevelop] [Bug 427147] Often the background parser causes crashes
https://bugs.kde.org/show_bug.cgi?id=427147 anonymous11oneele...@gmail.com changed: What|Removed |Added CC||anonymous11oneeleven@gmail. ||com --- Comment #6 from anonymous11oneele...@gmail.com --- I observe the same behavior. After I installed KDevelop (on Manjaro from the official repo, version 5.10.221202), it worked for a couple weeks, then it started crashing. Reinstalling did not help. Deleting everything containing the string "kdev" in the file or folder name within the home directory, including all subdirectories, did not help. However installing the flatpak (from flathub) did help, again only for a few weeks. Then out of nowhere I started getting the same kind of crash again, always at 13-14% according to the progress bar on the bottom right. Reinstalling the flatpak and deleting all the aforementioned files did not help. Reinstalling the version from the repo did not help either. Then I tried opening another project. One that was in fact not a C++ project, but php/python. KDevelop crashed again while parsing, this time at about 70% (sometimes a few more, sometimes less). It seems that at some point something "snaps", and the issue just keeps happening regularly, and in more than one project. Disabling the background parser in the settings stops the crashes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #2 from Bharadwaj Raju --- Probably the filter, yes. Not entirely sure about the cause, but maybe the logic we use for the secondary point is too slow? Will need profiling. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466727] Plasmashell doesn't start properly under Wayland.
https://bugs.kde.org/show_bug.cgi?id=466727 --- Comment #2 from Doug --- (In reply to David Edmundson from comment #1) > Please attach log from when you run plasmashell --replace plasmashell is still not starting properly, but plasmashell --replace is now working. I tried to pull logs after failing to start, and after plasmashell --replace. I got the same thing both times: journalctl /usr/bin/plasmashell -f 2> plasmashell.log ✔ Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead. Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead. Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead. Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead. Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead. Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead. Mar 03 00:15:35 douglas-home plasmashell[1864]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Mar 03 00:15:35 douglas-home plasmashell[1864]: 2 Mar 03 00:15:35 douglas-home plasmashell[1864]: file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/main.qml:30:5: Unable to assign [undefined] to bool Mar 03 00:15:35 douglas-home plasmashell[1864]: The Wayland connection broke. Did the Wayland compositor die? I don't know if any of that helps. I don't know how to work with logs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466757] New: none
https://bugs.kde.org/show_bug.cgi?id=466757 Bug ID: 466757 Summary: none Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: reven...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.2.1-gentoo-x86_64 x86_64 Windowing System: Wayland Distribution: "Gentoo Linux" DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: on edit application from programm menu plasmashell crash The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f13cb4bd8a4 in QWidgetLineControl::internalSetText(QString const&, int, bool) () at /usr/lib64/libQt5Widgets.so.5 #5 0x7f13c9b4bc5b in () at /usr/lib64/libKF5KIOWidgets.so.5 #6 0x7f13c9b4f3d8 in () at /usr/lib64/libKF5KIOWidgets.so.5 #7 0x7f13c9b4f91a in () at /usr/lib64/libKF5KIOWidgets.so.5 #8 0x7f13c9b5036d in KPropertiesDialog::KPropertiesDialog(QUrl const&, QWidget*) () at /usr/lib64/libKF5KIOWidgets.so.5 #9 0x7f13c9b5042d in KPropertiesDialog::showDialog(QUrl const&, QWidget*, bool) () at /usr/lib64/libKF5KIOWidgets.so.5 #10 0x7f13883c02e0 in () at /usr/lib64/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so #11 0x7f1388390877 in () at /usr/lib64/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so #12 0x7f13883987f7 in () at /usr/lib64/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so #13 0x7f138838aa27 in () at /usr/lib64/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so #14 0x7f138838cc0f in () at /usr/lib64/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so #15 0x7f13cbccc9f3 in () at /usr/lib64/libQt5Qml.so.5 #16 0x7f13cbba36c9 in () at /usr/lib64/libQt5Qml.so.5 #17 0x7f13cbba56bd in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /usr/lib64/libQt5Qml.so.5 #18 0x7f13cbbc1e03 in () at /usr/lib64/libQt5Qml.so.5 #19 0x7f13cbbc570f in () at /usr/lib64/libQt5Qml.so.5 #20 0x7f13cbb577f0 in () at /usr/lib64/libQt5Qml.so.5 #21 0x7f13cbbc1e03 in () at /usr/lib64/libQt5Qml.so.5 #22 0x7f13cbbc570f in () at /usr/lib64/libQt5Qml.so.5 #23 0x7f13cbb569fe in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib64/libQt5Qml.so.5 #24 0x7f13cbce7a4b in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib64/libQt5Qml.so.5 #25 0x7f13cbc9702f in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib64/libQt5Qml.so.5 #26 0x7f13cbc98808 in () at /usr/lib64/libQt5Qml.so.5 #27 0x7f13cbccc4c5 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib64/libQt5Qml.so.5 #28 0x7f13ca6b75bd in () at /usr/lib64/libQt5Core.so.5 #29 0x7f13ca6b7864 in () at /usr/lib64/libQt5Core.so.5 #30 0x7f13cb35c8b2 in QAction::triggered(bool) () at /usr/lib64/libQt5Widgets.so.5 #31 0x7f13cb35f64b in QAction::activate(QAction::ActionEvent) () at /usr/lib64/libQt5Widgets.so.5 #32 0x7f13cb4eea9a in () at /usr/lib64/libQt5Widgets.so.5 #33 0x7f13cb4f6afc in () at /usr/lib64/libQt5Widgets.so.5 #34 0x7f13cb3a7028 in QWidget::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #35 0x7f13cb36344e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #36 0x7f13cb36bd30 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #37 0x7f13ca683d98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #38 0x7f13cb369d64 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib64/libQt5Widgets.so.5 #39 0x7f13cb3c0d3d in () at /usr/lib64/libQt5Widgets.so.5 #40 0x7f13cb3c3d28 in () at /usr/lib64/libQt5Widgets.so.5 #41 0x7f13cb36344e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #42 0x7f13ca683d98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #43 0x7f13cab2727f in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib64/libQt5Gui.so.5 #44 0x7f13cab062bb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib64/libQt5Gui.so.5 #45 0x7f13cbf644b0 in () at /usr/lib64/libQt5WaylandClient.so.5 #46 0x7f13c932ddc8 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #47 0x7f13c932e068 in () at
[Kalk] [Bug 466756] New: blank window
https://bugs.kde.org/show_bug.cgi?id=466756 Bug ID: 466756 Summary: blank window Classification: Applications Product: Kalk Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: hanyo...@protonmail.com Reporter: mashkal2...@gmail.com CC: espi...@gmail.com Target Milestone: --- SUMMARY *** 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 *** Blank screen STEPS TO REPRODUCE 1. Open app 2. 3. OBSERVED RESULT blank screen EXPECTED RESULT not blank screen SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 466755] New: When changing a recurring event ONCE kde calendars (kontact, kalendar, or digital clock calendar) will not show it correctly
https://bugs.kde.org/show_bug.cgi?id=466755 Bug ID: 466755 Summary: When changing a recurring event ONCE kde calendars (kontact, kalendar, or digital clock calendar) will not show it correctly Classification: Applications Product: kdepim Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libkdepim Assignee: kdepim-b...@kde.org Reporter: voncl...@gmail.com Target Milestone: --- SUMMARY *** I use radicale (used to use google calendar) and I will have recurring events for my schedule for example meal prepping every saturday. Wellthis week I want to mealprep on friday so i make the change in a calendar client (kontact or google calendar) I will make the change to modify the event once on the 4th of march to move it to the 3rd NOT to modify all events just this one specific one.KDE calendars will show the 4th still has mealprep, and so does the 3rd. I tried with google calendar and radicale - it is the same result. *** STEPS TO REPRODUCE 1. Modify one event of a recurring series in a calendar client 2. Wait a few minutes for it to update in KDE calendar client 3. OBSERVED RESULT Show incorrect data EXPECTED RESULT Show the change dont show it for the 4th and the 3rd. 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 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465973] Display distorts when switching to 5120x1440 resolution
https://bugs.kde.org/show_bug.cgi?id=465973 --- Comment #10 from adavila89+...@protonmail.com --- (In reply to Nate Graham from comment #9) > Well darn. Thanks for following up! What's something I can do to help with debugging this? I'm super new to Linux, so I'm not entirely sure where to really begin. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 464689] Add more relevant document properties in Properties dialog
https://bugs.kde.org/show_bug.cgi?id=464689 --- Comment #4 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 465516] kwin-wayland crash Failed to recreate shadow for PlasmaQuick
https://bugs.kde.org/show_bug.cgi?id=465516 --- Comment #4 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.
[okular] [Bug 464952] Some PDF documents do not print on my printer without forcing rasterization
https://bugs.kde.org/show_bug.cgi?id=464952 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.
[krita] [Bug 465199] App freezes when I use animation docker
https://bugs.kde.org/show_bug.cgi?id=465199 sh_zam changed: What|Removed |Added CC||emmetoneill@gmail.com --- Comment #10 from sh_zam --- Thanks a lot for the recording! This looks like an internal deadlock somewhere in Krita. This is causing the app to not close, hence you have to invoke the Force Stop to kill the app. Let me ping Emmet, they manage animation side of Krita to see if they have any clue why/where something like this would happen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466753] Context menu goes transparent on monitor scaled higher than other monitors
https://bugs.kde.org/show_bug.cgi?id=466753 semperve...@gmail.com changed: What|Removed |Added CC||semperve...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 466754] New: Kalendar crashes when editing or adding events
https://bugs.kde.org/show_bug.cgi?id=466754 Bug ID: 466754 Summary: Kalendar crashes when editing or adding events Classification: Applications Product: kalendar Version: 22.12.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: voncl...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (22.12.3) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.103.0 Operating System: Linux 5.19.13 x86_64 Windowing System: X11 Distribution: LFS DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: Tried to edit and add events via Kalendar it crashes every time. The crash can be reproduced every time. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [KCrash Handler] #4 0x7f7fe4c221f5 in QDateTime::operator=(QDateTime const&) () at /usr/lib/libQt5Core.so.5 #5 0x561fa39a46d4 in () #6 0x7f7fe4d71066 in () at /usr/lib/libQt5Core.so.5 #7 0x7f7fe4cd55a5 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #8 0x7f7fe4d10f87 in () at /usr/lib/libQt5Core.so.5 #9 0x7f7fe4d710a0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f7fe4cd55a5 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #11 0x7f7fe4d10f87 in () at /usr/lib/libQt5Core.so.5 #12 0x7f7fe4d710a0 in () at /usr/lib/libQt5Core.so.5 #13 0x7f7fe4cd55a5 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #14 0x7f7fe4d10f87 in () at /usr/lib/libQt5Core.so.5 #15 0x7f7fe4d710a0 in () at /usr/lib/libQt5Core.so.5 #16 0x7f7fe4cd55a5 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #17 0x7f7fe70a8ba0 in () at /usr/lib64/libKF5ItemModels.so.5 #18 0x7f7fe70aa107 in () at /usr/lib64/libKF5ItemModels.so.5 #19 0x7f7fe4d71066 in () at /usr/lib/libQt5Core.so.5 #20 0x7f7fe4cd55a5 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #21 0x7f7fe7667d9d in () at /usr/lib64/libKF5AkonadiCore.so.5 #22 0x7f7fe76713a1 in () at /usr/lib64/libKF5AkonadiCore.so.5 #23 0x7f7fe4d710a0 in () at /usr/lib/libQt5Core.so.5 #24 0x7f7fe759ac70 in Akonadi::Monitor::itemChanged(Akonadi::Item const&, QSet const&) () at /usr/lib64/libKF5AkonadiCore.so.5 #25 0x7f7fe75ab846 in Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification const&, QVector const&, Akonadi::Collection const&, Akonadi::Collection const&) () at /usr/lib64/libKF5AkonadiCore.so.5 #26 0x7f7fe75acef0 in Akonadi::MonitorPrivate::emitNotification(QSharedPointer const&) () at /usr/lib64/libKF5AkonadiCore.so.5 #27 0x7f7fe75aec75 in Akonadi::MonitorPrivate::flushPipeline() () at /usr/lib64/libKF5AkonadiCore.so.5 #28 0x7f7fe75aef69 in Akonadi::MonitorPrivate::dataAvailable() () at /usr/lib64/libKF5AkonadiCore.so.5 #29 0x7f7fe4d71066 in () at /usr/lib/libQt5Core.so.5 #30 0x7f7fe4d710a0 in () at /usr/lib/libQt5Core.so.5 #31 0x7f7fe5118e05 in KJob::result(KJob*, KJob::QPrivateSignal) () at /usr/lib64/libKF5CoreAddons.so.5 #32 0x7f7fe511a30b in KJob::finishJob(bool) () at /usr/lib64/libKF5CoreAddons.so.5 #33 0x7f7fe4d66ab1 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #34 0x7f7fe59bc15f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #35 0x7f7fe4d3aa8a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #36 0x7f7fe4d3d4c1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #37 0x7f7fe4d92953 in () at /usr/lib/libQt5Core.so.5 #38 0x7f7fe04e2a6b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #39 0x7f7fe04e2d18 in () at /usr/lib/libglib-2.0.so.0 #40 0x7f7fe04e2dcf in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #41 0x7f7fe4d91fdf in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #42 0x7f7fe4d3944b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #43 0x7f7fe4d416c0 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #44 0x561fa396f23c in () #45 0x7f7fe4599b6b in __libc_start_main (main=0x561fa396cbb0, argc=1, argv=0x7ffdaf705928, init=, fini=, rtld_fini=, stack_end=0x7ffdaf705918) at ../csu/libc-start.c:308 #46 0x561fa396f7aa in () [Inferior 1 (process 6009) detached] Reported using DrKonqi -- You are receiving this mail because:
[kwin] [Bug 466753] Context menu goes transparent on monitor scaled higher than other monitors
https://bugs.kde.org/show_bug.cgi?id=466753 --- Comment #1 from semperve...@gmail.com --- Additional note: This bug only occurs when right clicking with the cursor on the higher scaled monitor (in my case the 4k scaled to 200%) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466753] New: Context menu goes transparent on monitor scaled higher than other monitors
https://bugs.kde.org/show_bug.cgi?id=466753 Bug ID: 466753 Summary: Context menu goes transparent on monitor scaled higher than other monitors Classification: Plasma Product: kwin Version: 5.27.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: semperve...@gmail.com Target Milestone: --- Created attachment 156943 --> https://bugs.kde.org/attachment.cgi?id=156943=edit Window Manager debug output SUMMARY When using a mixed monitor setup in Wayland, right clicking on the desktop or task bar brings up a context menu. As soon as you move the cursor, the context menu will go transparent leaving only the blur effect, until an item is hovered over. Once hovered over, that item will remain permanently solid until the menu is closed. STEPS TO REPRODUCE 0. Log in to a Wayland desktop session. 1. Set up at least two monitors (three recommended) of mixed resolution. To replicate this exact setup, use two 1080p monitors on the left and right, and one 4k monitor in the center. 2. Right click the wallpaper, hold still for a moment to see that it is solid, then move your mouse. 3. Once it is transparent, hover your mouse over each item in the menu to turn them back to opaque. OBSERVED RESULT Menu goes transparent, leaving only the blur layer, until the cursor hovers over an item - which then turns each item hovered opaque until the menu closes. EXPECTED RESULT Menu stays mostly opaque with all of its compositing effects remaining underneath. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2.1-zen1-1-zen/5.27.1 (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 CPU: AMD Ryzen 9 5900X (24) @ 3.700GHz GPU: AMD ATI Radeon RX 5600 OEM/5600 XT / 5700/5700 XT Memory: 5964MiB / 64211MiB ADDITIONAL INFORMATION This bug may have been occurring for several versions. Video of bug in action: https://www.youtube.com/watch?v=sqD8b70jkqA -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466634] 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 --- Comment #14 from kevin.david.h...@gmail.com --- Awesome Nate, thanks for the quick turnaround and attentiveness. I really appreciate it. Wish the devs I work with were this quick. On Wed, Mar 1, 2023 at 9:39 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=466634 > > --- Comment #12 from Nate Graham --- > Definitely not a fix, just a workaround that helps to confirm that this is > Bug > 466362. We'll see if we can get it fixed soon! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466752] Wallpaper assignments are forgotten between sessions with multiple screens and activities
https://bugs.kde.org/show_bug.cgi?id=466752 Bug Janitor Service changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.24.7 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.24.7, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466395] Random crashing
https://bugs.kde.org/show_bug.cgi?id=466395 --- Comment #7 from Sid --- Hi, yeah I think I'm fairly certain that its something to do with the taskbar, the taskbar is the most visible issue when plasmashell dies. now i dont know if its a cause or a symptom, but more often then not its the taskbar that freezes first (with everything else working just fine) before everything comes crashing down -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466752] Wallpaper assignments are forgotten between sessions with multiple screens and activities
https://bugs.kde.org/show_bug.cgi?id=466752 David Hillman changed: What|Removed |Added CC||davidahillman+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466752] New: Wallpaper assignments are forgotten between sessions with multiple screens and activities
https://bugs.kde.org/show_bug.cgi?id=466752 Bug ID: 466752 Summary: Wallpaper assignments are forgotten between sessions with multiple screens and activities Classification: Plasma Product: plasmashell Version: 5.24.7 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: davidahillman+...@gmail.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 SUMMARY This desktop machine has two physical displays, and multiple activities configured. Each activity has a unique wallpaper, that is assigned to both screens. Each time the user logs in, 1 screen each of several randomly-selected activities switches back to the default wallpaper. Resetting the wallpaper assignments lasts only until the next login, when a new randomly-selected set of activities again lose their wallpaper configuration. STEPS TO REPRODUCE 1. Create x activities where x > 2 2. Switch to activity x1 3. Set image 1 as the wallpaper for 2+ screens 4. Repeat steps 2 and 3 for activities x2...xN, using a different image for each. 5. Log out 6. Log in. OBSERVED RESULT Observe that a random selection of activities will no longer display the previously-configured image as the wallpaper on one screen -- instead they will have reverted to the default wallpaper. I have never witnessed both screens' wallpapers being lost, it is always just one. EXPECTED RESULT Wallpaper configuration should be saved, and persist between user sessions. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04.2 LTS -- updated immediately before logging this bug KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel: 5.19.0-35-generic ADDITIONAL INFORMATION In this instance, both displays are running at 4K resolution ( 3840x2160 ) -- I have not tested this behavior in other configurations. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445518] KDE Plasma doesn't respect icon theme for some applications and application icons
https://bugs.kde.org/show_bug.cgi?id=445518 --- Comment #32 from mozo --- Plasma 5.27.2 - the bug is still here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463024] Plasma doesn't respect Sub-pixel rendering for system tray and desktop
https://bugs.kde.org/show_bug.cgi?id=463024 --- Comment #32 from mozo --- Plasma 5.27.2 - the bug is still here. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 --- Comment #6 from Pierre Racz --- Created attachment 156941 --> https://bugs.kde.org/attachment.cgi?id=156941=edit New crash information added by DrKonqi systemsettings (5.27.2) using Qt 5.15.6 Here is the report of the problem using KDE 5.27.2 plasmashell 5.27.2 Qt: 5.15.6 KDE Frameworks: 5.103.0 -- Backtrace (Reduced): #4 0x7fe0d2b976b9 in QWidget::hide() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #6 0x7fe0d2d057d1 in QMenuBar::changeEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fe0d2baeb1f in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fe0d2b6bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7fe0d1cbae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 --- Comment #5 from Pierre Racz --- Created attachment 156940 --> https://bugs.kde.org/attachment.cgi?id=156940=edit New crash information added by DrKonqi systemsettings (5.27.2) using Qt 5.15.6 Here is the problem reproduced with KDE 5.27.2 plasmashell 5.27.2 Qt: 5.15.6 KDE Frameworks: 5.103.0 -- Backtrace (Reduced): #4 0x7f3cc01976b9 in QWidget::hide() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #6 0x7f3cc03057d1 in QMenuBar::changeEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f3cc01aeb1f in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f3cc016bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f3cbf4bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 Pierre Racz changed: What|Removed |Added CC||pr...@genetec.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 --- Comment #4 from Pierre Racz --- Created attachment 156939 --> https://bugs.kde.org/attachment.cgi?id=156939=edit New crash information added by DrKonqi systemsettings (5.27.2) using Qt 5.15.6 Here is the crash report updated for KDE 5.27.2 plasmashell 5.27.2 Qt: 5.15.6 KDE Frameworks: 5.103.0 -- Backtrace (Reduced): #4 0x7f71933976b9 in QWidget::hide() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #6 0x7f71935057d1 in QMenuBar::changeEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f71933aeb1f in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f719336bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f71924bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466475] Welcome Center doesn't write "ShouldShow=false" into config file when closed by a method other than the "Skip" and "finish" buttons
https://bugs.kde.org/show_bug.cgi?id=466475 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.3 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-welcome/commit/f4 ||c50c5ee61a2d2eaf3511959b20f ||9fac87489e6 Status|ASSIGNED|RESOLVED --- Comment #11 from Nate Graham --- Git commit f4c50c5ee61a2d2eaf3511959b20f9fac87489e6 by Nate Graham. Committed on 02/03/2023 at 23:58. Pushed by ngraham into branch 'Plasma/5.27'. Set "ShouldShow=false" when quitting the app using amy method ...Not just the Skip and Finish buttons. This isn't an issue in the 6.0 version of the app which uses different heuristics to determine whether to autostart the app, but it is an isue for the 5.27 version which simply checks for the presence of "ShouldShow=False" in the config file. The fact that we haven't gotten absolute avalance of bug reports about this indicates that nearly all of the people who encounter the welcome app are either clicking on the Skip button, or going through the entire thing and then clicking on the Finish button. So that's nice at least. Test Plan: remove "ShouldShow=false" from ~/.config/plasma-welcomerc, launch the app, and quit it with Ctrl+Q, Alt+F4, titlebar close button, or Task Manager close button/menu item FIXED-IN: 5.27.3 M +2-8src/contents/ui/main.qml M +1-0src/main.cpp https://invent.kde.org/plasma/plasma-welcome/commit/f4c50c5ee61a2d2eaf3511959b20f9fac87489e6 -- 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 Ganton changed: What|Removed |Added CC||ku...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 Pierre Racz changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- Ever confirmed|0 |1 --- Comment #3 from Pierre Racz --- I can reproduce it with KDE 5.27.2 plasmashell 5.27.2 Qt: 5.15.6 KDE Frameworks: 5.103.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 185710] wrong direction in "slide" plugin
https://bugs.kde.org/show_bug.cgi?id=185710 --- Comment #27 from Roey Katz --- I'm on Plasma 5.27. This bug is still there. I thought this has gotten resolved? I've never seen it working correctly, for what it's worth; the slide direction is the opposite of what is expected, when transitioning between one side to the other of a virtual desktop matrix of 2 rows of 3 columns. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466751] Window title stripped after dash
https://bugs.kde.org/show_bug.cgi?id=466751 --- Comment #2 from jan...@waterkant.dev --- Created attachment 156938 --> https://bugs.kde.org/attachment.cgi?id=156938=edit Screenshot with "classic" task bar -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466751] Window title stripped after dash
https://bugs.kde.org/show_bug.cgi?id=466751 --- Comment #1 from jan...@waterkant.dev --- Created attachment 156937 --> https://bugs.kde.org/attachment.cgi?id=156937=edit Screenshot of the bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466751] New: Window title stripped after dash
https://bugs.kde.org/show_bug.cgi?id=466751 Bug ID: 466751 Summary: Window title stripped after dash Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: jan...@waterkant.dev Target Milestone: 1.0 SUMMARY Opening an Virtual-Machine with virt-manager which has an dash "-" in the name, in the window preview all characters after and the dash itself are stripped from the name. The same is happening with an RDP-Connection opened with Remmina. STEPS TO REPRODUCE 1. Create a virt-manager vm with a dash in the name, or save an RDP-connection with a dash i the name in Remmina 2. Open the vm or RDP-Connection 3. Hover over the task icon and only the characters before the dash are shown OBSERVED RESULT Window title is stripped by dash EXPECTED RESULT Window title is fully visible SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFO The effect only occures in the window-preview title. When I change the style to "classic" and disable grouping the window title is shown correctly in the taskbar but not in the preview. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 405963] Firefox HTML5 player does not retain app volume setting when forwarded
https://bugs.kde.org/show_bug.cgi?id=405963 g...@section9.follonica.org changed: What|Removed |Added CC||g...@section9.follonica.org --- Comment #5 from g...@section9.follonica.org --- Still reproduceable with Firefox 110, Fedora 37 and Plasma 5.27.2. Audio volume get reset to 100% right after stream playback or seeking. Stream pause causes a volume reset only if the pause is longer than ~5 seconds. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 466750] Akonadi crashes
https://bugs.kde.org/show_bug.cgi?id=466750 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 466750] Akonadi crashes
https://bugs.kde.org/show_bug.cgi?id=466750 Nicolas Fella changed: What|Removed |Added Product|kde |Akonadi Assignee|unassigned-b...@kde.org |kdepim-b...@kde.org Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466750] New: Akonadi crashes
https://bugs.kde.org/show_bug.cgi?id=466750
Bug ID: 466750
Summary: Akonadi crashes
Classification: I don't know
Product: kde
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: nicolas.fe...@gmx.de
Target Milestone: ---
Application: akonadi_followupreminder_agent (5.22.40 (23.03.40))
(Compiled from sources)
Qt Version: 6.4.2
Frameworks Version: 5.240.0
Operating System: Linux 6.1.14-200.fc37.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 37 (KDE Plasma)
DrKonqi: 5.27.80 [KCrashBackend]
-- Information about the crash:
When loggin into Qt6 session
The crash can be reproduced every time.
-- Backtrace:
Application: akonadi_followupreminder_agent (akonadi_followupreminder_agent),
signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 Akonadi::AttributeStorage::AttributeStorage(Akonadi::AttributeStorage
const&) (this=0x7e698b30, other=) at
/home/nico/kde6/src/akonadi/src/core/attributestorage.cpp:20
#6 0x7f80794b3044 in
Akonadi::AttributeStorage::operator=(Akonadi::AttributeStorage const&)
(this=0x1c25b38, other=...) at
/home/nico/kde6/src/akonadi/src/core/attributestorage.cpp:26
#7 0x7f80794f5bdf in
Akonadi::ItemPrivate::ItemPrivate(Akonadi::ItemPrivate const&) (this=0x1a4a890,
other=) at /home/nico/kde6/src/akonadi/src/core/item_p.h:197
#8 0x7f80794f60d0 in QSharedDataPointer::clone()
(this=0x19ef930) at /usr/include/qt6/QtCore/qshareddata.h:212
#9 QSharedDataPointer::detach_helper()
(this=this@entry=0x19ef930) at /usr/include/qt6/QtCore/qshareddata.h:218
#10 0x7f80794f2260 in QSharedDataPointer::detach()
(this=0x19ef930) at /usr/include/qt6/QtCore/qshareddata.h:40
#11 QSharedDataPointer::operator->() (this=0x19ef930) at
/usr/include/qt6/QtCore/qshareddata.h:43
#12 Akonadi::Item::setParentCollection(Akonadi::Collection const&)
(this=0x19ef930, parent=...) at
/home/nico/kde6/src/akonadi/src/core/item.cpp:172
#13 0x7f807951dffb in
Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification
const&, QList const&, Akonadi::Collection const&,
Akonadi::Collection const&) (this=0x17f8f40, msg=..., items=,
collection=, collectionDest=) at
/home/nico/kde6/src/akonadi/src/core/monitor_p.cpp:1048
#14 0x7f807951f279 in
Akonadi::MonitorPrivate::emitNotification(QSharedPointer
const&) (this=this@entry=0x17f8f40, msg=) at
/home/nico/kde6/src/akonadi/src/core/monitor_p.cpp:544
#15 0x7f80794bfb9e in
Akonadi::ChangeRecorderPrivate::emitNotification(QSharedPointer
const&) (this=0x17f8f40, msg=) at
/home/nico/kde6/src/akonadi/src/core/changerecorder_p.cpp:216
#16 0x7f807952283c in Akonadi::MonitorPrivate::dispatchNotifications()
(this=0x17f8f40) at /home/nico/kde6/src/akonadi/src/core/monitor_p.cpp:989
#17 0x7f8079522b1f in
Akonadi::MonitorPrivate::slotNotify(QSharedPointer
const&) (this=this@entry=0x17f8f40, msg=) at
/home/nico/kde6/src/akonadi/src/core/monitor_p.cpp:958
#18 0x7f80794beb47 in
Akonadi::ChangeRecorderPrivate::slotNotify(QSharedPointer
const&) (this=0x17f8f40, msg=) at
/home/nico/kde6/src/akonadi/src/core/changerecorder_p.cpp:37
#19 0x7f807951bd3f in Akonadi::MonitorPrivate::handleCommands()
(this=0x17f8f40) at /home/nico/kde6/src/akonadi/src/core/monitor_p.cpp:856
#20 0x7f80773ba370 in QObject::event(QEvent*) () at /lib64/libQt6Core.so.6
#21 0x7f80787baa65 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt6Widgets.so.6
#22 0x7f8077368068 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt6Core.so.6
#23 0x7f807736f170 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt6Core.so.6
#24 0x7f8077623957 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt6Core.so.6
#25 0x7f806b6a2c7f in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#26 0x7f806b6f9118 in g_main_context_iterate.constprop () at
/lib64/libglib-2.0.so.0
#27 0x7f806b69ff00 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#28 0x7f8077623220 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt6Core.so.6
#29 0x7f807737465b in
QEventLoop::exec(QFlags) () at
/lib64/libQt6Core.so.6
#30 0x7f8077370528 in QCoreApplication::exec() () at /lib64/libQt6Core.so.6
#31 0x0040f842 in Akonadi::AgentBase::init(int,
char**) (argc=, argv=0x7e699948) at
/home/nico/kde6/usr/include/KPim6/AkonadiAgentBase/akonadi/agentbase.h:469
#32 0x7f8076c4a510 in __libc_start_call_main () at /lib64/libc.so.6
#33 0x7f8076c4a5c9 in __libc_start_main_impl () at /lib64/libc.so.6
#34 0x0040eba5 in _start ()
[Inferior 1 (process 2847) detached]
[plasmashell] [Bug 465979] Opened windows and applications are click-through sometimes on the bottom of Task Manager
https://bugs.kde.org/show_bug.cgi?id=465979 freeze_ball changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #4 from freeze_ball --- Can confirm that 5.27.2 fixed it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466749] New: Glitching cursor and browser content when Firefox is in full screen using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=466749 Bug ID: 466749 Summary: Glitching cursor and browser content when Firefox is in full screen using a fractional scaling factor Classification: Plasma Product: kwin Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: apri...@posteo.net Target Milestone: --- SUMMARY Visual glitches in Firefox STEPS TO REPRODUCE 1. Using KDE Plasma (Wayland) set your monitor scaling factor to a fractional value like 150%, 195%, etc. 100% and 200% do not have this problem. 2. Open Firefox in Wayland mode with "MOZ_ENABLE_WAYLAND=1 firefox" and check if it is actually running in Wayland mode using "qdbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole" in the terminal. 3. Open a YouTube video in full screen an let it play. 4. Move the mouse cursor slowly. OBSERVED RESULT When moving the mouse cursor depending on which scaling value is chosen exactly and the monitor resolution one or both glitches occur: 1) The mouse cursor flickers, jumps or changes in size (from it's 100% scale size to f.e. 150% and back and forth) 2) The whole window jitters left and right by a few pixels. Maybe this is related to https://bugs.kde.org/show_bug.cgi?id=459373 where full screen applications leave pixel gaps. EXPECTED RESULT When moving the mouse cursor it should stay consistently in size and the browser content should not wiggle. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2.1-arch1-1 (64-bit) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358240] KeePass2 system tray icon is shown as white square
https://bugs.kde.org/show_bug.cgi?id=358240 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466748] New: with laptop set to only turn off screen when lid is closed, opening laptop lid does not enable display
https://bugs.kde.org/show_bug.cgi?id=466748 Bug ID: 466748 Summary: with laptop set to only turn off screen when lid is closed, opening laptop lid does not enable display Classification: Plasma Product: Powerdevil Version: 5.27.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: erben...@comcast.net CC: m...@ratijas.tk Target Milestone: --- SUMMARY *** I have my laptop set to ONLY turn off the screen when the lid is closed, no hibernate, sleep, logout etc is enabled When i close the lid the screen shuts off as expected and everything stays running as expected and desired When i open the lid the display does not turn on until i press a key, it should turn on as soon as the lid is opened *** STEPS TO REPRODUCE 1. In system settings, select power management and under "Button handling events" select to "Turn of Screen" when lid is closed, make sure there is no hibernate, sleep etc selected anywhere on the page, click apply and close system settings 2. close laptop lid, the screen will go black as expected and desired 3. open the lid and the screen stays turned off until you press a key or move the mouse OBSERVED RESULT the screen stays turned off until you press a key or move the mouse EXPECTED RESULT The screen should re-enable and return to normal state SOFTWARE/OS VERSIONS KDE 5.103.0 Plasma 5.27.1 Qt: 5.15.8 Kernel: 6.1.12-1-default x86_64 Xorg 21.1.7 (I am not using wayland) Not using an external display OS: openSUSE Tumbleweed 2023-02-25 Manufacturer: ASUSTeK COMPUTER INC. Product Name: ZenBook UX535LI_UX535LI lshw shows: *-input:1 product: Lid Switch physical id: 2 logical name: input1 logical name: /dev/input/event1 capabilities: platform ADDITIONAL INFORMATION I have no idea what module is involved hence the selection of powerdevil, please change that if appropriate How can i provide more info? I remember there is a program that dumps out kde state and info but the name eludes me. -- 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 #3 from Nate Graham --- Git commit 3e7c711a5a3320c74bb27a01faf9525b0bd73e76 by Nate Graham. Committed on 02/03/2023 at 22:40. Pushed by ngraham into branch 'master'. Improve translation context for short "Update [thing]" strings The original English text of "Update Selected" in particular is inherently grammatically ambiguous and can be interpreted in various ways (e.g. as "An update is selected", rather than "Update the selected things") without adequate context. M +1-1discover/qml/UpdatesPage.qml https://invent.kde.org/plasma/discover/commit/3e7c711a5a3320c74bb27a01faf9525b0bd73e76 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466689] System Settings Crash After Applying Global Theme
https://bugs.kde.org/show_bug.cgi?id=466689 --- Comment #3 from Nate Graham --- See https://community.kde.org/Qt5PatchCollection which should have some info in there about it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466690] On top panel some types of app windows react wrong on restore from maximize
https://bugs.kde.org/show_bug.cgi?id=466690 --- Comment #2 from Szymon --- Problem is declared on thread title, some applications don't restore thier sizes after maximize when panel bar is on top of screen. All electron apps and Qt6 apps won't work at all, and some older gtk applications to. Original size that windows are overwritten after first attempt to unmaximize. Idk how to explain simpler to understand , my english is pretty bad. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466747] Wayland: Invert effect causes certain UI elements to stutter
https://bugs.kde.org/show_bug.cgi?id=466747 Naxdy changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466747] New: Wayland: Invert effect causes certain UI elements to stutter
https://bugs.kde.org/show_bug.cgi?id=466747 Bug ID: 466747 Summary: Wayland: Invert effect causes certain UI elements to stutter Classification: Plasma Product: kwin Version: 5.27.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: xna...@hydra-development.net Target Milestone: --- SUMMARY While inverted, certain UI elements seem to not update correctly, most notably the hamburger menu in Firefox. As far as I can tell, this bug is new to 5.27.0. >From what I've tested, only Firefox and Thunderbird are affected by this, but I can only *reliably* reproduce this bug in Firefox. STEPS TO REPRODUCE 0. Log in to Plasma Wayland 1. Open Firefox 2. Enable Invert effect 3. Open Firefox' hamburger menu (ensure the currently opened webpage is NOT actively rendering content, e.g. videos, animations) 4. Interact with the menu. OBSERVED RESULT When hovered, menu entries either don't highlight at all, or highlight after a delay. When clicked, menu is slow to update. When dismissed, menu sometimes leaves behind an artifact on the webpage (disappears once the page renders something, or the user scrolls). EXPECTED RESULT Menu responds normally, as it would without the Invert effect applied. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466689] System Settings Crash After Applying Global Theme
https://bugs.kde.org/show_bug.cgi?id=466689 --- Comment #2 from Michael Mikowski --- Thank you Nate! > I recommend upgrading to 5.15.8 + the KDE patches. Agreed. Please point me to a document on how to do this if you know one exists. I looked around for a few minutes, and didn't easily find anything. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466475] Welcome Center doesn't write "ShouldShow=false" into config file when closed by a method other than the "Skip" and "finish" buttons
https://bugs.kde.org/show_bug.cgi?id=466475 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #10 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-welcome/-/merge_requests/68 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 466309] As of Kirigami 5.103, under certain circumstances, headers don't show the correct background color when using a Header-color-using color scheme
https://bugs.kde.org/show_bug.cgi?id=466309 robloka...@gmail.com changed: What|Removed |Added CC||robloka...@gmail.com --- Comment #10 from robloka...@gmail.com --- I'm experiencing the same issue on Plasma 5.27.2 and Frameworks 5.103, with both Breeze Light and Breeze Dark. The only color-related option I remember changing is the accent color. I also remember playing around with some color options in a copy of the Breeze Light color scheme, but I don't know why that would affect the actual Breeze Light and Dark themes. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465502] Flatpak KCM generates broken override config
https://bugs.kde.org/show_bug.cgi?id=465502 --- Comment #5 from ratijas --- Git commit 7e45e4931ea1a84000255c54ae62bf2d2b8bc2d2 by ivan tkachenko. Committed on 02/03/2023 at 22:17. Pushed by ratijas into branch 'Plasma/5.27'. FlatpakPermission: Disable loading environment from user overrides as well (cherry picked from commit ce407199aae085210107e57fef0fd8ed7b0b63bc) M +6-3flatpakpermission.cpp https://invent.kde.org/plasma/flatpak-kcm/commit/7e45e4931ea1a84000255c54ae62bf2d2b8bc2d2 -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466475] Welcome Center doesn't write "ShouldShow=false" into config file when closed by a method other than the "Skip" and "finish" buttons
https://bugs.kde.org/show_bug.cgi?id=466475 --- Comment #9 from Nate Graham --- I see the problem. We do handle it, but we only write the config key relevant for the Plasma 6 version of the app, not also the Plasma 5.27 version of it as well. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466475] Welcome Center doesn't write "ShouldShow=false" into config file when closed by a method other than the "Skip" and "finish" buttons
https://bugs.kde.org/show_bug.cgi?id=466475 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #8 from Nate Graham --- Can confirm. in 5.27 we don't handle external quit events. I could have sworn we did. Will fix. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465502] Flatpak KCM generates broken override config
https://bugs.kde.org/show_bug.cgi?id=465502 --- Comment #4 from ratijas --- Git commit ce407199aae085210107e57fef0fd8ed7b0b63bc by ivan tkachenko. Committed on 02/03/2023 at 22:10. Pushed by ratijas into branch 'master'. FlatpakPermission: Disable loading environment from user overrides as well M +6-3flatpakpermission.cpp https://invent.kde.org/plasma/flatpak-kcm/commit/ce407199aae085210107e57fef0fd8ed7b0b63bc -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466746] New: Error when opening chm files with Okular
https://bugs.kde.org/show_bug.cgi?id=466746 Bug ID: 466746 Summary: Error when opening chm files with Okular Classification: Applications Product: okular Version: 22.12.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: CHM backend Assignee: okular-de...@kde.org Reporter: viktor_hor...@hotmail.com Target Milestone: --- Created attachment 156936 --> https://bugs.kde.org/attachment.cgi?id=156936=edit Picture of the error message and the chm file that causes error SUMMARY *** 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. Open the chm file that causes error when opening with Okular 2. You will probably get an error message like "The file or the folder ms-its:PathToTheFile.chm:: doesn't exist" 3. When you click ok it will continue popping up the same error message when you scroll down OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Windows 11/22H2 (22621.1265) macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 466694] KOSRelease::logo() doesn't check if distro logo has been upgraded
https://bugs.kde.org/show_bug.cgi?id=466694 Harald Sitter changed: What|Removed |Added Assignee|mp...@kde.org |cf...@kde.org Product|frameworks-kcoreaddons |frameworks-kiconthemes Component|general |general --- Comment #5 from Harald Sitter --- That's an icon caching problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 185311] Option to auto erase content
https://bugs.kde.org/show_bug.cgi?id=185311 --- Comment #4 from Mike --- I would like to see this request revisited. With the popularity of password managers and the increasing use of pseudorandom strings as identifiers for things like crypto wallets, the clipboard is increasingly used to hold highly sensitive information. This has also been a lure for malicious actors. And while the overwhelming majority, of those malicious actors target Windows users, I would prefer we not become victims of our own hubris :) Currently I manage this with a script that runs from .config/autostart and checks org.kde.klipper.klipper.getClipboardContents once per minute. Then, when extant data in the clipboard is unchanged for >10 minutes, it runs clearClipboardHistory. A more perfect (for me) solution would watch for clipboard activity (copy AND paste), then clear the contents if there is no activity for x seconds. Seeing a check box for "Automatically clear clipboard history when inactive?" and a box to specify how many seconds after the last copy/paste action to wait near 'Clipboard history' in the Klipper configuration applet seems to make perfect sense. :) (In reply to Mike from comment #3) > Created attachment 156935 [details] > script to clear kde/klipper clipboard after n seconds of last 'copy' action -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 185311] Option to auto erase content
https://bugs.kde.org/show_bug.cgi?id=185311 Mike changed: What|Removed |Added CC||mike.p...@gmail.com --- Comment #3 from Mike --- Created attachment 156935 --> https://bugs.kde.org/attachment.cgi?id=156935=edit script to clear kde/klipper clipboard after n seconds of last 'copy' action -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466730] System Setting Crash when Multi-Monitor Docking Station plugged in.
https://bugs.kde.org/show_bug.cgi?id=466730 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #2 from Nate Graham --- I'm afraid Plasma 5.25 is unfortunately no longer eligible for support or maintenance. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. Please update to Plasma 5.27 as soon as your distro offers it to you. If you need support for Plasma 5.25, please contact your distro, who bears the responsibility of providing support for older non-LTS releases. If you can reproduce the issue after upgrading to Plasma 5.27, feel free to re-open this bug report. Thanks for understanding! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 466694] KOSRelease::logo() doesn't check if distro logo has been upgraded
https://bugs.kde.org/show_bug.cgi?id=466694 Alberto Salvia Novella changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #4 from Alberto Salvia Novella --- 1. Read which logo is used at "/etc/os-release". 2. Figure out where's that logo file, either in (/usr/share/pixmaps) or (/usr/share/icons). 2. Change the logo file, preserving the name. You can use the command "sudo cp". 3. Go to [System Settings -> About this system]. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466580] [NVIDIA] Panel freezes when rearranging or unpinning on icons only task manager widget
https://bugs.kde.org/show_bug.cgi?id=466580 --- Comment #2 from Derek --- Recent updates over last 2 days may have resolved the problem. I haven't noticed any freezing when rearranging or unpinning yet. Will keep using and seeing if any particular scenario triggers it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466745] Android over USB in dolphin have missing functionality .
https://bugs.kde.org/show_bug.cgi?id=466745 mrwan changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |alansari...@hotmail.com --- Comment #1 from mrwan --- Created attachment 156934 --> https://bugs.kde.org/attachment.cgi?id=156934=edit the missing functionality -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466745] Android over USB in dolphin have missing functionality .
https://bugs.kde.org/show_bug.cgi?id=466745 mrwan changed: What|Removed |Added Platform|Other |Archlinux CC||alansari...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466745] New: Android over USB in dolphin have missing functionality .
https://bugs.kde.org/show_bug.cgi?id=466745 Bug ID: 466745 Summary: Android over USB in dolphin have missing functionality . Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: alansari...@hotmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** 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. conncet the android phone via usb cable. 2. allow the pc mtp access from android. OBSERVED RESULT the cut and rename functions do not work ? EXPECTED RESULT all permissions should be granted by default . SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466702] Discover crashes in PackageKitBackend::resolvePackages() at start after failed offline-update
https://bugs.kde.org/show_bug.cgi?id=466702 Nate Graham changed: What|Removed |Added Component|discover|PackageKit CC||n...@kde.org Summary|Discover crashes at start |Discover crashes in |after failed offline-update |PackageKitBackend::resolveP ||ackages() at start after ||failed offline-update -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466721] Touchscreen does not work when using kwin_wayland as compositorcommand on SDDM
https://bugs.kde.org/show_bug.cgi?id=466721 Nate Graham changed: What|Removed |Added CC||n...@kde.org Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466686] [NVIDIA] On Wayland, screen goes black after changing resolution and doesn't come back
https://bugs.kde.org/show_bug.cgi?id=466686 Nate Graham changed: What|Removed |Added CC||xaver.h...@gmail.com Status|NEEDSINFO |REPORTED Summary|In Wayland screen goes |[NVIDIA] On Wayland, screen |blank after changing|goes black after changing |resolution and doesn't come |resolution and doesn't come |back|back Resolution|WAITINGFORINFO |--- --- Comment #3 from Nate Graham --- Thanks for the info. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466686] In Wayland screen goes blank after changing resolution and doesn't come back
https://bugs.kde.org/show_bug.cgi?id=466686 --- Comment #2 from kevin --- (In reply to Nate Graham from comment #1) > If you wait 16 seconds, does it revert to its former settings and bring back > the image? I've waited as long as 10 min and the image didn't come back. Which screen? All screens? How many screens do you have? Only one screen. >What GPU hardware are you using? Output of inxi -SG System: Host: localhost.localdomain Kernel: 6.2.0-1-default arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.27.1 Distro: openSUSE Tumbleweed 20230301 Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 530.30.02 Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch resolution: 3840x2160~60Hz API: OpenGL v: 4.6.0 NVIDIA 530.30.02 renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Does it happen on X11 too? No -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466708] Alt+shift does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=466708 Nate Graham changed: What|Removed |Added Component|general |wayland-generic CC||n...@kde.org --- Comment #1 from Nate Graham --- Works for me. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453071] 22.04.0: test suite is failing
https://bugs.kde.org/show_bug.cgi?id=453071 Waqar Ahmed changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME CC||waqar@gmail.com --- Comment #2 from Waqar Ahmed --- These tests now pass… -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434615] On Wayland, quick tile actions and window rules cannot override window's minimum size if needed as on X11
https://bugs.kde.org/show_bug.cgi?id=434615 Nate Graham changed: What|Removed |Added CC||amanita+kdeb...@mailbox.org --- Comment #9 from Nate Graham --- *** Bug 466717 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466717] Tiling window to right half makes it exceed that half
https://bugs.kde.org/show_bug.cgi?id=466717 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 434615 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 Oleg changed: What|Removed |Added CC||o...@np880.ru --- Comment #2 from Oleg --- Can confirm OpenGL and Vulkan applications won't start with 110% scaling, but start just fine with 125% scaling. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfigwidgets] [Bug 466743] Crash when using KCommandBar
https://bugs.kde.org/show_bug.cgi?id=466743 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462673] Clipboard does not include items copied via copy/paste (CTRL+C or right click+copy) until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=462673 Oleg changed: What|Removed |Added CC||o...@np880.ru --- Comment #28 from Oleg --- Can confirm. In Firefox wayland version if I copy URL from address bar I can't paste it anywhere else than Firefox itself. For some reason it only happens to URLs from address bar, any other text from Firefox copies just fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466740] wayland: 2 monitor setup with 175%/100% scaling: enable preview in dolphin (F11) destroys dolphin window contents
https://bugs.kde.org/show_bug.cgi?id=466740 slartibar...@gmail.com changed: What|Removed |Added Depends on||466744 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=466744 [Bug 466744] wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466741] wayland: 2 monitor setup with 175%/100% scaling: mouse scroll-wheel creates a jumping motion when operated slowly
https://bugs.kde.org/show_bug.cgi?id=466741 slartibar...@gmail.com changed: What|Removed |Added Depends on||466744 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=466744 [Bug 466744] wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466739] wayland: 2 monitor setup with 175%/100% scaling: gwenview home/browse view not rendered correctly after viewing an image
https://bugs.kde.org/show_bug.cgi?id=466739 slartibar...@gmail.com changed: What|Removed |Added Depends on||466744 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=466744 [Bug 466744] wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466736] wayland: 2 monitor setup with 175%/100% scaling: cannot reposition screen-miniatures in display config
https://bugs.kde.org/show_bug.cgi?id=466736 slartibar...@gmail.com changed: What|Removed |Added Depends on||466744 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=466744 [Bug 466744] wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466738] wayland: 2 monitor setup with 175%/100% scaling: gwenview scales images having the same pixel size as the screen
https://bugs.kde.org/show_bug.cgi?id=466738 slartibar...@gmail.com changed: What|Removed |Added Depends on||466744 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=466744 [Bug 466744] wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466683] wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems
https://bugs.kde.org/show_bug.cgi?id=466683 slartibar...@gmail.com changed: What|Removed |Added Blocks||466744 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=466744 [Bug 466744] wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466744] New: wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems
https://bugs.kde.org/show_bug.cgi?id=466744 Bug ID: 466744 Summary: wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: slartibar...@gmail.com CC: k...@davidedmundson.co.uk, n...@kde.org, plasma-b...@kde.org Depends on: 466683 Blocks: 466736, 466738, 466739, 466740, 466741 Target Milestone: 1.0 +++ This bug was initially created as a clone of Bug #466683 +++ Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 31,1 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 Setup: Laptop with 2K Laptop screen and a fullhd screen (1920x1080) connected by displayPort Use fullHD monitor as 'primary' and perform all tests on the fullHD monitor (ignore laptop screen) Go to systemsettings > display config and set 175% scale for 2K laptop screen, 100% for fullhd screen. This makes apps/windows on both monitors the same visual size. Problem: The font renderings on the fullhd monitor are not as clear/smooth as compared to normal (100/100% scale). - This affects the font-rendering which appears pixelated - The kerning/hinting of letters is also bad (font hinting is set to 'slight', but it gets worse with medium or full) This is especially noticeable with small fonts like in thunderbird, a browser like chrome/firefox and typical webpage-fonts render smoothly. In my case, i am using Tahoma (ttf) with 8px size. As indicated above, switching to 100%/100% on both monitors solves the problem Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=466683 [Bug 466683] wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems https://bugs.kde.org/show_bug.cgi?id=466736 [Bug 466736] wayland: 2 monitor setup with 175%/100% scaling: cannot reposition screen-miniatures in display config https://bugs.kde.org/show_bug.cgi?id=466738 [Bug 466738] wayland: 2 monitor setup with 175%/100% scaling: gwenview scales images having the same pixel size as the screen https://bugs.kde.org/show_bug.cgi?id=466739 [Bug 466739] wayland: 2 monitor setup with 175%/100% scaling: gwenview home/browse view not rendered correctly after viewing an image https://bugs.kde.org/show_bug.cgi?id=466740 [Bug 466740] wayland: 2 monitor setup with 175%/100% scaling: enable preview in dolphin (F11) destroys dolphin window contents https://bugs.kde.org/show_bug.cgi?id=466741 [Bug 466741] wayland: 2 monitor setup with 175%/100% scaling: mouse scroll-wheel creates a jumping motion when operated slowly -- You are receiving this mail because: You are watching all bug changes.
