Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QtWebEngine
  4. Can't get QtWebEngine to work on Raspberry Pi 3B
Forum Updated to NodeBB v4.3 + New Features

Can't get QtWebEngine to work on Raspberry Pi 3B

Scheduled Pinned Locked Moved Unsolved QtWebEngine
qtwebengineraspberry pi 3yocto
1 Posts 1 Posters 824 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.
  • Y Offline
    Y Offline
    Yury Lunev
    wrote on last edited by
    #1

    Hello! I try to run the bare most sample of QtWebEngine on a Raspberry Pi using Yocto thud/warrior and EGLFS platform:

    import QtQuick 2.0
    import QtQuick.Window 2.0
    import QtWebEngine 1.5
    
    Window {
        width: 1024
        height: 750
        visible: true
        WebEngineView {
            anchors.fill: parent
            url: "https://www.qt.io"
        }
    }
    

    But I get this on stdout:

    # QTWEBENGINE_DISABLE_SANDBOX=1 qmlscene -platform eglfs 123.qml
    QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/var/volatile/tmp/runtime-root'
    Unable to query physical screen size, defaulting to 100 dpi.
    To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters).
    Sandboxing disabled by user.
    Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing.
    Trace/breakpoint trap
    

    And this on dmesg (a line on each attempt):

    [ 2742.973347] Unhandled prefetch abort: breakpoint debug exception (0x002) at 0x7143f14a
    [ 2776.056549] Unhandled prefetch abort: breakpoint debug exception (0x002) at 0x6fc3f14a
    [ 3024.671555] Unhandled prefetch abort: breakpoint debug exception (0x002) at 0x6fc3f14a
    

    I have gpu_mem=512 and I use userland drivers, not vc4. Had the very same issue with vc4graphics, though.

    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