Job for snapd.service failed because the control process exited with error code. See “systemctl status snapd.service” and “journalctl -xeu snapd.service” for details.
I am having an issue in ubunto with the above error message. Please help
When you run that command is there any relevant error messages displayed?
Only message I receive is: Job for snapd.service failed because the control process exited with error code. See “systemctl status snapd.service” and “journalctl -xeu snapd.service” for details.
Well, that message asks you to run two commands, it would be helpful if you do that and provide the output of them here.
First run systemctl status snapd.service, copy/paste the output here (make sure to add three backticks ``` above and below the pasted text so the formatting stays intact).
Second run the journalctl line it gave you and paste it here the same way, that should hopefully give some information about what went wrong…
The first command gave me the following output:
syystemctl status snapd.service
hamsi@ilhan-Latitude-5290:/$ systemctl status snapd.service × snapd.service - Snap Daemon Loaded: loaded (/lib/systemd/system/snapd.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2023-09-13 17:36:31 BST; 53min left TriggeredBy: × snapd.socket Main PID: 1319 (code=exited, status=1/FAILURE) CPU: 273ms
The Second output is:
journalctl
Hint: You are currently not seeing messages from other users and the system.
Users in groups ‘adm’, ‘systemd-journal’ can see all messages.
Pass -q to turn off this notice.
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-12
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: Linux version 6.2.0-20-generic (buildd@lcy02-amd64-035) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (>
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=a5dec396-a422-494b-9107-010043845d27 ro quiet splash vt.h>
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: KERNEL supported cpus:
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: Intel GenuineIntel
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: AMD AuthenticAMD
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: Hygon HygonGenuine
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: Centaur CentaurHauls
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: zhaoxin Shanghai
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Supporting XSAVE feature 0x004: ‘AVX registers’
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Supporting XSAVE feature 0x008: ‘MPX bounds registers’
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Supporting XSAVE feature 0x010: ‘MPX CSR’
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using ‘compacted’ format.
lines 1-18…skipping…
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-12
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: Linux version 6.2.0-20-generic (buildd@lcy02-amd64-035) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (>
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=a5dec396-a422-494b-9107-010043845d27 ro quiet splash vt.h>
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: KERNEL supported cpus:
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: Intel GenuineIntel
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: AMD AuthenticAMD
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: Hygon HygonGenuine
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: Centaur CentaurHauls
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: zhaoxin Shanghai
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Supporting XSAVE feature 0x004: ‘AVX registers’
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Supporting XSAVE feature 0x008: ‘MPX bounds registers’
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Supporting XSAVE feature 0x010: ‘MPX CSR’
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using ‘compacted’ format.
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: signal: max sigframe size: 2032
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-provided physical RAM map:
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000b91d3fff] usable
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000b91d4000-0x00000000b91d4fff] ACPI NVS
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000b91d5000-0x00000000b91d5fff] reserved
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000b91d6000-0x00000000c8d59fff] usable
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000c8d5a000-0x00000000ca4d6fff] reserved
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000ca4d7000-0x00000000ca51ffff] ACPI data
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000ca520000-0x00000000cae94fff] ACPI NVS
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000cae95000-0x00000000cb5fefff] reserved
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000cb5ff000-0x00000000cb5fffff] usable
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000cb600000-0x00000000cf7fffff] reserved
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Jul 31 14:44:11 ilhan-Latitude-5290 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
lines 1-38
1 Like
Also the same issue with snapd not working. Details are the same. Everything happened after kernel update / chmod 777 while trouble shooting. The outcome was identical. UBUNTU SERVER 24.04.3 (now with kernel 15.5.85
Hoping for assistance from the community.
anyone has an idea about the root cause of this issue.
Can you re-run the 2 commands but with 2 changes.
-
Can you follow ogra’s guidelines on posting the output? He mentioned using the triple backticks. That makes the output formatting easier for us to read because it uses a monospaced font and the line breaks are preserved. I doube anyone wants to read through blocks of serif text with no line breaks.
-
add
sudoin front of those commands. You’re not seeing helpful debug messages because you’re not part of the admin (adm) group.
So, the commands would be
sudo systemctl status snapd.service
and
sudo journalctl -xeu snapd.service
Thanks
My apologies for posting to a 2-year old thread, and if there was some other one (that I haven’t found) that addresses this issue. If there is one, I will be happy to move my question there.
Having said that, I am still having this issue on OpenSuse 15.6 Leap. I followed the instrucutions here: https://snapcraft.io/docs/installing-snap-on-opensuse up to sudo zypper install snapd. This last command gives me the error message:
Job for snapd.service failed because the control process exited with error code.
See "systemctl status snapd.service" and "journalctl -xeu snapd.service" for details.
Output of the sudo systemctl status snapd.service command:
× snapd.service - Snap Daemon
Loaded: loaded (/usr/lib/systemd/system/snapd.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Thu 2025-07-03 15:16:34 EDT; 3min 55s ago
TriggeredBy: × snapd.socket
Process: 14120 ExecStart=/usr/libexec/snapd/snapd (code=exited, status=1/FAILURE)
Main PID: 14120 (code=exited, status=1/FAILURE)
CPU: 140ms
Jul 03 15:16:34 kitchencomputer snapd[14120]: daemon.go:353: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jul 03 15:16:34 kitchencomputer snapd[14120]: backends.go:91: AppArmor status: apparmor is enabled but some kernel features are missing: dbus, n>
Jul 03 15:16:34 kitchencomputer snapd[14120]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exe>
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Failed with result 'exit-code'.
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Start request repeated too quickly.
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Failed with result 'exit-code'.
Jul 03 15:16:34 kitchencomputer systemd[1]: Failed to start Snap Daemon.
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Triggering OnFailure= dependencies.
lines 1-18/18 (END)
Output of sudo journalctl -xeu snapd.service:
Jul 03 15:16:33 kitchencomputer systemd[1]: Starting Snap Daemon...
░░ Subject: A start job for unit snapd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit snapd.service has begun execution.
░░
░░ The job identifier is 8272.
Jul 03 15:16:33 kitchencomputer snapd[14120]: overlord.go:284: Acquiring state lock file
Jul 03 15:16:33 kitchencomputer snapd[14120]: overlord.go:289: Acquired state lock file
Jul 03 15:16:33 kitchencomputer snapd[14120]: daemon.go:250: started snapd/2.68.3 (series 16; classic; devmode) opensuse-leap/15.6 (amd64) linux>
Jul 03 15:16:34 kitchencomputer snapd[14120]: daemon.go:353: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
Jul 03 15:16:34 kitchencomputer snapd[14120]: backends.go:91: ==AppArmor status: apparmor is enabled but some kernel features are missing: dbus, network==
Jul 03 15:16:34 kitchencomputer snapd[14120]: ==cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap-seccomp: no such file or directory]==
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit snapd.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit snapd.service has entered the 'failed' state with result 'exit-code'.
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit snapd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Start request repeated too quickly.
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit snapd.service has entered the 'failed' state with result 'exit-code'.
Jul 03 15:16:34 kitchencomputer systemd[1]: Failed to start Snap Daemon.
░░ Subject: A start job for unit snapd.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit snapd.service has finished with a failure.
░░
░░ The job identifier is 8272 and the job result is failed.
Jul 03 15:16:34 kitchencomputer systemd[1]: snapd.service: Triggering OnFailure= dependencies.
lines 1096-1146/1146 (END)
A few things to mention:
kitchencomputeris the name of my machine- I added The double ‘=’ signs on lines 13 and 14 in the hope that the error message might get highlighted in markup.
- I read somewhere else that the firewall could be an issue. So, against my better judgement, I temporarily disabled the firewall and tried running the commands but with the same result.
Any help or pointers are much appreciated. Thanks in advance.
Well, this thread is for a problem on Ubuntu, you should simply have opened a fresh thread and also should have put your distro in the topic, that way @zyga (who works on cross distribution support in snapd) would have seen it immediately…
@ogra - thank you for your response.
Did I have to provide more information beyond that as far as distro is concerned? Please let me know. In the mean time, I will go look for a thread specific to OpenSuse. I figured I would post it here since it was the same error with snap as the OP had reported, and it looked like it was unresolved. I didn’t realize it was Ubuntu-specific. My apologies.
@zyga - will you be able to help me by pointing the right place to post my question? I will also search for what might be a relevant thread. If not, I will open a new one as @ogra suggested, and and reference this Thank you.
It looks to me you have installed a Tumbleweed package, rather than the one for leap.
Can you attach the output of zypper lr -d ? Have another look at the instructions at Installing snap on openSUSE | Snapcraft documentation which mentions to replace Tumbleweed with Leap_15.6
1 Like
Ah! I am blind 
!! (Kicking myself)
Thank you @mborzecki1! I cannot believe that I missed that part. You were right, I was indeed using Tumbleweed. Can I ask you, for my own learning, what it was in the error message snippet you pasted in your response that tipped you off to the issue?
Here’s the output that you asked you, not that it matters now. You had already identified the issue. snappy is the 3rd one from the bottom. I have fixed it now and was able to install and enable the service without any issue. Now, onto installing the actual apps that I needed from the Snap Store 
.
# | Alias | Name | Enabled | GPG Check | Refresh | Keep | Priority | Type | URI | Service
---+-----------------------------+----------------------------------------------------------------------+---------+-----------+---------+------+----------+--------+-------------------------------------------------------------------------------+--------
1 | MEGAsync | MEGAsync | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://mega.nz/linux/repo/openSUSE_Leap_15.6/ |
2 | Packman | Packman | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.6/ |
3 | X11_Utilities | X11 Utilities x86_64 (15.6) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.opensuse.org/repositories/X11:/Utilities/15.6/ |
4 | X11_Utils | X11 Utils x86_64 | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://download.opensuse.org/repositories/X11:Utilities/15.6/ |
5 | X11_XOrg | X.Org development (openSUSE_Tumbleweed) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Tumbleweed/ |
6 | brave-browser | Brave Browser | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://brave-browser-rpm-release.s3.brave.com/x86_64 |
7 | code | Visual Studio Code | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://packages.microsoft.com/yumrepos/vscode |
8 | home_pbek_QOwnNotes | QOwnNotes (15.6) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.opensuse.org/repositories/home:/pbek:/QOwnNotes/15.6/ |
9 | openSUSE-Leap-15.6-1 | openSUSE-Leap-15.6-1 | No | ---- | ---- | - | 99 | rpm-md | hd:/?device=/dev/disk/by-id/dm-name-ventoy |
10 | packages-microsoft-com-prod | Microsoft Production | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://packages.microsoft.com/opensuse/15/prod/ |
11 | repo-backports-debug-update | Update repository of openSUSE Backports (Debug) | No | ---- | ---- | - | 99 | N/A | http://download.opensuse.org/update/leap/15.6/backports_debug/ |
12 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://download.opensuse.org/update/leap/15.6/backports/ |
13 | repo-debug | Debug Repository | No | ---- | ---- | - | 99 | N/A | http://download.opensuse.org/debug/distribution/leap/15.6/repo/oss/ |
14 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ---- | - | 99 | N/A | http://download.opensuse.org/debug/distribution/leap/15.6/repo/non-oss/ |
15 | repo-debug-update | Update Repository (Debug) | No | ---- | ---- | - | 99 | N/A | http://download.opensuse.org/debug/update/leap/15.6/oss/ |
16 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | ---- | ---- | - | 99 | N/A | http://download.opensuse.org/debug/update/leap/15.6/non-oss/ |
17 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.6/repo/non-oss/ |
18 | repo-openh264 | Open H.264 Codec (openSUSE Leap) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Leap/ |
19 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.6/repo/oss/ |
20 | repo-sle-debug-update | Update repository with updates from SUSE Linux Enterprise 15 (Debug) | No | ---- | ---- | - | 99 | N/A | http://download.opensuse.org/debug/update/leap/15.6/sle/ |
21 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://download.opensuse.org/update/leap/15.6/sle/ |
22 | repo-source | Source Repository | No | ---- | ---- | - | 99 | N/A | http://download.opensuse.org/source/distribution/leap/15.6/repo/oss/ |
23 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://download.opensuse.org/update/leap/15.6/oss |
24 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://download.opensuse.org/update/leap/15.6/non-oss/ |
25 | snappy | snappy | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.opensuse.org/repositories/system:/snappy/openSUSE_Tumbleweed |
26 | sublime-text | Sublime Text - x86_64 - Stable | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.sublimetext.com/rpm/stable/x86_64 |
27 | warpdotdev | warpdotdev | Yes | ( p) Yes | No | - | 99 | rpm-md | https://releases.warp.dev/linux/rpm/stable |
No worries. I’ve updated the installation instructions to make them clearer. Hopefully we’ll avoid more issues like that in the future.
@mborzecki1 - Do you know how I can mark your response as the solution (at least to my issue - can’t speak for the OP). Thanks!
There is a little square with a check mark inside it underneath each post (next to the heart), if you click on it under the specific post you consider the solution it will be marked as such.