4
Freshly installed Arch DBus service fail to start (lemmy.ml)
submitted 8 months ago* (last edited 8 months ago) by notTheCat@lemmy.ml to c/linux@lemmy.ml
4 comments fedilink hide all child comments

Two days ago, I did a fresh Arch install, everything went fine, then I changed my mind about my HDD partitioning and reformatted it, and installed Arch again, the install boots okay and all, but NetworkManager was down, when I investigated it, I found out that dbus service fails to start here is what systemctl status dbus returns:

dbus-broker-launch[383]: launcher_add_services @ ../dbus-broker-35/src/launch/launcher.c +805 dbus-broker-launch[383]: launcher_run @ ../dbus-broker-35/src/launch/launcher.c +1416 dbus-broker-launch[383]: run @ ../dbus-broker-35/src/launch/main.c +152 dbus-broker-launch[383]: main @ ../dbus-broker-35/src/launch/main.c +178 dbus-broker-launch[383]: Exiting due to fatal error: -107

I've run journalctl with some filtering and found this too:

systemd-tmpfiles[327]: Detected unsafe path transition / (owned by 999) -> /var (owned by root) during canonicalization of var/lib/dbus systemd-tmpfiles[327]: Detected unsafe path transition / (owned by 999) -> /run (owned by root) during canonicalization of run/dbus

I ran ls / -l and found out that my boot partition is owned by a user named 999 and group adm (what the hell is this?)

I've tried installing dbus-daemon-units and remove dbus-broker and dbus-broker-units, now I got a different problem which was that dbus was timing out on start, so the problem might not be caused by dbus itself, I really don't want to reinstall Arch again, I'm chrooting into my install for internet connection too

you are viewing a single comment's thread
view the rest of the comments
[-] Max_P@lemmy.max-p.me 2 points 8 months ago

Yes I only created / and /boot from the Mint live boot

So that's why the wrong IDs came from. Technically the filesystem doesn't know about names, it knows about IDs, and software just look at /etc/passwd and /etc/groups to go ID<>name.

/ should be 0755 (drwxr-xr-x). Boot, you can chown it all to root and 0755 for directories and 0644 for files safely. The reason you can't for the root is, you'll likely break executable state or SUID bits that sudo needs to be sudo.

[-] notTheCat@lemmy.ml 1 points 8 months ago

you can chown it all

The permissions inside the partition were set correctly, it was only the "root" of the partition that went off, I only created the partition using Mint, while Arch did the whole installation and wrote all the files

Either way I chown both / and /boot to root:root and chmod both / and /boot to 0755 (looked these up from my other Arch machine) and the bugs are gone

this post was submitted on 05 Mar 2024
4 points (64.3% liked)

Linux

48143 readers
741 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
nooter692@lemmy.ml
AgreeableLandscape@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz