Qt6.5.0 and ibus (Ubuntu)

posktomten

@Abderrahmene_Rayene said in Qt6.5.0 and ibus (Ubuntu):

I just ignore it since nothing seems to be broken

Nothing terrible seems to be happening. I do as you do. Just a little curious. Maybe it will work when Qt6.5.1 arrives. And a bit annoying...

CPPUIX

@posktomten I am curious as well, and would like my terminal output cleaned up, I intended to post about it here, but completely forgot to, thanks for the post.

JoeCFD

@posktomten said in Qt6.5.0 and ibus (Ubuntu):

qt.dbus.integration: Could not connect "org.freedesktop.IBus"

Is your Ubuntu 22.04 in a virtual machine? I have Qt6.5 on a machine with Ubuntu 22.04 and Qt works fine.

posktomten

@JoeCFD said in Qt6.5.0 and ibus (Ubuntu):

Is your Ubuntu 22.04 in a virtual machine?

No the opposite. Ubuntu 22.04 is a "real" computer. Ubuntu 20.04 is a VirtualBox guest to 22.04.

JoeCFD

This post is deleted!

posktomten

@JoeCFD It didn't help
Checked the sys log:

cat /var/log/syslog | grep org.freedesktop.IBus.session.GNOME

Apr 12 18:53:03 dell systemd[2307]: org.freedesktop.IBus.session.GNOME.service: Main process exited, code=exited, status=143/n/a
Apr 12 18:53:03 dell systemd[2307]: org.freedesktop.IBus.session.GNOME.service: Failed with result 'exit-code'.
Apr 12 18:53:03 dell systemd[2307]: org.freedesktop.IBus.session.GNOME.service: Consumed 2.087s CPU time.
Apr 14 19:34:21 dell systemd[2280]: org.freedesktop.IBus.session.GNOME.service: Consumed 7.672s CPU time.

Something doesn't seem right.
April 12, April 14

posktomten

Lubuntu 20.04 (Sorry, not Ubuntu. But it shouldn't matter. I think.)
Looks significantly nicer.

Apr 15 00:29:50 virt-lubuntu-20 dbus-daemon[774]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=775 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 15 00:29:50 virt-lubuntu-20 NetworkManager[775]: <info>  [1681511390.4501] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Apr 15 00:29:50 virt-lubuntu-20 NetworkManager[775]: <info>  [1681511390.4508] manager: (enp0s3): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Apr 15 00:29:50 virt-lubuntu-20 dbus-daemon[774]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 15 00:29:50 virt-lubuntu-20 udisksd[813]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Apr 15 00:29:50 virt-lubuntu-20 whoopsie[1073]: [00:29:50] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1
Apr 15 00:29:50 virt-lubuntu-20 whoopsie[1073]: [00:29:50] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
Apr 15 00:29:50 virt-lubuntu-20 whoopsie[1073]: [00:29:50] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
Apr 15 00:29:51 virt-lubuntu-20 dbus-daemon[774]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.31' (uid=0 pid=804 comm="/usr/lib/snapd/snapd " label="unconfined")
Apr 15 00:29:51 virt-lubuntu-20 dbus-daemon[774]: [system] Successfully activated service 'org.freedesktop.timedate1'
Apr 15 00:29:51 virt-lubuntu-20 dbus-daemon[774]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.19' (uid=0 pid=983 comm="/usr/sbin/cupsd -l " label="/usr/sbin/cupsd (enforce)")
Apr 15 00:29:51 virt-lubuntu-20 dbus-daemon[774]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Apr 15 00:29:54 virt-lubuntu-20 dbus-daemon[774]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.72' (uid=1000 pid=1542 comm="/usr/bin/lxqt-panel " label="unconfined")
Apr 15 00:29:54 virt-lubuntu-20 dbus-daemon[774]: [system] Successfully activated service 'org.freedesktop.UPower'
Apr 15 00:29:54 virt-lubuntu-20 ofonod[794]: parse_devices_reply: found 1st battery device: /org/freedesktop/UPower/devices/battery_BA
```T0

JoeCFD

This post is deleted!

posktomten

@JoeCFD I think you are right. No Qt related problem. Restarting ibus unfortunately does not help. I don't think it wants to start. Seems to be quite common if you check online.

JoeCFD

@posktomten I got the same issue on Ubuntu 22.04 in a virtual machine. And my test case even crashes. I googled around and could not find a solution. Then I switched to Wayland and the code does not crash anymore. Has Qt6.5 switched to Wayland completely? However, the ibus message is still there, but does not matter.

posktomten

@JoeCFD said in Qt6.5.0 and ibus (Ubuntu):

Then I switched to Wayland and the code does not crash anymore.

Hello! @JoeCFD
I use Wayland. No crashes but error message.

JoeCFD

@posktomten sorry I mixed ibus and dbus up. The following
/usr/bin/ibus-daemon --panel disable
is running. Killing it will remove the message. I will figure out why it is set-up.

CPPUIX

@JoeCFD Thank you!
Running ibus exit worked for me.

CPPUIX

@JoeCFD I'm not sure if this was caused by me stopping ibus, but it might've broken my system, I tried to access system settings and it kept crashing, I'm suspicious so I thought I'd just reboot and see if it goes away, and things got worse, my desktop could not load, except for the mouse pointer, and the screen edges were activated, but nothing else worked, just a dark screen.

I had to purge sddm and reinstall it, reboot, and things are back to normal, and so is ibus, it's running again, I'm too scared to have a go at it again haha, so the message can stay for now.

Again I'm not sure if it's due to ibus being stopped, just thought I'd share this in case someone else experiences this.

Thank you anyway!

JoeCFD

@Abderrahmene_Rayene
I guess Qt 6.5 needs ibus connection. But it seems
/usr/bin/ibus-daemon --panel disable
disables panel program and causes Qt code to generate the message. It should be enabled. On X11 it is ok since ibus is not even needed by Qt6.5. I believe it is only an issue on Wayland.
It is triggered by a script somewhere at start-up.

CPPUIX

@JoeCFD I'm on X11 actually.

JoeCFD

@Abderrahmene_Rayene can you try to purge ibus to see what will happen. I can run Qt6.5 on my LUbuntu 22.04. Ibus is not installed.

CPPUIX

@JoeCFD Oh no sorry, I cannot experiment on my current machine. OP might on his virtual machine

JoeCFD

@Abderrahmene_Rayene just tested it. the message is gone after ibus is purged. This is on Wayland.

CPPUIX

@JoeCFD I backed up my data, prayed, purged ibus, tested it, message gone, rebooted, system works fine, tested it again, message gone, problem solved!

This is on X11.

Thank you again!