[Merkuro] [Bug 474938] Qt6: Calendar fails to start
https://bugs.kde.org/show_bug.cgi?id=474938 --- Comment #2 from Martin Flöser --- 71 min from report to fix - I am deeply impressed! -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 474938] New: Qt6: Calendar fails to start
https://bugs.kde.org/show_bug.cgi?id=474938 Bug ID: 474938 Summary: Qt6: Calendar fails to start Classification: Applications Product: Merkuro Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: mgraess...@kde.org CC: c...@carlschwan.eu Target Milestone: --- Package provided by KDE Neon Unstable edition (Package version: 23.08.1+p22.04+vunstable+git20230926.1408-0) fails to launch merkuro-calendar: QQmlApplicationEngine failed to load component qrc:/main.qml:549:5: Type IncidenceEditorPage unavailable qrc:/IncidenceEditorPage.qml:828:35: Type Kirigami.CheckableListItem unavailable file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/CheckableListItem.qml:53:5: Non-existent attached object SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Unstable edition (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453558] Floating (detached) Qt toolbar can't be dragged nor re-attached to window
https://bugs.kde.org/show_bug.cgi?id=453558 Martin Flöser changed: What|Removed |Added Component|client |wayland-generic Product|frameworks-kwayland |kwin Version|5.93.0 |unspecified Assignee|mgraess...@kde.org |kwin-bugs-n...@kde.org --- Comment #3 from Martin Flöser --- I fear that this is a bug in Qt and that we in KWin cannot do anything about it. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] After waking the system, the desktop gets displayed for a moment before the lock screen appears
https://bugs.kde.org/show_bug.cgi?id=316734 --- Comment #61 from Martin Flöser --- (In reply to Shmerl from comment #60) > I haven't tested it with X11, but is the code shared for it too? It's in > wayland_server.cpp, so I assumed it only fixes the Wayland use case. The patch is Wayland only! This change does not have any influence on X11. I am not sure whether we have any chance to fix this for good on X11. Concerning Wayland I am also not yet convinced that we should consider it as fixed. The patch only addresses point 2a which means we can still enter racy conditions especially on multiple output setups. We still do not wait for the page flip of every output. Though it is very unlikely to hit and on resume the time an old buffer would be shown is shorter. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] After waking the system, the desktop gets displayed for a moment before the lock screen appears
https://bugs.kde.org/show_bug.cgi?id=316734 --- Comment #48 from Martin Flöser --- (In reply to Nate Graham from comment #47) > Cannot reproduce in the Plasma Wayland session with current git master, FWIW. Just experienced the issue on wakeup with relatively recent git master (2024). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336369] Lock screen: power actions (sleep, shut down, restart) are missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #47 from Martin Flöser --- (In reply to Krystof Jelinek from comment #45) > I am pretty confident that quite a lot of people still hold it, and again I > ask: how does it improve security? As a father of a 3 year old child I can tell you that I am very happy that the lock screen does not provide any destructive actions! It means I can lock the screen and don't have to care what will happen to the system. Editing an important document and tiny hands want to write things: lock the screen. Even the suspend option would be rather destructive as it means downloads, etc. might get cancelled by tiny hands. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.
https://bugs.kde.org/show_bug.cgi?id=316734 --- Comment #46 from Martin Flöser --- Based on comment #43 I read through the relevant code pieces for Wayland. On Wayland we ensure that when the screen is locked only the lock screen window or input method window should be visible (see https://invent.kde.org/plasma/kwin/-/blob/v5.22.4/src/composite.cpp#L608 ). As stated in comment #43 this seems to not work correctly. By investigating I found two smallish issues which might cause it: 1. There seems to be no full repaint triggered when the screenlocker reports to get locked. In the handler for the aboutToLock signal (see https://invent.kde.org/plasma/kwin/-/blob/v5.22.4/src/wayland_server.cpp#L604 ) a full repaint needs to be triggered. This would ensure that KWin stops rendering all windows before the lock screen gets shown. Thus the screen should turn black. (Please note that the code in Kscreenlocker needs to be adjusted as the emit happens before the lock state is changed to AcquiringLock. Maybe a dedicated signal is needed, see https://invent.kde.org/plasma/kscreenlocker/-/blob/v5.22.4/ksldapp.cpp#L380). 2. KWin reports the screen as fully locked once the window for the lock screen is registered (see https://invent.kde.org/plasma/kwin/-/blob/v5.22.4/src/wayland_server.cpp#L245 ). At that time it is not yet rendered, not yet even damaged. It is only created. The screenlocker immediately removes the inhibition and the system suspends (see https://invent.kde.org/plasma/kscreenlocker/-/blob/v5.22.4/ksldapp.cpp#L720 and https://invent.kde.org/plasma/kscreenlocker/-/blob/v5.22.4/ksldapp.cpp#L301 ). This needs to be changed to wait for a) surface fully damaged b) composition pass finished c) screen presented (e.g. drm frame callback) In combination these two issues can create a race condition where the screen stays in the content of the unlocked state. Still it is likely for many systems to not hit the issue. E.g. anything triggering a repaint between aboutToLock and Wayland window created will ensure the screen to go black. This can e.g. happen when clicking a button to suspend (the button release of the mouse will do) or when closing a notebook lid by triggering the common fake touchpad moves in these cases. This especially explains the pinephone case where the system is probably not put to lock through a pointer/touch event. The second issue explains why the problem came back. The code was written against the wl_shell interface and got migrated over the years to xdg_shell which is a more complex interface and needs more time to setup thus the too early removed inhibition is more likely to cause issues. Of course this is only for Wayland. For X11 we need other solutions which might be possible to reuse ideas from Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.
https://bugs.kde.org/show_bug.cgi?id=316734 --- Comment #42 from Martin Flöser --- Can those affected by the problem please check dmesg after a suspend cycle for messages related to drm? Personally I haven't experienced this problem for years (!) any more and given the past I fear that this is a driver issue. Which can make it difficult to investigate. We might need much more information from everyone experiencing this issue. It is possible that this is a driver/distro specific problem. Thus I would like anybody experiencing the problem as first step try whether the issue also persist on a Wayland session. This is extremely important to know whether the problem is only X11 specific or also on Wayland and thus in general. Then further I would like every affected user to report: * Distribution and version * Mesa version * Hardware (which CPU and GPU) This should hopefully give us some more information to understand who is affected and why. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439137] GTK4 child windows/dialogs positioned incorrectly on KWin X11
https://bugs.kde.org/show_bug.cgi?id=439137 --- Comment #11 from Martin Flöser --- Good! That explains the behavior. The placement is done in the manage method, thus once we know it's a transient, it's too late. I think this should go back to GTK devs to look into ensuring that the property only gets update in withdrawn state. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439137] GTK4 child windows/dialogs positioned incorrectly on KWin X11
https://bugs.kde.org/show_bug.cgi?id=439137 --- Comment #9 from Martin Flöser --- (In reply to nyanpasu64 from comment #8) > On the technical side of things, how would I "monitor the property states > once the window gets mapped and then monitor for changes of the property"? > Should I insert debug statements into kwin? Or try reading kwin or GTK4 > myself? Yes adding debug statements in KWin is the way I would go. It might be possible to also use KWin scripts, though I am not completely sure whether that is exposed (especially if KWin does not handle transient_for changes the change signal is probably missing). > > On the social side of things, should I ping the GTK bug and ask them to > reevaluate GTK4's code? Should I mention my hypothesis or your message? I would wait till we have more information. If the hypothesis is correct then we should ask GTK to reevaluate the code. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439137] GTK4 child windows/dialogs positioned incorrectly on KWin X11
https://bugs.kde.org/show_bug.cgi?id=439137 --- Comment #7 from Martin Flöser --- >From the description it sounds that window gets mapped without the WM_TRANSIENT_FOR property and KWin and likewise XFWM does not support changing the state of that property. I just checked ICCCM and could not find anything regarding whether it is allowed or disallowed to change that property once the window is mapped. In my opinion it doesn't make sense to change it once it is mapped. At least I cannot imagine how a window manager should handle this property change once the window is mapped. If you are able to monitor the property states once the window gets mapped and then monitor for changes of the property we know more. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 437742] New: maliit-keyboard has broken dependencies
https://bugs.kde.org/show_bug.cgi?id=437742 Bug ID: 437742 Summary: maliit-keyboard has broken dependencies Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: mgraess...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- maliit-framework was updated to depend on libmaliit-plugins2, but maliit-keyboard still depends on libmaliit-plugins0, while at the same time depends on maliit-framework. This obviously results in a conflict. Available package versions: * libmaliit-plugins0/focal 0.99.1+git20151118+62bd54b-0ubuntu26 * libmaliit-plugins2/focal,now 0.99.1+p20.04+tunstable+git20210512.1403-0 * maliit-framework/focal,now 0.99.1+p20.04+tunstable+git20210512.1403-0 * maliit-keyboard/focal 0.99.1+p20.04+tunstable+git20210424.0135-0 -- sudo apt install maliit-keyboard Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) libmaliit-plugins2:amd64 < 0.99.1+p20.04+tunstable+git20210512.1403-0 @ii mK Ib > Broken libmaliit-plugins2:amd64 Beschädigt on libmaliit-plugins0:amd64 < none -> 0.99.1+git20151118+62bd54b-0ubuntu26 @un uN > (< 0.99.1+p20.04+tunstable+git20210512.1403-0~ciBuild) Considering libmaliit-plugins0:amd64 -2 as a solution to libmaliit-plugins2:amd64 0 Added libmaliit-plugins0:amd64 to the remove list Fixing libmaliit-plugins2:amd64 via keep of libmaliit-plugins0:amd64 Investigating (1) maliit-keyboard:amd64 < none -> 0.99.1+p20.04+tunstable+git20210424.0135-0 @un puN Ib > Broken maliit-keyboard:amd64 Hängt ab von on libmaliit-plugins0:amd64 < none | 0.99.1+git20151118+62bd54b-0ubuntu26 @un uH > Considering libmaliit-plugins0:amd64 -2 as a solution to maliit-keyboard:amd64 9998 Re-Instated libmaliit-plugins0:amd64 Investigating (1) libmaliit-plugins2:amd64 < 0.99.1+p20.04+tunstable+git20210512.1403-0 @ii mK Ib > Broken libmaliit-plugins2:amd64 Beschädigt on libmaliit-plugins0:amd64 < none -> 0.99.1+git20151118+62bd54b-0ubuntu26 @un uN > (< 0.99.1+p20.04+tunstable+git20210512.1403-0~ciBuild) Considering libmaliit-plugins0:amd64 -2 as a solution to libmaliit-plugins2:amd64 0 Added libmaliit-plugins0:amd64 to the remove list Fixing libmaliit-plugins2:amd64 via keep of libmaliit-plugins0:amd64 Investigating (2) maliit-keyboard:amd64 < none -> 0.99.1+p20.04+tunstable+git20210424.0135-0 @un puN Ib > Broken maliit-keyboard:amd64 Hängt ab von on libmaliit-plugins0:amd64 < none | 0.99.1+git20151118+62bd54b-0ubuntu26 @un uH > Considering libmaliit-plugins0:amd64 -2 as a solution to maliit-keyboard:amd64 9998 Done Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass Sie eine unmögliche Situation angefordert haben oder, wenn Sie die Unstable-Distribution verwenden, dass einige erforderliche Pakete noch nicht erstellt wurden oder Incoming noch nicht verlassen haben. Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen: Die folgenden Pakete haben unerfüllte Abhängigkeiten: maliit-keyboard : Hängt ab von: libmaliit-plugins0 soll aber nicht installiert werden E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435467] KWIN_DRM_DEVICE no longer supported
https://bugs.kde.org/show_bug.cgi?id=435467 --- Comment #2 from Martin Flöser --- (In reply to Vlad Zahorodnii from comment #1) > Would it be sufficient if we introduce an environment variable with a > slightly different name, KWIN_DRM_DEVICES? sure -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435468] New: XDG_SESSION_ID no longer honored by KWin
https://bugs.kde.org/show_bug.cgi?id=435468 Bug ID: 435468 Summary: XDG_SESSION_ID no longer honored by KWin Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: mgraess...@kde.org Target Milestone: --- SUMMARY KWin used to support XDG_SESSION_ID to specify the session to start on. Since https://invent.kde.org/plasma/kwin/-/commit/ade861d6de185cff9e49ec08dd95704f338eff4f this is no longer supported. This is a very useful way to launch KWin through ssh in gdb or through ssh on embedded hardware during the development face. Please see also my older blog post introducing this: https://blog.martin-graesslin.com/blog/2016/04/starting-kwinwayland-on-another-virtual-terminal/ STEPS TO REPRODUCE 1. Use weird vivante hardware which crashes KWin on startup 2. Set XDG_SESSION_ID to a started session 3. Launch KWin through gdb in ssh OBSERVED RESULT KWin doesn't start. EXPECTED RESULT KWin starts on the specified logind session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435467] New: KWIN_DRM_DEVICE no longer supported
https://bugs.kde.org/show_bug.cgi?id=435467 Bug ID: 435467 Summary: KWIN_DRM_DEVICE no longer supported Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: mgraess...@kde.org Target Milestone: --- SUMMARY KWin used to support an environment variable to overwrite the selection of which drm device to use. This got lost in commit https://invent.kde.org/plasma/kwin/-/commit/b50f7478769c1b50b48d5f0e9201a8e4b7e275ef STEPS TO REPRODUCE 1. Use weird vivante hardware with a card0 and a card1 which doesn't support GL on /dev/dri/card0 2. specify KWIN_DRM_DEVICE to point to /dev/dri/card1 OBSERVED RESULT /dev/dri/card0 is used and KWin doesn't work EXPECTED RESULT /dev/dri/card1 is used and KWin works -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 434794] New: maliit-keyboard misses dependency to qml-module-qtquick-localstorag
https://bugs.kde.org/show_bug.cgi?id=434794 Bug ID: 434794 Summary: maliit-keyboard misses dependency to qml-module-qtquick-localstorag Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: mgraess...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY When switching maliit-keyboard to the emoji selection it fails and prints the following warning: file:///usr/lib/x86_64-linux-gnu/maliit/keyboard2/languages/emoji/Keyboard_emoji.qml:18:1: module "QtQuick.LocalStorage" is not installed STEPS TO REPRODUCE 1. Install maliit-keyboard in KDE Neon Unstable Edition 2. Try maliit-keyboard in Wayland session 3. Select the emoji layout OBSERVED RESULT UI breaks and cannot be switched back to normal layout EXPECTED RESULT maliit-keyboard package pulls in all required dependencies ADDITIONAL INFORMATION After manually installing the missing package, the keyboard is functional again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428195] System Tray triggers constant repaints on Wayland
https://bugs.kde.org/show_bug.cgi?id=428195 Martin Flöser changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #13 from Martin Flöser --- I didn't observe the problem lately. So I assume it was the invisible spinner, which would match my observation as I couldn't blame any individual item. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428195] System Tray triggers constant repaints on Wayland
https://bugs.kde.org/show_bug.cgi?id=428195 --- Comment #10 from Martin Flöser --- (In reply to Konrad Materka from comment #9) > (In reply to Martin Flöser from comment #3) > > yep, none is causing it. > Do I understand correctly, that even if you disable all applets and close > all applications (s) just empty System Tray), it still causes constant > repaints? I disabled one after another, checked whether it changed the state and then re-enabled it. So I never was in a state with empty System Tray. Currently (after a system restart) I am not able to reproduce. I'm monitoring the situation to notice when it happens again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428195] Panel triggers constant repaints
https://bugs.kde.org/show_bug.cgi?id=428195 --- Comment #4 from Martin Flöser --- Created attachment 132718 --> https://bugs.kde.org/attachment.cgi?id=132718=edit Wayland debug output Run with WAYLAND_DEBUG=1 - we can nicely see the constant repaints. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428195] Panel triggers constant repaints
https://bugs.kde.org/show_bug.cgi?id=428195 --- Comment #3 from Martin Flöser --- (In reply to David Edmundson from comment #2) > Does > > QSG_VISUALIZE=changes plasmashell --replace > > tell use anything? Nothing repaints... (In reply to Konrad Materka from comment #1) > Hi, if that is the System Tray, it might be one applet/application that is > causing repaints. Can you disable all applets (from System Tray settings) > and close all applications, then run one by one? yep, none is causing it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428195] New: Panel triggers constant repaints
https://bugs.kde.org/show_bug.cgi?id=428195 Bug ID: 428195 Summary: Panel triggers constant repaints Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: mgraess...@kde.org Target Milestone: 1.0 I observed very high cpu usage in kwin_wayland. Investigation with the show paint effect showed that KWin is constantly repainting the complete screen. By closing all application windows I could identify plasmashell as the offender (also high cpu usage but lower than kwin and confirmed by killing and restarting plasmashell). By making the panel auto-hide I could end the constant repaint, as soon as the panel is visible, one can observe the constant repaints again. I added an empty panel and added plasmoids untill the problem started and could identify SystemTray. STEPS TO REPRODUCE 1. Enable show paint effect 2. Make plasma panel autohide 3. hide/show panel OBSERVED RESULT the show paint effect shows constant repaint when enabled, which ends as soon as auto-hide gets enabled, restarts when shown. EXPECTED RESULT My notebook doesn't burn my legs :-) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Unstable Edition (available in About System) KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.75 Qt Version: 5.15.0 ADDITIONAL INFORMATION Obviously a Wayland system. When starting Plasma it takes a few seconds till the Problem emerges, the same is the case when adding system tray to a panel. If you have any question, please let me know. Items shown in systray: * Discover * keepassx * owncloud * telegram * yakuake * night-color * klipper * battery monitor * audio * network manager -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421131] Wayland: cursor lags under heavy CPU load
https://bugs.kde.org/show_bug.cgi?id=421131 --- Comment #8 from Martin Flöser --- cmake looks for optional build dependency Libcap. Verify that you have built KWin with that dependency. In case your KWin is built with libcap support do: sudo setcap CAP_SYS_NICE=+ep `which kwin_wayland` Unfortunatelly you will have to do this after every make/ninja install. In case you run make/ninja install as root, this should be done automatically. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421131] Wayland: cursor lags under heavy CPU load
https://bugs.kde.org/show_bug.cgi?id=421131 --- Comment #5 from Martin Flöser --- You could also check getcap /usr/bin/kwin_wayland it should print: /usr/bin/kwin_wayland = cap_sys_nice+ep -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421131] Wayland: cursor lags under heavy CPU load
https://bugs.kde.org/show_bug.cgi?id=421131 --- Comment #4 from Martin Flöser --- You can use ksysguard. Enable the process priority column and check whether kwin_wayland is marked as realtime or FIFO. I would like to give you a screenshot how it should look like, but on KDE neon it's defunct and my kwin_wayland does not use rt-priority. (if it shows a 0 it's wrong). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421131] Wayland: cursor lags under heavy CPU load
https://bugs.kde.org/show_bug.cgi?id=421131 --- Comment #2 from Martin Flöser --- Can you please check whether KWin is running with real-time scheduling? The whole idea of giving real-time scheduling was to prevent laggy situations on heavy system load. But not all distributions were able to deliver it (in case of openSUSE I remember that the security team had comments). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421131] Wayland: cursor lags under heavy CPU load
https://bugs.kde.org/show_bug.cgi?id=421131 Martin Flöser changed: What|Removed |Added CC||mgraess...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 423610] New: Krunner crashes once entering text
https://bugs.kde.org/show_bug.cgi?id=423610 Bug ID: 423610 Summary: Krunner crashes once entering text Product: krunner Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: mgraess...@kde.org CC: plasma-b...@kde.org Target Milestone: --- Application: krunner (5.19.80) Qt Version: 5.14.2 Frameworks Version: 5.72.0 Operating System: Linux 4.15.0-108-generic x86_64 Windowing system: Wayland Distribution: KDE neon Unstable Edition -- Information about the crash: - What I was doing when the application crashed: Launched KRunner, started typing. This started with the latest updates of neon unstable. Unfortunately it's fully reproducable. Using the search in application launcher widget does not crash. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault [KCrash Handler] #4 0x7f5f63de4ddc in Plasma::QueryMatch::urls() const (this=this@entry=0x560fa401a018) at ./src/querymatch.cpp:264 #5 0x7f5f63dd5fd8 in Plasma::AbstractRunner::mimeDataForMatch(Plasma::QueryMatch const&) (this=, match=...) at ./src/abstractrunner.cpp:226 #6 0x7f5f63df3563 in Plasma::RunnerManagerPrivate::loadInstalledRunner(KPluginMetaData const&) (this=this@entry=0x560fa43217a0, pluginMetaData=...) at ./src/runnermanager.cpp:399 #7 0x7f5f63df4f9b in Plasma::RunnerManagerPrivate::loadRunners() (this=0x560fa43217a0) at ./src/runnermanager.cpp:270 #8 0x7f5f63df162d in Plasma::RunnerManager::launchQuery(QString const&, QString const&) (this=0x560fa426deb0, untrimmedTerm=..., runnerName=...) at ./src/runnermanager.cpp:913 #9 0x7f5f63df17a7 in Plasma::RunnerManager::launchQuery(QString const&) (this=, term=...) at ./src/runnermanager.cpp:883 #10 0x7f5f6834896d in Milou::RunnerResultsModel::setQueryString(QString const&) (this=0x560fa43131d0, queryString=...) at ./lib/runnerresultsmodel.cpp:194 #11 0x7f5f6834532d in Milou::ResultsModel::setQueryString(QString const&) (this=, queryString=...) at ./lib/resultsmodel.cpp:370 #12 0x7f5f68352c6a in Milou::ResultsModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at ./obj-x86_64-linux-gnu/lib/milou_autogen/EWIEGA46WW/moc_resultsmodel.cpp:228 #13 0x7f5f87a00d1f in QQmlPropertyData::writeProperty(QObject*, void*, QFlags) const (flags=..., value=0x7ffd9cfbe6d8, target=, this=) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:286 #14 0x7f5f87a00d1f in GenericBinding<10>::doStore(QString, QQmlPropertyData const*, QFlags) const (flags=..., pd=, value=..., this=0x560fa4302c50) at qml/qqmlbinding.cpp:334 #15 0x7f5f87a00d1f in GenericBinding<10>::write(QV4::Value const&, bool, QFlags) (this=0x560fa4302c50, result=..., isUndefined=, flags=...) at qml/qqmlbinding.cpp:315 #16 0x7f5f87a0144a in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) (this=0x560fa4302c50, watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:250 #17 0x7f5f879fe032 in QQmlBinding::update(QFlags) (this=0x560fa4302c50, flags=...) at qml/qqmlbinding.cpp:186 #18 0x7f5f879d7322 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=a@entry=0x0) at qml/qqmlnotifier.cpp:104 #19 0x7f5f87985119 in QQmlData::signalEmitted(QAbstractDeclarativeData*, QObject*, int, void**) (object=0x560fa4268070, index=, a=0x0) at qml/qqmlengine.cpp:858 #20 0x7f5f84c3c314 in doActivate(QObject*, int, void**) (sender=0x560fa4268070, signal_index=32, argv=0x0) at kernel/qobject.cpp:3762 #21 0x7f5f87980851 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) (this=0x560fa43585f0, o=, c=, _id=, a=) at qml/qqmlvmemetaobject.cpp:782 #22 0x7f5f878c885d in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) (engine=engine@entry=0x560fa42842b0, object=object@entry=0x560fa4268070, property=0x7f5f5c205858, value=...) at jsruntime/qv4qobjectwrapper.cpp:542 #23 0x7f5f878c8b4e in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&) (engine=0x560fa42842b0, qmlContext=, object=0x560fa4268070, name=, revisionMode=QV4::QObjectWrapper::IgnoreRevision, value=...) at jsruntime/qv4qobjectwrapper.cpp:435 #24 0x7f5f878c8c9b in QV4::QObjectWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) (m=0x7f5f6a4ae560, id=..., value=..., receiver=0x7f5f6a4ae560) at jsruntime/qv4qobjectwrapper.cpp:721 #25 0x7f5f8788e8a9 in QV4::Object::put(QV4::PropertyKey, QV4::Value const&, QV4::Value*) (receiver=0x7f5f6a4ae560,
[kwin] [Bug 394772] Some GTK apps temporarily lose scroll focus while desktop notification are shown
https://bugs.kde.org/show_bug.cgi?id=394772 --- Comment #26 from Martin Flöser --- For unfocused windows a mouse grab is always installed. So that is probably the same issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394772] Some GTK apps temporarily lose scroll focus while desktop notification are shown
https://bugs.kde.org/show_bug.cgi?id=394772 --- Comment #24 from Martin Flöser --- KWin holds a passive mouse grab. This is established in events.cpp in method X11Client::updateMouseGrab (https://cgit.kde.org/kwin.git/tree/events.cpp#n861 ). I assume this is the relevant piece of code especially as it checks for the clickRaise option. This piece of code is still using the xcore input grabs. My hope would be that changing to xinput2 grabs this would fix it. I had thought about that in the past when Krita complained about alt+click breaking things. If we changed the grabs to only operate on the pointer devices the scroll wheel should no longer be affected neither wacom devices. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386114] KRunner/Yakuake on Wayland always appears under Kickoff-panel
https://bugs.kde.org/show_bug.cgi?id=386114 Martin Flöser changed: What|Removed |Added CC|mgraess...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 Martin Flöser changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #21 from Martin Flöser --- Screenshot of krdc to krfb on Wayland: https://share.kde.org/s/cAXwLerPZcmy92j Setting to fixed as packaging wise everything gets properly installed. Verified in my virtual machine. Unfortunately also in the VM pipewire did not autostart, but that's probably a topic for a different bug and maybe resolves itself once Neon updates to Ubuntu 20.04. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 --- Comment #20 from Martin Flöser --- Yeah pipewire should socket-activate, but it doesn't - at least on my system. I tried system restart already. That might be a local issue or a general issue in the upstream package. It's a new technology after all. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 --- Comment #17 from Martin Flöser --- I got it working: one just needs to start pipewire -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #16 from Martin Flöser ---
and on xdg-desktop-portal-kde side:
dp-kde-remotedesktop: CreateSession called with parameters:
xdp-kde-remotedesktop: handle:
"/org/freedesktop/portal/desktop/request/1_167/krfb1156724296"
xdp-kde-remotedesktop: session_handle:
"/org/freedesktop/portal/desktop/session/1_167/krfb287183258"
xdp-kde-remotedesktop: app_id: ""
xdp-kde-remotedesktop: options: QMap()
xdp-kde-remotedesktop: SelectDevices called with parameters:
xdp-kde-remotedesktop: handle:
"/org/freedesktop/portal/desktop/request/1_167/krfb435177637"
xdp-kde-remotedesktop: session_handle:
"/org/freedesktop/portal/desktop/session/1_167/krfb287183258"
xdp-kde-remotedesktop: app_id: ""
xdp-kde-remotedesktop: options: QMap(("types", QVariant(uint, 7)))
xdp-kde-screencast: SelectSource called with parameters:
xdp-kde-screencast: handle:
"/org/freedesktop/portal/desktop/request/1_167/krfb2905553260"
xdp-kde-screencast: session_handle:
"/org/freedesktop/portal/desktop/session/1_167/krfb287183258"
xdp-kde-screencast: app_id: ""
xdp-kde-screencast: options: QMap(("multiple", QVariant(bool, false)))
xdp-kde-remotedesktop: Start called with parameters:
xdp-kde-remotedesktop: handle:
"/org/freedesktop/portal/desktop/request/1_167/krfb649013723"
xdp-kde-remotedesktop: session_handle:
"/org/freedesktop/portal/desktop/session/1_167/krfb287183258"
xdp-kde-remotedesktop: app_id: ""
xdp-kde-remotedesktop: parent_window: ""
xdp-kde-remotedesktop: options: QMap()
[New Thread 0x7fffd88cd700 (LWP 31160)]
[New Thread 0x7fffc6087700 (LWP 31161)]
xdp-kde-screencast-stream: Remote state: connecting
xdp-kde-screencast-stream: Remote error: connect failed No such file or
directory
[New Thread 0x7fffc545a700 (LWP 31162)]
xdp-kde-screencast-stream: Remote state: unconnected
[Thread 0x7fffc545a700 (LWP 31162) exited]
[Thread 0x7fffc6087700 (LWP 31161) exited]
xdp-kde-session: "org.freedesktop.impl.portal.Session"
xdp-kde-session: "Close"
xdp-kde-session: "/org/freedesktop/portal/desktop/session/1_167/krfb287183258"
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 --- Comment #15 from Martin Flöser --- Error point in krfb: https://cgit.kde.org/krfb.git/tree/framebuffers/pipewire/pw_framebuffer.cpp#n385 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 --- Comment #14 from Martin Flöser --- With pipewire installed xdg-desktop-portal-kde no longer crashes, but krfb still doesn't work and I get now: Using FrameBuffer: "pw" Initializing D-Bus connectivity with XDG Desktop Portal DBus session created: "/org/freedesktop/portal/desktop/request/1_154/krfb3821356350" Starting server. Listen port: 5900 Listen Address: "0.0.0.0" Password enabled: true Failed to start screencast: 2 Followed by a crash once we try to connect. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 --- Comment #13 from Martin Flöser --- Looks like we need a (runtime) dependency on pipewire. The package pipewire contains that file but on my system pipewire isn't installed yet, only libpipewire. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 --- Comment #12 from Martin Flöser --- Running xdg-desktop-portal-kde from command line gives the right hint: can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: cannot open shared object file: No such file or directory -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 --- Comment #11 from Martin Flöser --- Yet another step, but still no success. We get a dialog from xdg-desktop-portal-kde asking whether we want to allow and then a crash :-( Application: xdg-desktop-portal-kde (xdg-desktop-portal-kde), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6c34041800 (LWP 29437))] Thread 5 (Thread 0x7f6c14995700 (LWP 29986)): #0 0x7f6c2b9c29f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e72523a408) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e72523a3b8, cond=0x55e72523a3e0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e72523a3e0, mutex=0x55e72523a3b8) at pthread_cond_wait.c:655 #3 0x7f6c1e3b42cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f6c1e3b3ff7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f6c2b9bc6db in start_thread (arg=0x7f6c14995700) at pthread_create.c:463 #6 0x7f6c2f46488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f6c16236700 (LWP 29440)): #0 0x7f6c28912649 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6c288cbfec in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6c288cc570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6c288cc6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6c2fdaa9db in QEventDispatcherGlib::processEvents (this=0x7f6c0c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f6c2fd4aeaa in QEventLoop::exec (this=this@entry=0x7f6c16235da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f6c2fb663ca in QThread::exec (this=) at thread/qthread.cpp:531 #7 0x7f6c2fb67b72 in QThreadPrivate::start (arg=0x55e72500c8c0) at thread/qthread_unix.cpp:360 #8 0x7f6c2b9bc6db in start_thread (arg=0x7f6c16236700) at pthread_create.c:463 #9 0x7f6c2f46488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f6c1d0e1700 (LWP 29439)): #0 0x7f6c2b9c29f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e724e9c4e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e724e9c498, cond=0x55e724e9c4c0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e724e9c4c0, mutex=0x55e724e9c498) at pthread_cond_wait.c:655 #3 0x7f6c1e3b42cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f6c1e3b3ff7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f6c2b9bc6db in start_thread (arg=0x7f6c1d0e1700) at pthread_create.c:463 #6 0x7f6c2f46488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f6c1f84d700 (LWP 29438)): #0 0x7f6c2f457bf9 in __GI___poll (fds=0x7f6c18003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6c288cc5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6c288cc6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6c2fdaa9db in QEventDispatcherGlib::processEvents (this=0x7f6c18000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f6c2fd4aeaa in QEventLoop::exec (this=this@entry=0x7f6c1f84cd70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f6c2fb663ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f6c314bd0e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f6c2fb67b72 in QThreadPrivate::start (arg=0x7f6c31734d80) at thread/qthread_unix.cpp:360 #8 0x7f6c2b9bc6db in start_thread (arg=0x7f6c1f84d700) at pthread_create.c:463 #9 0x7f6c2f46488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f6c34041800 (LWP 29437)): [KCrash Handler] #6 0x7f6c33024c21 in pw_thread_loop_new (loop=0x0, name=name@entry=0x55e72390cd22 "pipewire-main-loop") at ../src/pipewire/thread-loop.c:128 #7 0x55e7238f056e in ScreenCastStream::init (this=this@entry=0x55e725487f80) at ./src/screencaststream.cpp:294 #8 0x55e7238fefcf in WaylandIntegration::WaylandIntegrationPrivate::startStreaming (this=0x55e723b1f460 <(anonymous namespace)::Q_QGS_globalWaylandIntegration::innerFunction()::holder>, outputName=) at ./src/waylandintegration.cpp:243 #9 0x55e7238f7254 in RemoteDesktopPortal::Start (this=, handle=..., session_handle=..., app_id=..., parent_window=..., options=..., results=...) at ./src/remotedesktop.cpp:129 #10 0x55e7239046b8 in RemoteDesktopPortal::qt_static_metacall (_o=_o@entry=0x55e724eb97e0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=2, _a=_a@entry=0x7ffd06869930) at ./obj-x86_64-linux-gnu/src/xdg-desktop-portal-kde_autogen/EWIEGA46WW/moc
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 --- Comment #9 from Martin Flöser --- And I think I found it. xdg-desktop-portal-kde also needs the pipewire dependency. From build.neon log: -- The following features have been disabled: 02:36:40 02:36:40 * Screencast portal, Support for screen sharing 02:36:40 02:36:40 -- The following OPTIONAL packages have not been found: 02:36:40 02:36:40 * PipeWire, PipeWire - multimedia processing, <http://www.pipewire.org> 02:36:40Required for screencast portal 02:36:40 * GBM, Mesa gbm library., <http://www.mesa3d.org> 02:36:40Required for screencast portal 02:36:40 * Epoxy, libepoxy, <http://github.com/anholt/libepoxy> 02:36:40Required for screencast portal -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 --- Comment #8 from Martin Flöser --- Another step in the right direction, but we are still not there :-( Krfb starts now without an error message, but in log I see: "Failed to create session: 2" and as soon as a client connects, krfb crashes. I do not know whether something is still missing or whether this is a bug in krfb. I'll try to investigate. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 --- Comment #6 from Martin Flöser --- I think I found it :-) 20:44:10 dh_auto_configure -- \ 20:44:10--enable-docbook-docs \ 20:44:10--enable-geoclue \ 20:44:10--enable-installed-tests \ 20:44:10--disable-pipewire \ From https://build.neon.kde.org/job/bionic_unstable_backports-bionic_xdg-desktop-portal_bin_amd64/1/console I guess --disable-pipewire disables pipewire support which is required for screencast. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 --- Comment #5 from Martin Flöser --- Weird, I still get the same error and looking in qdbusviewer it indeed does not have the required interface. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412969] New: Rendering issue with window decoration borders and fractional scaling
https://bugs.kde.org/show_bug.cgi?id=412969 Bug ID: 412969 Summary: Rendering issue with window decoration borders and fractional scaling Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scene-opengl Assignee: kwin-bugs-n...@kde.org Reporter: mgraess...@kde.org Target Milestone: --- Created attachment 123202 --> https://bugs.kde.org/attachment.cgi?id=123202=edit gap between window and content visible SUMMARY When using fractional scaling (e.g. 1.25) on Wayland one can notice a gap between the window content and the window decoration. Comparable to what we always had when enabling wobbly windows. STEPS TO REPRODUCE 1. Use Wayland 2. Use fractional scaling of 1.25 3. Use window decoration borders OBSERVED RESULT Gap between window content and window decoration (see screenshot) EXPECTED RESULT Properly rendered window ADDITIONAL INFORMATION Version === KWin version: 5.17.80 Qt Version: 5.13.1 Qt compile version: 5.13.1 XCB compile version: 1.13 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_EGL_STREAMS: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11906000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Plugin recommends border size: None Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 12 font: Noto Sans,10,-1,5,50,0,0,0,0,0,Regular smallSpacing: 3 largeSpacing: 12 Platform == Name: DRM Active: true Atomic Mode Setting: true Using EGL Streams: false Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: true condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 2 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 101 glPlatformInterface: 2 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: LG Display eDP-1-unknown Geometry: 0,0,1536x864 Scale: 1.25 Refresh Rate: 60.042 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2) OpenGL version string: 3.0 Mesa 19.0.8 OpenGL platform interface: EGL OpenGL shading language version string: 1.30 Driver: Intel GPU class: Unknown OpenGL version: 3.0 GLSL version: 1.30 Mesa version: 19.0.8 Linux kernel version: 4.15 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom trackmouse touchpoints thumbnailaside kwin4_effect_morphingpopups kwin4_effect_login kwin4_effect_logout kwin4_effect_frozenapp kwin4_effect_maximize kwin4_effect_fadingpopups kwin4_effect_translucency kwin4_effect_fade kwin4_effect_dialogparent
[kwin] [Bug 412969] Rendering issue with window decoration borders and fractional scaling
https://bugs.kde.org/show_bug.cgi?id=412969 Martin Flöser changed: What|Removed |Added Flags||Wayland+ Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 Martin Flöser changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #3 from Martin Flöser --- Unfortunately it is still not working: Using FrameBuffer: "pw" Initializing D-Bus connectivity with XDG Desktop Portal Unsupported XDG Portal screencast interface version: 0 No valid framebuffer found. returning null. QObject::connect(FrameBuffer, RfbServerManager): invalid null parameter Unable to get rbfserver screen --- It looks to me like we also need an updated xdg-desktop-portal. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411636] New: krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 Bug ID: 411636 Summary: krfb misses pipewire plugin Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Dev Edition [unstable] Assignee: neon-b...@kde.org Reporter: mgraess...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Since 19.08 krfb provides a pipewire plugin. This is not built/installed in the neon package. Due to that krfb errors out when used on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Placement policy 'Remember'
https://bugs.kde.org/show_bug.cgi?id=15329 --- Comment #42 from Martin Flöser --- Sorry, but this is not possible to implement for a window manager. We lack information to identify that a window is the same as previous window. Please see Thomas's comments on that. As Thomas states this is clearly a client job and we can only do something in frameworks for KDE applications. On Wayland we lack the same information and I don't see a possibility to add a spec adding the required functionality as it requires each and every application to change. Even Qt API doesn't provide anything to specify the required functionality. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 411369] Does not trigger lock screen if right click menu is shown
https://bugs.kde.org/show_bug.cgi?id=411369 Martin Flöser changed: What|Removed |Added Component|general |general Product|kwin|kscreenlocker Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Version|5.16.4 |unspecified CC||bhus...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Martin Flöser --- This is a known limitation on X11 and is fixed on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 411199] KWin crashes when changing colour schemes
https://bugs.kde.org/show_bug.cgi?id=411199 Martin Flöser changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |unassigned-b...@kde.org Version|git master |unspecified Product|kwin|Breeze Component|wayland-generic |QStyle --- Comment #1 from Martin Flöser --- Reassigning to breeze as the assert I'd triggered from the kstyle. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411049] Kwin crash after turn off "Sync to VBlank"
https://bugs.kde.org/show_bug.cgi?id=411049 Martin Flöser changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Martin Flöser --- Backtrace is better. What we can see is the previous KWin instance crashing on tear down. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411071] When Chrome startup and is running then kde menu stop working.
https://bugs.kde.org/show_bug.cgi?id=411071 Martin Flöser changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Martin Flöser --- Crash happens in proprietary Nvidia driver. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411044] Badly rendered font after adding Flathub to sources
https://bugs.kde.org/show_bug.cgi?id=411044 Martin Flöser changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #5 from Martin Flöser --- KWin ist not responsible for don't rendering. Nate, please don't move unrelated bugs to KWin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411049] Kwin crash after turn off "Sync to VBlank"
https://bugs.kde.org/show_bug.cgi?id=411049 Martin Flöser changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #3 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. if you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410839] Kwin crashes sometimes when using the virtual desktop grid
https://bugs.kde.org/show_bug.cgi?id=410839 Martin Flöser changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- --- Comment #3 from Martin Flöser --- Backtrace is provided -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410869] kwin_x11 crashed after swtching to tty
https://bugs.kde.org/show_bug.cgi?id=410869 Martin Flöser changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #3 from Martin Flöser --- You are running multiple KWin instances. This is probably the reason for the high cpu usage. Please kill the additional ones. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410839] Kwin crashes sometimes when using the virtual desktop grid
https://bugs.kde.org/show_bug.cgi?id=410839 Martin Flöser changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410827] Neither KWinscript nor wmctrl show all the windows on Wayland
https://bugs.kde.org/show_bug.cgi?id=410827 Martin Flöser changed: What|Removed |Added Resolution|--- |LATER Status|REPORTED|RESOLVED --- Comment #1 from Martin Flöser --- Wmctrl is an X11 tool. Obviously it cannot show Wayland windows. Wayland windows are currently excluded from scripting due to security constraints. This will eventually be changed in future. As this is currently intended I'm setting to resolved later. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410795] "Focus prevention: High" prevents windows from being raised, despite independent raise & focus preference
https://bugs.kde.org/show_bug.cgi?id=410795 Martin Flöser changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Martin Flöser --- I'm sorry, but our understanding of focus stealing is also preventing windows from raising itself. I assume you don't experience this with all apps. If I am right, please report the issue to the affected applications: they shouldn't try to raise themselves. This is important as Wayland doesn't allow changes of stacking order. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410298] BUG : Incorrect window sizes previewed in the "Present Windows" Desktop effect !!!
https://bugs.kde.org/show_bug.cgi?id=410298 Martin Flöser changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Martin Flöser --- In the grid layout all windows get the same slot size. What you experience as a bug is the intention of this layout. If you want a layout which honors the sizes use the default layout mode. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410296] FEATURE REQUEST : Present Windows Effect ... ability to change the size and spacing of the Window Preview thumbnails !!!
https://bugs.kde.org/show_bug.cgi?id=410296 Martin Flöser changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Martin Flöser --- I'm sorry but the Present Windows effect is unfortunately not in any state to extend it further. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410294] FEATURE REQUEST : Improving the 'Elegance Quotient' of kwin with additional controls at the discretion of the user to adapt them to their respective screen sizes !!!
https://bugs.kde.org/show_bug.cgi?id=410294 Martin Flöser changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Martin Flöser --- Please report one feature request per issue. We cannot track multiple issues in one report. Please note that the pager is not part of KWin but Plasma. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407917] Poor performance when open a more than N argb windows
https://bugs.kde.org/show_bug.cgi?id=407917 Martin Flöser changed: What|Removed |Added Summary|Poor performance when open |Poor performance when open |a more than N windows |a more than N argb windows -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407917] Poor performance when open a more than N windows
https://bugs.kde.org/show_bug.cgi?id=407917 Martin Flöser changed: What|Removed |Added Component|platform-wayland|compositing Flags||Wayland+, X11+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Super (Meta) Key stops working
https://bugs.kde.org/show_bug.cgi?id=391322 Martin Flöser changed: What|Removed |Added Flags||Wayland-, X11+ Component|input |platform-x11-standalone -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409548] fails to assign window shortcut which includes META
https://bugs.kde.org/show_bug.cgi?id=409548 --- Comment #4 from Martin Flöser --- What's your keyboard layout? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410154] Contextu Menu & Drag & Drop Actions Don't Work As It Expected Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410154 --- Comment #3 from Martin Flöser --- Do I understand correctly that you want to drag and drop while this context menu is open? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410181] when using an xmodmap, some key-combinations never reach the active application
https://bugs.kde.org/show_bug.cgi?id=410181 Martin Flöser changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Martin Flöser --- KWin (and no KDE software) is responsible for xmodmap handling. Please report to the appropriate place where the incorrect handling occurs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410178] Screen framerate doesn't change with refresh rate changes
https://bugs.kde.org/show_bug.cgi?id=410178 Martin Flöser changed: What|Removed |Added Component|core|platform-x11-standalone Flags||Wayland-, X11+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410154] Contextu Menu & Drag & Drop Actions Don't Work As It Expected Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410154 --- Comment #1 from Martin Flöser --- Could you please illustrate with a screenshot where you click? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410146] Kwin crashes with too many visual effects
https://bugs.kde.org/show_bug.cgi?id=410146 Martin Flöser changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #2 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland while numlock is enabled
https://bugs.kde.org/show_bug.cgi?id=400658 --- Comment #26 from Martin Flöser --- Interesting, so numlock is not active, but a "mod2". The event resolving shows Keypad modifier to be active. Something is weird. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410093] KWin crash after switch to/from text console
https://bugs.kde.org/show_bug.cgi?id=410093 Martin Flöser changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland while numlock is enabled
https://bugs.kde.org/show_bug.cgi?id=400658 --- Comment #22 from Martin Flöser --- Could you please open KWin debug console and check in the input event tab what keysyms are reported when triggering the not working shortcut. Also the keyboard tab could be interesting as it lists the active modifiers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #12 from Martin Flöser --- Actually no. KWin only performs a sanity check for windows requesting a size larger than the screen. This isn't meant for restore of windows, but for screen layout changes. Such a sanity check is useful, but shouldn't replace a correct implementation in the applications. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #9 from Martin Flöser --- I assume the problem lies in a library. Either Qt or a KDE Framework. Unfortunately I do not know which part is responsible here. So I would suggest to report against an application so that they can investigate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #6 from Martin Flöser --- Well, as I said: restoring size (including maximized state) is task of the applications. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland while numlock is enabled
https://bugs.kde.org/show_bug.cgi?id=400658 --- Comment #19 from Martin Flöser --- Can you please try with us layout? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland while numlock is enabled
https://bugs.kde.org/show_bug.cgi?id=400658 --- Comment #17 from Martin Flöser --- What's the used keyboard layout? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409979] Kwin rules forcing all windows to single monitor do not (always) apply.
https://bugs.kde.org/show_bug.cgi?id=409979 --- Comment #1 from Martin Flöser --- Rules are not evaluated when the screen layout changes. Only apply initial and apply now makes sense for the screen rule. If you want dynamic actions use a script instead. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #1 from Martin Flöser --- Restoring the size is the task of the applications. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409889] Staking order is not accessible in KWin scripts
https://bugs.kde.org/show_bug.cgi?id=409889 --- Comment #4 from Martin Flöser --- Please be aware that stacking order would be read only. To manipulate you would have to use the existing API calls. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409903] With kwin Wayland, the settings app have a minimum size.
https://bugs.kde.org/show_bug.cgi?id=409903 Martin Flöser changed: What|Removed |Added Product|kwin|systemsettings Component|wayland-generic |general Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409490] Recording desktop video isn't possible with compositing disabled
https://bugs.kde.org/show_bug.cgi?id=409490 --- Comment #13 from Martin Flöser --- Yes of course all of them. There is no screen recording interface on X11. So what do the applications do? None of them created a performant screen recording interface. So they all abuse functionality which is not meant this way. I just checked how recordmydesktop records: it uses either GetImage or ShmGetImage. You are playing a game which is probably OpenGL rendered using direct rendering? I do hope for you that the game uses direct rendering to bypass the X server and render directly to the GPU. In no sane world ShmGetImage will return back the image to you. The closest X11 has to a screen recording interface is the composite extension which is not used by recordmydesktop. Sorry, but there is just no sane way to record on X11. On Wayland we created this by explicitly looking at what's wrong on X11 and added it directly in the compositor in a way that it doesn't need to read back to memory and provide a performance penalty. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409490] Recording desktop video isn't possible with compositing disabled
https://bugs.kde.org/show_bug.cgi?id=409490 --- Comment #11 from Martin Flöser --- @Nick: Did you try recordmydesktop with the --no-wm-check command line option? Are you recording the complete desktop or do you use the --windowid command line switch to just capture the game? I'm now in front of a real keyboard and explain why I am so sure that this is not a bug in our software. I am aware of the heuristics for example recordmydesktop does - such heuristics are a bad idea to start with. How does one want to do one heuristic to cover KWin composited and non-composited? And even if, is that the only contributing factor? Certainly not, in Plasma we have several untypical components which break such heuristics. For example the task manager is an additional compositor (which is totally fine and in-spec) and the main difference to other desktop environments is that Plasma doesn't render into the root window. This can be contributing factors to breaking screen recorders. But everything we do is totally fine and totally in compliance with the X protocol and we have done so for years. If screen recorders cannot handle this, it's their bug and not ours. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409845] switch desktop shortcut not work
https://bugs.kde.org/show_bug.cgi?id=409845 Martin Flöser changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Martin Flöser --- Sorry but I do not understand what you tell us. Could you please explain in more detail? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409838] Kwin crashed
https://bugs.kde.org/show_bug.cgi?id=409838 Martin Flöser changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409490] Recording desktop video isn't possible with compositing disabled
https://bugs.kde.org/show_bug.cgi?id=409490 Martin Flöser changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #10 from Martin Flöser --- Nate, this is not a bug in any component of our stack. We track bugs in our software and are not a user support forum. If users need user support, this needs to go somewhere else. If you want to provide the use support please do so but not in the KWin product. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409490] Recording desktop video isn't possible with compositing disabled
https://bugs.kde.org/show_bug.cgi?id=409490 Martin Flöser changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #7 from Martin Flöser --- Of course games run on Wine in Wayland. KWin is not related in this issue, there is nothing premature about this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409396] Random app launches when top-left corner is clicked
https://bugs.kde.org/show_bug.cgi?id=409396 Martin Flöser changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #6 from Martin Flöser --- This is not KWin related. KWin can neither launch applications nor does it register any left click in top-left corner. This sounds like a problem with status notifiers. Please ensure the xembedsniproxy is running. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor
https://bugs.kde.org/show_bug.cgi?id=409763 --- Comment #8 from Martin Flöser --- (In reply to aska990 from comment #7) > Fair enough. > > Then I have 2 more questions, if you don't mind : > > - Is there a reliable way to measure the actual refresh rate used by KWin ? No. And it doesn't make any sense to try to measure. KWin renders only if something changes, so in practice it's around 0 Hz on idle. > - What should it be in theory in a mixed setup (say, 60Hz + 144Hz) ? X11 only supports rendering to both screens at the same time. It doesn't make sense to render with 144 Hz on a 60 Hz Screen, but a 144 Hz screen handles 60 Hz just fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409490] Recording desktop video isn't possible with compositing disabled
https://bugs.kde.org/show_bug.cgi?id=409490 --- Comment #2 from Martin Flöser --- This is a problem of the recorder you use. If compositing is disabled KWin is not involved at all. Please be aware that recording adds a huge lag no matter whether compositing is enabled or not. X11 is not designed for such use cases and performs extremely bad for screen recording. I recommend to use Wayland instead. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409797] KWin Window Rules Doesn't Work Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409797 --- Comment #1 from Martin Flöser --- Not all rules are supported yet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor
https://bugs.kde.org/show_bug.cgi?id=409763 Martin Flöser changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #6 from Martin Flöser --- As you are quite aware of: fps effect is not a way to detect the actual used refresh rate, especially not if refresh rate of screens is > 100 Hz. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403421] some QT based application don't show anything but plain color in their window
https://bugs.kde.org/show_bug.cgi?id=403421 --- Comment #4 from Martin Flöser --- Please provide the output of qdbus org.kde.KWin /KWin supportInformation Please also attach screenshots to the bug report instead of link to external page. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403421] some QT based application don't show anything but plain color in their window
https://bugs.kde.org/show_bug.cgi?id=403421 Martin Flöser changed: What|Removed |Added Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor
https://bugs.kde.org/show_bug.cgi?id=409763 Martin Flöser changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Martin Flöser --- According to the output of xrandr the screen is running at 60 Hz. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409760] Windows dont remember their size/location with dual monitors
https://bugs.kde.org/show_bug.cgi?id=409760 Martin Flöser changed: What|Removed |Added Version|5.16.2 |unspecified Assignee|kwin-bugs-n...@kde.org |dolphin-bugs-n...@kde.org Component|general |general Product|kwin|dolphin CC||elvis.angelac...@kde.org --- Comment #1 from Martin Flöser --- It's the task of the applications to remember the size. Reassigning to dolphin as it's the used example. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400645] First launch of Discover after boot: Borders drawn but content of window is "screenshot" of the last active window for 1-2 seconds
https://bugs.kde.org/show_bug.cgi?id=400645 Martin Flöser changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #5 from Martin Flöser --- This is a typical problem of graphics drivers on X11 for applications using opengl. There is nothing we can do except switching to Wayland. -- You are receiving this mail because: You are watching all bug changes.
