Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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.