[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#956538: marked as done (kde-config-fcitx5: cannot connect to fcitx via dbus error message)

Your message dated Mon, 13 Apr 2020 06:48:35 +0900
with message-id <20200412214835.GA15373@burischnitzel.preining.info>
and subject line Re: Bug#956538: kde-config-fcitx5: cannot connect to fcitx via dbus error message
has caused the Debian Bug report #956538,
regarding kde-config-fcitx5: cannot connect to fcitx via dbus error message
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
956538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956538
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kde-config-fcitx5
Version: 0.0~git20200403.8afa921-1
Severity: grave
Justification: renders package unusable

Dear all,

I am trying to configure fcitx via the plasma/kde panel, but it gave me
an error
	Cannot connect to Fcitx by DBus, is Fcitx running?
Then I tried to start it directly via
	fcitx5-config-qt
with the same result.

But fcitx is running, I checked the addons and the dbus interface is
activated, so I am a bit surprised what is going on?

Any suggestion how to get this working?

Thanks a lot for your work on fcitx!!!

Norbert



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.3 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kde-config-fcitx5 depends on:
ii  libc6                 2.30-4
ii  libfcitx5-qt1         0.0~git20200404.366aed5-1
ii  libfcitx5utils1       0.0~git20200409.6409547-1
ii  libkf5configwidgets5  5.69.0-0.1
ii  libkf5coreaddons5     5.69.0-0.1
ii  libkf5i18n5           5.69.0-0.1
ii  libkf5itemviews5      5.69.0-0.1
ii  libkf5widgetsaddons5  5.69.0-0.1
ii  libqt5core5a          5.12.5+dfsg-9
ii  libqt5dbus5           5.12.5+dfsg-9
ii  libqt5gui5            5.12.5+dfsg-9
ii  libqt5widgets5        5.12.5+dfsg-9
ii  libqt5x11extras5      5.12.5-1
ii  libstdc++6            10-20200410-1
ii  libx11-6              2:1.6.9-2
ii  libxkbfile1           1:1.1.0-1

kde-config-fcitx5 recommends no packages.

kde-config-fcitx5 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sun, 12 Apr 2020, Boyuan Yang wrote:
> Are you using fcitx or fcitx5? They are completely different packages and
> should not be mixed together.

Ah .. uhmm ... sorry for the noise. Yes, with the correct version it
works. Closing this bug.

BTW, is fcitx5 prime for working with it? I am a happy user of fcitx
since years (and was burned by ibus many times), and I'm happy doing
some testing with fcitx5.

Best

Norbert

--
PREINING Norbert                              https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

--- End Message ---
Reply to: