getsolus
fwupdmgr not working "Failed to connect to daemon'
Please confirm there isn't an open report for this issue
- [x] I have searched through bug reports
Summary
fwupdmgr get-updates Failed to connect to daemon: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.fwupd': startup job failed
I used to be able to manually fetch updates. Now I cannot.
I did every debugging and log known to man here: https://discuss.getsol.us/d/11835-speaking-of-fwupd
Identical errors at github: https://github.com/fwupd/fwupd/issues/8251 (thanks harvey) looks like success rate for version 2.13 is around 50%...
We are a couple versions behind according to my research.
Thank you all.
Steps to reproduce
fwupdmgr get-updates
Expected result
Expected to see the usual output 1) [there are updates to install] or 2 [no firmware updates available.]
Actual result
fwupdmgr get-updates Failed to connect to daemon: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.fwupd': startup job failed
Environment
- [x] Is system up to date?
Repo
Shannon (stable)
Desktop Environment
Budgie
System details
$ inxi -b
System:
Host: budgie Kernel: 6.15.6-321.current arch: x86_64 bits: 64
Desktop: Budgie v: 10.9.2 Distro: Solus 4.7 endurance
Machine:
Type: Desktop System: LENOVO product: 10A8S09N00
v: ThinkCentre M93p serial:
Other comments
No response
Can confirm the commandfwupdmgr get-updatesworks in my backup Endeavour, and its service active and loaded in systemctl.
Neither of these (command or service) work on Solus yet. I wonder if there is any investigation I can do.
I've updated fwupd to 2.0.13 in b997cc8ee7037c3e668ce502a0b41285e1c5e3de, it will be included in the next sync. Let's see if that fixes the issue for you. We can do some more investigation if it does not.
I've updated fwupd to 2.0.13 in b997cc8, it will be included in the next sync. Let's see if that fixes the issue for you. We can do some more investigation if it does not.
Thank you for updating the package and for your reply, Will get back after the sync.
updated. rebooted a couple times. same:
fwupdmgr get-updates
Failed to connect to daemon: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.fwupd': startup job failed
sudo systemctl start fwupd
[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 journalctl -xeu fwupd.service
SupSupport: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit fwupd.service has begun execution.
░░
░░ The job identifier is 3235.
Aug 08 17:46:34 budgie fwupd[3227]: 00:46:34.623 FuPluginDell failed to parse system ID: cannot parse datastr>
Aug 08 17:46:34 budgie fwupd[3227]: 00:46:34.623 FuEngine tpm [dfb1a4db3787a1799167fb68010ef732c71041f9] >
Aug 08 17:46:34 budgie systemd[1]: fwupd.service: Main process exited, code=dumped, status=5/TRAP
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit fwupd.service has exited.
░░
░░ The process' exit code is 'dumped' and its exit status is 5.
Aug 08 17:46:34 budgie systemd[1]: fwupd.service: Failed with result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit fwupd.service has entered the 'failed' state with result 'core-dump'.
Aug 08 17:46:34 budgie systemd[1]: Failed to start fwupd.service - Firmware update daemon.
░░ Subject: A start job for unit fwupd.service has failed
░░ Defined-By: systemdport: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit fwupd.service has begun execution.
░░
░░ The job identifier is 3235.
Aug 08 17:46:34 budgie fwupd[3227]: 00:46:34.623 FuPluginDell failed to parse system ID: cannot parse datastr>
Aug 08 17:46:34 budgie fwupd[3227]: 00:46:34.623 FuEngine tpm [dfb1a4db3787a1799167fb68010ef732c71041f9] >
Aug 08 17:46:34 budgie systemd[1]: fwupd.service: Main process exited, code=dumped, status=5/TRAP
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit fwupd.service has exited.
░░
░░ The process' exit code is 'dumped' and its exit status is 5.
Aug 08 17:46:34 budgie systemd[1]: fwupd.service: Failed with result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit fwupd.service has entered the 'failed' state with result 'core-dump'.
Aug 08 17:46:34 budgie systemd[1]: Failed to start fwupd.service - Firmware update daemon.
░░ Subject: A start job for unit fwupd.service has failed
░░ Defined-By: systemd
**not an emergency by any stretch; backup OS has this covered (edit)
@brent111: can you try to start it again using sudo systemctl start fwupd and paste the output of sudo journalctl -b0 -u fwupd.service --no-pager? In addition, do you have a core dump of the crash? (coredumpctl list should show you).
re-start failed; here are all 3 outputs, thank you.
$ sudo systemctl start fwupd
[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 journalctl -b0 -u fwupd.service --no-pager
Aug 13 07:49:08 budgie systemd[1]: /usr/lib/systemd/system/fwupd.service:57: Failed to parse error number, ignoring: SIGSYS
Aug 13 07:49:08 budgie systemd[1]: /usr/lib/systemd/system/fwupd.service:57: Failed to parse error number, ignoring: SIGSYS
Aug 13 07:49:08 budgie systemd[1]: Starting fwupd.service - Firmware update daemon...
Aug 13 07:49:09 budgie fwupd[6760]: 14:49:09.404 FuPluginDell failed to parse system ID: cannot parse datastream
Aug 13 07:49:09 budgie fwupd[6760]: 14:49:09.407 FuEngine tpm [dfb1a4db3787a1799167fb68010ef732c71041f9] does not declare signed/unsigned payload -- perhaps add fu_device_add_flag(device, FWUPD_DEVICE_FLAG_UNSIGNED_PAYLOAD);
Aug 13 07:49:09 budgie systemd[1]: fwupd.service: Main process exited, code=dumped, status=5/TRAP
Aug 13 07:49:09 budgie systemd[1]: fwupd.service: Failed with result 'core-dump'.
Aug 13 07:49:09 budgie systemd[1]: Failed to start fwupd.service - Firmware update daemon.
Aug 13 07:49:09 budgie systemd[1]: Starting fwupd.service - Firmware update daemon...
Aug 13 07:49:10 budgie fwupd[6783]: 14:49:10.176 FuPluginDell failed to parse system ID: cannot parse datastream
$ sudo coredumpctl list
TIME PID UID GID SIG COREFILE EXE SIZE
Thu 2025-08-07 15:51:04 MST 1661 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Thu 2025-08-07 15:51:04 MST 1686 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Thu 2025-08-07 16:56:31 MST 6655 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Thu 2025-08-07 16:56:32 MST 6678 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Thu 2025-08-07 17:03:13 MST 1623 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Thu 2025-08-07 17:03:14 MST 1659 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Thu 2025-08-07 17:03:59 MST 1783 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Thu 2025-08-07 17:04:00 MST 1803 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 06:54:54 MST 1646 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 06:54:55 MST 1678 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 11:46:32 MST 20050 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 11:46:33 MST 20072 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 16:56:19 MST 48011 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.2M
Fri 2025-08-08 16:56:20 MST 48033 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 16:57:14 MST 1662 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 16:57:15 MST 1688 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 16:58:45 MST 2232 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 16:58:46 MST 2252 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 17:14:40 MST 14060 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.2M
Fri 2025-08-08 17:14:40 MST 14083 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 17:33:47 MST 1705 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 17:33:48 MST 1725 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 17:40:29 MST 2412 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Fri 2025-08-08 17:46:34 MST 3227 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Mon 2025-08-11 16:10:33 MST 27387 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Mon 2025-08-11 16:10:34 MST 27412 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:27:48 MST 24408 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:27:49 MST 24430 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:28:41 MST 24502 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:28:42 MST 24525 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:30:15 MST 24609 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:30:16 MST 24648 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:30:54 MST 24689 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:30:55 MST 24710 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:32:27 MST 24827 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:32:27 MST 24849 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:33:17 MST 24892 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 13:33:18 MST 24922 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 18:21:49 MST 44829 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Tue 2025-08-12 18:21:50 MST 44852 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Wed 2025-08-13 07:49:09 MST 6760 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Wed 2025-08-13 07:49:10 MST 6783 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Wed 2025-08-13 07:50:09 MST 6856 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Wed 2025-08-13 07:50:10 MST 6878 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Wed 2025-08-13 10:27:53 MST 21256 0 0 SIGTRAP present /usr/lib64/fwupd/fwupd/fwupd 1.0M
Well it has started to fail for me as well. This is my error:
Remote peer disconnected
Well it has started to fail for me as well. This is my error:
Remote peer disconnected
thanks for corroborating Me, still: ~ $ sudo fwupdmgr get-updates Failed to connect to daemon: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.fwupd': startup job failed ~ $ sudo fwupdmgr update Failed to connect to daemon: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.fwupd': startup job failed
SAME.
@brent111, @androidnisse: fwupd was updated to v2.0.14 yesterday. Does that update resolve the issue for you?
I get the same error with the newest version. I have restarted my computer.
Seeing the same issue. something about invalid pointer in the logs if it helps.
ov 03 13:55:39 avocato systemd[1]: Started fwupd.service - Firmware update daemon.
Nov 03 13:55:39 avocato fwupd[95750]: 13:55:39.332 FuEngine HSI attribute org.fwupd.hsi.Kernel.Lockdown (from linux_lockdown) had unknown result
Nov 03 14:00:29 avocato fwupd[95750]: free(): invalid pointer
Nov 03 14:00:29 avocato systemd[1]: fwupd.service: Main process exited, code=dumped, status=6/ABRT
Nov 03 14:00:29 avocato systemd[1]: fwupd.service: Failed with result 'core-dump'.
Nov 03 14:00:29 avocato systemd[1]: fwupd.service: Consumed 2.576s CPU time.
Nov 03 14:00:29 avocato systemd[1]: Starting fwupd.service - Firmware update daemon...
Nov 03 14:00:31 avocato fwupd[96982]: 14:00:31.099 FuUsbDevice failed to parse platform BOS descriptor: failed to parse: no supported platform version: did not find magic
Nov 03 14:00:31 avocato fwupd[96982]: 14:00:31.781 FuMain fwupd 2.0.16 ready for requests (locale en_GB.UTF-8)
Nov 03 14:00:31 avocato systemd[1]: Started fwupd.service - Firmware update daemon.
Nov 03 14:00:31 avocato fwupd[96982]: 14:00:31.814 FuEngine HSI attribute org.fwupd.hsi.Kernel.Lockdown (from linux_lockdown) had unknown result
@silkeh - fwupd core dumping is bad. Is there anything we can do here, or does this need to be handled by fwupd?
I see there's a new release 2.0.17, fresh off the presses yesterday
I've just updated fwupd to 2.0.17 in unstable, so it should be included in the next sync.
If the issue persists I would appreciate a coredump from someone affected. It can be extracted using coredumpctl. For example:
coredumpctl dump /usr/lib64/fwupd/fwupd/fwupd | zstd > fwupd.dump.zst
That should hopefully include enough information to find out if this is a Solus issue or an upstream issue.
I've just pushed a build to unstable that should fix this issue thanks to a coredump I received on Matrix. If you are on polaris (stable), please use the following command to install the updated package:
sudo eopkg install https://shared.getsol.us/silke/fwupd-2.0.17-37-1-x86_64.eopkg
And let me know if this resolves this issue for you.
I've just pushed a build to unstable that should fix this issue thanks to a coredump I received on Matrix. If you are on polaris (stable), please use the following command to install the updated package:
sudo eopkg install https://shared.getsol.us/silke/fwupd-2.0.17-37-1-x86_64.eopkgAnd let me know if this resolves this issu
it works thanks cut and paste a 32k pic of success and drag and drop etc etc all failure. but I got it back
Still broken for me with the latest update from @silkeh
fwupdmgr update
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade System Firmware from 1.46.1 to 1.47.1? ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ This stable release fixes the following issues: ║
║ ║
║ • This release contains security updates as disclosed in the Dell ║
║ Security Advisories. ║
║ • Fixed the issue where the Bloomberg Keyboard 5 does not work with Dell ║
║ systems. ║
║ • Fixed the issue where the system fan stops working and the system shuts ║
║ down. ║
║ • Fixed the issue where the AMT Selection is displayed after you disable ║
║ the Management Engine in the BIOS Setup. ║
║ ║
║ Latitude 5420 must remain plugged into a power source for the duration of ║
║ the update to avoid damage. ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: y
Unknown [ ]
Successfully uploaded report
Remote peer disconnected
[for the record I had success running
fwupdmgr get-updates
I tried nothing else]
Get the same issue on my Framework 13 with a recent update.
Perform operation? [Y|n]: y
Unknown [ ] Less than one minute remaining…
Remote peer disconnected
Looked at some logs and this came out of the fwupd daemon...
Nov 15 23:51:38 Retrospection systemd[1]: Starting fwupd.service - Firmware update daemon...
Nov 15 23:51:39 Retrospection fwupd[3641]: 05:51:39.391 FuEngine failed to add device /sys/devices/pci0000:00/0000:00>
Nov 15 23:51:39 Retrospection fwupd[3641]: 05:51:39.571 FuMain fwupd 2.0.17 ready for requests (locale en_US.utf8)
Nov 15 23:51:39 Retrospection systemd[1]: Started fwupd.service - Firmware update daemon.
Nov 15 23:53:15 Retrospection fwupd[3641]: free(): invalid pointer
Nov 15 23:53:15 Retrospection systemd-coredump[3843]: [🡕] Process 3641 (fwupd) of user 0 dumped core.
Stack trace of thread 3641:
#0 0x00007fcab0aa977b pthread_kill (libc.so.6 + 0xa977b)
#1 0x00007fcab0a47646 raise (libc.so.6 + 0x47646)
#2 0x00007fcab0a29286 abort (libc.so.6 + 0x29286)
#3 0x00007fcab0a2a4b8 n/a (libc.so.6 + 0x2a4b8)
#4 0x00007fcab0ab3de5 n/a (libc.so.6 + 0xb3de5)
#5 0x00007fcab0ab3e01 n/a (libc.so.6 + 0xb3e01)
#6 0x00007fcab14d0159 fu_uefi_get_esp_path_for_os (libfwupdengine.so + 0xd>
#7 0x00007fcab14cbbe3 n/a (libfwupdengine.so + 0xcbbe3)
#8 0x00007fcab13789fc fu_plugin_runner_write_firmware (libfwupdplugin.so +>
#9 0x00007fcab14a3372 n/a (libfwupdengine.so + 0xa3372)
#10 0x00007fcab14a7005 fu_engine_install_blob (libfwupdengine.so + 0xa7005)
Stack trace of thread 3646:
#0 0x00007fcab0b36dad syscall (libc.so.6 + 0x136dad)
#1 0x00007fcab0d2572d n/a (libglib-2.0.so.0 + 0xc472d)
#2 0x00007fcab0d23877 n/a (libglib-2.0.so.0 + 0xc2877)
#3 0x00007fcab0aa783e n/a (libc.so.6 + 0xa783e)
#4 0x00007fcab0b39544 __clone (libc.so.6 + 0x139544)
Stack trace of thread 3645:
#0 0x00007fcab0aafd22 n/a (libc.so.6 + 0xafd22)
#1 0x00007fcab0aa3ab8 n/a (libc.so.6 + 0xa3ab8)
#2 0x00007fcab0b2ac03 ppoll (libc.so.6 + 0x12ac03)
#3 0x00007fcab0ce291f n/a (libglib-2.0.so.0 + 0x8191f)
#4 0x00007fcab0ce2d65 n/a (libglib-2.0.so.0 + 0x81d65)
#5 0x00007fcab0d23877 n/a (libglib-2.0.so.0 + 0xc2877)
#6 0x00007fcab0aa783e n/a (libc.so.6 + 0xa783e)
#7 0x00007fcab0b39544 __clone (libc.so.6 + 0x139544)
Stack trace of thread 3647:
#0 0x00007fcab0aafd22 n/a (libc.so.6 + 0xafd22)
#1 0x00007fcab0aa3ab8 n/a (libc.so.6 + 0xa3ab8)
#2 0x00007fcab0b2ac03 ppoll (libc.so.6 + 0x12ac03)
#3 0x00007fcab0ce291f n/a (libglib-2.0.so.0 + 0x8191f)
#4 0x00007fcab0ce2bb7 g_main_loop_run (libglib-2.0.so.0 + 0x81bb7)
#5 0x00007fcab0f7fc60 n/a (libgio-2.0.so.0 + 0x17fc60)
#6 0x00007fcab0d23877 n/a (libglib-2.0.so.0 + 0xc2877)
#7 0x00007fcab0aa783e n/a (libc.so.6 + 0xa783e)
#8 0x00007fcab0b39544 __clone (libc.so.6 + 0x139544)
ELF object binary architecture: AMD x86-64
Nov 15 23:53:15 Retrospection systemd[1]: fwupd.service: Main process exited, code=dumped, status=6/ABRT
Nov 15 23:53:15 Retrospection systemd[1]: fwupd.service: Failed with result 'core-dump'.
Nov 15 23:53:15 Retrospection systemd[1]: fwupd.service: Consumed 1.348s CPU time, 263.3M memory peak.
Nov 15 23:53:15 Retrospection systemd[1]: Starting fwupd.service - Firmware update daemon...
Nov 15 23:53:16 Retrospection fwupd[3856]: 05:53:16.171 FuMain fwupd 2.0.17 ready for requests (locale en_US.utf8)
Nov 15 23:53:16 Retrospection systemd[1]: Started fwupd.service - Firmware update daemon.
Fwupd 2.0.18 should be available in unstable shortly. I'm still very much interested in core dumps for those still seeing crashes with 2.0.18, see this comment for instructions.
Well it does not crash but it does not update. Would a core dump help here?
~ fwupdmgr update ✔ 17:15:29
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade System Firmware from 1.46.1 to 1.49.0? ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ This stable release fixes the following issues: ║
║ ║
║ • Fixed the issue where the system would reboot or shut down when ║
║ plugging or unplugging a Type-C monitor. ║
║ ║
║ Latitude 5420 must remain plugged into a power source for the duration of ║
║ the update to avoid damage. ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: y
Unknown [ ]
Successfully uploaded report
Remote peer disconnected
Well it does not crash but it does not update. Would a core dump help here?
~ fwupdmgr update ✔ 17:15:29
╔══════════════════════════════════════════════════════════════════════════════╗ ║ Upgrade System Firmware from 1.46.1 to 1.49.0? ║ ╠══════════════════════════════════════════════════════════════════════════════╣ ║ This stable release fixes the following issues: ║ ║ ║ ║ • Fixed the issue where the system would reboot or shut down when ║ ║ plugging or unplugging a Type-C monitor. ║ ║ ║ ║ Latitude 5420 must remain plugged into a power source for the duration of ║ ║ the update to avoid damage. ║ ╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: y Unknown [ ] Successfully uploaded report Remote peer disconnected
Same here