FS#36528 - [p11-kit] and lib32-p11-kit violate the FHS and work incorrectly on multilib systems

Attached to Project: Arch Linux
Opened by Pascal Ernster (hardfalcon) - Wednesday, 14 August 2013, 14:14 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 30 May 2023, 21:13 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ionut Biru (wonder)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
p11-kit and lib32-p11-kit both put the configuration files for their modules into /usr/share/p11-kit/modules/ although these configuration files are architecture dependend because they control which modules from /usr/lib/pkcs11/ and /usr/lib32/pkcs11/ are loaded. This violates the HFS[1] and causes applications using lib32-p11-kit to throw errors when x86_64 p11-kit modules are installed without their respective i686 counterparts.
The most notable example is probably wine and gnome-keyring on x86_64 without having lib32-gnome-keyring installed which is an AUR package and does currently not exist as official package in the multilib repositories).

I therefore propose that p11-kit and lib32-p11-kit be changed to respect the HFS and put these configuration files into /usr/lib/p11-kit/modules/ and /usr/lib32/p11-kit/modules.



[1] https://wiki.archlinux.org/index.php/Arch_filesystem_hierarchy#.2Fusr.2Fshare:_Architecture_independent_data



Additional info:
* affected packages:
- p11-kit <= 0.18.4-1
- lib32-p11-kit <= 0.18.4-1
- gnome-keyring <= 3.8.2-1



Steps to reproduce:

1. On an x86_64 system, install wine, p11-kit, gnome-keyring and lib32-p11-kit, but *not* lib32-gnome-keyring (not in the repos anyway, but exists as AUR package).

2. Delete/remove your ~/.wine directory (if existing)

3. Run winecfg and notice the error message "p11-kit: couldn't load module: /usr/lib32/pkcs11/gnome-keyring-pkcs11.so: /usr/lib32/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory"
This task depends upon

Closed by  Toolybird (Toolybird)
Tuesday, 30 May 2023, 21:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  "Issue can't be reproduced anymore"
Comment by Pascal Ernster (hardfalcon) - Friday, 16 August 2013, 15:51 GMT
I've filed the bug upstream and written a patch, which has been adopted into their git repository:

https://bugs.freedesktop.org/show_bug.cgi?id=68122

http://cgit.freedesktop.org/p11-glue/p11-kit/commit/?id=2978f8fb27681e9f40575ae2be26012e8a54fc71

I suggest to include that patch into p11-kit and lib32-p11-kit for the time being until upstream pushes out a new release (see 2 attached PKGBUILD files).

The package gnome-keyring would have to be rebuilt as well.
   PKGBUILD (1.2 KiB)
   PKGBUILD (1.5 KiB)
Comment by Pascal Ernster (hardfalcon) - Sunday, 12 April 2015, 18:40 GMT
Will there be any follow-up to this? In the meantime, wine has become a native x86_64 package, and as far as I can tell, there doesn't seem to be any package having lib32-p11-kit as an optional dependency (at least not in the official repositories).

Upstream has added the additional ./configure option of "--with-module-config" to address this already one and a half year ago.
Comment by Florian Pritz (bluewind) - Sunday, 12 April 2015, 18:57 GMT
I'm waiting on p11-kit (so Ionut) for a decision. I try to stay as close as possible to the extra packages.
Comment by Pascal Ernster (hardfalcon) - Sunday, 18 June 2017, 09:48 GMT
Can this bug be reassigned to heftig?

The p11-kit package is marked as orphaned, and even though the lib32-p11-kit package is formally still owend by fyan (even though he doesn't seem to have made a single git commit concerning Archlinux packages since a whole year, and hasn't looked after the lib32-p11-kit package for one and a half years), it is effectively heftig who has been keeping both packages up to date for quite a while now.
Comment by Jan Alexander Steffens (heftig) - Sunday, 18 June 2017, 20:50 GMT
I'm not sure avoiding an error message is worth the potential headache of a non-default path.
Comment by Florian Pritz (bluewind) - Thursday, 22 June 2017, 08:22 GMT
I just tried to remove the .wine dir and run winecfg, but I didn't get this error message. p11-kit, lib32-p11-kit and gnome-keyring are installed, but I had just installed gnome-keyring so maybe this requires it to be set up in some specific way.

Can you still reproduce the issue?
Comment by Pascal Ernster (hardfalcon) - Tuesday, 30 May 2023, 21:10 GMT
Sorry for not responding earlier. I can't reproduce the issue anymore, either.

Loading...