igorka67 I might be wrong but the frontend file dictates the process to run as root, so the tree shouldn't matter.

Wat-now I have exactly the same error:

ErrorName:org.freedesktop.DBus.Error.AccessDenied
Error Message: Rejected send message 

what is the output of echo $DBUS_SESSION_BUS_ADDRESS and what does your cat ~/.xinitrc look like?

Wat-now the output of the first command is Unix:path=/run/user/1000/dbus
In my .xinitrc I have:

#!/usr/bin/bash

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

list=( $(ls -A1 /home/wastelander/.66/conf/svscan@wastelander | sort) )
for i in ${list[@]};do
    var=( $(</home/wastelander/.66/conf/svscan@wastelander/${i}) )
    for j in ${var[@]}; do
        export ${j}
    done
done

66 tree start

## Try consolekit
if 66-which -q ck-launch-session; then
    cmd="exec ck-launch-session $@"
else
    cmd="exec $@"
fi

## Select the session to start
${cmd} jwm"

That's my tree status:

Name        : global
Current     : no
Enabled     : yes
Allowed     : root
Groups      : admin
Depends     : None
Required by : session
Contents    : openntpd-log openntpd wpa_supplicant-log wpa_supplicant
              php-fpm-log php-fpm tor-log tor nginx-log nginx dbus-log
              dbus consolekit-log consolekit connmand-log connmand

Name        : boot
Current     : no
Enabled     : no
Allowed     : root
Groups      : boot
Depends     : None
Required by : None
Contents    : boot@system:system-hostname boot@system:mount-run
              boot@system:populate-run boot@system:mount-tmp
              boot@system:populate-tmp boot@system:mount-proc
              boot@system:mount-sys boot@system:populate-sys
              boot@system:mount-dev boot@system:mount-pts
              boot@system:mount-shm boot@system:populate-dev
              boot@system:mount-cgroups boot@system:mount-branch
              boot@system:system-hwclock boot@system:modules-kernel
              boot@system:system-random boot@system:modules-system
              boot@system:system-sysctl boot@system:udevd-log
              boot@system:udevd boot@system:udevadm
              boot@system:system-fontnkey boot@system:system-fsck
              boot@system:mount-fstab boot@system:system-branch
              boot@system:mount-rw boot@system:local-loop
              boot@system:local-authfiles boot@system:local-sethostname
              boot@system:local-time boot@system:local-tmpfiles
              boot@system:local-dmesg boot@system:tty-earlier@tty12
              boot@system:mount-netfs boot@system:local-branch
              boot@system:runtime-branch boot@system:canopy
              boot@system:tty-rc@tty1 boot@system:tty-rc@tty2 boot@system

Name        : session
Current     : no
Enabled     : yes
Allowed     : root
Groups      : admin
Depends     : global
Required by : None
Contents    : scandir@wastelander:setenv@wastelander
              scandir@wastelander:svscan@wastelander
              scandir@wastelander:svscan@wastelander-log scandir@wastelander
              boot-user@wastelander:mount-run@wastelander boot-user@wastelander

and my user tree:

Name        : global
Current     : no
Enabled     : yes
Allowed     : wastelander
Groups      : user
Depends     : None
Required by : None
Contents    : xdg-user-dirs dbus@wastelander-log dbus@wastelander pipewire-log
              pipewire pipewire-pulse-log pipewire-pulse wireplumber-log
              wireplumber

Output of groups:
wheel log network video audio optical floppy storage scanner power users rfkill wastelander

temporary workaround is #66 configure -e <youreditor> boot-user@<yoursystem> then edit DESKTOP_CMDLINE=dbus-run-session what-ever-you-use before #66 reconfigure boot-user@<yoursystem>

I dont know why some systems seem to need this and some don't, and I dont know why you didnt need it before the dbus update. dbus is a head-scratcher for sure

Wat-now thanks but the result is the same. When I run connman-gtk I have no more errors in the terminal but the GUI is still blank..

This is a permission issue

** (connman-gtk:7668): CRITICAL **: 14:20:26.840: Failed to connect to connman: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 3 matched rules; type="method_call", sender=":1.2349" (uid=1000 pid=7668 comm="connman-gtk") interface="net.connman.Manager" member="GetTechnologies" error name="(unset)" requested_reply="0" destination=":1.451" (uid=0 pid=3010 comm="/usr/bin/connmand -n --nobacktrace --nodnsproxy")

For now, i don't found the fix.
As you can see, the connection with dbus is made perfectly.

eric after this change I can only see my current network in the UI, no other ones. Indeed in the terminal I have the same error as before preceded by Failed to scan Wifi
UPDATE: I think I fixed it! (source: https://github.com/aldebaran/connman/blob/master/src/connman-dbus.conf). I edited connman.conf this way:

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
    <policy user="root">
        <allow own="net.connman"/>
        <allow send_destination="net.connman"/>
        <allow send_interface="net.connman.Agent"/>
        <allow send_interface="net.connman.Counter"/>
        <allow send_interface="net.connman.Notification"/>
    </policy>
    <policy group="network">
       <allow send_destination="net.connman"/>
    </policy>
    <policy context="default">
        <allow send_destination="net.connman"/>
    </policy>
</busconfig>

It seems to work fine now. Can you try it on your side?

@Wat-now can you also test this configuration but with the dbus Arch patch applied too? I have just downgraded dbus to 1.16.0-4 (the patched release) and it works fine, so I really think that the patch wasn't the offender.

igorka67 no prob, glad it worked for you too, now the fix can be safely applied to the package in the repos as long as it works:)

Wat-now good, so the only needed commit is to patch that connman.conf file.
Btw I have seen that it's the same change that's present in the official Debian package, though they don't use a policy for a network group:
https://salsa.debian.org/debian/connman/-/blob/debian/sid/src/connman-dbus.conf?ref_type=heads

@Wat-now my proposed configuration might work but is possibly incorrect. The debian configuration is not really theirs, it's simply the default upstream source configuration. Arch removed by purpose the allow send_destination line (that I reintroduced) from the root policy block and replaced the policy at_console block with a network group policy, the latter containing the allow send_interface line. So it's not that straightforward as it seemed and the changes that I made might not really make sense. I even tried the default source configuration but it didn't work, so far the only working configuration is the one that I posted before...