GNU bug report logs -
#45267
Using gnome-keyring and LXQt as Desktop Environment
Previous Next
To reply to this bug, email your comments to 45267 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#45267
; Package
guix
.
(Wed, 16 Dec 2020 12:03:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"Hamzeh Nasajpour" <h.nasajpour <at> pantherx.org>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 16 Dec 2020 12:03:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi guys,
I want to install `gnome-keyring` service on my system. I'm using the LXQt as Desktop Environment. I had an issue for integrating ssh-agent with `gnome-keyring` and I noticed I should update this line in `desktop` files of `gnome-keyring`:
```
OnlyShowIn=GNOME;Unity;MATE;
```
to
```
OnlyShowIn=GNOME;Unity;MATE;LXQt;
```
So I re-packaged the `gnome-keyring` as follow:
```
(define-public gnome-keyring-modified
(package
(inherit gnome-keyring)
(name "gnome-keyring-modified")
(arguments
(substitute-keyword-arguments (package-arguments gnome-keyring)
((#:phases phases)
`(modify-phases ,phases
(add-after 'unpack 'patch-desktop-files
(lambda _
(substitute* '("daemon/gnome-keyring-secrets.desktop.in.in")
(("OnlyShowIn=GNOME;Unity;MATE;") "OnlyShowIn=GNOME;Unity;MATE;LXQt;"))
(substitute* '("daemon/gnome-keyring-pkcs11.desktop.in.in")
(("OnlyShowIn=GNOME;Unity;MATE;") "OnlyShowIn=GNOME;Unity;MATE;LXQt;"))
(substitute* '("daemon/gnome-keyring-ssh.desktop.in.in")
(("OnlyShowIn=GNOME;Unity;MATE;") "OnlyShowIn=GNOME;Unity;MATE;LXQt;"))
#t))))))))
```
The above package definition is ok and works, but since I want to use the `gnome-keyring` as service I should update `gnome-keyring-configuration` in my system configuration, so I'm using this config:
```
...
(service gnome-keyring-service-type
(gnome-keyring-configuration
(keyring gnome-keyring-modified)
(pam-services '(("passwd" . passwd)
("sddm" . login)))))
...
```
Now I reconfigured the system successfully, but `gnome-keyring` service is using the default `gnome-keyring`, not `gnome-keyring-modified` package, while I set the `keyring` to `gnome-keyring-modified`.
Do you have any idea?
--
Hamzeh Nasajpour
PantherX Team
Information forwarded
to
bug-guix <at> gnu.org
:
bug#45267
; Package
guix
.
(Fri, 18 Dec 2020 13:28:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 45267 <at> debbugs.gnu.org (full text, mbox):
Hello Hamzeh,
the gnome-keyring service is not the only place, in which gnome-keyring
is used. As far as I understand, all it does is unlocking your login
keyring; you have to ensure on your own, that the keyring argument
passed to it matches the keyring used by your applications.
I think you have two options going ahead. One would be to mark your
keyring as a replacement to the existing one. That would require the
non-trivial effort of maintaining a Guix fork while the patch is not
upstreamed and lobbying for its inclusion in mainline Guix. Is there
some merit in adding LXQt to this line or even dropping it entirely?
The second would be to replace gnome-keyring in every package using it
through package transformations.
Regards,
Leo
This bug report was last modified 4 years and 86 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.