From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] New libcap-ng package breaks gnome-keyring-daemon and cifs-utils
Date: Thu, 17 Dec 2020 14:51:27 +0100 [thread overview]
Message-ID: <20201217135127.smGDSkMN0Z1aPAT9B68h7LyNI0u_lQiT6KxOb-sJ6L4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27216@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
Closed issue by lane-brain on void-packages repository
https://github.com/void-linux/void-packages/issues/27216
Description:
It seems that `libcap-ng` 0.8.2 was finally committed to master 10 hours ago. Upon updating to the new package today, I noticed that gnome-keyring-daemon could not launch, giving the following error:
`gnome-keyring-daemon: error dropping process capabilities, aborting'
Research led me to this:
https://bugs.archlinux.org/task/68664
Then to:
https://github.com/stevegrubb/libcap-ng/issues/21
Which then led me to this:
https://github.com/GNOME/gnome-keyring/commit/ebc7bc9efacc17049e54da8d96a4a29943621113#diff-362e1a6b74e7bdbf1d0448cb892b79fe99ff7949c8c7bfd95788e9c5cd70b61b
And it seems also that `cifs-utils` was affected. Here is the commit that fixes their issue with the new libcap-ng.
https://github.com/piastry/cifs-utils/commit/fcef79bc705b70862326e1394dfe77295086bcbb
Merging the patch from gnome-keyring-daemon was all it took to get it back working, so I bumped up the revision and added the patchfile pulled from the commit. Also built the cifs-utils with that repo's commit fixing this issue and included the patch as well.
I've made a branch on my forked repo with the changes. Builds look good on my end. Submitting a pull request.
prev parent reply other threads:[~2020-12-17 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 6:44 [ISSUE] " lane-brain
2020-12-17 6:52 ` lane-brain
2020-12-17 7:14 ` lane-brain
2020-12-17 13:51 ` ericonr
2020-12-17 13:51 ` ericonr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201217135127.smGDSkMN0Z1aPAT9B68h7LyNI0u_lQiT6KxOb-sJ6L4@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).