Help with X-tile in Fedora 26 LXDE 64 Bits

Home Forums x tile Help with X-tile in Fedora 26 LXDE 64 Bits

This topic contains 3 replies, has 2 voices, and was last updated by  giuspen 2 weeks, 5 days ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #124426

    RADEL
    Member

    Hello everyone, please kindly help me with a problem with x-tile in Fedora Linux 26 LXDE 64 bits. Install x-tile through the Terminal with the command “dnf -y install x-tile”, but when accessed by the icon through the menu in the shortcut does not launch x-tile, I have also tried to access x-tile by means of the terminal with the command “x-tile” which leaves the following message:

    Traceback (most recent call last):
    File “/bin/x-tile”, line 40, in <module>
    gconf_client.add_dir(cons.GCONF_DIR, gconf.CLIENT_PRELOAD_NONE)
    glib.GError: 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.

    Please, I reiterate my request to be able to solve this problem.

    Thank you for your attentions and prompt responses.

    #124431

    giuspen
    Moderator

    Hi, it seems that the package “gconf” is missing. Try to install “gconf” or if the package is missing search for “gconf-editor”

    #124500

    RADEL
    Member

    Thanks for your reply, I inform you that you can not install the “gconf” but if you installed the “gconf-editor”. But still installed the “gconf-editor” I can not launch the “x-tile” program, either through the Fedora LXDE 26 64 Bit or through the Fedora Accessories menu.

    Please kindly help me with this persisting problem.

    Traceback (most recent call last):
    File “/ bin / x-tile”, line 40, in <module>
    gconf_client.add_dir (cons.GCONF_DIR, gconf.CLIENT_PRELOAD_NONE)
    glib.GError: 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.
    [root @ Radel bin] # x-tile
    Traceback (most recent call last):
    File “/ bin / x-tile”, line 40, in <module>
    gconf_client.add_dir (cons.GCONF_DIR, gconf.CLIENT_PRELOAD_NONE)
    glib.GError: 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.

    #124630

    giuspen
    Moderator

    Hi @radel, it looks like gconf is not supported anymore (obsolete), I need to get rid of it

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.