#18 xenmanager will not run in ubuntu 11.04 x64

closed-invalid
nobody
None
5
2011-09-15
2011-09-15
Anonymous
No

following the instructions in ubuntu 11.04 x64 and trying to run ./openxenmanager from terminal the xen manager window opens for s split second closes then i recieve the following.

(window.py:1956): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: 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.

(window.py:1956): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: 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.

(window.py:1956): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: 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.
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Traceback (most recent call last):
File "window.py", line 1584, in <module>
gtk.main()
KeyboardInterrupt
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 42, in apport_excepthook
try:
TypeError: signal_handler() takes exactly 1 argument (3 given)

Original exception was:
Traceback (most recent call last):
File "window.py", line 1584, in <module>
gtk.main()
KeyboardInterrupt
Exiting...

Discussion

  • chengsun
    chengsun
    2011-09-15

    Confirmed; this is caused when you use OXM in a su environment. This is not a bug of OXM. See this bug:
    https://bugs.freedesktop.org/show_bug.cgi?id=17970

    Marking as invalid.

    If you are trying to run OXM as root, (note that this is a bad idea, OXM does not require root privileges to run), (gk)sudo seems to work OK for this purpose.

     
  • chengsun
    chengsun
    2011-09-15

    • status: open --> closed-invalid