FS#68963 - [libcap-ng] [cifs-utils] > 0.8.1 breaks cifs mounts

Attached to Project: Arch Linux
Opened by Tarqi Kazan (Tarqi) - Sunday, 13 December 2020, 01:05 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 13 December 2020, 18:06 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To David Runge (dvzrv)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:

- Updated libcap-ng from 0.8.1 to 0.8.2-1, client could not mount any cifs share, failing with "Unable to apply new capability set."
- Donwgraded to 0.8.1-1, same behavior.
- Downgraded to 0.8.1, works again.

Additional info:
- Slackware-Thread: https://www.linuxquestions.org/questions/slackware-14/unable-to-mount-cifs-error-unable-to-apply-new-capability-set-4175685756/
- Slackware-Thread: https://www.linuxquestions.org/questions/slackware-14/i-had-a-problem-with-current-package-libcap-ng-0-8-1-placed-in-current-11-19-a-4175685551/
- Possible Patch for cifs-utils: https://marc.info/?l=linux-cifs&m=160595758021262

Steps to reproduce:
- Upgrade to libcap-ng on some cifs-client
- Try to mount a share
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 13 December 2020, 18:06 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#68666 
Comment by Lukas Sabota (punkrockguy318) - Sunday, 13 December 2020, 01:12 GMT
This happened to me as well. It looks like gentoo is also having this same issue with libcap-ng 0.8.2 https://bugs.gentoo.org/759565
Comment by David Runge (dvzrv) - Sunday, 13 December 2020, 09:15 GMT
@Tarqi: Thanks for the report.

Can you test whether cifs-utils 6.11-2 fixes your problem? It has a patch applied for this situation.
Comment by Karel De Vriendt (kdvgent) - Sunday, 13 December 2020, 17:14 GMT
Did a new "pacman -Syu" that included cifs-utils 6.11-2. Fixed indeed the problem for me.
Comment by Tarqi Kazan (Tarqi) - Sunday, 13 December 2020, 17:20 GMT
@David: Sorry for the duplicate, I usually search just for OPEN bugs.

Updating to cifs-utlis 6.11-2 has fixed the problem.

So that's one of the rare cases, that an update has made it into the repos, but not its "dependency". Ideas, how to handle this?

Loading...