[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 --- Comment #9 from Kyle Tirak --- Filed at https://gitlab.gnome.org/GNOME/gnome-keyring/issues/19 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 --- Comment #8 from David Edmundson --- File it with gnome-keyring. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 --- Comment #7 from now-im --- I have filed a bug in mailspring as this doesn't seem like a KDE software problem. https://github.com/Foundry376/Mailspring/issues/1257 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 --- Comment #6 from Kyle Tirak --- 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. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 Kyle Tirak changed: What|Removed |Added CC||lonefen...@gmail.com --- Comment #5 from Kyle Tirak --- 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. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #4 from David Edmundson --- @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. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 --- Comment #3 from Martin Flöser --- 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. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 --- Comment #2 from now-im --- 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. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 Martin Flöser changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Martin Flöser --- I'm sorry but this is outside of KWin's responsibility. -- You are receiving this mail because: You are watching all bug changes.
