I'm a new user of Obarun and Arch in general and have really been enjoying my time learning with this OS. Currently Im having an issue trying to get Network Manager functioning correctly and wasnt able to find an easy answer. On the Obarun repos I was able to find and installed the networkmanager and networkmanager-66serv packages. I figured I would find a service file for network manger under /etc/66/service after installing the networkmanager-66serv package (so not sure how this functions exactly) but this was not the case, but I was still able to run the commands to enable and start networkmanager,

signal: info: Successfully started service: dbus-log
signal: info: Successfully started service: dbus
signal: info: Successfully started service: networkmanager-log
signal: info: Successfully started service: networkmanager

but the service doesnt actually start as shown when I run 66 status.

Name : networkmanager
Version : 0.7.0
In tree : global
Status : enabled, down (exitcode 1) 0 seconds, normally up, want up, ready 0 seconds
Type : classic
Description : networkmanager daemon
Part of : None
Notify : 0
Max death : 5
Earlier : 0
Source : /usr/share/66/service/networkmanager
Live : /run/66/scandir/0/networkmanager
Dependencies : networkmanager-log dbus-log dbus
Required by : None
Contents : None
Optional dependencies : None
Start script :
#!/usr/bin/execlineb -P
/usr/bin/fdmove -c 2 1
execl-envfile -v4 /etc/66/conf/networkmanager/version


                     /usr/bin/execl-cmdline -s { /usr/bin/NetworkManager ${Args} } 

Stop script :
None
Environment source : /etc/66/conf/networkmanager/0.7.0
Environment file :
environment variables from: /etc/66/conf/networkmanager/0.7.0/.networkmanager
Args=!-n --debug

Log name : networkmanager-log
Log destination : /var/log/66/networkmanager
Log file :
<info> [1730070861.6735] settings: Loaded settings plugin: keyfile (internal)
<warn> [1730070861.7411] dhcp: init: DHCP client 'dhclient' not available
<info> [1730070861.7411] dhcp: init: Using DHCP client 'internal'
<info> [1730070861.7413] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
<info> [1730070861.7418] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
<info> [1730070861.7421] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
<info> [1730070861.7427] device (lo): Activation: starting connection 'lo' (1fa54a6a-8382-4367-8810-169f5929af5f)
<info> [1730070861.7431] device (enp42s0): carrier: link connected
<info> [1730070861.7434] manager: (enp42s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
<info> [1730070861.7439] device (enp42s0): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
<info> [1730070861.7445] device (enp42s0): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
<info> [1730070861.7451] device (enp42s0): Activation: starting connection 'enp42s0' (ce6cb40d-9d4d-4620-8b03-8420e93a7290)
<info> [1730070861.7454] device (wlp39s0): driver supports Access Point (AP) mode
<info> [1730070861.7458] manager: (wlp39s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
<info> [1730070861.7460] device (wlp39s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
<info> [1730070861.7785] device (wlp39s0): set-hw-addr: set MAC address to 0E:5D:9E:89:41:19 (scanning)
<error> [1730070861.7809] bus-manager: fatal failure to acquire D-Bus service "org.freedesktop.NetworkManager" (3). Service already taken
<info> [1730070861.7814] device (wlp39s0): state change: unavailable -> unmanaged (reason 'unmanaged-quitting', managed-type: 'full')
<info> [1730070861.8421] device (wlp39s0): set-hw-addr: reset MAC address to E2:F6:27:2D:3A:3D (unmanage)
<info> [1730070861.8554] exiting (error)

I was hoping someone could point me in the right direction as Im a bit lost. Ive been able to successfully add my own services and start them via creating my own service files within /etc/66/service then parsing, starting and enabling them but when it comes to networkmanager-66erv not actually placing a service file in that directory or working correctly, it requires more knowledge of how this system works than I currently possess. Any help would be greatly appreciated.

~ CrazyAce

Seems like dhclient is not in use for some reason?

Do you have a broadcom chipset by chance?

Also did it work using connmand?

PS: make sure youre not also running connmand, they conflict.

lets see your: # 66 tree status -g global

substitute global for whatever tree you have networkmanager in

The system actually uses an Intel chipset. Connman worked fine on the live image, but as soon as it was installed and booted it no longer functioned correctly. When I loaded up connman-gtk manually, it was completely blank. After messing around a bit with trying to get it to load with zero success , I decided to try out network manager, which I tend to prefer anyway. Im still having the same issues though. I loaded up network manager applet and when you click the tray icon it just says, "NetworkManager is not running..." which is the same thing 66 status tells me.

    CrazyAce I suspect a driver issue. Do you have the package linux-firmware insatlled or at least the iwlwifi drivers extracted from it?

    edit: Maybe youre using ethernet?
    Maybe the dmesg log could help?

      Wat-now It turned out to be the issue you mentioned before regarding a conflict with connman. I had made the apparently erroneous assumption that when connman was completely uninstalled that the services would go along with it, which turned out to be wrong. Once I stopped and removed the connman service, there was no more conflict and network manager began to work after relogging. So now that I have that fixed (thank you btw), Im wondering why it is that connman-gtk wouldnt load right in the first place, so I've reloaded a fresh Obarun install to troubleshoot. While I do prefer network manager for some configurations, connman is also useful for others and thus I would like to figure out why connman-gtk has to be manually started and even then still shows no data unless ran as root.
      It functions fine under jwm, but stops functioning as soon as I move to XFCE. I found this thread earlier, https://forum.obarun.org/d/725-connman-gtk-displays-blank-output-wifi-is-down-solved/11, and maybe there is a way to apply that fix to the current version of Obarun but I wouldnt know how. It calls for editing a file located /etc/dbus-1/system.d/connman.conf which doesnt exist on my system. /etc/dbus-1 is non existent.

      sudo 66 status connmand-66serv
      [sudo] password for oblive:
      status: fatal: service: connmand-66serv is not parsed -- try to parse it using '66 parse connmand-66serv'
      oblive@Ob66 [111] ~ % sudo 66 status connmand
      Name : connmand
      Version : 0.7.0
      In tree : global
      Status : enabled, up (pid 1036 pgid 1036) 3336 seconds
      Type : classic
      Description : connman daemon
      Part of : None
      Notify : 0
      Max death : 5
      Earlier : 0
      Source : /usr/share/66/service/connmand
      Live : /run/66/scandir/0/connmand
      Dependencies : dbus-log connmand-log dbus
      Required by : None
      Contents : None
      Optional dependencies : None
      Start script :
      #!/usr/bin/execlineb -P
      /usr/bin/fdmove -c 2 1
      execl-envfile -v4 /etc/66/conf/connmand/version


                           /usr/bin/execl-cmdline -s { /usr/bin/connmand ${Args} } 

      Stop script :
      None
      Environment source : /etc/66/conf/connmand/0.7.0
      Environment file :
      environment variables from: /etc/66/conf/connmand/0.7.0/.connmand
      Args=!-n --nobacktrace --nodnsproxy

      Log name : connmand-log
      Log destination : /var/log/66/connmand
      Log file :
      connmand[1036]: enp42s0 {newlink} index 2 address 70:85:C2:46:DB:BA mtu 1500
      connmand[1036]: enp42s0 {newlink} index 2 operstate 2 <DOWN>
      connmand[1036]: enp42s0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
      connmand[1036]: enp42s0 {newlink} index 2 address 70:85:C2:46:DB:BA mtu 1500
      connmand[1036]: enp42s0 {newlink} index 2 operstate 6 <UP>
      connmand[1036]: Interface enp42s0 [ ethernet ] state is configuration
      connmand[1036]: Cannot create /var/run/connman/resolv.conf falling back to /etc/resolv.conf
      connmand[1036]: Interface enp42s0 [ ethernet ] state is ready
      connmand[1036]: Interface enp42s0 [ ethernet ] is the default
      connmand[1036]: enp42s0 {add} address 192.168.1.17/24 label enp42s0 family 2
      connmand[1036]: Interface enp42s0 [ ethernet ] IPv4 online check to http://ipv4.connman.net/online/status.html succeeded
      connmand[1036]: Interface enp42s0 [ ethernet ] state is online
      connmand[1036]: chi308 {create} index 4 type 65534 <NONE>
      connmand[1036]: chi308 {update} flags 144 <DOWN>
      connmand[1036]: chi308 {newlink} index 4 address 00:00:00:00:00:00 mtu 1420
      connmand[1036]: chi308 {newlink} index 4 operstate 2 <DOWN>
      connmand[1036]: chi308 {add} address 10.67.118.29/32 label chi308 family 2
      connmand[1036]: chi308 {update} flags 65745 <UP,RUNNING,LOWER_UP>
      connmand[1036]: chi308 {newlink} index 4 address 00:00:00:00:00:00 mtu 1420
      connmand[1036]: chi308 {newlink} index 4 operstate 0 <UNKNOWN>

      oblive@Ob66 ~ % ps aux | grep dbus
      root 971 0.0 0.0 2848 1776 ? S 02:20 0:00 s6-supervise dbus
      root 972 0.0 0.0 2848 1704 ? S 02:20 0:00 s6-supervise dbus-log
      s6log 1008 0.0 0.0 2852 1564 ? Ss 02:20 0:00 s6-log -d3 n3 s1000000 /var/log/66/dbus
      dbus 1021 0.0 0.0 4136 3356 ? Ss 02:20 0:03 /usr/bin/dbus-daemon --system --print-pid=4 --nofork --nopidfile --address=unix:path=/run/dbus/system_bus_socket
      oblive 1245 0.0 0.0 2848 1816 ? S 02:20 0:00 s6-supervise dbus@oblive
      oblive 1246 0.0 0.0 2848 1852 ? S 02:20 0:00 s6-supervise dbus@oblive-log
      oblive 1257 0.0 0.0 2852 1588 ? Ss 02:20 0:00 s6-log -d3 n3 s1000000 /home/oblive/.66/log/dbus@oblive
      oblive 1261 0.0 0.0 4304 3660 ? Ss 02:20 0:00 /usr/bin/dbus-daemon --session --print-pid=4 --nofork --nopidfile --address=unix:path=/run/user/1000/bus
      oblive 1286 0.0 0.0 3688 3064 ? S 02:20 0:00 /usr/sbin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/1000/at-spi/bus_0
      oblive 8264 0.0 0.0 6640 4112 pts/2 S+ 14:02 0:00 grep --colour=auto dbus

      Alright, so from the post above from 2019 I was able to find the following, but edited " /usr/share/dbus-1/system.d/connman.conf" instead to add that specific line, as I dont have the other folder on my system.

      "what i do to get connman-gtk to work for my user:

      1. be in the network group
      2. edit /etc/dbus-1/system.d/connman.conf to look like:

      <!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_interface="net.connman.Agent"/>
      <allow send_interface="net.connman.Counter"/>
      <allow send_interface="net.connman.Notification"/>
      </policy>
      <policy group="network">
      <allow send_interface="net.connman.Agent"/>
      <allow send_interface="net.connman.Manager"/>
      </policy>
      <policy context="default">
      <allow send_destination="net.connman"/>
      </policy>
      </busconfig>

      i think it's the line:
      <allow send_interface="net.connman.Manager"/>"
      I

      This does indeed allow connman-gtk to start and actually show its interface, but no changes made within the GUI actually save at all. If I diable IPv6 or change the name servers, apply and then close the app and re open it, the changes have been reverted.

        CrazyAce I'm glad you got networkmanager working! For changes under connman-gtk make sure your user is in the right group, network or something. Thats my best guess.

        Powered by Obarun