*** This bug is a duplicate of bug 1755250 ***
https://bugs.launchpad.net/bugs/1755250
** This bug has been marked a duplicate of bug 1792552
Qt doesn't cope with EPERM returned from statx(2)
** This bug is no longer a duplicate of bug 1792552
Qt doesn't cope with EPERM returned from st
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/177473
https://bugreports.qt.io/browse/QTBUG-70447 notes that a newer Docker
fixes it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774739
Title:
Running Qt apps inside a 18.04 container crashes
To mana
@mitya57, Thanks for having a look at this. I have tried starting dbus
and dbus-daemon as you have described before running QtCreator - but it
still fails in the same way :-/
I have also tried installing dbus-x11 and executing $ export $(dbus-
launch)to set the env vars, but this still results
Interesting that I cannot reproduce this on Debian sid, which has a
newer Docker.io version (18.03.1 vs. 17.12.1).
Can you try starting dbus before running the application, to see if that
helps?
$ sudo /etc/init.d/dbus start # Start the system bus
$ dbus-daemon --session --fork # And the sessi
Note I have tried using the .run offline installer of Qt 5.6/5.9/5.11,
what seems to happen is that they work on Ubuntu 16.04, 17.10 but fail
on 18.04 - this is the stacktrace for reference
https://pastebin.ubuntu.com/p/Yzj5gsmwQ3/
So it seems possible that it might be some underlying change to th
