Summary: | libsecrect/ gnome-keyring not working under wayland | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Nowshed H. Imran <now.im.627> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | kde, lonefenris |
Priority: | NOR | ||
Version: | 5.14.4 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Mailspring error message |
Description
Nowshed H. Imran
2018-12-03 04:54:30 UTC
I'm sorry but this is outside of KWin's responsibility. This is a KDE problem though. If you can kindly refer it to the maintainer that can solve it or the package related to it. There is no indication that this is a kde problem. All we know is that using two non kde applications don't work in a plasma Wayland session. What we also know is that at least one of those applications is not intended to be used outside of gnome. The problem is certainly not in anything kde provides. If you need user support to set this up please consult the user support of the named applications. Kde's bug tracker is not a user support forum, though. If there is any evidence showing that this is truly a bug in our software, please provide it. @now-im to help narrow it down, please run "env" in both the X and wayland case and look for differences there wrt gnome keyring. I filed the sddm issue. I'll look deeper into my env tomorrow. It seems to be a volatile issue for me as its gone from applications not being able to communicate with the gnome-keyring-daemon, to the daemon not starting on login, and back to the daemon starting but not communicating over the last several months. I'll note that I am also on Arch Linux, so there is some possibility of it being a packaging issue as well. The only differences I see in my env that I'd think *might* have some effect are SHLVL is one higher in Wayland (3) vs X (2) The X session sets GTK_MODULES=canberra-gtk-module, while the Wayland session does not. I don't necessarily think either of these should affect gnome-keyring, but the only other differences are ones I would expect -- thinks like the Wayland session having QT_WAYLAND_DISABLE_WINDOWDECORATION and QT_WAYLAND_FORCE_DPI variables and XDG_VTNR being set to 2 in Wayland instead of 1. No env variables seem to directly relate to gnome-keyring. I have filed a bug in mailspring as this doesn't seem like a KDE software problem. https://github.com/Foundry376/Mailspring/issues/1257 File it with gnome-keyring. |