Bug 783093 - Use of gnutls_global_init causes gnome-keyring to print WARNING: no socket to connect to
Summary: Use of gnutls_global_init causes gnome-keyring to print WARNING: no socket to...
Keywords:
Status: CLOSED DUPLICATE of bug 782725
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-keyring
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-19 10:27 UTC by Daniel Berrangé
Modified: 2015-03-03 23:04 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-01-19 10:42:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Daniel Berrangé 2012-01-19 10:27:11 UTC
Description of problem:
If you have the gnome-keyring package installed (which is compulsory on any GNOME based Fedora install), and you run 'gnutls_global_init' in a non-desktop session,  gnome-keyring will print

 WARNING: no socket to connect to

to the console very time. This is a useless error message because it doesn't tell the user what socket is missing, so they have no way to find out what needs fixing, other than to attach GDB to the process and single step till the find the source of the warning.  Second, it should not print such stuff to the console in the first place, since this is an entirely expected scenario when running GNUTLS apps outside a desktop session

This issue is preventing builds of libvirt in Fedora because we're getting this error message spewed out in the middle of places where it is not expected to be, breaking the tests.

This bogus warning should just be removed.

Version-Release number of selected component (if applicable):
gnutls-2.12.14-1.fc16.x86_64
gnome-keyring-3.2.1-2.fc16.x86_64
pkcs11-helper-1.09-1.fc16.x86_6

How reproducible:
Always, if GNOME_KEYRING_CONTROLL env variable is not set (ie on a text / ssh console)

Steps to Reproduce:
1. Install gnutls-2.12.14
2. $ unset GNOME_KEYRING_CONTROL
3. $ virsh -c test:///default list
  
Actual results:
WARNING: no socket to connect to
 Id Name                 State
----------------------------------
  1 test                 running



Expected results:
 Id Name                 State
----------------------------------
  1 test                 running



Additional info:



(gdb) bt
#0  write () at ../sysdeps/unix/syscall-template.S:82
#1  0x0000003631a76f63 in _IO_new_file_write (f=0x3631db0160, data=0x7fffffffb0a0, n=33) at fileops.c:1289
#2  0x0000003631a76e2a in new_do_write (fp=0x3631db0160, data=0x7fffffffb0a0 "WARNING: no socket to connect to\n", to_do=33) at fileops.c:543
#3  0x0000003631a778de in _IO_new_file_xsputn (n=33, data=<optimized out>, f=0x3631db0160) at fileops.c:1383
#4  _IO_new_file_xsputn (f=0x3631db0160, data=<optimized out>, n=33) at fileops.c:1305
#5  0x0000003631a4c236 in buffered_vfprintf (s=0x3631db0160, format=<optimized out>, args=<optimized out>) at vfprintf.c:2228
#6  0x0000003631a4763e in _IO_vfprintf_internal (s=0x3631db0160, format=0x7ffff1131f6f "%s\n", ap=0x7fffffffd818) at vfprintf.c:1256
#7  0x0000003631b0496b in ___fprintf_chk (fp=0x3631db0160, flag=1, format=<optimized out>) at fprintf_chk.c:37
#8  0x00007ffff112fe32 in do_log (pref=<optimized out>, msg=0x7ffff1131da4 "no socket to connect to", va=0x7fffffffdd38) at gkm-rpc-util.c:45
#9  0x00007ffff112ff06 in gkm_rpc_warn (msg=<optimized out>) at gkm-rpc-util.c:53
#10 0x00007ffff1128d71 in call_connect (cs=0x6781c0) at gkm-rpc-module.c:232
#11 call_lookup (ret=0x7fffffffded8) at gkm-rpc-module.c:332
#12 0x00007ffff112922e in rpc_C_Initialize (init_args=<optimized out>) at gkm-rpc-module.c:1201
#13 0x0000003642a04b97 in initialize_module_unlocked_reentrant (mod=0x677af0) at modules.c:522
#14 initialize_module_unlocked_reentrant (mod=0x677af0) at modules.c:503
#15 0x0000003642a05085 in _p11_kit_initialize_registered_unlocked_reentrant () at modules.c:693
#16 0x0000003642a0574d in p11_kit_initialize_registered () at modules.c:736
#17 0x0000003643648495 in gnutls_pkcs11_init () from /usr/lib64/libgnutls.so.26
#18 0x0000003643632032 in gnutls_global_init () from /usr/lib64/libgnutls.so.26
#19 0x00007ffff7b341c1 in virNetTLSInit () at ../../src/rpc/virnettlscontext.c:1432
#20 0x00007ffff7aaaa32 in virInitialize () at ../../src/libvirt.c:412
#21 0x000000000040a50d in main (argc=4, argv=0x7fffffffe528) at ../../tools/virsh.c:18663

Comment 1 Tomáš Bžatek 2012-01-19 10:42:21 UTC

*** This bug has been marked as a duplicate of bug 782725 ***


Note You need to log in before you can comment on or make changes to this bug.