You are not logged in.

#1 2025-09-15 18:55:31

bobber228
Member
Registered: 2025-09-15
Posts: 2

fwupd Will Not Start

Hello everyone.
This is my first post so sorry if its hard to follow.

I'm trying to update my peripherals with fwupd, but the daemon does not start.
I checked its status with

Systemd status

but I don't understand the output enough to fix the error.

Here it is:

× fwupd.service - Firmware update daemon
     Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static)
     Active: failed (Result: core-dump) 
 Invocation: 7126cc2277f549038335e6a321f0e73b
       Docs: https://fwupd.org/
    Process: 7943 ExecStart=/usr/lib/fwupd/fwupd (code=dumped, signal=SEGV)
   Main PID: 7943 (code=dumped, signal=SEGV)
   Mem peak: 7.6M
        CPU: 123ms

systemd[1]: Starting Firmware update daemon...
systemd-coredump[7954]: Process 7943 (fwupd) of user 0 dumped core.
                        
                        Stack trace of thread 7943:
                        #0  0x00007fee5ae690f0 n/a (libflashrom.so.1 + 0xc0f0)
                        #1  0x00007fee5ae6d87b flashrom_flash_probe_v2 (libflashrom.so.1 + 0x1087b)
                        #2  0x00007fee5af7d532 n/a (libfu_plugin_flashrom.so + 0x4532)
                        #3  0x00007fee60624589 fu_plugin_runner_startup (libfwupdplugin.so + 0xe3589)
                        #4  0x00007fee608339ca fu_engine_load (libfwupdengine.so + 0xd19ca)
                        #5  0x00005595d46c103e n/a (/usr/lib/fwupd/fwupd + 0xb03e)
                        #6  0x00005595d46c65a2 fu_daemon_setup (/usr/lib/fwupd/fwupd + 0x105a2)
                        #7  0x00005595d46bd5ff main (/usr/lib/fwupd/fwupd + 0x75ff)
                        #8  0x00007fee5fe53675 n/a (libc.so.6 + 0x27675)
                        #9  0x00007fee5fe53729 __libc_start_main (libc.so.6 + 0x27729)
                        #10 0x00005595d46bdb95 _start (/usr/lib/fwupd/fwupd + 0x7b95)
                        
                        Stack trace of thread 7947:
                        #0  0x00007fee5fecb042 n/a (libc.so.6 + 0x9f042)
                        #1  0x00007fee5febf1ac n/a (libc.so.6 + 0x931ac)
                        #2  0x00007fee5febf1f4 n/a (libc.so.6 + 0x931f4)
                        #3  0x00007fee5ff39a36 ppoll (libc.so.6 + 0x10da36)
                        #4  0x00007fee600fbe04 n/a (libglib-2.0.so.0 + 0x5fe04)
                        #5  0x00007fee600fbee5 g_main_context_iteration (libglib-2.0.so.0 + 0x5fee5)
                        #6  0x00007fee600fbf32 n/a (libglib-2.0.so.0 + 0x5ff32)
                        #7  0x00007fee6013297c n/a (libglib-2.0.so.0 + 0x9697c)
                        #8  0x00007fee5fec29cb n/a (libc.so.6 + 0x969cb)
                        #9  0x00007fee5ff46834 __clone (libc.so.6 + 0x11a834)
                        
                        Stack trace of thread 7950:
                        #0  0x00007fee5ff4476d syscall (libc.so.6 + 0x11876d)
                        #1  0x00007fee6012b87e g_cond_wait_until (libglib-2.0.so.0 + 0x8f87e)
                        #2  0x00007fee600c1e87 n/a (libglib-2.0.so.0 + 0x25e87)
                        #3  0x00007fee6013436b n/a (libglib-2.0.so.0 + 0x9836b)
                        #4  0x00007fee6013297c n/a (libglib-2.0.so.0 + 0x9697c)
                        #5  0x00007fee5fec29cb n/a (libc.so.6 + 0x969cb)
                        #6  0x00007fee5ff46834 __clone (libc.so.6 + 0x11a834)
                        
                        Stack trace of thread 7948:
                        #0  0x00007fee5ff4476d syscall (libc.so.6 + 0x11876d)
                        #1  0x00007fee6012a8ee g_cond_wait (libglib-2.0.so.0 + 0x8e8ee)
                        #2  0x00007fee600c1ebd n/a (libglib-2.0.so.0 + 0x25ebd)
                        #3  0x00007fee60133547 n/a (libglib-2.0.so.0 + 0x97547)
                        #4  0x00007fee6013297c n/a (libglib-2.0.so.0 + 0x9697c)
                        #5  0x00007fee5fec29cb n/a (libc.so.6 + 0x969cb)
                        #6  0x00007fee5ff46834 __clone (libc.so.6 + 0x11a834)
                        
                        Stack trace of thread 7949:
                        #0  0x00007fee5fecb042 n/a (libc.so.6 + 0x9f042)
                        #1  0x00007fee5febf1ac n/a (libc.so.6 + 0x931ac)
                        #2  0x00007fee5febf1f4 n/a (libc.so.6 + 0x931f4)
                        #3  0x00007fee5ff39a36 ppoll (libc.so.6 + 0x10da36)
                        #4  0x00007fee600fbe04 n/a (libglib-2.0.so.0 + 0x5fe04)
                        #5  0x00007fee600fc097 g_main_loop_run (libglib-2.0.so.0 + 0x60097)
                        #6  0x00007fee6036afe4 n/a (libgio-2.0.so.0 + 0x117fe4)
                        #7  0x00007fee6013297c n/a (libglib-2.0.so.0 + 0x9697c)
                        #8  0x00007fee5fec29cb n/a (libc.so.6 + 0x969cb)
                        #9  0x00007fee5ff46834 __clone (libc.so.6 + 0x11a834)
                        ELF object binary architecture: AMD x86-64
systemd[1]: fwupd.service: Main process exited, code=dumped, status=11/SEGV
systemd[1]: fwupd.service: Failed with result 'core-dump'.
systemd[1]: Failed to start Firmware update daemon.

Offline

#2 2025-09-16 12:15:51

gromit
Administrator
From: Germany
Registered: 2024-02-10
Posts: 1,519
Website

Re: fwupd Will Not Start

Hm, works without issue here. Is the issue still present?

Also could you try to fetch the backtrace of the crash?
https://gitlab.archlinux.org/-/snippets/3742

Offline

#3 2025-09-16 14:32:10

kmr167
Member
Registered: 2025-09-16
Posts: 5

Re: fwupd Will Not Start

I am also having this issue. I attempted a backtrace, but no idea if I did it correctly:

#0  0x00007f50f99200f0 in ?? () from /usr/lib/libflashrom.so.1
#1  0x00007f50f992487b in flashrom_flash_probe_v2 () from /usr/lib/libflashrom.so.1
#2  0x00007f50fbdf6532 in ?? () from /usr/lib/fwupd-2.0.16/libfu_plugin_flashrom.so
#3  0x00007f50fe362849 in fu_plugin_runner_startup () from /usr/lib/fwupd-2.0.16/libfwupdplugin.so
#4  0x00007f50fe4d201a in fu_engine_load () from /usr/lib/fwupd-2.0.16/libfwupdengine.so
#5  0x0000561342b1d07e in ?? ()
#6  0x0000561342b226d2 in fu_daemon_setup ()
#7  0x0000561342b1963f in main ()

What other information can I provide to help troubleshoot?

Offline

#4 2025-09-16 14:50:47

gromit
Administrator
From: Germany
Registered: 2024-02-10
Posts: 1,519
Website

Re: fwupd Will Not Start

No the backtrace is lacking debug symbols .. Did you say yes / y when being asked about debuginfod?

Offline

#5 2025-09-16 14:58:32

kmr167
Member
Registered: 2025-09-16
Posts: 5

Re: fwupd Will Not Start

gromit wrote:

No the backtrace is lacking debug symbols .. Did you say yes / y when being asked about debuginfod?

No, it didn't ask me. Is there a way to force it to do that manually?

Offline

#6 2025-09-16 15:00:36

gromit
Administrator
From: Germany
Registered: 2024-02-10
Posts: 1,519
Website

Re: fwupd Will Not Start

what's the output of "echo $DEBUGINFOD_URLS" for you?

Offline

#7 2025-09-16 15:01:58

tekstryder
Member
Registered: 2013-02-14
Posts: 508

Re: fwupd Will Not Start

DEBUGINFOD_URLS="https://debuginfod.archlinux.org/" coredumpctl gdb 7943

It will always ask.

Offline

#8 2025-09-16 15:02:22

kmr167
Member
Registered: 2025-09-16
Posts: 5

Re: fwupd Will Not Start

gromit wrote:

what's the output of "echo $DEBUGINFOD_URLS" for you?

https://debuginfod.archlinux.org

Offline

#9 2025-09-16 15:11:05

kmr167
Member
Registered: 2025-09-16
Posts: 5

Re: fwupd Will Not Start

tekstryder wrote:
DEBUGINFOD_URLS="https://debuginfod.archlinux.org/" coredumpctl gdb 7943

It will always ask.

Well, I must be doing something very wrong then because it takes me straight to a (gdb) prompt and does not ask any questions.

This is the command I ran:

sudo coredumpctl gdb 20448

I also ran it as root (without sudo) but also was not asked any questions.

Offline

#10 2025-09-16 15:17:52

gromit
Administrator
From: Germany
Registered: 2024-02-10
Posts: 1,519
Website

Re: fwupd Will Not Start

Could you try setting "set debuginfod enabled on" manually? Also if you run as root please make sure that the environment variable is really set, i.e. by running "sudo DEBUGINFOD_URLS="https://debuginfod.archlinux.org/" coredumpctl gdb -1"

Offline

#11 2025-09-16 15:28:08

kmr167
Member
Registered: 2025-09-16
Posts: 5

Re: fwupd Will Not Start

gromit wrote:

Could you try setting "set debuginfod enabled on" manually? Also if you run as root please make sure that the environment variable is really set, i.e. by running "sudo DEBUGINFOD_URLS="https://debuginfod.archlinux.org/" coredumpctl gdb -1"

I really appreciate the guidance; that worked. Here is the backtrace:

#0  0x00007f50f99200f0 in probe_flash (mst=mst@entry=0x7f50f99fe320 <registered_masters>, startchip=startchip@entry=0, flash=flash@entry=0x0, chip_to_probe=chip_to_probe@entry=0x0, force=0) at ../flashrom/flashrom.c:1140
#1  0x00007f50f992487b in flashrom_flash_probe_v2 (flashrom_flashctx=0x0, all_matched_names=all_matched_names@entry=0x7ffda4377360, flashprog=<optimized out>, chip_name=chip_name@entry=0x0) at ../flashrom/libflashrom.c:390
#2  0x00007f50fbdf6532 in fu_flashrom_plugin_probe (self=0x5613647a7110, error=0x7ffda43773b0) at ../fwupd/plugins/flashrom/fu-flashrom-plugin.c:304
#3  fu_flashrom_plugin_startup (plugin=<optimized out>, progress=0x561364862260, error=0x7ffda43773b0) at ../fwupd/plugins/flashrom/fu-flashrom-plugin.c:408
#4  0x00007f50fe362849 in fu_plugin_runner_startup (self=self@entry=0x5613646d9950, progress=0x561364862260, error=error@entry=0x7ffda43774b8) at ../fwupd/libfwupdplugin/fu-plugin.c:867
#5  0x00007f50fe4d201a in fu_engine_plugins_startup (self=0x5613646805b0, progress=0x561364695c80) at ../fwupd/src/fu-engine.c:6160
#6  fu_engine_load (self=self@entry=0x5613646805b0, flags=<optimized out>, flags@entry=(FU_ENGINE_LOAD_FLAG_COLDPLUG | FU_ENGINE_LOAD_FLAG_REMOTES | FU_ENGINE_LOAD_FLAG_HWINFO | FU_ENGINE_LOAD_FLAG_BUILTIN_PLUGINS | FU_ENGINE_LOAD_FLAG_ENSURE_CLIENT_CERT | FU_ENGINE_LOAD_FLAG_EXTERNAL_PLUGINS | FU_ENGINE_LOAD_FLAG_DEVICE_HOTPLUG), progress=0x561364690840, error=error@entry=0x7ffda4377628) at ../fwupd/src/fu-engine.c:8754
#7  0x0000561342b1d07e in fu_dbus_daemon_setup (daemon=0x5613646806f0, socket_address=0x0, progress=0x56136468efc0, error=0x7ffda4377628) at ../fwupd/src/fu-dbus-daemon.c:2817
#8  0x0000561342b226d2 in fu_daemon_setup (self=self@entry=0x5613646806f0, socket_address=socket_address@entry=0x0, error=error@entry=0x7ffda4377628) at ../fwupd/src/fu-daemon.c:198
#9  0x0000561342b1963f in main (argc=<optimized out>, argv=<optimized out>) at ../fwupd/src/fu-main.c:184

Offline

#12 2025-09-16 15:33:29

gromit
Administrator
From: Germany
Registered: 2024-02-10
Posts: 1,519
Website

Re: fwupd Will Not Start

Could you post the same with "thread apply all backtrace full"?

Offline

#13 2025-09-16 15:35:51

bobber228
Member
Registered: 2025-09-15
Posts: 2

Re: fwupd Will Not Start

Alright, here's what I got from gdb.

#0  0x00007efc7a0a40f0 in probe_flash (mst=mst@entry=0x7efc7a182320 <registered_masters>, startchip=startchip@entry=0, flash=flash@entry=0x0, chip_to_probe=chip_to_probe@entry=0x0, force=0) at ../flashrom/flashrom.c:1140
        probe_func = <optimized out>
        chip = <optimized out>
        buses_common = <optimized out>
        tmp = <optimized out>
#1  0x00007efc7a0a887b in flashrom_flash_probe_v2 (flashrom_flashctx=0x0, all_matched_names=all_matched_names@entry=0x7fffb4387a20, flashprog=<optimized out>, chip_name=chip_name@entry=0x0) at ../flashrom/libflashrom.c:390
        second_flashctx = {chip = 0x0, physical_memory = 0, virtual_memory = 0, physical_registers = 0, virtual_registers = 0, mst = 0x0, layout = 0x0, default_layout = 0x0, flags = {force = false, force_boardmismatch = false, verify_after_write = false, verify_whole_chip = false, skip_unreadable_regions = false, skip_unwritable_regions = false}, address_high_byte = 0, in_4ba_mode = false, chip_restore_fn_count = 0, chip_restore_fn = {{func = 0x0, data = 0x0}, {func = 0x0, data = 0x0}, {func = 0x0, data = 0x0}, {func = 0x0, data = 0x0}}, progress_callback = 0x0, progress_state = {stage = FLASHROM_PROGRESS_READ, current = 0, total = 0, user_data = 0x0}, stage_progress = {{current = 0, total = 0}, {current = 0, total = 0}, {current = 0, total = 0}}, deprecated_progress_callback = 0x0, deprecated_progress_state = 0x0, sacrifice_ratio = 0}
        context_for_probing = 0x0
        i = 0
        startchip = 0
        all_matched_count = 0
        matched_names = 0x5638d9494c70
        ret = <optimized out>
#2  0x00007efc7a842532 in fu_flashrom_plugin_probe (self=0x5638d93c6360, error=0x7fffb4387a70) at ../fwupd/plugins/flashrom/fu-flashrom-plugin.c:304
        rc = <optimized out>
        all_matched_names = 0x0
#3  fu_flashrom_plugin_startup (plugin=<optimized out>, progress=0x5638d945a540, error=0x7fffb4387a70) at ../fwupd/plugins/flashrom/fu-flashrom-plugin.c:408
        flashrom_args = 0x0
        flashrom_prog = 0x7efc7a84417b "internal"
        guid = <optimized out>
        ctx = 0x5638d92a9550
        self = 0x5638d93c6360
#4  0x00007efc7ff0d849 in fu_plugin_runner_startup (self=self@entry=0x5638d9300810, progress=0x5638d945a540, error=error@entry=0x7fffb4387b78) at ../fwupd/libfwupdplugin/fu-plugin.c:867
        vfuncs = <optimized out>
        error_local = 0x0
        __func__ = "fu_plugin_runner_startup"
#5  0x00007efc8011e01a in fu_engine_plugins_startup (self=0x5638d92ad9e0, progress=0x5638d92bc520) at ../fwupd/src/fu-engine.c:6160
        error = 0x0
        plugin = <optimized out>
        i = 36
        plugins = 0x5638d92af860
#6  fu_engine_load (self=self@entry=0x5638d92ad9e0, flags=<optimized out>, flags@entry=(FU_ENGINE_LOAD_FLAG_COLDPLUG | FU_ENGINE_LOAD_FLAG_REMOTES | FU_ENGINE_LOAD_FLAG_HWINFO | FU_ENGINE_LOAD_FLAG_BUILTIN_PLUGINS | FU_ENGINE_LOAD_FLAG_ENSURE_CLIENT_CERT | FU_ENGINE_LOAD_FLAG_EXTERNAL_PLUGINS | FU_ENGINE_LOAD_FLAG_DEVICE_HOTPLUG), progress=0x5638d92b6b90, error=error@entry=0x7fffb4387ce8) at ../fwupd/src/fu-engine.c:8754
        plugin_uefi = <optimized out>
        quirks_flags = <optimized out>
        backends = 0x5638d92ac990
        plugins = 0x5638d92af860
        host_emulate = <optimized out>
        checksums_approved = 0x5638d92c6cc0
        checksums_blocked = 0x5638d92f8c40
        error_quirks = 0x0
        error_json_devices = 0x0
        error_local = 0x0
        __func__ = "fu_engine_load"
#7  0x00005638af93f07e in fu_dbus_daemon_setup (daemon=0x5638d92a0ef0, socket_address=0x0, progress=0x5638d92b5390, error=0x7fffb4387ce8) at ../fwupd/src/fu-dbus-daemon.c:2817
        self = 0x5638d92a0ef0
        engine = 0x5638d92ad9e0
#8  0x00005638af9446d2 in fu_daemon_setup (self=self@entry=0x5638d92a0ef0, socket_address=socket_address@entry=0x0, error=error@entry=0x7fffb4387ce8) at ../fwupd/src/fu-daemon.c:198
        klass = 0x5638d92a7f20
        priv = <optimized out>
        engine = 0x5638d92ad9e0
        machine_kind = 0x0
        timer_max_ms = <optimized out>
        progress = 0x5638d92b5390
        timer = 0x5638d92d0880
        __func__ = "fu_daemon_setup"
#9  0x00005638af93b63f in main (argc=<optimized out>, argv=<optimized out>) at ../fwupd/src/fu-main.c:184
        immediate_exit = 0
        timed_exit = 0
        socket_filename = <optimized out>
        options = {{long_name = 0x5638af946a41 "timed-exit", short_name = 0 '\000', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x7fffb4387ce0, description = 0x5638af946a16 "Exit after a small delay", arg_description = 0x0}, {long_name = 0x5638af946a4c "immediate-exit", short_name = 0 '\000', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x7fffb4387ce4, description = 0x5638af947390 "Exit after the engine has loaded", arg_description = 0x0}, {long_name = 0x0, short_name = 0 '\000', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x0, description = 0x0, arg_description = 0x0}}
        socket_address = 0x0
        error = 0x0
        argv0_file = 0x5638d92a64f0
        context = 0x5638d92b87c0
        daemon = 0x5638d92a0ef0
        argv0_monitor = 0x0
        memory_monitor = 0x0
quit

Offline

Board footer

Powered by FluxBB