Closed fedelibre closed 3 years ago
I'm now testing the latest release (5.15.2) of PyQtWebEngine and I see different errors in the terminal.
When I launch Frescobaldi:
[2:2:1220/231455.045194:ERROR:network_service_instance_impl.cc(262)] Network service crashed, restarting service.
LaunchProcess: failed to execvp:
/app/bin
When I launch QtWebEngineProcess:
[📦 org.frescobaldi.Frescobaldi ~]$ QtWebEngineProcess
LaunchProcess: failed to execvp:
/app/bin
LaunchProcess: failed to execvp:
/app/bin
[4:10:1220/231534.533016:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
Rilevato trace/breakpoint (core dump creato)
I'll try the --disable-gpu
flag.
Here's what I get after building with --disable-gpu
. See the qtwebengine-fix branch.
Note the two different messages:
[📦 org.frescobaldi.Frescobaldi ~]$ QtWebEngineProcess
LaunchProcess: failed to execvp:
/app/bin
[3:3:1221/234651.580983:FATAL:zygote_communication_linux.cc(260)] Cannot communicate with zygote
Rilevato trace/breakpoint (core dump creato)
[📦 org.frescobaldi.Frescobaldi ~]$
[📦 org.frescobaldi.Frescobaldi ~]$ QtWebEngineProcess
LaunchProcess: failed to execvp:
/app/bin
LaunchProcess: failed to execvp:
/app/bin
[22:28:1221/234715.009174:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
Rilevato trace/breakpoint (core dump creato)
I need some help.
Does passing --device=dri
maybe help?
I've added it, but it doesn't help:
$ flatpak info --show-permissions org.frescobaldi.Frescobaldi
[Context]
shared=network;ipc;
sockets=x11;pulseaudio;
devices=dri;all;
filesystems=home;xdg-config/kdeglobals:ro;
[Session Bus Policy]
com.canonical.AppMenu.Registrar=talk
[Environment]
QTWEBENGINEPROCESS_PATH=/app/bin
[Environment] QTWEBENGINEPROCESS_PATH=/app/bin
If you search QTWEBENGINEPROCESS_PATH
in the flathub organisation on github you'll find that the two other occurences are as follow:
--env=QTWEBENGINEPROCESS_PATH=/app/bin/QtWebEngineProcess
Which given the error
LaunchProcess: failed to execvp:
/app/bin
make sense...
Does passing
--device=dri
maybe help?
For the record --device=all
includes dri
.
For the record
--device=all
includesdri
.
Are you sure? Then why Flatseal uses separate/indipendent items?
Back then, I did look at the flatpak source code to answer the question:
--device=all expose all the devices but shm
.
Flatseal expose the options as they are available.
--env=QTWEBENGINEPROCESS_PATH=/app/bin/QtWebEngineProcess
Thank you @hfiguiere ! This fixes the problem. And --device=dri
is not needed.
BTW, I cannot remember why I put --device=all
. Perhaps to be able to open files from USB disks? I'll have to check if I can remove it.
BTW, I cannot remember why I put
--device=all
. Perhaps to be able to open files from USB disks? I'll have to check if I can remove it.
You need this for MIDI and/or ALSA sound.
It won't help to open files from USB disks.
Qt5 WebEngine module is built incorrectly because:
I've verified that this does not occur if I build the flatpak without WebEngine module.
Short term workaround might be disabling this module. But I'd prefer fixing it.
Debugging
Enter the sandbox:
Here's the culprit:
Now if I disable GPU in the module:
I get this error: