[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 #80 from r0ck3r --- Bug appeared again for me on 5.26.4 -- 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 #78 from r0ck3r --- (In reply to Benny Zen from comment #76) > Unfortunately, I'm not that lucky. It's not fixed for me. Still experiencing > the very same bug as before. This is strange. So, probably, I've did something to disappear this bug. In plasma 5.26.3 I have disabled kscreen service and used autorandr as autoinit script and after upgrade I have configured screens in plasma settings, started kscreen service, disabled autorandr and rebooted. May be, there can be a workaround. Could it be configuring screens with kscreen stopped? -- 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 #75 from r0ck3r --- Just upgraded to plasma-5.26.4 in Fedora 37 and looks like bug is fixed -- 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 #73 from r0ck3r --- (In reply to Rainer Klier from comment #71) > (In reply to r0ck3r from comment #70) > > and Plasma 5.26. I have tried to downgrade NVIDIA drivers to 470xx version, > > but no result. > > yes, i didn't post this yet, but i also use the 470 version of the nvidia > driver, since the old GeForce GTX 765M GPU isn't supported any more by other > driver versions, and as i wrote in the initial post, this problem is > affecting me. > > so it seems to happen with all current nvidia drivers (470, 510, 515, 525). yeah, looks so -- 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 #72 from r0ck3r --- To provoke this bug is enought to run xset dpms force off and wait for about 30 sec, and move mouse cursor after that. I have triple monitor configuration and my main display, which is connected to DisplayPort, can't start. Rest two monitors, that is connected to HDMI, shows visual glitches. Disable kscreen service and using autorandr as autostart script can workaround this -- 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 r0ck3r changed: What|Removed |Added CC||r0c...@bk.ru --- Comment #70 from r0ck3r --- I can confirm, that this is happening only with Nvidia proprietary driver and Plasma 5.26. I have tried to downgrade NVIDIA drivers to 470xx version, but no result. On nouveau bug did not happens -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 362058] Dual monitor loses settings after screen sleep
https://bugs.kde.org/show_bug.cgi?id=362058 --- Comment #13 from r0ck3r --- I have very stange things after upgrading to Fedora 37. On Fedora 36 I had troubles after waking up displays from power save mode, such as loosing positions of windows, panels and widgets. After upgrading to 37 my middle display, connected to DP, won't start at all after powersave and I have massive visual glitches on left and right displays. By pressing Ctrl+Alt+F12 and disabling graphic effects, glitches are gone, but I still can't enable main display. I try to enable this display manual via kscreen settings, but with no luck. Sometimes, I can do that, but almost - no. When I reboot my PC, middle display stays disabled. Only what I can do - is switching to Wayland, reconfiguring displays and start Xorg again. After this, display works as expected until next powersave. Another strange thing: after I have this bug, when I try to logout from KDE to switch to Wayland, SDDM freezes. But it is shown on all displays -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 362058] Dual monitor loses settings after screen sleep
https://bugs.kde.org/show_bug.cgi?id=362058 r0ck3r changed: What|Removed |Added Version|5.19.5 |5.26.3 Platform|Manjaro |Fedora RPMs --- Comment #12 from r0ck3r --- Output: 445 DVI-D-0 disabled disconnected DVI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 446 HDMI-0 enabled connected HDMI Modes: 447:1920x1080@60*! 448:1920x1080@75 449:1920x1080@60 450:1920x1080@50 451:1920x1080@60 452:1920x1080@50 453:1680x1050@60 454:1280x1024@75 455:1280x1024@60 456:1280x960@60 457:1280x720@60 458:1280x720@60 459:1280x720@50 460:1024x768@75 461:1024x768@70 462:1024x768@60 463:800x600@75 464:800x600@72 465:800x600@60 466:800x600@56 467:720x576@50 468:720x480@60 469:640x480@75 470:640x480@73 471:640x480@72 472:640x480@60 473:640x480@60 Geometry: 4480,360 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 474 HDMI-1 enabled connected HDMI Modes: 447:1920x1080@60*! 448:1920x1080@75 449:1920x1080@60 450:1920x1080@50 451:1920x1080@60 452:1920x1080@50 453:1680x1050@60 454:1280x1024@75 455:1280x1024@60 456:1280x960@60 457:1280x720@60 458:1280x720@60 459:1280x720@50 460:1024x768@75 461:1024x768@70 462:1024x768@60 463:800x600@75 464:800x600@72 465:800x600@60 466:800x600@56 467:720x576@50 468:720x480@60 469:640x480@75 470:640x480@73 471:640x480@72 472:640x480@60 473:640x480@60 Geometry: 0,360 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 475 DP-0 enabled connected primary DisplayPort Modes: 447:1920x1080@60 449:1920x1080@60 450:1920x1080@50 453:1680x1050@60 454:1280x1024@75 455:1280x1024@60 457:1280x720@60 458:1280x720@60 459:1280x720@50 460:1024x768@75 461:1024x768@70 462:1024x768@60 463:800x600@75 464:800x600@72 465:800x600@60 466:800x600@56 467:720x576@50 468:720x480@60 469:640x480@75 470:640x480@73 472:640x480@60 476:2560x1440@144*! 477:2560x1440@120 478:2560x1440@100 479:2560x1440@60 480:1600x900@60 481:1440x900@60 482:1280x800@60 483:1152x864@75 Geometry: 1920,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown primary Output: 484 DP-1 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 485 DP-2 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 486 DP-3 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 362058] Dual monitor loses settings after screen sleep
https://bugs.kde.org/show_bug.cgi?id=362058 --- Comment #11 from r0ck3r --- It was after fail. Next will be before -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 362058] Dual monitor loses settings after screen sleep
https://bugs.kde.org/show_bug.cgi?id=362058 r0ck3r changed: What|Removed |Added CC||r0c...@bk.ru --- Comment #10 from r0ck3r --- Output: 445 DVI-D-0 disabled disconnected DVI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 446 HDMI-0 enabled connected HDMI Modes: 447:1920x1080@60*! 448:1920x1080@75 449:1920x1080@60 450:1920x1080@50 451:1920x1080@60 452:1920x1080@50 453:1680x1050@60 454:1280x1024@75 455:1280x1024@60 456:1280x960@60 457:1280x720@60 458:1280x720@60 459:1280x720@50 460:1024x768@75 461:1024x768@70 462:1024x768@60 463:800x600@75 464:800x600@72 465:800x600@60 466:800x600@56 467:720x576@50 468:720x480@60 469:640x480@75 470:640x480@73 471:640x480@72 472:640x480@60 473:640x480@60 Geometry: 4480,360 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 474 HDMI-1 enabled connected HDMI Modes: 447:1920x1080@60*! 448:1920x1080@75 449:1920x1080@60 450:1920x1080@50 451:1920x1080@60 452:1920x1080@50 453:1680x1050@60 454:1280x1024@75 455:1280x1024@60 456:1280x960@60 457:1280x720@60 458:1280x720@60 459:1280x720@50 460:1024x768@75 461:1024x768@70 462:1024x768@60 463:800x600@75 464:800x600@72 465:800x600@60 466:800x600@56 467:720x576@50 468:720x480@60 469:640x480@75 470:640x480@73 471:640x480@72 472:640x480@60 473:640x480@60 Geometry: 0,360 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 475 DP-0 disabled connected primary DisplayPort Modes: 447:1920x1080@60 449:1920x1080@60 450:1920x1080@50 453:1680x1050@60 454:1280x1024@75 455:1280x1024@60 457:1280x720@60 458:1280x720@60 459:1280x720@50 460:1024x768@75 461:1024x768@70 462:1024x768@60 463:800x600@75 464:800x600@72 465:800x600@60 466:800x600@56 467:720x576@50 468:720x480@60 469:640x480@75 470:640x480@73 472:640x480@60 476:2560x1440@144! 477:2560x1440@120 478:2560x1440@100 479:2560x1440@60 480:1600x900@60 481:1440x900@60 482:1280x800@60 483:1152x864@75 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown primary Output: 484 DP-1 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 485 DP-2 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442212] Laggy parabolic animation when thin tooltips enabled on Nvidia-BLOB
https://bugs.kde.org/show_bug.cgi?id=442212 r0ck3r changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |ASSIGNED Ever confirmed|0 |1 --- Comment #3 from r0ck3r --- Yes, it helps, animations goes smooth, but whithout tooltips I can't see what application I have in dock, if it have not it's own icon and displaying standart Xorg icon. Tooltips are useful for this. But they are laggy. What if we add some timeout to display tooltip? Maybe, one second after hovering? If it will not render immediately after mouse hover, there will not any lag? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442212] New: Laggy parabolic animation when thin tooltips enabled on Nvidia-BLOB
https://bugs.kde.org/show_bug.cgi?id=442212 Bug ID: 442212 Summary: Laggy parabolic animation when thin tooltips enabled on Nvidia-BLOB Product: lattedock Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: containment Assignee: mvourla...@gmail.com Reporter: r0c...@bk.ru Target Milestone: --- SUMMARY When using nvidia-blob parabolic animation is slow and laggy, but when I disable "Thin title tooltips on hovering" animations goes very smooth. As far I understand, there is some bug in nvidia-blob, but we can try to workaround it by adding some delay to show tooltip, maybe one second. Full disabling tooltips for me is not good, because I can not know what application is in dock, if it doesn't use self icon, for example, most games from Steam doesn't show game icon on dock, they uses standart Xorg icon. I've tried to research how tooltip is shown, but as far I understood, it uses QML to do this. I have never used QML, so it is hard for me STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407526] New: Plasmashell and ksysguardd uses cpu
https://bugs.kde.org/show_bug.cgi?id=407526 Bug ID: 407526 Summary: Plasmashell and ksysguardd uses cpu Product: plasmashell Version: 5.15.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: r0c...@bk.ru Target Milestone: 1.0 SUMMARY After some uptime plasma is using 100% one of my CPU cores. After killing plasmashell and rerun it - CPU usage goes normal, but after some time it happens again. Killing ksysguardd fixes this problem too, but it happens again too STEPS TO REPRODUCE 1. Add next widgets to your desktop: cpu usage, ram usage, disk usage, disk io 2. Wait for some hours OBSERVED RESULT In your CPU usage widget you will see, that cpu usage is big and plasma works very slow EXPECTED RESULT Stable work, without abnormally cpu usage SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 30 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.1 OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile -- You are receiving this mail because: You are watching all bug changes.
