[systemsettings] [Bug 468217] xf86-input-libinput 1.3.0 DPI and mouse acceleration issue on KDE Plasma X11
https://bugs.kde.org/show_bug.cgi?id=468217 --- Comment #18 from Nikos Chantziaras --- (In reply to Martin from comment #17) > I noticed a changed mouse sensitivity after upgrading my KDE Plasma. I > searched and found this bug report and from here I got the idea of using > `xinput set-prop` command to fix it. Though I have to run it after every > boot and also when I switch to tty and back or another X instance the mouse > sensitivty gets reset so I have to re-run `xinput set-prop`. I've put the following in a .conf file inside /etc/X11/xorg.conf.d/ to disable acceleration: Section "InputClass" Identifier "My Mouse" Driver "libinput" MatchIsPointer "yes" Option "AccelProfile" "flat" Option "AccelSpeed" "0" EndSection If you already have a section for your mouse, you should instead modify that instead of creating a new one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468217] xf86-input-libinput 1.3.0 DPI and mouse acceleration issue on KDE Plasma X11
https://bugs.kde.org/show_bug.cgi?id=468217 Nikos Chantziaras changed: What|Removed |Added CC||rea...@gmail.com -- 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 Nikos Chantziaras changed: What|Removed |Added CC||rea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449870] Tray icons don't react to right click
https://bugs.kde.org/show_bug.cgi?id=449870 Nikos Chantziaras changed: What|Removed |Added CC||rea...@gmail.com --- Comment #4 from Nikos Chantziaras --- I have the exact same issue. Downgrading to 5.23.5 fixes it. A workaround is to install libappindicator, which is detected by discord and makes it use a different method to implement its tray icon. However, this is far from a good workaround because then there's no left click support anymore. Both right and left clicking on the tray icon will simply open the same context menu. Normally, what you want is not have libappindicator installed so that a left click on the tray icon will unminimize discord, and a right click will open the context menu, like in virtually any other application that has a tray icon. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 447153] Kate ignores the "Remove trailing spaces" being "On Modified Lines" when an .editorconfig is present
https://bugs.kde.org/show_bug.cgi?id=447153 --- Comment #4 from Nikos Chantziaras --- (In reply to Waqar Ahmed from comment #3) > You have another option. As you said it's up to you, you can remove that > setting from the editorconfig and then Kate will respect your settings. It' not my project. I just contribute to it. I didn't put the editorconfig in it. > In practice there shouldn't be any spaces in the first place or not a > setting in the config if you want spaces to be preserved. The only way > spaces would end up in files would be that someone used an editor which > didn't respect editorconfig which again defeats the point of having that > config. Yeah. So I would like to ignore it. > Also I closed the issue because there is no way forward with this. We cannot > not respect editorconfig. Reopening doesn't change that. Why can you not not respect editorconfig? I don't get it. Is it a law and you have to respect it? Would you get sued if you had an option to either ignore it, or leave the interpretation of "clean spaces" up to the user? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 447153] Kate ignores the "Remove trailing spaces" being "On Modified Lines" when an .editorconfig is present
https://bugs.kde.org/show_bug.cgi?id=447153 Nikos Chantziaras changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #2 from Nikos Chantziaras --- (In reply to Waqar Ahmed from comment #1) > We have to respect the editorconfig and do exactly what it says otherwise > there is no point in having the editorconfig file. I believe it's up to me whether or not I want to respect the editorconfig file. I mean, I'm the one writing the code, the decision is up to me :P My only options right now is to either drive myself insane with all these changed lines and then jump off a bridge when I can't take it anymore, or use another editor, which would really suck because Kate is great. > To resolve this, the editorconfig must add another option to "Remove > trailing spaces on modified lines only" I don't think there is such an option? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448116] After update to frameworks 5.90, .desktop files with paths to SVG icons fail to display them
https://bugs.kde.org/show_bug.cgi?id=448116 Nikos Chantziaras changed: What|Removed |Added CC||rea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447214] New: When deleting a file in an encrypted vault, the file is moved to the trash folder outside the vault, becoming unencrypted
https://bugs.kde.org/show_bug.cgi?id=447214 Bug ID: 447214 Summary: When deleting a file in an encrypted vault, the file is moved to the trash folder outside the vault, becoming unencrypted Product: dolphin Version: 21.12.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rea...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** When opening an encrypted vault in Dolphin and deleting files in it, the files are moved outside the vault and thus are exposed unencrypted. They end up in ~/.local/share/Trash. I believe this is a serious security issue, which is why I marked this bug with a severity of "major." *** STEPS TO REPRODUCE 1. Open a vault. 2. Create a new text file in the fault. 3. Select the new file in Dolphin and press the Del key on the keyboard. OBSERVED RESULT The file gets moved to "~/.local/share/Trash", which is unencrypted. EXPECTED RESULT The file should be moved to the trash folder on the root directory of the vault. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.10.87-gentoo (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 447153] New: Kate ignores the "Remove trailing spaces" being "On Modified Lines" when an .editorconfig is present
https://bugs.kde.org/show_bug.cgi?id=447153 Bug ID: 447153 Summary: Kate ignores the "Remove trailing spaces" being "On Modified Lines" when an .editorconfig is present Product: kate Version: 21.12.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: rea...@gmail.com Target Milestone: --- SUMMARY *** When editing a file in a project that ships an .editorconfig file with: trim_trailing_whitespace = true in it, then Kate will ignore that I have set the "Remove Trailing Spaces" option to "On Modified Lines." As a result, when I save the file and then do "git add" and "git commit", there can be dozens of even hundreds of modified lines even though I only touched one or two lines. This currently makes Kate completely unusable in such projects. *** STEPS TO REPRODUCE 1. Create an .editorconfig with: [*] trim_trailing_whitespace = true in it. 2. Create a text file with lots of lines and spaces at the end of the lines. 3. In Settings->Configure Kate->Open/Save, set "Remove Trailing Spaces" to "On Modified Lines." 4. Edit that file with kate and only change one line, then save. OBSERVED RESULT The whole file is modified. EXPECTED RESULT Only changed lines should be modified. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.10.87-gentoo (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 445611] Corrupted screenshots with fullscreen OpenGL applications
https://bugs.kde.org/show_bug.cgi?id=445611 --- Comment #1 from Nikos Chantziaras --- Created attachment 143642 --> https://bugs.kde.org/attachment.cgi?id=143642=edit glxgears screenshot -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 445611] New: Corrupted screenshots with fullscreen OpenGL applications
https://bugs.kde.org/show_bug.cgi?id=445611 Bug ID: 445611 Summary: Corrupted screenshots with fullscreen OpenGL applications Product: Spectacle Version: 21.08.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: rea...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 143641 --> https://bugs.kde.org/attachment.cgi?id=143641=edit RetroArch screenshot SUMMARY When running a fullscreen application that uses OpenGL (primary use case are video games) with desktop effects disabled (the application disables them or manually with Shift+Alt+F12, Spectacle often produces pixel garbage in the screenshots. Attached are two screenshots showing the issue. One is from RetroArch, the other with plain old glxgears after switching it to fullscreen mode using Alt+F3/More Actions/Fullscreen. STEPS TO REPRODUCE 1. Disable the compositor (default shortcut Shift+Alt+F12.) 2. Run glxgears. 3. Make it fullscreen through KWin (upper-left icon on the window title bar, "More Actions", "Fullscreen". 4. Press Shift+PrintScr multiple times to take several screenshots and automatically save them in the default screenshot location configured in Spectacle. OBSERVED RESULT Some of the screenshots will have thick horizontal bars of black pixels. EXPECTED RESULT Screenshots should be clean without black pixels. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.10.79-gentoo (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 ADDITIONAL INFORMATION I installed flameshot (a screenshot tool, https://github.com/flameshot-org/flameshot) and it does not have this issue. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 437378] Add lossless crop support
https://bugs.kde.org/show_bug.cgi?id=437378 Nikos Chantziaras changed: What|Removed |Added CC||rea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 433362] Applications started through keyboard shortcuts are not placed in the correct CGroup
https://bugs.kde.org/show_bug.cgi?id=433362
--- Comment #11 from Nikos Chantziaras ---
(In reply to Nate Graham from comment #10)
> It was reverted pending a better fix; re-opening this.
kstart5 does seem to support "-- ", where everything following it is parsed as
part of the command to be executed, not as options to kstart5. For example this
works when called from the command line:
$ kstart5 -- kdocker -d 20 -m -q dolphin
So I tested this and it works:
if (!kstart.isEmpty()) {
parts.prepend(command);
parts.prepend("--");
QProcess::startDetached(kstart, parts);
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 433362] Applications started through keyboard shortcuts are not placed in the correct CGroup
https://bugs.kde.org/show_bug.cgi?id=433362 --- Comment #8 from Nikos Chantziaras --- Btw, this is not limited to custom desktop files places in ~/.local. The same happens with everything else. For example, there is: /usr/share/applications/mpv.desktop with this in it: Exec=mpv --player-operation-mode=pseudo-gui -- %U It's impossible to launch MPV now with a keyboard shortcut. Instead, you get an error: kglobalaccel5[3721]: kstart: Unknown option 'player-operation-mode'. So this commit does much more harm than good IMO. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 433362] Applications started through keyboard shortcuts are not placed in the correct CGroup
https://bugs.kde.org/show_bug.cgi?id=433362 --- Comment #7 from Nikos Chantziaras --- I applied the patch against 5.85.0 and it works. However, it breaks some applications. For example, I have a "thunderbird.desktop" file in my ~/.local/share/applications directory for launching thunderbird with kdocker (so that I can minimize it to the system tray.) It has this exec line: Exec=kdocker -d 20 -m -q thunderbird -- %u If I run kstart5 manually: $ kstart5 --application thunderbird-bin it works fine. kstart5 will run it as-is, meaning it runs kdocker and passes it the specified arguments, which in turn runs thunderbird in the system tray. However, if I try to launch it with a keyboard shortcut, then it doesn't work. The log then shows this error: kglobalaccel5[2002]: kstart: Unknown options: d, m, q. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544
Nikos Chantziaras changed:
What|Removed |Added
CC||rea...@gmail.com
--- Comment #4 from Nikos Chantziaras ---
I have the same issue with 21.08.0. I downgraded yakuake to 21.04.3 and it
works fine again.
The bug is reproducible 100% of the time. Use the yakuake config shown below.
Then open an application (Dolphin will do,) then focus yakuake, then click
Dolphin's close button. Focus is not returned to yakuake, but to whatever
window is behind it.
The commit that introduces the bug is 9202df97322ae2f58104e387e914de15b06644ff
("Fix Yakuake icon appearing in taskbar through Qt::Tool window flag").
Reverting this one commit fixes the issue. Of course, it probably re-introduces
the issue it fixes.
It's pretty annoying :P I do "git commit", then my editor pops up, then I close
it, then I type because I expect yakuake to have focus, but instead I end up
typing into whatever window is behind yakuake, usually my IDE or Discord.
I'm using:
Gentoo Linux AMD64
X11 (xorg-server 1.20.13)
Plasma 5.22.4
Qt 5.12.2
My yakuake config:
[Animation]
Frames=0
[Appearance]
Skin=plastik_dark
[Desktop Entry]
DefaultProfile=Profile 1.profile
[Dialogs]
FirstRun=false
[Window]
Height=78
KeepAbove=false
Position=46
ShowSystrayIcon=false
ToggleToFocus=true
Width=72
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-systemmonitor] [Bug 433362] New: Applications started through keyboard shortcut are not listed in the "Overview" page
https://bugs.kde.org/show_bug.cgi?id=433362 Bug ID: 433362 Summary: Applications started through keyboard shortcut are not listed in the "Overview" page Product: plasma-systemmonitor Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: rea...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 135996 --> https://bugs.kde.org/attachment.cgi?id=135996=edit Screenshot demontrating the problem. In System Monitor's "Overview" page, in the "Applications" section, any applications that have been started through a keyboard shortcut are not listed. STEPS TO REPRODUCE 1. Create an application keyboard shortcut in System Settings->Shortcuts->Applications (see attached screenshot.) For example, I start Firefox with Meta+W and Thunderbird through Meta+M. 2. Start System Monitor. 3. Press the keyboard shortcut that launches the application. OBSERVED RESULT The application will be listed in the Overview page. EXPECTED RESULT The application should be listed in the Overview page. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux AMD64 KDE Plasma Version: 5.21 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391781] Add support for SIXEL in Konsole
https://bugs.kde.org/show_bug.cgi?id=391781 Nikos Chantziaras changed: What|Removed |Added CC||rea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425757] Drag and drop mp3s into audacious not possible anymore
https://bugs.kde.org/show_bug.cgi?id=425757 Nikos Chantziaras changed: What|Removed |Added CC||rea...@gmail.com --- Comment #1 from Nikos Chantziaras --- Same thing when trying to drag image files into the eog (Eye Of Gnome) image viewer. Downgrading to Dolphin 20.04.3 fixes it. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360037] KF5 yakuake sometimes gets detached and shows up in the task manager
https://bugs.kde.org/show_bug.cgi?id=360037 --- Comment #25 from Nikos Chantziaras --- (In reply to Clay Weber from comment #24) > This still happens on Yakuake 20.08.0 > KDE Neon with Plasma 5.194 and Qt 5.14.2 Yes, same here. It has never stopped happening for years. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load
https://bugs.kde.org/show_bug.cgi?id=322060 Nikos Chantziaras changed: What|Removed |Added CC||rea...@gmail.com --- Comment #156 from Nikos Chantziaras --- For anyone coming here through a web search, there's a KWin fork that fixed all issues for me: https://github.com/tildearrow/kwin-lowlatency No more frame skipping or stutter, no more lag, works great with modern, better-than-60Hz displays. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402589] Text cursor disappears or doesn't move
https://bugs.kde.org/show_bug.cgi?id=402589 --- Comment #6 from Nikos Chantziaras --- (In reply to Wolfgang Bauer from comment #5) > This fixes it for me: > https://phabricator.kde.org/D19513 Same here. Applied to 18.12.2 and it fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402589] Text cursor disappears or doesn't move
https://bugs.kde.org/show_bug.cgi?id=402589 --- Comment #3 from Nikos Chantziaras --- If you have problems reproducing, try using a bitmap font. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402589] Text cursor disappears or doesn't move
https://bugs.kde.org/show_bug.cgi?id=402589 Nikos Chantziaras changed: What|Removed |Added Version|master |18.12.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402589] New: Text cursor disappears or doesn't move
https://bugs.kde.org/show_bug.cgi?id=402589 Bug ID: 402589 Summary: Text cursor disappears or doesn't move Product: konsole Version: master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kpart Assignee: konsole-de...@kde.org Reporter: rea...@gmail.com Target Milestone: --- SUMMARY Commit e7085310d6d594823d0ed491fa8bdbd99dec4932 (fix cursor when anti aliasing is enabled) breaks the text cursor. It either gets stuck and doesn't move, or it disappears completely. Video showing the issue: https://youtu.be/0vGjH0A0vds Reverting the offending commit fixed the issue. STEPS TO REPRODUCE 1. In the profile settings, go to the "Advanced" tab and enable "blinking cursor" and "cursor shape" to "underline". SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux AMD64 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402461] Alternate screen buffer scrolling gets disabled after reset
https://bugs.kde.org/show_bug.cgi?id=402461 --- Comment #3 from Nikos Chantziaras --- The patch applies cleanly to Konsole 18.12.0 and fixes the issue. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402461] New: Alternate screen buffer scrolling gets disabled after reset
https://bugs.kde.org/show_bug.cgi?id=402461 Bug ID: 402461 Summary: Alternate screen buffer scrolling gets disabled after reset Product: konsole Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kpart Assignee: konsole-de...@kde.org Reporter: rea...@gmail.com Target Milestone: --- SUMMARY I use the "Enable Alternate Screen buffer scrolling" option in Konsole to be able to scroll using the mouse wheel when using "less". However, when the terminal is reset (using the "reset" command or by using the "Clear scrollback and reset" option of Konsole), the mouse wheel stops working. I have to go to the options, uncheck "alternate screen buffer scrolling" checkbox, click "apply", then check it again and "apply", at which point it starts working again. STEPS TO REPRODUCE 1. Make sure "Enable Alternate Screen buffer scrolling" is enabled (right-click, "Edit current profile", "Mouse" tab.) 2. Type "man ls". You can scroll up/down with the mouse wheel. 3. Exit the manpage viewer and type "reset". 4. Type "man ls" again. You can no longer scroll using the mouse wheel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux AMD64 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402327] Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 (DW_OP_drop)
https://bugs.kde.org/show_bug.cgi?id=402327 --- Comment #2 from Nikos Chantziaras --- That does indeed help. Warning is gone. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402327] New: Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13
https://bugs.kde.org/show_bug.cgi?id=402327 Bug ID: 402327 Summary: Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 Product: valgrind Version: 3.15 SVN Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: rea...@gmail.com Target Milestone: --- SUMMARY Running GTK or Qt in Valgrind prints the following warning: --2646-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux AMD64 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load
https://bugs.kde.org/show_bug.cgi?id=322060 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added CC|rea...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load
https://bugs.kde.org/show_bug.cgi?id=322060 --- Comment #144 from Nikos Chantziaras <rea...@gmail.com> --- (In reply to Mahendra Tallur from comment #143) > As suggested, I finally created a thread on the NVIDIA forum where an NVIDIA > dev frequently replies... A message in a bottle ! > > https://devtalk.nvidia.com/default/topic/1029568/linux/the-situation-on-kde- > kwin-plasma-performance/ That link doesn't seem to work. I can't see any such thread there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load
https://bugs.kde.org/show_bug.cgi?id=322060 --- Comment #134 from Nikos Chantziaras <rea...@gmail.com> --- (In reply to Thomas Lübking from comment #132) > > and the time on the systray says "20:00", but the time now is 21:00 > That's not what you said :-P > > https://bugs.kde.org/show_bug.cgi?id=353983 I don't see any post from me on that bug :-P -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load
https://bugs.kde.org/show_bug.cgi?id=322060 --- Comment #130 from Nikos Chantziaras <rea...@gmail.com> --- (In reply to Thomas Lübking from comment #128) > > My wallpaper even reverts back to some previous datetime's image. > That I cannot explain at all. This is reproducible by simply suspending compositing. After an undetermined amount of time, the non-composited desktop will freeze its appearance and will not get updated anymore. New applications don't appear on the task manager bar, the system tray doesn't get updated, basically it's frozen to some state in the past. Resuming compositing again makes it work correctly. Suspending compositing after that makes it revert to the same old frozen state. For example, if it got frozen and the time on the systray says "20:00", but the time now is 21:00, then suspending and resuming compositing makes it display 20:00 - 21:00 - 20:00 - 21:00, etc, as you suspend/resume compositing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376245] Mouse cursor changes size when pointer on Kwin window title bar
https://bugs.kde.org/show_bug.cgi?id=376245 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added CC|rea...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 344547] vex x86->IR: unhandled instruction bytes: 0xC5 0xF8 0x77 0xE9
https://bugs.kde.org/show_bug.cgi?id=344547 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Resolution|WONTFIX |LATER Status|RESOLVED|VERIFIED --- Comment #4 from Nikos Chantziaras <rea...@gmail.com> --- It seems rather unlikely at this point, which is why I closed it. I'm changing it to "Verified/Later" since you think it's not completely out of the question. I don't think it would be me adding the feature though. I'm afraid my hands-on experience with machine instructions only went as far as setting VGA mode 13h in DOS back in 1993 ;-) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 344547] vex x86->IR: unhandled instruction bytes: 0xC5 0xF8 0x77 0xE9
https://bugs.kde.org/show_bug.cgi?id=344547 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 318068] KDE mounts devices as root instead of as user
https://bugs.kde.org/show_bug.cgi?id=318068 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #11 from Nikos Chantziaras <rea...@gmail.com> --- Closing. I don't care anymore. -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 320199] File dialogs print warnings on stdout
https://bugs.kde.org/show_bug.cgi?id=320199 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #8 from Nikos Chantziaras <rea...@gmail.com> --- Closing. I don't care anymore. -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 269661] Per-application keyboard layout switching ignores the desktop
https://bugs.kde.org/show_bug.cgi?id=269661 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Resolution|--- |WONTFIX Status|CONFIRMED |RESOLVED --- Comment #16 from Nikos Chantziaras <rea...@gmail.com> --- Closing. I don't care anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351700] kwin is frame skipping
https://bugs.kde.org/show_bug.cgi?id=351700 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #54 from Nikos Chantziaras <rea...@gmail.com> --- Closing. I don't care anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 352161] Panel pop-ups do not always disappear when the mouse leaves
https://bugs.kde.org/show_bug.cgi?id=352161 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Nikos Chantziaras <rea...@gmail.com> --- Closing. I don't care anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #20 from Nikos Chantziaras <rea...@gmail.com> --- With the same maintainer closing another bugs and claiming "it's a feature", it's kind of difficult to not get mad at that person: https://bugs.kde.org/show_bug.cgi?id=377913 > We all want a strong community and awesome software. That's difficult if bugs are presented as "features." We will never have awesome software. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #16 from Nikos Chantziaras <rea...@gmail.com> --- Why are you trying to trigger me all the time? First with arrogance, then with this. Do you have something against me? I assure you this is nothing personal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #14 from Nikos Chantziaras <rea...@gmail.com> --- So how on earth do I prevent applications from stealing the focus? They do it all the time on "medium". When I work on MS Windows, all applications are blocked from stealing focus from the currently active application. Under KDE, they are allowed to pop-up their windows wherever they want. "Medium" is useless. So now you're saying "High" is also useless. What can I say to that other than it's a mess that needs fixing? So this is a request for fixing it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #8 from Nikos Chantziaras <rea...@gmail.com> --- But you know what? I'm going to reopen this bug, simply because you're wrong. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #7 from Nikos Chantziaras <rea...@gmail.com> --- Brilliant. Very smart design choices by the KDE team. You have my congratulations. We need more people like you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #4 from Nikos Chantziaras <rea...@gmail.com> --- I would like to add that if I click on the application launcher, I am giving it focus. So it should open. Focus stealing prevention is for preventing stuff you didn't click on from getting focused. But I explicitly click on something, then that means I do want it to get focus. Preventing something I explicitly click on from getting focus does not make much sense. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360037] KF5 yakuake sometimes gets detached and shows up in the task manager
https://bugs.kde.org/show_bug.cgi?id=360037 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added CC||rea...@gmail.com --- Comment #18 from Nikos Chantziaras <rea...@gmail.com> --- With Yakuake 3.0.4 on Qt 5.7.1 it still happens at the same frequency as in the past for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377913] Windows are not centered correctly
https://bugs.kde.org/show_bug.cgi?id=377913 --- Comment #4 from Nikos Chantziaras <rea...@gmail.com> --- With decisions like that, no wonder KDE is still a broken mess. I wonder why the hell I even bother reporting issues. Bugs are by design these days. Never again. Have a nice life. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377913] Windows are not centered correctly
https://bugs.kde.org/show_bug.cgi?id=377913 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from Nikos Chantziaras <rea...@gmail.com> --- No, it doesn't work correctly. The whole point of "centered" is to get windows centered on my screen. Centered in front of my eyes. Having to shifting my monitor to be off-center is a funny requirement. The panel is part of the screen. Centering the window on the screen doesn't mean you have to place the window in a non-allowed area. It means you place the window in the center of the screen. If that HAPPENS to overlap the panel then you place it right next to the panel. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #2 from Nikos Chantziaras <rea...@gmail.com> --- I completely disagree, but whatever. It's a broken design for the desktop environment to be completely unaware of itself. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] New: KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 Bug ID: 377914 Summary: KWin prevents Application Launcher from opening when using focus stealing prevention Product: kwin Version: 5.9.4 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rea...@gmail.com Target Milestone: --- When setting a focus stealing prevention level higher than "medium" makes it impossible to open the application launcher anymore. Clicking it does nothing. The only case where it opens is when manually unfocusing all windows (by clicking on the desktop first.) Plasma 5.9.4 Frameworks 5.32.0 X.Org Server 1.19.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377913] New: Windows are not centered correctly
https://bugs.kde.org/show_bug.cgi?id=377913 Bug ID: 377913 Summary: Windows are not centered correctly Product: kwin Version: 5.9.4 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rea...@gmail.com Target Milestone: --- When using "Centered" as the default placement for new windows, they are not centered correctly on the screen if the task manager panel is on the side of the screen. I place the task manager panel of the left side of the screen, and new windows are not centered but instead are pushed to the right. The wider the panel is, the more off-center windows are placed. Plasma 5.9.4 Frameworks 5.32.0 X.Org Server 1.19.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376245] Mouse cursor changes size when pointer on Kwin window title bar
https://bugs.kde.org/show_bug.cgi?id=376245 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added CC||rea...@gmail.com --- Comment #7 from Nikos Chantziaras <rea...@gmail.com> --- I have the same issue. In System Settings, I have "Resolution dependent" selected for the cursor size, but KWin doesn't use it. In fact, it doesn't use it even if I specify a size manually. If I select "32", KWin still uses 24. I'm using a 27" 2560x1440 monitor. X11 reports: $ xdpyinfo | grep -B 2 resolution screen #0: dimensions:2560x1440 pixels (602x341 millimeters) resolution:108x107 dots per inch This is the output of "qdbus org.kde.KWin /KWin supportInformation": https://paste.kde.org/p1o81y41e -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 307112] Blur effect: doCachedBlur() is broken for non opaque windows (at least)
https://bugs.kde.org/show_bug.cgi?id=307112 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added CC|rea...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory
https://bugs.kde.org/show_bug.cgi?id=372594 --- Comment #13 from Nikos Chantziaras <rea...@gmail.com> --- Oops, I thought this is the Gentoo bugzilla :-P Sorry. Didn't pay attention to the URL. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory
https://bugs.kde.org/show_bug.cgi?id=372594 --- Comment #11 from Nikos Chantziaras <rea...@gmail.com> --- Thanks. I think it might be a good idea to revbump plasma-workspace though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory
https://bugs.kde.org/show_bug.cgi?id=372594 --- Comment #8 from Nikos Chantziaras <rea...@gmail.com> --- I've hit a slow mirror. I updated again, and there was an update to kpackage, which applies the patch. It doesn't fix anything. The same issues are still there. Please reopen this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory
https://bugs.kde.org/show_bug.cgi?id=372594 --- Comment #7 from Nikos Chantziaras <rea...@gmail.com> --- This bug was closed as "FIXED". So what do I do? There's no update in portage or anything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory
https://bugs.kde.org/show_bug.cgi?id=372594 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added CC||rea...@gmail.com --- Comment #4 from Nikos Chantziaras <rea...@gmail.com> --- Changing desktop layout from "Desktop" to "Folder View" is also not possible. You can select it, but "Apply" (or "OK") do nothing. The desktop settings dialog ignores all settings changes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358047] Extremely sluggish and unusable drag
https://bugs.kde.org/show_bug.cgi?id=358047 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Nikos Chantziaras <rea...@gmail.com> --- Forgot to close this. It was a Qt issue. Recent versions of Qt have fixed it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358047] Extremely sluggish and unusable drag
https://bugs.kde.org/show_bug.cgi?id=358047 --- Comment #3 from Nikos Chantziaras <rea...@gmail.com> --- (In reply to CapsAdmin from comment #2) > I have this problem as well when I have an application rendering something > every frame in the background. For this happens without even a single application running. Just logging in to KDE without starting anything, the problem is there. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 358378] New: krunner crash
https://bugs.kde.org/show_bug.cgi?id=358378 Bug ID: 358378 Summary: krunner crash Product: krunner Version: 5.5.3 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: rea...@gmail.com Application: krunner (5.5.3) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.1.15-gentoo-r1 x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: - What I was doing when the application crashed: I pressed alt+f2 and entered "kwrite" in krunner. Then it crashed. The crash can be reproduced sometimes. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7fd1a22e17c0 (LWP 2412))] Thread 12 (Thread 0x7fd1876d6700 (LWP 2432)): #0 0x7fd19ee6a64d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd19e366ac2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fd19e36872f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fd189635c89 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fd19f4d6302 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7fd19d0c5444 in start_thread (arg=0x7fd1876d6700) at pthread_create.c:334 #6 0x7fd19ee7309d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7fd17dd6d700 (LWP 2483)): #0 0x7fd19ee6a64d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd19b127edc in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fd19b127fec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fd19f6d0efc in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fd19f68213a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fd19f4d1894 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fd1a1294595 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7fd19f4d6302 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7fd19d0c5444 in start_thread (arg=0x7fd17dd6d700) at pthread_create.c:334 #9 0x7fd19ee7309d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7fd175f0b700 (LWP 3914)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd19f4d698a in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7fd1a178a413 in ?? () from /usr/lib64/libQt5Quick.so.5 #3 0x7fd1a178a810 in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7fd19f4d6302 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7fd19d0c5444 in start_thread (arg=0x7fd175f0b700) at pthread_create.c:334 #6 0x7fd19ee7309d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7fd16b67e700 (LWP 3917)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd19f4d698a in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7fd1775a0a1b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=, th=) at /var/tmp/portage/kde-frameworks/threadweaver-5.18.0/work/threadweaver-5.18.0/src/weaver.cpp:594 #3 0x7fd1775a188f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x1422350, th=th@entry=0x162b410, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at /var/tmp/portage/kde-frameworks/threadweaver-5.18.0/work/threadweaver-5.18.0/src/weaver.cpp:554 #4 0x7fd1775a58c8 in ThreadWeaver::WorkingHardState::applyForWork (this=0xf9fa50, th=0x162b410, wasBusy=) at /var/tmp/portage/kde-frameworks/threadweaver-5.18.0/work/threadweaver-5.18.0/src/workinghardstate.cpp:66 #5 0x7fd1775a095f in ThreadWeaver::Weaver::applyForWork (this=, th=0x162b410, wasBusy=) at /var/tmp/portage/kde-frameworks/threadweaver-5.18.0/work/threadweaver-5.18.0/src/weaver.cpp:568 #6 0x7fd1775a5922 in ThreadWeaver::WorkingHardState::applyForWork (this=0xf9fa50, th=0x162b410, wasBusy=) at /var/tmp/portage/kde-frameworks/threadweaver-5.18.0/work/threadweaver-5.18.0/src/workinghardstate.cpp:73 #7 0x7fd1775a095f in ThreadWeaver::Weaver::applyForWork (this=, th=0x162b410, wasBusy=) at /var/tmp/portage/kde-frameworks/threadweaver-5.18.0/work/threadweaver-5.18.0/src/weaver.cpp:568 #8 0x7fd1775a3723 in ThreadWeaver::Thread::run (this=0x162b410) at /var/tmp/portage/kde-frameworks/threadweaver-5.18.0/work/threadweaver-5.18.0/src/thread.cpp:103 #9 0x7fd19f4d6302 in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7fd19d0c5444 in start_thread (arg=0x7fd16b67e700) at pthread_create.c:334 #11
[krunner] [Bug 358378] krunner crash
https://bugs.kde.org/show_bug.cgi?id=358378 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Platform|Compiled Sources|Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 320199] File dialogs print warnings on stdout
https://bugs.kde.org/show_bug.cgi?id=320199 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 320199] File dialogs print warnings on stdout
https://bugs.kde.org/show_bug.cgi?id=320199 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Resolution|UNMAINTAINED|--- Status|RESOLVED|UNCONFIRMED --- Comment #7 from Nikos Chantziaras <rea...@gmail.com> --- Oh, OK. Reopening. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351700] kwin is frame skipping
https://bugs.kde.org/show_bug.cgi?id=351700 --- Comment #53 from Nikos Chantziaras <rea...@gmail.com> --- Well, turns out 61 doesn't work for 1080p video. Or even slightly higher values (62, 63). It works only for lower resolutions. I've set MaxFPS=70 and RefreshRate=70 to get stutter-free 1080p@60FPS. The driver version doesn't seem to matter, btw. 352.63, 355.11 and 358.16 all exhibit the problem. I didn't try 361.x versions yet, because they seem to break KDE and a lot of Qt applications so I'll have to wait for things to be sorted out first. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358047] Extremely sluggish and unusable drag
https://bugs.kde.org/show_bug.cgi?id=358047 --- Comment #1 from Nikos Chantziaras <rea...@gmail.com> --- Created attachment 96669 --> https://bugs.kde.org/attachment.cgi?id=96669=edit Video demonstrating the bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351700] kwin is frame skipping
https://bugs.kde.org/show_bug.cgi?id=351700 --- Comment #50 from Nikos Chantziaras <rea...@gmail.com> --- > What happens if you raise the desired swap frequency (as in comment #17, feel > free to try even higher values) OK, I tried 70 and it works! No stutter, but there's input lag. I've tried 61 and it works too, and without the input lag of 70. I then tried 60.1, 60.2, 60.9, but none work. It doesn't like fractional numbers (which is weird, because some monitor modes ARE inherently fractional; like 47.952Hz (for 23.976FPS video content.) > PS, does the same problem also occur for glxgears (or is it limited to video > playback) Hm, glxgears doesn't seem to suffer. It's only video that does. But thank you for pointing out comment #17 again. I somehow missed it completely. You just saved me hours of messing around with installation and setup of other window managers :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351700] kwin is frame skipping
https://bugs.kde.org/show_bug.cgi?id=351700 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Version|5.5.2 |5.5.3 --- Comment #51 from Nikos Chantziaras <rea...@gmail.com> --- Btw, since nothin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351700] kwin is frame skipping
https://bugs.kde.org/show_bug.cgi?id=351700 --- Comment #52 from Nikos Chantziaras <rea...@gmail.com> --- Btw, since nothing changed in kwin, this has to be a side effect of the GPU upgrade? I wonder if rendering speed matters. I had a 780 before, which is already very fast GPU, and the 980 Ti I have now is even faster than that. Could it be that there's some bug that only triggers when rendering times/latency are very low? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351700] kwin is frame skipping
https://bugs.kde.org/show_bug.cgi?id=351700 --- Comment #45 from Nikos Chantziaras <rea...@gmail.com> --- Video now went from borderline unwatchable to actually unwatchable after a KDE Plasma update (going to kwin 5.5.2. I also upgraded my GPU to a GTX 980 Ti. The frame skipping in video is now so extreme, you can see frames flickering back and forward all the time. Doesn't matter if I watch a video with mpv or with Chrome's HTML5 video player on YouTube. It is so bad where I'm now looking at how to switch my system from KDE to something else, after 17 years of KDE use :-( -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351700] kwin is frame skipping
https://bugs.kde.org/show_bug.cgi?id=351700 --- Comment #47 from Nikos Chantziaras <rea...@gmail.com> --- Yes. It now has extreme frame skipping even with __GL_YIELD="USLEEP" and TB. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351700] kwin is frame skipping
https://bugs.kde.org/show_bug.cgi?id=351700 Nikos Chantziaras <rea...@gmail.com> changed: What|Removed |Added Version|5.4.2 |5.5.2 -- You are receiving this mail because: You are watching all bug changes.
