[Spectacle] [Bug 377157] [Wayland] It's not possible to take a picture of a rectangle region
https://bugs.kde.org/show_bug.cgi?id=377157 AnAkkk changed: What|Removed |Added CC||anakin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387721] "screenshotArea" dbus API needs a "selectArea" method or similar
https://bugs.kde.org/show_bug.cgi?id=387721 AnAkkk changed: What|Removed |Added CC||anakin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397444] Image Copy to Clipboard does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=397444 AnAkkk changed: What|Removed |Added CC||anakin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #79 from AnAkkk <anakin...@gmail.com> --- The weird thing is that this issue does not happen with Plasma Wayland, so it is probably not only related to only "malloc", but this might be an issue in the X11 specific code. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one
https://bugs.kde.org/show_bug.cgi?id=309193 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added CC|anakin...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #45 from AnAkkk <anakin...@gmail.com> --- This issue doesn't happen with the wayland session, the CPU usage of plasmashell is always 0%. Unfortunately, the wayland session is not usable right now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #43 from AnAkkk <anakin...@gmail.com> --- How many reports does this need before this get fixed, or at least before someone tell us what kind of information is needed to fix this? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3
https://bugs.kde.org/show_bug.cgi?id=353203 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added CC|anakin...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #15 from AnAkkk <anakin...@gmail.com> --- I'm tired of this bug, and other similar ones (I'm getting high CPU usage on plasmashell even without any animation quite often) and now switched to Gnome, which isn't impacted by such bugs. I have animations with the system tray icons (e.g. kalu) in Gnome as well, but the CPU usage doesn't change and everything stay smooth. So there is definitely something that KDE/Qt doesn't do properly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #12 from AnAkkk <anakin...@gmail.com> --- Is there any info I can provide to help fix the issue, or is the cause already known? This is very annoying and cause my mouse to be very laggy every time it happens. It just needs any program to have an icon with an animation... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 349910] KWIN doesn't respect _NET_WM_BYPASS_COMPOSITOR application window property
https://bugs.kde.org/show_bug.cgi?id=349910 --- Comment #10 from AnAkkk <anakin...@gmail.com> --- That seem to be set with CS GO indeed. Does it still disable compositing for the window, even if you have an intel card? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 349910] KWIN doesn't respect _NET_WM_BYPASS_COMPOSITOR application window property
https://bugs.kde.org/show_bug.cgi?id=349910 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added CC||anakin...@gmail.com --- Comment #8 from AnAkkk <anakin...@gmail.com> --- Does that mean that is it no longer needed to disable compositing with Valve games? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358778] Blank space in system tray after upgrade 5.4.3 > 5.5.4
https://bugs.kde.org/show_bug.cgi?id=358778 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added CC||anakin...@gmail.com --- Comment #8 from AnAkkk <anakin...@gmail.com> --- I'm seeing the same blank space. Plasma 5.5.4. I don't have any crash though, and killing xembedsniproxy also makes it disappear. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #9 from AnAkkk <anakin...@gmail.com> --- This seem better than before, but I still can't use anything that have animations, since the constant CPU usage of 15% of the plasmashell process makes my laptop fan consistently spin up and spin down, this makes too much noise. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #8 from AnAkkk <anakin...@gmail.com> --- This doesn't seem to fix the issue. I mean, when there is any animation, it seems to use at least 15% CPU constantly. I don't currently have time to wait longer to see if it increase to 100% over time like it did before. Will keep octopi notifier enabled and report back. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356992] Intel Mesa drivers not supported EGL_SWAP_BEHAVIOR_PRESERVED_BIT
https://bugs.kde.org/show_bug.cgi?id=356992 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added CC||anakin...@gmail.com --- Comment #28 from AnAkkk <anakin...@gmail.com> --- There seem to be a mistake in the patch: EGLDisplay dpy = eglGetDisplay(EGL_DEFAULT_DISPLAY); if (dpy == EGL_NO_DISPLAY) dpy = eglGetDisplay(EGL_DEFAULT_DISPLAY); I guess the first line was not supposed to be changed, as this is now calling the same function again with the same parameters in case it fails. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356992] Intel Mesa drivers not supported EGL_SWAP_BEHAVIOR_PRESERVED_BIT
https://bugs.kde.org/show_bug.cgi?id=356992 --- Comment #30 from AnAkkk <anakin...@gmail.com> --- No problem :) I don't know anything about EGL, but shouldn't the call be eglGetCurrentDisplay() instead of eglGetDisplay() like it is in the updated patched version? Seems like eglGetDisplay always take a parameter. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 354151] kmailservice5 restart repeatly when no mail client is installed
https://bugs.kde.org/show_bug.cgi?id=354151 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added CC||anakin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 354151] kmailservice5 restart repeatly when no mail client is installed
https://bugs.kde.org/show_bug.cgi?id=354151 --- Comment #5 from AnAkkk <anakin...@gmail.com> --- I have the same issue, and IIRC it was also present on KDE4. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #16 from AnAkkk <anakin...@gmail.com> --- (In reply to AnAkkk from comment #13) > Writing anything in kate/konsole is very slow, it can take several seconds > for the text to appear. Restarting kwin also fixes the issue. This issue doesn't seem to be related to compositing, as I've now completely disabled it, and that seem to happen quite often. I have no idea how to debug it though. I'm having the issue right now, and writing in Yakuake is fast without any issues, but in Konsole/Kate it's very laggy and characters appear after several seconds. CPU usage looks fine, my computer doesn't feel slow at all, it's really just when writing text in these two app. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] [Optimus] Using a window rule to turn off compositing w/ CS GO causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #19 from AnAkkk <anakin...@gmail.com> --- (In reply to Thomas Lübking from comment #18) > I'm fairly sure that what you see is a sync issue between the two graphics > chips. > Can you disable one of them in bios/uefi and check the results (also reg. > the original problems)? No, there is no option in bios/uefi to do that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #4 from AnAkkk <anakin...@gmail.com> --- No problem :) Thanks for the reply I am on ArchLinux, I had 5.5.2, and I just upgraded to 5.5.3 a few minutes ago. I'm guessing you might mean this: https://bugs.kde.org/show_bug.cgi?id=353974 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added Summary|plasmashell uses 100% CPU |plasmashell uses 100% CPU |when octopi-notifier shows |when there is an animation |that updates are available |in the task bar -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added Version|5.5.0 |5.5.2 --- Comment #1 from AnAkkk <anakin...@gmail.com> --- This is actually not specific to octopi-notifier. I just had a connection issue and the network applet kept trying to connect, which also displayed the "connection" animation in the task bar, and I had exactly the same issue. My computer was very laggy (the mouse would "jump" on the screen) and plasmashell CPU usage was increasing. Stopping the connection would fix the issue (plasmashell CPU usage would go back to 0%) and trying to connect again would bring the issue back again. For octopi, when there is an update, it changes the icon in the task bar and it's animated as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #12 from AnAkkk <anakin...@gmail.com> --- (In reply to Thomas Lübking from comment #11) > Do you have positive knowledge on the relation, ie. does killing plasmashell > remove the window? No, you're right, it doesn't actually remove the window. But I thought this was plasmashell, since it's at the place of the desktop "movable menu". > Errr... stupid question: did you optirun glxgears? No, but now I did, no difference :/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=312919 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #2 from AnAkkk <anakin...@gmail.com> --- I added two issues which seem related. Maybe https://bugs.kde.org/show_bug.cgi?id=351923 is also related? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=357099 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 357099] Stuck at connecting animation [regression]
https://bugs.kde.org/show_bug.cgi?id=357099 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added CC||anakin...@gmail.com --- Comment #4 from AnAkkk <anakin...@gmail.com> --- I think I had the same problem here (high CPU usage): https://bugs.kde.org/show_bug.cgi?id=356479 This is not only specific to the network applet, but any animation on the task bar is actually causing this CPU usage issue apparently. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 312919] high CPU usage for copying notification
https://bugs.kde.org/show_bug.cgi?id=312919 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added CC||anakin...@gmail.com --- Comment #8 from AnAkkk <anakin...@gmail.com> --- Seems like this is the same as: https://bugs.kde.org/show_bug.cgi?id=356479 https://bugs.kde.org/show_bug.cgi?id=357099 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #10 from AnAkkk <anakin...@gmail.com> --- (In reply to Thomas Lübking from comment #9) > It would then probably belong to a crashed (and stopped) process? > ps ax | grep T No, nothing. xkill probably doesn't work because there is no PID attached to the window (doesn't it rely on the PID that is showed by xprop?) .Anyway, why would it belong to a crashed process, since we know it belongs to plasmashell? > What about fullscreen glxgears (you can turn it fullscreen using the Alt+F3 > menu and in doubt close it by Alt+F4 w/o unfullscreening it before) Tried, that doesn't trigger the issue either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #107 from AnAkkk <anakin...@gmail.com> --- I never had swap enabled, and didn't use infinality either. For some reason I haven't had the issue the last few days though, it looks like it fixed itself for me. I have no idea what changed, maybe this is after I updated to Plasma 5.5.2. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #8 from AnAkkk <anakin...@gmail.com> --- (In reply to Thomas Lübking from comment #7) > Idiocracy. Seriously. Whatever it is, it's idiocracy. > run "xkill" and click the window - the process it belongs to should die > afterwards > (maybe take a "ps fax" diff on before and after) xkill has no effect on it, it's still here. > ... "glxgears", sorry :-) Just tried, I don't have issues 2) and 3) with glxgears. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] New: Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 Bug ID: 357116 Summary: Using a window rule to turn off compositing causes flickering windows when compositing is turned back on Product: kwin Version: 5.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: anakin...@gmail.com I am now using a window rule to turn off compositing when I launch CS GO. When I exit CS GO, I see lot of flickering problems. For example, it happens to the decorations around some windows (although not all the time). It also just happened to the place where the yakuake window was (yakuake is hidden), when I switch between windows, I see a black window flickering at the same place as this window was. Grabbing a fullscreen window title bar (like firefox) and then moving it around causes huge flickering all over the screen. I am on a laptop with an optimus setup, so everything runs on the intel card, and the game on the nvidia card. The only way I have found to fix the issue is to restart kwin. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #3 from AnAkkk <anakin...@gmail.com> --- To be more precise, I get 2) and 3) only when the compositor suspended by the rules and reenabled. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #2 from AnAkkk <anakin...@gmail.com> --- (In reply to Thomas Lübking from comment #1) > Sounds like a buffer age problem. KWin still running on the intel chip? Yes, it is. Apparently, I have 3 different issues: 1) A black square in the top left corner when compositing is disabled, which is put on top of every window, this is actually the "button" which is on plasma desktop to access the desktop settings menu etc, for some reason it's totally black with compositing disabled. Happens even with ALT-SHIFT-F12. So actually that black square appears on top of the game as well. This disappear when reenabling the compositor. 2) Flickering when moving windows after compositing has been reenabled 3) Windows decorations having weird "buggy" black borders around them > Does it go away with > KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace & That seem to fix 2), but doesn't fix 3) > > Did you maybe export KWIN_EXPLICIT_SYNC=0 ? No, I'm not exporting anything specific to kwin. > You do not get this when suspending/resuming the compositor by hand? No, only when suspended with the rules. > Do you have fullscreen unredirection enabled? No, it's impossible to enable it with an intel card. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #5 from AnAkkk <anakin...@gmail.com> --- Created attachment 96290 --> https://bugs.kde.org/attachment.cgi?id=96290=edit Screenshot of firefox window after reenabling compositing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #6 from AnAkkk <anakin...@gmail.com> --- (In reply to Thomas Lübking from comment #4) > Can you "xprop" & "xwininfo" it? Output of xprop: _NET_WM_WINDOW_OPACITY(CARDINAL) = 0 Output of xwininfo: xwininfo: Window id: 0x246 (has no name) Absolute upper-left X: 0 Absolute upper-left Y: 0 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 32 Height: 32 Depth: 24 Visual: 0x20 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x22 (installed) Bit Gravity State: ForgetGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: yes Corners: +0+0 -1888+0 -1888-1048 +0-1048 -geometry 32x32+0+0 > > 3) Windows decorations having weird "buggy" black borders around them > Can you make a Screenshot? Attached a screenshot of the firefox window border. > Does it also happen if you eg. create a rule for > a) xterm > b) (windowed!) glxinfo a) No, doesn't seem to happen with xterm, maybe because it's not a fullscreen app b) windowed ? what do you mean? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #40 from AnAkkk <anakin...@gmail.com> --- Thanks for the fix :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348156] Add a feature to unredirect all fullscreen windows except some selected
https://bugs.kde.org/show_bug.cgi?id=348156 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added CC||anakin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #98 from AnAkkk <anakin...@gmail.com> --- I think the leak only happens when I play CS GO (OpenGL app) and plasmashell is running. I now stop the plasmashell process while playing, and Xorg seems to have a normal memory usage. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #28 from AnAkkk <anakin...@gmail.com> --- (In reply to Thomas Lübking from comment #26) > I meant "what if you hover the taskbar button of another minimized window" > (oc. if you should only show minimized windows in the taskbar, that's > answered) Minimized or not, this fixes the issue, as in comment #23, as long as I over anything else than CS GO. > Game -> alt+tab -> activate "something" (eg. xterm should be unsuspicious) > -> hover the games taskbar entry -> activate the game (in either way, > alt+tab or click the taskbar button) Alt-tabbed, I launched xterm through the task bar, then hovered the game taskbar entry, and I had the bug again when going back in-game. > Btw, does it also happen with the "icons-only" taskbar? I have added an icons-only taskbar, and the issue is exactly the same. What I actually noticed is that I need to apply my "fix" to both taskbars, otherwise I get the issue. This means I need to hover something else than CS GO on both taskbars. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #29 from AnAkkk <anakin...@gmail.com> --- Also tried to hover another window on the task bar, and to use the mouse wheel to switch between windows, and it fixes the bug since I am hovering something else. If I hover CS GO and do the same, I have the same issue again. So apparently as long as the last hovered window on the taskbar is the CS GO, in any case, I get the performance issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #19 from AnAkkk <anakin...@gmail.com> --- Thanks, this patch actually fix the crash :) Now it correctly disables compositing when launching CS GO. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #21 from AnAkkk <anakin...@gmail.com> --- Ok :) Do you have any idea how I can debug the plasmashell performance issue? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #9 from AnAkkk <anakin...@gmail.com> --- export __GL_YIELD="NOTHING" doesn't seem to change anything Sending the STOP signal to plasmashell seem to work. Running everything on the nvidia GPU isn't really a solution, I used to do this but this kill the battery, and make the fans spin faster. Tried to "primusrun plasmashell", and the bug is still present, it doesn't help. I am seeing the same behaviour as in bug #356366, if I click on the CS GO window to come back from the ALT-TAB, I get the bug, but if I over some other icon on the task bar (like Dolphin) and use ALT-TAB to get back in-game, I don't have the bug. I went to kwin window rules, but I can't find any option to block compositing for the window. Or maybe it's called differently here? __GL_THREADED_OPTIMIZATIONS=1 is set in the game launch script by default in all Source games, because there is a "Multicore rendering" option in the game settings which improve FPS and works with it. If I get rid of it, I would surely have lower FPS as that option would no longer work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #4 from AnAkkk <anakin...@gmail.com> --- Apparently I might not be the only one with the same issue: https://bugs.kde.org/show_bug.cgi?id=356366 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #5 from AnAkkk <anakin...@gmail.com> --- Please note that I also need to disable compositing to have the same perf as Gnome. So basically, two issues: 1) The performance issue caused by ALT-TAB and requiring me to kill plasmashell 2) Compositing, which is also causing some performance loss in the game (although less than the first issue). I guess that could be solved with "Suspend compositor for fullscreen window"? Unfortunately since the main card is an intel card, the option is unavailable for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #2 from AnAkkk <anakin...@gmail.com> --- kwin runs on the intel chip. baloo is disabled. The only processes that seem to use CPU are the game, Steam and plasmashell. I have tried to kill plasmashell, and it looks like the FPS immediately went to the same level as Gnome! Then, something interesting I could reproduce multiple times: 1) ALT-F2 -> plasmashell 2) I go back to CS GO, the performance is still the best one 3) I ALT-TAB back to desktop, then go back to CS GO, the performance is back to the "bad one" I have to kill plasmashell again to get the best performance, and can launch it once again, but if I then ALT-TAB out from the game, it brings the bad performance back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #11 from AnAkkk <anakin...@gmail.com> --- (In reply to Thomas Lübking from comment #10) > (In reply to AnAkkk from comment #9) > > Running everything on the nvidia GPU isn't really a solution > > I rather meant "for a test" - to see whether it's optimus related reg. > management of multiple contexts. > I'll try running everything on the Nvidia card later, this is a bit annoying to setup. > > I went to kwin window rules, but I can't find any option to block > > compositing for the window. Or maybe it's called differently here? > > Last tab (appearance and fixes), last item "block compositing" (I've > unfortunately no idea how it's called in the french translation) I see, the translation doesn't really match, it actually says "Compositing by blocks" in French :D (like "a block of wood") I just tried this option, and it sent a SIGSTOP message the kwin_x11 process apparently, making me totally unable to ALT-TAB, and even after putting back kwin_x11 in a normal state, it just wouldn't work, I had to use kwin_x11 --replace. > > __GL_THREADED_OPTIMIZATIONS=1 is set in the game launch script by default in > > While __GL_THREADED_OPTIMIZATIONS should get you a benefit on multicore > systems, I doubt it has actual impact on multicore rendering (which should > work just as much) Removing __GL_THREADED_OPTIMIZATIONS doesn't actually change anything, it doesn't solve the issue and doesn't change the FPS either apparently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #15 from AnAkkk <anakin...@gmail.com> --- (In reply to Thomas Lübking from comment #14) > Just "i18n" - ki18n is the translation infrastructure, not the translated > strings. > I filed a bug and attached you, I cannot really handle this (my french is by > far not good enough to lector others ;-) Thanks :) > echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope # allow attaching gdb > gdb --pid PID_OF_STOPPED_KWIN 2>&1 | tee stopped_kwin.gdb > thread apply all bt Thread 4 (Thread 0x7fb6d52af700 (LWP 3797)): #0 0x7fb6ec88f18d in poll () from /usr/lib/libc.so.6 #1 0x7fb6eab7fae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fb6eab81757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fb6d5b51379 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fb6eae3db8e in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fb6ecb5a4a4 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fb6ec89813d in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fb6cf678700 (LWP 3845)): #0 0x7fb6ec890e23 in select () from /usr/lib/libc.so.6 #1 0x7fb6eb070c1f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib/libQt5Core.so.5 #2 0x7fb6eb0726f7 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib/libQt5Core.so.5 #3 0x7fb6eb072bfe in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fb6eb01c57a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fb6eae38be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fb6e5af8055 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7fb6eae3db8e in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fb6ecb5a4a4 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fb6ec89813d in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fb6ccac8700 (LWP 3855)): #0 0x7fb6ecb6007f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb6e9fa1934 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7fb6e9fa1979 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7fb6ecb5a4a4 in start_thread () from /usr/lib/libpthread.so.0 ---Type to continue, or q to quit--- #4 0x7fb6ec89813d in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fb6ecfa7840 (LWP 3796)): #0 0x7fb6ec86791d in nanosleep () from /usr/lib/libc.so.6 #1 0x7fb6ec8677b4 in sleep () from /usr/lib/libc.so.6 #2 0x7fb6e5617d8a in ?? () from /usr/lib/libKF5Crash.so.5 #3 0x7fb6e561821b in KCrash::defaultCrashHandler(int) () from /usr/lib/libKF5Crash.so.5 #4 #5 0x7fb6ec44cdfd in ?? () from /usr/lib/libkwin.so.5 #6 0x7fb6eb04e200 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #7 0x7fb6eb9119ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #8 0x7fb6eb916e86 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #9 0x7fb6eb01ebab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #10 0x7fb6eb020fa6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #11 0x7fb6eb072ac2 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #12 0x7fb6d5bb821d in ?? () from /usr/lib/libQt5XcbQpa.so.5 #13 0x7fb6eb01c57a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #14 0x7fb6eb02453c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #15 0x7fb6ecd757cb in kdemain () from /usr/lib/libkdeinit5_kwin_x11.so #16 0x7fb6ec7cf610 in __libc_start_main () from /usr/lib/libc.so.6 #17 0x004007c9 in _start () Unfortunately there are no debug symbols on Arch :/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #16 from AnAkkk <anakin...@gmail.com> --- I removed the "strip" option and recompiled kwin: #5 0x7f14261c462d in KWin::SceneOpenGLShadow::~SceneOpenGLShadow() () from /usr/lib/libkwin.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #17 from AnAkkk <anakin...@gmail.com> --- >From what I can see it's crashing because the "effects" pointer is NULL inside the SceneOpenGLShadow::~SceneOpenGLShadow destructor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356938] Worse performance with KDE than Gnome when playing CS GO
https://bugs.kde.org/show_bug.cgi?id=356938 --- Comment #13 from AnAkkk <anakin...@gmail.com> --- (In reply to Thomas Lübking from comment #12) > Can you please file a bug against i18n/french? Should it be frameworks-ki18n or ki18n? > > I just tried this option, and it sent a SIGSTOP message the kwin_x11 process > > apparently > No, that's drkonqi - kwin apparently crashed, but that won't be related to > the setting (coincident) (see bug #353428) - SIGCONT will then just abort > the kwin process (you may now have a stale drkonqi process around) Indeed, I do have a drkonqi process. It crashes every time I try to use that setting though. I have tried to run everything in the nvidia card, but it's not actually possible anymore due to a bug in Xorg 1.18, which requires me to use a workaround, but then all windows are unusable, including the game menus (no cursor), see https://bugs.archlinux.org/task/47151 I tried to downgrade Xorg, but then I had files conflicting with my Nvidia packages...so I ended up just reverting all changes I've made :/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356900] Crashing plasma after double click mouse wheel on networkmanager applet
https://bugs.kde.org/show_bug.cgi?id=356900 --- Comment #2 from AnAkkk <anakin...@gmail.com> --- This seem to be a duplicate of: https://bugs.kde.org/show_bug.cgi?id=356428 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added CC||anakin...@gmail.com --- Comment #87 from AnAkkk <anakin...@gmail.com> --- I have the same issue, Arch Linux and Plasma 5.5. Xorg is currently using 1,2 GB of memory. Plasmashell 196M. It happened yesterday as well. I'm not using infinality. I don't use suspend or hibernate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] New: plasmashell uses 100% CPU when octopi-notifier shows that updates are available
https://bugs.kde.org/show_bug.cgi?id=356479 Bug ID: 356479 Summary: plasmashell uses 100% CPU when octopi-notifier shows that updates are available Product: plasmashell Version: 5.5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: anakin...@gmail.com Every time that octopi scans for updates and octopi-notifier shows that updates are available, plasmashell CPU usage slowly rise until it uses 100% of the CPU. This is very annoying and also causes my mouse to jump until I kill octopi-notifier which makes the CPU usage back to 0%. Also reported here: https://github.com/aarnt/octopi/issues/142 I'm now on Plasma 5.5, and the issue is still the same. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356415] Multiple clicks are necessary in order to activate panel elements
https://bugs.kde.org/show_bug.cgi?id=356415 --- Comment #9 from AnAkkk <anakin...@gmail.com> --- Same issue after updating to Plasma 5.5 in Arch. Antonio Rojas, could you please revert that commit in the arch package ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356415] Multiple clicks are necessary in order to activate panel elements
https://bugs.kde.org/show_bug.cgi?id=356415 AnAkkk <anakin...@gmail.com> changed: What|Removed |Added CC||anakin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
