You are not logged in.
Apologies for the rambling intro, but I'm not really sure what's going on.
I'm running Sway/Wayland and XWayland, and with an upgrade today I was no longer able to authenticate when starting nextcloud-client. I had been using just gnome-keyring and libsecret (no seahorse) without PAM auto-start so that when I logged in and started nextcloud I was presented with a dialog box to unlock the default keyring. This dialog box is no longer shown.
First I tried using PAM to unlock the keyring on login as described in the gnome keyring wiki entry. This works, but generates the "login" keyring and does not unlock the "default keyring" that I need.
Then I tried installing seahorse to see what was going on. It shows the default keyring and that it is locked as expected. However, when I try to unlock it nothing happens. In fact, I've found that seahorse will display certain dialog boxes, but not others. For example, if I try to add a new keyring it will prompt for a name, but nothing else. If I try to open the preferences I get nothing and the program freezes.
When I tail journalctl after launching nextcloud-client I get:
Apr 04 13:24:39 frank gcr-prompter[100090]: Gcr: deriving shared transport key
Apr 04 13:24:39 frank gcr-prompter[100090]: Gcr: deriving transport key
Apr 04 13:24:39 frank gcr-prompter[100090]: Gcr: starting password prompt for callback /org/gnome/keyring/Prompt/p8@:1.10
Apr 04 13:24:39 frank gcr-prompter[100090]: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height -3
Apr 04 13:24:39 frank gcr-prompter[100090]: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height 143
Apr 04 13:24:39 frank gcr-prompter[100090]: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height -3
Apr 04 13:24:39 frank gcr-prompter[100090]: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height 143
<message repeats>And when I run seahorse from the cli and try to open a dialog box that fails I get (for example):
seahorse-Message: 12:04:12.818: DNS-SD initialization failed: Daemon not running
Gdk-Message: 12:04:16.171: Window 0x2a30b6d5bd0 is a temporary window without parent, application will not be able to position it on screen.I assume the DNS message is unrelated.
I noticed that gtk was included in my upgrade today.
Any ideas on how to fix this? Should I try downgrading gtk?
Last edited by lecramed (2020-04-05 12:00:31)
Offline
Update: I have an i3/Xorg system set up largely the same way and it still works after upgrade - the original dialog box is presented to unlock the keychain when nextcloud is started. Unfortunately, there are too many differences between the machines to say anything definitive, but I suppose it could be a Wayland issue.
Offline
gtk3 3.24.17 broke wofi and waybar in sway for me (neither displayed anything). Downgrading fixed it.
Offline
Looks like I was running into https://gitlab.gnome.org/GNOME/gtk/-/issues/2572
Not sure if your problem is the same.
Offline
Seems to be my issue as well. Thanks for the link.
Resolved by downgrading to gtk3-1:3.24.16. Already fixed upstream I think: https://gitlab.gnome.org/GNOME/gtk/-/me … uests/1633
Offline