* [ISSUE] New libcap-ng package breaks gnome-keyring-daemon and cifs-utils
@ 2020-12-17 6:44 lane-brain
2020-12-17 6:52 ` lane-brain
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: lane-brain @ 2020-12-17 6:44 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
New 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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: New libcap-ng package breaks gnome-keyring-daemon and cifs-utils
2020-12-17 6:44 [ISSUE] New libcap-ng package breaks gnome-keyring-daemon and cifs-utils lane-brain
@ 2020-12-17 6:52 ` lane-brain
2020-12-17 7:14 ` lane-brain
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: lane-brain @ 2020-12-17 6:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 253 bytes --]
New comment by lane-brain on void-packages repository
https://github.com/void-linux/void-packages/issues/27216#issuecomment-747249203
Comment:
PR: https://github.com/void-linux/void-packages/pull/27217/commits/fa4bb383323f3ba2088cf40dde269a1118848e9c
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: New libcap-ng package breaks gnome-keyring-daemon and cifs-utils
2020-12-17 6:44 [ISSUE] New libcap-ng package breaks gnome-keyring-daemon and cifs-utils 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 ` [ISSUE] [CLOSED] " ericonr
3 siblings, 0 replies; 5+ messages in thread
From: lane-brain @ 2020-12-17 7:14 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 253 bytes --]
New comment by lane-brain on void-packages repository
https://github.com/void-linux/void-packages/issues/27216#issuecomment-747249203
Comment:
PR: https://github.com/void-linux/void-packages/pull/27217/commits/fa4bb383323f3ba2088cf40dde269a1118848e9c
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: New libcap-ng package breaks gnome-keyring-daemon and cifs-utils
2020-12-17 6:44 [ISSUE] New libcap-ng package breaks gnome-keyring-daemon and cifs-utils 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 ` [ISSUE] [CLOSED] " ericonr
3 siblings, 0 replies; 5+ messages in thread
From: ericonr @ 2020-12-17 13:51 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 275 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/27216#issuecomment-747450812
Comment:
Fixed in https://github.com/void-linux/void-packages/pull/27227 and https://github.com/void-linux/void-packages/pull/27220 , thanks!
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ISSUE] [CLOSED] New libcap-ng package breaks gnome-keyring-daemon and cifs-utils
2020-12-17 6:44 [ISSUE] New libcap-ng package breaks gnome-keyring-daemon and cifs-utils lane-brain
` (2 preceding siblings ...)
2020-12-17 13:51 ` ericonr
@ 2020-12-17 13:51 ` ericonr
3 siblings, 0 replies; 5+ messages in thread
From: ericonr @ 2020-12-17 13:51 UTC (permalink / raw)
To: ml
[-- 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.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-12-17 13:51 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-17 6:44 [ISSUE] New libcap-ng package breaks gnome-keyring-daemon and cifs-utils 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 ` [ISSUE] [CLOSED] " ericonr
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).