Snap mount problem

[sammndl]

All issues related to Garuda Linux and its assistance

I am facing this issue in Garuda Linux, please help me out

sudo snap install photoscape
[sudo] password for sam_mndl:
error: cannot perform the following tasks:

• Mount snap "snapd" (11036) ([start snap-snapd-11036.mount] failed with exit status 1: Job failed. See "journalctl -xe" for details.
  )

sudo journalctl -xe
Feb 09 19:35:50 DarkLord audit: BPF prog-id=415 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=416 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=417 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=418 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=419 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=420 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=421 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=422 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=423 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=424 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=425 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=426 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=427 op=LOAD
Feb 09 19:35:50 DarkLord audit: BPF prog-id=428 op=LOAD
Feb 09 19:35:50 DarkLord snapd[692]: taskrunner.go:271: [change 16 "Mount snap "snapd" (11036)" task] failed: [start snap-snapd-11036.mount] faile>
Feb 09 19:35:52 DarkLord systemd[1]: snapd.service: Got notification message from PID 68110, but reception only permitted for main PID 692
Feb 09 19:35:54 DarkLord snapd[692]: handlers.go:496: Reported install problem for "snapd" as Crash report successfully submitted.
Feb 09 19:35:55 DarkLord auto-cpufreq[68132]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 09 19:35:55 DarkLord auto-cpufreq[68132]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 09 19:35:55 DarkLord auto-cpufreq[68132]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 09 19:35:55 DarkLord auto-cpufreq[68132]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 09 19:35:55 DarkLord sudo[67365]: pam_unix(sudo:session): session closed for user root
Feb 09 19:35:55 DarkLord audit[67365]: USER_END pid=67365 uid=1000 auid=1000 ses=5 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit>
Feb 09 19:35:55 DarkLord audit[67365]: CRED_DISP pid=67365 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_failloc>
Feb 09 19:35:55 DarkLord kernel: kauditd_printk_skb: 126 callbacks suppressed
Feb 09 19:35:55 DarkLord kernel: audit: type=1106 audit(1612879555.816:1014): pid=67365 uid=1000 auid=1000 ses=5 msg='op=PAM:session_close grantors=>
Feb 09 19:35:55 DarkLord kernel: audit: type=1104 audit(1612879555.816:1015): pid=67365 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_fa>
Feb 09 19:36:02 DarkLord auto-cpufreq[68603]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 09 19:36:02 DarkLord auto-cpufreq[68603]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 09 19:36:02 DarkLord auto-cpufreq[68603]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 09 19:36:02 DarkLord auto-cpufreq[68603]: /usr/bin/cpufreqctl.auto-cpufreq: line 267: echo: write error: Invalid argument
Feb 09 19:36:09 DarkLord dbus-daemon[499]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.se>
Feb 09 19:36:09 DarkLord dbus-daemon[499]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freed>
Feb 09 19:36:09 DarkLord sudo[68667]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not fo>
Feb 09 19:36:09 DarkLord audit[68667]: USER_ACCT pid=68667 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acc>
Feb 09 19:36:09 DarkLord audit[68667]: CRED_REFR pid=68667 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam>
Feb 09 19:36:09 DarkLord sudo[68667]: sam_mndl : TTY=pts/0 ; PWD=/home/sam_mndl ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Feb 09 19:36:09 DarkLord kernel: audit: type=1101 audit(1612879569.522:1016): pid=68667 uid=1000 auid=1000 ses=5 msg='op=PAM:accounting grantors=pam>
Feb 09 19:36:09 DarkLord kernel: audit: type=1110 audit(1612879569.522:1017): pid=68667 uid=1000 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_fa>
Feb 09 19:36:09 DarkLord sudo[68667]: pam_unix(sudo:session): session opened for user root(uid=0) by sam_mndl(uid=1000)
Feb 09 19:36:09 DarkLord kernel: audit: type=1105 audit(1612879569.524:1018): pid=68667 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=p>
Feb 09 19:36:09 DarkLord audit[68667]: USER_START pid=68667 uid=1000 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permi>

what to do?

[petsam]

@sammndl

what to do?

I am afraid you have to read a book, or a wiki. It's in the rules of the game.
Reporting bugs | Garuda Linux wiki
How to search for solutions the right way | Garuda Linux wiki

[dr460nf1r3]

Also the search function appearently has not been used..

Snapd issues

We decided to drop it lately as we have Chaotic-AUR. That doesnt mean it wont work at all, you will have to build snapd yourself from AUR and do the work yourself then. Anyway, even before this happened snapd & flatpak were clearly flagged unsupported in the wiki for quite some time now Might be time to switch to an available alternative?

[sammndl]

Thank you for your reply. I am using Linux base OS from last 12 Years. Mainly I used Fedora,Ubuntu,OpenSusa, and I was using Manjaro Linux from last 3 years. i recently switch too your Garuda Dr4g0n. And I like it. you have done a lot of work on it. keep on.

[sammndl]

sudo rm /snap

And this solved my problem. thanks.