https://bugs.kde.org/show_bug.cgi?id=457149
Weng Xuetian <wen...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #3 from Weng Xuetian <wen...@gmail.com> ---
(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.
