Try disabling connmand since you have dhcpcd running, maybe they conflict each other, but I suspect the problem is with dbus and consolekit. connman and dhcpcd are trying to configure network on their own and fight each other.

sudo 66-inservice -p10 dbus
sudo 66-inservice -p10 consolekit

The rest of the problems are related to this, both sddm and connmand I believe need a running dbus, and since root is not right boot-user will not start and so you have no user level services.

But xinit should start at this point and with dhcpcd running you at least should have ethernet.

Does "ip a " give you an IP?
@ fungalnet
You seems very confortable now to debug the things, this is warm my heart :).

@ saleem
Like fungalnet said you in his last post, only use one network daemon. So pick dhcpcd or command but do not enable the both.
Now, your trouble clearly come from dbus, tries to enable it again 
%sudo 66-enable -t root -C -F dbus
you also have trouble with your tree of your regular user. So destroy all trees of your regular user and rebuild them following the wiki like you did before.
fungal_net wroteTry disabling connmand since you have dhcpcd running, maybe they conflict each other, but I suspect the problem is with dbus and consolekit. connman and dhcpcd are trying to configure network on their own and fight each other.

sudo 66-inservice -p10 dbus
sudo 66-inservice -p10 consolekit

The rest of the problems are related to this, both sddm and connmand I believe need a running dbus, and since root is not right boot-user will not start and so you have no user level services.

But xinit should start at this point and with dhcpcd running you at least should have ethernet.

Does "ip a " give you an IP?
1 ) Try disabling connmand

I rather disabled dhcpcd and tried running connman from terminal and got this output

sudo connmanctl
Error: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

2 ) sudo 66-inservice -p10 dbus

https://paste.ubuntu.com/p/hG8vvNDZgf/

3 ) sudo 66-inservice -p10 consolekit

https://paste.ubuntu.com/p/zbrYTNzKN5/

4 ) The rest of the problems are related to this, both sddm

I disabled sddm too

5 ) Does "ip a " give you an IP?

https://paste.ubuntu.com/p/z49HRs2D62/
1st I forgot to mention it before, you are using a different system's boot loader than Obarun, which is probably making up the entry for obarun according to Arch's template. You have to go to that system and edit /boot/grub/grub.cfg and switch all the obarun entried from rw to ro It didn't make a big difference in the past but now it does. You can also try it first manually by going to the obarun entry while about to boot and hit "e" that will take you to an editor and you can go to the linux line, past the uuid replace " rw " with ro. Then ctrl-X This doesn't make a permanent change, it is only for that one session.

I don't know what to tell you about dbus, I was hoping Eric might.

If dhcpcd is still installed (just disabled) and ethernet cable plugged in to a lan with a router

# dhcpcd enp19s0
# ip a

should show you a connection

xinit should work with what you have despite of dbus and consolekit failures, just have exec openbox-session on .xinitrc
This should give you a terminal to do more work easier. I don't have dbus enabled or consolekit and things work well for me. I wouldn't try to use connman without dbus though.
For wifi you can use wpa_supplicant and aur has a little gadget to help you configure it if you can't do it manually (Arch wiki)
You will need wpa_supplicant-66serv installed and the service enabled and install wpa-cute or wifiman or something like this from AUR.
eric wrote@ fungalnet
You seems very confortable now to debug the things, this is warm my heart :).

@ saleem
Like fungalnet said you in his last post, only use one network daemon. So pick dhcpcd or command but do not enable the both.
Now, your trouble clearly come from dbus, tries to enable it again 
%sudo 66-enable -t root -C -F dbus
you also have trouble with your tree of your regular user. So destroy all trees of your regular user and rebuild them following the wiki like you did before.
fungalnet has been very helpful , I followed his post about Spark and things got fixed which I could not previously in three years .

Like fungalnet said you in his last post, only use one network daemon.

I disabled dhcpcd already . disabled and re enabled dbus already .

I will try to kill all my regular user trees .....
silly question but now im disoriented , how do I destroy and re create my regular user tree/trees?

  • [deleted]

  • Post #27
@ saleem

66-tree -R to remove the tree
66-tree -RU to remove the tree and unsupervise the tree

66-tree -h to print the help
Finally I managed to connect Obarun with connman , so posting this comment being on Obarun now.

How will I confirm ( through commands ) that my Obarun is ideally as latest and with the desired configurations and settings as the latest Obarun is ?
Now X crashes for me with startx , new development :(
This thread was meant especially for people making the transition from boot-66serv to boot@ -66serv, and obviously there weren't so many problems. It is not meant for Saleem's generally issues and problems.
You are free to create new topics for any particular problem, otherwise threads fill up with unrelated material and become less useful for people.


pacman -Qs xorg-server should show you whether you have this package installed.
pacman -Qi xorg-server should show you information about this pkg
pacman -Ql xorg-server shouls show you the list of files it contains

You said you had no /etc/X11/Xrapper.config or was this somewhere else? Because this file is standard in Obarun's xorg-server.

Question: Is this originally an Obarun installation or was it a conversion from some other arch-based distro?
pacman -Syu with all obarun repositories on top and arch below should have made it 100% obarun.
If you are in doubt, pacman -S base will show if you are missing something.
pacopts origin
pacopts origin obextra
pacopts origin obcommunity

can show if you are retaining packages from some other system that need to be replaced by obarun's versions.

This is now unrelated to 66 and I am making a big mistake responding here and not in some more appropriate place to be answered.
3 years later
eric unstickied the discussion .

Powered by Obarun