speaking of fwupd...

brent

why is this like this?

I will start/ restartservice but hoping to get an opinion.
graci

brent

sudo systemctl restart fwupd.service
[sudo] password for brent:
Job for fwupd.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status fwupd.service" and "journalctl -xeu fwupd.service" for details.

sudo systemctl start fwupd.service
Job for sudo systemctl start fwupd.service
Job for fwupd.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status fwupd.service" and "journalctl -xeu fwupd.service" for details.

journalctl -xeu fwupd.service:

brent

ruh ro

brent

we updated this 10/24 (v 2.0.12-32)

the fwupd people updated this 2 weeks ago: https://github.com/fwupd/fwupd/releases/tag/2.0.13 to v. 2.0.13

relevant?

brent

things I learned about core-dumps from the intetnet and solus forum in the last hour:

cause=who knows
one hour of radically different reasons...could spot no patterns or consistencies in the articles...something broke...read logs...yadda yadda. the only article I read about hardware (memory) was here in an axios/opensnitch thread in June.

BuzzPCSOS

brent Well on plasma I get
systemctl status fwupd ○ fwupd.service - Firmware update daemon Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static) Drop-In: /usr/lib64/systemd/system/service.d └─10-timeout-abort.conf Active: inactive (dead) Docs: https://fwupd.org/
But I know it worked via Discover because I got the MS keys update on that.
Have you tried turning your computer off and back on again?
Try refreshing the fwupd program.
Internet search for "fwupd failed (result core dump)" returns too many links to choose a definitive fix. Several at least pointed to a poor instruction causing it to fail, others were signed off because it fixed itself(?)
This might help refresh our memories.
Personally I monitor my computer manufactures sites for firmware updates. That way I know that it has been done.
That's all I've got.

banger

systemctl status fwupd
● fwupd.service - Firmware update daemon
Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static)
Drop-In: /etc/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Sun 2025-08-03 00:56:33 BST; 1 day 21h ago
Docs: https://fwupd.org/
Main PID: 40670 (fwupd)
Tasks: 4 (limit: 38253)
Memory: 58.8M
CPU: 2.681s
CGroup: /system.slice/fwupd.service
└─40670 /usr/lib64/fwupd/fwupd/fwupd

You broke it didn't you brent. 😃

brent

banger You broke it didn't you brent. 😃

I'd prefer to shift the blame to somewhere else..

..but yeah, probably 🙂

brent

Main process exited, code=dumped, status=5/TRAP

once I figure this out ^^ I might get somewhere(?)

brent

BuzzPCSOS Have you tried turning your computer off and back on again?
Try refreshing the fwupd program.

yes to both.

actually my output was code=dumped not core-dump which I read the first time.
and that search went down in flames.
I am going to re-read what you wrote and posted.
graci

brent

$ fwupdmgr
Failed to connect to daemon: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.fwupd': startup job failed

que paso?

BuzzPCSOS

brent Hope you get it all working. Sorry for the mis-read - it's late here and my eyes are tired.

brent

BuzzPCSOS the mis-read was all on me as I reported it wrong. all good!

Axios

If you have discover running it looks like Banger output he posted
if not it will look like Buzzpcsos Output

journalctl on mine says nothing to show.

Note: seems to stay running even after closing discover

brent

brent@budgie ~ $ sudo eopkg check fwupd
Checking integrity of fwupd OK

package is fine...can't start the service.....exit error of 5 =input/output read error which causes a dump, whatever the he** that means..

@Axios had neither gnome software or discover running when I ran the systemctl command in the terminal but I will study my output again for clues

Axios

brent I will check my budgie in a few I need to update it.
I you boot up it doesnt load it run discover it becomes active and stays that way till next boot
from what it appears.
(Just info)

banger

Maybe an update will appear on the next sync which might fix it.

brent

Axios Well KDE must be different Budgie its active all time.

i think the service is always active on budgie. just not my budgie today.
I ran fwupdmgr and did my own firmware update about 3 weeks ago.
now that service is disabled and I cant restart it.

the only thing I did not do was uninstall/reinstall but I think that's a longshot

banger was thinking that too, hopefully.

Axios

Well KDE must be different Budgie its active all time.

Axios

brent I was 2 updates behind on Budgie just did updates
then the firmware all is working properly.
But I do all firmware from Discover or Software no command line.
Still do other updates from command line tho (hard habit to break)

brent

Axios gnome-software, after hitting update, told me I was up to date. It lied (for lack of a better word) since it pretended to check firmware but fwupmgr cannot be used and I assume that's how it checks for updates.
thanks for the steers---I this could be a week-long investigation 🙂