Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Qt6.5.0 and ibus (Ubuntu)
Forum Updated to NodeBB v4.3 + New Features

Qt6.5.0 and ibus (Ubuntu)

Scheduled Pinned Locked Moved Unsolved General and Desktop
28 Posts 5 Posters 12.9k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • posktomtenP posktomten

    Hello!
    Hope this is the right forum, otherwise you can speak up!
    Problem with ibus.
    Ubuntu 20.04, Qt6.4.3 and Qt6.5.0 work fine.
    Ubuntu 22.04 Qt6.4.3 works, Qt6.5.0 does NOT work.

    qt.dbus.integration: Could not connect "org.freedesktop.IBus" to globalEngineChanged(QString)
    

    I have checked that ibus works. No error messages in the sys log.
    Qt6.5.0 not finding ibus? And why only in Ubuntu 22.04?

    Maybe someone has encountered this and knows what to do.

    JoeCFDJ Offline
    JoeCFDJ Offline
    JoeCFD
    wrote on last edited by JoeCFD
    #5

    @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.

    posktomtenP 1 Reply Last reply
    0
    • JoeCFDJ 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.

      posktomtenP Offline
      posktomtenP Offline
      posktomten
      wrote on last edited by
      #6

      @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.

      posktomten

      JoeCFDJ 1 Reply Last reply
      0
      • posktomtenP 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.

        JoeCFDJ Offline
        JoeCFDJ Offline
        JoeCFD
        wrote on last edited by
        #7
        This post is deleted!
        posktomtenP 1 Reply Last reply
        0
        • JoeCFDJ JoeCFD

          This post is deleted!

          posktomtenP Offline
          posktomtenP Offline
          posktomten
          wrote on last edited by
          #8

          @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

          1 Reply Last reply
          0
          • posktomtenP Offline
            posktomtenP Offline
            posktomten
            wrote on last edited by
            #9

            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

            posktomten

            JoeCFDJ 1 Reply Last reply
            0
            • posktomtenP 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
              JoeCFDJ Offline
              JoeCFDJ Offline
              JoeCFD
              wrote on last edited by JoeCFD
              #10
              This post is deleted!
              posktomtenP 1 Reply Last reply
              0
              • JoeCFDJ JoeCFD

                This post is deleted!

                posktomtenP Offline
                posktomtenP Offline
                posktomten
                wrote on last edited by
                #11

                @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.

                posktomten

                JoeCFDJ 1 Reply Last reply
                0
                • posktomtenP 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.

                  JoeCFDJ Offline
                  JoeCFDJ Offline
                  JoeCFD
                  wrote on last edited by JoeCFD
                  #12

                  @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.

                  posktomtenP 1 Reply Last reply
                  0
                  • JoeCFDJ 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.

                    posktomtenP Offline
                    posktomtenP Offline
                    posktomten
                    wrote on last edited by posktomten
                    #13

                    @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.

                    posktomten

                    JoeCFDJ 1 Reply Last reply
                    0
                    • posktomtenP 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.

                      JoeCFDJ Offline
                      JoeCFDJ Offline
                      JoeCFD
                      wrote on last edited by
                      #14

                      @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.

                      C 2 Replies Last reply
                      1
                      • JoeCFDJ 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.

                        C Offline
                        C Offline
                        CPPUIX
                        wrote on last edited by
                        #15

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

                        1 Reply Last reply
                        1
                        • JoeCFDJ 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.

                          C Offline
                          C Offline
                          CPPUIX
                          wrote on last edited by CPPUIX
                          #16

                          @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!

                          JoeCFDJ 1 Reply Last reply
                          0
                          • C 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!

                            JoeCFDJ Offline
                            JoeCFDJ Offline
                            JoeCFD
                            wrote on last edited by JoeCFD
                            #17

                            @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.

                            C 1 Reply Last reply
                            1
                            • JoeCFDJ 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.

                              C Offline
                              C Offline
                              CPPUIX
                              wrote on last edited by
                              #18

                              @JoeCFD I'm on X11 actually.

                              JoeCFDJ 1 Reply Last reply
                              0
                              • C CPPUIX

                                @JoeCFD I'm on X11 actually.

                                JoeCFDJ Offline
                                JoeCFDJ Offline
                                JoeCFD
                                wrote on last edited by JoeCFD
                                #19

                                @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.

                                C 1 Reply Last reply
                                0
                                • JoeCFDJ 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.

                                  C Offline
                                  C Offline
                                  CPPUIX
                                  wrote on last edited by
                                  #20

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

                                  JoeCFDJ 1 Reply Last reply
                                  0
                                  • C CPPUIX

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

                                    JoeCFDJ Offline
                                    JoeCFDJ Offline
                                    JoeCFD
                                    wrote on last edited by
                                    #21

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

                                    C 1 Reply Last reply
                                    1
                                    • JoeCFDJ JoeCFD

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

                                      C Offline
                                      C Offline
                                      CPPUIX
                                      wrote on last edited by CPPUIX
                                      #22

                                      @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!

                                      1 Reply Last reply
                                      0
                                      • K Offline
                                        K Offline
                                        ksiour
                                        wrote on last edited by
                                        #23

                                        I am using Ubuntu 22.04 with x11 and I get the same message but the application works fine. I cannot switch to wayland as I am having issues with MS Teams. Is there any other solution for the message to disapear?

                                        C 1 Reply Last reply
                                        0
                                        • K ksiour

                                          I am using Ubuntu 22.04 with x11 and I get the same message but the application works fine. I cannot switch to wayland as I am having issues with MS Teams. Is there any other solution for the message to disapear?

                                          C Offline
                                          C Offline
                                          CPPUIX
                                          wrote on last edited by
                                          #24

                                          @ksiour that solution works for X11 as well.

                                          Did you try to purge ibus?

                                          JoeCFDJ 1 Reply Last reply
                                          0

                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Users
                                          • Groups
                                          • Search
                                          • Get Qt Extensions
                                          • Unsolved