[bug](Meshroom:9223): dconf-WARNING **: 20:47:17.888: failed to commit changes to dconf: L’exécution du processus fils « dbus-launch » a échoué (Aucun fichier ou dossier de ce nom)

[gxcl2018]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Log
If applicable, copy paste the relevant log output (please embed the text in a markdown code tag "```" )

Desktop (please complete the following and other pertinent information):

• OS: [e.g. win 10, osx, ]
• Python version [e.g. 2.6]
• Qt/PySide version [e.g. 5.15.2]
• Meshroom version: please specify if you are using a release version or your own build
  • Binary version (if applicable) [e.g. 2019.1]
  • Commit reference (if applicable) [e.g. 08ddbe2]

Additional context
Add any other context about the problem here.

[gxcl2018]

Ubuntu22.03, Meshroom-2023.3.0, python3
Impossible d'utiliser les fonctions import, save etc.. l'interface des gestion de fichier se charge mais reste gelée, inactive, impossible de naviguer dans l'arborescence des fichiers, tout est figé sauf le bouton cancel.
Ce qui fonctionne, le glisser déposer les images , le calcul du modèle (sans sauvegarde possible) le résultat est disponible dans un dossier temp...
sudo systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/lib/systemd/system/dbus.service; static)
Active: active (running) since Fri 2024-04-26 20:24:15 CEST; 18min ago
TriggeredBy: ● dbus.socket
Docs: man:dbus-daemon(1)
Main PID: 688 (dbus-daemon)
Tasks: 1 (limit: 18716)
Memory: 566.6M
CPU: 12.820s
CGroup: /system.slice/dbus.service
└─688 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

avril 26 20:35:42 clem-Crawler-E30e AptDaemon[4284]: INFO: Quitting due to inactivity
avril 26 20:35:42 clem-Crawler-E30e org.debian.apt[4284]: 20:35:42 AptDaemon [INFO]: Quitting due to inactivity
avril 26 20:35:42 clem-Crawler-E30e org.debian.apt[4284]: 20:35:42 AptDaemon [INFO]: Quitting was requested
avril 26 20:35:42 clem-Crawler-E30e AptDaemon[4284]: INFO: Quitting was requested
avril 26 20:36:32 clem-Crawler-E30e dbus-daemon[688]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1>
avril 26 20:36:32 clem-Crawler-E30e dbus-daemon[688]: [system] Successfully activated service 'org.freedesktop.hostname1'
avril 26 20:37:36 clem-Crawler-E30e dbus-daemon[688]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1>
avril 26 20:37:36 clem-Crawler-E30e dbus-daemon[688]: [system] Successfully activated service 'org.freedesktop.hostname1'
avril 26 20:40:41 clem-Crawler-E30e dbus-daemon[688]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1>
avril 26 20:40:41 clem-Crawler-E30e dbus-daemon[688]: [system] Successfully activated service 'org.freedesktop.hostname1'

[msanta]

I have the same issue with 2023.3. You can try to use the previous version of Meshroom (2023.2)

[gxcl2018]

Ok, merci Le lun. 29 avr. 2024, 12:28, msanta ***@***.***> a écrit :

…

I have the same issue with 2023.3. You can try to use the previous version of Meshroom (2023.2) — Reply to this email directly, view it on GitHub <#2392 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJRTXADIVP37ILGCY5LSHADY7YOGHAVCNFSM6AAAAABG3335FOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSGM3TKNRWGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[gxcl2018]

Un grand merci, je confirme meshroom 3.2.0 fonctionne Many thanks, I confirm meshroom 3.2.0 works Le lun. 29 avr. 2024 à 12:28, msanta ***@***.***> a écrit :

…

I have the same issue with 2023.3. You can try to use the previous version of Meshroom (2023.2) — Reply to this email directly, view it on GitHub <#2392 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJRTXADIVP37ILGCY5LSHADY7YOGHAVCNFSM6AAAAABG3335FOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSGM3TKNRWGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>