Bug 1132491 - [abrt] guake: prefs.py:153:on_use_trayicon_toggled:GError: Configuration server couldn't be contacted: D-BUS error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked ...
Summary: [abrt] guake: prefs.py:153:on_use_trayicon_toggled:GError: Configuration serv...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: guake
Version: 20
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pierre-YvesChibon
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:422d172bd4ad7cc1c06ffe54ee2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-21 12:41 UTC by justsomebody
Modified: 2015-06-29 22:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:10:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (958 bytes, text/plain)
2014-08-21 12:41 UTC, justsomebody
no flags Details
File: environ (1.48 KB, text/plain)
2014-08-21 12:41 UTC, justsomebody
no flags Details

Description justsomebody 2014-08-21 12:41:27 UTC
Description of problem:
1. login
2. guake autostart produced notification, that F12 hotkey for visibility couldn't be assigned, although I've been using it for month now with a different hotkey
3. made guake window visible by clicking on tray icon
4. tried to close it - crash

Version-Release number of selected component:
guake-0.4.4-11.fc20

Additional info:
reporter:       libreport-2.2.3
cmdline:        python /usr/bin/guake
executable:     /usr/bin/guake
kernel:         3.15.8-200.fc20.i686+PAE
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
prefs.py:153:on_use_trayicon_toggled:GError: Configuration server couldn't be contacted: D-BUS error: 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 "/usr/lib/python2.7/site-packages/guake/prefs.py", line 153, in on_use_trayicon_toggled
    self.client.set_bool(KEY('/general/use_trayicon'), chk.get_active())
GError: Configuration server couldn't be contacted: D-BUS error: 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:
self: <guake.prefs.PrefsCallbacks object at 0x8b3ec4c>
chk: <gtk.CheckButton object at 0x8c3cbbc (GtkCheckButton at 0x8b75178)>

Comment 1 justsomebody 2014-08-21 12:41:29 UTC
Created attachment 929199 [details]
File: backtrace

Comment 2 justsomebody 2014-08-21 12:41:30 UTC
Created attachment 929200 [details]
File: environ

Comment 3 justsomebody 2014-08-21 12:45:38 UTC
in fact all of my settings were changed back to default...

Comment 4 Fedora Admin XMLRPC Client 2015-03-24 15:23:08 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Fedora Admin XMLRPC Client 2015-03-24 15:23:30 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Fedora End Of Life 2015-05-29 12:41:44 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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 7 Fedora End Of Life 2015-06-29 22:10:38 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


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