[xdg-desktop-portal-kde] [Bug 474746] Wayland: all Gnome apps fonts are rendered without anti-aliasing
https://bugs.kde.org/show_bug.cgi?id=474746 Pellaeon Lin changed: What|Removed |Added CC||nfsmw...@gmail.com --- Comment #15 from Pellaeon Lin --- I would like to provide some more sympton to people who might be facing the same issue. For me, other than having the same sympton in gnome apps, this issue also affects Firefox (non snap version from here https://launchpad.net/~mozillateam/+archive/ubuntu/ppa ). With Firefox, I observe the following sympton: - Antialiasing looks OK, but interface fonts (including the tabs bar, url bar, menu, but not the webpage content) are ~150% size of KDE apps - There is no Maximize and Minimize window buttons, only Close button - When mouse cursor is within the Firefox window, it is ~150% larger in size, when moved outside the window, cursor returns to normal size The suggested fix of editing kde-portals.conf works. Note: this issue appeared for me on my upgrade from Kubuntu 23.04 to 23.10. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473501] New: SSH_AUTH_SOCK is empty if Konsole is launched by Ctrl+Alt+T
https://bugs.kde.org/show_bug.cgi?id=473501 Bug ID: 473501 Summary: SSH_AUTH_SOCK is empty if Konsole is launched by Ctrl+Alt+T Classification: Applications Product: konsole Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: nfsmw...@gmail.com Target Milestone: --- SUMMARY SSH_AUTH_SOCK is empty if Konsole is launched by Ctrl+Alt+T. SSH_AUTH_SOCK is set normally if Konsole is launched from the start menu. In Yakuake the variable is also set normally. STEPS TO REPRODUCE 1. Press Ctrl+Alt+T to launch Konsole 2. run `echo $SSH_AUTH_SOCK` OBSERVED RESULT $SSH_AUTH_SOCK is not set EXPECTED RESULT $SSH_AUTH_SOCK should be set. In my case it should be set to `/run/user/1000/openssh_agent` SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 23.04 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION This bug only occurs in Wayland, not X11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 Pellaeon Lin changed: What|Removed |Added CC||nfsmw...@gmail.com --- Comment #32 from Pellaeon Lin --- *** Bug 464732 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464732] plasmashell hangs at a futex related to QXcbConnection::xi2HandleDeviceChangedEvent
https://bugs.kde.org/show_bug.cgi?id=464732 Pellaeon Lin changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Pellaeon Lin --- I saw a similar bug report https://bugs.kde.org/show_bug.cgi?id=457847 and tried its workaround downgrading Mesa. It seems to work. I haven't experienced any freezes for two weeks now. Closing this as duplicate. *** This bug has been marked as a duplicate of bug 457847 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464732] plasmashell hangs at a futex related to QXcbConnection::xi2HandleDeviceChangedEvent
https://bugs.kde.org/show_bug.cgi?id=464732 --- Comment #2 from Pellaeon Lin --- The bug happened a few more times after my initial reporting, usually once around every 3 days. I'd like to add a few points of observations and questions: When the last time freeze happened, I tried doing the following things: 1. Switch to tty2 using Ctrl+Alt+F2 and log in 2. Run `killall plasmashell` 3. Switch back to tty1 using Ctrl+Alt+F1 4. I observe that the screen does not change, displaying the same content as it was frozen. It does not respond to any keyboard input (except for Capslock). I can still move the mouse but clicking has no effect. 5. I observe that I can still toggle Caps Lock (the light will switch on/off). I have the following questions: 1. According to this thread https://forum.manjaro.org/t/plasmashell-freezes/127677 , `killall plasmashell` should stop the shell and I can launch a new terminal and run `plasmashell --replace` to restart it. However as I mentioned in (4) above it stays frozen. Does this mean that this problem is not related to plasmashell? 2. According to https://wiki.ubuntu.com/X/Troubleshooting/Freeze , my symptons might indicate a X server issue? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464732] New: plasmashell hangs at a futex related to QXcbConnection::xi2HandleDeviceChangedEvent
https://bugs.kde.org/show_bug.cgi?id=464732 Bug ID: 464732 Summary: plasmashell hangs at a futex related to QXcbConnection::xi2HandleDeviceChangedEvent Classification: Plasma Product: plasmashell Version: 5.25.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: nfsmw...@gmail.com Target Milestone: 1.0 Created attachment 14 --> https://bugs.kde.org/attachment.cgi?id=14&action=edit backtrace SUMMARY Plasmashell and applications freeze randomly, none of them respond to keyboard or mouse input. I use my computer everyday and this happens about twice a week. It only happens since my upgrade from Ubuntu 22.04 to 22.10. I switched to tty and used `sudo strace -p` on the plasmashell process. It showed that plasmashell stucked at a futex call. I loaded the debug symbols and attached the process with gdb. It showed that plasmashell stuck at a xcb_wait_for_reply call inside QXcbConnection::xi2HandleDeviceChangedEvent. However, I did not plug / unplug any device from the computer at the time of freeze. This freeze also happens when the computer (Thinkpad X13 Gen 2 AMD) is not connected to any external device (no bluetooth device either). The backtrace is attached. I understand this might be hard to debug, so please tell me things I can try and information to collect, and I will collect them when the next crash happens. STEPS TO REPRODUCE 1. Use desktop normally OBSERVED RESULT Desktop freezes EXPECTED RESULT Desktop not freeze SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.10 (System installed via Ubuntu installer, then apt install kubuntu-desktop afterwards) (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Graphics platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 338796] Blank the screen using Esc key while on the lock screen
https://bugs.kde.org/show_bug.cgi?id=338796 Pellaeon Lin changed: What|Removed |Added CC||nfsmw...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396010] Krita defaults to fallback locale instead of preferred locale
https://bugs.kde.org/show_bug.cgi?id=396010 --- Comment #8 from Pellaeon Lin --- Thank you all for fixing this so quickly! Many kudos. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396010] Krita defaults to fallback locale instead of preferred locale
https://bugs.kde.org/show_bug.cgi?id=396010 Pellaeon Lin changed: What|Removed |Added CC||nfsmw...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396010] Krita defaults to fallback locale instead of preferred locale
https://bugs.kde.org/show_bug.cgi?id=396010 --- Comment #2 from Pellaeon Lin --- Yes, this will happen without klanguageoverriderc present, when my system locale setting is: 1. Chinese Traditional (Taiwan) (default, highest priority) 2. English 3. Chinese Simplified 4. Korean -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396010] New: Krita defaults to fallback locale instead of preferred locale
https://bugs.kde.org/show_bug.cgi?id=396010 Bug ID: 396010 Summary: Krita defaults to fallback locale instead of preferred locale Product: krita Version: 4.1.0 Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: nfsmw...@gmail.com Target Milestone: --- As titled, this is the first time I installed Krita, and when I opened it, it showed a Korean interface. My system locale settings is: 1. Chinese Traditional (Taiwan) (default, highest priority) 2. English 3. Chinese Simplified 4. Korean Seems that Krita automatically uses the least preferred language. I'm suspecting that this might be involved with how Qt handles fallback locales? https://doc.qt.io/qt-5/internationalization.html （I've never programmed in Qt) Also, as a test, I removed 4. Korean locale from my system, and Krita now shows English. I'm sure Krita 4.1.0 ships with Chinese Traditional locale, because on Linux it shows Chinese Traditional without problem. I'd be happy to help triage the bug, please instruct me on how to do that. Thanks! -- You are receiving this mail because: You are watching all bug changes.
