Bug 626248 - [abrt] guake-0.4.2-1.fc13: guake.py:649:__init__:GError: Message did not receive a reply (timeout by message bus)
Summary: [abrt] guake-0.4.2-1.fc13: guake.py:649:__init__:GError: Message did not rece...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: guake
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Pierre-YvesChibon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:63fc752c
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-22 23:56 UTC by mario
Modified: 2011-05-18 11:36 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-05-18 11:36:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.18 KB, text/plain)
2010-08-22 23:56 UTC, mario
no flags Details

Description mario 2010-08-22 23:56:05 UTC
abrt version: 1.1.13
architecture: i686
cmdline: guake -OO /usr/lib/guake/guake.py
comment: Solo me pasa al iniciar el sistema 
component: guake
executable: /usr/lib/guake/guake.py
kernel: 2.6.33.6-147.2.4.fc13.i686
package: guake-0.4.2-1.fc13
reason: guake.py:649:__init__:GError: Message did not receive a reply (timeout by message bus)
release: Fedora release 13 (Goddard)
time: 1282405857
uid: 500

backtrace
-----
guake.py:649:__init__:GError: 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 649, in __init__
    notification.show()
GError: Message did not receive a reply (timeout by message bus)

Local variables in innermost frame:
keyval: 65481
colormap: <gtk.gdk.Colormap object at 0x93fd1e4 (GdkColormap at 0x9301108)>
img: '/usr/share/pixmaps/guake/guake-tray.png'
evtbox: <gtk.EventBox object at 0x93f7a54 (GtkEventBox at 0x9300cf0)>
notification: <pynotify.Notification object at 0x93fd914 (NotifyNotification at 0x94b7f00)>
screen: <gtk.gdk.ScreenX11 object at 0x93fd1bc (GdkScreenX11 at 0x92fe0f0)>
mask: <flags 0 of type GdkModifierType>
label: 'F12'
ipath: '/usr/share/pixmaps/guake/add_tab.png'
hide_context_menu: <function hide_context_menu at 0x93fae64>
key: 'F12'
destroy: <function destroy at 0x93faed4>
filename: '/usr/share/pixmaps/guake/guake-notification.png'
self: Guake(path="/usr/share/guake/guake.glade")
double_click: <function double_click at 0x93fae2c>

How to reproduce
-----
1.al iniciar el sistema junto co Compiz fusion icon y no podia iniciar la aplicacin
2.
3.

Comment 1 mario 2010-08-22 23:56:07 UTC
Created an attachment (id=440274)
File: backtrace

Comment 2 Pierre-YvesChibon 2010-08-23 05:07:19 UTC
Could you please comment in english on how you produced this bug ?
Also, are you able to reproduce it ?

Comment 3 mario 2010-08-23 16:37:14 UTC
after reboot with co Compiz fusion icon and could not start
implemen the aplication guake

Comment 4 Pierre-YvesChibon 2010-08-23 16:45:07 UTC
You can reproduce it all the time ?
Does it also bug if compiz is not activated ?

Comment 5 mario 2010-08-23 17:08:38 UTC
occasionally happens, only with compiz fusion icon started very late with the system.

But fix it by uninstalling compiz fusion icon and returning to "Desktop Effects"

Comment 6 Pierre-YvesChibon 2010-09-21 18:21:37 UTC
Shall we close this bug ?

Comment 7 Michal Klich 2010-09-27 08:00:43 UTC
Package: guake-0.4.2-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Start guake
2.
3.


Comment
-----
Start guake, happens everytime.

Comment 8 Pierre-YvesChibon 2010-09-27 08:13:26 UTC
(In reply to comment #7)

> Start guake, happens everytime.

Does it work when compiz is off ?

Comment 9 Michal Klich 2010-10-19 10:57:13 UTC
It looks like it is resolved as it does not crash anymore. I do have "Desktop Effects" enabled.

Comment 10 Pierre-YvesChibon 2010-11-06 16:05:18 UTC
You seem to agree that the problem is resolved. I am closing this bug, please reopen it if the problem occurs again.

Thanks!

Comment 11 frogge 2010-11-29 04:41:21 UTC
Fedora 14, Xfce4, guake-0.4.2-2
When starting guake, "unable to connect to server" happens every time.

guake.py:649:__init__:GError: Unable to connect to server

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 649, in __init__
    notification.show()
GError: Unable to connect to server

Comment 12 Pierre-YvesChibon 2010-11-29 06:07:00 UTC
Do you have libnotify installed or any desktop effects ?

Comment 13 frogge 2010-11-29 08:34:28 UTC
Hello, I have libnotify installed, no desktop effects.

$ rpm -q libnotify
libnotify-0.5.1-1.fc14.i686

Comment 14 Pierre-YvesChibon 2010-11-29 21:53:52 UTC
I am reopening this bug as it seems unclear to whether it exists or not.

Comment 15 Jindřich Skácel 2010-12-11 21:24:28 UTC
Hi,

I found something on the web - https://bbs.archlinux.org/viewtopic.php?pid=856702#p856702

Comment 16 al morris 2011-01-25 19:33:26 UTC
Package: guake-0.4.2-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. new install
2. type guake in open terminal
3. feed back message in terminal


Comment
-----
[al@greenfan ~]$ guake -p
Traceback (most recent call last):
  File "/usr/lib64/guake/guake.py", line 1353, in <module>
    if not main():
  File "/usr/lib64/guake/guake.py", line 1296, in main
    instance = Guake()
  File "/usr/lib64/guake/guake.py", line 649, in __init__
    notification.show()
glib.GError: Unable to connect to server
[al@greenfan ~]$

Comment 17 al morris 2011-01-25 19:56:04 UTC
Read the
https://bbs.archlinux.org/viewtopic.php?pid=856702#p856702
and
http://us.generation-nt.com/answer/bug-588272-xfce4-notifyd-does-not-work-after-upgrade-libnotify-0-5-help-199275771.html

I am running Fedora 14 so got rid of:
xfce4-notifyd-0.1.0-3.fc12.x86_64
since is hasn't updated to 14 yet.

Now guake is working but don't yet know what won't work as far as notifications.
It would be nice to be able to fix the guake package but that is a little above my current level.

Thanks,
al

Comment 18 al morris 2011-01-25 20:27:44 UTC
Brain very slow...more thinking...

Guake package works now with libnotify-0.5.1-1.fc14.x86_64.

System is Fedora 14 but no xfce4-notifyd.fc14 available.
Removing Fedora 12 xfce4-notifyd-0.1.0-3.fc12.x86_64 package made things work.

Probably something needs updating in xfce4-notifyd.
It is a Fedora 12 package after all.

thanks again,
al

Comment 19 isi.floss 2011-02-21 21:57:07 UTC
Problem persists for me with both xfce4-notifyd installed and uninstalled.

Comment 20 isi.floss 2011-03-01 20:50:37 UTC
works for me now. (installed updates regularly, nothing else)

Comment 21 Jindřich Skácel 2011-03-01 22:11:22 UTC
yep, works for me too

Comment 22 Jeff Layton 2011-03-25 00:06:10 UTC
Package: guake-0.4.2-3.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
Start guake on login.

Comment 23 Reinout van Schouwen 2011-04-02 09:33:31 UTC
Package: guake-0.4.2-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Guake was started as part of the gnome session
2.
3.

Comment 24 Tim Cuthbertson 2011-04-26 03:21:58 UTC
Package: guake-0.4.2-3.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1. configure `guake` to run on each session with gnome-session-properties
2. log in
3. abrt reports that guake failed to load


Comment
-----
If guake is started *after* the session is fully logged in and everything loaded, it works just fine. So maybe there's some dbus service it needs to run after?

Comment 25 Tim Cuthbertson 2011-05-18 11:29:42 UTC
I'm not sure when exactly it was, but a recent update seems to have fixed this issue for me (on FC15)

Comment 26 Pierre-YvesChibon 2011-05-18 11:36:04 UTC
Same for me, I cannot reproduce the bug anymore.

I will therefore close this bug as we are at least 3 who had the bug and don't have it anymore.

If you still face this bug on a up-to-date Fedora, please feel free to reopen this bug.


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