[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 --- Comment #55 from petrk --- This is still a thing on Plasma 6.1.2. I am not touching Wayland anytime soon, so I simply moved to a X11 DE that doesn't introduce major regressions every couple years. Operating System: Arch Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.8-273-tkg-bore (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 93.9 GiB of RAM Graphics Processor: AMD Radeon RX 7800 XT -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 489332] Background Services KCM missing from Session section
https://bugs.kde.org/show_bug.cgi?id=489332 --- Comment #2 from petrk --- That's not the way. For future reference kcmshell6 kded kcmshell --list -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 --- Comment #50 from petrk --- Settings page for managing services appears to be hidden, probably because of this bug. That's not how we do things in opensource I knew for the last 20 years. I will not argue about intentions of KDE contributor who pushed that change, you can still access the applet it via "kcmshell6 kded" from terminal. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 489332] New: Plasma services menu missing from Session section
https://bugs.kde.org/show_bug.cgi?id=489332 Bug ID: 489332 Summary: Plasma services menu missing from Session section Classification: Applications Product: systemsettings Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- Created attachment 171097 --> https://bugs.kde.org/attachment.cgi?id=171097&action=edit screenshot After updating to 6.1 there is no GUI access to managing services. Things like disabling kscreen and other components. Is it intentional, or a bug? I can't find it. Log from going to the usual place: f.kirigami.layouts: FormData.buddyFor must be a direct child of the attachee. Attachee: QQuickColumnLayout(0x6126775f1880, parent=0x6126776ef6e0, geometry=0,0 0x0), buddyFor: TextField_QMLTYPE_92(0x6126776a80d0, parent=0x6126775f1a00, geometry=0,0 0x0) qml: Page SubCategoryPage_QMLTYPE_118(0x6126770e0f30) is already in the PageRow qml: Pushed pages do not conform to the rules. Please check the documentation. qml: push (file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:223) onActiveSubCategoryRowChanged (qrc:/qt/qml/org/kde/systemsettings/SubCategoryPage.qml:180) expression for onClicked (qrc:/qt/qml/org/kde/systemsettings/CategoriesPage.qml:207) Operating System: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.8.12-273-tkg-eevdf (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 93.9 GiB of RAM Graphics Processor: AMD Radeon RX 7800 XT -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 488425] New: Dragging scrollbar on child window drags parent window.
https://bugs.kde.org/show_bug.cgi?id=488425 Bug ID: 488425 Summary: Dragging scrollbar on child window drags parent window. Classification: Applications Product: plasma-systemmonitor Version: 6.0.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: pepk...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 170427 --> https://bugs.kde.org/attachment.cgi?id=170427&action=edit demonstration I tried to add more columns in new system monitor and then encountered a bug. It is on Wayland, haven't tested on X11. I am attaching a demo, pretty self explanatory. OK and Cancel buttons seem out of focus as well, had to click them "hard" to make them work. I do not like extra items being in a popup window by the way, ksysguard did it better. Lots of wasted space, unreadable in my opinion. More options is not always better. Operating System: Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.8.12-273-tkg-eevdf (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 93.9 GiB of RAM Graphics Processor: AMD Radeon RX 7800 XT -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 --- Comment #44 from petrk --- Well, it just happened. I had kscreen service disabled for a few weeks and re-enabled it yesterday. Operating System: Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.8.11-273-tkg-eevdf (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 93.4 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475468] On X11 with NVIDIA GPU, window and panel resizing is very laggy when any panels are set to Floating or Adapting transparency
https://bugs.kde.org/show_bug.cgi?id=475468 --- Comment #25 from petrk --- Well, it's super smooth with AMD iGPU, so that's rather disappointing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475468] On X11 with NVIDIA GPU, window and panel resizing is very laggy when any panels are set to Floating or Adapting transparency
https://bugs.kde.org/show_bug.cgi?id=475468 --- Comment #24 from petrk --- So as I understand it, the commit adds warning when user wants to use settings which cause performance issues. Correct? Is anyone with AMD GPU affected? I am seriously considering selling my GeForce. Although I would miss CUDA. I can reliably cause frame drops in glxgears just by cycling through kicker menu. Basic stuff like launching applications can cause stutters on my PC. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475468] On X11 with NVIDIA GPU, window and panel resizing is very laggy when any panels are set to Floating or Adapting transparency
https://bugs.kde.org/show_bug.cgi?id=475468 petrk changed: What|Removed |Added CC||pepk...@gmail.com --- Comment #22 from petrk --- I can reproduce it on Plasma 6.1 beta. Moving windows with adaptive transparency causes stutters and input lag. Increasing animation speed to immediate works as a workaround. After switching taskbar to solid color windows are no longer stuttering on "snapping to taskbar" and I can use slower animations. Works fine with transparent taskbar as well. Wayland doesn't seem to be affected. Nvidia 555.42.02 Operating System: Arch Linux KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.8.10-273-tkg-eevdf (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 93.9 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 Manufacturer: ASRock Product Name: B650I Lightning WiFi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 --- Comment #27 from petrk --- Still affected. 6.0.3 Nvidia -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482105] Plasma 6.0 Wayland doesn't switch to SDDM TTY on logout reliably
https://bugs.kde.org/show_bug.cgi?id=482105 petrk changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from petrk --- Doesn't happen anymore. Could have been 5.27 -> 6.0 update glitch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483430] New: Popup notifications show up near center of the screen on X11
https://bugs.kde.org/show_bug.cgi?id=483430 Bug ID: 483430 Summary: Popup notifications show up near center of the screen on X11 Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- Created attachment 167094 --> https://bugs.kde.org/attachment.cgi?id=167094&action=edit demo There seems to be a regression on X11 coming from 5.27. Notifications don't show in corner, instead I get them near center of the screen. Spamming notify-send I get them at the wrong place 100% of the time once the bug is triggered. I haven't figured out a trigger yet. 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.9-273-tkg-eevdf (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 93.9 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 Manufacturer: ASRock Product Name: B650I Lightning WiFi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483134] Plasma crash on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=483134 --- Comment #3 from petrk --- Haven't encountered it on 6.0 yet, but wasn't 5.27 meant to be an LTS release? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483134] Plasma crash on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=483134 --- Comment #1 from petrk --- Created attachment 166891 --> https://bugs.kde.org/attachment.cgi?id=166891&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483134] New: Plasma crash on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=483134 Bug ID: 483134 Summary: Plasma crash on resume from sleep Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.7.9-273-tkg-eevdf x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: Plasmashell process crashes when my PC wakes up from suspend to RAM. At least it recovers The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 QSGAreaAllocator::mergeNodeWithNeighbors (this=0x7ac434185ad0, node=0x7ac4341a8e40) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/util/qsgareaallocator.cpp:194 #6 0x7ac5c21a5997 in QSGAreaAllocator::deallocateInNode (this=this@entry=0x7ac434185ad0, pos=..., node=) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/util/qsgareaallocator.cpp:178 #7 0x7ac5c21a59db in QSGAreaAllocator::deallocate (this=this@entry=0x7ac434185ad0, rect=...) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/util/qsgareaallocator.cpp:116 #8 0x7ac5c21abb9c in QSGOpenGLAtlasTexture::AtlasBase::remove (t=0x7ac434425110, this=0x7ac434185ac0) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:286 #9 QSGOpenGLAtlasTexture::TextureBase::~TextureBase (this=0x7ac434425110, this=) at /usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:516 The reporter indicates this bug may be a duplicate of or related to bug 480308. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482104] Don't change to floated taskbar if theme other than Breeze is used, or don't change it on update.
https://bugs.kde.org/show_bug.cgi?id=482104 --- Comment #2 from petrk --- One good deed a day, please remain arrogant. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482105] New: Plasma 6.0 Wayland doesn't switch to SDDM TTY on logout reliably
https://bugs.kde.org/show_bug.cgi?id=482105 Bug ID: 482105 Summary: Plasma 6.0 Wayland doesn't switch to SDDM TTY on logout reliably Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- It seeems that when I logout Plasma Wayland session it doesn't switch to seat containing SDDM, so I'm left with blinking TTY cursor. Switching with Ctrl + Alt + Function key works. Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.7.6-273-tkg-eevdf (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 93.9 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482104] New: Don't change to floated taskbar if theme other than Breeze is used, or don't change it on update.
https://bugs.kde.org/show_bug.cgi?id=482104 Bug ID: 482104 Summary: Don't change to floated taskbar if theme other than Breeze is used, or don't change it on update. Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Needless to say, why is KDE trying to be Microsoft? Why are you forcing me to go into customization mode to revert your decision? I don't even use Breeze, so it looks even more out of place with my theme. It's a useless gimmick. Congratulations, change for the sake of change. Job well done. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #54 from petrk --- With 6.0 RC2 performance is still not on par with X11, glxgears doesn't quite reach screen refresh framerate. It's around 150fps on a 165Hz screen, it may be closer than where it was, but not on there yet. Nvidia 550.40.07 on 4060Ti. Plus there appears to be delay between typing and text appearing on screen, which may be unrelated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469507] plasmashell segfaults but recovers
https://bugs.kde.org/show_bug.cgi?id=469507 --- Comment #3 from petrk --- It doesn't happen for me anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480813] New: Panel items break on Wayland
https://bugs.kde.org/show_bug.cgi?id=480813 Bug ID: 480813 Summary: Panel items break on Wayland Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 165513 --> https://bugs.kde.org/attachment.cgi?id=165513&action=edit bug in action At first I thought that kicker broke, but then I realized that all panel items sometimes decide to fail to show up on triggering them. Doesn't seem to happen on X11. Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.6.15-273-tkg-eevdf (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 93.4 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400461] Cursor doesn't change or fails to revert to pointer while using zoom effect (Firefox and Thunderbird)
https://bugs.kde.org/show_bug.cgi?id=400461 --- Comment #16 from petrk --- I can't reproduce it on Firefox with 6.0 RC2, however it still happens with Thunderbird. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475605] On X11 with NVIDIA GPU and proprietary driver, black screen with only cursor shown on wake from sleep
https://bugs.kde.org/show_bug.cgi?id=475605 petrk changed: What|Removed |Added CC||pepk...@gmail.com --- Comment #14 from petrk --- My panel becomes unresponsive after resume, Usually I would recover with "killall plasmashell && plasmashell", but this time I attempted "plasmashell --replace" and I got: kf.dbusaddons: Couldn't register name 'org.kde.plasmashell' with DBUS - another process owns it already! Needless to say, it wouldn't recover without killing plasmashell first. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 --- Comment #25 from petrk --- Nevermind, it just took longer sleep to trigger. Ignore my previous comment. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 petrk changed: What|Removed |Added CC||pepk...@gmail.com --- Comment #23 from petrk --- Would plasmashell becoming unresponsive after resume from S3 sleep on X11 be related? I did have such issue and was wondering what the problem is. Then I checked Arch Wiki. >From https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks Quote: "Note: Contrary to NVIDIA's instructions, it is currently not necessary to enable nvidia-resume.service (and it is in fact probably not a good idea to enable it), because the /usr/lib/systemd/system-sleep/nvidia script does the same thing as the service (but slightly earlier), and it is enabled by default (systemd calls it after waking up from a suspend). Only enable nvidia-suspend.service and/or nvidia-hibernate.service, unless you are using GDM with Wayland which requires nvidia-resume.service too." So I have disabled nvidia-resume.service and havent had to do "plasmashell --replace" ever since. Operating System: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.4-273-tkg-bore (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H RTX 2060 Mobile (0x1f15) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #43 from petrk --- On Arch with 545.23.06 no changes, X11 is flawless while Wayland struggles. On Neon Unstable with 545.23.06 X11 is flawless as well, Wayland struggles, plus kscreen backend has issues loading in systemsettings and nvidia-settings segfaults. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475708] New: Taskbar flickers after changing virtual desktop with "Fade Desktop" effect.
https://bugs.kde.org/show_bug.cgi?id=475708 Bug ID: 475708 Summary: Taskbar flickers after changing virtual desktop with "Fade Desktop" effect. Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- Created attachment 162352 --> https://bugs.kde.org/attachment.cgi?id=162352&action=edit Bug in action "Slide" effect is not affected. Steps to reproduce on my system: Switch between virtual desktops with fade effect, click on desktop to unfocus windows, that's it. Taskbar will start flickering. It looks like effect which toggles when window gets close to touching taskbar gets triggered rapidly. I haven't used virtual desktops in a while, so I don't know if previous versions are afffected. Optimus laptop with nvidia_drm.modeset=1 Operating System: Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.5.7-273-tkg-pds-llvm (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H RTX 2060 Mobile Nvidia 535.113.01 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #41 from petrk --- No changes with that variable. I noticed something interesting, checking power draw via nvidia-smi on X11 session running external screen I get power ramps to 20W+ while moving windows around, on Idle I get around 4W. Now on Wayland session I can't get Nvidia to bump above 5W. On idle it stays at 2W. Not does that it that Wayland session renders on IGP for all outputs by default? Or am I misunderstanding things from looking at a glance? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #38 from petrk --- Using latest Neon Unstable, glxgears tops at 157 fps, but usually it reports around 84-120 fps average. I use two screens, 1080p@144Hz and 1440p@165Hz There is a constant 50% load on a single CPU thread by kwin_wayland. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-32-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H RXT 2060 Mobile -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 474261] Draggable margin renders at the bottom of kinfocenter if launched as standalone applicationt
https://bugs.kde.org/show_bug.cgi?id=474261 --- Comment #2 from petrk --- This area is draggable either way. It's quite harder to see with Breeze color scheme. Apologies for mail spam. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 474261] Draggable margin renders at the bottom of kinfocenter if launched as standalone applicationt
https://bugs.kde.org/show_bug.cgi?id=474261 --- Comment #1 from petrk --- Created attachment 161496 --> https://bugs.kde.org/attachment.cgi?id=161496&action=edit screenshot Apologies, forgot to attach a screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 474261] Draggable margin renders at the bottom of kinfocenter if launched as standalone applicationt
https://bugs.kde.org/show_bug.cgi?id=474261 petrk changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 474261] New: Draggable margin renders at the bottom of kinfocenter if launched as standalone applicationt
https://bugs.kde.org/show_bug.cgi?id=474261 Bug ID: 474261 Summary: Draggable margin renders at the bottom of kinfocenter if launched as standalone applicationt Classification: Applications Product: kinfocenter Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com CC: sit...@kde.org Target Milestone: --- For reference, I'm using color scheme called "Blank" I went to kinfocenter from start menu, and noticed that there is a small horizontal margin at the bottom. It can be dragged, like title bar or pre-kirigami empty application content area. To make it disappear it is enough to select a different item from left sidebar, after returning to main page "margin" is gone. Starting kinfocenter from systemsettings doesn't trigger any such bug. Here's console output while it is occuring, not sure if those errors are relevant: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8. Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead. If this causes problems, reconfigure your locale. See the locale(1) manual for more information. kf.xmlgui: cannot find .rc file "kinfocenterui.rc" for component "kinfocenter" qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/ScrollablePage.qml:334: TypeError: Cannot read property 'activeFocus' of null (exception occurred during delayed function evaluation) file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/ScrollablePage.qml:334: TypeError: Cannot read property 'activeFocus' of null (exception occurred during delayed function evaluation) qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool qrc:/qt/qml/org/kde/desktop/private/MobileCursor.qml:33:13: Unable to assign [undefined] to bool -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474233] New: kcreen doesn't load kcm_kscreen/main.qml:241 Invalid property assignment: int expected
https://bugs.kde.org/show_bug.cgi?id=474233 Bug ID: 474233 Summary: kcreen doesn't load kcm_kscreen/main.qml:241 Invalid property assignment: int expected Classification: Applications Product: systemsettings Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: pepk...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 161449 --> https://bugs.kde.org/attachment.cgi?id=161449&action=edit systemsettings screenshot Just installed Neon Unstable on bare metal to check progress and see if there are any regressions I would care about. After installing nvidia drivers I went to kscreen kcm to set native refresh rate on my "gaming" monitor. Well, that didn't go as planned. Please see attachment below. Log from running systemsettings from konsole: qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" "qrc:/kcm/kcm_kscreen/main.qml" "Error loading QML file.\n241: Invalid property assignment: int expected\n" qml: The item SubCategoryPage_QMLTYPE_115(0x55963394e5f0) is already in the PageRow Reproducible on both X11 and Wayland session. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-32-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H nvidia 535.86.05 RTX 2060 Mobile -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 472468] New: Characters illegal for FAT32 and NTFS break transfer and connection to Android device
https://bugs.kde.org/show_bug.cgi?id=472468
Bug ID: 472468
Summary: Characters illegal for FAT32 and NTFS break transfer
and connection to Android device
Classification: Frameworks and Libraries
Product: kio-extras
Version: 23.04.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: MTP
Assignee: unassigned-b...@kde.org
Reporter: pepk...@gmail.com
CC: elvis.angelac...@kde.org
Target Milestone: ---
As you all are aware FAT32 and NTFS doesn't allow certain characters in
filenames. Unfortunately in recent versions of Android Google decided to go
with compatibility over what makes sense to "powerusers". There's a custom FUSE
layer over EXT4 on Android, and recently a change was made to disallow extra
characters in filenames, probably to make Windows users happy.
So in short:
1. Try to copy a file over MTP to an Android 13 device. Say, filename contains
":" or "colon" if you will.
2. Copy job times out when encountering offending file.
3. After about 30 seconds I get a dialog asking to retry, but MTP breaks.
4. "Skip" option is not doing anything, it times out like on step 2, only
"Cancel" option does its job. Browsing of MTP device is broken and it needs to
be reconnected to recover.
Can we fail without breaking connection? Ideally KIO would detect what the
problem is and propose a filename change.
21/07/2023 16:40kernel usb 6-2: new SuperSpeed USB device number 9
using xhci_hcd
21/07/2023 16:40kernel usb 6-2: New USB device found, idVendor=18d1,
idProduct=4ee1, bcdDevice= 4.40
21/07/2023 16:40kernel usb 6-2: New USB device strings: Mfr=1,
Product=2, SerialNumber=3
21/07/2023 16:40kernel usb 6-2: Product: Pixel 4a
21/07/2023 16:40kernel usb 6-2: Manufacturer: Google
21/07/2023 16:40kernel usb 6-2: SerialNumber: Redacted
21/07/2023 16:40dolphin 16:40:04.878 INFO DeviceManager:449
Device added: "mtp://Google_Pixel_4a_12021JEC201128/"
QList("mtp://Google_Pixel_4a_12021JEC201128/")
Snippet from logs:
21/07/2023 16:41org.kde.kmtpd5 Error 2: PTP Layer error 02ff:
LIBMTP_Send_File_From_File_Descriptor(): Could not send object.
21/07/2023 16:41org.kde.kmtpd5 Error 2: Error 02ff: PTP I/O Error
It's part a bug report because of MTP connection breaking, and a wishlist item
for filename correction logic.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 471431] kded5 crash on system update
https://bugs.kde.org/show_bug.cgi?id=471431 --- Comment #2 from petrk --- After such crash there is a chance for my keymap to get reset to US. Special characters are not working properly It can't be a coincidence and it's not first time it happened. Here's output from localectl: System Locale: LANG=pl_PL.UTF-8 VC Keymap: uk X11 Layout: gb X11 Model: pl -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 471431] kded5 crash on system update
https://bugs.kde.org/show_bug.cgi?id=471431 --- Comment #1 from petrk --- #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f2f8609f2d3 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7f2f8604fa08 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7f2f87b613ac in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash/kcrash-5.107.0/src/kcrash.cpp:611 #4 0x7f2f8604fab0 in () at /usr/lib/libc.so.6 #5 0x7f2f85f0a1ed in XPending (dpy=0x18) at /usr/src/debug/libx11/libX11-1.8.6/src/Pending.c:51 #6 0x7f2f641b1d91 in XlibNotifications::processEvents() (this=) at /usr/src/debug/plasma-desktop/plasma-desktop-5.27.6/kcms/touchpad/backends/x11/xlibnotifications.cpp:63 #7 XlibNotifications::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x55f59a06c040, _c=, _id=, _a=) at /usr/src/debug/plasma-desktop/build/kcms/touchpad/touchpad_autogen/include/moc_xlibnotifications.cpp:91 #8 0x7f2f868d0863 in doActivate(QObject*, int, void**) (sender=0x55f599f88c50, signal_index=5, argv=0x7ffe499808c0) at kernel/qobject.cpp:3937 #9 0x7f2f868d1f19 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) (this=this@entry=0x55f599f88c50, _t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:185 #10 0x7f2f868d200b in QSocketNotifier::event(QEvent*) (this=0x55f599f88c50, e=) at kernel/qsocketnotifier.h:115 #11 0x7f2f8757893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55f599f88c50, e=0x7ffe499809d0) at kernel/qapplication.cpp:3640 #12 0x7f2f8689b778 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55f599f88c50, event=0x7ffe499809d0) at kernel/qcoreapplication.cpp:1064 #13 0x7f2f868e9336 in socketNotifierSourceDispatch(GSource*, GSourceFunc, gpointer) (source=0x55f599b17d50) at kernel/qeventdispatcher_glib.cpp:107 #14 0x7f2f85310981 in g_main_dispatch (context=0x7f2f7c000ee0) at ../glib/glib/gmain.c:3460 #15 g_main_context_dispatch (context=0x7f2f7c000ee0) at ../glib/glib/gmain.c:4200 #16 0x7f2f8536db39 in g_main_context_iterate.isra.0 (context=context@entry=0x7f2f7c000ee0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276 #17 0x7f2f8530e032 in g_main_context_iteration (context=0x7f2f7c000ee0, may_block=1) at ../glib/glib/gmain.c:4343 #18 0x7f2f868ea5cc in QEventDispatcherGlib::processEvents(QFlags) (this=0x55f599b17dc0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 471431] New: kded5 crash on system update
https://bugs.kde.org/show_bug.cgi?id=471431 Bug ID: 471431 Summary: kded5 crash on system update Classification: Frameworks and Libraries Product: frameworks-kded Version: 5.107.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: pepk...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 159889 --> https://bugs.kde.org/attachment.cgi?id=159889&action=edit segfault details with backtrace It seems that often when I update my system kded5 decides to segfault. Details from package manager on what was updated: [2023-06-25T11:32:56+0100] [ALPM] upgraded aalib (1.4rc5-16 -> 1.4rc5-17) [2023-06-25T11:32:56+0100] [ALPM] upgraded btrfs-progs (6.3.1-1 -> 6.3.2-1) [2023-06-25T11:32:56+0100] [ALPM] upgraded libcups (1:2.4.5-1 -> 1:2.4.6-1) [2023-06-25T11:32:56+0100] [ALPM] upgraded libssh2 (1.10.0-3 -> 1.11.0-1) [2023-06-25T11:32:56+0100] [ALPM] upgraded libpng (1.6.39-1 -> 1.6.40-1) [2023-06-25T11:32:56+0100] [ALPM] upgraded cups (1:2.4.5-1 -> 1:2.4.6-1) [2023-06-25T11:32:56+0100] [ALPM] upgraded mesa (23.1.2-1 -> 23.1.3-1) [2023-06-25T11:32:56+0100] [ALPM] upgraded sdl2 (2.26.5-2 -> 2.28.0-1) [2023-06-25T11:32:56+0100] [ALPM] upgraded flac (1.4.2-1 -> 1.4.3-1) [2023-06-25T11:32:56+0100] [ALPM] upgraded libopenmpt (0.7.1-1 -> 0.7.2-1) [2023-06-25T11:32:56+0100] [ALPM] upgraded darktable (2:4.2.1-6 -> 2:4.4.0-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded electron25 (25.1.1-3 -> 25.2.0-2) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-brotli (1.0.9-5 -> 1.0.9-12) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-flac (1.4.2-1 -> 1.4.3-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-libpng (1.6.39-1 -> 1.6.40-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-libcups (2.4.4-1 -> 2.4.6-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-libssh2 (1.10.0-2 -> 1.11.0-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-nvidia-utils (535.54.03-1 -> 535.54.03-2) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-mesa (23.1.2-1 -> 23.1.3-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-mesa-vdpau (23.1.2-1 -> 23.1.3-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-opencl-nvidia (535.54.03-1 -> 535.54.03-2) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-sdl2 (2.26.5-1 -> 2.28.0-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded vulkan-mesa-layers (23.1.2-1 -> 23.1.3-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-vulkan-mesa-layers (23.1.2-1 -> 23.1.3-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded vulkan-radeon (23.1.2-1 -> 23.1.3-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-vulkan-radeon (23.1.2-1 -> 23.1.3-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded lib32-vulkan-virtio (23.1.2-1 -> 23.1.3-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded libva-mesa-driver (23.1.2-1 -> 23.1.3-1) [2023-06-25T11:32:57+0100] [ALPM] upgraded libzip (1.9.2-1 -> 1.10.0-1) [2023-06-25T11:32:58+0100] [ALPM] upgraded linux-zen (6.3.8.zen1-1 -> 6.3.9.zen1-1) [2023-06-25T11:33:01+0100] [ALPM] upgraded linux-zen-headers (6.3.8.zen1-1 -> 6.3.9.zen1-1) [2023-06-25T11:33:01+0100] [ALPM] upgraded mesa-vdpau (23.1.2-1 -> 23.1.3-1) [2023-06-25T11:33:01+0100] [ALPM] upgraded ostree (2023.3-1 -> 2023.4-1) [2023-06-25T11:33:01+0100] [ALPM] upgraded qt5-base (5.15.10+kde+r129-1 -> 5.15.10+kde+r129-3) [2023-06-25T11:33:01+0100] [ALPM] upgraded powerdevil (5.27.6-1 -> 5.27.6-3) [2023-06-25T11:33:03+0100] [ALPM] upgraded pycharm-community-edition (2023.1.2-1 -> 2023.1.3-1) [2023-06-25T11:33:03+0100] [ALPM] upgraded python-cryptography (40.0.2-1 -> 41.0.1-2) [2023-06-25T11:33:03+0100] [ALPM] upgraded python-google-auth (2.17.3-1 -> 2.18.0-1) [2023-06-25T11:33:03+0100] [ALPM] upgraded python-googleapis-common-protos (1.59.0-2 -> 1.59.1-1) [2023-06-25T11:33:03+0100] [ALPM] upgraded python-pytest (7.3.2-1 -> 7.4.0-1) [2023-06-25T11:33:03+0100] [ALPM] upgraded python-sentry_sdk (1.25.1-1 -> 1.26.0-1) [2023-06-25T11:33:03+0100] [ALPM] upgraded python-setuptools (1:67.8.0-1 -> 1:68.0.0-1) [2023-06-25T11:33:03+0100] [ALPM] upgraded qt6-base (6.5.1-2 -> 6.5.1-4) [2023-06-25T11:33:03+0100] [ALPM] upgraded sddm (0.19.0-9 -> 0.20.0-1) [2023-06-25T11:33:03+0100] [ALPM] upgraded vulkan-virtio (23.1.2-1 -> 23.1.3-1) [2023-06-25T11:33:03+0100] [ALPM] upgraded wolfssl (5.6.2-1 -> 5.6.3-1) [2023-06-25T11:33:03+0100] [ALPM] upgraded yt-dlp (2023.06.21-1 -> 2023.06.22-1) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 469569] Plasma applet doesn't control PCM volume
https://bugs.kde.org/show_bug.cgi?id=469569 --- Comment #2 from petrk --- I did some digging on how alsa and pipewire work under the hood when I had spare time at work. Turns out that profiles actually change how the sound card is interacted with. I switched profile from digital to analog and now plasma applet can control PCM volume instead only pipewire master. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 469569] New: Plasma applet doesn't control PCM volume
https://bugs.kde.org/show_bug.cgi?id=469569 Bug ID: 469569 Summary: Plasma applet doesn't control PCM volume Classification: Plasma Product: plasma-pa Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com CC: isma...@gmail.com, m...@ratijas.tk, now...@gmail.com Target Milestone: --- Is it possible for plasma-pa applet to be able to control PCM volume, or check if it's at 100% on devices which only expose PCM slider? My USB DAC only exposes PCM slider, and from time to time something lowers it, but I can't bring it back up to 100% via GUI and I am forced to use alsamixer. I am using pipewire and two audio devices. Integrated sound card which I mostly use for speakers and mic and Fiio E10K via USB which I use for headphones. Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469552] New: Seeking using first letter regression
https://bugs.kde.org/show_bug.cgi?id=469552 Bug ID: 469552 Summary: Seeking using first letter regression Classification: Applications Product: dolphin Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pepk...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Hello, I am quite sure that recently there was a change to the way dolphin reacts to key presses inside a directory. Here's my workload and how it got broken: Say I'm in /etc and I want to go to "fstab" file, sure I could type fstab to select it directly, or use filter function, but what if I don't know the correct file name. I could keep pressing "F" key until I get to the file I wanted to, but I want to skip folders, there used to be a trick in such case: 1. Scroll down past folders and select any file 2. Press first letter key until you get to the desired file 3. Seeking continues from where selection was made. ! That's the crucial part So recently it changed for some reason, instead of continuing from where the selection is it jumps back to the beginning, starting from folders. That obviously wastes my time, because I have to go through folders first, before going to files. Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469507] New: plasmashell segfaults but recovers
https://bugs.kde.org/show_bug.cgi?id=469507 Bug ID: 469507 Summary: plasmashell segfaults but recovers Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.4) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.3.1-zen1-1-zen x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.4 [CoredumpBackend] -- Information about the crash: My plasmashell crashed after I was done configuring ddcci-plasmoid (https://github.com/davidhi7/ddcci-plasmoid) addon. I am not sure if it's in any way related. I used my laptop with external display when it happened. It's an Optimus setup, using both AMD and Nvidia with kms enabled. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x7f0e13c2d16e in QQmlContextData::ContextGuard::objectDestroyed(QObject*) (this=0x55803bbd4998) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlcontext_p.h:382 #6 0x7f0e13c3cf2c in QQmlData::destroyed(QObject*) (this=0x5580378484f0, object=0x5580378484d0) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlengine.cpp:1961 #7 0x7f0e126b5066 in QObject::~QObject() (this=0x5580378484d0, this=) at kernel/qobject.cpp:1019 #8 0x7f0dd4b474eb in QQmlPrivate::QQmlElement::~QQmlElement() (this=0x5580378484d0, this=) at /usr/include/qt/QtQml/qqmlprivate.h:144 #9 QQmlPrivate::QQmlElement::~QQmlElement() (this=0x5580378484d0, this=) at /usr/include/qt/QtQml/qqmlprivate.h:144 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469507] plasmashell segfaults but recovers
https://bugs.kde.org/show_bug.cgi?id=469507 --- Comment #1 from petrk --- Created attachment 158783 --> https://bugs.kde.org/attachment.cgi?id=158783&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461068] kscreen_osd_ser coredumps in KScreen::Output::~Output() when pressing Fn+F7 (monitor config key)
https://bugs.kde.org/show_bug.cgi?id=461068 petrk changed: What|Removed |Added CC||pepk...@gmail.com --- Comment #11 from petrk --- Not sure if it's interesting but here you go. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f50115425af in QWindow::setVisible (this=, visible=false) at kernel/qwindow.cpp:630 Downloading source file /usr/src/debug/qt5-base/qtbase/src/gui/kernel/qwindow.cpp 630 d->setVisible(visible); [Current thread is 1 (Thread 0x7f500f806680 (LWP 5442))] (gdb) trace Tracepoint 1 at 0x7f50115425af: file kernel/qwindow.cpp, line 630. (gdb) bt #0 0x7f50115425af in QWindow::setVisible (this=, visible=false) at kernel/qwindow.cpp:630 #1 0x7f50110bea71 in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #2 doActivate (sender=0x557d05fe8900, signal_index=0, argv=0x7ffe6cafc880) at kernel/qobject.cpp:3923 #3 0x7f50110bee14 in QObject::destroyed (this=, _t1=) at .moc/moc_qobject.cpp:219 #4 0x7f50110b537c in QObject::~QObject (this=, this=) at kernel/qobject.cpp:1010 #5 0x7f50129c967a in KScreen::Output::~Output (this=, this=) at /usr/src/debug/libkscreen/libkscreen-5.27.3/src/output.cpp:180 #6 QtSharedPointer::CustomDeleter::execute (this=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:187 #7 QtSharedPointer::ExternalRefCountWithCustomDeleter::deleter ( self=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:205 #8 0x557d050a1956 in QtSharedPointer::ExternalRefCountData::destroy (this=0x557d05fed2b0) at /usr/include/qt/QtCore/qsharedpointer_impl.h:149 #9 QSharedPointer::deref (dd=0x557d05fed2b0) at /usr/include/qt/QtCore/qsharedpointer_impl.h:458 #10 QSharedPointer::deref (dd=, dd=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:454 #11 QSharedPointer::deref (this=, this=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:453 #12 QSharedPointer::~QSharedPointer (this=, this=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:310 #13 KScreen::Osd::~Osd (this=, this=) at /usr/src/debug/kscreen/kscreen-5.27.3/osd/osd.cpp:38 #14 0x557d050a19e5 in KScreen::Osd::~Osd (this=, this=) at /usr/src/debug/kscreen/kscreen-5.27.3/osd/osd.cpp:36 #15 qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/qt/QtCore/qalgorithms.h:320 #16 qDeleteAll > (c=...) at /usr/include/qt/QtCore/qalgorithms.h:328 #17 KScreen::OsdManager::quit (this=0x7ffe6cafce70) at /usr/src/debug/kscreen/kscreen-5.27.3/osd/osdmanager.cpp:49 #18 0x7f50110b1bb0 in QObject::event (this=0x7ffe6cafce70, e=0x7f502560) at kernel/qobject.cpp:1347 #19 0x7f501108df48 in QCoreApplication::notifyInternal2 (receiver=0x7ffe6cafce70, event=0x7f502560) at kernel/qcoreapplication.cpp:1064 --Type for more, q to quit, c to continue without paging--c #20 0x7f501108dfb3 in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #21 0x7f501108ea53 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x557d05b1f450) at kernel/qcoreapplication.cpp:1821 #22 0x7f50110d4e88 in postEventSourceDispatch (s=0x557d05b999f0) at kernel/qeventdispatcher_glib.cpp:277 #23 0x7f500f90f53b in g_main_dispatch (context=0x7f5008000ee0) at ../glib/glib/gmain.c:3460 #24 g_main_context_dispatch (context=0x7f5008000ee0) at ../glib/glib/gmain.c:4200 #25 0x7f500f96c219 in g_main_context_iterate.constprop.0 (context=0x7f5008000ee0, block=1, dispatch=1, self=) at ../glib/glib/gmain.c:4276 #26 0x7f500f90e1a2 in g_main_context_iteration (context=0x7f5008000ee0, may_block=1) at ../glib/glib/gmain.c:4343 #27 0x7f50110d8c6c in QEventDispatcherGlib::processEvents (this=0x557d05b7f150, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f50110866ec in QEventLoop::exec (this=0x7ffe6cafcdd0, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #29 0x7f5011091219 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #30 0x7f501153a052 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1870 #31 0x557d0509c4db in main (argc=, argv=) at /usr/src/debug/kscreen/kscreen-5.27.3/osd/main.cpp:17 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467815] External display runs at 60 Hz in a Wayland session.
https://bugs.kde.org/show_bug.cgi?id=467815
--- Comment #3 from petrk ---
kscreen-console output since doctor doesn't create any output:
START: Requesting Config
Received config. Took 27 milliseconds
Screen:
maxSize: QSize(64000, 64000)
minSize: QSize(0, 0)
currentSize: QSize(4480, 1440)
-
Id: 1
Name: "eDP-2"
Type: "Panel (Laptop)"
Connected: true
Enabled: true
Priority: 1
Rotation: KScreen::Output::None
Pos: QPoint(0,360)
MMSize: QSize(340, 190)
FollowPreferredMode: false
Size: QSize(1920, 1080)
Scale: 1
Clones: None
Mode: "0"
Preferred Mode: "0"
Preferred modes: ("0")
Modes:
"0""1920x1080@144" QSize(1920, 1080) 144.104
"1""1680x1050@144" QSize(1680, 1050) 144.104
"10""1024x768@60" QSize(1024, 768) 59.92
"11""1280x800@60" QSize(1280, 800) 59.81
"12""1920x1080@60" QSize(1920, 1080) 59.963
"13""1600x900@60" QSize(1600, 900) 59.946
"14""1368x768@60" QSize(1368, 768) 59.882
"15""1280x720@60" QSize(1280, 720) 59.855
"2""1280x1024@144" QSize(1280, 1024) 144.104
"3""1440x900@144" QSize(1440, 900) 144.104
"4""1280x800@144" QSize(1280, 800) 144.104
"5""1280x720@144" QSize(1280, 720) 144.104
"6""1024x768@144" QSize(1024, 768) 144.104
"7""800x600@144" QSize(800, 600) 144.104
"8""640x480@144" QSize(640, 480) 144.104
"9""1280x1024@60" QSize(1280, 1024) 59.895
EDID Info:
Device ID: "xrandr-AU Optronics"
Name: ""
Vendor: "AU Optronics"
Serial: ""
EISA ID: "B156HAN09.2"
Hash: "2a02f9b1d575bba4cdf2f53f69881597"
Width: 34
Height: 19
Gamma: 2.2
Red: QQuaternion(scalar:1, vector:(0.566406, 0.335938, 0))
Green: QQuaternion(scalar:1, vector:(0.350586, 0.568359, 0))
Blue: QQuaternion(scalar:1, vector:(0.158203, 0.121094, 0))
White: QQuaternion(scalar:1, vector:(0.313477, 0.329102, 0))
-
Id: 2
Name: "DP-1"
Type: "DisplayPort"
Connected: true
Enabled: true
Priority: 2
Rotation: KScreen::Output::None
Pos: QPoint(1920,0)
MMSize: QSize(690, 390)
FollowPreferredMode: false
Size: QSize(2560, 1440)
Scale: 1
Clones: None
Mode: "1"
Preferred Mode: "0"
Preferred modes: ("0")
Modes:
"0""2560x1440@60" QSize(2560, 1440) 59.951
"1""2560x1440@165" QSize(2560, 1440) 164.835
"10""1280x1024@60" QSize(1280, 1024) 60.02
"11""1440x900@60" QSize(1440, 900) 59.887
"12""1280x720@100" QSize(1280, 720) 100
"13""1280x720@60" QSize(1280, 720) 59.943
"14""1280x720@50" QSize(1280, 720) 50
"15""1024x768@75" QSize(1024, 768) 75.029
"16""1024x768@70" QSize(1024, 768) 70.069
"17""1024x768@60" QSize(1024, 768) 60.004
"18""800x600@75" QSize(800, 600) 75
"19""800x600@72" QSize(800, 600) 72.188
"2""2560x1440@144" QSize(2560, 1440) 144
"20""800x600@60" QSize(800, 600) 60.317
"21""800x600@56" QSize(800, 600) 56.25
"22""720x576@50" QSize(720, 576) 50
"23""720x480@60" QSize(720, 480) 59.94
"24""640x480@75" QSize(640, 480) 75
"25""640x480@73" QSize(640, 480) 72.809
"26""640x480@60" QSize(640, 480) 59.94
"27""1600x1200@60" QSize(1600, 1200) 59.869
"28""1280x1024@60" QSize(1280, 1024) 59.895
"29""1024x768@60" QSize(1024, 768) 59.92
"3""1920x1080@120" QSize(1920, 1080) 119.879
"30""1920x1200@60" QSize(1920, 1200) 59.885
"31&quo
[kwin] [Bug 467815] External display runs at 60 Hz in a Wayland session.
https://bugs.kde.org/show_bug.cgi?id=467815 --- Comment #2 from petrk --- Created attachment 157592 --> https://bugs.kde.org/attachment.cgi?id=157592&action=edit wayland info Is there anything else that needs attaching? I run Nvidia 520.56.06. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467815] External display runs at 60 Hz in a Wayland session.
https://bugs.kde.org/show_bug.cgi?id=467815 --- Comment #1 from petrk --- Created attachment 157591 --> https://bugs.kde.org/attachment.cgi?id=157591&action=edit kwin info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467815] New: External display runs at 60 Hz in a Wayland session.
https://bugs.kde.org/show_bug.cgi?id=467815 Bug ID: 467815 Summary: External display runs at 60 Hz in a Wayland session. Classification: Plasma Product: kwin Version: 5.27.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- Created attachment 157589 --> https://bugs.kde.org/attachment.cgi?id=157589&action=edit drminfo --all output For the background, I use a Legion 5 AMD with 4800H cpu and RTX 2060 driving external display. Display is a 1440p display running at 165 Hz. I logged in to a Wayland session to see how's the progress and what struck me immediately was that framerate was not what I set in systemesttings. It's running at 60Hz, how do I know? mouse ghosting gaps, and preceived sluggishness from going to a lower framerate screen. Operating System: Arch Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.1.21-1-lts (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407161] Only two items are highlighted when pasting them
https://bugs.kde.org/show_bug.cgi?id=407161 --- Comment #5 from petrk --- Still a thing. KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400461] Cursor doesn't change or fails to revert to pointer while using zoom effect (Firefox and Thunderbird)
https://bugs.kde.org/show_bug.cgi?id=400461 petrk changed: What|Removed |Added Keywords||accessibility Version|5.25.90 |5.27.3 --- Comment #15 from petrk --- Unfortunately this is still a thing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 466944] kded5 crashed upon waking up
https://bugs.kde.org/show_bug.cgi?id=466944 petrk changed: What|Removed |Added CC||pepk...@gmail.com --- Comment #3 from petrk --- kded5 crashes for me as well Once it does touchpad "tap to click" stops working and all my audio profiles get messed up. Don't know if that backtrace is of any use: #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f70f40a0953 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7f70f4051ea8 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7f70f5b6637c in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash/kcrash-5.104.0/src/kcrash.cpp:611 #4 0x7f70f4051f50 in () at /usr/lib/libc.so.6 #5 0x7f70f3f08bfd in XPending (dpy=0x18) at /usr/src/debug/libx11/libX11-1.8.4/src/Pending.c:51 #6 0x7f70c21b0c87 in XlibNotifications::processEvents() (this=) at /usr/src/debug/plasma-desktop/plasma-desktop-5.27.3/kcms/touchpad/backends/x11/xlibnotifications.cpp:63 #7 XlibNotifications::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x5577b0897d00, _c=, _id=, _a=) at /usr/src/debug/plasma-desktop/build/kcms/touchpad/touchpad_autogen/include/moc_xlibnotifications.cpp:91 #8 0x7f70f48bec20 in () at /usr/lib/libQt5Core.so.5 #9 0x7f70f48c0999 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #10 0x7f70f48c0a8b in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #11 0x7f70f5578b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #12 0x7f70f488df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7f70f48d7ac6 in () at /usr/lib/libQt5Core.so.5 #14 0x7f70f370fafb in g_main_dispatch (context=0x7f70ec000ee0) at ../glib/glib/gmain.c:3460 #15 g_main_context_dispatch (context=0x7f70ec000ee0) at ../glib/glib/gmain.c:4200 #16 0x7f70f376c5d9 in g_main_context_iterate.constprop.0 (context=0x7f70ec000ee0, block=1, dispatch=1, self=) at ../glib/glib/gmain.c:4276 --Type for more, q to quit, c to continue without paging--c #17 0x7f70f370d382 in g_main_context_iteration (context=0x7f70ec000ee0, may_block=1) at ../glib/glib/gmain.c:4343 #18 0x7f70f48d8c6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7f70f48866ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x7f70f4891219 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #21 0x5577b01bb040 in main(int, char**) (argc=, argv=) at /usr/src/debug/kded/kded-5.104.0/src/kded.cpp:785 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 petrk changed: What|Removed |Added CC||pepk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464911] Primary screen changes in-between reboots.
https://bugs.kde.org/show_bug.cgi?id=464911 --- Comment #5 from petrk --- Created attachment 156389 --> https://bugs.kde.org/attachment.cgi?id=156389&action=edit requested output I can't reproduce it, which is good probably. Here's requested details, apologies for keeping you waiting, I was trying to catch it. The only issue I have since testing 5.27 beta is that after sleep my layouts may change to overlapping, even though I have them side to side. Other than that it was pretty solid this past weeks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462649] Composited desktop unusable with Nvidia 525.60.11 switchable graphics when only external screen is being driven
https://bugs.kde.org/show_bug.cgi?id=462649 --- Comment #6 from petrk --- True, my next purchase will be all AMD, unless Intel releases something compelling by that time, but for now there's no reason to upgrade, apart from being stuck on a driver from last year, which for now is just a line in pacman.conf. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462649] Composited desktop unusable with Nvidia 525.60.11 switchable graphics when only external screen is being driven
https://bugs.kde.org/show_bug.cgi?id=462649 --- Comment #4 from petrk --- This sucks, but it's understandable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462649] Composited desktop unusable with Nvidia 525.60.11 switchable graphics when only external screen is being driven
https://bugs.kde.org/show_bug.cgi?id=462649 petrk changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Version|5.26.4 |5.26.90 Resolution|UPSTREAM|--- --- Comment #2 from petrk --- Reopening as there's no answer from Nvidia. Tried 525.85.05 and my desktop is still broken. Surprisingly wayland session of plasma doesn't slow down to a crawl if screen is closed and I consider it unaffected. However it seems that my external screen runs at 60 Hz even though control panel says it's running at 165 Hz, so that's a no go for me. Not sure if it belongs to kwin, as even with compositing disabled on xorg animations from inside windows lag. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #125 from petrk --- Created attachment 155742 --> https://bugs.kde.org/attachment.cgi?id=155742&action=edit screenshot Too soon? My external monitor didn't wake up after sleep. It was off on lock screen. After waking up it came back on, but my primary screen is corrupted. Logging off and back on fixes corruption. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464911] Primary screen changes in-between reboots.
https://bugs.kde.org/show_bug.cgi?id=464911 --- Comment #1 from petrk --- Is it a duplicate of the following bug? https://bugs.kde.org/show_bug.cgi?id=426817 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464911] New: Primary screen changes in-between reboots.
https://bugs.kde.org/show_bug.cgi?id=464911 Bug ID: 464911 Summary: Primary screen changes in-between reboots. Classification: Plasma Product: KScreen Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- It was all going quite smoothly for me since trying 5.27 beta, however today I had a puzzling issue after closing my laptop's lid. Panels from external screen stayed unchanged. I was trying to figure out what the hell happened until deciding to check display configuration applet. My external monitor has been assigned as primary, but I haven't done it myself. Issue: Primary screen may change for whatever reason, which in turn stops panels and widgets from moving around when internal screen gets disabled. 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-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 426817] KScreen does not save "Primary" setting between reboots
https://bugs.kde.org/show_bug.cgi?id=426817 petrk changed: What|Removed |Added CC||pepk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464762] Cursor harder to move between screens if those are set to appear at different height relative to each-other.
https://bugs.kde.org/show_bug.cgi?id=464762 petrk changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from petrk --- Ah crap, I got so used to overlapping desktops that I haven't noticed workspace constraints while using mouse. Having downgraded to 5.26 I can confirm that it does indeed behave in the same way. And yeah, my panels got all messed up after downgrade. So kudos to whoever rewrote multi-display handling for 5.27. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464762] New: Cursor harder to move between screens if those are set to appear at different height relative to each-other.
https://bugs.kde.org/show_bug.cgi?id=464762 Bug ID: 464762 Summary: Cursor harder to move between screens if those are set to appear at different height relative to each-other. Classification: Plasma Product: KScreen Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- Created attachment 155563 --> https://bugs.kde.org/attachment.cgi?id=155563&action=edit doodle Since 5.27 rewrite it's harder to move the cursor diagonally between screens if those are set at different height, or if one is bigger than the other. It used to be possible to move cursor smoothly between workspaces, not there's no approximation on "empty space", and so cursor hits "brick wall". Seems like a regression, is it going to be reintroduced, or is it deemed as an unnecessary complexity? Little explanation in attachments, as I'm not sure if my explanation is clear. In short, it messes with my muscle memory. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464760] New: Not possible to overlap screens anymore on multiscreen setups.
https://bugs.kde.org/show_bug.cgi?id=464760 Bug ID: 464760 Summary: Not possible to overlap screens anymore on multiscreen setups. Classification: Plasma Product: KScreen Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- It seems that since 5.27 rewrite it's not possible to arrange screens, so that one of them overlaps the other. Is it an intentional simplification? It was useful in my case, since my "desk" is small, and if I chose to keep laptop lid up (for wifi strength) it would be possible to sacrifice a small chunk of space for smoother transition. And gain extra space at little cost. 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-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #119 from petrk --- Seems resolved in my case, so far. I use a laptop with Optimus setup. Nvidia drivers pinned at 520.56.06 because latest version breaks Optimus on my system. But that's on Nvidia probably. Observed result: External screen wakes up, there is a bunch of internal screen backlight flicker before the other monitor powers on. 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-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 464578] Kwin produces window border, despite borders being disabled in breeze.
https://bugs.kde.org/show_bug.cgi?id=464578 --- Comment #5 from petrk --- What makes this "outline" not a border, since it looks like a line, and it surrounds the window? Guess "no border" option in deco settings needs to say "itty-bitty border" from now on. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 464578] Kwin produces window border, despite borders being disabled in breeze.
https://bugs.kde.org/show_bug.cgi?id=464578 --- Comment #3 from petrk --- How do I disable it then? I don't want to switch compositors because of the "outline". Breeze is not the only style which is affected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464578] New: Kwin produces window border, despite borders being disabled in breeze.
https://bugs.kde.org/show_bug.cgi?id=464578 Bug ID: 464578 Summary: Kwin produces window border, despite borders being disabled in breeze. Classification: Plasma Product: kwin Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- Created attachment 155464 --> https://bugs.kde.org/attachment.cgi?id=155464&action=edit screenshot Kwin draws thin window border, overriding systemsettings breeze options. Is this a regression, or intended change? Either way, there's a dedicated setting in breeze for it, and it should be respected. Suspending kwin removes the border. 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-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462649] New: Composited desktop unusable with Nvidia 525.60.11 switchable graphics when only external screen is being driven
https://bugs.kde.org/show_bug.cgi?id=462649 Bug ID: 462649 Summary: Composited desktop unusable with Nvidia 525.60.11 switchable graphics when only external screen is being driven Classification: Plasma Product: kwin Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- Created attachment 154317 --> https://bugs.kde.org/attachment.cgi?id=154317&action=edit nvidia logs from affected driver version Now, here's a disclaimer, I am quite sure that this is a problem on Nvidia's side, since reverting to 520 series of drivers fixes it. Posting it here for posterity, feel free to mark it as invalid. Here's a link to nvidia forum post I made: https://forums.developer.nvidia.com/t/525-60-11-breaks-composited-desktop-on-x11-if-laptop-lid-is-closed/236181/1 Reproducible with kwin and compiz. STEPS TO REPRODUCE 1. Use both screens on Nvidia Optimus laptop. 2. Close the lid, or disable internal screen from systemsettings. 3. External screen becomes unbearably slow, disabling compositor works arond aforementioned issue. OBSERVED RESULT Session becomes extremely slow EXPECTED RESULT Session should continue as usual with external screen. 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.11-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H RTX 2060 ADDITIONAL INFORMATION Internal screen is not affected -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #57 from petrk --- Pretty sure that this bug could be marked as depending on https://bugs.kde.org/show_bug.cgi?id=450068 since connector IDs are volatile, and there's no permanent fix until that is solved in a robust way. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else
https://bugs.kde.org/show_bug.cgi?id=450068 petrk changed: What|Removed |Added CC||pepk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443742] Option to show subcategory structure
https://bugs.kde.org/show_bug.cgi?id=443742 petrk changed: What|Removed |Added CC||pepk...@gmail.com --- Comment #24 from petrk --- I would like to vote for respecting structure, at least optionally. Say, user installs easyeffects/pulseeffects, it pulls LSP Plugins, which adds ~130 elements to menu, cluttering Multimedia section completly. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #21 from petrk --- Not sure if it's a duplicate, as layout is remembered (until it isn't). My problem is with monitor not powering on when layout is changed, say from "internal only" to "extend". All I get is a laptop screen flicker, until I spam layout change enough times. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460685] Kscreen has issues turning on external monitor
https://bugs.kde.org/show_bug.cgi?id=460685 petrk changed: What|Removed |Added Summary|Kscreen 5.26 appears to |Kscreen has issues turning |break my DP monitor |on external monitor Version|5.26.0 |5.26.1 Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO Keywords|regression |multiscreen --- Comment #1 from petrk --- After more spamming of Super + P it turns out that both beta and 5.26.1 are about the same when it comes to reliability of switching my display on. I have no idea what to do at this point, ever since I got this display I have bad experience with Plasma. What I don't understand is that kscreen struggles powering it on, but if I logout to SDDM or switch to TTY, then it powers right up no problem. Right now it's connected via USB-C to DP. If I trigger it then I lose connection with its USB dock, it's on a separate USB3 cable. logout fixes the issue. Spamming Super+P fixes it as well. Any pointers at where to dig? Priority can be lowered I am afraid, not a regression. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460685] New: Kscreen 5.26 appears to break my DP monitor
https://bugs.kde.org/show_bug.cgi?id=460685 Bug ID: 460685 Summary: Kscreen 5.26 appears to break my DP monitor Classification: Plasma Product: KScreen Version: 5.26.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- Issue: If external screen powers off, then I can't make it display anything, all I get is a flickering internal monitor, and and no output on external screen. Screen settings keeps refreshing, same with nvidia-settings. It seems that kscreen 5.26 and 5.26.1 breaks my external display. I suspected Nvidia, so downgraded from 520.56.06 to 515.76, but it didn't solve the issue. Disabling kscreen service and relying on nvidia-xconfig helped, but then I lost ability do switch to external only on "lid close". Downgraded to 5.26, then 5.25.90 and finally layout switching works as intended. Right now I'm running RTX 2060 on an AMD laptop with internal GPU disabled in BIOS. Screen is a 1440p@165hz, using DP cable, 1080o@144hz internal. Operating System: Arch Linux KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2 System Version: Lenovo Legion 5 15ARH05H -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459902] New: Update logind.conf while setting lid actions from systemsettings
https://bugs.kde.org/show_bug.cgi?id=459902 Bug ID: 459902 Summary: Update logind.conf while setting lid actions from systemsettings Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_powerdevil Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com CC: k...@privat.broulik.de Target Milestone: --- So here is some background. I'm using my laptop with lid down, since 32" is more usable than 15". I told systemsettings to ignore the lid switch when it's on running with external power. Here's the problem, when I tell my system to shutdown while lid is down, it half kills the session and goes to sleep instead. After waking up all I get is a black screen and cursor, restarting sddm gets me fully functional system. I was puzzled at first, coming from work and I could have sworn that I pressed shutdown in plasma. Turns out that after session is done, logind takes over (my theory at least) and whatever is in logind.conf takes priority. After setting "HandleLidSwitch and HandleSuspendKey, just for good measure to "ignore" my system shuts down even with lid down. Does logind even support what powerdevil with plasma can do? Having multiple options for different power supply states I mean. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 459568] Keyboard output is being ignored after waking up when in "Unify outputs" mode.
https://bugs.kde.org/show_bug.cgi?id=459568 --- Comment #4 from petrk --- Sure thing, I will come back if it happens again and it is doing it reliably. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 459568] Keyboard output is being ignored after waking up when in "Unify outputs" mode.
https://bugs.kde.org/show_bug.cgi?id=459568 --- Comment #2 from petrk --- I went back to 5.25 and couldn't trigger it either through Wayland or Xorg session. Now I went back to beta and I can't trigger it on either session as well, that's rather puzzling. However I did have some resume issues with Wayland, once I was greeted with breeze cursor on black background on both screens. Had to restart session, but I considered it unreliable with Nvidia and am avoiding it. 1. After going back and forth I can't trigger it either on stable not beta. 2. Wayland works, but it has other problems with Nvidia. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459548] Cursor is leaving corrupted trail behind. Switchable graphics, Nvidia driven screen.
https://bugs.kde.org/show_bug.cgi?id=459548 --- Comment #5 from petrk --- Created attachment 152376 --> https://bugs.kde.org/attachment.cgi?id=152376&action=edit qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459548] Cursor is leaving corrupted trail behind. Switchable graphics, Nvidia driven screen.
https://bugs.kde.org/show_bug.cgi?id=459548 --- Comment #4 from petrk --- Created attachment 152375 --> https://bugs.kde.org/attachment.cgi?id=152375&action=edit drm_info output -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 459568] New: Keyboard output is being ignored after waking up when in "Unify outputs" mode.
https://bugs.kde.org/show_bug.cgi?id=459568 Bug ID: 459568 Summary: Keyboard output is being ignored after waking up when in "Unify outputs" mode. Classification: Plasma Product: kscreenlocker Version: 5.25.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Today I stumbled on an interesting bug, I couldn't input my password after resume to ram, lockscreen was staying empty. I tested in all modes provided by Kscreen OSD and it turns out that I can reliably prevent myself from unlocking session by choosing "Unify outputs". All other options in Super+P menu work fine. STEPS TO REPRODUCE 1. Switch to "Unify outputs" 2. Put PC to sleep 3. Wake up and try to unlock with password 4. Password field stays empty OBSERVED RESULT Password field remains empty, have to switch tty and do what's necessary to reach desktop. EXPECTED RESULT Password field should accept keystrokes. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.10-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Nvidia 515.76 Two screens, one at 1080p, another at 1440p. Both @ 144hz. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459560] Show output change applet on screen where cursor is.
https://bugs.kde.org/show_bug.cgi?id=459560 --- Comment #3 from petrk --- I am not sure to be honest, would have to download older image. It seems like a nice option to me regardless. That's how dashboard used to work before it was changed for some reason. Whoever reworked multiscreen for this version, nice work. It's appears more robust now. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459560] New: Show output change applet on screen where cursor is.
https://bugs.kde.org/show_bug.cgi?id=459560 Bug ID: 459560 Summary: Show output change applet on screen where cursor is. Classification: Plasma Product: KScreen Version: 5.25.90 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Plasma Applet Assignee: kscreen-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- SUMMARY Layout change OSD shows up on main screen, not where cursor is right now. Could it be changed to follow cursor to currently active screen? STEPS TO REPRODUCE 1. Hit Super+P or equivalent on keyboard. 2. OSD pops up on a screen which is set as main output, while my head expects it on screen where mouse cursor is right now. 3. Confusion, muscle memory tells me that it used to follow cursor, can't confirm though. I haven't used multiple screens for a while. OBSERVED RESULT OSD pops up on my "main" screen, then I have to move my mouse over to that screen, or use arrow keys. EXPECTED RESULT OSD should show up on currently active screen. Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.10-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR I am not sure what it was like before, however I am 100% sure, that behaviour of Application Dashboard used to behave how I describe, could be related if it's a regression. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459548] Cursor is leaving corrupted trail behind. Switchable graphics, Nvidia driven screen.
https://bugs.kde.org/show_bug.cgi?id=459548 --- Comment #2 from petrk --- (In reply to Nate Graham from comment #1) > Is this a new issue in the Plasma 5.26 beta? Or has it always been like this > in 5.25 or earlier? Just reverted to 5.25.5, and I can confirm that it happens there as well. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 459549] New: Add support for switchable graphics in kinfocenter
https://bugs.kde.org/show_bug.cgi?id=459549 Bug ID: 459549 Summary: Add support for switchable graphics in kinfocenter Classification: Applications Product: kinfocenter Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: About this System Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com CC: sit...@kde.org Target Milestone: --- SUMMARY Since switchable graphics are a norm for a few years no, it seems like a good idea to me to show second GPU on hardware info screen. External screens are usually being wired through another GPU, which can expose bugs that are present on let's say Nvidia. Having driver version as well may be beneficial, but optional. It's just seems like a convenience feature to me. Here's what I have in mind: Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.10-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Secondary Graphics Processor: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] (rev a1) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 459548] New: Cursor is leaving corrupted trail behind. Switchable graphics, Nvidia driven screen.
https://bugs.kde.org/show_bug.cgi?id=459548 Bug ID: 459548 Summary: Cursor is leaving corrupted trail behind. Switchable graphics, Nvidia driven screen. Classification: Plasma Product: kdeplasma-addons Version: 5.25.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Dashboard Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- Created attachment 152354 --> https://bugs.kde.org/attachment.cgi?id=152354&action=edit issue captured with obs SUMMARY Cursor leaves corrupted trail, video file attached. Can't trigger it on internal screen so my guess is that it's Nvidia issue. STEPS TO REPRODUCE 1. Open dashboard and move cursor around. 2. Corrupted rectangular area is trailing cursor. OBSERVED RESULT Black rectangular trail. EXPECTED RESULT Uncorrupted output. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.10-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Secondary Graphics Processor: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] (rev a1) Nvidia with "nvidia_drm.modeset=1", no external screen otherwise, wayland as well probably. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 459547] New: Items elided despite having enough space in search mode, horizontal scroll bar always present in search mode.
https://bugs.kde.org/show_bug.cgi?id=459547 Bug ID: 459547 Summary: Items elided despite having enough space in search mode, horizontal scroll bar always present in search mode. Classification: Plasma Product: kdeplasma-addons Version: 5.25.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Dashboard Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- Created attachment 152353 --> https://bugs.kde.org/attachment.cgi?id=152353&action=edit search results SUMMARY As seen in screenshot, item area is search mode is being limited despite being on a 1080p screen. That shouldn't happen. It doesn't happen for every phrase that's being searched, but horizontal scroll bar is is being shown on all queries. STEPS TO REPRODUCE 1. Search for "nvi", that's most reliable way for me to trigger it, also starting with letter "J". 2. Results are being constrained to the point of being unreadable. OBSERVED RESULT Unreadable text at worst, unnecessary scroll bars at least. EXPECTED RESULT All items clearly visible, no unnecessary constraints. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.10-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Secondary Graphics Processor: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] (rev a1) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400461] Cursor doesn't change or fails to revert to pointer while using zoom effect (Firefox and Thunderbird)
https://bugs.kde.org/show_bug.cgi?id=400461 petrk changed: What|Removed |Added Version|5.24.5 |5.25.90 --- Comment #12 from petrk --- Still a thing. Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.10-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Nvidia 515.65.01 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 393792] [Wayland]Dashboard not scaled properly if previously used and screen with different resolution.
https://bugs.kde.org/show_bug.cgi?id=393792 petrk changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from petrk --- Tested on 5.25.90, dashboard only shows up on monitor which has taskbar, so kind of fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459407] External monitor wallpaper gets corrupted with second wallpaper if external screen has higher resolution.
https://bugs.kde.org/show_bug.cgi?id=459407 --- Comment #3 from petrk --- I think I also saw something similar happen to logout screen as well. I'll wait for 5.26, and report back if it happens again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459368] Plasma very unstable when attached to docking station
https://bugs.kde.org/show_bug.cgi?id=459368 --- Comment #13 from petrk --- (In reply to David Edmundson from comment #12) > WIP at https://invent.kde.org/plasma/kscreen/-/merge_requests/132 I tried to recompile with this patch, turns out Arch Linux changed some defaults in how it handles extracted sources since I last played with makepkg. User error, disregard comment 5. Anyways, patched for sure this time: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fcc2c3666cf in QWindow::setVisible (this=, visible=false) at kernel/qwindow.cpp:623 Downloading 0.08 MB source file /usr/src/debug/qtbase/src/gui/kernel/qwindow.cpp 623 d->setVisible(visible); [Current thread is 1 (Thread 0x7fcc27a0a840 (LWP 3795))] (gdb) bt #0 0x7fcc2c3666cf in QWindow::setVisible (this=, visible=false) at kernel/qwindow.cpp:623 #1 0x7fcc2bfc0381 in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #2 doActivate (sender=0x55fad97e8a20, signal_index=0, argv=0x7fffb50a0a20) at kernel/qobject.cpp:3919 #3 0x7fcc2bfc0724 in QObject::destroyed (this=, _t1=) at .moc/moc_qobject.cpp:219 #4 0x7fcc2bfb6cec in QObject::~QObject (this=, this=) at kernel/qobject.cpp:1010 #5 0x7fcc2d28272a in KScreen::Output::~Output (this=, this=) at /usr/src/debug/libkscreen-5.25.90/src/output.cpp:176 #6 QtSharedPointer::CustomDeleter::execute (this=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:187 #7 QtSharedPointer::ExternalRefCountWithCustomDeleter::deleter (self=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:205 #8 0x55fad8aadb59 in QtSharedPointer::ExternalRefCountData::destroy ( this=0x55fad98141a0) at /usr/include/qt/QtCore/qsharedpointer_impl.h:149 #9 QSharedPointer::deref (dd=0x55fad98141a0) at /usr/include/qt/QtCore/qsharedpointer_impl.h:458 #10 QSharedPointer::deref (dd=0x55fad98141a0) at /usr/include/qt/QtCore/qsharedpointer_impl.h:454 #11 QSharedPointer::deref (this=0x55fad9882460) at /usr/include/qt/QtCore/qsharedpointer_impl.h:453 #12 QSharedPointer::~QSharedPointer (this=0x55fad9882460, -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459405] "kwin_core: Got invalid presentation timestamp" spams logs if switched to display on external screen only, Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=459405 --- Comment #5 from petrk --- Thanks, less clutter in logs now. If I decide to follow up on that, should I nag Mesa or Nvidia? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459407] External monitor wallpaper gets corrupted with second wallpaper if external screen has higher resolution.
https://bugs.kde.org/show_bug.cgi?id=459407 --- Comment #1 from petrk --- Appears to be fixed in 5.25.90. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459368] Plasma very unstable when attached to docking station
https://bugs.kde.org/show_bug.cgi?id=459368 --- Comment #6 from petrk --- Created attachment 152233 --> https://bugs.kde.org/attachment.cgi?id=152233&action=edit backtrace Attaching backtrace, hope it has something useful in it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459368] Plasma very unstable when attached to docking station
https://bugs.kde.org/show_bug.cgi?id=459368 petrk changed: What|Removed |Added CC||pepk...@gmail.com --- Comment #5 from petrk --- (In reply to ratijas from comment #4) > Maybe this will fix it: > https://invent.kde.org/plasma/kscreen/-/merge_requests/132 I am also seeing some instability with 5.25.90. skcreen_osd_service crashes on exit but it does its job Tried recompiling with 18171d60 applied, but it still crashes. Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H Will try to get trace and come back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459407] New: External monitor wallpaper gets corrupted with second wallpaper if external screen has higher resolution.
https://bugs.kde.org/show_bug.cgi?id=459407 Bug ID: 459407 Summary: External monitor wallpaper gets corrupted with second wallpaper if external screen has higher resolution. Classification: Unclassified Product: plasmashell Version: 5.25.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 152231 --> https://bugs.kde.org/attachment.cgi?id=152231&action=edit Issue present on a screenshot SUMMARY I run two displays, 1080p internal and 1440p external, external is being driven by Nvidia, as verified by gpu not idling in nvidia-settings. If I set same resolution for both displays, changing screen layouts proceeds smoothly with no glitches, howerver if external runs at higher resolution and I switch to external only, I get wallpaper corruption. STEPS TO REPRODUCE 1. Set higher resolution on secondary screen. 2. Switch between internal only, extended, and finally to external only, just to make sure that more than one wallpaper is cached. 3. In external only mode two wallpapers are present, main on the left, and a piece of second on the right. 4. Clicking on desktop makes main wallpaper span whole desktop, switching to some application brings the glitch back, clicking back and forth fixes it eventually. OBSERVED RESULT Two wallpapers are present on a single screen EXPECTED RESULT Only one wallpaper should be present when only one screen is being driven. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: LENOVO Product Name: 82B1 System Version: Lenovo Legion 5 15ARH05H -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 petrk changed: What|Removed |Added CC||pepk...@gmail.com --- Comment #410 from petrk --- Similar issue here, If I change outputs sometimes panel doesn't move. It even disappeared entirely, got it back by fiddling with "Super+P". I run with switchable graphics laptop, external outputs are wired to Nvidia RTX 2060. Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459405] New: "kwin_core: Got invalid presentation timestamp" spams logs if switched to display on external screen only, Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=459405 Bug ID: 459405 Summary: "kwin_core: Got invalid presentation timestamp" spams logs if switched to display on external screen only, Nvidia Optimus Classification: Unclassified Product: kwin Version: 5.25.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- Created attachment 152230 --> https://bugs.kde.org/attachment.cgi?id=152230&action=edit Logs from kwin_x11 --replace when issue appeared SUMMARY kwin_core spams logs with around 2000 messages per minute with: kwin_core: Got invalid presentation timestamp: 0 (current "redacted number") Spam only happens when only external display is being driven. STEPS TO REPRODUCE 1. Switch to render on external display only. 2. do kwin_x11 --replace. 3. Log spam starts. 3. Switch either to "internal only", "extend(left or ritght)". 4. Spam stops 5. If switched to external only, spam resumes. OBSERVED RESULT Spam in logs, yesterday I counted around 2k lines per minute. EXPECTED RESULT No journalctl tripping logrotate quite often SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Secondary Graphics Processor: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] (rev a1) ADDITIONAL INFORMATION I encountered this problem by accident, because there are some graphical glitches happening since I connected to an external screen. Both displays run at 144hz, internal resolution: 1920x1080, external: 2560x1440. External screen is being driven by Nvidia, as it idles when external display is not in use. No Optimus configuration was made, games work on Nvidia without configuration so I didn't bother. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 459264] 5.25.90 Can't see full profile names in systemsettings applet for audio devices.
https://bugs.kde.org/show_bug.cgi?id=459264 --- Comment #1 from petrk --- Created attachment 152145 --> https://bugs.kde.org/attachment.cgi?id=152145&action=edit screenshot from stable version Same window after reverting to 5.25.5 As you can see, profile names are readable now. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454328] Can't type password immediately, keystrokes "get eaten" otherwise
https://bugs.kde.org/show_bug.cgi?id=454328 petrk changed: What|Removed |Added CC||pepk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454328] New: Can't type password immediately, keystrokes "get eaten" otherwise
https://bugs.kde.org/show_bug.cgi?id=454328 Bug ID: 454328 Summary: Can't type password immediately, keystrokes "get eaten" otherwise Product: kscreenlocker Version: 5.24.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY It appears that in 5.25 beta lockscreen was given some overhaul. Before that I was able to type in my password and press enter even if screen was displaying clock. Now it ignores keys until password field starts showing. Is that intended behavior? I would assume in the name of "security" if true. Now if it's intended, may I suggest doing it like Microsoft and asking user to press Enter, or do a swipe up gesture before password could be inserted? Otherwise it's just looks like UI is lagging from my perspective. STEPS TO REPRODUCE 1. Lock screen 2. Start typing 3. Keys are being ignored until lockscreen displays password field OBSERVED RESULT Can't type my password from muscle memory, unless I want to see "password incorrect" answer. EXPECTED RESULT Screenlocker should parse input as before. 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-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3720QM CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
