[kwin] [Bug 494547] Parts of external screens "flickering"
https://bugs.kde.org/show_bug.cgi?id=494547 --- Comment #6 from Lech --- I've created kwin_settings.sh file in ~/.config/plasma-workspace/env and added there: export KWIN_DRM_DISABLE_TRIPLE_BUFFERING=1 This way the file is called when KDE is started and the variable is set for the whole session. It can be confirmed with "printenv". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494769] New: Some windows seem to treat dual monitors as extended display
https://bugs.kde.org/show_bug.cgi?id=494769 Bug ID: 494769 Summary: Some windows seem to treat dual monitors as extended display Classification: Plasma Product: kwin Version: 6.2.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: misc@lwp.email Target Milestone: --- SUMMARY Some windows seem to treat dual monitors as extended display - they should be placed and contained in one monitor, but are not. STEPS TO REPRODUCE 1. Open KDE on 2 monitors 2. Click "Add or manage widgets" on a panel on the secondary screen OBSERVED RESULT The dialog for searching for widgets will be split among the monitors. EXPECTED RESULT The dialog should be contained in one screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.7.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION This happens on my secondary monitor, not on the primary. My setup is Optimus laptop ASUS TUF, with the laptop screen off and external monitors connected through HDMI and USB-C->DP -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494769] Some windows seem to treat dual monitors as extended display
https://bugs.kde.org/show_bug.cgi?id=494769 --- Comment #1 from Lech --- Created attachment 174845 --> https://bugs.kde.org/attachment.cgi?id=174845&action=edit a screenshot with misplaced dialog -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494547] Parts of external screens "flickering"
https://bugs.kde.org/show_bug.cgi?id=494547 --- Comment #3 from Lech --- Thank you! export KWIN_DRM_DISABLE_TRIPLE_BUFFERING=1 for the session fixed the problem. When will it no longer be needed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494547] New: Parts of external screens "flickering"
https://bugs.kde.org/show_bug.cgi?id=494547 Bug ID: 494547 Summary: Parts of external screens "flickering" Classification: Plasma Product: kwin Version: 6.2.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: misc@lwp.email Target Milestone: --- SUMMARY After upgrading to KDE 6.2.0 on Wayland on Fedora 40, I experienced screen "flickering" on my external monitors connected to a laptop. Most visible on updating items, such as panels with widgets or movies. STEPS TO REPRODUCE 1. Run KDE 6.2.0 on Wayland on an optimus laptop with AMD Radeon 780M/NVidia 4070 graphic cards 2. Connect any external monitor (HDMI or USB-C->DP) 3. Observe the flickering on updating objects (panels, movies) on external monitors OBSERVED RESULT By "flickering" I mean very short corruptions of parts of the screen. Too short to notice what the corruptions "include", but I think sometimes garbage, sometimes parts of windows from other parts of the screen. Not sure though. Most visible on movies, because occupying bigger part of the screen (not whole image though). Tried with movies playing both in Firefox and through the system player. EXPECTED RESULT No flickering/corruption. Was perfectly fine before the update, on Plasma 6.1. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.7.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION 1. Bug present regardless if 1 or 2 external monitors is connected, and which one of them (HDMI or USB-C->DP) 2. Not present on the built-in monitor of the laptop, regardless of the refresh rate (144 Hz, or 60 Hz like the external monitors) 3. Chaning scaling on the external monitors did not help 4. I am not sure if both my external monitors are connected to the dGPU, or just one. My laptop is ASUS TUF Gaming A15 FA507XI_FA507XI -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494547] Parts of external screens "flickering"
https://bugs.kde.org/show_bug.cgi?id=494547 --- Comment #1 from Lech --- An update: after ~3 hours of work, screens started flickering very often even with all programs minimised, and kwin_wayland process started using >=62% of a single core. Closing the programs did not help, but logging out and back into KDE brought the situation back to the somewhat less intrusive flickering described in the main bug report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] New: Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 Bug ID: 496469 Summary: Memory leaks and instabilities on multi-monitor setup Classification: Plasma Product: kwin Version: 6.2.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: misc@lwp.email Target Milestone: --- SUMMARY Since about a month kwin_wayland here: 1) Uses more and more memory after external monitors have been disconnected and reconnected 2) Randomly freezes image output on one or all external monitors kwin_wayland --replace helps. STEPS TO REPRODUCE For the case (1) 1. Disconnect both external monitors, so that laptop turns on internal monitor 2. Reconnect the external monitors (the internal monitor switches off) 3. Wait, browse web pages, watch movies, etc. - the kwin_wayland process will start utilising more and more memory For the case (2) 1. Don't know. I am not sure what triggers the stop of updating of image on one of the monitors. OBSERVED RESULT Case (1) - the kwin_wayland process will start utilising more and more memory Case (2) - image on one or both external monitors stop updating. Attempting to disconnect one of the monitors hangs the system or image updates completely - only "REISUB" seems to help EXPECTED RESULT Stable performance of Plasma. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.7.2 Kernel Version: 6.11.8-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 7940HS w/ Radeon 780M Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon 780M ADDITIONAL INFORMATION This is an Optimus laptop ASUS TUF Gaming A15 FA507XI_FA507XI with laptop NVidia RTX 4070. One external monitor is connected through HDMI, the other one through USB-C->DP. I am not sure what caused the problem, since 3 things happened in very close moments: 1. Plasma update 2. Kernel update 3. NVidia drivers update -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 Lech changed: What|Removed |Added Version|6.2.3 |6.2.4 --- Comment #3 from Lech --- Is it possible that kwin developers to look into this? Using KDE now with multiple monitors is like moving into lovely Windows 95 times, with 2 Plasma restarts per day... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #5 from Lech --- (In reply to Zamundaaa from comment #4) > There's a high chance this is fixed by > https://invent.kde.org/plasma/kwin/-/merge_requests/6845, so I'm closing > this. If it still happens in 6.2.5, just reopen this bug report! Thank you. Will check when 6.2.5 reaches Fedora. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 Lech changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #9 from Lech --- I can confirm, that the issue is still present in KDE 6.2.5 on Fedora 40, making KDE barely usable on my multi-monitor NVidia Optimus laptop setup. Perhaps I'll find a way to downgrade it to 6.2.3 or it will work better on X... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #7 from Lech --- (In reply to sowieso from comment #6) > I really hope that solves it and 6.2.5 gets released soon. > I noticed that KWin returns it's memory if the second screen gets replugged > after getting unplugged once (physically pulling the HDMI cable). > Not a nice workaround, but better than having to log in again. I've noticed something like that too, although not tested extensively. However, I notice some lagging after these operations. Not sure it is related, so I am waiting for solving this bug before (hopefully not) reporting more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #13 from Lech --- Above is the log generated with sudo journalctl --boot 0 --grep=nvidia >> nvidia-memory-leak-log.txt && sudo journalctl --boot 0 --identifier=kwin_wayland >> nvidia-memory-leak-log.txt && sudo journalctl --boot 0 --identifier=kwin_wayland_wrapper >> nvidia-memory-leak-log.txt as given in https://bugs.kde.org/show_bug.cgi?id=496898. The relevant part starts on 12 Jan 10:35, as it is when I woke up my laptop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #12 from Lech --- Created attachment 177296 --> https://bugs.kde.org/attachment.cgi?id=177296&action=edit journalctl output -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #27 from Lech --- journalctl --user-unit plasma-kwin_wayland --boot 0 | grep import Journal file /var/log/journal/49739eb258bf4717b5bb4420280b45ab/system@000629a3af917a7a-efdf6713f41a1159.journal~ is truncated, ignoring file. Jan 24 19:27:45 lwpcomp4 kwin_wayland[3128]: kwin_wayland_drm: chose egl import with format AB30 and modifier 0 Jan 24 19:27:45 lwpcomp4 kwin_wayland[3128]: kwin_wayland_drm: chose egl import with format AB30 and modifier 0 Jan 24 19:27:54 lwpcomp4 kwin_wayland[3128]: kwin_wayland_drm: chose cpu import with format AR24 and modifier 0 Jan 24 19:27:55 lwpcomp4 kwin_wayland[3128]: kwin_wayland_drm: chose cpu import with format AR24 and modifier 0 wayland-info | grep NVIDIA gives nothing wayland-info | grep AMD 0x32335247 = 'GR32'; 0x02001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x32335247 = 'GR32'; 0x020010467b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x32335247 = 'GR32'; 0x020010437b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_64B,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=64B,PIPE_XOR_BITS=2 0x32335247 = 'GR32'; 0x020010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x32335247 = 'GR32'; 0x02000a04 = AMD_GFX11,GFX9_64K_D 0x48344258 = 'XB4H'; 0x02001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x48344258 = 'XB4H'; 0x020010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x48344258 = 'XB4H'; 0x02000a04 = AMD_GFX11,GFX9_64K_D 0x35314241 = 'AB15'; 0x02001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x35314241 = 'AB15'; 0x020010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x35314241 = 'AB15'; 0x02000a04 = AMD_GFX11,GFX9_64K_D 0x48344241 = 'AB4H'; 0x02001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x48344241 = 'AB4H'; 0x020010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x48344241 = 'AB4H'; 0x02000a04 = AMD_GFX11,GFX9_64K_D 0x35315241 = 'AR15'; 0x02001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x35315241 = 'AR15'; 0x020010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x35315241 = 'AR15'; 0x02000a04 = AMD_GFX11,GFX9_64K_D 0x38344258 = 'XB48'; 0x02001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x38344258 = 'XB48'; 0x020010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x38344258 = 'XB48'; 0x02000a04 = AMD_GFX11,GFX9_64K_D 0x36314752 = 'RG16'; 0x02001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x36314752 = 'RG16'; 0x020010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x36314752 = 'RG16'; 0x02000a04 = AMD_GFX11,GFX9_64K_D 0x32314241 = 'AB12'; 0x02001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x32314241 = 'AB12'; 0x020010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x32314241 = 'AB12'; 0x02000a04 = AMD_GFX11,GFX9_64K_D 0x38385247 = 'GR88'; 0x02001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x38385247 = 'GR88'; 0x020010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x38385247 = 'GR88'; 0x02000a04 = AMD_GFX11,GFX9_64K_D 0x20203852 = 'R8 '; 0x02001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x20203852 = 'R8 '; 0x020010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x20203852 = 'R8 '; 0x02000a04 = AMD_GFX11,GFX9_64K_D 0x3231564e = 'NV12'; 0x020010401b04 = AMD_GFX11,GFX9_64K_R_X
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #16 from Lech --- And I assume you tested it after waking up from sleep? The fact that it happens for several people would suggest a difference in configuration (maybe it has to be AMD+Nvidia?) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #21 from Lech --- (In reply to Zamundaaa from comment #18) > Could everyone that has the issue please comment the NVidia driver version > they're using? > > On this laptop I have driver version 565.77-12, on kernel 6.12.10 I have 565.77 (not sure how to get subnumber) on kernel 6.12.8-100.fc40.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #24 from Lech --- Here it depends on how I am using the machine. If I leave it be, kwin_wayland may gain a few GB in a few hours. If I use it, for example for web browsing, it may gain the same amount in one hour. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #14 from Lech --- Could you update us if anyone is trying to fix this issue? This is important, because due to the very serious nature of this instability and the level of unusability it causes, we may have to start looking for an alternative to KDE if no fix is planned in the near future... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #35 from Lech --- Trying to be helpful here: - are we all using optimus with the amd/intel GPU as the main one? - do we all have the external monitor ports connected to the same GPU? - are we all having this issue only when putting the laptop to sleep and waking it up? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #30 from Lech --- Did out outputs provide any clue? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498482] New: Plasma on Xorg usually crashes when waking up from sleep on multi-monitor optimus notebook
https://bugs.kde.org/show_bug.cgi?id=498482 Bug ID: 498482 Summary: Plasma on Xorg usually crashes when waking up from sleep on multi-monitor optimus notebook Classification: Plasma Product: plasmashell Version: 6.2.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: misc@lwp.email Target Milestone: 1.0 Created attachment 177262 --> https://bugs.kde.org/attachment.cgi?id=177262&action=edit journalctl log with the crash SUMMARY STEPS TO REPRODUCE 1. Put laptop and KDE to sleep by disconnecting external monitors 2. Wake up laptop by connecting external monitors OBSERVED RESULT Login screen, because Plasma has crashed. EXPECTED RESULT Standard wake up from sleep to the KDE with apps opened before going to sleep. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.2.5 ADDITIONAL INFORMATION Asus TUF gaming laptop with NVidia 4070 running on proprietary nvidia drivers in optimus mode. Two external monitors connected, one with HDMI and one with USB->DP. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 Lech changed: What|Removed |Added Version|6.2.4 |6.2.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #66 from Lech --- Still the same on 6.3.3 here :( -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #75 from Lech --- (In reply to righn from comment #74) > (In reply to Vlad Zabotinsky from comment #73) > > Any updates on this issue? Maybe any workaround? Kinda bad that i need to > > unplug my monitor 3-6 times a day. If any info is needed to understand > > problems cause, provide me guide how to get this requiered info, so i can > > provide it to you. Thanks! > > Just do kwin_wayland --replace everytime you encounter this issue. It's not > great and keep in mind most of your applications will be closed, but at > least the memory leak won't happen until the next time you unplug and replug > your monitor. Difficult to call it a workaround, if you have to close and reopen your apps several times per day (happens, if you walk with your laptop or put it to sleep, connecting and disconnecting it from external monitors). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities with NVIDIA GPUs driving multi-monitor setups
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #139 from Lech --- With a heavy heart, I am coming back to GNOME. While KDE is far more responsive, GNOME is at least stable. Restarting almost all programs a few times per day, as is the case with KDE, destroys the workflow. The sad thing is that while bugs happen, it does not seem like KDE developers are interested in fixing this one, despite the fact that it is very serious, easily reproducible, affects a significant number of people and was reported half a year ago. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities with NVIDIA GPUs driving multi-monitor setups
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #141 from Lech --- (In reply to Nick H from comment #140) > Created attachment 181202 [details] > attachment-670598-0.html > > Yes Gnome is very stable generally. I migrated over from Gnome to KDE and > love plasma's power and flexibility but I have noticed more bugs. Generally > the developers at KDE are very good at fixing them quite quickly. This is > one of the few bugs I've been involved with logging that seems to have very > little developer feedback and yet is fairly serious (but then I don't know > who in this discussion is a developer and who is not). Perhaps they have > been unable to isolate the issue so far. > Perhaps. The problem then is a lack of communication. In the current state, I have no idea if they are ignoring the issue, working on it, and the solution is almost there, or working on it, but unable to isolate the issue, etc. Thus, no idea if KDE will be stable for me in 1 week, 1 month, 1 year or never... The logical thing to do is to move to a stable environment, despite its shortcomings. As I said, with a heavy heart. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities with different GPUs driving multi-monitor setups when a screen wakes / is added
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #169 from Lech --- I can confirm that I have been running Nvidia drivers 570.153.02 on Fedora 42 for a few days without any leaks. Thank you! There are other issues, like seldom flickering of one of the screens that can be solved only with kwin_wayland --replace, corruption in LibreOffice and corruption and frequent crashes in Firefox with gfx.webrenderer.all=True (without it, FF frequently uses a lot of CPU). But that's for other bug reports. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 505047] New: Display hangs on one external monitor on NVidia/AMD Optimus laptop
https://bugs.kde.org/show_bug.cgi?id=505047 Bug ID: 505047 Summary: Display hangs on one external monitor on NVidia/AMD Optimus laptop Classification: Plasma Product: kwin Version First 6.3.5 Reported In: Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: misc@lwp.email Target Milestone: --- Created attachment 181922 --> https://bugs.kde.org/attachment.cgi?id=181922&action=edit journalctl log SUMMARY >From time to time, the display hangs on one of 2 external monitors connected to an NVidia/AMD Optimus laptop. The mouse cursor is still moving there, but nothing else gets draw/updated. Sometimes part of the display starts to flicker. The only way to fix it, known to me, is kwin_wayland --replace. Disconnecting and reconnecting the screen makes the whole screen flicker, but it displays the same image as when the hang happened. The apps are working fine and KDE is able to move them from the diconnected monitor to the connected one. Happens most often on a monitor connected through HDMI, but sometimes also on a monitor connected through USB->DP. Happens most often when using PyCharm, but not only. Happens maybe once per day. Happens also on Gnome on Wayland, but much less frequently, and on Gnome disconnecting and reconnecting the monitor fixes the issue. STEPS TO REPRODUCE 1. Use the KDE on Wayland on an Optimus Nvidia/KDE laptop with 2 external screens connected 2. Run PyCharm, work 3. Should happen at some point OBSERVED RESULT One screen stops updating. EXPECTED RESULT Everything works normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 42 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel: 6.14.8-300 GPU 1: AMD Radeon 780M GPU 2: Nvidia GeForce RTX 4070 Laptop GPU Nvidia Driver Version: 570.153.02 ADDITIONAL INFORMATION I attach journalctl log. The clock on the hung monitor froze at 11:57:43. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 505048] New: The battery charge limit is not preserved across reboots and the entry box works wrong
https://bugs.kde.org/show_bug.cgi?id=505048 Bug ID: 505048 Summary: The battery charge limit is not preserved across reboots and the entry box works wrong Classification: Plasma Product: plasmashell Version First 6.3.5 Reported In: Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Power and Battery widget Assignee: plasma-b...@kde.org Reporter: misc@lwp.email CC: k...@privat.broulik.de, natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY The battery charge limit is not preserved across reboots. Setting to, eg. 80% works until the reboot, when it has to be reset again manually, otherwise it is at 100%. In addition, setting it to 80% is not easy. Deleting "100%" in the entry text box and entering anything, or backspacing on 2 characters of "100%" causes it to fill up with "50%", while it should just fill up with the value I enter or allow me to backspace everything. Then, editing the "50%" is normal. STEPS TO REPRODUCE 1. Open the Power and Battery widget 2. Click on "Configure Power Management" icon 3. Click on "Advanced Power Settings" 4. Change (or try to change) the "Charge Limit" 5. Apply 6. Reboot OBSERVED RESULT 1) The manually set charge limit does not persist across the reboots (on, for example, Gnome, it does) 2) The text box for entering the charge limit does not work as expected EXPECTED RESULT 1) The charge limit persist across reboots 2) The charge limit textbox works like a standard textbox, not overwriting what a user tries to do SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 42 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 505071] New: The battery charge limit settings spin box works wrong
https://bugs.kde.org/show_bug.cgi?id=505071 Bug ID: 505071 Summary: The battery charge limit settings spin box works wrong Classification: Applications Product: systemsettings Version First 6.3.5 Reported In: Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_powerdevil Assignee: plasma-b...@kde.org Reporter: misc@lwp.email CC: k...@privat.broulik.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY Deleting "100%" in the spin entry text box and entering anything, or backspacing on 2 characters of "100%" causes it to fill up with "50%", while it should just fill up with the value I enter or allow me to backspace everything. Then, editing the "50%" is normal. STEPS TO REPRODUCE 1. Open the Power and Battery widget 2. Click on "Configure Power Management" icon 3. Click on "Advanced Power Settings" 4. Change (or try to change) the "Charge Limit" in the spinbox, by backspacing, or deleting the whole and entering a new value OBSERVED RESULT "50%" appears EXPECTED RESULT Only what I enter appears SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 42 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 505048] The battery charge limit is not preserved across reboots
https://bugs.kde.org/show_bug.cgi?id=505048 --- Comment #2 from Lech --- (In reply to cwo from comment #1) > Thank you for the bug report! > > Having multiple issues in one report makes them hard to track. (I can > reproduce the second but not the first, so I can't confirm this report as > is, but I could if they were separate.) Let's use this one for the battery > charge limit not being preserved. Please file a separate report for the > spinbox entry field being hard to use, in product "systemsettings", > component "kcm_powerdevil". Thanks. Submitted. Is there any info I can provide to help with this bug? If you can't reproduce, it may be hardware-dependent, but solvable, as the setting persists on GNOME. However, I am not sure what info I should give you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 505047] Display hangs on one external monitor on NVidia/AMD Optimus laptop
https://bugs.kde.org/show_bug.cgi?id=505047 --- Comment #3 from Lech --- Today another hang and no information from that time in dmesg. Can I provide some other info? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 505047] Display hangs on one external monitor on NVidia/AMD Optimus laptop
https://bugs.kde.org/show_bug.cgi?id=505047 --- Comment #2 from Lech --- Created attachment 182289 --> https://bugs.kde.org/attachment.cgi?id=182289&action=edit dmesg log The monitor hang happened at 16:13:57, and there is nothing in dmesg from that time... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 505047] Display hangs on one external monitor on NVidia/AMD Optimus laptop
https://bugs.kde.org/show_bug.cgi?id=505047 Lech changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 505047] Display hangs on one external monitor on NVidia/AMD Optimus laptop
https://bugs.kde.org/show_bug.cgi?id=505047 Lech changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Lech --- I couldn't reproduce this bug on 6.4.3 on Fedora 42 for more than a week, so I think it is indeed fixed. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 459150] New: "wrong url" when trying to open a locally stored PDF file
https://bugs.kde.org/show_bug.cgi?id=459150 Bug ID: 459150 Summary: "wrong url" when trying to open a locally stored PDF file Product: KBibTeX Version: 0.9.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Loading/saving files Assignee: fisc...@unix-ag.uni-kl.de Reporter: lech.lobo...@pw.edu.pl Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Add a local file to a reference in KBibtex 2. Try to open it (crtl-d on highlighted item) 3. OBSERVED RESULT message box comes up reporting "incorrect URL" or "wrong URL" (I am using another language) EXPECTED RESULT A PDF opening, like in previously used version SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 36 (available in About System) KDE Plasma Version: 5.25 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
