- Edited
Installing "fcitx" and "fcitx-mozc" on a fresh, up-to-date XFCE install, most applications give an "Input/Output Error" upon launch attempt and the xfce4-panel bugs out.
Attempting to launch applications via (u)xterm gives the following:
If you already have an instance running (tested with Firefox, xfce4-terminal), the error doesn't occur when you launch additional instances. It only occurs when you want to launch a first instance.
However, Parole launches normally via (u)xterm.
This error happens immediately upon installation (without launching fcitx), and disappears (all goes back to normal) upon removing both packages.
Installing fcitx alone for the first time doesn't cause any errors (to the best of my testing). Following up with fcitx-mozc immediately causes it. No reboot required.
However, you can't remove only fcitx-mozc, you need to remove fcitx too to get the system working again. No reboot required.
If you reinstall only fcitx after removing it, that package alone is enough to cause the errors again, without rebooting.
Here is a different error message with gparted:
However, a reboot worked.
Running 66-intree as both user and root, before and after reinstalling fcitx, showed no difference.
Is anyone else able to replicate it, and is able to figure out why having these 2 packages alone messes with D-Bus?
Extra details below - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I have been using my system for months without issue, updating it on a weekly basis.
My last working update was on February 26. Upon updating on March 5, the above error manifested.
Librewolf, Tor Browser, mpv, Viewnior, Deadbeef, Lutris, and PulseEffects failed to launch as well.
Krita and JDownloader still works though. (They don't rely on D-Bus or something?)
fcitx and fcitx-mozc were not updated on March 5, so some other package update must have have caused the sudden issue.
I didn't realize it was an issue from fcitx and fcitx-mozc back then.
To make matters worst, Timeshift CLI couldn't restore my system too.
Since I had to urgently get my computer working for the weekday. it was reformatted.
Reconfiguring my fresh system led me to the above discovery.
Attempting to launch applications via (u)xterm gives the following:
% thunar
dbus[6273]: D-Bus library appears to be incorrectly set up: see the manual page for dbus-uuidgen to correct this issue. (Failed to open "/var/lib/dbus/machine-id": No such file or directory; Failed to open "/etc/machine-id": No such file or directory)
D-Bus not built with -rdynamic so unable to print a backtrace
zsh: IOT instruction thunar
If you already have an instance running (tested with Firefox, xfce4-terminal), the error doesn't occur when you launch additional instances. It only occurs when you want to launch a first instance.
However, Parole launches normally via (u)xterm.
This error happens immediately upon installation (without launching fcitx), and disappears (all goes back to normal) upon removing both packages.
Installing fcitx alone for the first time doesn't cause any errors (to the best of my testing). Following up with fcitx-mozc immediately causes it. No reboot required.
However, you can't remove only fcitx-mozc, you need to remove fcitx too to get the system working again. No reboot required.
If you reinstall only fcitx after removing it, that package alone is enough to cause the errors again, without rebooting.
Here is a different error message with gparted:
% gparted
Error executing command as another user: No authentication agent found.
However, a reboot worked.
Running 66-intree as both user and root, before and after reinstalling fcitx, showed no difference.
Is anyone else able to replicate it, and is able to figure out why having these 2 packages alone messes with D-Bus?
Extra details below - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I have been using my system for months without issue, updating it on a weekly basis.
My last working update was on February 26. Upon updating on March 5, the above error manifested.
Librewolf, Tor Browser, mpv, Viewnior, Deadbeef, Lutris, and PulseEffects failed to launch as well.
Krita and JDownloader still works though. (They don't rely on D-Bus or something?)
fcitx and fcitx-mozc were not updated on March 5, so some other package update must have have caused the sudden issue.
I didn't realize it was an issue from fcitx and fcitx-mozc back then.
To make matters worst, Timeshift CLI couldn't restore my system too.
Since I had to urgently get my computer working for the weekday. it was reformatted.
Reconfiguring my fresh system led me to the above discovery.
