[kwin] [Bug 486556] New: No longer possible to disable composition through the API
https://bugs.kde.org/show_bug.cgi?id=486556 Bug ID: 486556 Summary: No longer possible to disable composition through the API Classification: Plasma Product: kwin Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- Kwin_X11 used to have three methods for disable composition: 1. By creating a window that had the hint: _NET_WM_BYPASS_COMPOSITOR 2. By running the command: qdbus org.kde.KWin /Compositor suspend 3. From QML, by calling: client.blocksCompositing = true The two last methods have been removed. This renders one of the most popular Kwin scripts broken, Autocomposer (https://www.opendesktop.org/p/1502826). This script is important for people because it allows running games fluently, more in low end hardware. Without it games perform slower, specially if desktop effects like "Blur" or "Background Contrast" are in use. The only way to fix Autocomposer right now is by creating an invisible window that holds the first hint, which is ugly. Alternatively the option "allow applications to block compositing" could affect full-screen applications that don't explicitly set the hint, as Autocomposer does. This is a more expected behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483433] On Breeze SDDM theme, test mode cannot locate plasma components
https://bugs.kde.org/show_bug.cgi?id=483433 --- Comment #1 from Alberto Salvia Novella --- Installing plasma-framework5 work-around the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483433] On Breeze SDDM theme, test mode cannot locate plasma components
https://bugs.kde.org/show_bug.cgi?id=483433 Alberto Salvia Novella changed: What|Removed |Added URL||https://github.com/sddm/sdd ||m/issues/1892 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483433] New: On Breeze SDDM theme, test mode cannot locate plasma components
https://bugs.kde.org/show_bug.cgi?id=483433 Bug ID: 483433 Summary: On Breeze SDDM theme, test mode cannot locate plasma components Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: plasma-b...@kde.org Reporter: es204904...@gmail.com CC: visual-des...@kde.org Target Milestone: 1.0 Running on Plasma 6, if you do: sddm-greeter --test-mode --theme /usr/share/sddm/themes/breeze | grep "(WW)" It compains that library import requires a version. If you remove the non versioned lines on /usr/share/sddm/themes/breeze/Main.qml, then it complains that plasma modules are not installed. But if you just use Breeze on the login screen, it works. So test mode and actual SDDM behave differently. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482872] Font dpi doesn't apply to qt5 apps
https://bugs.kde.org/show_bug.cgi?id=482872 Alberto Salvia Novella changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Alberto Salvia Novella --- Installing the packages mentioned here: https://discuss.kde.org/t/how-to-set-qt5-font-size/11820/7?u=albertosalvianovella Solved the issue, so I guess this isn't a bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482872] Font dpi doesn't apply to qt5 apps
https://bugs.kde.org/show_bug.cgi?id=482872 --- Comment #1 from Alberto Salvia Novella --- The culprit is qt5 apps not understanding the font format in "~/.config/kdeglobals". If I run: pcmanfm-qt I get: QFont::fromString: Invalid description 'Noto Sans,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1' QFont::fromString: Invalid description 'Hack,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1' QFont::fromString: Invalid description 'Noto Sans,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1' QFont::fromString: Invalid description 'Noto Sans,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1' But if in kdeglobals I change: font=Noto Sans,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1 To: font=Noto Sans,11 Both qt5 and qt6 apps shows the correct font size. So if that is a new qt6 format, maybe we should delay that a little bit. Till more apps use qt6. For example pcmanfm-qt will upgrade to qt6 at the end of April: https://github.com/lxqt/pcmanfm-qt/commit/adf83ac373cd826c1ac16ad9702c04de8f757f8c -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482872] Font dpi doesn't apply to qt5 apps
https://bugs.kde.org/show_bug.cgi?id=482872 Alberto Salvia Novella changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482872] New: Font dpi doesn't apply to qt5 apps
https://bugs.kde.org/show_bug.cgi?id=482872 Bug ID: 482872 Summary: Font dpi doesn't apply to qt5 apps Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_fonts Assignee: plasma-b...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- Setting fonts dpi doesn't affect qt5 apps, like pcmanfm-qt or qt4wine. OS: Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 480742] New: Indentation doesn't work correctly with long continuous lines
https://bugs.kde.org/show_bug.cgi?id=480742 Bug ID: 480742 Summary: Indentation doesn't work correctly with long continuous lines Classification: Applications Product: kate Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: indentation Assignee: kwrite-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- Created attachment 165478 --> https://bugs.kde.org/attachment.cgi?id=165478=edit bad-indent.sh When a line has no spaces and exceeds the window width, an extra newline is created above it, which is wrong. See the attachment. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477495] Allowing a password policy
https://bugs.kde.org/show_bug.cgi?id=477495 --- Comment #1 from Alberto Salvia Novella --- Sorry: retry=10 minlen=8 maxrepeat=3 maxsequence=3 usersubstr=4 enforce_for_root -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477495] Allowing a password policy
https://bugs.kde.org/show_bug.cgi?id=477495 Alberto Salvia Novella changed: What|Removed |Added Summary|Allowing a minimum policy |Allowing a password policy -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477495] New: Allowing a minimum policy
https://bugs.kde.org/show_bug.cgi?id=477495 Bug ID: 477495 Summary: Allowing a minimum policy Classification: Applications Product: systemsettings Version: 5.27.9 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_users Assignee: plasma-b...@kde.org Reporter: es204904...@gmail.com CC: uhh...@gmail.com Target Milestone: --- Passwords are usually the weakest link on a system security wise. So probably it would be a good idea if creating an user through System Settings will warn if their password was weak or common. This could be done through libpwquality. System Settings just needed to abide to the policy defined at "/etc/security/pwquality.conf". Calamares already implements it like this: - https://github.com/calamares/calamares/blob/calamares/src/modules/users/CheckPWQuality.h - https://github.com/calamares/calamares/blob/calamares/src/modules/users/CheckPWQuality.cpp And here's the manual: - https://man.archlinux.org/man/pwquality.conf.5.en An the settings that would meet NIST recommendations: retry=10 minlen=9 maxrepeat=3 maxsequence=3 usersubstr=4 enforce_for_root -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475251] New: Keeping extra spaces by default
https://bugs.kde.org/show_bug.cgi?id=475251 Bug ID: 475251 Summary: Keeping extra spaces by default Classification: Applications Product: kate Version: 23.08.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- REPRODUCING: 1. Copy and paste the following patch into Kate: http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=effadce6c756247ea8bae32dc13bb3e6f464f0eb 2. Observe that at the end of it there's a space 3. Save 4. Observe that the space was removed RESULT The patch is no longer valid, and the user won't notice why. SOLUTION: At katerc "Keep Extra Spaces" shall be "true" by default. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 474922] Toolbars reset after upgrades
https://bugs.kde.org/show_bug.cgi?id=474922 --- Comment #1 from Alberto Salvia Novella --- https://gitlab.com/es20490446e/kate-skull-wipeout/-/blob/main/root/etc/skulls/kate-wipeout/.local/share/kate/anonymous.katesession?ref_type=heads -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 474922] Toolbars reset after upgrades
https://bugs.kde.org/show_bug.cgi?id=474922 Alberto Salvia Novella changed: What|Removed |Added Summary|Toolbars resets after |Toolbars reset after |upgrades|upgrades -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 474922] New: Toolbars resets after upgrades
https://bugs.kde.org/show_bug.cgi?id=474922 Bug ID: 474922 Summary: Toolbars resets after upgrades Classification: Applications Product: kate Version: Git Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- I have Kate with most add-on buttons disabled. Only the "search" button is enabled. But when Kate upgrades, all the buttons come back. Aka `~/.local/share/kate/anonymous.katesession` gets reset. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471356] Button "apply plasma settings" no longer works
https://bugs.kde.org/show_bug.cgi?id=471356 --- Comment #5 from Alberto Salvia Novella --- https://github.com/sddm/sddm/issues/1801 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471356] Button "apply plasma settings" no longer works
https://bugs.kde.org/show_bug.cgi?id=471356 --- Comment #3 from Alberto Salvia Novella --- It also happens with the default theme, Breeze. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471356] Button "apply plasma settings" no longer works
https://bugs.kde.org/show_bug.cgi?id=471356 Alberto Salvia Novella changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Alberto Salvia Novella --- [Autologin] Relogin=true Session= User= [General] HaltCommand=/usr/bin/systemctl poweroff Numlock=on RebootCommand=/usr/bin/systemctl reboot [Theme] Current=dawn CursorSize=36 CursorTheme=breeze_cursors Font=Noto Sans,11,-1,5,50,0,0,0,0,0 [Users] MaximumUid=6 MinimumUid=1000 [X11] ServerArguments=-dpi 144 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471356] New: Button "apply plasma settings" no longer works
https://bugs.kde.org/show_bug.cgi?id=471356 Bug ID: 471356 Summary: Button "apply plasma settings" no longer works Classification: Applications Product: systemsettings Version: 5.27.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_sddm Assignee: plasma-b...@kde.org Reporter: es204904...@gmail.com CC: k...@david-redondo.de, k...@davidedmundson.co.uk Target Milestone: --- === SYSTEM === - KDE Plasma 5.27.5 - KDE Frameworks 5.106.0 - Qt: 5.15.9 - SDDM 0.19.0 - Manjaro KDE === REPRODUCING === 1. At "System Settings -> Display and Monitor -> Display Configuration" change "global scale". 2. At "System Settings -> Startup and Shutdown - > Login Screen (SDDM)", press the button "Apply Plasma Settings". === RESULT === - SDDM scale doesn't change -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467870] Desktop layout reverts to folder view
https://bugs.kde.org/show_bug.cgi?id=467870 --- Comment #3 from Alberto Salvia Novella --- No idea, as it doesn't seem to happen consistently. I have just asked the variety developers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467870] Desktop layout reverts to folder view
https://bugs.kde.org/show_bug.cgi?id=467870 Alberto Salvia Novella changed: What|Removed |Added URL||https://github.com/varietyw ||alls/variety/issues/606 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467870] New: Desktop layout reverts to folder view
https://bugs.kde.org/show_bug.cgi?id=467870 Bug ID: 467870 Summary: Desktop layout reverts to folder view Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: es204904...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 SYSTEM - Variety 0.8.10 - KDE Plasma 5.26.5 - KDE Frameworks 5.103.0 - Qt 5.15.8 - Graphics platform X11 - Linux 6.2.8 Zen HOW TO REPRODUCE 1. Create any file or folder on the desktop. 1. Right click on the desktop and select "configure desktop and wallpaper" 2. Set "layout" to "desktop" 3. Install and enable "variety" RESULT After a few days the layout reverts to "folder view", and the contents of the desktop become visible again. -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 467869] Firefox colors look weird
https://bugs.kde.org/show_bug.cgi?id=467869 Alberto Salvia Novella changed: What|Removed |Added URL||https://bugzilla.mozilla.or ||g/show_bug.cgi?id=1824882 -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 467869] New: Firefox colors look weird
https://bugs.kde.org/show_bug.cgi?id=467869 Bug ID: 467869 Summary: Firefox colors look weird Classification: Plasma Product: colord-kde Version: 22.12.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Daemon Module (KDED) Assignee: dantt...@gmail.com Reporter: es204904...@gmail.com Target Milestone: --- Created attachment 157659 --> https://bugs.kde.org/attachment.cgi?id=157659=edit shot.png SYSTEM - KDE Plasma 5.26.5 - KDE Frameworks 5.103.0 - Qt 5.15.8 - Graphics platform X11 - Linux 6.2.8 Zen HOW TO REPRODUCE 1. Install "colord-kde" and "displaycal". 2. Using "displaycal" calibrate the screen. 3. Open an image with blues or purples on an image viewer, then on Firefox. RESULT Colors look weird on Firefox only. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 466694] KOSRelease::logo() doesn't check if distro logo has been upgraded
https://bugs.kde.org/show_bug.cgi?id=466694 Alberto Salvia Novella changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #4 from Alberto Salvia Novella --- 1. Read which logo is used at "/etc/os-release". 2. Figure out where's that logo file, either in (/usr/share/pixmaps) or (/usr/share/icons). 2. Change the logo file, preserving the name. You can use the command "sudo cp". 3. Go to [System Settings -> About this system]. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466694] Doesn't check if distro logo has been upgraded
https://bugs.kde.org/show_bug.cgi?id=466694
--- Comment #1 from Alberto Salvia Novella ---
Work around: Remove:
${HOME}/.cache/icon-cache.kcache
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 466694] New: Doesn't check if distro logo has been upgraded
https://bugs.kde.org/show_bug.cgi?id=466694 Bug ID: 466694 Summary: Doesn't check if distro logo has been upgraded Classification: Applications Product: systemsettings Version: 5.26.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- If you update the distro logo file, specified at "/etc/os-release", [System Settings -> About this system] continues showing the old logo. Even after reboot, or after updating the icon cache. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463602] No print option = Useless
https://bugs.kde.org/show_bug.cgi?id=463602 --- Comment #3 from Alberto Salvia Novella --- This is like having a word processor without fonts. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463602] No print option = Useless
https://bugs.kde.org/show_bug.cgi?id=463602 --- Comment #1 from Alberto Salvia Novella --- Really guys, this is so bad. My eyes are bleeding. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463602] New: No print option = Useless
https://bugs.kde.org/show_bug.cgi?id=463602 Bug ID: 463602 Summary: No print option = Useless Classification: Applications Product: krita Version: 5.1.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- No option to print in Krita, if I export the image qView also doesn't have the option, if I open in Firefox the color management is broken. Conclusion: The average user won't be capable to print. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 401092] Selecting a second scan area results in garbage
https://bugs.kde.org/show_bug.cgi?id=401092 Alberto Salvia Novella changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Alberto Salvia Novella --- It happened to me again a few weeks ago. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462224] New: AVIF format
https://bugs.kde.org/show_bug.cgi?id=462224 Bug ID: 462224 Summary: AVIF format Classification: Applications Product: krita Version: 5.1.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- Krita can open AVIF, but it's not registered on its desktop file. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438795] Refresh rate list not updated after resolution change
https://bugs.kde.org/show_bug.cgi?id=438795 Alberto Salvia Novella changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Alberto Salvia Novella --- That's right. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 --- Comment #15 from Alberto Salvia Novella --- Thanks for the help. Let me know if you need more testing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 --- Comment #13 from Alberto Salvia Novella --- Just you to get the idea: when I convert 1080p using all cores I cannot perceive any system slowdown. When I compile C++ code I can only perceive a small one. Baloo seems to be the sole program that causes a real slowdown, where even other high demanding tasks don't. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 --- Comment #12 from Alberto Salvia Novella --- It happens instantly after Baloo starts indexing, and the performance drop stays stable. Furthermore my CPU thermal grease has been replaced by high quality one, and the laptop fan barely switches on compared with before. Usually staying between 40-50ºC. Hence I don't think it is due to thermal issues. My guess is that either the APU, or the motherboard, is the limiting factor. I have seen that unbuffered SSDs don't perform so well on this laptop, where they do in older machines I have tried them on. Some path becomes too busy. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 --- Comment #10 from Alberto Salvia Novella --- "iotop" shows no IO activity from baloo_file. Only from time to time. It seems that most of its processing happens on RAM. It doesn't seem to be CPU Cores, RAM or IO saturation. What happens is that when "baloo_file" uses 25% of CPU, one core of four, the graphical interface sees a drop in framerate. Like going from 120 to 15 permanently till "baloo_file" stops. This is probably related with the fact that APUs share memory between CPU, GPU and RAM. So most likely some shared memory between those is saturated, not in amount, but in frequency. Context switching. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 --- Comment #9 from Alberto Salvia Novella --- Created attachment 153408 --> https://bugs.kde.org/attachment.cgi?id=153408=edit monitor-resources.png -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 --- Comment #8 from Alberto Salvia Novella --- Created attachment 153407 --> https://bugs.kde.org/attachment.cgi?id=153407=edit monitor-processes.png -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 Alberto Salvia Novella changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Alberto Salvia Novella --- Compilation usually involves creating and deleting files. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 --- Comment #5 from Alberto Salvia Novella --- Same indexing the recently created files using the above method. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 --- Comment #4 from Alberto Salvia Novella --- The initial indexing of baloo slows things more, than creating 50 files recursively itself. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 Alberto Salvia Novella changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Alberto Salvia Novella --- It doesn't happen with the above commands, while baloo turned off. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 --- Comment #2 from Alberto Salvia Novella --- When I disabled Baloo I deleted the index. But if I enable Baloo again, the resulting index is: $ balooctl indexSize File Size: 141,81 MiB Used: 137,87 MiB PostingDB: 23,63 MiB17.142 % PositionDB: 25,91 MiB18.791 % DocTerms: 21,74 MiB15.770 % DocFilenameTerms: 21,56 MiB15.637 % DocXattrTerms:0 B 0.000 % IdTree: 5,78 MiB 4.193 % IdFileName: 23,84 MiB17.289 % DocTime: 14,34 MiB10.401 % DocData:0 B 0.000 % ContentIndexingDB:0 B 0.000 % FailedIdsDB:0 B 0.000 % MTimeDB: 1,07 MiB 0.776 % -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461140] Black box on the desktop during login
https://bugs.kde.org/show_bug.cgi?id=461140 --- Comment #5 from Alberto Salvia Novella --- The box belongs to the desktop itself. Maybe this is due to the frame-rate change that takes place between SDDM and the user session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461140] Black box on the desktop during login
https://bugs.kde.org/show_bug.cgi?id=461140 Alberto Salvia Novella changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461140] Black box on the desktop during login
https://bugs.kde.org/show_bug.cgi?id=461140 --- Comment #4 from Alberto Salvia Novella --- Created attachment 153379 --> https://bugs.kde.org/attachment.cgi?id=153379=edit xprop-screenshot.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461140] Black box on the desktop during login
https://bugs.kde.org/show_bug.cgi?id=461140 --- Comment #3 from Alberto Salvia Novella --- Created attachment 153378 --> https://bugs.kde.org/attachment.cgi?id=153378=edit xprop.log -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 461256] New: Baloo slows the system when many files are created
https://bugs.kde.org/show_bug.cgi?id=461256 Bug ID: 461256 Summary: Baloo slows the system when many files are created Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.98.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- If you create many files at the same time, like you do when compiling software, that makes baloo to noticeably slow the system down. This happens despite using a brand new SanDisk high speed SSD with DRAM cache. This laptop has an AMD A10-8700P APU, and 16GiB of RAM DDR3. No swap, no encryption. Choosing a different kernel edition (generic/zen), with their different I/O schedulers (endline/bfq), doesn't make the slowness to go away. Selecting baloo not to index file contents, the same. I think this defeats the purpose of baloo all together, as it's just better to have it switched off in any circumstance. It really needs to get easy on resources. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461140] New: Black box on the desktop during login
https://bugs.kde.org/show_bug.cgi?id=461140 Bug ID: 461140 Summary: Black box on the desktop during login Classification: Plasma Product: plasmashell Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: es204904...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 153284 --> https://bugs.kde.org/attachment.cgi?id=153284=edit Screenshot.png Just after login I see a black box on the Plasma desktop. Till I open any window that covers it, then the box disappears. It also happens on the live USB. Operating System: Manjaro Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 4 × AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G Memory: 15,1 GiB of RAM Graphics Processor: AMD Radeon R6 Graphics Manufacturer: TOSHIBA Product Name: SATELLITE L50D-C System Version: PSKXJE-00600KCE -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460028] New: Grabbing a window snapped at the corner makes it to disappear
https://bugs.kde.org/show_bug.cgi?id=460028 Bug ID: 460028 Summary: Grabbing a window snapped at the corner makes it to disappear Classification: Plasma Product: kwin Version: 5.25.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- SYSTEM: - plasma-desktop 5.25.5 - plasma-framework 5.98.0 - qt5-tools 5.15.6 - linux-zen 5.19.12 SCREEN-CAST: - https://youtu.be/ESk1RFMjO_8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455272] Simplify the interface
https://bugs.kde.org/show_bug.cgi?id=455272 --- Comment #2 from Alberto Salvia Novella --- With the applet, as you type the password, it changes SSID meanwhile. Which is a bug already listed in this bug tracker. I think that the module should be intuitive despite the applet, and that just minor repositioning could improve that sensibly. Otherwise MOST people is unable to figure it out. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 455272] New: Simplify the interface
https://bugs.kde.org/show_bug.cgi?id=455272 Bug ID: 455272 Summary: Simplify the interface Product: plasma-nm Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: es204904...@gmail.com Target Milestone: --- I usually install KDE Plasma to people, and the most frequent complain I get is that is too hard to connect to wi-fi. That is, on one hand, because the applet is buggy at this time. The next option they have the system settings module, which we will talk about here. Users frequently are unable to figure out the interface. My suggestion is: - Use simpler linguistics. For example instead of SSID, name it "network name". - Visually separate common options from advanced ones. The user most of the time only needs to set the network name and the password field. The rest are special cases. - Put those common options in the same tab. - Automatically change the "connection name" to the SSID if unmodified. - If possible make more evident that you can rollout the list of nearby networks, for example, instead of having to manually type the network name. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 453277] The Kwin scripting tutorial misses crucial info
https://bugs.kde.org/show_bug.cgi?id=453277 --- Comment #4 from Alberto Salvia Novella --- Reported at: https://invent.kde.org/documentation/develop-kde-org/-/issues/77 -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 453277] The Kwin scripting tutorial misses crucial info
https://bugs.kde.org/show_bug.cgi?id=453277 --- Comment #2 from Alberto Salvia Novella --- What I do with my software is documenting it right away. Keep up with me if you can -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 453277] New: The Kwin scripting tutorial misses crucial info
https://bugs.kde.org/show_bug.cgi?id=453277 Bug ID: 453277 Summary: The Kwin scripting tutorial misses crucial info Product: docs Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Missing Content Assignee: kde-doc-engl...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- At: https://develop.kde.org/docs/extend/plasma/kwin/ Missing info: https://forum.kde.org/viewtopic.php?f=305=163749=454755#p454755 https://askubuntu.com/a/1406027/19033 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452780] Expose on the scripting api: NET_WM_BYPASS_COMPOSITOR
https://bugs.kde.org/show_bug.cgi?id=452780 --- Comment #4 from Alberto Salvia Novella --- I suspect it's just simpler to expose the structure as it is, and let the developer figure out the use case versus anticipating all the plausible scenarios. Aka separating the policy from the mechanism. The only thing we may need is to name things in a way it doesn't cause confusion, as maybe the hint currently does. There could be a property called "client.preferredCompositionMode" with the options "no preference", "composed", "not composed". Likely having a global option to change composition status won't really help further, specially if you cannot tell what the preference for each window is. For example web browsers tear badly if composition is disabled, where games usually have their own vsync mechanisms and don't benefit whatsoever from composition. So blocking composition per application makes more sense. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452796] New: The application launcher to follow its panel opacity setting during startup
https://bugs.kde.org/show_bug.cgi?id=452796 Bug ID: 452796 Summary: The application launcher to follow its panel opacity setting during startup Product: plasmashell Version: 5.24.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: es204904...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 https://youtu.be/8O5LCzCGefM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452780] Expose on the scripting api: NET_WM_BYPASS_COMPOSITOR
https://bugs.kde.org/show_bug.cgi?id=452780
--- Comment #2 from Alberto Salvia Novella ---
They are independent. `NET_WM_BYPASS_COMPOSITOR` (aka the hint) is what the
window requests, and `blocksCompositing` (aka the property) is what kwin is
currently doing with it.
The hint is inmutable, where the property is mutable. Changing the property
doesn't affect the hint, and reading the property doesn't tell what the hint
could be.
Furthermore the hint has three settings (unset, true, false), where the
property has only two (true, false).
This is relevant because through the kwin api you can't really tell what the
windows actually requests. You can only guess, for example, by storing the
initial status of composition for a window. But even then it has corner cases
where you can't really guess.
The rest of properties are unrelated. They are either signals or refer to
different objects. For example for Firefox I get:
resourceClass = firefox
blocksCompositing = false
isBlockingCompositing = undefined
setBlockingCompositing = undefined
blockingCompositingChanged = function() { [native code] }
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 452780] New: Expose on the scripting api: NET_WM_BYPASS_COMPOSITOR
https://bugs.kde.org/show_bug.cgi?id=452780 Bug ID: 452780 Summary: Expose on the scripting api: NET_WM_BYPASS_COMPOSITOR Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- The said hint tells if an application would benefit from running with or without composition: (https://specifications.freedesktop.org/wm-spec/wm-spec-latest.html#idm45446104333040) Examples: - A web browser indicates to always run composited, to prevent screen tearing. - A game indicates that it will benefit its performance to run without composition. This may greatly help scripts that manage composition: (https://gitlab.com/es20490446e/kwin-script-autocomposer/-/issues/1) Or even Kwin to decide by itself. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 451363] New: Bash highlighting fails with: "${PWD##*/}"
https://bugs.kde.org/show_bug.cgi?id=451363
Bug ID: 451363
Summary: Bash highlighting fails with: "${PWD##*/}"
Product: frameworks-syntax-highlighting
Version: 5.91.0
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: syntax
Assignee: kwrite-bugs-n...@kde.org
Reporter: es204904...@gmail.com
CC: walter.von.entfer...@posteo.net
Target Milestone: ---
This variable shows the current directory without path in Bash:
"${PWD##*/}"
But if you type it on a script, with the quotes, the next lines are no longer
highlighted.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 451131] New: Application menu goes beyond screen boundaries when in a button
https://bugs.kde.org/show_bug.cgi?id=451131 Bug ID: 451131 Summary: Application menu goes beyond screen boundaries when in a button Product: plasmashell Version: 5.24.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: es204904...@gmail.com Target Milestone: 1.0 https://youtu.be/iXip2eRz93M -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444821] Enabling "set date and time automatically" stops "ntpd.service" rather than starting it
https://bugs.kde.org/show_bug.cgi?id=444821 --- Comment #5 from Alberto Salvia Novella --- Thanks for the info. Very valuable. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444821] Enabling "set date and time automatically" shall start "ntpd.service"
https://bugs.kde.org/show_bug.cgi?id=444821 Alberto Salvia Novella changed: What|Removed |Added Summary|Enabling "set date and time |Enabling "set date and time |automatically" shall start |automatically" shall start |ntpd.service|"ntpd.service" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 178968] Unable to contact time server when the ntp daemon is running.
https://bugs.kde.org/show_bug.cgi?id=178968 --- Comment #21 from Alberto Salvia Novella --- Related: Enabling "set date and time automatically" shall start ntpd.service https://bugs.kde.org/show_bug.cgi?id=444821 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 309195] Automatic time update cannot enable the needed ntpd.service with systemctl. (systemd)
https://bugs.kde.org/show_bug.cgi?id=309195 --- Comment #2 from Alberto Salvia Novella --- The option shall do the least surprising, most functional, thing: enabling the network time protocol. https://bugs.kde.org/show_bug.cgi?id=444821 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444821] New: Enabling "set date and time automatically" shall start ntpd.service
https://bugs.kde.org/show_bug.cgi?id=444821 Bug ID: 444821 Summary: Enabling "set date and time automatically" shall start ntpd.service Product: systemsettings Version: 5.22.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_clock Assignee: p...@taniwha.com Reporter: es204904...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE: 1. sudo systemctl start ntpd 2. systemctl status ntpd 3. Date & Time -> "Set date and time automatically" 4. systemctl status ntpd RESULT: "ntpd.service" has been deactivated. ADDITIONAL INFO: Same the other way around: activating "ntpd.service" disables the box "set date and time automatically". ROOT CAUSE: In reality the box is only intended to sync the time once. But that's not what the wording suggests, neither it's the most functional thing to do. It should instead enable ntpd. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430139] plasmashell has a memory leak
https://bugs.kde.org/show_bug.cgi?id=430139 --- Comment #8 from Alberto Salvia Novella --- I discovered a while ago that, in my case, the leak was caused by a tray icon: qsyncthingtray. Yet it would be smart that the plasma service has a maximum memory limit. Systemd allows that, and automatically restarts the service once reached. For the moment I'm using the following software to accomplish that: https://gitlab.com/es20490446e/plasma-leakguard -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 431402] Make it possible to scale down/zoom out images further than the window width/height
https://bugs.kde.org/show_bug.cgi?id=431402 Alberto Salvia Novella changed: What|Removed |Added CC|es204904...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 431402] Make it possible to scale down/zoom out images further than the window width/height
https://bugs.kde.org/show_bug.cgi?id=431402 --- Comment #25 from Alberto Salvia Novella --- qView is even better. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438872] End line to have a predictable behavior
https://bugs.kde.org/show_bug.cgi?id=438872 --- Comment #3 from Alberto Salvia Novella --- Neither Github, Gitlab or most editors on Linux do this the other way. It's quite surprising to code something just to see it with different spaces in almost everything else. This reason alone is enough for me not to use Kate. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 433455] Unable to save trailing spaces
https://bugs.kde.org/show_bug.cgi?id=433455 --- Comment #33 from Alberto Salvia Novella --- Related: End line to have a predictable behavior: https://bugs.kde.org/show_bug.cgi?id=438872 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438872] New: End line to have a predictable behavior
https://bugs.kde.org/show_bug.cgi?id=438872 Bug ID: 438872 Summary: End line to have a predictable behavior Product: kate Version: 21.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: encoding Assignee: kwrite-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- Created attachment 139493 --> https://bugs.kde.org/attachment.cgi?id=139493=edit doc.txt - I open the attached document in ANY other text editor: no extra end line is shown. - I open it in Kate: extra end line is shown. - Even when having disabled the option to insert new line at the end of the document. - It doesn't happen with all documents. -- You are receiving this mail because: You are watching all bug changes.
[krandr] [Bug 103538] Control Center - Peripherals - Display, the refresh rate not change
https://bugs.kde.org/show_bug.cgi?id=103538 --- Comment #2 from Alberto Salvia Novella --- Still there: https://bugs.kde.org/show_bug.cgi?id=438795 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 438795] New: Update the refresh rate list on resolution change
https://bugs.kde.org/show_bug.cgi?id=438795 Bug ID: 438795 Summary: Update the refresh rate list on resolution change Product: KScreen Version: 5.21.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- When you change resolution, the available refresh rates to choose from are the ones from the previous resolution. Not from the current one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435223] Allowing disabling composition for the current session without login out
https://bugs.kde.org/show_bug.cgi?id=435223 --- Comment #12 from Alberto Salvia Novella --- You were right, much better as kwinscript. Thanks for the suggestion: https://store.kde.org/p/1502826/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435223] Allowing disabling composition for the current session without login out
https://bugs.kde.org/show_bug.cgi?id=435223 --- Comment #11 from Alberto Salvia Novella --- Umm, I don't know. I will think about that 樂 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435223] Allowing disabling composition for the current session without login out
https://bugs.kde.org/show_bug.cgi?id=435223 --- Comment #9 from Alberto Salvia Novella --- By the way I have figured out an even better algorithm to do this. Now: - Entering or leaving full-screen instantly toggles composition. You can't even see the transition. - Composition isn't re-enabled if the full-screen window loses focus, till that window is closed. - Applications started as windowed don't automatically block composition when maximized, for example web-browsers. - No perceivable use of CPU or IO on the system monitor. The trick was simple: only re-test for full-screen if the last known full-screen window is no longer full-screen. Everything is done in memory for maximum performance, and only iterated on window focus change. Solving problems that no bunch of people were able to solve in the last 20 years, with a few lines, is the license of being awe. https://gitlab.com/es20490446e/kwin-autocomposer/-/blob/master/root/usr/share/kwin-autocomposer/kwin-autocomposer -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435223] Allowing disabling composition for the current session without login out
https://bugs.kde.org/show_bug.cgi?id=435223 --- Comment #7 from Alberto Salvia Novella --- Okay, that was easy: only re-enabling composition after 10 seconds of being non full-screen prevented 95% of glitches. Even better: done by checking the status of the current window without using polling, but interruptions. It seems that, as usual, I will be taking all the credit: https://gitlab.com/es20490446e/kwin-autocomposer/-/blob/master/root/usr/share/kwin-autocomposer/kwin-autocomposer -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431736] Being able to set that the compositor gets disabled automatically if a window is in borderless fullscreen
https://bugs.kde.org/show_bug.cgi?id=431736 --- Comment #8 from Alberto Salvia Novella --- My opinion is this design is amateuristic, and shows low compromise with quality. Having to disable all composition so only specific content is not composite, and that not being done automatically but explicitly by each application (won't happen). It is, at its best, a collection of ugly work-arounds. Windows 98 had lower input latency for gaming than 2021 Plasma. Perhaps in another 15 years you will figure it out. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431736] Being able to set that the compositor gets disabled automatically if a window is in borderless fullscreen
https://bugs.kde.org/show_bug.cgi?id=431736 --- Comment #7 from Alberto Salvia Novella --- It should be the other way around, those applications explicitly requesting not to block composition. You are overlooking an important issue here. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 435270] SSL Error: Flatpak distribution cert errors
https://bugs.kde.org/show_bug.cgi?id=435270 Alberto Salvia Novella changed: What|Removed |Added CC|es204904...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 435270] SSL Error: Flatpak distribution cert errors
https://bugs.kde.org/show_bug.cgi?id=435270 --- Comment #5 from Alberto Salvia Novella --- If you need my feedback, add me back. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 435270] SSL Error: Flatpak distribution cert errors
https://bugs.kde.org/show_bug.cgi?id=435270 --- Comment #3 from Alberto Salvia Novella --- Why have you added me? Do you require any feedback from me on this? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435223] Allowing disabling composition for the current session without login out
https://bugs.kde.org/show_bug.cgi?id=435223 --- Comment #6 from Alberto Salvia Novella --- Not allowing toggling composition, but allowing all other kinds of things like the opengl version you use and the scaling technique? Sorry, I disagree. It's poorly designed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435223] Allowing disabling composition for the current session without login out
https://bugs.kde.org/show_bug.cgi?id=435223 --- Comment #4 from Alberto Salvia Novella --- Doing it by a shortcut, and not by an option in the panel, is quite surprising. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435223] Allowing disabling composition for the current session without login out
https://bugs.kde.org/show_bug.cgi?id=435223 --- Comment #2 from Alberto Salvia Novella --- It's just that, process wise, the extra step of having to log off seems wasteful. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435223] New: Allowing disabling composition for the current session without login out
https://bugs.kde.org/show_bug.cgi?id=435223 Bug ID: 435223 Summary: Allowing disabling composition for the current session without login out Product: kwin Version: git master Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- There's the option "enable compositor on startup", but once composition is enabled in the current session there's no way to turn it off except by disabling that first option and login off. Most likely it would be better having that option as "enable composition" alone. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435140] Rethinking which compositing settings shall be configurable by the user
https://bugs.kde.org/show_bug.cgi?id=435140 Alberto Salvia Novella changed: What|Removed |Added Resolution|INTENTIONAL |--- Status|RESOLVED|REPORTED --- Comment #3 from Alberto Salvia Novella --- Those settings where put there in a long gone era of graphics, perhaps 15 years ago. Have you checked that those still apply? For example who would see a difference by changing from opengl 2 to opengl 3? Does this case even exist? And about the scale method: who would want to set it as "crisp", a setting intended for performance on GPUs that won't work well anyway these days under plasma? Would the scale method "accurate" work poorly in any case anymore? Keep in mind that I use four different 12 years old computers, with different graphics, and even then I see no improvement whatsoever by changing to these options. Why do you think it will do for other people? Do you know of any other case? And even if some of those settings where kept, won't be better noticing the user only to change them if they experience problems? For deciding this properly, we should ask people first about how they are using these settings. Cause these sound like keeping 256 colors around. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431736] Being able to set that the compositor gets disabled automatically if a window is in borderless fullscreen
https://bugs.kde.org/show_bug.cgi?id=431736 Alberto Salvia Novella changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #5 from Alberto Salvia Novella --- Wanting to disable the compositor in full-screen isn't the exception, but the rule. 95% of user cases. Nearly all full-screen applications can enable v-sync by themselves, preventing tearing when composition is off. And not having to render desktop effects actually makes a perceivable difference. The worst thing that happens by disabling composition while being in full-screen is not having shadows and animations in a desktop you aren't actually seeing. I would say that if the option "allow applications to block compositing" is on, kwin should assume that any full-screen window wants to block compositing. And perhaps only keep composition if the window has a rule for it. I would go further and say that this option alone is enough reason to favor kwin-lowlatency over the official kwin right now, as the first gives this option and has it enabled by default. They got it right. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435103] Using an interlaced resolution hangs the desktop
https://bugs.kde.org/show_bug.cgi?id=435103 Alberto Salvia Novella changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #8 from Alberto Salvia Novella --- I have tested this only happens with radeon hardware, so that driver is the one to blame. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435140] Rethinking which compositing settings shall be configurable by the user
https://bugs.kde.org/show_bug.cgi?id=435140 --- Comment #1 from Alberto Salvia Novella --- I would ask users if they ever needed to change these settings, to figure out which are truly valuable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435140] Rethinking which compositing settings shall be configurable by the user
https://bugs.kde.org/show_bug.cgi?id=435140 Alberto Salvia Novella changed: What|Removed |Added Summary|Rethink which compositing |Rethinking which |settings to make|compositing settings shall |configurable by the user|be configurable by the user -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435140] New: Rethink which compositing settings to make configurable by the user
https://bugs.kde.org/show_bug.cgi?id=435140 Bug ID: 435140 Summary: Rethink which compositing settings to make configurable by the user Product: kwin Version: git master Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- Currently kwin exposes all kinds of settings as configurable by the user. Most of which you cannot tell the difference, or what they are about. This is because these settings are quite low end, and require deep insight on how kwin code handles composition and specially why. Exposing settings to the user makes sense when it's a matter of aesthetics, or if you cannot decide automatically if they will fit the target system. But low end predictable settings are better decided by the code itself, automatically. For example the same it won't make sense making the user decide if they have an Nvidia or an AMD card to decide the low-latency strategy, as that can be detected automatically, it also doesn't make sense making them decide what API as rendering back-end to use. It's just the highest well supported. If you ask me, I suspect that all settings except "enable composition at startup" don't make sense to an end user. They only make it more likely for them, not to improve, but to worsen their system configuration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435138] New: Assume that all full-screen applications want to block composition
https://bugs.kde.org/show_bug.cgi?id=435138 Bug ID: 435138 Summary: Assume that all full-screen applications want to block composition Product: kwin Version: git master Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- Composition provides no value when there's a full-screen application running, for 95% of cases, and you can tell performance is smoother when turned off. I don't know if the full-screen window is composited itself, but even if that wasn't the case having the rest of desktop elements being composited does nothing and decrease performance. So it would be better disabling composition by default when there's a full screen application, as kwin-lowlatency does, while perhaps allowing composition for some full screen windows if they explicitly request so with a window rule. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435103] Using an interlaced resolution hangs the desktop
https://bugs.kde.org/show_bug.cgi?id=435103 --- Comment #7 from Alberto Salvia Novella --- Any idea how to figure which subsystem is to blame? I don't see anything useful in the system logs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435103] Using an interlaced resolution hangs the desktop
https://bugs.kde.org/show_bug.cgi?id=435103 Alberto Salvia Novella changed: What|Removed |Added Summary|Desktop hangs with |Using an interlaced |Telefunken TV |resolution hangs the ||desktop -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435103] Desktop hangs with Telefunken TV
https://bugs.kde.org/show_bug.cgi?id=435103 Alberto Salvia Novella changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Alberto Salvia Novella --- It varies. Sometimes only the panel becomes unresponsive, others all the content in the screen. If there is music playing in the background it continues playing normally. I confirm you that when using 720p on this screen the desktop doesn't freeze, so this is due to using an interlaced signal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435103] Desktop hangs with Telefunken TV
https://bugs.kde.org/show_bug.cgi?id=435103 --- Comment #3 from Alberto Salvia Novella --- I'm seeing it also without composition, but there it's rare to happen. I also figured out that there's a difference between the screens that don't exhibit the problem and this one. This one uses an interlaced signal. -- You are receiving this mail because: You are watching all bug changes.
