[SOLVED] latest upgrade breaks system

Scimmia · 2024-01-23 16:00:31

We also need a log with dbus-broker failing.

seth · 2024-01-23 16:08:50

Also maybe better

pacman -Qikk dbus dbus-broker dbus-units systemd

aquilarubra · 2024-01-23 16:10:09

Ok, solution found.

dbus-daemon-units runs dbus in daemon mode and uninstalls (is not compatible with) dbus-broker-units, which uses sockets.

My system was failing because it was using dbus-broker-units, which changed the dbus.service file in /usr/lib/systemd/system and /usr/lib/systemd/user.

Why dbus-broker is not working, I don't know.

Last edited by aquilarubra (2024-01-23 16:11:05)

seth · 2024-01-23 16:11:14

Scimmia wrote:

We also need a log with dbus-broker failing.

aquilarubra · 2024-01-23 16:13:11

I didn't have dbus-daemon-units. Now I have it, I don't have dbus-broker-units, but I still do have dbus-broker, and it works.

seth · 2024-01-23 16:15:12

Because it's just wasting space on your drive w/o the units.

aquilarubra · 2024-01-23 16:20:07

I removed also dbus-broker and it works flawlessly.

I wouldn't test with dbus-broker-units again...

seth · 2024-01-23 16:24:00

Of course it does, w/o the units its presence is meaningless.

You can use dbus-broker or not; if you decide to re-try it, don't flail around when you're getting problems. Ask.
As you figured, there's always a way to make things worse this way.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Scimmia · 2024-01-23 17:06:52

You can still get the log we need using an argument for journalctl's -b option. You likely have something wrong on your system that needs fixed instead of ignoring it by using dbus-daemon.

aquilarubra · 2024-01-23 17:09:48

It's here:

sudo journalctl --boot=-1 | curl -F 'file=@-' 0x0.st

http://0x0.st/HGT9.txt

aquilarubra · 2024-01-23 17:11:01

This is the trigger:

Jan 23 14:49:54 main systemd[1]: dbus.socket: Socket service dbus.service not loaded, refusing.
Jan 23 14:49:54 main systemd[1]: Failed to listen on D-Bus System Message Bus Socket.

Scimmia · 2024-01-23 17:14:55

That is from when your unit files were screwed up because of using --overwrite. That's not when it was using dbus-broker.

seth · 2024-01-23 17:15:24

That's just https://bbs.archlinux.org/viewtopic.php … 2#p2145862 again.

Edit: F5ck

Last edited by seth (2024-01-23 17:15:43)

aquilarubra · 2024-01-23 17:22:13

No, I restored the upgrade and the 2 dbus.service files were also changed to use the socket.

Only when I used the journal command I was again in the downgraded system, but I logged the previous boot, so the one with the latest upgrades and not overwritten files.

To downgrade, each time I had to --overwrite again, as the upgrade touched those 2 files.

Scimmia wrote:

That is from when your unit files were screwed up because of using --overwrite. That's not when it was using dbus-broker.

Scimmia · 2024-01-23 17:25:15

None of that is how any of this works.

We need the journal from when dbus-broker was actually being used before you did any downgrading at all.

aquilarubra · 2024-01-23 17:30:16

That's what I'm saying. That log was made with:

- latest dbus
- dbus-broker-units
- no dbus-daemon-units

And no overwritten files. Just original files installed by dbus, latest version.

Then, as the system did not reach the console, I had to downgrade dbus, which overwrite the 2 dbus.service files (I posted exactly how they looked before and after downgrade), and I could use journal to see what happened in the previous failed boot.

Scimmia · 2024-01-23 17:33:43

You're not getting it. As soon as you used --overwrite THE FIRST TIME, everything was screwed. When you updated dbus again, it removed the files completely, it didn't restore them to what they were.

aquilarubra · 2024-01-23 17:35:16

Scimmia wrote:

You're not getting it. As soon as you used --overwrite THE FIRST TIME, everything was screwed. When you updated dbus again, it removed the files completely, it didn't restore them to what they were.

They were exactly as posted. "Backup"

Scimmia · 2024-01-23 17:37:23

What you posted was completely wrong, so no, those are not backups

Whatever. At this point, I don't care, we'll just wait for your system to blow up again.

Last edited by Scimmia (2024-01-23 17:38:14)

aquilarubra · 2024-01-23 17:41:26

Anyway, the latest dbus latest upgrade replaces those 2 files, whatever you had before. I could see that. So, it is no point in discussing what was before, because it was anyway replaced. I could backup only before making the first downgrade, and it indicated me only those files.

seth · 2024-01-23 18:19:29

Install dbus-broker-units again, it'll drag in dbus-broker and replace dbus-daemon-units.
If this breaks anything, post the journal for that.
Under no circumstances try to fix anything by downgrading or overwriting stuff.
If there're odd errors or warnings when installing dbus-broker-units, post those too.

I'l be afk until ~22:00 UTC, so if you're scared, you can wait a moment

aquilarubra · 2024-01-23 18:22:46

Lol. I would rather not do it, as it won't work. And I won't be able to reach a console, unless I downgrade and resurrect the system again. So it is the dog biting its tail.

V1del · 2024-01-23 18:27:50

There are literally thousands of people that do not have this issue. While this will work for now and likely for the foreseeable future there might be a time when it's officially deprecated and you will have to face this again. You rather want to do that while it's fresh in memory rather than when people are like "wtf are you using dbus-daemon still, no one knows how that works anymore"

seth · 2024-01-23 18:30:12

Dogs chase their tail, what's mean but fun to watch.
Brits are going round in circles.
And in germany, cats bite their tail.

Either way:
1. ideally this will just work
2. if not you can get the journal from a live distro (I linked before, how to)
3. or re-install dbus-daemon-units (what will remove dbus-broker-units)

Whatever the cause for your previous troubles was might still be there and come back to bite you at some point.
You can't just run from that forever.

aquilarubra · 2024-01-23 20:33:27

I see it is a very common issue. Maybe this may be the solution:

https://bbs.archlinux.org/viewtopic.php?id=249082

I will try tomorrow.

Arch Linux

#26 2024-01-23 16:00:31

Re: [SOLVED] latest upgrade breaks system

#27 2024-01-23 16:08:50

Re: [SOLVED] latest upgrade breaks system

#28 2024-01-23 16:10:09

Re: [SOLVED] latest upgrade breaks system

#29 2024-01-23 16:11:14

Re: [SOLVED] latest upgrade breaks system

#30 2024-01-23 16:13:11

Re: [SOLVED] latest upgrade breaks system

#31 2024-01-23 16:15:12

Re: [SOLVED] latest upgrade breaks system

#32 2024-01-23 16:20:07

Re: [SOLVED] latest upgrade breaks system

#33 2024-01-23 16:24:00

Re: [SOLVED] latest upgrade breaks system

#34 2024-01-23 17:06:52

Re: [SOLVED] latest upgrade breaks system

#35 2024-01-23 17:09:48

Re: [SOLVED] latest upgrade breaks system

#36 2024-01-23 17:11:01

Re: [SOLVED] latest upgrade breaks system

#37 2024-01-23 17:14:55

Re: [SOLVED] latest upgrade breaks system

#38 2024-01-23 17:15:24

Re: [SOLVED] latest upgrade breaks system

#39 2024-01-23 17:22:13

Re: [SOLVED] latest upgrade breaks system

#40 2024-01-23 17:25:15

Re: [SOLVED] latest upgrade breaks system

#41 2024-01-23 17:30:16

Re: [SOLVED] latest upgrade breaks system

#42 2024-01-23 17:33:43

Re: [SOLVED] latest upgrade breaks system

#43 2024-01-23 17:35:16

Re: [SOLVED] latest upgrade breaks system

#44 2024-01-23 17:37:23

Re: [SOLVED] latest upgrade breaks system

#45 2024-01-23 17:41:26

Re: [SOLVED] latest upgrade breaks system

#46 2024-01-23 18:19:29

Re: [SOLVED] latest upgrade breaks system

#47 2024-01-23 18:22:46

Re: [SOLVED] latest upgrade breaks system

#48 2024-01-23 18:27:50

Re: [SOLVED] latest upgrade breaks system

#49 2024-01-23 18:30:12

Re: [SOLVED] latest upgrade breaks system

#50 2024-01-23 20:33:27

Re: [SOLVED] latest upgrade breaks system

Board footer