owncloud-client and nextcloud-client prompt for password despite that the keyring is unlocked #38266

alexeymuranov · 2018-03-31T23:13:06Z

Issue description

When starting OwnCloud client on NixOS, it prompts for password with the message:

Reading from keychain failed with error: 'No keychain service available'

This is on GNOME3, and the keyring is unlocked.

Steps to reproduce

Unlock Gnome Keyring and start OwnCloud client.

Technical details

§ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 4.14.29, NixOS, 18.03pre131587.b6ddb9913f2 (Impala)`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.0`
 - channels(alexey): `"nixos-17.03-17.03.1949.78e9665b48f, nixos-17.09-17.09.3205.12512f25e9e"`
 - channels(root): `"nixos-18.03pre131587.b6ddb9913f2"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs`

The text was updated successfully, but these errors were encountered:

jtojnar · 2018-04-02T13:31:27Z

It uses qtkeychain which should support libsecret, even though it is not linked against it. Maybe libsecret needs to be added to LD_LIBRARY_PATH like nextcloud-client does with the deprecated libgnome-keyring?

alexeymuranov · 2018-04-02T22:03:47Z

I installed and tried nextcloud-client, it also prompts for password.

eqyiel · 2018-05-23T00:15:47Z

@alexeymuranov IIRC it only prompts you for the password if you have nextcloud-client installed in your user env. Do you see the same result if it's in environment.systemPackages?

alexeymuranov · 2018-05-23T04:54:00Z

Yes, i installed it manually with nix-env -i.

I tried again after including both owncloud-client and nextcloud-client to environment.systemPackages, they both keep asking for password with the same message.

eqyiel · 2018-05-27T06:19:08Z

@alexeymuranov do you have security.pam.services.gdm.enableGnomeKeyring = true;?

alexeymuranov · 2018-05-27T08:06:41Z

I have security.pam.services.lightdm.enableGnomeKeyring = true;, i use LightDM.

jtojnar · 2018-06-21T04:58:59Z

Will that ever work? If I understand it correctly, the option is only respected when the default value of security.pam.services.<name?>.text is used:

nixpkgs/nixos/modules/security/pam.nix

Line 269 in cac9f08

text = mkDefault

lightdm seems to override it:

nixpkgs/nixos/modules/services/x11/display-managers/lightdm.nix

Line 230 in cac9f08

text = ''

Or is there some merge policy I am not aware of?

M-Gregoire · 2018-11-12T14:04:23Z

Does anyone has update on this? I have the exact same problem, I tried installing gnome3.libgnome-keyring, enabling the gnome keyring or create a keyring manually in seahorse but couldn't make it work.

rycee · 2018-11-15T22:43:24Z

The Nextcloud and keyrings topic seems related to this. The owncloud-client doesn't seem to have the wrapping around libgnome-keyring, though, so I don't know if anything like this is possible for it.

gmarmstrong · 2018-11-16T15:27:28Z

I've always had this issue, but it disappeared this month with some update (on NixOS 18.09). Is anyone still facing this issue on the latest 18.09?

alexeymuranov · 2018-11-16T18:26:56Z

I still have the problem in 18.09.

I tried the solution proposed in Nextcloud and keyrings topic, but it didn't work for some reason that is yet unclear to me (i started getting a message "the provided credentials are not correct" on nextcloud-client startup).

alexeymuranov · 2018-11-17T17:01:38Z

By the way, nextcloud-client on NixOS is somewhat outdated: still version 2.3.3 on master, while the latest stable is 2.5.0.

(I haven't got to properly test the solution with packageOverrides yet because I have my home folder shared between Ubuntu and NixOS, and I have nextcloud-client on both, and apparently trying to launch the version 2.3.3 on NixOS after using the version 2.5.0 on Ubuntu messes up the configuration. I believe this is not the issue when I do not use packageOverrides though -- the configuration is not getting messed up, but i have to enter the password each time.)

alexeymuranov · 2018-11-17T17:30:03Z

Ok, I confirm that using packageOverrides in configuration.nix as follows solves the problem for me:

{ # ...

  environment.systemPackages = [ # ...
    pkgs.nextcloud-client
  ];

  nixpkgs.config.packageOverrides = pkgs: {
    nextcloud-client = pkgs.nextcloud-client.override {
      withGnomeKeyring = true;
      libgnome-keyring = pkgs.gnome3.libgnome-keyring;
    };
  };
}

I am not closing the issue yet because I suppose that packageOverrides should not be necessary.

jtojnar · 2018-11-17T18:06:54Z

pkgs.nextcloud-client.override {
  withGnomeKeyring = true;
}

is how packages with withFoo arguments are supposed to be used. You do not need to use packageOverrides or overlays, you can pass the overridden package directly to environment.systemPackages.

As you noticed there is a bug where the package uses libgnome-keyring2, which should be fixed as follows:

--- a/pkgs/applications/networking/nextcloud-client/default.nix
+++ b/pkgs/applications/networking/nextcloud-client/default.nix
@@ -1,5 +1,5 @@
 { stdenv, fetchgit, cmake, pkgconfig, qtbase, qtwebkit, qtkeychain, qttools, sqlite
-, inotify-tools, withGnomeKeyring ? false, makeWrapper, libgnome-keyring }:
+, inotify-tools, withGnomeKeyring ? false, makeWrapper, libgnome-keyring ? null }:
 
 stdenv.mkDerivation rec {
   name = "nextcloud-client-${version}";
--- a/pkgs/top-level/all-packages.nix
+++ b/pkgs/top-level/all-packages.nix
@@ -4385,7 +4385,9 @@
 
   nextcloud = callPackage ../servers/nextcloud { };
 
-  nextcloud-client = libsForQt5.callPackage ../applications/networking/nextcloud-client { };
+  nextcloud-client = libsForQt5.callPackage ../applications/networking/nextcloud-client {
+    inherit (gnome3) libgnome-keyring;
+  };
 
   nextcloud-news-updater = callPackage ../servers/nextcloud/news-updater.nix { };

It would be even better to switch to libsecret as I suggested before:

--- a/pkgs/applications/networking/nextcloud-client/default.nix
+++ b/pkgs/applications/networking/nextcloud-client/default.nix
@@ -1,5 +1,5 @@
 { stdenv, fetchgit, cmake, pkgconfig, qtbase, qtwebkit, qtkeychain, qttools, sqlite
-, inotify-tools, withGnomeKeyring ? false, makeWrapper, libgnome-keyring }:
+, inotify-tools, makeWrapper, libsecret }:
 
 stdenv.mkDerivation rec {
   name = "nextcloud-client-${version}";
@@ -15,11 +15,10 @@
   patches = [ ./find-sql.patch ];
   patchFlags = "-d client -p1";
 
-  nativeBuildInputs = [ pkgconfig cmake ];
+  nativeBuildInputs = [ pkgconfig cmake makeWrapper ];
 
   buildInputs = [ qtbase qtwebkit qtkeychain qttools sqlite ]
-    ++ stdenv.lib.optional stdenv.isLinux inotify-tools
-    ++ stdenv.lib.optional withGnomeKeyring makeWrapper;
+    ++ stdenv.lib.optional stdenv.isLinux inotify-tools;
 
   enableParallelBuilding = true;
 
@@ -39,9 +38,9 @@
   postInstall = ''
     sed -i 's/\(Icon.*\)=nextcloud/\1=Nextcloud/g' \
       $out/share/applications/nextcloud.desktop
-  '' + stdenv.lib.optionalString (withGnomeKeyring) ''
+
     wrapProgram "$out/bin/nextcloud" \
-      --prefix LD_LIBRARY_PATH : ${stdenv.lib.makeLibraryPath [ libgnome-keyring ]}
+      --prefix LD_LIBRARY_PATH : ${stdenv.lib.makeLibraryPath [ libsecret ]}
   '';
 
   meta = with stdenv.lib; {

feel free to open a PR.

alexeymuranov · 2018-11-24T10:52:13Z

Thanks for the explanation, @jtojnar.

I do not think i will get to making a PR though, and by the way nextcloud-client has been updated to 2.5.0 on master: #50463. I have not checked if the problem is resolved in the with the update.

jtojnar · 2018-11-24T13:44:58Z

Nothing really changed in master, it was only refactoring. cc @Ma27 do you want to do the PR?

Ma27 · 2018-11-24T14:32:05Z

@jtojnar thanks a lot for the reference. In fact I'm currently using the Nextcloud client with the GNOME keyring enabled ATM.

I'll read through the entire conversation later and report back (or file a patch if needed) :)

This change makes it easier for users to setup the nextcloud client with GNOME keyring support as discussed in the IRC[1][2]. Additionaly we now use `libsecret` instead of `libgnome-keyring` which integrates better in a GNOME setup (libgnome-keyring defaults to the Gnome2 library)[3]. [1] https://logs.nix.samueldr.com/nixos/2018-11-24#1745871; [2] https://logs.nix.samueldr.com/nixos/2018-11-24#1746033; [3] NixOS#38266

kenogo · 2018-12-05T16:16:12Z

Still doesn't work for me. Here are the relevant parts of my /etx/nixos/configuration.nix

{ config, pkgs, ... }:
let
  nextcloud-client-keyring = pkgs.nextcloud-client.override {
    withGnomeKeyring = true;
    libgnome-keyring = pkgs.gnome3.libgnome-keyring;
  };
in
{
  environment.systemPackages = with pkgs; [
    nextcloud-client-keyring
  ];
  services.xserver = {
    enable = true;
    layout = "de";
    windowManager.bspwm.enable = true;
    displayManager.sddm.enable = true;
  };
  security.pam.services.sddm.enableGnomeKeyring = true;
}

ps aux | grep keyring confirms that gnome-keyring is running.

nghamilton · 2019-01-22T06:18:54Z

The following worked for me on 18.03:

{ config, pkgs, ... }:
let
  nextcloud-client-keyring = pkgs.nextcloud-client.override {
    withGnomeKeyring = true;
    libgnome-keyring = pkgs.gnome3.libgnome-keyring;
  };
in
{
  environment.systemPackages = with pkgs; [
    nextcloud-client-keyring
    gnome3.gcr
  ];
  services.dbus.packages = [ pkgs.gnome3.gnome-keyring pkgs.gnome3.gcr ];
  security.pam.services.<<your display manager>>.enableGnomeKeyring = true;
}

tiulpin · 2019-07-11T15:11:38Z

I still experience this issue on 19.03. Nothing suggested here helped, there is no flag 'withGnomeKeyring' anymore.

jtojnar · 2019-07-13T00:43:57Z

Someone needs to backport #60327 to 19.03.

jtojnar · 2019-07-13T00:46:59Z

Closing as the following config should be enough on NixOS unstable:

{ config, pkgs, ... }:
{
  services.gnome3.gnome-keyring.enable = true;
  environment.systemPackages = with pkgs; [
    nextcloud-client
  ];
}

Ma27 · 2019-07-13T01:13:37Z

@jtojnar oof, seems as I forgot to backport back then :(

I'll give it a try now :)

EDIT: nix-review with this change takes some time on release-19.03... I'll get some sleep now and push the fix tomorrow :)

Ma27 · 2019-07-13T10:18:37Z

Backported as 88cb463

caugner · 2019-08-05T17:53:36Z

@Ma27 Unfortunately, the backport doesn't seem to have solved the issue (for me). Did it for you, @jtojnar @tiulpin?

jtojnar · 2019-08-05T18:05:08Z

@caugner I use unstable and do not use nextcloud-client so cannot confirm. Can only confirm that it worked for me on unstable when I tested it.

caugner · 2019-08-06T13:17:31Z

@jtojnar Are you using unstable with Gnome? I tried it and Gnome was so unstable that I couldn't even login to any (local user) account anymore.

jtojnar · 2019-08-06T13:28:18Z

Yes, I use it every day without any issues. I suggest opening a separate issue for that.

b-m-f · 2019-08-31T18:01:22Z

This seems to persist for me on 19.03.

{ config, pkgs, ... }:
{
  services.gnome3.gnome-keyring.enable = true;
  environment.systemPackages = with pkgs; [
    nextcloud-client
  ];
}

Does unfortunately not work.

Did you make any progress @caugner ?

caugner · 2019-09-02T11:59:42Z

@b-m-f Nope, still doesn't work for me.

jtojnar · 2019-09-02T12:05:39Z

I cannot really test it on anything other than unstable but for what it’s worth, it works here in GNOME.

puppe · 2019-10-23T23:27:39Z

I have just submitted pull request #71874 which fixes this issue. Reviews are welcome.

alexeymuranov changed the title ~~owncloud-client prompts for password despite that the keyring is unlocked~~ owncloud-client and nextcloud-client prompt for password despite that the keyring is unlocked Apr 13, 2018

jtojnar mentioned this issue Jun 21, 2018

Gnome3 on Wayland sets SSH_AUTH_SOCK which breaks stuff #42291

Closed

gmarmstrong mentioned this issue Nov 23, 2018

owncloud-client always ask for password nix-community/home-manager#442

Closed

Ma27 mentioned this issue Nov 25, 2018

nextcloud-client: switch to libsecret and use it by default #51044

Merged

10 tasks

jtojnar closed this as completed Jul 13, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

owncloud-client and nextcloud-client prompt for password despite that the keyring is unlocked #38266

owncloud-client and nextcloud-client prompt for password despite that the keyring is unlocked #38266

alexeymuranov commented Mar 31, 2018

jtojnar commented Apr 2, 2018

alexeymuranov commented Apr 2, 2018 •

edited

Loading

eqyiel commented May 23, 2018

alexeymuranov commented May 23, 2018 •

edited

Loading

eqyiel commented May 27, 2018

alexeymuranov commented May 27, 2018

jtojnar commented Jun 21, 2018 •

edited

Loading

M-Gregoire commented Nov 12, 2018

rycee commented Nov 15, 2018

gmarmstrong commented Nov 16, 2018

alexeymuranov commented Nov 16, 2018

alexeymuranov commented Nov 17, 2018 •

edited

Loading

alexeymuranov commented Nov 17, 2018

jtojnar commented Nov 17, 2018

alexeymuranov commented Nov 24, 2018 •

edited

Loading

jtojnar commented Nov 24, 2018

Ma27 commented Nov 24, 2018

kenogo commented Dec 5, 2018 •

edited

Loading

nghamilton commented Jan 22, 2019 •

edited

Loading

tiulpin commented Jul 11, 2019

jtojnar commented Jul 13, 2019

jtojnar commented Jul 13, 2019

Ma27 commented Jul 13, 2019 •

edited

Loading

Ma27 commented Jul 13, 2019

caugner commented Aug 5, 2019 •

edited

Loading

jtojnar commented Aug 5, 2019

caugner commented Aug 6, 2019

jtojnar commented Aug 6, 2019

b-m-f commented Aug 31, 2019 •

edited

Loading

caugner commented Sep 2, 2019

jtojnar commented Sep 2, 2019

puppe commented Oct 23, 2019 •

edited

Loading

owncloud-client and nextcloud-client prompt for password despite that the keyring is unlocked #38266

owncloud-client and nextcloud-client prompt for password despite that the keyring is unlocked #38266

Comments

alexeymuranov commented Mar 31, 2018

Issue description

Steps to reproduce

Technical details

jtojnar commented Apr 2, 2018

alexeymuranov commented Apr 2, 2018 • edited Loading

eqyiel commented May 23, 2018

alexeymuranov commented May 23, 2018 • edited Loading

eqyiel commented May 27, 2018

alexeymuranov commented May 27, 2018

jtojnar commented Jun 21, 2018 • edited Loading

M-Gregoire commented Nov 12, 2018

rycee commented Nov 15, 2018

gmarmstrong commented Nov 16, 2018

alexeymuranov commented Nov 16, 2018

alexeymuranov commented Nov 17, 2018 • edited Loading

alexeymuranov commented Nov 17, 2018

jtojnar commented Nov 17, 2018

alexeymuranov commented Nov 24, 2018 • edited Loading

jtojnar commented Nov 24, 2018

Ma27 commented Nov 24, 2018

kenogo commented Dec 5, 2018 • edited Loading

nghamilton commented Jan 22, 2019 • edited Loading

tiulpin commented Jul 11, 2019

jtojnar commented Jul 13, 2019

jtojnar commented Jul 13, 2019

Ma27 commented Jul 13, 2019 • edited Loading

Ma27 commented Jul 13, 2019

caugner commented Aug 5, 2019 • edited Loading

jtojnar commented Aug 5, 2019

caugner commented Aug 6, 2019

jtojnar commented Aug 6, 2019

b-m-f commented Aug 31, 2019 • edited Loading

caugner commented Sep 2, 2019

jtojnar commented Sep 2, 2019

puppe commented Oct 23, 2019 • edited Loading

alexeymuranov commented Apr 2, 2018 •

edited

Loading

alexeymuranov commented May 23, 2018 •

edited

Loading

jtojnar commented Jun 21, 2018 •

edited

Loading

alexeymuranov commented Nov 17, 2018 •

edited

Loading

alexeymuranov commented Nov 24, 2018 •

edited

Loading

kenogo commented Dec 5, 2018 •

edited

Loading

nghamilton commented Jan 22, 2019 •

edited

Loading

Ma27 commented Jul 13, 2019 •

edited

Loading

caugner commented Aug 5, 2019 •

edited

Loading

b-m-f commented Aug 31, 2019 •

edited

Loading

puppe commented Oct 23, 2019 •

edited

Loading