Weird IBus error: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation

○ org.freedesktop.IBus.session.generic.service - IBus Daemon for generic sessions
     Loaded: error (Reason: Unit org.freedesktop.IBus.session.generic.service failed to load properly, please adjust/correct and reload service manager: File exists)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

4月 25 14:14:23 ASUS-TX-FX608-PC systemd[3171]: org.freedesktop.IBus.session.generic.service: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation.
4月 25 14:14:23 ASUS-TX-FX608-PC systemd[3171]: org.freedesktop.IBus.session.generic.service: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation.
4月 25 14:14:23 ASUS-TX-FX608-PC systemd[3171]: org.freedesktop.IBus.session.generic.service: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation.
4月 25 14:20:54 ASUS-TX-FX608-PC systemd[3171]: org.freedesktop.IBus.session.generic.service: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation.
4月 25 14:20:54 ASUS-TX-FX608-PC systemd[3171]: org.freedesktop.IBus.session.generic.service: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation.
4月 25 14:20:54 ASUS-TX-FX608-PC systemd[3171]: org.freedesktop.IBus.session.generic.service: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation.
4月 25 19:17:49 ASUS-TX-FX608-PC systemd[3171]: org.freedesktop.IBus.session.generic.service: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation.
● org.freedesktop.IBus.session.GNOME.service - IBus Daemon for GNOME
     Loaded: loaded (/usr/lib/systemd/user/org.freedesktop.IBus.session.GNOME.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2026-04-25 13:28:07 CST; 7h ago
 Invocation: 2267250d89534bf3bc970d3e0eab7db3
   Main PID: 3617 (ibus-daemon)
      Tasks: 20 (limit: 37562)
     Memory: 116.3M (peak: 119.5M)
        CPU: 40.430s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
             ├─3617 /usr/bin/ibus-daemon --panel disable
             ├─3757 /usr/libexec/ibus-dconf
             ├─3758 /usr/libexec/ibus-extension-gtk3
             └─4018 /usr/libexec/ibus-engine-libpinyin --ibus

4月 25 13:28:07 ASUS-TX-FX608-PC systemd[3171]: Starting org.freedesktop.IBus.session.GNOME.service - IBus Daemon for GNOME...
4月 25 13:28:07 ASUS-TX-FX608-PC systemd[3171]: Started org.freedesktop.IBus.session.GNOME.service - IBus Daemon for GNOME.
/usr/lib/systemd/user/gnome-session.target.wants/org.freedesktop.IBus.session.GNOME.service:BusName=org.freedesktop.IBus
/usr/lib/systemd/user/org.freedesktop.IBus.session.GNOME.service:BusName=org.freedesktop.IBus
/usr/lib/systemd/user/org.freedesktop.IBus.session.generic.service:BusName=org.freedesktop.IBus

I only moved the hard drive from my old computer to a new one, and then this error suddenly appeared for no obvious reason. I don’t understand what happened at all.

EDIT: I have found the trigger path for this warning (i.e. when enumerating all systemd services), but I still haven’t figured out where the change occurred that caused this warning to suddenly appear.

We would need more details to understand your issue:

  • Make, models, and graphics cards of the old and new systems
  • Fedora version
  • Was the old system working?
  • Have you tried the rescue kernel?
  • Are you able to boot a Fedora Live USB installer?

Installing Fedora is less open-ended if you can use a Fedora Live USB installer. You should use the installer Live session to make a backup of important data before attempting the install.

This is weird since those services look like they should be mutually exclusive (one requires gnome-session-initialized.target and one declares a conflict with it).

Do your unit files look the same as these?

$ cat /usr/lib/systemd/user/org.freedesktop.IBus.session.generic.service
[Unit]
Description=IBus Daemon for generic sessions
CollectMode=inactive-or-failed

# Never run in GNOME
Conflicts=gnome-session-initialized.target

[Service]
Type=dbus
ExecStart=sh -c 'exec /usr/bin/ibus-daemon $IBUS_DAEMON_ARGS'
Restart=on-abnormal
BusName=org.freedesktop.IBus
TimeoutStopSec=5
Slice=session.slice
$ cat /usr/lib/systemd/user/org.freedesktop.IBus.session.GNOME.service
[Unit]
Description=IBus Daemon for GNOME
CollectMode=inactive-or-failed

# Require GNOME session and specify startup ordering
Requisite=gnome-session-initialized.target
After=gnome-session-initialized.target
PartOf=gnome-session-initialized.target
Before=gnome-session.target

# Needs to run when DISPLAY/WAYLAND_DISPLAY is set
After=gnome-session-initialized.target
PartOf=gnome-session-initialized.target

[Service]
Type=dbus
# Only pull --xim in X11 session, it is done via Xwayland-session.d on Wayland
ExecStart=sh -c 'exec /usr/bin/ibus-daemon --panel disable $([ "$XDG_SESSION_TYPE" = "x11" ] && echo "--xim")'
Restart=on-abnormal
BusName=org.freedesktop.IBus
TimeoutStopSec=5
Slice=session.slice

[Install]
WantedBy=gnome-session.target

I have similar warnings, seems ibus conflicts with itself .

leigh@mpd-pc:~$ rpm -qf /usr/lib/systemd/user/org.freedesktop.IBus.session.generic.service /usr/lib/systemd/user/gnome-session.target.wants/org.freedesktop.IBus.session.GNOME.service
ibus-1.5.34~rc2-1.fc44.x86_64
ibus-1.5.34~rc2-1.fc44.x86_64
leigh@mpd-pc:~$ systemctl --user status org.freedesktop.IBus.session.GNOME.service
○ org.freedesktop.IBus.session.GNOME.service - IBus Daemon for GNOME
     Loaded: loaded (/usr/lib/systemd/user/org.freedesktop.IBus.session.GNOME.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

Apr 25 13:13:30 mpd-pc systemd[1596]: org.freedesktop.IBus.session.GNOME.service: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation.
Apr 25 13:15:02 mpd-pc systemd[1596]: org.freedesktop.IBus.session.GNOME.service: Two services allocated for the same bus name org.freedesktop.IBus, refusing operation.
leigh@mpd-pc:~$ systemctl --user status org.freedesktop.IBus.session.generic.service
○ org.freedesktop.IBus.session.generic.service - IBus Daemon for generic sessions
     Loaded: loaded (/usr/lib/systemd/user/org.freedesktop.IBus.session.generic.service; static)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)
leigh@mpd-pc:~$ 

It seems harmless, neither gnome-shell, cinnamon and probably other DE’s use these user services.

Yes, it’s all the same.

Yes, harmless. The main question I’m asking is that I don’t have this warning on my old computer, but it does on my new computer. I have found the trigger path for this warning, but I still haven’t figured out where the change occurred that caused this warning to suddenly appear.

Seeing how the hardware differs might provide a clue.

Maybe there’s a race condition in service startup, and it’s sensitive to hardware timings.

Just guessing though, and I don’t know that it could be reliably deduced from hardware specs.

The org.freedesktop.IBus.session.generic.service file includes a line of Conflicts=gnome-session-initialized.target but the systemd does not skip the service for the same bus name.
Probably I think it would be a RFE for systemd.

I can make a sub package of the file org.freedesktop.IBus.session.generic.service likes ibus-session-file-generic separated from ibus package if you desire it.

Race conditions change with hardware. It would be useful to know if the Unit org.freedesktop.IBus.session.generic.service failed to load properly entries occur in journals from the old system.

I’m not sure why you insist the race conditions. The systemctl status shows the error is caused by the same BusName clearly.

When you log into the GNOME session with IBus, org.freedesktop.IBus.session.GNOME.service is started by the GNOME DE automatically.

When you start org.freedesktop.IBus.session.generic.service with systemd command by manual after the login, the error can happen as I explained it above.

The puzzle is that OP didn’t have this issue when using identical software on different hardware:

What would you say is the most likely reason for that?

I’m not insisting it’s a race condition – I literally said I was “just guessing”! – I’m only suggesting it as a possibility.