Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#36008 - multilib/wine 1.6rc4-1 is missing dependency lib32-gnome-keyring

Attached to Project: Community Packages
Opened by Pascal Ernster (hardfalcon) - Wednesday, 03 July 2013, 10:58 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 14 August 2013, 14:09 GMT
Task Type Bug Report
Category Packages: Multilib
Status Closed
Assigned To Florian Pritz (bluewind)
Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

The wine package is missing the dependency "lib32-gnome-keyring" on 64bit systems (and probably also "gnome-keyring" on 32bit systems). On my machine, this leads to error messages on the terminal when launching winecfg:

[hardfalcon@hardfalcon-3 ~]$ winecfg
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:iphlpapi:NotifyAddrChange (Handle 0x114e378, overlapped 0x114e390): stub
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
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:iphlpapi:NotifyAddrChange (Handle 0x130e8f0, overlapped 0x130e8fc): stub
wine: configuration in '/home/hardfalcon/.wine' has been updated.


These error messages disappear after compiling and installing the lib32-gnome-keyring package from AUR. I haven't tested this on i686, but given that the i686 wine package in community doesn't depend on gnome-keyring, I assume that i686 is also affected.

Additional info:
* package versions (for x86_64):
multilib/wine 1.6rc4-1
AUR/lib32-gnome-keyring 3.8.2-1

* config and/or log files etc: see above


Steps to reproduce:
Install multilib/wine 1.6rc4-1, launch "winecfg" and look at the error messages on the terminal.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Wednesday, 14 August 2013, 14:09 GMT
Reason for closing:  Not a bug
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 06 July 2013, 13:33 GMT
Cannot reproduce given the instructions and I have no gnome-keyring installed.
Comment by dx (dx) - Tuesday, 13 August 2013, 14:28 GMT
  • Field changed: Percent Complete (100% → 0%)
It happens with other apps too, but it's particularly easy to reproduce when creating a new prefix like this:

WINEPREFIX=~/newdir/ winecfg

Checking the strace logs, the "p11-kit" and "gnome-keyring" packages are involved - I suspect one of the config files of these packages (or related ones) makes wine load those .so
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 13 August 2013, 14:30 GMT
Still can't reproduce given the instructions.
Comment by Florian Pritz (bluewind) - Tuesday, 13 August 2013, 14:43 GMT
I can reproduce if I install gnome-keyring.

gnome-keyring contains /usr/share/p11-kit/modules/gnome-keyring.module which is most likely read by
lib32-p11-kit which then tries to load a 32bit module that doesn't exist.

Given winecfg starts just fine I don't consider this a real problem. Do you have an app that doesn't work without that module?
Comment by dx (dx) - Tuesday, 13 August 2013, 14:52 GMT
EDIT: well it looks like my message is a bit redundant, i didn't refresh the page for 10 minutes...

Doing strace gives me a 400mb file (i had to capture the wineserver too), so here's the part that seems relevant to me.

In particular, /usr/share/p11-kit/modules/gnome-keyring.module is telling it to load gnome-keyring-pkcs11.so.

gnome-keyring gets loaded by p11-kit, p11-kit gets loaded by gnutls, and I can't really see what happens before that

I forgot what other apps caused this issue (i'm not good at this "remembering" thing), but like i said, it happens every time when creating a new wine prefix.
   wine-gnome-keyring-pkcs11-str... (7 KiB)
Comment by dx (dx) - Tuesday, 13 August 2013, 15:01 GMT
Oh, I also got the error message when trying puttytray (not in a new wineprefix), but i'm not sure if it blocks any functionality, ssh seemed to work fine at least.
Comment by Pascal Ernster (hardfalcon) - Tuesday, 13 August 2013, 15:55 GMT
If someone flying a version of Outlook flying around, you might wanna check if this affects MS Outlook, as suggested in this thread:
https://bbs.archlinux.org/viewtopic.php?pid=1161002

On he other handside, the folks at CodeWeaver state that "This error tends to be harmless as far as Crossover's functions are concerned":
http://www.codeweavers.com/support/wiki/linux/faq/ubuntu_keyring

IMHO, software should execute properly without throwing errors, even if we don't immediately find a specific case where it actually breaks functionality. If you really feel *that* uncomfortable with adding a 2.2 MB dependency, at least add it as an optional dependency.
Comment by Florian Pritz (bluewind) - Tuesday, 13 August 2013, 19:39 GMT
Currently lib32-gnome-keyring isn't in our repos so I can't add an optdep. I also don't want to pull yet another package into multilib unless I know it is needed for certain applications to run properly.
Comment by Pascal Ernster (hardfalcon) - Tuesday, 13 August 2013, 19:57 GMT
Well, IMHO, wine isn't running properly, otherwise it wouldn't be throwing errors.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 14 August 2013, 11:47 GMT
wine will always throw errors. This bug report seems to be only addressing a cosmetic issue at this point. Is functionality at all at risk here?
Comment by Pascal Ernster (hardfalcon) - Wednesday, 14 August 2013, 13:50 GMT
Okay, I think I've found the culprit. The packages gnome-keyring, p11-kit (and of course their lib32 counterparts) violate the filesystem hierarchy standard by putting architecture dependend files, more specifically /usr/share/p11-kit/modules/*.module, into /usr/share instead of /usr/lib and /usr/lib32.

This leads to a situation where lib32-p11-kit tries to use the configu files of the 64bit versions of p11-kit and gnome-keyring.

This is not a bug in the wine package so this bug can be closed again. Thanks for your patience and sorry for not correctly debugging this issue in the first place.

Loading...