[konsole] [Bug 462910] Missing font ligatures
https://bugs.kde.org/show_bug.cgi?id=462910
--- Comment #5 from David Mak ---
I wonder whether it is possible to make enabling font ligatures more
discoverable, since:
(1) it is changed to be disabled by default, meaning that users will need to
find the option to enable it,
(2) the option to enable ligatures ("Word mode") do not appear to suggest that
it control the rendering of ligatures, and
(3) several options under "Word mode" controls how ligatures are rendered, and
only a specific combination of options will restore ligature rendering to the
pre-22.12 behavior.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 462910] New: Missing font ligatures
https://bugs.kde.org/show_bug.cgi?id=462910 Bug ID: 462910 Summary: Missing font ligatures Classification: Applications Product: konsole Version: 22.12.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: david.18.19...@gmail.com Target Milestone: --- SUMMARY After upgrading to Konsole 22.12.0, font ligatures are not rendered anymore. STEPS TO REPRODUCE 1. Upgrade to Konsole 22.12.0 OBSERVED RESULT Font ligatures are not rendered anymore. EXPECTED RESULT Font ligatures should be rendered, or an option should be provided to toggle this option. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.12-arch1-1 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION 461530 mentioned that "ligatures will be disabled by default, but there is an option to enable them". However, I cannot find this option in Konsole settings or profile settings. This affects Yakuake as well. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #12 from David Mak --- Created attachment 153423 --> https://bugs.kde.org/attachment.cgi?id=153423=edit journalctl --user logs from a boot where Powerdevil fails to launch -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 David Mak changed: What|Removed |Added Resolution|WORKSFORME |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #10 from David Mak --- I can attach a few more logs tomorrow when I get back to my laptop, since this issue has persisted for me. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #5 from David Mak --- Created attachment 150801 --> https://bugs.kde.org/attachment.cgi?id=150801=edit Powerdevil Logs from Journalctl, last 10 boots. (In reply to Nicolas Fella from comment #3) > Can you run "systemctl --user status plasma-powerdevil.service" when it > failed and show the output? Since I am not able to reproduce it every time, here is the `journactl --user -u plasma-powerdevil` for the last 10 boots. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #4 from David Mak --- (In reply to Nate Graham from comment #1) > Seems quite relevant: > > > Jul 21 10:14:08 david-laptop org_kde_powerdevil[1135]: org.kde.powerdevil: > > org.kde.powerdevil.discretegpuhelper.hasdualgpu failed > > Is this a dual-GPU system? It's not. It's an APU (Ryzen 7 PRO 6850U with Radeon 680M) with no discrete GPU. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] New: Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 Bug ID: 456966 Summary: Failed to start Powerdevil on AMD Rembrandt Product: Powerdevil Version: 5.25.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: david.18.19...@gmail.com CC: m...@ratijas.tk Target Milestone: --- SUMMARY Sometimes when logging into a user, instead of displaying the splash screen followed by the desktop, the screen will have no output for ~15 seconds before displaying the splash screen and desktop (with only the wallpaper). The default panel and any shortcuts will not work on the desktop. Whenever this happens, systemctl logs seem to indicate that Powerdevil's job timed out. This issue does not occur on an AMD Ryzen 7 PRO 4750U laptop (Renoir). STEPS TO REPRODUCE 1. Login into any user. OBSERVED RESULT Screen turns off for ~10-15 seconds, then splash screen shows for 3 seconds, then only the wallpaper is shown (no configured panel will show, and no keyboard shortcut works). Only occurs occasionally. EXPECTED RESULT Splash screen should show, followed by the usual desktop environment with panels. SOFTWARE/OS VERSIONS Linux: 5.18.12-arch1-1 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION `systemctl --user` logs: ``` Jul 21 10:14:02 david-laptop systemd[742]: Starting Powerdevil... Jul 21 10:14:08 david-laptop systemd[742]: plasma-powerdevil.service: start operation timed out. Terminating. Jul 21 10:14:08 david-laptop systemd[742]: plasma-powerdevil.service: Failed with result 'timeout'. Jul 21 10:14:08 david-laptop systemd[742]: Failed to start Powerdevil. Jul 21 10:14:08 david-laptop systemd[742]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 1. Jul 21 10:14:08 david-laptop systemd[742]: Stopped Powerdevil. Jul 21 10:14:08 david-laptop systemd[742]: Starting Powerdevil... Jul 21 10:14:08 david-laptop org_kde_powerdevil[1135]: org.kde.powerdevil: org.kde.powerdevil.discretegpuhelper.hasdualgpu failed Jul 21 10:14:13 david-laptop systemd[742]: plasma-powerdevil.service: start operation timed out. Terminating. Jul 21 10:14:13 david-laptop systemd[742]: plasma-powerdevil.service: Failed with result 'timeout'. Jul 21 10:14:13 david-laptop systemd[742]: Failed to start Powerdevil. ``` This issue only started occurring since I upgraded from a AMD Renoir (Ryzen 7 PRO 4750U) laptop to a AMD Rembrandt (Ryzen 7 PRO 6850U) laptop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438618] New: XWayland fullscreen corruption using Intel iGPU
https://bugs.kde.org/show_bug.cgi?id=438618 Bug ID: 438618 Summary: XWayland fullscreen corruption using Intel iGPU Product: kwin Version: 5.22.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: david.18.19...@gmail.com Target Milestone: --- SUMMARY I have filed a similar bug report to Mesa, and they have directed me here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4913. Apologies if this is the wrong component to file the report to When running Vulkan applications in fullscreen via XWayland with an Intel iGPU, the application window becomes corrupted. This only appears to happen if the window is in-focus, uses XCB, and (as far as I can test) uses Vulkan. STEPS TO REPRODUCE 1. Clone Sascha Willem's Vulkan examples, and build the samples in XCB mode (without specifying any flags in CMake) 2. Run any example in fullscreen (e.g. ./gltfscenerendering --fullscreen) OBSERVED RESULT The window becomes corrupted when in-focus. When out-of-focus, the application window renders correctly. Capturing the application window via other software (e.g. OBS Studio and Spectacle) will also cause it to output correctly. EXPECTED RESULT No visual corruption. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.12.10-arch1-1 (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.83.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION This bug was originally filed to Mesa (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4913). It can only be reproduced using an Intel iGPU and not an AMD iGPU or dGPU. -- You are receiving this mail because: You are watching all bug changes.
