Bug 1039227

Summary: [abrt] istanbul-0.2.2-19.fc19: gconf_client.py:27:__init__:GError: Client failed to connect to the D-BUS daemon:
Product: [Fedora] Fedora Reporter: Chuck Lasher <chuck.lasher>
Component: istanbulAssignee: Jef Spaleta <jspaleta>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: jspaleta
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/196fe6e6af3cc5c2c054a1b74cd575c584875b15
Whiteboard: abrt_hash:584a98ab2dc5aad84290c0d96da25a52298b67ad
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:34:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description Chuck Lasher 2013-12-07 04:41:36 UTC
Description of problem:
plex media server running as normal background service (under systemctl control).
accessed via standard web interface... 

CRASH

Version-Release number of selected component:
istanbul-0.2.2-19.fc19

Additional info:
reporter:       libreport-2.1.9
cmdline:        /usr/bin/python /bin/istanbul
executable:     /bin/istanbul
kernel:         3.11.9-200.fc19.x86_64
runlevel:       3 5
type:           Python
uid:            0

Truncated backtrace:
gconf_client.py:27:__init__:GError: Client failed to connect to the D-BUS daemon:
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.

Traceback (most recent call last):
  File "/bin/istanbul", line 30, in <module>
    from istanbul.main import main
  File "/usr/lib/python2.7/site-packages/istanbul/main/main.py", line 37, in <module>
    from istanbul.main.tray_icon import TrayIcon
  File "/usr/lib/python2.7/site-packages/istanbul/main/tray_icon.py", line 31, in <module>
    class TrayIcon:
  File "/usr/lib/python2.7/site-packages/istanbul/main/tray_icon.py", line 35, in TrayIcon
    popup_menu = TrayPopupMenu()
  File "/usr/lib/python2.7/site-packages/istanbul/main/tray_popup.py", line 38, in __init__
    self._setup_popup_menu()
  File "/usr/lib/python2.7/site-packages/istanbul/main/tray_popup.py", line 47, in _setup_popup_menu
    self._setup_record_3d()
  File "/usr/lib/python2.7/site-packages/istanbul/main/tray_popup.py", line 102, in _setup_record_3d
    new_widget = Widget(record_3d)
  File "/usr/lib/python2.7/site-packages/istanbul/main/constants.py", line 36, in __init__
    self.associate_preference()
  File "/usr/lib/python2.7/site-packages/istanbul/main/constants.py", line 39, in associate_preference
    preferences = Preferences()
  File "/usr/lib/python2.7/site-packages/istanbul/main/preferences.py", line 134, in __init__
    new_pref = Preference(setting, setting_v[0], setting_v[1], setting_v[2])
  File "/usr/lib/python2.7/site-packages/istanbul/main/preferences.py", line 38, in __init__
    self.gconf = IstanbulGConf()
  File "/usr/lib/python2.7/site-packages/istanbul/main/gconf_client.py", line 78, in __init__
    GConfClient.__init__(self, '/apps/istanbul')
  File "/usr/lib/python2.7/site-packages/istanbul/main/gconf_client.py", line 27, in __init__
    self.client.add_dir (directory, gconf.CLIENT_PRELOAD_NONE)
GError: Client failed to connect to the D-BUS daemon:
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.

Local variables in innermost frame:
directory: '/apps/istanbul'
self: <istanbul.main.gconf_client.IstanbulGConf object at 0x1316090>

Comment 1 Chuck Lasher 2013-12-07 04:41:41 UTC
Created attachment 833818 [details]
File: backtrace

Comment 2 Chuck Lasher 2013-12-07 04:41:43 UTC
Created attachment 833819 [details]
File: environ

Comment 3 Fedora End Of Life 2015-01-09 20:48:34 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-17 19:34:05 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.