[plasmashell] [Bug 460895] plasmashell process uses all available RAM and several UI elements freeze
https://bugs.kde.org/show_bug.cgi?id=460895 Marcelo Bossoni changed: What|Removed |Added CC||mmboss...@gmail.com --- Comment #16 from Marcelo Bossoni --- I've seen the exact behavior described in 462399... After deleting one of the notifications my shell froze and started eating memory until kernel said it was enough jun 02 10:47:56 URSO kernel: Out of memory: Killed process 1038 (plasmashell) total-vm:35975184kB, anon-rss:23749760kB, file-rss:828kB, shmem-rss:0kB, UID:1000 pgtables:55704kB oom_score_adj:200 I have 32gb of ram... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #17 from Marcelo Bossoni --- Your best bet: upgrade do plasma 6 OR disable thumbnails on taskbar/ I believe this has to do with nvidia + thumbnailer + opengl quirks on nvidia -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486693] Kwin coredumps in KWin::Workspace::raiseWindow() using Ctrl + Alt + A on discord
https://bugs.kde.org/show_bug.cgi?id=486693
--- Comment #5 from Marcelo Bossoni ---
Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0
--xwayland-fd 8 --xwayl'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x77c121640d74 in KWin::Workspace::raiseWindow (this=0x622554311fa0,
window=0x622555f1bdc0,
nogroup=) at
/usr/src/debug/kwin/kwin-6.0.4.1/src/layers.cpp:365
365 if (!nogroup && window->isTransient()) {
[Current thread is 1 (Thread 0x77c11994ff00 (LWP 839))]
(gdb) bt
#0 0x77c121640d74 in KWin::Workspace::raiseWindow
(this=0x622554311fa0, window=0x622555f1bdc0, nogroup=)
at /usr/src/debug/kwin/kwin-6.0.4.1/src/layers.cpp:365
#1 0x77c12155e917 in KWin::Workspace::activateWindow
(force=false, window=0x622555f1bdc0, this=0x622554311fa0)
at /usr/src/debug/kwin/kwin-6.0.4.1/src/activation.cpp:297
#2 KWin::Workspace::activateWindow (this=0x622554311fa0,
window=0x622555f1bdc0, force=)
at /usr/src/debug/kwin/kwin-6.0.4.1/src/activation.cpp:282
#3 0x77c11ed9b57f in QtPrivate::QSlotObjectBase::call
(a=0x7fffc19650b0, r=0x622554311fa0, this=0x6225544816c0, this=, r=, a=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:469
#4 doActivate (sender=0x622554556470, signal_index=7,
argv=0x7fffc19650b0)
at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:4078
#5 0x77c11f701eda in QAction::triggered (_t1=,
this=0x622554556470)
at
/usr/src/debug/qt6-base/build/src/gui/Gui_autogen/include/moc_qaction.cpp:480
#6 QAction::activate (this=0x622554556470, event=)
at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qaction.cpp:1102
#7 0x77c11ed9b57f in QtPrivate::QSlotObjectBase::call
(a=0x7fffc1965240, r=0x77c12056bcc0
<_ZZN13QGlobalStaticIN14QtGlobalStatic6HolderIN12_GLOBAL__N_116Q_QGS_s_instance8instanceEvE6holder.lto_priv.0>,
this=0x622554729c30, this=, r=, a=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:469
#8 doActivate (sender=0x622554731470, signal_index=3,
argv=0x7fffc1965240)
at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:4078
#9 0x77c12055f1e0 in
OrgKdeKglobalaccelComponentInterface::globalShortcutPressed
(_t3=, _t2=, _t1=,
this=)
at
/usr/src/debug/kglobalaccel/build/src/moc_kglobalaccel_component_interface.cpp:255
#10 OrgKdeKglobalaccelComponentInterface::qt_static_metacall
(_o=_o@entry=0x622554731470, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=0, _a=_a@entry=0x7fffc1965418) at
/usr/src/debug/kglobalaccel/build/src/moc_kglobalaccel_component_interface.cpp:165
#11 0x77c12055fcc0 in OrgKdeKglobalaccelComponentInterface::qt_metacall
(this=0x622554731470, _c=QMetaObject::InvokeMetaMethod, _id=0,
_a=0x7fffc1965418)
at
/usr/src/debug/kglobalaccel/build/src/moc_kglobalaccel_component_interface.cpp:236
#12 0x77c11fbe7def in QDBusConnectionPrivate::deliverCall
(this=0x77c114001690, object=0x622554731470, msg=..., metaTypes=, slotIdx=5)
at /usr/src/debug/qt6-base/qtbase/src/dbus/qdbusintegrator.cpp:1007
#13 0x77c11ed8c147 in QObject::event (this=0x622554731470,
e=0x6225559056e0)
at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1446
#14 0x77c11fefc44d in QApplicationPrivate::notify_helper
(this=, receiver=0x622554731470, e=0x6225559056e0)
at /usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:3287
#15 0x77c11ed3fe18 in QCoreApplication::notifyInternal2
(receiver=0x622554731470, event=event@entry=0x6225559056e0)
at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1142
#16 0x77c11ed401d2 in QCoreApplication::sendEvent (event=0x6225559056e0,
receiver=)
at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1583
#17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x622553f98460)
at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1940
#18 0x77c11eeb9cbd in QEventDispatcherUNIX::processEvents
(this=0x622554036b10, flags=flags@entry=...)
at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventdispatcher_unix.cpp:415
#19 0x77c11f7e12b3 in QUnixEventDispatcherQPA::processEvents
(this=, flags=...)
at
/usr/src/debug/qt6-base/qtbase/src/gui/platform/unix/qunixeventdispatcher.cpp:27
#20 0x77c11ed48350 in QEventLoop::processEvents (flags=...,
this=0x7fffc1965980)
at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventloop.cpp:100
#21 QEventLoop::exec (this=0x7fffc1965980, flags=...)
at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventloop.cpp:182
#22 0x77c11ed43c1d in QCoreApplication::exec ()
at /usr/src/debug/qt6-base/qtbase/src/corelib/global/qflags.h:74
#23 0x77c11fef863a in QApplication::exec ()
at /usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:2555
#24 0x6225523ccdee in
[kwin] [Bug 486693] Kwin coredumps in KWin::Workspace::raiseWindow() using Ctrl + Alt + A on discord
https://bugs.kde.org/show_bug.cgi?id=486693 --- Comment #4 from Marcelo Bossoni --- Nothing to be honest It is just KDE default that supposedly is Ctrl+Alt+A Activate Window Demanding Attention At least according to this site https://docs.kde.org/stable5/en/khelpcenter/fundamentals/kbd.html -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486693] Kwin coredump using Ctrl + Alt + A on discord
https://bugs.kde.org/show_bug.cgi?id=486693 --- Comment #2 from Marcelo Bossoni --- Is that what you were expecting? Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayl'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f1fa3240d74 in KWin::Workspace::raiseWindow(KWin::Window*, bool) () from /usr/lib/libkwin.so.6 [Current thread is 1 (Thread 0x7f1f9b61aec0 (LWP 2392))] (gdb) bt #0 0x7f1fa3240d74 in KWin::Workspace::raiseWindow(KWin::Window*, bool) () at /usr/lib/libkwin.so.6 #1 0x7f1fa315e917 in KWin::Workspace::activateWindow(KWin::Window*, bool) () at /usr/lib/libkwin.so.6 #2 0x7f1fa0b97549 in ??? () at /usr/lib/libQt6Core.so.6 #3 0x7f1fa14f4087 in QAction::activate(QAction::ActionEvent) () at /usr/lib/libQt6Gui.so.6 #4 0x7f1fa0b97549 in ??? () at /usr/lib/libQt6Core.so.6 #5 0x7f1fa2ec31e0 in ??? () at /usr/lib/libKF6GlobalAccel.so.6 #6 0x7f1fa2ec3cc0 in ??? () at /usr/lib/libKF6GlobalAccel.so.6 #7 0x7f1fa18c408f in ??? () at /usr/lib/libQt6DBus.so.6 #8 0x7f1fa0b88324 in QObject::event(QEvent*) () at /usr/lib/libQt6Core.so.6 #9 0x7f1fa1afbfcb in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6 #10 0x7f1fa0b3daa8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6 #11 0x7f1fa0b3de34 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6 #12 0x7f1fa0cb1abb in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt6Core.so.6 #13 0x7f1fa15c14e2 in QUnixEventDispatcherQPA::processEvents(QFlags) () at /usr/lib/libQt6Gui.so.6 #14 0x7f1fa0b45c3e in QEventLoop::exec(QFlags) () at /usr/lib/libQt6Core.so.6 #15 0x7f1fa0b416a8 in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6 #16 0x63cd0a24cdee in ??? () #17 0x7f1fa0441d4a in ??? () at /usr/lib/libc.so.6 #18 0x7f1fa0441e0c in __libc_start_main () at /usr/lib/libc.so.6 #19 0x63cd0a252df5 in ??? () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486693] New: Kwin coredump using Ctrl + Alt + A on discord
https://bugs.kde.org/show_bug.cgi?id=486693 Bug ID: 486693 Summary: Kwin coredump using Ctrl + Alt + A on discord Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- SUMMARY I was playing with discord and trying to hope for global shortcuts on wayland, but ended up facing this crash STEPS TO REPRODUCE 1. Run discord in wayland mode (ozone platform + wayland) - this is my full launch for the record discord --enable-features=UseOzonePlatform,WaylandWindowDecorations,VaapiVideoDecoder --ozone-platform=wayland --ignore-gpu-blocklist --use-gl=desktop --enable-gpu-rasterization --enable-zero-copy --disable-gpu-sandbox 2. Discord opens in friends tab 3. Make sure one of the servers have unread messages 4. Open discord settings 5. Ctrl + Alt + A OBSERVED RESULT Kwin crashes EXPECTED RESULT no crashes SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-1-cachyos (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6750 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 ADDITIONAL INFORMATION Stack trace of thread 42406: #0 0x6ffd2bf442b4 _ZN4KWin6Window15cancelAutoRaiseEv (libkwin.s> #1 0x6ffd2be40cc9 _ZN4KWin9Workspace11raiseWindowEPNS_6WindowEb> #2 0x6ffd2bd5e917 _ZN4KWin9Workspace14activateWindowEPNS_6Windo> #3 0x6ffd29797549 n/a (libQt6Core.so.6 + 0x197549) #4 0x6ffd2a0f4087 _ZN7QAction8activateENS_11ActionEventE (libQt> #5 0x6ffd29797549 n/a (libQt6Core.so.6 + 0x197549) #6 0x6ffd2b3f31e0 n/a (libKF6GlobalAccel.so.6 + 0x241e0) #7 0x6ffd2b3f3cc0 n/a (libKF6GlobalAccel.so.6 + 0x24cc0) #8 0x6ffd2a4c408f n/a (libQt6DBus.so.6 + 0x3b08f) #9 0x6ffd29788324 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 +> #10 0x6ffd2a6fbfcb _ZN19QApplicationPrivate13notify_helperEP7QOb> #11 0x6ffd2973daa8 _ZN16QCoreApplication15notifyInternal2EP7QObj> #12 0x6ffd2973de34 _ZN23QCoreApplicationPrivate16sendPostedEvent> #13 0x6ffd298b1abb _ZN20QEventDispatcherUNIX13processEventsE6QFl> #14 0x6ffd2a1c14e2 _ZN23QUnixEventDispatcherQPA13processEventsE6> #15 0x6ffd29745c3e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEven> #16 0x6ffd297416a8 _ZN16QCoreApplication4execEv (libQt6Core.so.6> #17 0x5a49f84a5dee n/a (kwin_wayland + 0x3adee) #18 0x6ffd29041d4a n/a (libc.so.6 + 0x25d4a) #19 0x6ffd29041e0c __libc_start_main (libc.so.6 + 0x25e0c) #20 0x5a49f84abdf5 n/a (kwin_wayland + 0x40df5) Stack trace of thread 42413: #0 0x6ffd290a68d9 n/a (libc.so.6 + 0x8a8d9) #1 0x6ffd290a9299 pthread_cond_wait (libc.so.6 + 0x8d299) #2 0x6ffd20c863fc n/a (radeonsi_dri.so + 0x863fc) #3 0x6ffd20c9ec2c n/a (radeonsi_dri.so + 0x9ec2c) #4 0x6ffd290aa1cf n/a (libc.so.6 + 0x8e1cf) #5 0x6ffd2912b6ec n/a (libc.so.6 + 0x10f6ec) Stack trace of thread 42411: #0 0x6ffd2911d9ed __poll (libc.so.6 + 0x1019ed) #1 0x6ffd2819f306 n/a (libglib-2.0.so.0 + 0xb9306) #2 0x6ffd2813f712 g_main_context_iteration
[xdg-desktop-portal-kde] [Bug 481290] Steam in home streaming/Steam link shows a black screen on wayland session
https://bugs.kde.org/show_bug.cgi?id=481290 --- Comment #2 from Marcelo Bossoni --- Apparently it is working with steam beta. Need to double check that on other plasma install -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 485697] New: Screen dialog allow restore on future sessions doesn't work
https://bugs.kde.org/show_bug.cgi?id=485697 Bug ID: 485697 Summary: Screen dialog allow restore on future sessions doesn't work Classification: Plasma Product: xdg-desktop-portal-kde Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mmboss...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY When selecting a screen to share dialog have a checkbox for "Allow restore on future sessions" (sorry I'm translating back from my language) and it is selected by default but it doesn't work STEPS TO REPRODUCE 1. launch steam with -pipewire 2. select a screen and make sure Allow restore checkbox is marked 3. exit steam and launch steam again with -pipewire OBSERVED RESULT Screen picker dialog is shown again EXPECTED RESULT Screen picker dialog is not shown... As an addendum, KDE lacks any tools to revoke those permissions As a second addendum, this seems to also be true for KDEConnect remote input plugin SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-cachyos (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6750 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 485695] New: Screen select screen doesn't enable click if checkbox is clicked
https://bugs.kde.org/show_bug.cgi?id=485695 Bug ID: 485695 Summary: Screen select screen doesn't enable click if checkbox is clicked Classification: Plasma Product: xdg-desktop-portal-kde Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mmboss...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Start steam from command line with steam -pipewire 2. When the screen picker dialog show up, click on the checkbox instead of the screen 3. Check OK button OBSERVED RESULT OK Button doesn't become enabled EXPECTED RESULT OK Button is enabled SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-cachyos (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6750 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483049] New: Skype flatpak systray icon shown as generic file instead of skype icon
https://bugs.kde.org/show_bug.cgi?id=483049 Bug ID: 483049 Summary: Skype flatpak systray icon shown as generic file instead of skype icon Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: mmboss...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY System tray is showing a generic file icon instead of the expected skype icon STEPS TO REPRODUCE 1. Install skype from flatpak 2. Run skype OBSERVED RESULT Generic file icon is shown on systray EXPECTED RESULT Skype icon is shown on systray SOFTWARE/OS VERSIONS Operating System: Nobara Linux 39 KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-201.fsync.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6750 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 482597] New: Unable to pair headphone (mi buds)
https://bugs.kde.org/show_bug.cgi?id=482597 Bug ID: 482597 Summary: Unable to pair headphone (mi buds) Classification: Plasma Product: Bluedevil Version: 6.0.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wizard Assignee: now...@gmail.com Reporter: mmboss...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I'm unable to pair my mibuds using KDE wizard. It always fail. STEPS TO REPRODUCE 1. Put headphone into pairing state 2. Select MiBuds on wizard 3. Wait OBSERVED RESULT Pairing fail EXPECTED RESULT Pairing succeed SOFTWARE/OS VERSIONS Operating System: Nobara Linux 39 KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-201.fsync.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6750 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 ADDITIONAL INFORMATION I can only pair them through bluetoothctl when I set both pairable and discoverable to on Other than that `pair` command would fail as well The same bug is also reproducible on arch -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 481290] New: Steam in home streaming/Steam link shows a black screen on wayland session
https://bugs.kde.org/show_bug.cgi?id=481290 Bug ID: 481290 Summary: Steam in home streaming/Steam link shows a black screen on wayland session Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mmboss...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY When running steam under wayland session (host) steam link only shows a black screen (at least on an android device client) STEPS TO REPRODUCE 1. Start steam with either -pipewire or -pipewire-dmabuf 2. When requested by portal, choose a monitor to share 3. Run steamlink on android device and start streaming OBSERVED RESULT Black screen on client, audio and input works fine EXPECTED RESULT Steam is properly shown on client device SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-1-cachyos (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6750 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 ADDITIONAL INFORMATION Notice I've opened this to KDE because I've tested on Gnome (opensuse tumbleweed) and there it works fine Also tested on Fedora and got the same problem with KDE 5.27.10 After streaming starts, terminal get flooded with CDesktopCapturePipeWire: Couldn't import dmabuf: Function not implemented CDesktopCapturePipeWire: Failed to mmap memory: Operation not permitted CDesktopCapturePipeWire: Couldn't get image data Steam logs: CDesktopCapturePipeWire: Opening DRM render node /dev/dri/renderD128 CDesktopCapturePipeWire: Start signal received. BuildCompleteAppOverviewChange: 502 apps RegisterForAppOverview 1: 15ms RegisterForAppOverview 2: 16ms tid(5852) burning pthread_key_t == 0 so we never use it 02/13 09:14:06 Init: Installing breakpad exception handler for appid(steam_monitor)/version(20240113005129)/tid(5852) 02/13 09:14:06 Init: Installing breakpad exception handler for appid(steam_monitor)/version(1.0)/tid(5852) Streaming initialized and listening on port 27031 CLIENT: Sending HID device /11fb/-1 Mobile Touch Control at touch://0 Streaming started to Motorola motorola edge 20 pro Android 13 at 192.168.15.2:47022, audio channels = 2, MTU = 1468 Streaming quality: k_EStreamQualityBalanced Streaming bitrate: Automatic Device form factor: phone Maximum capture: 2400x1080 60.00 FPS Video Streaming: enabled Audio Streaming: enabled Input Streaming: enabled = Game: UNKNOWN (0) Setting target bitrate to 15000 Kbit/s, burst bitrate is 75000 Kbit/s GameScope focus changed to appID 0 Window title set to Steam — Modo Big Picture Changing record window: 0x1a00073 >>> Starting desktop stream SynchronizeClientState(): setting capture size 1920x1080 SynchronizeClientState(): setting title to Steam — Modo Big Picture SynchronizeClientState(): setting icon 128x128 SynchronizeClientState(): setting activity to k_EStreamActivityDesktop: Steam Controller Configs - Desktop Recording system audio PulseAudio: Sink alsa_output.pci-_2a_00.4.analog-stereo is default PulseAudio: Adding sink[0] alsa_output.pci-_28_00.1.hdmi-stereo with priority 1, monitor is alsa_output.pci-_28_00.1.hdmi-stereo.monitor PulseAudio: Adding sink[1] alsa_output.pci-_2a_00.4.analog-stereo with priority 7, monitor is alsa_output.pci-_2a_00.4.analog-stereo.monitor PulseAudio: Recording on device alsa_output.pci-_2a_00.4.analog-stereo.monitor CDesktopCapturePipeWire: PipeWire stream state changed to connecting CDesktopCapturePipeWire: PipeWire stream state changed to paused CDesktopCapturePipeWire: PipeWire stream format changed (size: 1920x1080, format 8, stride 7680, size 8294400, dmabuf: 1) CDesktopCapturePipeWire: PipeWire stream format changed (size: 1920x1080, format 8, stride 7680, size 8294400, dmabuf: 1) CDesktopCapturePipeWire: PipeWire stream state changed to streaming PulseAudio: Connected to device alsa_output.pci-_2a_00.4.analog-stereo.monitor (1, not suspended). PulseAudio: Using sample spec 's16le 2ch 48000Hz', channel map 'front-left,front-right'. >>> Switching video stream from NONE to Desktop_MovieStream BuildCompleteAppOverviewChange: 502 apps CDesktopCapturePipeWire: Couldn't import dmabuf: Function not implemented CDesktopCapturePipeWire: Failed to mmap memory: Operation not permitted CDesktopCapturePipeWire: Couldn't get image data CDesktopCapturePipeWire: PipeWire stream format changed (size: 1920x1080, format 8, stride 7680, size 8294400, dmabuf: 1)
[konsole] [Bug 478804] New: Plugins are always shown on start and unable to keep them disabled/hidden
https://bugs.kde.org/show_bug.cgi?id=478804 Bug ID: 478804 Summary: Plugins are always shown on start and unable to keep them disabled/hidden Classification: Applications Product: konsole Version: 24.01.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugins Assignee: konsole-de...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- SUMMARY When opening konsole quick commands and ssh plugin views are loaded but, even if I closed them, they will show again on next launch and there is no visible way to configure to keep them hidden SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch with KDE beta2 (available in About System) KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247 Qt Version: 6.7.0beta1-1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477912] Cpu/case fan speed sensors are not available anymore
https://bugs.kde.org/show_bug.cgi?id=477912 Marcelo Bossoni changed: What|Removed |Added Ever confirmed|0 |1 CC||mmboss...@gmail.com Status|REPORTED|CONFIRMED --- Comment #2 from Marcelo Bossoni --- Just giving my "Same here" as well. I can see only 3 sensors instead of tons that I have (zenpower + nct6795 + nvme) and, for the ones that I can see, they don't yield any value on plasmoid. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475808] New: [FeatureRequest] Implement Explicit Sync for xwayland
https://bugs.kde.org/show_bug.cgi?id=475808 Bug ID: 475808 Summary: [FeatureRequest] Implement Explicit Sync for xwayland Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- SUMMARY New NVIDIA beta drivers are unusable with xwayland apps (mainly games) on wayland due to them kind of requiring explicit synchronization now. Since Plasma 6 wants to be Wayland first it is paramount for explicit sync to be implemented. NVIDIA have the biggest market share on gaming setups, unfortunately. STEPS TO REPRODUCE 1. Use new 545 drivers in a wayland session and a monitor with high refresh rate (144hz+) 2. Play a demanding game that renders at 70fps 3. Open discord in xwayland mode OBSERVED RESULT Check all kind of weird stuff happening, like flickering on screen and old frames being drawn. Check discord in xwayland mode also have the famous "rubberbanding" EXPECTED RESULT Game is smooth discord doesn't have the rubberbanding effect Some links https://forums.developer.nvidia.com/t/feature-g-sync-freesync-under-wayland-session/220822/46 https://forums.developer.nvidia.com/t/new-545-beta-only-renders-update-game-if-window-is-unfocused-otherwise-it-will-have-0-fps/269759 ADDITIONAL INFORMATION https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/90 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967 https://gitlab.freedesktop.org/xorg/proto/xorgproto/-/merge_requests/59 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474918] New: Gamescope-git complains about missing wp_presentation/presentation-time support
https://bugs.kde.org/show_bug.cgi?id=474918 Bug ID: 474918 Summary: Gamescope-git complains about missing wp_presentation/presentation-time support Classification: Plasma Product: kwin Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- SUMMARY Tried to run gamescope git today and it complained about missing functionality in KDE STEPS TO REPRODUCE 1. Run KDE 2. Try to run gamescope from git branch OBSERVED RESULT gamescope is aborted with the following message Your Wayland compositor does NOT support wp_presentation/presentation-time which is required for VK_KHR_present_wait and VK_KHR_present_id which is needed for Gamescope to function. EXPECTED RESULT Gamescope works Operating System: Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.5-2-cachyos (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466580] [NVIDIA] Panel freezes when rearranging or unpinning on icons only task manager widget
https://bugs.kde.org/show_bug.cgi?id=466580 --- Comment #8 from Marcelo Bossoni --- Yes, it does. In fact this is what I've being doing lately. But thumbnails are so nice... Fun fact is that on 5.27.6, if __GL_SYNC_TO_VBLANK=0 was set, the bug was another one (stutter whenever a taskbar item was hovered) With 5.27.7 I don't get stuttering anymore, but it now freezes no matter the value of __GL_SYNC_TO_VBLANK. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466580] [NVIDIA] Panel freezes when rearranging or unpinning on icons only task manager widget
https://bugs.kde.org/show_bug.cgi?id=466580 Marcelo Bossoni changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Marcelo Bossoni --- Another easy way of reproducing it: Hover on some task on task manager Wait for the window preview to show up Quickly alt tab couple of times (I have cover task switcher) Alt+Tab must be quick so cover task switcher is not able to show up, but you just switch tasks Panel will stop updating/refreshing after a few tabs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464530] Plasma shell freezes when cycling through task manager when window previews are being shown (hover or on grouped)
https://bugs.kde.org/show_bug.cgi?id=464530 --- Comment #15 from Marcelo Bossoni --- Post Mortem comment: This is NOT a duplicate of bug 450248 This seems to be a NVIDIA thing. I end up finding the root cause. I have __GL_SYNC_TO_VBLANK=0 set in my variables and that end up causing the issue. Removing the flag fixed the bug for me. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 470474] New: new nvidia beta driver (535 series) not showing statistics
https://bugs.kde.org/show_bug.cgi?id=470474 Bug ID: 470474 Summary: new nvidia beta driver (535 series) not showing statistics Classification: Applications Product: plasma-systemmonitor Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: mmboss...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY I've installed new nvidia drivers and card stats reporting seems to be broken again :( STEPS TO REPRODUCE 1. Install new nvidia 535 driver OBSERVED RESULT All stats showing 0 as result (temp, usage, frequency...) EXPECTED RESULT All statistics properly shown 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-zen3-xanmod1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 ADDITIONAL INFORMATION nvidia-smi dmon -s pucm # gpupwr gtemp mtemp smmemencdecjpgofa mclk pclk fb bar1 ccpm # Idx W C C % % % % % %MHz MHz MB MB MB 0 11 48 - 0 5 0 0 - - 405139 512 15 0 0 11 48 - 0 5 0 0 - - 405139 512 15 0 0 11 48 - 0 5 0 0 - - 405139 504 15 0 0 11 48 - 0 5 0 0 - - 405139 504 15 0 0 11 48 - 0 5 0 0 - - 405139 504 15 0 0 11 48 - 0 5 0 0 - - 405139 504 15 0 0 11 48 - 0 5 0 0 - - 405139 496 15 0 0 11 47 - 0 5 0 0 - - 405139 496 15 0 0 11 47 - 0 5 0 0 - - 405139 496 15 0 0 11 47 - 0 5 0 0 - - 405139 488 15 0 0 11 47 - 0 5 0 0 - - 405139 488 15 0 0 11 47 - 0 5 0 0 - - 405139 488 15 0 0 11 47 - 0 6 0 0 - - 405139 480 15 0 0 11 47 - 0 5 0 0 - - 405139 480 15 0 0 11 47 - 0 5 0 0 - - 405139 480 15 0 0 11 47 - 0 5 0 0 - - 405139 480 15 0 0 11 47 - 0 5 0 0 - - 405139 472 15 0 0 11 47 - 7 11 0 0 - - 405139 586 15 0 0 13 47 - 1 6 0 0 - - 405139 586 15 0 0 12 47 - 0 6 0 0 - - 405139 586 15 0 0 12 47 - 0 5 0 0 - - 405139 578 15 0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469028] New: Kate no longer work as sudoedit editor and closes file immediately
https://bugs.kde.org/show_bug.cgi?id=469028 Bug ID: 469028 Summary: Kate no longer work as sudoedit editor and closes file immediately Classification: Applications Product: kate Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- SUMMARY Since new applications, kate closes the file being edited as sudoedit before being able to edit it STEPS TO REPRODUCE 1. Launch sudoedit with EDITOR=kate sudoedit /etc/somesystemfile OBSERVED RESULT Empty temp file is shown on editor instead of the file being edited and sudoedit tells file has no changes EXPECTED RESULT File being edited show on kate SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-1-cachyos-bore (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464530] Plasma shell freezes when cycling through task manager when window previews are being shown (hover or on grouped)
https://bugs.kde.org/show_bug.cgi?id=464530 --- Comment #13 from Marcelo Bossoni --- Still happening on 5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 Marcelo Bossoni changed: What|Removed |Added Ever confirmed|0 |1 Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #11 from Marcelo Bossoni --- Still happening on 5.27.4 Every time mouse is entering task manager icons it lags/skip frames -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467834] Screen doesn't turn on after long time sleeping (DPMS error)
https://bugs.kde.org/show_bug.cgi?id=467834 --- Comment #4 from Marcelo Bossoni --- Did a bit more digging... Apparently this is a problem with night colors on wayland since Nvidia doesn't support it. Apparently if night colors is applied while display is off make it unable to wake again https://invent.kde.org/plasma/kwin/-/merge_requests/3868 Try setting it to off -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467834] Screen doesn't turn on after long time sleeping (DPMS error)
https://bugs.kde.org/show_bug.cgi?id=467834 --- Comment #2 from Marcelo Bossoni --- Forgot to add the system info Operating System: Arch Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467834] Screen doesn't turn on after long time sleeping (DPMS error)
https://bugs.kde.org/show_bug.cgi?id=467834 --- Comment #1 from Marcelo Bossoni --- Created attachment 157606 --> https://bugs.kde.org/attachment.cgi?id=157606=edit systemd journal -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467834] New: Screen doesn't turn on after long time sleeping (DPMS error)
https://bugs.kde.org/show_bug.cgi?id=467834 Bug ID: 467834 Summary: Screen doesn't turn on after long time sleeping (DPMS error) Classification: Plasma Product: kwin Version: 5.27.3 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- SUMMARY I left computer idle for a long time (around 2 hours) and screen cannot turn on again. SSH from other machine worked fine. Switch to TTY didn't work Disconnecting/reconnecting the DP cable didn't work STEPS TO REPRODUCE 1. Use the computer 2. Leave the computer idle for a long time so that screen goes to sleep (and more after that) 3. Try to use the PC again OBSERVED RESULT Screen didn't come back EXPECTED RESULT Screen is turned on normally SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I stopped playing around 17:42 mar 26 17:42:15 URSO kwin_wayland[725]: kwin_core: could not find the toplevel to activate KWaylandServer::SurfaceInterface(0x55fcffd37d20) mar 26 17:42:15 URSO kwin_wayland[725]: kwin_core: could not find the toplevel to activate KWaylandServer::SurfaceInterface(0x55fcffd37d20) mar 26 17:40:18 URSO kwin_wayland[725]: kwin_core: XCB error: 3 (BadWindow), sequence: 22843, resource id: 90177651, major code: 129 (SHAPE), minor code: 6 (Input) Then near 20:00 kwin had some strange messages (that repeated for about 4 minutes) mar 26 20:00:19 URSO kwin_wayland[725]: kwin_wayland_drm: Failed to create gamma blob! Argumento inválido mar 26 20:00:12 URSO kwin_wayland[725]: kwin_wayland_drm: Failed to create gamma blob! Argumento inválido mar 26 20:00:06 URSO kwin_wayland[725]: kwin_wayland_drm: Failed to create gamma blob! Argumento inválido When I tried to use the PC again (20:13) mar 26 20:13:14 URSO kwin_wayland[725]: kwin_wayland_drm: Setting dpms mode failed! mar 26 20:13:14 URSO kwin_wayland[725]: kwin_wayland_drm: Setting dpms mode failed! mar 26 20:13:14 URSO kwin_wayland[725]: kwin_wayland_drm: Setting dpms mode failed! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #9 from Marcelo Bossoni --- For me even disabling previews doesn't work. It makes it better, but doesn't fix the problem. I also see some instances of failed thumbnailing when youtube is the page in focus (don't know if it is related to media controls though). If you minimize and restore some window (like konsole) using the taskbar button, things get worse. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #3 from Marcelo Bossoni --- Any way to disable the effect on user side just to test? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466580] [NVIDIA] Panel freezes when rearranging or unpinning on icons only task manager widget
https://bugs.kde.org/show_bug.cgi?id=466580 --- Comment #3 from Marcelo Bossoni --- For me just hovering the mouse back and forth through items cause it to stop updating. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466680] Plasma panel freezes and stopped updating after using a bit
https://bugs.kde.org/show_bug.cgi?id=466680 --- Comment #1 from Marcelo Bossoni --- Video evidence https://photos.app.goo.gl/fTy1QBQbtBrVgk1b7 This happens while trying to reproduce https://bugs.kde.org/show_bug.cgi?id=466681 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] New: Mouse is hitching/skipping frames when entering task manager area
https://bugs.kde.org/show_bug.cgi?id=466681 Bug ID: 466681 Summary: Mouse is hitching/skipping frames when entering task manager area Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mmboss...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY On plasma 5.27 series hovering mouse over task manager area make it stop for a while, like skipped frames STEPS TO REPRODUCE 1. Hover the mouse normally on some task to switch or show thumbnails OBSERVED RESULT Mouse skip some frames and get stuck for some time EXPECTED RESULT Mouse movement is smooth SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-273-tkg-pds (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 ADDITIONAL INFORMATION Video evidence https://photos.app.goo.gl/afaMvgyKtAxTZVXk6 And bug didn't happen on .26 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466680] New: Plasma panel freezes and stopped updating after using a bit
https://bugs.kde.org/show_bug.cgi?id=466680 Bug ID: 466680 Summary: Plasma panel freezes and stopped updating after using a bit Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mmboss...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY On 5.27 series, playing with task manager for a bit make plasma panel to stop updating. Need to change sizes to make it responsive again STEPS TO REPRODUCE 1. Just go through open tasks OBSERVED RESULT Shell freezes EXPECTED RESULT Shell works properly and newly open apps are shown on task manager SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-273-tkg-pds (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464763] Applets/widget placement get misplaced on every plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=464763 --- Comment #2 from Marcelo Bossoni --- Created attachment 155566 --> https://bugs.kde.org/attachment.cgi?id=155566=edit After a few reboots/plasmashell restarts -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464763] Applets/widget placement get misplaced on every plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=464763 --- Comment #1 from Marcelo Bossoni --- Created attachment 155565 --> https://bugs.kde.org/attachment.cgi?id=155565=edit How I setup my desktop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464763] New: Applets/widget placement get misplaced on every plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=464763 Bug ID: 464763 Summary: Applets/widget placement get misplaced on every plasmashell startup Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mmboss...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY I have an odd applet placement. Taskbar is on left, widgets/applets on the right close to each other. Every startup (or just restarting plasma shell) widget placement is shifted. This is on a single monitor STEPS TO REPRODUCE 1. put some widgets in a grid close to each other on the right of the screen 2. full panel on the left 3. restart plasmashell a few times (to simulate a fresh boot) OBSERVED RESULT Widgets are misplaced EXPECTED RESULT Widgets keep their positions 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-273-tkg-pds (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464530] Plasma shell freezes when cycling through task manager when window previews are being shown (hover or on grouped)
https://bugs.kde.org/show_bug.cgi?id=464530 --- Comment #4 from Marcelo Bossoni --- Just as a test, I've downgraded to 5.26.5 to rule out library updates and it worked fine. So this really seems a breakage from 5.27. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464530] Plasma shell freezes when cycling through task manager when window previews are being shown (hover or on grouped)
https://bugs.kde.org/show_bug.cgi?id=464530 Marcelo Bossoni changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Marcelo Bossoni --- [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". 0x7f9d6809c4b6 in ?? () from /usr/lib/libc.so.6 (gdb) bt #0 0x7f9d6809c4b6 in () at /usr/lib/libc.so.6 #1 0x7f9d6809ecd0 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f9d5e8b8f08 in () at /usr/lib/libEGL_nvidia.so.0 #3 0x7f9d5e8b9085 in () at /usr/lib/libEGL_nvidia.so.0 #4 0x7f9d5e88ffca in () at /usr/lib/libEGL_nvidia.so.0 #5 0x7f9d5e892a7d in () at /usr/lib/libEGL_nvidia.so.0 #6 0x7f9d5e89bdee in () at /usr/lib/libEGL_nvidia.so.0 #7 0x7f9d5e89c924 in () at /usr/lib/libEGL_nvidia.so.0 #8 0x7f9d5e89ca2e in () at /usr/lib/libEGL_nvidia.so.0 #9 0x7f9d5e847c23 in () at /usr/lib/libEGL_nvidia.so.0 #10 0x7f9d609f8dba in () at /usr/lib/libnvidia-egl-wayland.so.1 #11 0x7f9d5e8a878e in () at /usr/lib/libEGL_nvidia.so.0 #12 0x7f9d5e847bc0 in () at /usr/lib/libEGL_nvidia.so.0 #13 0x7f9d6390a6bd in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #14 0x7f9d6a3d6b9c in () at /usr/lib/libQt5Quick.so.5 #15 0x7f9d6a452739 in QQuickWindow::event(QEvent*) () at /usr/lib/libQt5Quick.so.5 #16 0x7f9d4d459c9a in () at /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so #17 0x7f9d69578b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f9d6888de08 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7f9d68d333b0 in QPlatformWindow::deliverUpdateRequest() () at /usr/lib/libQt5Gui.so.5 #20 0x7f9d688b1a70 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7f9d69578b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #22 0x7f9d6888de08 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #23 0x7f9d6888e913 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #24 0x7f9d688d4d48 in () at /usr/lib/libQt5Core.so.5 #25 0x7f9d675f687b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #26 0x7f9d6764dc89 in () at /usr/lib/libglib-2.0.so.0 #27 0x7f9d675f5132 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #28 0x7f9d688d8b2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #29 0x7f9d688865ac in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #30 0x7f9d688910d9 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #31 0x561d371ed158 in () #32 0x7f9d6803c290 in () at /usr/lib/libc.so.6 #33 0x7f9d6803c34a in __libc_start_main () at /usr/lib/libc.so.6 #34 0x561d371ed505 in () (gdb) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464530] Plasma shell freezes when cycling through task manager when window previews are being shown (hover or on grouped)
https://bugs.kde.org/show_bug.cgi?id=464530 --- Comment #1 from Marcelo Bossoni --- It seems to happen with other plasma popups as well, like notifications -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464530] Plasma shell freezes when cycling through task manager when window previews are being shown (hover or on grouped)
https://bugs.kde.org/show_bug.cgi?id=464530 Marcelo Bossoni changed: What|Removed |Added Platform|Other |Archlinux -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464530] New: Plasma shell freezes when cycling through task manager when window previews are being shown (hover or on grouped)
https://bugs.kde.org/show_bug.cgi?id=464530 Bug ID: 464530 Summary: Plasma shell freezes when cycling through task manager when window previews are being shown (hover or on grouped) Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mmboss...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY When cycling through tasks with thumbnails being shown plasma shell eventually freeze. I can use alt + tab and other stuff. If I press Alt + F2 it eventually unfreeze itself after some time (10 seconds or so) STEPS TO REPRODUCE 1. Enable either window preview on hover OR show previews for grouped tasks 2. Hover another task 3. Keep doing it until it freezes (it took me two attempts) OBSERVED RESULT Plasma shell completely freeze EXPECTED RESULT Shell doesn't freeze and properly show the other task preview(s) 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.7-273-tkg-pds (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 (Video evidence - there is no sound but I clicked outside previews several times) https://photos.google.com/photo/AF1QipPwvOrPXYzvSg_tQtVylQuftMkBijNlzeRMf9kL -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 462512] [NVIDIA] Missing sensor information after driver update
https://bugs.kde.org/show_bug.cgi?id=462512 --- Comment #1 from Marcelo Bossoni --- Created attachment 154330 --> https://bugs.kde.org/attachment.cgi?id=154330=edit nvidia smi output comparing 520 vs 525 A bit more info I've compared the output of "/usr/bin/nvidia-smi dmon -d 2 -s pucm" between driver versions and newer driver add some more spaces it seems... Maybe parser is broken? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 462512] New: [NVIDIA] Missing sensor information after driver update
https://bugs.kde.org/show_bug.cgi?id=462512 Bug ID: 462512 Summary: [NVIDIA] Missing sensor information after driver update Classification: Plasma Product: plasma-systemmonitor Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: mmboss...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY After updating nvidia drivers to version 525, sensor information is missing STEPS TO REPRODUCE 1. Install new nvidia drivers (525) OBSERVED RESULT Missing sensor information EXPECTED RESULT All sensor information is shown SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.10-272-tkg-pds (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open when using an NVIDIA GPU on Wayland
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #61 from Marcelo Bossoni --- (In reply to Eduard from comment #60) > On my system QSG_RENDER_LOOP is set to "basic" anyway. > From the info on https://nobaraproject.org/ I learned today that this value > is set by default if you are using NVIDIA's proprietary driver: > "QSG_RENDER_LOOP=”basic” set for nvidia cards — fixes nouveau Wayland > freezes. The nvidia proprietary driver sets this anyway after installation. > This fixes the issue of KDE Wayland often times freezing on first login > before nvidia proprietary drivers are installed." > > In other words: This fix is ONLY effective if you use Nouveau. If you > experience the issues with the proprietary driver like me, something else is > wrong that you probably cannot fix by yourself. This fix is not only for Nouveau. Do not spread incomplete information. What one distro do is not what all of them do. QSG_RENDER_LOOP workaround works for proprietary driver as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open when using an NVIDIA GPU on Wayland
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #53 from Marcelo Bossoni --- Same problem here on beta. Fun fact: arch added this patch to 5.25.5-2 (https://github.com/archlinux/svntogit-packages/commit/c3af8a4b079f81ceb1aabad413539a77dd164e90) and it works. But moving to beta bring the problem back unless I set the loop to basic. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open when using an NVIDIA GPU on Wayland
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #44 from Marcelo Bossoni --- QSG_RENDER_LOOP=basic brings back another bug where panel items stop updating, like clock freezes at a certain time and list of running apps on task manager are out of sync with what is opened. (Closed applications are still shown and newly opened ones do not show on it). Only way to recover is to enter edit mode and move the panel to another screen corner. But this bug happens far less than the app menu not showing up. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open when using an NVIDIA GPU on Wayland
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #40 from Marcelo Bossoni --- Confirmed workaround work -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open when using an NVIDIA GPU on Wayland
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #38 from Marcelo Bossoni --- Would setting QSG_RENDER_LOOP=basic be enough as a workaround while bug is being worked on? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #28 from Marcelo Bossoni --- Interesting. Tried wayland again after installing vulkan beta drivers on arch. For some reason it doesn't install gbm.so files needed for wayland. KDE/kwin ended up falling back to mesa LLVMpipe and I couldn't reproduce the bug there. So it really seems to be related to nvidia/kwin -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #25 from Marcelo Bossoni --- Created attachment 150882 --> https://bugs.kde.org/attachment.cgi?id=150882=edit Fresh user, bug on application menu and tray icons -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #24 from Marcelo Bossoni --- Yeap. Fresh user, first login, just played a bit and got the issue. Are you on nvidia? Maybe kwin/compositor is to blame and not plasma shell?(In reply to Bernie Innocenti from comment #23) > I can't reproduce this bug on my Arch and Fedora desktops, running KDE > Frameworks 5.96.0 and Plasma 5.25.3. > > Does it also happen when logging in with a new account? Yeap. Fresh user, first login, just played a bit and got the issue. Are you on nvidia? Maybe kwin/compositor is to blame and not plasma shell? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #16 from Marcelo Bossoni --- yeap, I do -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #14 from Marcelo Bossoni --- (In reply to Marcelo Bossoni from comment #13) > Two extra findings on this: > 1 - Tooltips (and thumbnails for windows) are not shown in this case (mouse > hover) > 2 - If I clear clipboard and disable my phone (KDE connect), this issue is > really hard do reproduce on system tray (although it still easy to reproduce > on app launcher) > The moment I copy something and clipboard icon shows up in the tray the > issue becomes much easier to reproduce like if it is stealing focus and > actions? Or maybe this is just lucky because it received focus because of the right click... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #13 from Marcelo Bossoni --- Two extra findings on this: 1 - Tooltips (and thumbnails for windows) are not shown in this case (mouse hover) 2 - If I clear clipboard and disable my phone (KDE connect), this issue is really hard do reproduce on system tray (although it still easy to reproduce on app launcher) The moment I copy something and clipboard icon shows up in the tray the issue becomes much easier to reproduce like if it is stealing focus and actions? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open
https://bugs.kde.org/show_bug.cgi?id=455575 --- Comment #12 from Marcelo Bossoni --- This is a really big and annoying regression and QT6 seems to be too far away. Is there anything that can be done to help debug this? Some patch or build flag with tons of debug/log messages? I can easily reproduce this bug on normal desktop usage. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455276] Menu doesn't open sometimes (pressing Win key). Also happens with tray icons and other panel popups
https://bugs.kde.org/show_bug.cgi?id=455276 --- Comment #5 from Marcelo Bossoni --- Still happening on 5.25.1 Is there anything I can do to help figure that out? Maybe build from source with extra debug messages or anything? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455276] Menu doesn't open sometimes (pressing Win key). Also happens with tray icons and other panel popups
https://bugs.kde.org/show_bug.cgi?id=455276 --- Comment #3 from Marcelo Bossoni --- Does this messages mean anything? jun 15 17:46:05 URSO plasmashell[745]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_19(0x55f39283d6f0, name> jun 15 17:46:05 URSO plasmashell[745]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_19(0x55f39283d6f0, name> jun 15 17:46:05 URSO plasmashell[745]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_19(0x55f39283d6f0, name> jun 15 17:46:05 URSO plasmashell[745]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() jun 15 17:44:15 URSO plasmashell[745]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_19(0x55f39283d6f0, name> jun 15 17:44:15 URSO plasmashell[745]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_19(0x55f39283d6f0, name> jun 15 17:44:15 URSO plasmashell[745]: kf.plasma.quick: Couldn't create KWindowShadow for PlasmaQuick::Dialog_QML_19(0x55f39283d6f0, name> I got tons of it on journalctl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455276] New: Menu doesn't open sometimes (pressing Win key). Also happens with tray icons and other panel popups
https://bugs.kde.org/show_bug.cgi?id=455276 Bug ID: 455276 Summary: Menu doesn't open sometimes (pressing Win key). Also happens with tray icons and other panel popups Product: plasmashell Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mmboss...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Randomly app menu doesn't open. This also happen with tray and other tray items that open popups. This happened on beta, and now it is still happening on final version, although it is supposed to be fixed STEPS TO REPRODUCE 1. Try to use the application menu and tray items OBSERVED RESULT Sometimes only the highlight indication is shown, but popup is not https://photos.app.goo.gl/DUeoYNgFGvi93aFi6 EXPECTED RESULT Highlight and menu is opened SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.3-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454243] Window glitching and blinking after closing
https://bugs.kde.org/show_bug.cgi?id=454243 --- Comment #1 from Marcelo Bossoni --- https://photos.app.goo.gl/CiTmTMVJDG5DPj6x9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454242] Randomly System Tray or app menu/launcher does not open and just show the highlight
https://bugs.kde.org/show_bug.cgi?id=454242 Marcelo Bossoni changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Marcelo Bossoni --- Just testing right now. Reproducible with clipboard, media controls, bluetooth, audio controls -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454242] Randomly System Tray or app menu/launcher does not open and just show the highlight
https://bugs.kde.org/show_bug.cgi?id=454242 --- Comment #3 from Marcelo Bossoni --- Don't know if with ALL of them, but I've seem it happening with app menu, audio and the "arrow" https://photos.app.goo.gl/GHz8SWP1np2ZKQbg9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454242] Randomly System Tray or app menu/launcher does not open and just show the highlight
https://bugs.kde.org/show_bug.cgi?id=454242 --- Comment #1 from Marcelo Bossoni --- Forgot to mention: My panel is placed vertically full height on the left. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454243] New: Window glitching and blinking after closing
https://bugs.kde.org/show_bug.cgi?id=454243 Bug ID: 454243 Summary: Window glitching and blinking after closing Product: kwin Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- SUMMARY After closing a window, it glitches out and blinks on screen. Sometimes it keeps like that for a while I'm using the "explode" effect. Don't know if that plays any rules on that. STEPS TO REPRODUCE 1. Close a window OBSERVED RESULT Close animation plays and window blinks again with full content and then disappears EXPECTED RESULT Close animation plays and window is properly closed with no glitching SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-xanmod1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454242] New: Randomly System Tray or app menu/launcher does not open and just show the highlight
https://bugs.kde.org/show_bug.cgi?id=454242 Bug ID: 454242 Summary: Randomly System Tray or app menu/launcher does not open and just show the highlight Product: plasmashell Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mmboss...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY After opening and closing system tray a few times, it does not open again, but highlight the area as opened. This also happens with Applications menu/launcher STEPS TO REPRODUCE 1. Keep opening and closing system tray by pressing the "arrow" OBSERVED RESULT System tray does not open EXPECTED RESULT System tray open SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-xanmod1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449426] (SEGV) Plasmashell crashed when dragging and dropping item from Kickoff onto any place on Wayland
https://bugs.kde.org/show_bug.cgi?id=449426 Marcelo Bossoni changed: What|Removed |Added CC||mmboss...@gmail.com --- Comment #2 from Marcelo Bossoni --- Just passing by to say it happens to me as well When dragging from app launcher to desktop to create a shortcut -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450181] Memory Leak on Kwin?
https://bugs.kde.org/show_bug.cgi?id=450181 Marcelo Bossoni changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450181] Memory Leak on Kwin?
https://bugs.kde.org/show_bug.cgi?id=450181 --- Comment #4 from Marcelo Bossoni --- Created attachment 146740 --> https://bugs.kde.org/attachment.cgi?id=146740=edit heaptrack (400+ MB being used after closing all windows/apps) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448839] [NVIDIA Wayland] Task Manager's tooltip window thumbnails are black
https://bugs.kde.org/show_bug.cgi?id=448839 --- Comment #3 from Marcelo Bossoni --- (In reply to Marcelo Bossoni from comment #2) > Created attachment 146739 [details] > heaptrack (400+ MB being used after closing all windows/apps) Wrong bug.. how can I delete the attachment? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448839] [NVIDIA Wayland] Task Manager's tooltip window thumbnails are black
https://bugs.kde.org/show_bug.cgi?id=448839 --- Comment #2 from Marcelo Bossoni --- Created attachment 146739 --> https://bugs.kde.org/attachment.cgi?id=146739=edit heaptrack (400+ MB being used after closing all windows/apps) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450181] Memory Leak on Kwin?
https://bugs.kde.org/show_bug.cgi?id=450181 --- Comment #3 from Marcelo Bossoni --- (In reply to Vlad Zahorodnii from comment #2) > Can you run heaptrack to track kwin's memory usage? heaptrack --pid $(pidof > kwin_wayland) Quick question: this is a dump tool or do I need to keep it running while using the system? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450181] Memory Leak on Kwin?
https://bugs.kde.org/show_bug.cgi?id=450181 --- Comment #1 from Marcelo Bossoni --- Forgot to mention that I'm using firefox (MOZ_ENABLE_WAYLAND=1) and watching a lot of youtube, don't know if those videos play a role as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450181] New: Memory Leak on Kwin?
https://bugs.kde.org/show_bug.cgi?id=450181 Bug ID: 450181 Summary: Memory Leak on Kwin? Product: kwin Version: 5.24.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- Created attachment 146686 --> https://bugs.kde.org/attachment.cgi?id=146686=edit Mem usage after 10 minutes SUMMARY Kwin starts wayland session using about 50MB of ram. If you keep using the PC, it will go up to huge amounts (got 1.5gb) One thing I noticed is that if you keep passing the mouse on the task manager to see the window thumbnail/preview it increases memory usage. Eventually it goes down a bit, but never at initial levels. Even after closing all windows/apps ram never goes down to initial levels (or near them) STEPS TO REPRODUCE 1. Just use the PC? OBSERVED RESULT High Ram Usage EXPECTED RESULT Low ram usage ADDITIONAL INFORMATION All window previews are black, don't know if that is related to "preview" functionality or not. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448839] [NVIDIA Wayland] Task Manager's tooltip window thumbnails are black
https://bugs.kde.org/show_bug.cgi?id=448839 Marcelo Bossoni changed: What|Removed |Added CC||mmboss...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421304] [NVIDIA] Plasma panel stops updating at some point
https://bugs.kde.org/show_bug.cgi?id=421304 Marcelo Bossoni changed: What|Removed |Added CC||mmboss...@gmail.com --- Comment #4 from Marcelo Bossoni --- Have this same bug, but just on wayland session (what is weird) Entering Edit mode and moving panel to another screen corner and back to the original place restore updates. Operating System: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.8-xanmod1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443171] When deleting a file using delete/shift+delete no button is selected as default
https://bugs.kde.org/show_bug.cgi?id=443171 --- Comment #5 from Marcelo Bossoni --- Updated to final kde 5.23 and it seems to be solved now. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443171] When deleting a file using delete/shift+delete no button is selected as default
https://bugs.kde.org/show_bug.cgi?id=443171 --- Comment #4 from Marcelo Bossoni --- Even after a system reboot I still have the same issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443171] When deleting a file using delete/shift+delete no button is selected as default
https://bugs.kde.org/show_bug.cgi?id=443171 --- Comment #2 from Marcelo Bossoni --- Just retested with frameworks 5.87. Still no default button selected. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443171] New: When deleting a file using delete/shift+delete no button is selected as default
https://bugs.kde.org/show_bug.cgi?id=443171 Bug ID: 443171 Summary: When deleting a file using delete/shift+delete no button is selected as default Product: dolphin Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mmboss...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When trying to delete one file using the delete key, neither delete, not cancel buttons are selected, so user need to either resort to navigation keys, but it is not able to press enter right away and just confirm deletion. Although it is not a breaking bug, it is quite annoying. STEPS TO REPRODUCE 1. Select one file 2. Press delete 3. Press enter OBSERVED RESULT confirmation dialog remains open EXPECTED RESULT file is deleted since delete button is selected by default Operating System: Arch Linux KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.8-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 432715] Paired PlayStation Dualshock 3 Wireless Controller does not appear in Bluetooth tray
https://bugs.kde.org/show_bug.cgi?id=432715 Marcelo Bossoni changed: What|Removed |Added CC||mmboss...@gmail.com --- Comment #6 from Marcelo Bossoni --- This bug is also present on latest 5.23 beta -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442671] New: Missing sensors (cpu temps/fan speed) after update to 5.23 beta
https://bugs.kde.org/show_bug.cgi?id=442671 Bug ID: 442671 Summary: Missing sensors (cpu temps/fan speed) after update to 5.23 beta Product: plasma-systemmonitor Version: 5.22.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: mmboss...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY After updating to 5.23 beta, all sensors related to libsensors are missing STEPS TO REPRODUCE 1. Try to add fan speed sensor on any page of system monitor OBSERVED RESULT Fans are not available CPU temps are not available Vcore info not available EXPECTED RESULT All of sensors from lm_sensors available Operating System: Arch Linux KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.5-zen2-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442588] No data displayed on overview page graphical monitors or graphical desktop widgets
https://bugs.kde.org/show_bug.cgi?id=442588 Marcelo Bossoni changed: What|Removed |Added CC||mmboss...@gmail.com --- Comment #2 from Marcelo Bossoni --- Have the same issue on ArchLinux with kde 5.23.80 All sensors from lm-sensors are not showing up. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442241] Black screen with egl-wayland 1.1.8
https://bugs.kde.org/show_bug.cgi?id=442241 Marcelo Bossoni changed: What|Removed |Added Version|5.22.5 |5.22.90 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442241] Black screen with egl-wayland 1.1.8
https://bugs.kde.org/show_bug.cgi?id=442241 --- Comment #5 from Marcelo Bossoni --- Created attachment 141458 --> https://bugs.kde.org/attachment.cgi?id=141458=edit firefox screen capture -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442241] Black screen with egl-wayland 1.1.8
https://bugs.kde.org/show_bug.cgi?id=442241 --- Comment #4 from Marcelo Bossoni --- Created attachment 141457 --> https://bugs.kde.org/attachment.cgi?id=141457=edit Screen capture of about kcm -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442241] Black screen with egl-wayland 1.1.8
https://bugs.kde.org/show_bug.cgi?id=442241 --- Comment #3 from Marcelo Bossoni --- Interesting, tried with current master and same thing happens. When I open Firefox in wayland mode, my mouse cursor turns into a small white dot. After closing it, it turn into a black box. Screen capture using spectacle seems to show it properly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442241] Black screen with egl-wayland 1.1.8
https://bugs.kde.org/show_bug.cgi?id=442241 --- Comment #2 from Marcelo Bossoni --- Yes, I have firefox to open automatically on login (xwayland) I could open ksysguard by using Ctrl + esc I could open a konsole from ksysguard. If I try plasmashell --replace if finishes stating that dbus something is already being used by another process. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442241] New: Black screen with egl-wayland 1.1.8
https://bugs.kde.org/show_bug.cgi?id=442241 Bug ID: 442241 Summary: Black screen with egl-wayland 1.1.8 Product: plasmashell Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mmboss...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On Arch, plasmashell works fine using egl-wayland 1.1.7 using egl-wayland 1.1.8 process seems to be running, but not is seen on screen. I can´t see any panels or wallpaper STEPS TO REPRODUCE 1. Use Plasma wayland session with egl-wayland 1.1.8 SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Let me know if you need any more info. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440852] Black or vertically mirrored window with some XWayland apps on nvidia 470+ drivers
https://bugs.kde.org/show_bug.cgi?id=440852 --- Comment #8 from Marcelo Bossoni --- Just built everything using kdesrc-build This bug seems fixed using that version. There are some other small bugs like lamp animation during maximize seems borked on firefox trying to move an mpv window glitches it but no black screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440852] Black or vertically mirrored window with some XWayland apps on nvidia 470+ drivers
https://bugs.kde.org/show_bug.cgi?id=440852 --- Comment #6 from Marcelo Bossoni --- Any easy way to do that on Arch? I mean, should I replace all kde packages or just kwin? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440852] Black or upside down window with some XWayland apps on nvidia 470+ drivers
https://bugs.kde.org/show_bug.cgi?id=440852 --- Comment #2 from Marcelo Bossoni --- Created attachment 140649 --> https://bugs.kde.org/attachment.cgi?id=140649=edit Upside down window content -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440852] Black or upside down window with some XWayland apps on nvidia 470+ drivers
https://bugs.kde.org/show_bug.cgi?id=440852 --- Comment #1 from Marcelo Bossoni --- Created attachment 140648 --> https://bugs.kde.org/attachment.cgi?id=140648=edit Full black window on steam app -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440852] New: Black or upside down window with some XWayland apps on nvidia 470+ drivers
https://bugs.kde.org/show_bug.cgi?id=440852 Bug ID: 440852 Summary: Black or upside down window with some XWayland apps on nvidia 470+ drivers Product: kwin Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open a XWayland app like Steam 2. Resize it 3. Minimize and Maximize it OBSERVED RESULT After 1: Window is black After 2: Window content is upside down After 3: Window is correct EXPECTED RESULT Window is always correct Operating System: Arch Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.9-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432481] Selected configuration using screen (Win+P) applet does nothing
https://bugs.kde.org/show_bug.cgi?id=432481 --- Comment #7 from Marcelo Bossoni --- Quick update. It works with mouse click, but doesn't with keyboard navigation + enter. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432481] Selected configuration using screen (Win+P) applet does nothing
https://bugs.kde.org/show_bug.cgi?id=432481 --- Comment #6 from Marcelo Bossoni --- Is that supposed to be integrated on final 5.21? If so, still not working. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432481] New: Selected configuration using screen (Win+P) applet does nothing
https://bugs.kde.org/show_bug.cgi?id=432481 Bug ID: 432481 Summary: Selected configuration using screen (Win+P) applet does nothing Product: KScreen Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Win+P 2. Select any of the options OBSERVED RESULT Nothing happens (extend doesn't extend, switch to external doesn't switch to external) EXPECTED RESULT Selected option apply the configuration SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.11-zen2-1-zen OS Type: 64-bit Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION xrandr -q output Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 59.9450.0029.9725.0024.0023.98 60.0560.0050.04 1600x1200 60.00 1360x765 60.00 1280x1024 60.02 1280x720 59.9450.00 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 59.94 640x480 59.9459.93 DP-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm x 296mm 1920x1080144.00*+ 119.98 119.8899.9360.0059.9450.00 1680x1050 59.88 1440x900 59.90 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1024x768 119.9999.9775.0370.0760.00 800x600 119.9799.6675.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 119.5299.7775.0072.8159.9459.93 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 Marcelo Bossoni changed: What|Removed |Added CC||mmboss...@gmail.com --- Comment #56 from Marcelo Bossoni --- Arch user here. Network manager is installed (because of powerdevil that requires it) but not started/used. I use netctl for network setup (it is a desktop with static ip) Ran commands described on comments with the same output. When searching for interfaces to show, it only show me "All interfaces" option. But I remember this same widget working. Also, ksysguard works fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421033] Different items shown after disabling composition
https://bugs.kde.org/show_bug.cgi?id=421033 --- Comment #7 from Marcelo Bossoni --- Yes, I can confirm bug was solved with latest driver update -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421033] Different items shown after disabling composition
https://bugs.kde.org/show_bug.cgi?id=421033 --- Comment #5 from Marcelo Bossoni --- I think that is the same as https://bugs.kde.org/show_bug.cgi?id=353983. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 422792] Maximum volume increase (boost volume) per app not available from plasmoid anymore
https://bugs.kde.org/show_bug.cgi?id=422792 --- Comment #3 from Marcelo Bossoni --- Created attachment 129233 --> https://bugs.kde.org/attachment.cgi?id=129233=edit Firefox still at 100% even if increase maximum volume is checked -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 422792] Maximum volume increase (boost volume) per app not available from plasmoid anymore
https://bugs.kde.org/show_bug.cgi?id=422792 Marcelo Bossoni changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #2 from Marcelo Bossoni --- Although it works for main volume, it doesn't apply per application. (Application tab of the volume plasmoid) -- You are receiving this mail because: You are watching all bug changes.
