remote office – xinit for the correct startup of awesome wm in Manjaro (xrdp)

Connecting to Manjaro 18.00 with the xrdp configuration, running on a virtual machine using the remote desktop connection leads to an incomplete start (without taskbar) of the awesome WM.

Go great via

exec / usr / bin / awesome >> ~ / .cache / awesome / stdout 2 >> ~ / .cache / awesome / stderr

shows the following:

2019-02-25 15:13:23 W: awesome: xerror: 1038: error X: request = CreateWindow (major 1, minor 0), error = BadMatch (8)
2019-02-25 15:13:23 W: awesome: xerror: 1038: error X: request = CreateGC (major 55, minor 0), error = BadDrawable (9)
2019-02-25 15:13:23 W: awesome: xerror: 1038: error X: request = CreateWindow (major 1, minor 0), error = BadMatch (8)
2019-02-25 15:13:23 W: awesome: xerror: 1038: error X: request = CreateWindow (major 1, minor 0), error = BadMatch (8)
2019-02-25 15:13:23 W: awesome: xerror: 1038: error X: request = CopyArea (major 62, minor 0), error = BadDrawable (9)
2019-02-25 15:13:23 W: awesome: xerror: 1038: error X: request = CopyArea (major 62, minor 0), error = BadDrawable (9)
2019-02-25 15:13:23 W: awesome: xerror: 1038: error X: request = CopyArea (major 62, minor 0), error = BadDrawable (9)

(light-locker: 3097): Gtk-WARNING **: 15: 13: 23.158: Theme analysis error: gtk.css: 12: 80: & gt; gtkalpha & # 39; is not a valid color name.

(light-locker: 3097): Gtk-WARNING **: 15: 13: 23.158: Theme analysis error: gtk.css: 15: 80: & gt; gtkalpha & # 39; is not a valid color name.

** (light locker: 3097): ERROR **: 15: 13: 23.230: The XDG_SESSION_PATH environment variable is not set. Is LightDM running?

(blueman-applet: 3121): Gtk-WARNING **: 15: 13: 23.302: Theme analysis error: gtk.css: 12: 80: & gt; ktkalpha & # 39; is not a valid color name.

(blueman-applet: 3121): Gtk-WARNING **: 15: 13: 23.302: Theme analysis error: gtk.css: 15: 80: & gt; ktkalpha & # 39; is not a valid color name.
Traceback (most recent call last):
"/Usr/lib/python3.7/site-packages/dbus/bus.py" file, line 175, in activate_name_owner
return self.get_name_owner (bus name)
"/Usr/lib/python3.7/site-packages/dbus/bus.py" file, line 361, in get_name_owner
& # 39; s & # 39 ;, (bus_name,), ** keywords)
"/Usr/lib/python3.7/site-packages/dbus/connection.py" file, line 651, in call_blocking
message, waiting time)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Can not get the owner of the name "org.blue": no name of this type

When processing the exception above, another exception occurred:

Traceback (most recent call last):
"/ Sbin / blueman-applet" file, line 121, in 
    BluemanApplet ()
"/ Sbin / blueman-applet" file, line 63, in __init__
self.Plugins.Load ()
"/Usr/lib/python3.7/site-packages/blueman/main/PluginManager.py" file, line 90, in Load
__import __ (self.module_path .__ name__ + ".% s"% plugin, None, None [])
"/Usr/lib/python3.7/site-packages/blueman/plugins/applet/AuthAgent.py" file, line 9, in 
    import blueman.main.applet.BluezAgent as BluezAgent
"/Usr/lib/python3.7/site-packages/blueman/main/applet/BluezAgent.py" file, line 23, in 
    blueman.bluez.Agent Import Agent, AgentMethod
"/Usr/lib/python3.7/site-packages/blueman/bluez/Agent.py" file, line 48, in 
    Agent class (dbus.service.Object):
File "/usr/lib/python3.7/site-packages/blueman/bluez/Agent.py", line 56, in the agent
@AgentMethod
"/Usr/lib/python3.7/site-packages/blueman/bluez/Agent.py" file, line 38, in AgentMethod
if BlueZInterface.get_interface_version ()[0] <5:
"/Usr/lib/python3.7/site-packages/blueman/blue/BlueZInterface.py" file, line 16, in get_interface_version
obj = dbus.SystemBus (). get_object (org.blue, & # 39; / & # 39;)
"/Usr/lib/python3.7/site-packages/dbus/bus.py" file, line 241, in get_object
follow_name_owner_changes = follow_name_changer_owner_changes)
"/Usr/lib/python3.7/site-packages/dbus/proxies.py" file, line 248, in __init__
self._named_service = conn.activate_name_owner (bus name)
"/Usr/lib/python3.7/site-packages/dbus/bus.py" file, line 180, in activate_name_owner
self.start_service_by_name (bus name)
"/Usr/lib/python3.7/site-packages/dbus/bus.py" file, line 278, in start_service_by_name
& # 39; su & # 39 ;, (bus_name, flags)))
"/Usr/lib/python3.7/site-packages/dbus/connection.py" file, line 651, in call_blocking
message, waiting time)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Service activation failed. org.blue: timeout (service_start_timeout = 25000ms)
2019-02-25 15:14:00 W: awesome: xerror: 1038: error X: request = CopyArea (major 62, minor 0), error = BadDrawable (9)

The content of ~ / .xinitrc is

#! / bin / sh
#
# ~ / .xinitrc
#
# Run by startx (launch your window manager from here)

user resources = $ HOME / .Xresources
usermodmap = $ HOME / .Xmodmap
sysresources = / etc / X11 / xinit / .Xresources
sysmodmap = / etc / X11 / xinit / .Xmodmap

# awesome is kept by default
DEFAULT_SESSION = awesome

# merge defaults and key cards

if [ -f $sysresources ]; then
xrdb -merge $ sysresources
Fi

if [ -f $sysmodmap ]; then
xmodmap $ sysmodmap
Fi

if [ -f "$userresources" ]; then
xrdb -merge "$ userresources"
Fi

if [ -f "$usermodmap" ]; then
xmodmap "$ usermodmap"
Fi

# starts some good programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
for f in /etc/X11/xinit/xinitrc.d/?*.sh; make
        [ -x "$f" ] &&. "$ f"
completed
unsettled f
Fi

get_session () {
local dbus_args = (- - sh syntax --exit-with-session)
case $ 1 in
awesome) dbus_args + = (awesome);
bspwm) dbus_args + = (bspwm-session) ;;
budget) dbus_args + = (budget-desktop) ;;
cinnamon) dbus_args + = (cinnamon-session);
deepin) dbus_args + = (startdde) ;;
illumination) dbus_args + = (illumination_start) ;;
fluxbox) dbus_args + = (startfluxbox) ;;
gnome) dbus_args + = (gnome-session) ;;
i3 | i3wm) dbus_args + = (i3 --shmlog-size 0) ;;
jwm) dbus_args + = (jwm) ;;
kde) dbus_args + = (startkde) ;;
lxde) dbus_args + = (startlxde) ;;
lxqt) dbus_args + = (lxqt-session) ;;
mate) dbus_args + = (mate-session) ;;
xfce) dbus_args + = (xfce4-session) ;;
openbox) dbus_args + = (openbox-session) ;;
*) dbus_args + = ($ DEFAULT_SESSION) ;;
esac

echo "dbus-launch $ {dbus_args[*]} "
}

exec $ (get_session)

What's the problem? Can any one give a .xinitrc file for a correct startup of awesome wm? Log on without connecting to the remote office, everything is fine.

Is it true that lightdm starts the session with awesome does not run ~ / .xinitrc or rather configures dbus-related items in addition? …