dirkdavidis Posted August 9, 2020 Report Posted August 9, 2020 Hi i have a strange behaviour of Enpass. I have a brand new Fedora32 install. Enpass configured so far so good. So i check: autostart on login feature. Next time when i logged in after reboot i got just black screen nothing happens. So after figure out some stuff i deleted step after step all autostart apps and gotcha after i deleted Enpass from autostart login is possible. After login i can start Enpass no Problem but just when i let Enpass start automatically black screen. I use Fedora32 with Appindicator extension. Nothing really special i think. Any ideas what causes this issue?
Garima Singh Posted August 10, 2020 Report Posted August 10, 2020 Hey @dirkdavidis Welcome to the forum! Please share the following detail so that we can try to identify the issue- Which Enpass version are you using on the same device? Is your hardware an ARM architecture? Please share the screenshot of Enpass General settings. Are you having this issue on any other Linux device as well? Thanks for the co-operation.
dirkdavidis Posted August 12, 2020 Author Report Posted August 12, 2020 Hi @Garima Singh my Enpass Version is: 6.4.1.643 Architecture is x64 i just have one linux device: fedora 32. with Gnome 3.36.2 so i have the issue just on this device. i deactivated autostart for enpass settings and $USER/.config/autostart
dirkdavidis Posted August 12, 2020 Author Report Posted August 12, 2020 enpass.desktop[4364]: QQmlComponent: Created graphical object was not placed in the graphics scene. this is what journalctl logs when i am trying to login to gnome-shell and enpass is in autostart
Dentonthebear Posted August 12, 2020 Report Posted August 12, 2020 (edited) Hi @dirkdavidis There are a few posts that list the QQmlComponent error messages, a search will show you if anything applies to your setup. Edited August 12, 2020 by Dentonthebear
dirkdavidis Posted August 12, 2020 Author Report Posted August 12, 2020 Hi @Dentonthebear i think this qml is not the causing issue. i am trying to figure out what causes enpass + gdm + gnome-shell to cause this error
Garima Singh Posted August 13, 2020 Report Posted August 13, 2020 Hey @dirkdavidis Thanks for sharing the details. I have noted down this issue and notified the QA team to look into it. Thanks for your cooperation.
Pratyush Sharma Posted August 18, 2020 Report Posted August 18, 2020 Hi @dirkdavidis, Update Our team has been able to reproduce this issue, and we're now working for a fix. Hopefully, the fix will be available in future updates. We'll keep you updated on this topic. Thanks!
Recommended Posts