mumblez Posted August 12, 2016 Report Posted August 12, 2016 Fresh installation of Fedora 24 Enpass rpm installed as normal user (non-root) After installation I'm able to launch and set up sync with dropbox After sync I see a list of all entries but no details, clicking on an entry to edit causes it to crash. Ran with runepass.sh afterwards to see if the output will help you: qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile QLayout: Attempting to add QLayout "" to QPasswordEdit "", which already has a layout libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile ./runenpass.sh: line 16: 4827 Segmentation fault (core dumped) $enpassRoot/Enpass $* The segmentation fault happens if I try to edit. Any ideas? (note if I run as root, fresh database, I am able to add an entry and see it's details without crashing)
mumblez Posted August 12, 2016 Author Report Posted August 12, 2016 Managed to get it working, instead of importing my 1password export (from mac) I started fresh on the linux side with a new database, added one entry and sync'd to dropbox (clearing the old app folder first), sync'd to mac to ensure it worked and then imported the 1password backup and sync again, now it's all working. I think it didn't like it when I tried syncing with dropbox where the data was on a mac first, so cleared everything and did it the other way around and it seems be working. We can close this. I also had an email from support related to this but lost track of the email, any chance someone can find it and close that too? Many Thanks
Burble-Bucket Posted August 30, 2016 Report Posted August 30, 2016 (edited) On Fedora 24 (and using KDE) you need to do this: 1) Run Enpass like this: "LD_LIBRARY_PATH=/opt/Enpass/libs/ QT_QPA_PLATFORM_PLUGIN_PATH=/opt/Enpass/plugins/ /opt/Enpass/Enpass" I created myself an alias for it to simplify the step. Basically, if the EnpassInstaller put it in the normal distirbution locations (i.e. not generic /opt), &/or they packaged it for Fed24 then neither of these steps would be necessary and you would not have had a problem. As I learned the hard way, I should advise others: do not put /opt/Enpass/libs in to your normal ld config, because you will break a bucket load of other items. Also, enpass does not run with LD_RUN_PATH, only the LD_LIBRARY_PATH variable. Edited August 30, 2016 by Burble-Bucket Ooopsies in the fix!
Recommended Posts