Bug 1399809

Summary:	No shutdown option under System menu when logged in using smartcard
Product:	Red Hat Enterprise Linux 6	Reporter:	Roshni <rpattath>
Component:	dbus	Assignee:	David King <dking>
Status:	CLOSED WORKSFORME	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.9	CC:	rpattath, rstrode
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-30 20:51:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Roshni 2016-11-29 19:12:16 UTC

Description of problem:
No shutdown option under System menu when logged in using smartcard

Version-Release number of selected component (if applicable):
gdm-2.30.4-67.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Login to the desktop using smartcard enrolled with a Kerberos user
2.
3.

Actual results:
System menu does not have a shutdown option

Expected results:
System menu should have a shutdown option

Additional info:
/var/log messages

Nov 29 14:09:40 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:40 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:41 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:41 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:41 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:41 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:41 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:42 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:42 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:42 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:42 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:42 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:42 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:42 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:42 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:42 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:42 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:42 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:43 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:44 dhcp129-152 pcscd: utils.c:123:StatSynchronize() Can't open /var/run/pcscd.events/event.14701.16981463: Bad file descriptor
Nov 29 14:09:45 dhcp129-152 gnome-session[14726]: devkit-power-gobject-WARNING: Couldn't connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:45 dhcp129-152 gnome-session[14726]: WARNING: Could not connect to ConsoleKit: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:45 dhcp129-152 gnome-session[14726]: WARNING: Could not connect to ConsoleKit: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 seahorse-daemon[14820]: DNS-SD initialization failed: An unexpected D-Bus error occured
Nov 29 14:09:46 dhcp129-152 seahorse-daemon[14820]: init gpgme version 1.1.8
Nov 29 14:09:46 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:46 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:46 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:46 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:46 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:46 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: bluetooth-util.c: Failed to get D-Bus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: main.c: Module load failed.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14850]: main.c: Failed to initialize daemon.
Nov 29 14:09:46 dhcp129-152 pulseaudio[14848]: main.c: Daemon startup failed.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: bluetooth-util.c: Failed to get D-Bus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: main.c: Module load failed.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14895]: main.c: Failed to initialize daemon.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 abrtd: Directory 'ccpp-2016-11-29-14:09:47-14858' creation detected
Nov 29 14:09:47 dhcp129-152 abrtd: Directory 'ccpp-2016-11-29-14:09:47-14866' creation detected
Nov 29 14:09:47 dhcp129-152 abrt[14900]: Saved core dump of pid 14858 (/usr/libexec/gdu-notification-daemon) to /var/spool/abrt/ccpp-2016-11-29-14:09:47-14858 (2019328 bytes)
Nov 29 14:09:47 dhcp129-152 abrt[14901]: Saved core dump of pid 14866 (/usr/libexec/polkit-gnome-authentication-agent-1) to /var/spool/abrt/ccpp-2016-11-29-14:09:47-14866 (1744896 bytes)
Nov 29 14:09:47 dhcp129-152 abrt[14904]: Saved core dump of pid 14865 (/usr/bin/gpk-update-icon) to /var/spool/abrt/ccpp-2016-11-29-14:09:47-14865 (2424832 bytes)
Nov 29 14:09:47 dhcp129-152 gnome-session[14726]: WARNING: Could not connect to ConsoleKit: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 gnome-session[14726]: WARNING: Could not connect to ConsoleKit: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:47 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:47 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:47 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:47 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:47 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:47 dhcp129-152 pcscd: ifdhandler.c:1091:IFDHTransmitToICC() usb:076b/3021:libhal:/org/freedesktop/Hal/devices/usb_device_76b_3021_noserial_if0 (lun: 0)
Nov 29 14:09:47 dhcp129-152 abrtd: Directory 'ccpp-2016-11-29-14:09:47-14865' creation detected
Nov 29 14:09:48 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[14915]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[14915]: bluetooth-util.c: Failed to get D-Bus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[14915]: module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.
Nov 29 14:09:48 dhcp129-152 pulseaudio[14915]: main.c: Module load failed.
Nov 29 14:09:48 dhcp129-152 pulseaudio[14915]: main.c: Failed to initialize daemon.
Nov 29 14:09:48 dhcp129-152 pulseaudio[14911]: main.c: Daemon startup failed.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: bluetooth-util.c: Failed to get D-Bus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 14:09:48 dhcp129-152 pulseaudio[15153]: module.c: Failed to load module "module-bluetooth-discover" (argument: ""): initialization failed.

[root@dhcp129-152 ~]# tail -f /var/log/gdm/\:0-greeter.log

Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-SmY8vd2SCa: Connection refused)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-SmY8vd2SCa: Connection refused)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-SmY8vd2SCa: Connection refused)
^C

Comment 4 Roshni 2016-11-30 17:48:02 UTC

This issue is inconsistent, I was not able to reproduce it to provide the requested information. Please close the bug if nothing can be diagnosed from the log messages I provided, I will re-open the bug if I see this issue again.