Connman-gtk shows blank

wastelander

nfg hmm I uninstalled connman-gtk, deleted the /etc/connman folder and reinstalled it, no joy..also, the /etc/connman folder didn't come back..

nfg

wastelander

But as you say, this does seem to be dbus related. I wonder if stopping, removing and re-enabling & re-starting the dbus root service might help. I wish I could reproduce your guys error and be more helpful.

nfg

You would probably need to reinstall connman itself to repopulate /etc/connman. FWIW, my just contains main.conf whose contents are [General] followed by a bunch of commented out text.

nfg

wastelander When you run networkmanager with success as non-root, do you see anything in the root dbus logs?

wastelander

nfg sorry you were correct, I had forgotten to reinstall connman and I got the folder back. Yes, I tried to reload the dbus service after the reinstall, it doesn't help. When I enable and start the networkmanager service the dbus log shows Successfully activated service "org.freedesktop.nm_dispatcher"and"Successfully activated service "fi.wl.wpa_supplicant"

wastelander

@nfg btw, do you have kind of a vanilla setup or did you install anything particular? Because my install is pretty fresh, maybe I'm missing some post-install package?

Wat-now

sync and install the latest 1.16.0-5, the patch has been removed which prevented the legacy config which I think connman-gtk uses.

wastelander

Wat-now done, I also reinstalled connman and reloaded connmand and dbus, I still get the same behavior..So at this point maybe it's better to keep the patch :) what's really odd is that even downgrading dbus to 1.14 didn't work anymore (it did when I opened the issue for the first time though)

wastelander

Could anyone please try to build the connman git version from the aur and test it? I have tried to build it but it kept failing

Wat-now

wastelander try cmst (in obocmmunity now) which should also communicate with connman and see if it works, because connman-gtk works on my system.

igorka67

Maybe connmand should be started from the user tree and not from the root tree...
Is this nonsense?

wastelander

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

wastelander

Wat-now I have exactly the same error:


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

Wat-now

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

wastelander

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

Wat-now

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

wastelander

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..

Wat-now

wastelander Interesting, I tried this in a system of mine having the same trouble and it worked.

wastelander

Wat-now It looks like my system is really out of luck:) but would it make sense to try dbus-launch instead of dbus-run-session?

Wat-now

wastelander You may have to downgrade back to dbus-1.14.10-2, something is up with the permissions somewhere I suspect.

wastelander

Wat-now yes, I uninstalled dbus, wiped out the /usr/share/dbus-1 , downgraded to 1.14 and now its working. Wondering if we should patch connman to work with dbus 1.16 or the opposite.I also guess it's a permission issue, connman-gtk always works with sudo.

« Previous Page Next Page »