[kwin] [Bug 449518] kwin_wayland doesnt focus window when right clicking decoration/window border
https://bugs.kde.org/show_bug.cgi?id=449518 --- Comment #4 from Tom Englund --- (In reply to Vlad Zahorodnii from comment #3) > Can you please reiterate the purpose or the usecase why the window should be > activated? 2022-02-02 its some time ago but as i remember it it was just different to how X dealt with it, and felt like an odd thing to see the context menu appear but the window not focused. like i was interacting with an unfocused window? heh. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484593] no context menu for taskmanager with touchpad two finger click
https://bugs.kde.org/show_bug.cgi?id=484593 --- Comment #3 from Tom Englund --- actually just reverting this makes it work again https://invent.kde.org/plasma/plasma-desktop/-/commit/f2160c3b68c4adcac6c399e14a88b80c23343d55 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484593] no context menu for taskmanager with touchpad two finger click
https://bugs.kde.org/show_bug.cgi?id=484593 --- Comment #2 from Tom Englund --- (In reply to Zamundaaa from comment #1) > If it only affects the task manager, it'll be some bug there. > FWIW it does work for me though, might be specific to how your touchpad > emits events or something hm anyway i can test or provide more info regarding that? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484593] New: no context menu for taskmanager with touchpad two finger click
https://bugs.kde.org/show_bug.cgi?id=484593 Bug ID: 484593 Summary: no context menu for taskmanager with touchpad two finger click Classification: Plasma Product: kwin Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- SUMMARY if i change touchpad settings -> right click to "press anywhere with two fingers" im not getting a context menu in the task manager for pinning/unpinning applications. works if i revert it to "Press bottom right corner" only seem to affect taskmanager, the panel itself and other widgets/systray or desktop works. SOFTWARE/OS VERSIONS Operating System: Gentoo KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.8.1-gentoo-tom (64-bit) Graphics Platform: Wayland Processors: 32 × 13th Gen Intel® Core™ i9-13900HX Memory: 94,0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LENOVO Product Name: 82WQ System Version: Legion Pro 7 16IRX8H -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482668] Crash in Energy Savings KCM when configured power action is newly unsupported
https://bugs.kde.org/show_bug.cgi?id=482668 --- Comment #12 from Tom Englund --- (In reply to Jakob Petsovits from comment #11) > (In reply to Tom Englund from comment #10) > > i guess worth mentioning 16 didnt work either > > Sorry yeah, 16 was meant as an example for people who explicitly want to > make it crash but don't have your system setup. oh i misread your comment "For anyone to reproduce a crash like this" i read it first as "for anyone having a crash like this one can add this to their config " gotta properly read the entire thing before thinking! my mistake. :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482668] Crash in Energy Savings KCM when configured power action is newly unsupported
https://bugs.kde.org/show_bug.cgi?id=482668 --- Comment #10 from Tom Englund --- (In reply to Jakob Petsovits from comment #6) > (In reply to Tom Englund from comment #5) > > [BatteryManagement] > > BatteryCriticalAction=1 > > > > and yeah removing it makes it work again > > Okay, nice. "1" is the value for "Sleep". What it looks like to me is that > your system does not actually support the Sleep action (as in > PowerManagement::canSuspend()), so it's missing from the list of combo box > actions but the UI still tries to find and set it. One instance I could see > this happening is if one copies an existing laptop Arch installation (with > that setting already set) to a new drive that powers e.g. a PC without > "Sleep" functionality. Or maybe "Sleep" was the default a long time ago and > written to the config file before we used KConfigXT even for global settings > (i.e. before my time here). > > Either way, we should probably do something more graceful with unsupported > power actions than just crash. Although I'm not quite sure how to deal with > that in the UI. > > For anyone to reproduce a crash like this, one can add this to their > ~/.config/powerdevilrc: > > [BatteryManagement] > BatteryCriticalAction=16 > > which is an action that generally exists (PromptLogoutDialog) but does not > exist in the option list for the critical battery action combobox. i guess worth mentioning 16 didnt work either, removing the entry the only two options i have is "do nothing and shutdown" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482668] systemsettings/powerdevil crash pressing Advanced Power Settings
https://bugs.kde.org/show_bug.cgi?id=482668 --- Comment #7 from Tom Englund --- (In reply to Jakob Petsovits from comment #6) > (In reply to Tom Englund from comment #5) > > [BatteryManagement] > > BatteryCriticalAction=1 > > > > and yeah removing it makes it work again > > Okay, nice. "1" is the value for "Sleep". What it looks like to me is that > your system does not actually support the Sleep action (as in > PowerManagement::canSuspend()), so it's missing from the list of combo box > actions but the UI still tries to find and set it. One instance I could see > this happening is if one copies an existing laptop Arch installation (with > that setting already set) to a new drive that powers e.g. a PC without > "Sleep" functionality. Or maybe "Sleep" was the default a long time ago and > written to the config file before we used KConfigXT even for global settings > (i.e. before my time here). > > Either way, we should probably do something more graceful with unsupported > power actions than just crash. Although I'm not quite sure how to deal with > that in the UI. > > For anyone to reproduce a crash like this, one can add this to their > ~/.config/powerdevilrc: > > [BatteryManagement] > BatteryCriticalAction=16 > > which is an action that generally exists (PromptLogoutDialog) but does not > exist in the option list for the critical battery action combobox. I think its because i disabled sleep in systemd confs, its half broken on my Nvidia dgpu and the kids have fingered that fn + sleep button more then once heh -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482668] systemsettings/powerdevil crash pressing Advanced Power Settings
https://bugs.kde.org/show_bug.cgi?id=482668 --- Comment #5 from Tom Englund --- (In reply to Jakob Petsovits from comment #4) > Thanks. That's not a duplicate then, different bug. > > The stacktrace indicates that it wants something from PowerButtonActionModel > but is apparently not finding it there, and crashes instead when trying to > access it. The only use of PowerButtonActionModel on the Advanced Settings > page is for the critical-battery action combo box. Which... hm, here's an > idea > > In your $HOME/.config/powerdevilrc file, is there a line that goes like, > > BatteryCriticalAction=(some value) > > If so, could you please paste that line? And also try if it still crashes > when you delete it and save the config file? [BatteryManagement] BatteryCriticalAction=1 and yeah removing it makes it work again -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482668] systemsettings/powerdevil crash pressing Advanced Power Settings
https://bugs.kde.org/show_bug.cgi?id=482668 --- Comment #3 from Tom Englund --- (In reply to Jakob Petsovits from comment #2) > (In reply to Nate Graham from comment #1) > > Is this that thing you fixed recently, Jakob? > > Possibly, but the reproduction steps don't involve *closing* navigating away > from the Energy Saving KCM (by closing System Setting, or by trying to open > another settings module), which was a crucial step in Bug 481045. > > Tom, could you confirm that merely opening Advanced Power Settings is > causing the crash? i.e. you don't even get to see the settings form with > battery levels and stuff? yeah as fast as i press the button it crashes, no window even slightly starts to appear like its trying to load. just instantly on press -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482668] New: systemsettings/powerdevil crash pressing Advanced Power Settings
https://bugs.kde.org/show_bug.cgi?id=482668 Bug ID: 482668 Summary: systemsettings/powerdevil crash pressing Advanced Power Settings Classification: Plasma Product: Powerdevil Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tomenglun...@gmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY #0 0x74a951cb in pthread_kill@@GLIBC_2.34 () at /usr/lib/libc.so.6 #1 0x74a40f64 in raise () at /usr/lib/libc.so.6 #2 0x77b6443f in KCrash::defaultCrashHandler (sig=11) at /usr/src/debug/kcrash/kcrash-6.0.0/src/kcrash.cpp:586 #3 0x74a41000 in () at /usr/lib/libc.so.6 #4 std::__atomic_base::fetch_add (__m=std::memory_order_acq_rel, __i=1, this=0x7, this=, __i=, __m=) at /usr/include/c++/13.2.1/bits/atomic_base.h:633 #5 QAtomicOps::ref (_q_value=, _q_value=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qatomic_cxx11.h:258 #6 QBasicAtomicInteger::ref (this=0x7, this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qbasicatomic.h:49 #7 QArrayData::ref (this=0x7, this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qarraydata.h:52 #8 QArrayDataPointer::ref (this=0x7fff3b30, this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qarraydatapointer.h:412 #9 QArrayDataPointer::QArrayDataPointer (other=..., this=0x7fff3b30, this=, other=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qarraydatapointer.h:40 #10 QString::QString (other=..., this=0x7fff3b30, this=, other=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/text/qstring.h:1107 #11 QVariant::Private::Private (t=..., this=0x7fff3b30) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qvariant_p.h:98 #12 QVariant::QVariant (this=0x7fff3b30, val=..., this=, val=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qvariant.cpp:946 #13 0x7fffd21999c6 in PowerButtonActionModel::data (this=, index=, role=) at /usr/src/debug/powerdevil/powerdevil-6.0.1/kcmodule/common/PowerButtonActionModel.cpp:113 #14 0x75320e52 in QAbstractItemModel::qt_static_metacall (_o=, _c=, _id=, _a=0x7fff3e18) at /usr/src/debug/qt6-base/build/src/corelib/Core_autogen/include/moc_qabstractitemmodel.cpp:1078 #15 0x75321d33 in QAbstractItemModel::qt_metacall (_a=0x7fff3e18, _id=38, _c=QMetaObject::InvokeMetaMethod, this=0x57d5a360) at /usr/src/debug/qt6-base/build/src/corelib/Core_autogen/include/moc_qabstractitemmodel.cpp:1307 #16 QAbstractListModel::qt_metacall (this=0x57d5a360, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff3e18) at /usr/src/debug/qt6-base/build/src/corelib/Core_autogen/include/moc_qabstractitemmodel.cpp:1597 #17 0x762d7d64 in QQmlObjectOrGadget::metacall (this=0x7fff40d0, type=QMetaObject::InvokeMetaMethod, index=, argv=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlobjectorgadget.cpp:14 #18 0x761b742f in QV4::CallMethod (callType=, callArgs=, engine=, argTypes=, argCount=, returnType=..., index=, object=) at /usr/include/qt6/QtCore/qvarlengtharray.h:84 #19 QV4::CallPrecise (object=..., data=, engine=, engine@entry=0x56a1fa30, callArgs=, callArgs@entry=0x7fffd1be88c0, callType=callType@entry=QMetaObject::InvokeMetaMethod) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:1850 #20 0x761bb239 in operator() (__closure=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:2753 #21 operator() > (call=, __closure=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:2730 #22 QV4::QObjectMethod::callInternal (this=0x7fff4190, thisObject=, argv=0x7fffd1be8860, argc=2) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:2753 #23 0x761cef61 in QV4::Runtime::CallPropertyLookup::call (engine=0x56a1fa30, base=..., index=, argv=0x7fffd1be8860, argc=2) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4runtime.cpp:1511 STEPS TO REPRODUCE 1. open system settings 2. to to Energy Saving 3. press Advanced Power Settings SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × 13th Gen Intel® Core™ i9-13900HX Memory: 31,1 GiB of RAM Graphics P
[kwin] [Bug 479958] New: nvidia spams journal/dmesg with a second monitor on a dgpu setup
https://bugs.kde.org/show_bug.cgi?id=479958 Bug ID: 479958 Summary: nvidia spams journal/dmesg with a second monitor on a dgpu setup Classification: Plasma Product: kwin Version: 5.92.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- SUMMARY im not sure if this is a kwin bug or a nvidia one but if i use an external monitor on my dgpu and run a game in wine or some other random thing eventually it begins spamming "[drm] [nvidia-drm] [GPU ID 0x0100] Framebuffer memory not appropriate for scanout" in dmesg/journal. this happend before on 5.27.x series and testing the 5.92.0 RC from archlinux kde-unstable repo it does aswell. was seeing posts like https://forums.developer.nvidia.com/t/hardware-cursor-is-not-working-on-wayland-drm-sessions/261853/2 so i thought id wait until that is figured out but if im not mistaken this RC has the HW cursor patches from https://invent.kde.org/plasma/kwin/-/merge_requests/4695 STEPS TO REPRODUCE 1. run a laptop with a nvidia dgpu and attach a external monitor 2. launch a wine game fullscreened 3. nvidia begins spamming SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.7.0 Kernel Version: 6.6.8-273-tkg-eevdf-llvm (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 30,7 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474364] dual monitors with one monitor scaled sometimes corrupts the non scaled
https://bugs.kde.org/show_bug.cgi?id=474364 --- Comment #1 from Tom Englund --- i have been backporting various commits and merge requests just for fun tinkering and hopes that i manage to get https://invent.kde.org/plasma/kwin/-/merge_requests/4177 built ontop of plasma5. now something like two thirds there and like 30 merge requests later. this has stopped happening so might be fixed in plasma 6/kwin master. the issue was not because of my tinkering, its occuring on the default kwin from repos. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474364] New: dual monitors with one monitor scaled sometimes corrupts the non scaled
https://bugs.kde.org/show_bug.cgi?id=474364 Bug ID: 474364 Summary: dual monitors with one monitor scaled sometimes corrupts the non scaled Classification: Plasma Product: kwin Version: 5.27.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- SUMMARY i have two monitors with 2560x1440 but since one is 15" and one 27" im scaling the 15" to 125% to get a relative readable font. but sometimes when either logging in or launching applications from the desktop icons the non scaled monitor flickers and somehow corrupts/changes like its trying to scale itself. screenshot https://i.imgur.com/fiwgri4.jpg , ignore the white bar on the left scaled monitor thats something spectacle adds. this can be "reverted" by simply disabling the non scaled monitor in system settings and enabling it again. sadly it doesnt happend always so its not all to easy to reproduce. STEPS TO REPRODUCE 1. use dual monitors 2. scale one monitor 3. at random when logging in or launching applications from desktop icons it "flickers/rescales" the second monitor. doesnt seem to occur when launching things from either konsole or alt + f2. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.5.2-arch1-1 (64-bit) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick/controller/gamepad is in use
https://bugs.kde.org/show_bug.cgi?id=328987 Tom Englund changed: What|Removed |Added CC||tomenglun...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470463] New: resizing popups somewhat artifacts
https://bugs.kde.org/show_bug.cgi?id=470463 Bug ID: 470463 Summary: resizing popups somewhat artifacts Classification: Plasma Product: kwin Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- bit hard to screenshot so il upload two photos taken with a phone. but hovering system tray icons and a popup shows text/content if you go from a big popup over to a small one, it seems like it tries to resize it but leaves old content around. almost like its rendering it before it has been properly resized. using the morphing popup effect makes it more visible, it happends without it but gets rerendered fast enough to not be an annoyance. small popup https://i.imgur.com/ZK7YrKY.jpg big popup https://i.imgur.com/ahm0piE.jpg hovering the mouse over the artifacts makes them go away. STEPS TO REPRODUCE 1. hover a systray icon with a "big" popup. 2. mouse over to another icon with a smaller size. 3. artifacts appear while its "resizing/morphing" SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.4-1-tom (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 30,7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Acer Product Name: Nitro AN515-45 System Version: V1.10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465416] when second monitor powers off/on virtual desktop pager doesnt update
https://bugs.kde.org/show_bug.cgi?id=465416 --- Comment #1 from Tom Englund --- https://i.imgur.com/SfliTIG.png as an example, on this virtual desktop i had 2 windows with konsole open. they get restored positioned wise, but the virtual pager shows it as empty until i move/resize it. https://i.imgur.com/SfliTIG.png -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463958] Recurring stutter of the whole desktop
https://bugs.kde.org/show_bug.cgi?id=463958 Tom Englund changed: What|Removed |Added CC||tomenglun...@gmail.com --- Comment #18 from Tom Englund --- if i didnt miss something but seems you all are on ryzens. i would check if your fTPM/TPM is enabled in bios. unsure when exactly this landed https://github.com/torvalds/linux/commit/b006c439d58db625318bf2207feabf847510a8a6 but it introduces the https://www.amd.com/en/support/kb/faq/pa-410 which windows 11 users hit when it began requiring people to enable TPM. i myself hit it aswell. affects pretty much entire ryzen lineup. some vendors have bios updates to mitigate this. most dont. they are working on some workaround for this tho https://bugzilla.kernel.org/show_bug.cgi?id=216989 , i myself dont use the tpm for anything and simply disabled it in bios. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465444] xwayland firefox tab doesnt appear unless mouse over
https://bugs.kde.org/show_bug.cgi?id=465444 --- Comment #4 from Tom Englund --- yeah tested on amdgpu laptop, same deal there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465444] xwayland firefox tab doesnt appear unless mouse over
https://bugs.kde.org/show_bug.cgi?id=465444 --- Comment #3 from Tom Englund --- i guess its worth mentioning nvidia is a bit flawed regarding xwayland too, https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317 but that should only make it misrender i guess? and not, not finish the drag and drop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465444] xwayland firefox tab doesnt appear unless mouse over
https://bugs.kde.org/show_bug.cgi?id=465444 --- Comment #2 from Tom Englund --- (In reply to Nate Graham from comment #1) > Works for me when Firefox is in native Wayland mode. Does it also work for > you? yeah it does, only xwayland mode it does this behaviour. however having some weird issues with running it wayland mode because of nvidia and dgpu. so thought id report it atleast, doesnt seem like it should behave like this :p , or is it perhaps some flaw of firefox itself? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465444] New: xwayland firefox tab doesnt appear unless mouse over
https://bugs.kde.org/show_bug.cgi?id=465444 Bug ID: 465444 Summary: xwayland firefox tab doesnt appear unless mouse over Classification: Plasma Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- dragging a tab from the "tab bar" in firefox and dropping it on the desktop when firefox runs in xwayland shows an "small preview window" that gets stuck on the desktop and unless you mouse over the preview it doesnt finish and if you are doing it to slow it seems to cancel the drag and drop. screenshot of the "preview window" https://i.imgur.com/YVNcITM.png STEPS TO REPRODUCE 1. run firefox in xwayland 2. drag a tab and drop it on the desktop. 3. "ghost window" gets stuck, mouse over it fast enough and the new window gets created. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 30,7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Acer Product Name: Nitro AN515-45 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465416] New: when second monitor powers off/on virtual desktop pager doesnt update
https://bugs.kde.org/show_bug.cgi?id=465416 Bug ID: 465416 Summary: when second monitor powers off/on virtual desktop pager doesnt update Classification: Plasma Product: kwin Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- when second hdmi connected monitors enters dpms it "powers off" as in kwin thinks its unplugged. does the same on windows so probably monitor itself being quirky. however when it powers on windows remembers its position and moves back but the virtual pager in the panel doesnt update and show the windows until i move/resize them. STEPS TO REPRODUCE 1. use dual monitors and virtual desktops. 2. open windows on both monitors. 3. turn off second monitor, then turn it on and watch it restore positions. 4. virtual desktop pager, doesnt update until you do a move or resize of the window on the second monitor. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 30,7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Acer Product Name: Nitro AN515-45 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465171] New: scaling changes mouse acceleration/sensitivity
https://bugs.kde.org/show_bug.cgi?id=465171 Bug ID: 465171 Summary: scaling changes mouse acceleration/sensitivity Classification: Plasma Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- mouse sensitivity gets changed with scaling, setting it to 150% i assume it now means im moving 1.5 pixels per same distance moved on touchpad or mouse as if i didnt scale it. it means acceleration profile is changed with its ramp up time etc also feels like its more "unprecise". i guess this is a sideffect of scaling when the idea was simply to enlarge my fonts. SUMMARY with scaling set to 150%, mouse sensitivity changed. STEPS TO REPRODUCE 1. Change the scaling and move mouse around OBSERVED RESULT changed sensitivity and acceleration. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 30,7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Acer Product Name: Nitro AN515-45 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465169] New: various artifacts with fractional scaling on GUI
https://bugs.kde.org/show_bug.cgi?id=465169 Bug ID: 465169 Summary: various artifacts with fractional scaling on GUI Classification: Plasma Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- various artifacts appears on GUI when using 150% scaling at random when moving around or doing things. https://i.imgur.com/57xOnuY.jpg see below the "LSP Client" and at the end of the dot in the text. SUMMARY with scaling set to 150% various artifacts appears randomly over various components. STEPS TO REPRODUCE 1. Change the scaling and open dolphin/kate or similiar move it around or resize and it appears. OBSERVED RESULT artifacts SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 30,7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Acer Product Name: Nitro AN515-45 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465168] New: blurry text with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=465168 Bug ID: 465168 Summary: blurry text with fractional scaling Classification: Plasma Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- since the move seems to be going from force font dpi to display scaling, i got to report it makes fonts and various components blurry as of currently on plasma 5.27 beta. this is with forcing font dpi to 144 https://i.imgur.com/0ZaR2WG.png , and this is with scaling 150% which makes them roughly the same size. https://i.imgur.com/p6U5CoT.png SUMMARY with fractional scaling instead of forcing font dpi you get blurry text all over, most noticeably on the desktop icons on the screenshots. STEPS TO REPRODUCE 1. Change the scaling and compare text with force font dpi. OBSERVED RESULT blurry text EXPECTED RESULT crisp fonts. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 30,7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Acer Product Name: Nitro AN515-45 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465167] New: mouse artifacts with display scaling
https://bugs.kde.org/show_bug.cgi?id=465167 Bug ID: 465167 Summary: mouse artifacts with display scaling Classification: Plasma Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- mouse artifacts and clips when using fractional scaling. SUMMARY I'm using fractional scaling 150% on wayland. when you move around the mouse it "clips/artifacts" took pictures of it happening. https://i.imgur.com/GdPhMw3.jpg and https://i.imgur.com/FNFSTmM.jpg STEPS TO REPRODUCE 1. Change the scaling move mouse around, most noticeable on a dark background. OBSERVED RESULT clipping and artifacts EXPECTED RESULT shouldnt clip and artifact. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 30,7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Acer Product Name: Nitro AN515-45 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464940] 1px weird border above panel on some sizes of panel
https://bugs.kde.org/show_bug.cgi?id=464940 Tom Englund changed: What|Removed |Added CC||tomenglun...@gmail.com --- Comment #7 from Tom Englund --- happends for me aswell on a 2560x1440 27" monitor when i scale it to 150% took a picture of it. https://i.imgur.com/Q1e8Tka.jpg this is on 5.27 beta. i would guess some rounding error. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439332] Ghost windows and popups
https://bugs.kde.org/show_bug.cgi?id=439332 --- Comment #26 from Tom Englund --- easiest way to trigger it is simply start dragging a window and press alt + f4 while doing so to close it, that will leave a ghost window around. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464541] qtcreator tooltips/popups doesnt follow mouse movement if already shown
https://bugs.kde.org/show_bug.cgi?id=464541 --- Comment #2 from Tom Englund --- (In reply to Vlad Zahorodnii from comment #1) > iirc xdg-popup repositioning was added after 5.15 release. qtwayland needs > to gain support for xdg_popup.reposition. Can you file a Qt bug report > please and leave a link here? seems to exist one already, so il leave it at that then :) https://bugreports.qt.io/browse/QTBUG-110425 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464541] New: qtcreator tooltips/popups doesnt follow mouse movement if already shown
https://bugs.kde.org/show_bug.cgi?id=464541 Bug ID: 464541 Summary: qtcreator tooltips/popups doesnt follow mouse movement if already shown Classification: Plasma Product: kwin Version: git master Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- SUMMARY popups/tooltips? in qtcreator doesnt follow the mouse. if i hover one file it shows the filepath, if i move the mouse over to another item and continue to traverse the file list the popup stays in the same place as the first shown but edits the text. STEPS TO REPRODUCE 1. open qtcreator and a project with a few files 2. hoover the mouse over one file until the tooltip/popup shows 3. begin move the mouse down over other files so the tooltip/popup changes OBSERVED RESULT popup changes text but does not move. EXPECTED RESULT on x11 it does follow the mouse when hoovering other items. it can be "moved" if you simply close the popup by not hoovering anything and then approach a new item. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.5 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461897] Mouse Pointer leaves duplicate on second monitor when moving quickly between monitors
https://bugs.kde.org/show_bug.cgi?id=461897 Tom Englund changed: What|Removed |Added CC||tomenglun...@gmail.com --- Comment #1 from Tom Englund --- happends for me aswell. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Graphics Platform: Wayland Graphics Processor: AMD 5800h cezanne + nvidia 3060 dgpu NVIDIA Driver Version: 525.78.01 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463299] New: on X11 closing a window mid drag leaves a blurred transclucent ghost window
https://bugs.kde.org/show_bug.cgi?id=463299 Bug ID: 463299 Summary: on X11 closing a window mid drag leaves a blurred transclucent ghost window Classification: Plasma Product: kwin Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- SUMMARY *** on X11 if you drag a window and while doing so press alt + f4 you get a "ghost window" of the contents left on the desktop that doesnt vanish until you restart the compositor. this is me done it 4 times in a row as an example https://i.imgur.com/nxaDPxD.png *** STEPS TO REPRODUCE 1. drag the window and observe it become blurred and transclucent 2. press alt + f4 meanwhile dragging 3. application exits but a "ghost window" is left permanent on the desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.4 (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.17.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462996] Windows do not stay on the virtual desktop they are on
https://bugs.kde.org/show_bug.cgi?id=462996 Tom Englund changed: What|Removed |Added CC||tomenglun...@gmail.com --- Comment #5 from Tom Englund --- i personally always have firefox on the 4th virtual desktop, for now i worked around this by making a special application setting/rule that always forces it to be on the 4th virtual desktop. now it doesnt move around when i open urls in other virtual desktops. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449518] New: kwin_wayland doesnt focus window when right clicking decoration/window border
https://bugs.kde.org/show_bug.cgi?id=449518 Bug ID: 449518 Summary: kwin_wayland doesnt focus window when right clicking decoration/window border Product: kwin Version: 5.23.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tomenglun...@gmail.com Target Milestone: --- SUMMARY *** focusing something else and then right clicking the window border/title/decoration the focus doesnt change to the window but the context menu do appear. STEPS TO REPRODUCE 1. launch firefox as a xwayland client. 2. click the desktop or another window. 3. right click the border/title/decoration and the menu appears but firefox doesnt get focused. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399234] Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 Tom Englund changed: What|Removed |Added CC||tomenglun...@gmail.com --- Comment #11 from Tom Englund --- still happends with plasma 5.15.2 and wine staging 4.2 on archlinux -- You are receiving this mail because: You are watching all bug changes.
