Hide Forgot
libreport version: 2.0.7 abrt_version: 2.0.6 cmdline: guake -OO /usr/lib/guake/guake.py executable: /usr/lib/guake/guake.py kernel: 3.1.1-2.fc16.i686 reason: guake.py:447:configure_terminal:GError: Configuration server couldn't be contacted: D-BUS error: Message did not receive a reply (timeout by message bus) reported_to: file: bugzillalog time: Friday 25 November 2011 05:21:59 AM IST uid: 1000 username: en smolt_data: Text file, 2959 bytes backtrace: :guake.py:447:configure_terminal:GError: Configuration server couldn't be contacted: D-BUS error: Message did not receive a reply (timeout by message bus) : :Traceback (most recent call last): : File "/usr/lib/guake/guake.py", line 1353, in <module> : if not main(): : File "/usr/lib/guake/guake.py", line 1296, in main : instance = Guake() : File "/usr/lib/guake/guake.py", line 620, in __init__ : self.add_tab() : File "/usr/lib/guake/guake.py", line 1121, in add_tab : box = GuakeTerminalBox() : File "/usr/lib/guake/guake.py", line 498, in __init__ : self.terminal = GuakeTerminal() : File "/usr/lib/guake/guake.py", line 438, in __init__ : self.configure_terminal() : File "/usr/lib/guake/guake.py", line 447, in configure_terminal : word_chars = client.get_string(KEY('/general/word_chars')) :GError: Configuration server couldn't be contacted: D-BUS error: Message did not receive a reply (timeout by message bus) : :Local variables in innermost frame: :self: <GuakeTerminal object at 0x91fddc4 (VteTerminal at 0x926d200)> :client: <gconf.Client object at 0x91fdcac (GConfClient at 0x9120590)> bugzillalog: :abrt_version: 2.0.6 :bugzillalog: :cmdline: guake -OO /usr/lib/guake/guake.py :event_log: 2011-11-28-20:27:37> Smolt profile successfully saved :executable: /usr/lib/guake/guake.py :kernel: 3.1.1-2.fc16.i686 :reason: guake.py:447:configure_terminal:GError: Configuration server couldn't be contacted: D-BUS error: Message did not receive a reply (timeout by message bus) :time: Friday 25 November 2011 05:21:59 AM IST :uid: 1000 :username: en : :smolt_data: Text file, 2959 bytes : :backtrace: ::guake.py:447:configure_terminal:GError: Configuration server couldn't be contacted: D-BUS error: Message did not receive a reply (timeout by message bus) :: ::Traceback (most recent call last): :: File "/usr/lib/guake/guake.py", line 1353, in <module> :: if not main(): :: File "/usr/lib/guake/guake.py", line 1296, in main :: instance = Guake() :: File "/usr/lib/guake/guake.py", line 620, in __init__ :: self.add_tab() :: File "/usr/lib/guake/guake.py", line 1121, in add_tab :: box = GuakeTerminalBox() :: File "/usr/lib/guake/guake.py", line 498, in __init__ :: self.terminal = GuakeTerminal() :: File "/usr/lib/guake/guake.py", line 438, in __init__ :: self.configure_terminal() :: File "/usr/lib/guake/guake.py", line 447, in configure_terminal :: word_chars = client.get_string(KEY('/general/word_chars')) ::GError: Configuration server couldn't be contacted: D-BUS error: Message did not receive a reply (timeout by message bus) :: ::Local variables in innermost frame: ::self: <GuakeTerminal object at 0x91fddc4 (VteTerminal at 0x926d200)> ::client: <gconf.Client object at 0x91fdcac (GConfClient at 0x9120590)> : :END: : event_log: :2011-11-28-20:27:37> Smolt profile successfully saved :2011-11-28-20:29:12> The report was appended to bugzillalog
Created attachment 537499 [details] File: smolt_data
Can you reproduce this bug ? And give me information on how to do so ?
(In reply to comment #2) > Can you reproduce this bug ? And give me information on how to do so ? Sorry, Haven't had the error again and i've done a new install... i used to switch between old kernels(starting from the default one installed in F16) 3.1.0.7 i think, and this would happen the bug reporting tool showed this error after login , Just thought would be good if i reported this, just happened twice... I'll report if i find this again, could you suggest any ways i could give more info you asked ? I'm new to Linux even after a year using it :)
Ok, thanks for the info, I'm going to close this bug for the moment but do re-open it if this happen again. I have the feeling that this was some d-bus weirdness which seem to be pretty specific to what you were doing. Again, re-open it if you can reproduce it.