Bug 969923

Summary: [abrt] guake-0.4.4-9.fc17: guake:1144:get_fork_params:GError: No se pudo contactar con el servidor de configuración: Error de D-Bus: Message did not receive a reply (timeout by message bus)
Product: [Fedora] Fedora Reporter: pabratte
Component: guakeAssignee: Pierre-YvesChibon <pingou>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: admiller, pingou
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:6de872e292bd8463834761c2b33d08d5f976de26
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 08:47:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: environ
none
File: smolt_data none

Description pabratte 2013-06-03 04:07:48 UTC
Version-Release number of selected component:
guake-0.4.4-9.fc17

Additional info:
cmdline:        python /usr/bin/guake
executable:     /usr/bin/guake
kernel:         3.8.12-100.fc17.x86_64
uid:            500
ureports_counter: 1

Truncated backtrace:
guake:1144:get_fork_params:GError: No se pudo contactar con el servidor de configuración: Error de D-Bus: Message did not receive a reply (timeout by message bus)

Traceback (most recent call last):
  File "/usr/bin/guake", line 1447, in <module>
    if not main():
  File "/usr/bin/guake", line 1391, in main
    instance = Guake()
  File "/usr/bin/guake", line 631, in __init__
    self.add_tab()
  File "/usr/bin/guake", line 1225, in add_tab
    final_params = self.get_fork_params(default_params)
  File "/usr/bin/guake", line 1144, in get_fork_params
    shell = self.client.get_string(KEY('/general/default_shell'))
GError: No se pudo contactar con el servidor de configuración: Error de D-Bus: Message did not receive a reply (timeout by message bus)

Local variables in innermost frame:
default_params: {}
params: {}
self: Guake(path="/usr/share/guake/guake.glade")

Comment 1 pabratte 2013-06-03 04:07:53 UTC
Created attachment 756159 [details]
File: backtrace

Comment 2 pabratte 2013-06-03 04:07:57 UTC
Created attachment 756160 [details]
File: core_backtrace

Comment 3 pabratte 2013-06-03 04:08:00 UTC
Created attachment 756161 [details]
File: environ

Comment 4 pabratte 2013-06-03 04:08:05 UTC
Created attachment 756162 [details]
File: smolt_data

Comment 5 Fedora End Of Life 2013-07-04 02:35:47 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 6 Fedora End Of Life 2013-08-01 08:47:52 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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