Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Gdk-Message: Unable to load exchange from the cursor theme

Discussion in 'Linux' started by sotolick, May 3, 2018.

  1. sotolick

    sotolick

    Joined:
    Mar 1, 2018
    Posts:
    1
    Hi
    today i installed new version of Unity, Unity-2018.2.0b2 ,and when i tried to start it after installation,i received this in terminal,and unity splash screen showed,but nothing happened.



    I dont know what to do.Any solutions?

    //EDIT
    I let it be for few hours and splash screen always showing same...please help
     
    Last edited: May 3, 2018
  2. Tak

    Tak

    Joined:
    Mar 8, 2010
    Posts:
    1,001
    Please post your editor log from a session like this. (~/.config/unity3d/Editor.log)
     
  3. Ironhide75

    Ironhide75

    Joined:
    Jun 28, 2015
    Posts:
    2
    I have this same issue and I have to kill -9 the process to end it and no Editor.log is created. Seems to only be an issue with wayland.
     
  4. DjLegolas

    DjLegolas

    Joined:
    Jul 29, 2017
    Posts:
    1
    I got this error as well, and the reason is with a load of a file:

    Filename: /home/builduser/buildslave/unity/build/Editor/Platform/Interface/NativeWebViewWindow.cpp Line: 51)

    Error loading file:///%2Fhome%2Fido%2F.local%2Fshare%2Funity3d%2FPackages%2Fnode_modules%2Funity-editor-home%2Fdist/index.html#/loginLegacy
     

    Attached Files:

  5. JManek

    JManek

    Joined:
    Jul 22, 2014
    Posts:
    1
    Found a workaround that requires using Xorg

    in
    /etc/gdm3/custom.conf


    uncomment the line
    #WaylandEnable=false
     
  6. Tak

    Tak

    Joined:
    Mar 8, 2010
    Posts:
    1,001
    The Unity editor doesn't support Wayland yet.
    It should Just Work using XWayland, but you can force it by setting GDK_BACKEND=x11 in the environment where you launch Unity.
     
  7. pbowmar

    pbowmar

    Joined:
    Jun 21, 2018
    Posts:
    2
    Just FYI for anyone stumbling on this, setting the GDK_BACKEND=x11 resolved this same issue for me. I'm on OpenSuse 42.3 but should likely work for Centos 7.5 and others.