On Tue, Mar 2, 2021 at 3:26 AM Andreas Henriksson wrote:
>
> Hello Shengjing Zhu,
>
> (FYI I've not been part of pkg-gnome maintenance for the better part of
> bullseye development cycle and don't speak for pkg-gnome team, but I
> feel this is not a new issue and hopefully my input can hopefully
On Tue, Mar 2, 2021 at 3:26 AM Andreas Henriksson wrote:
>
> Hello Shengjing Zhu,
>
> (FYI I've not been part of pkg-gnome maintenance for the better part of
> bullseye development cycle and don't speak for pkg-gnome team, but I
> feel this is not a new issue and hopefully my input can hopefully
Hello Shengjing Zhu,
(FYI I've not been part of pkg-gnome maintenance for the better part of
bullseye development cycle and don't speak for pkg-gnome team, but I
feel this is not a new issue and hopefully my input can hopefully help
shed some light on the situation at hand...)
First let me be
Control: severity -1 serious
Control: affects -1 src:tasksel
On Thu, Oct 03, 2019 at 05:49:37AM -0400, Jeremy Bicha wrote:
> On Wed, Oct 2, 2019 at 9:51 PM Mo Zhou wrote:
> > I've been using fcitx as the default Chinese input method for decades.
> > Recommending ibus simply breaks everything for
On Wed, Oct 2, 2019 at 9:51 PM Mo Zhou wrote:
> I've been using fcitx as the default Chinese input method for decades.
> Recommending ibus simply breaks everything for me.
GNOME Shell uses Wayland by default. It is my understanding that ibus
works in GNOME's Wayland session but fcitx does not.
Package: gnome-shell
Version: 3.34.0-2
Severity: important
I've been using fcitx as the default Chinese input method for decades.
Recommending ibus simply breaks everything for me.
Oct 03 01:23:57 Macadamia fcitx.desktop[2905]: (ERROR-10874 ime.c:432)
fcitx-keyboard-in-kan-kagapa already exists
6 matches
Mail list logo
