Hi. In the mean time I have run into a more serious problem. Ever since the latest updates to openSUSE Tumbleweed none of the (RPM) versions of 1password allow me to login, as they simply show a blank screen when selecting "open 1password". The app seems to be running fine, but simply does not display anything. Anything I can do to provide you with logfiles?
Hi @Frits, sorry to hear of this - we definitely would like to investigate, and logs would be very welcome!
There is a 1Password logs directory located at ~/.config/1Password/logs. If you can zip that up and attach it to an email to [email protected], our team will go through the data to figure out what might be going on here.
And we'll look forward to helping you get 1Password fully up and running! 🤝
Hi. No need to be sorry. As far as I can see there is nothing weird in the log. No error messages or anything.
It might have to do with a recent update to libc, which seems to have broken some programs. (electron based or not). The program I use for automatic backups to the cloud (Insync (https://www.insynchq.com/)) has exactly the same problem with multiple people mentioning the bug. Somewhere in forums people mentioned a couple more that show this behavior since the libc version bump.
I'll send the logfile and include a screenshot as well.
Having the same issue, dnf is giving a broken dependency error saying nothing provides systemd-udev, not sure if that's the cause or an additional issue along with libc.
Hi @rcj32 Starting to look like this is something we need to snag as soon as possible - would you mind reaching out to us at [email protected] and provide your logs? There is a 1Password logs directory located at ~/.config/1Password/logs
We're investigating this issue at the moment, so if we're able to confirm that the cause of the dependency error is the same we'll be able to personally follow up with you on this via email.
Please reference this post when you write in, and we'll pick things up there!
Great, I've just sent in an email with my logs. Thanks.
We've been looking into this on our end and have 1Password running normally with the below:
This should allow 1Password to start normally now.
@Frits @rcj32 Tagging you both for awareness, but we will have reached out to you both via email too.
Thanks. Received the email and instructions. Will try it out as early as possible today. I really appreciate the responsiveness of you (plural) in trying to solve this problem.
Success! I can confirm that it works.
Great to hear, @Frits. Thanks for the update! 😁