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. Migrating from Qt5 Beta 2 to Final Version
Forum Updated to NodeBB v4.3 + New Features

Migrating from Qt5 Beta 2 to Final Version

Scheduled Pinned Locked Moved General and Desktop
3 Posts 3 Posters 2.5k Views 1 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.
  • I Offline
    I Offline
    Itehnological
    wrote on last edited by
    #1

    Hello,
    I just installed the recently released Qt5 Final. I had been working on an app with Qt5 Beta 2, and now when I compile it I am getting some strange output and no GUI.

    @Qt at-spi: error getting the accessibility dbus address: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
    Accessibility DBus not found. Falling back to session bus.@

    P.S. There are some method missing from QWindow now like QWindow::setWindowFlags(). What should I use for a frameless window now?

    1 Reply Last reply
    0
    • M Offline
      M Offline
      marsupial
      wrote on last edited by
      #2

      bq. P.S. There are some method missing from QWindow now like QWindow::setWindowFlags(). What should I use for a frameless window now?

      QWindow now implements the function "setFlags()":http://qt-project.org/doc/qt-5.0/qtgui/qwindow.html#flags-prop which works the same way as "setWindowFlags() of QWidget":http://qt-project.org/doc/qt-5.0/qtwidgets/qwidget.html#windowFlags-prop.

      Note that QWidget and QWindow are unrelated.

      Regarding your other issue: Seems to have something to do with dbus and I have no experience with that module... But it's strange that you don't get any GUI just because some dbus functionality fails - at least if your main GUI doesn't heavily depend on it. Maybe you could try to disable the dbus parts of your app and try if everything else works as expected?

      1 Reply Last reply
      0
      • M Offline
        M Offline
        mutaphysis
        wrote on last edited by
        #3

        I had the same problem and "fixed" it by running

        @sudo apt-get remove qt-at-spi@

        Not sure if that helps...

        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