[neon] [Bug 485494] fcitx5 qt6 library cause desktop failed to start, their maintainer suggests rebuilding the package against new qt
https://bugs.kde.org/show_bug.cgi?id=485494 --- Comment #9 from Weng Xuetian --- (In reply to trulyliu from comment #7) > @Weng Xuetian > Which package should be rebuilt? Could you give a simple instruction? apt source fcitx5-qt and use dpkg-buildpackage, you probably want to look up how to build it and you'll also hit some deb lint error... I'm not so sure how neon build the new version of package without https://invent.kde.org/neon/backports-jammy/fcitx5-qt updated with debian upstream.. but it might be a good idea to sync with upstream debian/ in the next update.. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485494] fcitx5 qt6 library cause desktop failed to start, their maintainer suggests rebuilding the package against new qt
https://bugs.kde.org/show_bug.cgi?id=485494
Weng Xuetian changed:
What|Removed |Added
Component|Packages User Edition |Packages Testing Edition
CC||wen...@gmail.com
Assignee|neon-b...@kde.org |carlosdema...@gmail.com
--- Comment #6 from Weng Xuetian ---
Fcitx dev here, I downloaded
https://files.kde.org/neon/images/testing/20240423-0253/neon-testing-20240423-0253.iso
and installed it in qemu.
So indeed, any program that loads fcitx5's im module would crash immediately.
But with my experience on archlinux, it should be fine with either Qt6.6 or Qt
6.7.
So I just try this on kwrite, QT_DEBUG_PLUGINS=1 QT_IM_MODULE=fcitx kwrite
And it shows following lines:
```
{
"IID": "org.qt-project.Qt.QPlatformInputContextFactoryInterface.5.1",
"MetaData": {
"Keys": [
"fcitx",
"fcitx5"
]
},
"archlevel": 1,
"className": "QFcitx5PlatformInputContextPlugin",
"debug": false,
"version": 394752
}
```
Comparing to other plugins, they are showing "395008".
394752 is 0x60600, and 395008 is 0x60700, which is the Qt version
(major<<16|minor<<8|patch).
It clearly indicates that the qt6 part with in fcitx5-qt is built against Qt
6.6, not the Qt 6.7. For qpa platform plugin it's unfortunate that it need to
be rebuilt against any Qt minor update.
I also tried to rebuild with neon's deb source. Problem also go away, so it
seems that a rebuild should fix the issue.
For users who hit this issue but still want to use fcitx5, if you ARE planning
using wayland, you can:
1. Go to TTY (Ctrl+Alt+F(1,2,3...)
2. Run "im-config -n none", this will disable im-config profile and all the
environment variable like QT_IM_MODULE to be set. This is actually OK if you're
gonna use wayland.
3. Now you should be able to login, you can go to Systemsettings->Virtual
keyboard-> select fcitx5 there. You should be able to use fcitx5 input method
as long as application is running under wayland.
For more details on other thing to setup, check
https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland#KDE_Plasma
--
You are receiving this mail because:
You are watching all bug changes.
[i18n] [Bug 485357] KDE Git repos are flooded with commits that do not contain translation changes
https://bugs.kde.org/show_bug.cgi?id=485357 Weng Xuetian changed: What|Removed |Added Assignee|wen...@gmail.com|i...@guoyunhe.me -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 484451] translation errors(zh_CN) in Kwin
https://bugs.kde.org/show_bug.cgi?id=484451 Weng Xuetian changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||6.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482995] New: Randomly having an extra empty button in the systemsettings save confirmation dialog
https://bugs.kde.org/show_bug.cgi?id=482995 Bug ID: 482995 Summary: Randomly having an extra empty button in the systemsettings save confirmation dialog Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: wen...@gmail.com Target Milestone: --- Created attachment 166801 --> https://bugs.kde.org/attachment.cgi?id=166801=edit Empty button SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Change settings in systemsettings 2. Click another tab to trigger save confirmation dialog OBSERVED RESULT See screenshot (This does not always happens. I don't know how to reliably reproduce it yet). EXPECTED RESULT Buttons are correct SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.1 (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I guess this may not specific to systemsettings, but for now I only see it in this. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 479441] New: Screen locker ignores enter in password field in Plasma 6 X11
https://bugs.kde.org/show_bug.cgi?id=479441 Bug ID: 479441 Summary: Screen locker ignores enter in password field in Plasma 6 X11 Classification: Plasma Product: kscreenlocker Version: 5.91.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: wen...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Xephyr :2 2. DISPLAY=:2 /usr/lib/kscreenlocker_greet 3. type password and enter OBSERVED RESULT Enter is ignored, click button with mouse works. EXPECTED RESULT Unlock screen after enter is pressed, interestingly, wayland doesn't have such issue. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7beta ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 478910] New: Kirigami is having ReferenceError on enum values
https://bugs.kde.org/show_bug.cgi?id=478910 Bug ID: 478910 Summary: Kirigami is having ReferenceError on enum values Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.247.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: wen...@gmail.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE Launch systemsettings, while I'm aware of https://bugreports.qt.io/browse/QTBUG-120189, right now I'm setting QML_DISABLE_DISK_CACHE=1 to make it partially work OBSERVED RESULT See lots of errors like file:///usr/lib/qt6/qml/org/kde/kirigami/Separator.qml:50: ReferenceError: Weight is not defined file:///usr/lib/qt6/qml/org/kde/kirigami/Heading.qml:97: ReferenceError: Type is not defined and display having some issues about applying the style EXPECTED RESULT work without error SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.91.0 (available in About System) KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0 (beta1) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478705] New: Legacy X11 keyboard support does not receive key mask state update when Alt+tab is used
https://bugs.kde.org/show_bug.cgi?id=478705 Bug ID: 478705 Summary: Legacy X11 keyboard support does not receive key mask state update when Alt+tab is used Classification: Plasma Product: kwin Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: wen...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Set "All" to X11 legacy app support under kwin wayland 2. start xinput test-xi2 --root 3. first press any key like "a", and see modifier line is "base 0". 4. make sure alt+tab is set for window switching, and the focused window is wayland window. 5. press alt + tab with alt being held. 6. release all key. 7. press "a" again OBSERVED RESULT After that, the any key pressed is with "modifier base 0x8", which means alt mask is set. Press alt again will make the state back to normal. EXPECTED RESULT modifier is return to "base 0" because alt is released. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.90.0 (available in About System) KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION I suspect that alt is not forwarded to xwayland at all since kwin captured it for alt+tab, and later xwayland's key state is kept in a wrong state until the next X window is focused. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 477349] New: ListItemDragHandle's code example doesn't really work
https://bugs.kde.org/show_bug.cgi?id=477349 Bug ID: 477349 Summary: ListItemDragHandle's code example doesn't really work Classification: Frameworks and Libraries Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: wen...@gmail.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided Created attachment 163350 --> https://bugs.kde.org/attachment.cgi?id=163350=edit copy-pasted example SUMMARY STEPS TO REPRODUCE 1. copy the example in ListItemDragHandle 2. run with qml6 OBSERVED RESULT ReferenceError: model is not defined EXPECTED RESULT example works -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 450003] Kate crashed while I was typing
https://bugs.kde.org/show_bug.cgi?id=450003 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com --- Comment #2 from Weng Xuetian --- Send a potential fix for this for qt : https://codereview.qt-project.org/c/qt/qtwayland/+/445585 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461021] Xwayland window blur under new "Don't scale Xwayland" option in 5.26 doesn't work properly.
https://bugs.kde.org/show_bug.cgi?id=461021 Weng Xuetian changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/commit/fda53d8253b5 |ma/kwin/commit/00388f2b8a4f |583d253bd35315229768fd41457 |b81515eadf2768d49d09c4e31d6 |8 |d --- Comment #3 from Weng Xuetian --- Git commit 00388f2b8a4fb81515eadf2768d49d09c4e31d6d by Weng Xuetian. Committed on 01/11/2022 at 03:21. Pushed by xuetianweng into branch 'Plasma/5.26'. Fix blur/contrast for X11 window if Xwayland is not scaled. X property from X11 window contains X native coordinates. Need to apply transform to use them in the effects like blur/contrast. (cherry picked from commit fda53d8253b5583d253bd35315229768fd414578) M +2-1src/effects/backgroundcontrast/contrast.cpp M +2-1src/effects/blur/blur.cpp https://invent.kde.org/plasma/kwin/commit/00388f2b8a4fb81515eadf2768d49d09c4e31d6d -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461021] Xwayland window blur under new "Don't scale Xwayland" option in 5.26 doesn't work properly.
https://bugs.kde.org/show_bug.cgi?id=461021 Weng Xuetian changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/fda53d8253b5 ||583d253bd35315229768fd41457 ||8 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Weng Xuetian --- Git commit fda53d8253b5583d253bd35315229768fd414578 by Xuetian Weng, on behalf of Weng Xuetian. Committed on 31/10/2022 at 22:42. Pushed by xuetianweng into branch 'master'. Fix blur/contrast for X11 window if Xwayland is not scaled. X property from X11 window contains X native coordinates. Need to apply transform to use them in the effects like blur/contrast. M +2-1src/effects/backgroundcontrast/contrast.cpp M +2-1src/effects/blur/blur.cpp https://invent.kde.org/plasma/kwin/commit/fda53d8253b5583d253bd35315229768fd414578 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461021] New: Xwayland window blur under new "Don't scale Xwayland" option in 5.26 doesn't work properly.
https://bugs.kde.org/show_bug.cgi?id=461021 Bug ID: 461021 Summary: Xwayland window blur under new "Don't scale Xwayland" option in 5.26 doesn't work properly. Classification: Plasma Product: kwin Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: wen...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Enable blur 2. Try an application with blur OBSERVED RESULT Blur region is scaled EXPECTED RESULT Blur region should not be scaled like Xwayland app itself. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457149] Plasma start with systemd breaks certain autostart file
https://bugs.kde.org/show_bug.cgi?id=457149 Weng Xuetian changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Weng Xuetian --- (In reply to David Edmundson from comment #2) > out of curiosity which .desktop file were you affected by? Was it > ibus-daemon? I don't use ibus. This https://github.com/fcitx/fcitx/blob/eb54e2b244e93d695c83c1f3bdbe6ee83155058a/data/fcitx-autostart.desktop.in#L12 It just contains the "X-GNOME-Autostart-Phase" due to some random reason. Maybe because I want it start after the panel is loaded in GNOME 2 times. I don't know if it does anything good, but it was just there and suddenly break by plasma updade. (Also I don't know why I remove this line in fcitx5 which make it unaffected luckily) So to me the situation as fcitx dev is not that bad, because mainstream distro (debian/ubuntu/fedora) does not use fcitx's own xdg autostart for input method. Right now the most affected distro is arch linux, so I just release a new version of old fcitx 4 in emergency simply avoid breakage by plasma. I'm actually reading the bug and they even find fcitx is affected? but no one wants to just open a bug to fcitx upstream? https://github.com/systemd/systemd/issues/18791#issuecomment-788922727 I have no idea about X-system-skip, not sure what's the semantics of it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449488] GetSessionIdleTime always returns 0 on Wayland
https://bugs.kde.org/show_bug.cgi?id=449488 --- Comment #2 from Weng Xuetian --- ScreenSaver service is provided by kwin_wayland on wayland session. The return value comes from kwin's own kidle time implementation, which is at https://invent.kde.org/plasma/kwin/-/blob/master/src/plugins/idletime/poller.cpp#L79 We would just need to have a valid implementation for it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449488] GetSessionIdleTime always returns 0 on Wayland
https://bugs.kde.org/show_bug.cgi?id=449488 Weng Xuetian changed: What|Removed |Added Component|general |general Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Product|kscreenlocker |kwin CC||wen...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457149] New: Plasma start with systemd breaks certain autostart file
https://bugs.kde.org/show_bug.cgi?id=457149 Bug ID: 457149 Summary: Plasma start with systemd breaks certain autostart file Product: plasmashell Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: wen...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Right now, plasma autostart relies on systemd's xdg autostart generator. There are certain cases that is not handled with current mechanism. For the desktop file with X-systemd-skip or X-GNOME-Autostart-Phase (based on the doc, https://www.freedesktop.org/software/systemd/man/systemd-xdg-autostart-generator.html ), the service won't be generated, but also it doesn't mean they should not be started. Those should go through the traditional autostart code and be started. Right now startplasma would just skip all of such desktop file that is not generated by systemd. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 456379] Code completion combo box doesn't always show up on wayland
https://bugs.kde.org/show_bug.cgi?id=456379 Weng Xuetian changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Weng Xuetian --- Now I realized it's actually an Qt issue. Right now the attempt to fix this: https://codereview.qt-project.org/c/qt/qtwayland/+/422129 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 456379] New: Code completion combo box doesn't always show up on wayland
https://bugs.kde.org/show_bug.cgi?id=456379 Bug ID: 456379 Summary: Code completion combo box doesn't always show up on wayland Product: kdevelop Version: 5.8.220402 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: wen...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open any project 2. type code that should show completion OBSERVED RESULT Completion combobox does not always show up, and I can still navigate the combobox by keyboard just like it's still there. EXPECTED RESULT Completion combo box always show up. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.94 Qt Version: 5.15.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455849] mouse selector keeps resetting itself to "Asus keyboard"
https://bugs.kde.org/show_bug.cgi?id=455849 Weng Xuetian changed: What|Removed |Added Version|unspecified |5.24.5 Component|general |kcm_mouse Product|kimtoy |systemsettings Assignee|shuizhuyuan...@hotmail.com |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455499] KWin script doesn't load any more in 5.25.0
https://bugs.kde.org/show_bug.cgi?id=455499 Weng Xuetian changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Weng Xuetian --- Seems already fixed by 8a19796aa676f0e278a9c5c5b7096a9ab2298f0c / 9419acc1ff5ccd039d68be315dd4ac161b78b615 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455499] New: KWin script doesn't load any more in 5.25.0
https://bugs.kde.org/show_bug.cgi?id=455499 Bug ID: 455499 Summary: KWin script doesn't load any more in 5.25.0 Product: kwin Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: wen...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. enable some built in script shipped with kwin in the kcm 2. apply OBSERVED RESULT nothing happened, if I switch away in kcm and switch back, all script are unchecked. EXPECTED RESULT script loads and runs SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.25.0 (available in About System) KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452435] [Wayland] SDL Applications crash with error "wl_registry@2: error 0: invalid global wp_drm_lease_device_v1 (50)" when external display is unplugged
https://bugs.kde.org/show_bug.cgi?id=452435 --- Comment #15 from Weng Xuetian --- Git commit dc09ce85f00b3a790e2817888067c3826280dd8e by Weng Xuetian. Committed on 16/04/2022 at 20:18. Pushed by xuetianweng into branch 'Plasma/5.24'. Fix race in wp_drm_lease_v1. Basically this is a well known issue in wayland for globals. If bind comes after destroyed, it will raise a invalid global error. The common practice is to delay the destroy of global. Similar technique is also applied to wl_output. (cherry picked from commit cdc9dcfb0a1f0445c46ee2cefa114329a2408555) M +5-9src/server/drmleasedevice_v1_interface.cpp M +1-1src/server/drmleasedevice_v1_interface_p.h https://invent.kde.org/plasma/kwayland-server/commit/dc09ce85f00b3a790e2817888067c3826280dd8e -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452435] [Wayland] SDL Applications crash with error "wl_registry@2: error 0: invalid global wp_drm_lease_device_v1 (50)" when external display is unplugged
https://bugs.kde.org/show_bug.cgi?id=452435 --- Comment #14 from Weng Xuetian --- Git commit cdc9dcfb0a1f0445c46ee2cefa114329a2408555 by Weng Xuetian. Committed on 16/04/2022 at 07:01. Pushed by xuetianweng into branch 'master'. Fix race in wp_drm_lease_v1. Basically this is a well known issue in wayland for globals. If bind comes after destroyed, it will raise a invalid global error. The common practice is to delay the destroy of global. Similar technique is also applied to wl_output. M +5-9src/server/drmleasedevice_v1_interface.cpp M +1-1src/server/drmleasedevice_v1_interface_p.h https://invent.kde.org/plasma/kwayland-server/commit/cdc9dcfb0a1f0445c46ee2cefa114329a2408555 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452435] [Wayland] SDL Applications crash with error "wl_registry@2: error 0: invalid global wp_drm_lease_device_v1 (50)" when external display is unplugged
https://bugs.kde.org/show_bug.cgi?id=452435 --- Comment #11 from Weng Xuetian --- There are two bugs, in xwayland and kwayland-server. This https://invent.kde.org/plasma/kwayland-server/-/merge_requests/370 tries to fix the race condition triggered by kwayland-server. And xwayland has a bug of invalid pointer access that may crash xwayland. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/894 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452435] [Wayland] SDL Applications crash with error "wl_registry@2: error 0: invalid global wp_drm_lease_device_v1 (50)" when external display is unplugged
https://bugs.kde.org/show_bug.cgi?id=452435 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #10 from Weng Xuetian --- KWIN_XWAYLAND_DEBUG=1 Some relevant log from Xwayland, it seems there's some race. [1937782.511] wl_registry@15.global_remove(52) [1937782.581] wl_registry@2.global_remove(52) [1937782.734] -> zxdg_output_v1@31.destroy() [1937782.754] wl_registry@15.global_remove(51) [1937782.761] wl_registry@2.global_remove(51) [1937782.768] wl_registry@15.global_remove(50) [1937782.776] wl_registry@2.global_remove(50) [1937782.785] -> wp_drm_lease_device_v1@29.release() [1937782.792] wl_registry@15.global(53, "wp_drm_lease_device_v1", 1) [1937782.810] wl_registry@2.global(53, "wp_drm_lease_device_v1", 1) [1937782.834] -> wl_regis...@2.bind(53, "wp_drm_lease_device_v1", 1, new id [unknown]@32) [1937782.861] wl_registry@15.global_remove(53) [1937782.868] wl_registry@2.global_remove(53) [1937782.876] -> wp_drm_lease_device_v1@32.release() error in client communication (pid 43035) [1937783.583] wl_display@1.delete_id(31) [1937783.603] wl_display@1.delete_id(29) [1937783.611] wl_display@1.error(wl_registry@2, 0, "invalid global wp_drm_lease_device_v1 (53)") -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442846] Blocking calls to Xwayland can make kwin freeze
https://bugs.kde.org/show_bug.cgi?id=442846 --- Comment #26 from Weng Xuetian --- Also another observation is that, if Xwayland is killed or crashed, all new X client will just blocking on X. I don't think this should happen. I'm thinking that kwin might not release the socket fd or sth properly, so x client are still indefinitely waiting for X socket, including kwin itself. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442846] Blocking calls to Xwayland can make kwin freeze
https://bugs.kde.org/show_bug.cgi?id=442846 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com --- Comment #25 from Weng Xuetian --- It seems that I'm also affected by this. For some other probably unrelated reason, unplug external monitor would cause SIGSEGV on Xwayland on my setup, but I observed that kwin freeze due to this in this case. I gdb attached to Xwayland and noticed Xwayland received a sigsegv, after detach from gdb, noticed Xwayland become a zombie process. Relevant stack trace in kwin, looks similar to the existing ones. It seems that kwin is blocked on some X event request and never returns. I'd say we should try to manage Xwayland process in a separate thread, otherwise we may fail to collect xwayland process when making a blocking call. #0 0x7f18b7bd32af in poll () at /usr/lib/libc.so.6 #1 0x7f18b8d8963b in () at /usr/lib/libxcb.so.1 #2 0x7f18b8d8b08f in () at /usr/lib/libxcb.so.1 #3 0x7f18b8d8b1a2 in xcb_wait_for_reply () at /usr/lib/libxcb.so.1 #4 0x7f18ba58339a in KWin::Workspace::updateXStackingOrder() () at /usr/lib/libkwin.so.5 #5 0x7f18ba583479 in KWin::Workspace::xStackingOrder() const () at /usr/lib/libkwin.so.5 #6 0x7f18ba512243 in KWin::Compositor::windowsToRender() const () at /usr/lib/libkwin.so.5 #7 0x7f18ba5127be in KWin::Compositor::composite(KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #8 0x7f18b84af463 in () at /usr/lib/libQt5Core.so.5 #9 0x7f18ba4d07a7 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #10 0x7f18ba5a1c18 in KWin::RenderLoopPrivate::dispatch() () at /usr/lib/libkwin.so.5 #11 0x7f18b84af463 in () at /usr/lib/libQt5Core.so.5 #12 0x7f18b84b169f in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #13 0x7f18b84a2766 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7f18b8f3c1c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7f18b847e5aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7f18b84c9dd5 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #17 0x7f18b84ca272 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x557e3c5a97e2 in () #19 0x7f18b847688b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x7f18b8481fd7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #21 0x557e3c4b832a in () #22 0x7f18b7afa310 in __libc_start_call_main () at /usr/lib/libc.so.6 #23 0x7f18b7afa3c1 in __libc_start_main_impl () at /usr/lib/libc.so.6 #24 0x557e3c4b9ab5 in () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450737] 5.24.2 break multi monitor setup on wayland
https://bugs.kde.org/show_bug.cgi?id=450737 --- Comment #3 from Weng Xuetian --- (In reply to Zamundaaa from comment #2) > I'm relatively certain that the MR should fix it but could you test it to > make sure? I don't have a multi-gpu system I manually cherry-pick against Plasma/5.24 and it seems to fix my issue, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450737] New: 5.24.2 break multi monitor setup on wayland
https://bugs.kde.org/show_bug.cgi?id=450737 Bug ID: 450737 Summary: 5.24.2 break multi monitor setup on wayland Product: kwin Version: 5.24.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: wen...@gmail.com Target Milestone: --- SUMMARY 5.24.2 may give me black screen on laptop when external monitor is plugged. The first bad commit is 29bc1173c70b2a31753c791aa60fb33ee320440a backends/drm: ignore enabled state of outputs for the lifetime of surfaces STEPS TO REPRODUCE 1. plugin second monitor 2. log in into kwin OBSERVED RESULT laptop screen is still showing tty or blank (but not operatable). adjust systemsetting doesn't help to restore it into a usable state. Downgrade to 5.24.1 works. EXPECTED RESULT screen show content correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.24.2 Archlinux KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450014] Unable to switch input method in Overview search
https://bugs.kde.org/show_bug.cgi?id=450014 Weng Xuetian changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Weng Xuetian --- (In reply to Nate Graham from comment #1) > Does it work in other text fields in Plasma, such as the search field for > the Application Launcher or the Networks applet? I already did some initial investigation This is solely a overview effect issue. I'm not exactly sure about wayland case in terms of making it work, because it would be like talk to kwin itself or implement a special QPA. I'd at least assume we can try to make it work under X11. I think the reason behind this is that kwin is using QOffscreenWindow for this effect, and somehow setFocusObject is never triggered to the input method. Thus, input method doesn't know it the text field has focus and just bypass all the key event. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 428213] Plasma text fields (and only Plasma text fields) elements ignore Asian input via IBUS
https://bugs.kde.org/show_bug.cgi?id=428213 --- Comment #8 from Weng Xuetian --- The issue can be easily reproduced by 1. quit ibus 2. start kwrite 3. start ibus 4. try to type in kwrite. Which demonstrate that it is not relevant to plasma. IBus's own implemenation of Gtk im module works well if ibus restarts. It's solely Qt's ibus plugin problem that can't handle such case well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 428213] Plasma text fields (and only Plasma text fields) elements ignore Asian input via IBUS
https://bugs.kde.org/show_bug.cgi?id=428213 --- Comment #7 from Weng Xuetian --- I suggest report this to Qt to fix their IBus implementation. Their implementation of ibus platform input context should be able to handle this just like what I did in fcitx. If they implement it correctly, there should be no tricks required on the plasma side. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449112] Plugin external monitor may make plasma blank desktop and panel placed on the wrong screen with 5.24 beta on wayland
https://bugs.kde.org/show_bug.cgi?id=449112 Weng Xuetian changed: What|Removed |Added Summary|Plugin external monitor may |Plugin external monitor may |make plasma blank desktop |make plasma blank desktop |and panel placed on the |and panel placed on the |wrong screen with 5.24 beta |wrong screen with 5.24 beta ||on wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449112] New: Plugin external monitor may make plasma blank desktop and panel placed on the wrong screen with 5.24 beta
https://bugs.kde.org/show_bug.cgi?id=449112 Bug ID: 449112 Summary: Plugin external monitor may make plasma blank desktop and panel placed on the wrong screen with 5.24 beta Product: plasmashell Version: 5.23.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: wen...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 145897 --> https://bugs.kde.org/attachment.cgi?id=145897=edit screenshot when problem happens SUMMARY While it works mostly OK in 5.23.5, with 5.23.90 plasma I always get plasma show the wrong placement after plugin an external screen. STEPS TO REPRODUCE 1. plug in external monitor OBSERVED RESULT Panel that previously on the laptop screen is moved to the external monitor external monitor desktop is black. kquitapp5 plasmashell and restart plasmashell can make it work again. EXPECTED RESULT Plasma have panel in the right place and show desktop correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.23.90 (available in About System) KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION relevant supportInformation in KWin Screens === Multi-Head: no Active screen follows mouse: yes Number of Screens: 2 Screen 0: - Name: eDP-1 Geometry: 0,0,1536x864 Scale: 1.25 Refresh Rate: 144028 Adaptive Sync: incapable Screen 1: - Name: DP-1 Geometry: 1536,0,2048x1152 Scale: 1.25 Refresh Rate: 59951 Adaptive Sync: incapable -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448790] 19c471405e7eb4b6026db24d776d205125dbc013 breaks the multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=448790 Weng Xuetian changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/e64f60ce086c ||f2983e44b2815922c9fdd73e5d2 ||b --- Comment #3 from Weng Xuetian --- Git commit e64f60ce086cf2983e44b2815922c9fdd73e5d2b by Weng Xuetian. Committed on 19/01/2022 at 23:46. Pushed by ngraham into branch 'master'. Fix force xrgb 19c471405e7eb4b6026db24d776d205125dbc013 introduced a regression if there are two gbm backend and the backend fail to choose drm format. This fix does two things: 1. Current buffer format should not be reset after create new buffer, otherwise current.format may just be empty after resetOutput. 2. force xrgb need to be set on the primary backend. M +7-1src/backends/drm/egl_gbm_backend.cpp M +2-0src/backends/drm/egl_gbm_backend.h https://invent.kde.org/plasma/kwin/commit/e64f60ce086cf2983e44b2815922c9fdd73e5d2b -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448790] 19c471405e7eb4b6026db24d776d205125dbc013 breaks the multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=448790
--- Comment #1 from Weng Xuetian ---
Full stack strace from crashed kwin_wayland.
#0 0x7f369801fd22 in raise () at /usr/lib/libc.so.6
#1 0x7f369800990e in abort () at /usr/lib/libc.so.6
#2 0x7f36987dbee4 in qt_assert(char const*, char const*, int) () at
/usr/lib/libQt5Core.so.5
#3 0x7f36987dbf44 in qt_assert_x(char const*, char const*, char const*,
int) () at /usr/lib/libQt5Core.so.5
#4 0x7f3691edf3d0 in
KWin::EglGbmBackend::beginFrame(KWin::AbstractOutput*) (this=0x55a25a5d59a0,
drmOutput=0x55a25a836ce0) at
/home/csslayer/Develop/kwin/src/backends/drm/egl_gbm_backend.cpp:524
#5 0x7f3691ee12f8 in
KWin::EglGbmBackend::renderTestFrame(KWin::DrmAbstractOutput*)
(this=0x55a25a5d59a0, output=0x55a25a836ce0) at
/home/csslayer/Develop/kwin/src/backends/drm/egl_gbm_backend.cpp:770
#6 0x7f3691ed4693 in KWin::DrmPipeline::checkTestBuffer()
(this=0x55a25a6891b0) at
/home/csslayer/Develop/kwin/src/backends/drm/drm_pipeline.cpp:323
#7 0x7f3691ed2dea in
KWin::DrmPipeline::commitPipelinesAtomic(QVector const&,
KWin::DrmPipeline::CommitMode, QVector const&)
(pipelines=..., mode=KWin::DrmPipeline::CommitMode::Test,
unusedObjects=...) at
/home/csslayer/Develop/kwin/src/backends/drm/drm_pipeline.cpp:131
#8 0x7f3691ed2ae9 in
KWin::DrmPipeline::commitPipelines(QVector const&,
KWin::DrmPipeline::CommitMode, QVector const&)
(pipelines=..., mode=KWin::DrmPipeline::CommitMode::Test,
unusedObjects=...) at
/home/csslayer/Develop/kwin/src/backends/drm/drm_pipeline.cpp:103
#9 0x7f3691ec1253 in KWin::DrmGpu::testPipelines() (this=0x55a25a532cd0)
at /home/csslayer/Develop/kwin/src/backends/drm/drm_gpu.cpp:427
#10 0x7f3691ec098a in
KWin::DrmGpu::checkCrtcAssignment(QVector,
QVector) (this=0x55a25a532cd0, connectors=..., crtcs=...)
at /home/csslayer/Develop/kwin/src/backends/drm/drm_gpu.cpp:338
#11 0x7f3691ec0c59 in
KWin::DrmGpu::checkCrtcAssignment(QVector,
QVector) (this=0x55a25a532cd0, connectors=..., crtcs=...)
at /home/csslayer/Develop/kwin/src/backends/drm/drm_gpu.cpp:365
#12 0x7f3691ec0daa in operator()() const (__closure=0x7ffdfc4e63d0) at
/home/csslayer/Develop/kwin/src/backends/drm/drm_gpu.cpp:398
#13 0x7f3691ec1031 in
KWin::DrmGpu::testPendingConfiguration(KWin::DrmGpu::TestMode)
(this=0x55a25a532cd0, mode=KWin::DrmGpu::TestMode::TestWithCrtcReallocation)
at /home/csslayer/Develop/kwin/src/backends/drm/drm_gpu.cpp:403
#14 0x7f3691e98113 in
KWin::DrmBackend::applyOutputChanges(KWin::WaylandOutputConfig const&)
(this=0x55a25a46b690, config=...) at
/home/csslayer/Develop/kwin/src/backends/drm/drm_backend.cpp:628
#15 0x7f369abca146 in
KWin::Platform::requestOutputsChange(KWaylandServer::OutputConfigurationV2Interface*)
(this=0x55a25a46b690, config=0x55a25b3c42e0) at
/home/csslayer/Develop/kwin/src/platform.cpp:133
#16 0x7f369acb2c16 in
operator()(KWaylandServer::OutputConfigurationV2Interface*) const
(__closure=0x55a25a4680e0, config=0x55a25b3c42e0) at
/home/csslayer/Develop/kwin/src/wayland_server.cpp:501
#17 0x7f369acb81e6 in QtPrivate::FunctorCall,
QtPrivate::List, void,
KWin::WaylandServer::init(KWin::WaylandServer::InitializationFlags)::
>::call(struct {...} &, void **) (f=..., arg=0x7ffdfc4e67b0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#18 0x7f369acb7c44 in
QtPrivate::Functor,
1>::call,
void>(struct {...} &, void *, void **) (f=..., arg=0x7ffdfc4e67b0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:256
#19 0x7f369acb710d in
QtPrivate::QFunctorSlotObject,
1, QtPrivate::List,
void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=1, this_=0x55a25a4680d0, r=0x55a25a3dfae0, a=0x7ffdfc4e67b0, ret=0x0)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:443
#20 0x7f36989f85d3 in () at /usr/lib/libQt5Core.so.5
#21 0x7f369a71d2e4 in
KWaylandServer::OutputManagementV2Interface::configurationChangeRequested(KWaylandServer::OutputConfigurationV2Interface*)
() at /usr/lib/libKWaylandServer.so.5
#22 0x7f369670fd4a in () at /usr/lib/libffi.so.8
#23 0x7f369670f267 in () at /usr/lib/libffi.so.8
#24 0x7f369791f323 in () at /usr/lib/libwayland-server.so.0
#25 0x7f369791a5cc in () at /usr/lib/libwayland-server.so.0
#26 0x7f369791d1ca in wl_event_loop_dispatch () at
/usr/lib/libwayland-server.so.0
#27 0x7f369a735b7b in KWaylandServer::Display::dispatchEvents() () at
/usr/lib/libKWaylandServer.so.5
#28 0x7f36989f85d3 in () at /usr/lib/libQt5Core.so.5
#29 0x7f36989fa294 in QSocketNotifier::activated(QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at
/usr/lib/libQt5Core.so.5
#30 0x7f36989fa3df in QSocketNotifier::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#31 0x7f36994811a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#32 0x7f36989c79ba in QCoreApplication::notifyInternal2(QObject*, QEv
[kwin] [Bug 448790] New: 19c471405e7eb4b6026db24d776d205125dbc013 breaks the multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=448790 Bug ID: 448790 Summary: 19c471405e7eb4b6026db24d776d205125dbc013 breaks the multi-monitor setup Product: kwin Version: git-stable-Plasma/5.24 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: wen...@gmail.com Target Milestone: --- SUMMARY With 19c471405e7eb4b6026db24d776d205125dbc013, my HDMI output though USB-C is not working. My laptop is with intel + nvidia. When trying to enabling systemsettings, it will crash kwin_wayland. STEPS TO REPRODUCE 1. Disable HDMI (there's no actual output to this screen, but it's "enabled" in systemsettings) 2. Reenable it OBSERVED RESULT kwin_wayland crashes EXPECTED RESULT Output should be on and no crash SOFTWARE/OS VERSIONS == Version === KWin version: 5.23.90 Qt Version: 5.15.2 Qt compile version: 5.15.2 XCB compile version: 1.14 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12101004 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Plugin recommends border size: None Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 5, 4, 3, 0 decorationButtonsRight: borderSize: 0 gridUnit: 12 font: Sans Serif,8,-1,5,50,0,0,0,0,0 smallSpacing: 3 largeSpacing: 12 Platform == Name: DRM Active: true Atomic Mode Setting on GPU 0: true Atomic Mode Setting on GPU 1: true Cursor == themeName: breeze_cursors themeSize: 24 Options === focusPolicy: 0 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: 6 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777250 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: true killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 1 glStrictBinding: false glStrictBindingFollowsDriver: true glPreferBufferSwap: 101 glPlatformInterface: 2 windowsBlockCompositing: true latencyPolicy: renderTimeEstimator: Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: yes Number of Screens: 2 Screen 0: - Name: eDP-1 Geometry: 0,0,1536x864 Scale: 1.25 Refresh Rate: 144028 Adaptive Sync: incapable Screen 1: - Name: DP-1 Geometry: 1536,0,2048x1152 Scale: 1.25 Refresh Rate: 59951 Adaptive Sync: incapable Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2) OpenGL version string: 4.6 (Core Profile) Mesa 21.3.4 OpenGL platform interface: EGL OpenGL shading language version string: 4.60 Driver: Intel GPU class: Coffee Lake OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 21.3.4 Linux kernel version: 5.16.1 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Loaded Effects: --- kwin4_effect_fullscreen kwin4_effect_dialogparent kwin4_effect_squash kwin4_effect_login kwin4_effect_maximize kwin4_effect_scale kwin4_effect_logout kwin4_effect_sessionquit kwin4_effect_morphingpopups kwin4_effect_windowaperture kwin4_effect_frozenapp zoom slidingpopups colorpicker desktopgrid slide screenshot
[kate] [Bug 443977] URGENT REGRESSION: unusable with non-english keyboard: adds space before every accented character
https://bugs.kde.org/show_bug.cgi?id=443977 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com --- Comment #29 from Weng Xuetian --- Created attachment 144901 --> https://bugs.kde.org/attachment.cgi?id=144901=edit ibus-setup workaround Just FYI, While we're working on a fix, you may workaround it by unchecking "embed preedit in application" in ibus-setup for now. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432158] Mouse "back" button don't act as 'Go back'
https://bugs.kde.org/show_bug.cgi?id=432158 Weng Xuetian changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/systemsettings/-/commit/ ||266f884fe9894cad1561bb2 ||dc0cc7674c067 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432158] Mouse "back" button don't act as 'Go back'
https://bugs.kde.org/show_bug.cgi?id=432158 Weng Xuetian changed: What|Removed |Added Version Fixed In||5.23.80 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432158] Mouse "back" button don't act as 'Go back'
https://bugs.kde.org/show_bug.cgi?id=432158 Weng Xuetian changed: What|Removed |Added Resolution|--- |FIXED CC||wen...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #1 from Weng Xuetian --- I think this is fixed by https://invent.kde.org/plasma/systemsettings/-/commit/266f884fe9894cad1561bb2dc0cc7674c067 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430266] No thumbnails for video files since 20.12.0
https://bugs.kde.org/show_bug.cgi?id=430266 --- Comment #31 from Weng Xuetian --- Thanks for the information. I installed leap 15.2 for testing. The issue is removing a call to API deprecated in ffmpeg 4, while the call is necessary for ffmpeg 3 used by 15.2's ffmpegthumbs. I restored the call when compiling ffmpegthumbs with ffmpeg 3. The fix should be picked by the next release 21.04.1. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430266] No thumbnails for video files since 20.12.0
https://bugs.kde.org/show_bug.cgi?id=430266 Weng Xuetian changed: What|Removed |Added Latest Commit||https://invent.kde.org/mult ||imedia/ffmpegthumbs/commit/ ||26c1d3b790d621f89cf1cbf56bd ||c0b8c97a95151 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #30 from Weng Xuetian --- Git commit 26c1d3b790d621f89cf1cbf56bdc0b8c97a95151 by Weng Xuetian. Committed on 25/04/2021 at 21:12. Pushed by xuetianweng into branch 'release/21.04'. Restore the compatiblity with ffmpeg 3. M +4-0ffmpegthumbnailer/moviedecoder.cpp https://invent.kde.org/multimedia/ffmpegthumbs/commit/26c1d3b790d621f89cf1cbf56bdc0b8c97a95151 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430266] No thumbnails for video files since 20.12.0
https://bugs.kde.org/show_bug.cgi?id=430266 --- Comment #23 from Weng Xuetian --- Since can be made to work on some system with given version, it is less likely to be a bug in the package but more likely to be either your system has some misconfiguration or packaging issue. Here's the things I suggest to be checked : 1. Check if dolphin has the video thumbnailer enabled 2. I'm not sure what's your repo setup, leap 15.2 doesn't have 20.12 so are you using mixed packages or additional 3rd party repo? you may want to check carefully if everything matches expectation, and also list all the relevant packages version installed on your system, including libx264, all relevant libav* packages and ffmpegthumbs. 3. While I think it's unlikely to get broken linkage on rpm based system, what is your output of ldd /usr/lib64/qt5/plugins/ffmpegthumbs.so does it show anything "not found"? When you run dolphin from the command line, does it give any error that seems related to "video" or "stream"? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430266] does not create thumbnail preview for mp4 movies
https://bugs.kde.org/show_bug.cgi?id=430266 Weng Xuetian changed: What|Removed |Added Resolution|UPSTREAM|DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430266] does not create thumbnail preview for mp4 movies
https://bugs.kde.org/show_bug.cgi?id=430266 Weng Xuetian changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||wen...@gmail.com Resolution|--- |UPSTREAM --- Comment #19 from Weng Xuetian --- I just checked this on Archlinux. The necessary package for me to get it working is ffmpegthumbs-21.04.0-1, and I also need to manually enable it in doplhin. After that it just works. Since the report is about opensuse and the only release provides 20.12 in opensuse is tumbleweed, so I just go ahead and try that in the VM and downloaded some random mp4 file. And here's what I found. The error reported in dolphin is "Could not find video stream", so indeed there some error happens. After further investigation, I installed ffmpeg command line to and try to decode mp4 file manually and ffmpeg gives me error for not having h264 decoder. So I think your problem is the ffmpeg build doesn't have relevant codec support. I browsed opensuse repo on pkgs.org and older version of opensuse (15.2) does have libx264 but it's removed in tumbleweed. I also tried ffmpeg in Packman repository which is built with libx264 support. After installing that, dolphin thumbnail just starts to work in opensuse tumbleweed. So I think it's just a packaging issue. I think libx264 is removed from opensuse due to patent, FYI: https://en.opensuse.org/SDB:Firefox_MP4/H.264_Video_Support -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436106] kwin does not handle xdg popup reposition resize
https://bugs.kde.org/show_bug.cgi?id=436106 Weng Xuetian changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/17a585b5d554 ||7810b3f467a20b0943a9be1a480 ||5 Resolution|--- |FIXED --- Comment #2 from Weng Xuetian --- Git commit 17a585b5d5547810b3f467a20b0943a9be1a4805 by Weng Xuetian. Committed on 23/04/2021 at 20:36. Pushed by xuetianweng into branch 'master'. Always apply size change from xdg_popup_reposition. M +1-4src/xdgshellclient.cpp https://invent.kde.org/plasma/kwin/commit/17a585b5d5547810b3f467a20b0943a9be1a4805 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436106] New: kwin does not handle xdg popup reposition resize
https://bugs.kde.org/show_bug.cgi?id=436106 Bug ID: 436106 Summary: kwin does not handle xdg popup reposition resize Product: kwin Version: 5.21.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: wen...@gmail.com Target Milestone: --- SUMMARY When receiving xdg_popup_reposition request, the resize is not handled and the popup is still using the old size. STEPS TO REPRODUCE 1. Using Gtk4 to show popup, try to resize the popup. OBSERVED RESULT popup is using the old size, but new popistion. EXPECTED RESULT popup is using the new size and new popistion. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422465] Add Fcitx support to Krita's AppImage
https://bugs.kde.org/show_bug.cgi?id=422465 Weng Xuetian changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #20 from Weng Xuetian --- Just tried to check krita-5.0.0-prealpha-db8a16f-x86_64.appimage, it is simply not include the required file. and newer one works ./krita-5.0.0-prealpha-b55fcd5-x86_64.appimage. Probably due to how the krita jenkins job works, krita-5.0.0-prealpha-db8a16f-x86_64.appimage might not pick up the latest artifact of Krita_Nightly_Appimage_Dependency_Build so it doesn't include fcitx plugin. Tyson@, Please just try a newer image and it should just works. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422465] Add Fcitx support to Krita's AppImage
https://bugs.kde.org/show_bug.cgi?id=422465 --- Comment #19 from Weng Xuetian --- IMHO at this point since it at least works for me, it's likely to be a configuration issue (input method may require set some env var so it can goes wrong) instead of packaging issue. So I'd suggest close as fixed. For Tyson's issue feel free to ping me on KDE China and I can help you to take a look. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422465] Add Fcitx support to Krita's AppImage
https://bugs.kde.org/show_bug.cgi?id=422465
--- Comment #18 from Weng Xuetian ---
(In reply to Tyson Tan from comment #13)
> I tested krita-5.0.0-prealpha-db8a16f-x86_64.appimage under Archlinux with
> fcitx5, I was unable to use fcitx5 in that appimage. We often can't choose
> which version of fcitx under Linux, it's either fcitx(4) OR fcitx5 for a
> certain distro. I wonder if we need to package both fcitx-qt5 and fcitx5-qt
> at the same time?
No, for compatibility, both im module support fcitx4 / 5.
Actually I just tested with
https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/krita-5.0.0-prealpha-b55fcd5-x86_64.appimage
Both fcitx4/5 works fine with this image on my system.
Did you set QT_IM_MODULE=fcitx ?
run it with QT_DEBUG_PLUGINS=1 should gives you
QFactoryLoader::QFactoryLoader() looking at
"/tmp/.mount_krita-43CzQH/usr/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so"
Found metadata in lib
/tmp/.mount_krita-43CzQH/usr/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so,
metadata=
{
"IID": "org.qt-project.Qt.QPlatformInputContextFactoryInterface.5.1",
"MetaData": {
"Keys": [
"fcitx"
]
},
"archreq": 0,
"className": "QFcitxPlatformInputContextPlugin",
"debug": false,
"version": 330752
}
Got keys from plugin meta data ("fcitx"
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 422465] Add Fcitx support to Krita's AppImage
https://bugs.kde.org/show_bug.cgi?id=422465
Weng Xuetian changed:
What|Removed |Added
CC||wen...@gmail.com
--- Comment #4 from Weng Xuetian ---
Actually, #1 is not pointing to the exact right repo.
To support fcitx(both 4 and 5), either https://github.com/fcitx/fcitx-qt5 or
https://github.com/fcitx/fcitx5-qt can be used.
And you do not need https://github.com/fcitx/fcitx{,5} to build it. There is an
cmake option that only build the plugin part without the library.
https://github.com/fcitx/fcitx-qt5/blob/77cb995a1ed0c30401e43388842b99610b53569e/CMakeLists.txt#L12
I don't think it will pull in any additional dependency that is not in Qt's
dependency (the only explicit ones are xkbcommon, which is also used by Qt)
--
You are receiving this mail because:
You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 435382] Add FCITX to improve CJK languages
https://bugs.kde.org/show_bug.cgi?id=435382 Weng Xuetian changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Weng Xuetian --- I'll close this for now since this is only related to flatpak runtime and give my help in the original report. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 435382] Add FCITX to improve CJK languages
https://bugs.kde.org/show_bug.cgi?id=435382 --- Comment #4 from Weng Xuetian --- I don't think there's anything that need to be done to kde flatpak runtime. There was a upstream flatpak breaking change that make fcitx 4.2.9.7 to be the minimum version to work with current kde's flatpak runtime. So as long as the host system is up to date it should just work. Fcitx im module is included in kde flatpak runtime long time ago. So there is nothing we could do there. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415420] cjk input of apt install and flatpak (appimage)
https://bugs.kde.org/show_bug.cgi?id=415420 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com --- Comment #8 from Weng Xuetian --- As a fcitx developer point of view, since this bug is report quit long time ago, it's not really clear if the system is too old that doesn't have up to date fcitx (>=4.2.9.7). There was a upstream flatpak break change that make fcitx 4.2.9.7 to be the minimum version to work with current kde's flatpak runtime. Fcitx im module is included in kde flatpak runtime long time ago. So there is nothing we could do there. I just checked on archlinux + kdenlive from flathub. Fcitx just works properly. As for AppImage, it should be a totally different story. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435000] Crashed when i opened konsole
https://bugs.kde.org/show_bug.cgi?id=435000 Weng Xuetian changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Weng Xuetian --- The crash is in a plugin library of kime (https://github.com/Riey/kime) Likely to be a bug in kime instead of plasma since no other input method has similar bug reported. Since it's SIGSEGV so it might be some missing null pointer check in the kime's im module. Please report the bug to them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433224] The mouse event has a region that does not work for a scaled xwayland window
https://bugs.kde.org/show_bug.cgi?id=433224 Weng Xuetian changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/d612d76e09ec ||5d8d26121d3e2dee17ef4867f5f ||7 --- Comment #8 from Weng Xuetian --- Git commit d612d76e09ec5d8d26121d3e2dee17ef4867f5f7 by Weng Xuetian. Committed on 19/03/2021 at 16:53. Pushed by xuetianweng into branch 'master'. Replace xdg output done with explicit wl_output done M +6-1src/abstract_wayland_output.cpp https://invent.kde.org/plasma/kwin/commit/d612d76e09ec5d8d26121d3e2dee17ef4867f5f7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433224] The mouse event has a region that does not work for a scaled xwayland window
https://bugs.kde.org/show_bug.cgi?id=433224 --- Comment #7 from Weng Xuetian --- Git commit e004156aba52fc025f491b11ac26b0e9f873803e by Weng Xuetian. Committed on 19/03/2021 at 17:39. Pushed by xuetianweng into branch 'master'. Add explicit done to OutputInterface and deprecate zxdg_output_v1.done if version 3 is used. In zxdg_output_v1 version 3, done is deprecated and should be replaced with wl_output.done. This makes automatically send done upon change not suitable for the usage. OutputInterface user should now use done() explicitly to send the update. M +7-0autotests/client/test_wayland_output.cpp M +1-0autotests/client/test_xdg_output.cpp M +7-4src/server/output_interface.cpp M +6-0src/server/output_interface.h M +19 -6src/server/xdgoutput_v1_interface.cpp M +1-1src/server/xdgoutput_v1_interface.h https://invent.kde.org/plasma/kwayland-server/commit/e004156aba52fc025f491b11ac26b0e9f873803e -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 433284] Shortcut for switching input method (Windows + Space) does not work when using kimpanel-ibus-panel
https://bugs.kde.org/show_bug.cgi?id=433284 --- Comment #11 from Weng Xuetian --- Can you try killall kimpanel-ibus-panel and run it from command line? Did you see any error like "Could not convert keyval=.. to keycode"? If so, could you provide the output of setxkbmap -print ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 345731] Input method should be able to commit multi line to application
https://bugs.kde.org/show_bug.cgi?id=345731 Weng Xuetian changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Weng Xuetian --- This doesn't seem to be a problem as for ktexteditor 5.79.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com --- Comment #56 from Weng Xuetian --- Just FYI some information. Basically kde's battery widget queries upower via dbus. Randomly I noticed that upower would simply freeze due to some underlying calls to libusbmuxd (something that likely to be used when you plug in ios device, e.g. iphone and ipad). So you might want to check if this is related to a freezing upower. (Make some dbus call to upower) For me I could confirm that all my "missing battery" issue is not related to KDE but upower freezing. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 433293] Some KDE processes (like kdeconnectd) are not killed after session logout, hog CPU
https://bugs.kde.org/show_bug.cgi?id=433293 --- Comment #19 from Weng Xuetian --- Sent https://codereview.qt-project.org/c/qt/qtwayland/+/338188 for trying approach 1 mentioned above. But I guess we should also try to see if this can be avoided within drkonqi code. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 433293] Some KDE processes (like kdeconnectd) are not killed after session logout, hog CPU
https://bugs.kde.org/show_bug.cgi?id=433293 --- Comment #18 from Weng Xuetian --- I'm on arch and I kinda aware of this issue for some time. 1. Qt would capture wayland error upon logout, and it triggers SIGABRT, because it will call qFatal(). 2. This SIGABRT would trigger drkonqi, but drkonqi would likely to freeze at this point because wayland compositor is quiting. 3. The "crashed" app would simply wait for drkonqi for the instruction. I also observed two different kind of drkonqi freeze a. it stucked in Qt wayland for querying some font settings, potentially a bug in Qt. When this happens, it will also hog the CPU. b. it stucked in KIdleTime's wayland plugin. In order to avoid this, following approaches may be tried 1. Fix Qt wayland by not triggering abort. While the wayland error is "fatal", it doesn't seems to be worth to use qFatal and leave some coredump, something like _exit might just work. At least we know that XIOError on X11 won't trigger qFatal. 2. don't install drkonqi (not so good resolution but an easy workaround for current user) 3. Fix drkonqi to make it not do anything related to GUI upon logout. I noticed that drkonqi has code that monitoring ksmserver, but apparently it doesn't work in this wayland logout case. 4. Fix kidletime's wayland plugin and fix qt wayland for the freeze issue. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 433284] Shortcut for switching input method (Windows + Space) does not work when using kimpanel-ibus-panel
https://bugs.kde.org/show_bug.cgi?id=433284 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com Assignee|plasma-b...@kde.org |wen...@gmail.com --- Comment #9 from Weng Xuetian --- I can't reproduce your issue under X11. I wonder if there's any other keygrab happens that prevent this from working Could you try to set another key in ibus-setup to see if it works? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 433293] Some KDE processes (like kdeconnectd) are not killed after session logout, hog CPU
https://bugs.kde.org/show_bug.cgi?id=433293 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com --- Comment #9 from Weng Xuetian --- While it is totally legit to "exit" on wayland compositor exits for Qt application, for X11 error X11 client just exits instead of "abort" (signal 6). signal 6 triggers drkonqi, but actually the problem is drkonqi is also stucked due to compositor is gone... I wonder if drkonqi could handle this more kindly.. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433224] The mouse event has a region that does not work for a scaled xwayland window
https://bugs.kde.org/show_bug.cgi?id=433224 Weng Xuetian changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UPSTREAM|--- Ever confirmed|0 |1 --- Comment #4 from Weng Xuetian --- So here's my observation: Xwayland always received the "old size request", instead of the latest one. when set 150% -> xrandr output is still the last value. This is done by check kwin log and the xrandr output under wayland. Also I didn't notice that gnome-shell has the same problem. So I wonder if kwin is missing some kind "flush" operation in the implemenation. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 415236] Translation problem in KCacheGrind that brokes KDE File Dialog
https://bugs.kde.org/show_bug.cgi?id=415236 Weng Xuetian changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 358054] konsole: Ctrl+Shift+F, input the string I want to search, the chinese translation of search up and down button is wrong
https://bugs.kde.org/show_bug.cgi?id=358054 Weng Xuetian changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Weng Xuetian --- I don't think the translation is wrong. The original string is "reversed". I because I think the console output is newer in the below, so the search goes backward (up). That's why "up" is next. If you think it's confusing please report to konsole. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 403169] "Desktop Theme," is prepended to the localized string for zh_CN
https://bugs.kde.org/show_bug.cgi?id=403169 Weng Xuetian changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433224] The mouse event has a region that does not work for a scaled xwayland window
https://bugs.kde.org/show_bug.cgi?id=433224 --- Comment #1 from Weng Xuetian --- This seems only happen when change the scale back and forth. It works after a clean login. I changed to 150% first, then back to 125% and noticed this issue. Looks like there's some inconsistency state with in the kwin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433224] New: The mouse event has a region that does not work for a scaled xwayland window
https://bugs.kde.org/show_bug.cgi?id=433224 Bug ID: 433224 Summary: The mouse event has a region that does not work for a scaled xwayland window Product: kwin Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: wen...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. set scale to 125% 2. open xev, enlarge the window to be the same size as the screen. 3. try to select some text from xterm OBSERVED RESULT If you move the mouse to the right edge, you will notice that from a certain point, the mouse X coordinate doesn't go further right and stop there, while the mouse cursor can still be more "right" to the event. For example, on my screen (1920x1080), the maximum X of the mouse event reported by xev is 1279, no matter how much you move mouse beyond that point, the x is still 1279. On the scaled screen, it should be able to reach as much as 1536 (1920 / 1.25). EXPECTED RESULT The mouse event can correctly move with in the window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21 KDE Frameworks Version: 5.79 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433131] New: The tabbox on wayland doesn't blur
https://bugs.kde.org/show_bug.cgi?id=433131 Bug ID: 433131 Summary: The tabbox on wayland doesn't blur Product: kwin Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-tabbox Assignee: kwin-bugs-n...@kde.org Reporter: wen...@gmail.com Target Milestone: --- SUMMARY Tabbox on wayland doesn't have blur in the background STEPS TO REPRODUCE 1. Start wayland 2. Alt+tab (with default setup) OBSERVED RESULT Blur the tabbox EXPECTED RESULT Tabbox has blurred background. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE 5.21 (available in About System) KDE Plasma Version: 5.21 KDE Frameworks Version: 5.79 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431365] "WINDOW DECORATIONS RELOADED" shouldn't be written to stdout
https://bugs.kde.org/show_bug.cgi?id=431365 Weng Xuetian changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.21 Status|ASSIGNED|RESOLVED CC||wen...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 430388] Custom Shortcuts cannot record key presses
https://bugs.kde.org/show_bug.cgi?id=430388 Weng Xuetian changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kxmlgui/commit/1bd9a ||c05b0eed3582937829150b31ea4 ||8fd95bb0 --- Comment #23 from Weng Xuetian --- Git commit 1bd9ac05b0eed3582937829150b31ea48fd95bb0 by Xuetian Weng, on behalf of Weng Xuetian. Committed on 22/12/2020 at 05:19. Pushed by xuetianweng into branch 'master'. Fix key recording by setWindow before capture starts. It is common that during the construction of widget, it is not yet added to a window. Thus windowHandle will simply return null in this case. Always set the window to before the capture starts. M +1-0src/kkeysequencewidget.cpp https://invent.kde.org/frameworks/kxmlgui/commit/1bd9ac05b0eed3582937829150b31ea48fd95bb0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 430062] New key-held options need to default to repeat for backward compatibility
https://bugs.kde.org/show_bug.cgi?id=430062 --- Comment #10 from Weng Xuetian --- Git commit 6b7040f3ea2e02c7ca805278fe7fe06ff31b0ec7 by Xuetian Weng, on behalf of Weng Xuetian. Committed on 19/12/2020 at 18:11. Pushed by xuetianweng into branch 'master'. Hide accent option if it is not supported M +14 -1kcms/keyboard/kcmmisc.cpp M +38 -25 kcms/keyboard/kcmmiscwidget.ui https://invent.kde.org/plasma/plasma-desktop/commit/6b7040f3ea2e02c7ca805278fe7fe06ff31b0ec7 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430492] Application use konsolepart crashes on exist due to double free
https://bugs.kde.org/show_bug.cgi?id=430492 Weng Xuetian changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/util ||ities/konsole/commit/348051 ||4e706cb2d71014197fd61456fb1 ||9ab9329 --- Comment #3 from Weng Xuetian --- Git commit 3480514e706cb2d71014197fd61456fb19ab9329 by Weng Xuetian. Committed on 18/12/2020 at 17:24. Pushed by tcanabrava into branch 'master'. Only link konsoleprofile to konsoleprivate Using Object multiple times may cause the destructor handler called multiple times and leads to double free crash on exit. M +0-2src/CMakeLists.txt M +3-1src/profile/ProfileModel.h https://invent.kde.org/utilities/konsole/commit/3480514e706cb2d71014197fd61456fb19ab9329 -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 430062] New key-held options need to default to repeat for backward compatibility
https://bugs.kde.org/show_bug.cgi?id=430062 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com --- Comment #7 from Weng Xuetian --- So your behavior, if on X11, is probably due to this bug (I don't know how that config is applied on wayland, probably kwin is involved.): https://bugs.kde.org/show_bug.cgi?id=418175 The bug is when you apply rate config from kcm, it doesn't read the new value, which I just fixed. Also, the accent option, would rely on QT_IM_MODULE set to plasmaim, which probably doesn't set on your desktop. Due to the fact that it may break normal input method usage, it won't gonna be set by default or being override by your desktop setings. And right now when it is not set to plasmaim, accent and repeat will basically have the same behavior. I'll probably send patch to hide the key-held if QT_IM_MODULE is not plasmaim. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418175] Keyboard repeat delay not applied immediately when clicking "Apply", needs logout/login
https://bugs.kde.org/show_bug.cgi?id=418175 Weng Xuetian changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/27 ||a64b96f224b510234c76c22bcc6 ||407a86ea4b8 Version Fixed In||5.21 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Weng Xuetian --- Git commit 27a64b96f224b510234c76c22bcc6407a86ea4b8 by Weng Xuetian. Committed on 18/12/2020 at 06:08. Pushed by xuetianweng into branch 'master'. Reparse the key repeat rate config when we try to load it. Right now due to the fact that it is a shared config, we may load the old value from memory. FIXED-IN: 5.21 M +4-1kcms/keyboard/keyboard_hardware.cpp https://invent.kde.org/plasma/plasma-desktop/commit/27a64b96f224b510234c76c22bcc6407a86ea4b8 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 430388] Custom Shortcuts cannot record key presses
https://bugs.kde.org/show_bug.cgi?id=430388 Weng Xuetian changed: What|Removed |Added Product|systemsettings |frameworks-kxmlgui Assignee|k...@michael-jansen.biz |kdelibs-b...@kde.org Component|kcm_khotkeys|general Version|5.20.4 |5.77.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430388] Custom Shortcuts cannot record key presses
https://bugs.kde.org/show_bug.cgi?id=430388 Weng Xuetian changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #16 from Weng Xuetian --- (In reply to Nate Graham from comment #5) > No, the sources of the problem are different. This KCM has a totally custom > implementation, while KMenuEdit and the Shortcuts KCM use KGlobalAccel > > Please file a new bug for your issues with the kglobalaccel-based issue seen > in KMenuEdit and the Shortcuts page, which doesn't have anything to do with > this bug report. :) But looks like "kcmshell5 khotkeys" would also produced the same error. Looking closer, I think the bug is in kxmlgui, when it is ported to KeySequenceRecorder. I think the issue is when it is constructed, the widget may not yet added to a window. So pass the window to KeySequenceRecorder in constructor doesn't work. Sent a merge request to fix this. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430492] Application use konsolepart crashes on exist due to double free
https://bugs.kde.org/show_bug.cgi?id=430492 --- Comment #1 from Weng Xuetian --- I read the git log a little bit, likely to be caused by change in 9d8e47298c81fc1e47c998eda1b6e980589274eb . -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430492] New: Application use konsolepart crashes on exist due to double free
https://bugs.kde.org/show_bug.cgi?id=430492 Bug ID: 430492 Summary: Application use konsolepart crashes on exist due to double free Product: konsole Version: 20.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kpart Assignee: konsole-de...@kde.org Reporter: wen...@gmail.com Target Milestone: --- SUMMARY konsole crashes on exit, possiblly due the destruction of static data. Related output from valgrind: ==191447== Invalid free() / delete / delete[] / realloc() ==191447==at 0x483B9AB: free (vg_replace_malloc.c:538) ==191447==by 0x4A8FDFB: QHashData::free_helper(void (*)(QHashData::Node*)) (in /usr/lib/libQt5Core.so.5.15.2) ==191447==by 0x4F1C3AD: __cxa_finalize (in /usr/lib/libc-2.32.so) ==191447==by 0x50FB877: ??? (in /usr/lib/libkonsoleprivate.so.20.12.0) ==191447==by 0x401168A: _dl_fini (in /usr/lib/ld-2.32.so) ==191447==by 0x4F1BDB6: __run_exit_handlers (in /usr/lib/libc-2.32.so) ==191447==by 0x4F1BF5D: exit (in /usr/lib/libc-2.32.so) ==191447==by 0x4F04158: (below main) (in /usr/lib/libc-2.32.so) ==191447== Address 0xbdba380 is 0 bytes inside a block of size 42 free'd ==191447==at 0x483B9AB: free (vg_replace_malloc.c:538) ==191447==by 0x4A8FDFB: QHashData::free_helper(void (*)(QHashData::Node*)) (in /usr/lib/libQt5Core.so.5.15.2) ==191447==by 0x4F1C3AD: __cxa_finalize (in /usr/lib/libc-2.32.so) ==191447==by 0x48B01D7: ??? (in /usr/lib/libkdeinit5_konsole.so) ==191447==by 0x401168A: _dl_fini (in /usr/lib/ld-2.32.so) ==191447==by 0x4F1BDB6: __run_exit_handlers (in /usr/lib/libc-2.32.so) ==191447==by 0x4F1BF5D: exit (in /usr/lib/libc-2.32.so) ==191447==by 0x4F04158: (below main) (in /usr/lib/libc-2.32.so) ==191447== Block was alloc'd at ==191447==at 0x483A77F: malloc (vg_replace_malloc.c:307) ==191447==by 0x4A60912: QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) (in /usr/lib/libQt5Core.so.5.15.2) ==191447==by 0x4AD7494: QString::reallocData(unsigned int, bool) (in /usr/lib/libQt5Core.so.5.15.2) ==191447==by 0x4AD82B4: ??? (in /usr/lib/libQt5Core.so.5.15.2) ==191447==by 0x4AD8633: ??? (in /usr/lib/libQt5Core.so.5.15.2) ==191447==by 0x4ADBC9F: QString::toLower_helper(QString const&) (in /usr/lib/libQt5Core.so.5.15.2) ==191447==by 0x48CCB9A: Konsole::Profile::registerProperty(Konsole::Profile::PropertyInfo const&) (in /usr/lib/libkdeinit5_konsole.so) ==191447==by 0x48CCD54: Konsole::Profile::fillTableWithDefaultNames() (in /usr/lib/libkdeinit5_konsole.so) ==191447==by 0x48CCD95: Konsole::Profile::lookupByName(QString const&) (in /usr/lib/libkdeinit5_konsole.so) ==191447==by 0x48CD3A7: Konsole::ProfileCommandParser::parse(QString const&) (in /usr/lib/libkdeinit5_konsole.so) ==191447==by 0x5199FD7: Konsole::SessionManager::sessionProfileCommandReceived(QString const&) (in /usr/lib/libkonsoleprivate.so.20.12.0) ==191447==by 0x4C73DD5: ??? (in /usr/lib/libQt5Core.so.5.15.2) STEPS TO REPRODUCE 1. launch konsole 2. do something in 3. quit konsole OBSERVED RESULT konsole crashes with backtrace like QHashData::free_helper(void (*)(QHashData::Node*)) (in /usr/lib/libQt5Core.so.5.15.2) __cxa_finalize (in /usr/lib/libc-2.32.so) EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archliinux (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430388] Custom Shortcuts cannot record key presses
https://bugs.kde.org/show_bug.cgi?id=430388 Weng Xuetian changed: What|Removed |Added Component|kcm_keys|kcm_khotkeys CC||wen...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #22 from Weng Xuetian --- I added the fix in PR for query parser. So I think it's now ready to test: You'll need to purge the old data to trigger the new code. Right now I'm able to search Chinese content/file name quite easily. E.g. $ baloosearch 恋爱 /home/csslayer/Downloads/Telegram Desktop/恋爱循环歌词-中文+罗马音+日文.odt /home/csslayer/Downloads/Telegram Desktop/恋爱循环歌词-中文+罗马音+日文.doc -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #21 from Weng Xuetian --- Emm, other than the place in the PR, looks like there's another place need to be fixed: Baloo::QueryParser::parseQuery. Similar algorithm is applied but it has some extra code for handling the quote. Current implementation will not generate any term on the Chinese or Japanese Characters which also leads to empty result. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com --- Comment #20 from Weng Xuetian --- I created a PR at https://invent.kde.org/frameworks/baloo/-/merge_requests/11 by using ICU, would you mind to give it a test? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423525] New: Window is displayed above lock screen when show desktop effect is active
https://bugs.kde.org/show_bug.cgi?id=423525 Bug ID: 423525 Summary: Window is displayed above lock screen when show desktop effect is active Product: kwin Version: 5.19.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: wen...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Super+D to trigger show desktop 2. Super+L or timeout to trigger lock screen. OBSERVED RESULT Window is visible at the corner of the screen. EXPECTED RESULT No window should be displayed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.19.2 (available in About System) KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71 Qt Version: 5.15 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #18 from Weng Xuetian --- Created attachment 129164 --> https://bugs.kde.org/attachment.cgi?id=129164=edit KWin support info when running egl stream And actually only the graphics freezes. Things like keyboard input doesn't seem to have a problem. I tried to blindly use krunner to start kwrite via keyboard and kwrite does start. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com --- Comment #17 from Weng Xuetian --- I'm running archlinux with a intel+nvidia system and with KWIN_DRM_USE_EGL_STREAMS=1 I will also get a cursor in the middle of black screen. Without KWIN_DRM_USE_EGL_STREAMS being set, I can log into the wayland session without any problem (not so sure what's using). gdb attach to kwin doesn't seems to have a deadlock or sth. My Qt was already 5.15.0 and Plasma just updated to 5.19.0. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 420397] New: StrongSwan does not load password, nor be able to changed saved password
https://bugs.kde.org/show_bug.cgi?id=420397 Bug ID: 420397 Summary: StrongSwan does not load password, nor be able to changed saved password Product: plasma-nm Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: wen...@gmail.com Target Milestone: --- SUMMARY The password box is useless in editor, it does not save the password. When during the first connection, a password dialog show up, and no matter what, it will save the password in nm's config file instead of kwallet. And it is not possible to change the password. STEPS TO REPRODUCE 1. create strongswan connection 2. select password as auth method 3. connect 4. password dialog show up, fill a wrong password. 5. reconnect, OBSERVED RESULT password not show up again, always use the wrong password. EXPECTED RESULT at least password should be able to be updated in settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69 Qt Version: 5.14 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com --- Comment #43 from Weng Xuetian --- Just FYI, I tried to root cause the issue. There are some underlying dbus issue in krita that blocks things to be processed. I doubt there could be some deadlock. I tried to make fcitx im module to use its own dbus connection and seems that will solve the problem. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 403168] "System Settings, " is prepended to the localized string for zh_CN
https://bugs.kde.org/show_bug.cgi?id=403168 Weng Xuetian changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://websvn.kde.org/?vie ||w=revision=1533979 Status|REPORTED|RESOLVED --- Comment #1 from Weng Xuetian --- Should be fixed in svn already. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 387153] libinput-backend touchpad KCM only used on Wayland
https://bugs.kde.org/show_bug.cgi?id=387153 --- Comment #5 from Weng Xuetian <wen...@gmail.com> --- (In reply to Nate Graham from comment #4) > The old XInput-based touchpad KCM does indeed *sort of* work with > libinput-on-xorg, but 90% of the UI is grayed out, since those options > aren't supported on libinput. *Everything* on the Sensitivity tab is > disabled! And libinput-specific settings aren't exposed (e.g. left handed > mode, click method). > > The result is a poor user experience. It seems like it might be possible to > fix those problems, but why bother when we already have a better > libinput-specific UI that's used on Wayland? When libinput is being used on > X11, couldn't we show the nice UI but use the XInput backend? Emm, the problem is, xinput may use different driver at the same time so I assume it's not an easy issue to resolve. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 387153] libinput-backend touchpad KCM only used on Wayland
https://bugs.kde.org/show_bug.cgi?id=387153
Weng Xuetian <wen...@gmail.com> changed:
What|Removed |Added
CC||wen...@gmail.com
--- Comment #3 from Weng Xuetian <wen...@gmail.com> ---
Is it really a bug?
On X11, even if you're using libinput driver, libinput is configured via
XInput.
Even it's all "libinput" they will need to use different code path. You can
configure touchpad with old UI for libinput X11 driver.
On the new UI side, I assume that the new UI is only designed for libinput
because it don't want to carry the burden from X11 (on X11 we support synaptics
and libinput), so it's only used on wayland.
FYI X11+Libinput: kcms/touchpad/src/backends/x11/libinputtouchpad.{h,cpp}
--
You are receiving this mail because:
You are watching all bug changes.
[wacomtablet] [Bug 338453] Hide the wacom plasmoid if no tablet is connected.
https://bugs.kde.org/show_bug.cgi?id=338453 Weng Xuetian <wen...@gmail.com> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Weng Xuetian <wen...@gmail.com> --- (In reply to Valeriy Malov from comment #1) > This has been implemented in KF5 port of the plasmoid, right? It seems to > autohide when I disconnect my tablet. Yeah.. and probably it's implemented by me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386043] Switch window between same application sometimes does not work.
https://bugs.kde.org/show_bug.cgi?id=386043 --- Comment #5 from Weng Xuetian <wen...@gmail.com> --- (In reply to Martin Flöser from comment #1) > Please provide output of xprop for all dolphin windows. I checked the code change a little bit. I assume the problem is introduced by 5d9027b110. It seems that belongToSameApplication is focusing on the "same instance", dolphin at least would fail on the pid check. At least I'd expect the alt + ` works like the task manager's grouping. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386043] Switch window between same application sometimes does not work.
https://bugs.kde.org/show_bug.cgi?id=386043 --- Comment #4 from Weng Xuetian <wen...@gmail.com> --- Created attachment 108518 --> https://bugs.kde.org/attachment.cgi?id=108518=edit Another dolphin window xprop -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386043] Switch window between same application sometimes does not work.
https://bugs.kde.org/show_bug.cgi?id=386043 --- Comment #3 from Weng Xuetian <wen...@gmail.com> --- Created attachment 108517 --> https://bugs.kde.org/attachment.cgi?id=108517=edit Dolphin window xprop -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386043] New: Switch window between same application sometimes does not work.
https://bugs.kde.org/show_bug.cgi?id=386043 Bug ID: 386043 Summary: Switch window between same application sometimes does not work. Product: kwin Version: 5.11.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: wen...@gmail.com Target Milestone: --- To reproduce: 1. Open multiple dolphin window 2. Alt + ` 3. only current dolphin is displayed. Currently I noticed that kdevelop, konsole, dolphin doesn't not work with Alt+`. While kwrite or firefox works. AFAIK, everything works in Plasma 5.10.x. -- You are receiving this mail because: You are watching all bug changes.
