Bug 5680 - Virt-manager: Ошибка запуска менеджера виртуальных машин: Служба D-BUS не запущена
: Virt-manager: Ошибка запуска менеджера виртуальных машин: Служба D-BUS не зап...
Status: RESOLVED NOTABUG
Product: Desktop Bugs
Classification: ROSA Desktop
Component: -Enter Bugs Here-
: Fresh
: All Linux
: Normal normal
: ---
Assigned To: Desktop Triage Team
: Desktop Triage Team
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-06-02 05:03 MSD by Alexander Petryakov
Modified: 2015-10-27 12:45 MSK (History)
2 users (show)

See Also:
RPM Package: virt-manager-0.9.4-2.src.rpm
ISO-related:
Bad POT generating:
Upstream:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Petryakov 2015-06-02 05:03:20 MSD
Description of problem:

GUI Error:
Ошибка запуска менеджера виртуальных машин: Служба D-BUS не запущена


Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-manager.py", line 386, in <module>
    main()
  File "/usr/share/virt-manager/virt-manager.py", line 321, in main
    config = virtManager.config.vmmConfig(appname, appversion, ui_dir)
  File "/usr/share/virt-manager/virtManager/config.py", line 98, in __init__
    self.conf.add_dir(self.conf_dir, gconf.CLIENT_PRELOAD_NONE)
GError: Служба D-BUS не запущена

ConsoleError:
[root@ThinkPad-X61s ~]# virt-manager

(virt-manager:20367): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.



Steps to Reproduce:
1. # urpmi virt-manager
2. > sudo -E bash
3. # virt-manager


Error during install
(gconftool-2:20220): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/bin/dbus-launch terminated abnormally with the following error: No protocol specified
Autolaunch error: X11 initialization failed.
Comment 1 Eugene Shatokhin 2015-06-02 16:34:35 MSD
I do not use virt-manager myself, but is is needed to run it as root? 

Some applications, indeed, do not find DBUS when launched as root.
Comment 2 Alexander Petryakov 2015-06-05 17:07:54 MSD
Yes, I am run virt-manager from root
Comment 3 Denis Silakov 2015-10-27 12:45:14 MSK
This is a known specific of runnning programs after switching to the root user (https://bugzilla.redhat.com/show_bug.cgi?id=890576). The preferred way to become root for such cases is to use "su -". If you still see the dbus error after this, you cat run the following command additionally:

# dbus-uuidgen > /var/lib/dbus/machine-id