[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
https://bugs.kde.org/show_bug.cgi?id=409644 --- Comment #12 from Yiyang Wu --- Confirm that this issue still exists on my Debian 12 Plasma-5.27 laptop. Is there any progress these days? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
https://bugs.kde.org/show_bug.cgi?id=409644 Yiyang Wu changed: What|Removed |Added CC||xgreenlandfor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468180] Plasmashell crashed in QQuickTransition::prepare() after closing a notification
https://bugs.kde.org/show_bug.cgi?id=468180 --- Comment #2 from Yiyang Wu --- Created attachment 159624 --> https://bugs.kde.org/attachment.cgi?id=159624&action=edit New crash information added by DrKonqi plasmashell (5.27.5) using Qt 5.15.8 I was switching windows and plasmashell crashes. The backtrace looks similar with bug 465706. -- Backtrace (Reduced): #5 0x7faefd277c86 in QtQml::qmlExecuteDeferred(QObject*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7faefd749059 in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7faefd73e997 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7faefbadd50d in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7faefc962fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468180] Plasmashell crashed in QQuickTransition::prepare() after closing a notification
https://bugs.kde.org/show_bug.cgi?id=468180 Yiyang Wu changed: What|Removed |Added CC||xgreenlandfor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466810] text-input-v1 not working with fcitx5 on chromium
https://bugs.kde.org/show_bug.cgi?id=466810 Yiyang Wu changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466810] text-input-v1 not working with fcitx5 on chromium
https://bugs.kde.org/show_bug.cgi?id=466810 --- Comment #3 from Yiyang Wu --- (In reply to Fushan Wen from comment #2) > Have you selected fcitx5 in virtual keyboard KCM? No. And after I enabled it this issue is resolved. Thanks! > Also `export $(dbus-launch); startplasma-wayland` on tty is not a supported > way to use > fcitx5 on Wayland because an Arch user also reported the same bug. For me it seems not having any impact using `export $(dbus-launch); startplasma-wayland` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466810] text-input-v1 not working with fcitx5 on chromium
https://bugs.kde.org/show_bug.cgi?id=466810 --- Comment #1 from Yiyang Wu --- Created attachment 156986 --> https://bugs.kde.org/attachment.cgi?id=156986&action=edit (weston) logs running chromium with `WAYLAND_DEBUG=1` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466810] New: text-input-v1 not working with fcitx5 on chromium
https://bugs.kde.org/show_bug.cgi?id=466810 Bug ID: 466810 Summary: text-input-v1 not working with fcitx5 on chromium Classification: Plasma Product: kwin Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: xgreenlandfor...@gmail.com Target Milestone: --- Created attachment 156985 --> https://bugs.kde.org/attachment.cgi?id=156985&action=edit logs running chromium with `WAYLAND_DEBUG=1` Even with text-input-v1 implemented on kwin (https://invent.kde.org/plasma/kwin/-/merge_requests/3403), `chromium --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime` still cannot use fcitx5 to input Chinese (no input box popup). This bug is observed on Debian sid, and there's no sign of debian packaging turning off text-input-v1 feature. Using weston `chromium --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime` works without issue, so the bug shouldn't be on fcitx5/chromium package. STEPS TO REPRODUCE 1. Install plasma-desktop, kwin_wayland, plasma-workspace-wayland on debian sid 2. `export $(dbus-launch); startplasma-wayland` on tty 3. Start up fcitx5 4. `chromium --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime` 5. Switch to Chinese input method and type SOFTWARE/OS VERSIONS Linux/KDE Plasma KDE Plasma Version: Debian 5.27.2-1 KDE Frameworks Version: Debian 5.103.0-1 Qt Version: Debian 5.15.8+dfsg-3 The attachment are logs running chromium with `WAYLAND_DEBUG=1`, then choose the text_input_v1 related information `grep text_input_v1`; for better diff comparison, timestamps and some numbers are changed to be the same. It can be seen that weston has more output, generating desired Chinese characters, while on plasma, it only detects the keyboard action, but not generating input box, thus cannot type Chinese characters. -- You are receiving this mail because: You are watching all bug changes.
