Jump to content

Google drive automatyczne montowanie po uruchomieniu systemu.


Recommended Posts

W dniu 8.02.2022 o 19:07, sunrise napisał:

Google wie :)

Jeżeli naprawdę chcesz mieć dostęp po uruchomieniu systemu to proponuję się zapoznać z https://www.xmodulo.com/mount-google-drive-linux.html

 

Zapoznałem się i przeszedłem przez całą instrukcję - robiąc tak jak pisze. Dziękuję bardzo. Mam jeszcze jedno pytanie. Bo obecnie po zainstalowaniu tego mam tak: obraz.png.f9514e8e5041126ff8bb0b1f00e4449c.png

Chciałbym aby 1 - googledrive nie było, a 2 się montowała automatem tak jak 1.

Ewentualnie jak usunąć stąd 2?

 

Link to comment
Share on other sites

Chciałem ustawić automatyczne montowanie i po wpisaniu komendy:

sudo systemctl start google-drive
Job for google-drive.service failed because the control process exited with error code.
See "systemctl status google-drive.service" and "journalctl -xeu google-drive.service" for details.

((_niewiem_ → nie wiem) ORT czy ustawiłem dobrze w vi swoją konfigurację:

- zmieniłem nazwę użytownika dan na nazwę użytkownika w fedorze

- w grupie ustawiłem tak samo

- reszty nie zmieniałem

[Unit]
Description=FUSE filesystem over Google Drive
After=network.target

[Service]
User=user //zamiast słowa user wpisałem nazwę użytkownika w systemie fedora
Group=user 
ExecStart=/home/user/.opam/default/bin/google-drive-ocamlfuse -label default /home/user/googledrive
ExecStop=fusermount -u /home/user/googledrive
Restart=always
Type=forking

[Install]
WantedBy=multi-user.target
Alias=google-drive.service
sudo systemctl status start google-drive
Unit start.service could not be found.
× google-drive.service - FUSE filesystem over Google Drive
     Loaded: loaded (/etc/systemd/system/google-drive.service; disabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Thu 2022-02-17 18:10:27 CET; 11s ago
    Process: 46386 ExecStart=/home/dan/.opam/default/bin/google-drive-ocamlfuse -label default /home/dan/googledrive (code=exited, status=203/EXEC)
        CPU: 3ms

lut 17 18:10:27 fedora systemd[1]: google-drive.service: Scheduled restart job, restart counter is at 5.
lut 17 18:10:27 fedora systemd[1]: Stopped FUSE filesystem over Google Drive.
lut 17 18:10:27 fedora systemd[1]: google-drive.service: Start request repeated too quickly.
lut 17 18:10:27 fedora systemd[1]: google-drive.service: Failed with result 'exit-code'.
lut 17 18:10:27 fedora systemd[1]: Failed to start FUSE filesystem over Google Drive.
journalctl -xeu google-drive.service
lut 17 18:10:27 fedora systemd[1]: Failed to start FUSE filesystem over Google Drive.
░░ Subject: Zadanie uruchamiania dla jednostki google-drive.service się nie powiodło
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Zadanie uruchamiania dla jednostki google-drive.service zostało ukończone z niepowodzeniem.
░░ 
░░ Identyfikator zadania: 10236, wynik zadania: failed.
lut 17 18:10:27 fedora systemd[1]: google-drive.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Zaplanowano automatyczne ponowne uruchamianie jednostki
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ W wyniki skonfigurowania ustawienia Restart= zaplanowano automatyczne ponowne
░░ uruchamianie jednostki google-drive.service.
lut 17 18:10:27 fedora systemd[1]: Stopped FUSE filesystem over Google Drive.
░░ Subject: Ukończono zadanie zatrzymania dla jednostki google-drive.service
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Ukończono zadanie zatrzymania dla jednostki google-drive.service.
░░ 
░░ Identyfikator zadania: 10350, wynik zadania: done.
lut 17 18:10:27 fedora systemd[1]: google-drive.service: Start request repeated too quickly.
lut 17 18:10:27 fedora systemd[1]: google-drive.service: Failed with result 'exit-code'.
░░ Subject: Jednostka się nie powiodła
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Jednostka google-drive.service przeszła do stanu „failed” (niepowodzenia)
░░ z wynikiem „exit-code”.
lut 17 18:10:27 fedora systemd[1]: Failed to start FUSE filesystem over Google Drive.
░░ Subject: Zadanie uruchamiania dla jednostki google-drive.service się nie powiodło
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Zadanie uruchamiania dla jednostki google-drive.service zostało ukończone z niepowodzeniem.
░░ 
░░ Identyfikator zadania: 10350, wynik zadania: failed.

 

Proszę o pomoc.

Link to comment
Share on other sites

55 minut temu, fraktal15 napisał:

Chciałem ustawić automatyczne montowanie i po wpisaniu komendy:

W jednej konsoli jako root wpisz polecenie

journalctl -f

A w drugiej wystartuj usługę i popatrz jaki się pojawią komunikaty, może coś z selinuxem

Link to comment
Share on other sites

4 minuty temu, sunrise napisał:

W jednej konsoli jako root wpisz polecenie

journalctl -f

A w drugiej wystartuj usługę i popatrz jaki się pojawią komunikaty, może coś z selinuxem

Wynik:

[[email protected] ~]$ journalctl -f
lut 17 18:49:10 fedora gnome-shell[1756]: Can't update stage views actor <dash-blurred-background>[<StWidget>:0x556ec4df8eb0] is on because it needs an allocation.
lut 17 18:49:27 fedora systemd[1]: systemd-hostnamed.service: Deactivated successfully.
lut 17 18:49:27 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:49:27 fedora audit: BPF prog-id=0 op=UNLOAD
lut 17 18:49:27 fedora audit: BPF prog-id=0 op=UNLOAD
lut 17 18:50:10 fedora systemd[1604]: Started Application launched by gnome-shell.
lut 17 18:50:10 fedora systemd[1604]: Started Application launched by gnome-shell.
lut 17 18:50:10 fedora systemd[1604]: Starting GNOME Terminal Server...
lut 17 18:50:10 fedora systemd[1604]: Started GNOME Terminal Server.
lut 17 18:50:11 fedora systemd[1604]: Started VTE child process 53787 launched by gnome-terminal-server process 53766.
lut 17 18:50:41 fedora gnome-shell[1756]: JS ERROR: Exception in callback for signal: activate-window: TypeError: window is null
                                          [email protected]:///org/gnome/shell/ui/main.js:670:30
                                          popupMenu/<@/home/panekadamek/.local/share/gnome-shell/extensions/[email protected]/appIcons.js:387:22
                                          [email protected]:///org/gnome/gjs/modules/core/_signals.js:114:47
                                          _rebuildMenu/<@/home/panekadamek/.local/share/gnome-shell/extensions/[email protected]/appIcons.js:1063:26
                                          [email protected]:///org/gnome/shell/ui/popupMenu.js:191:14
                                          [email protected]:///org/gnome/shell/ui/popupMenu.js:138:14
lut 17 18:50:41 fedora systemd[1604]: Started Application launched by gnome-shell.
lut 17 18:50:42 fedora systemd[1604]: Started Application launched by gnome-shell.
lut 17 18:50:42 fedora systemd[1604]: Started VTE child process 53840 launched by gnome-terminal-server process 53766.
lut 17 18:50:45 fedora audit: BPF prog-id=343 op=LOAD
lut 17 18:50:45 fedora systemd[1]: Starting Fingerprint Authentication Daemon...
lut 17 18:50:45 fedora systemd[1]: Started Fingerprint Authentication Daemon.
lut 17 18:50:45 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:50:48 fedora audit[53873]: USER_AUTH pid=53873 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_usertype,pam_localuser,pam_unix acct="panekadamek" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
lut 17 18:50:48 fedora audit[53873]: USER_ACCT pid=53873 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="panekadamek" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
lut 17 18:50:48 fedora audit[53873]: USER_CMD pid=53873 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/home/panekadamek" cmd=73797374656D63746C20737461727420676F6F676C652D6472697665 exe="/usr/bin/sudo" terminal=pts/1 res=success'
lut 17 18:50:48 fedora sudo[53873]: panekadamek : TTY=pts/1 ; PWD=/home/panekadamek ; USER=root ; COMMAND=/usr/bin/systemctl start google-drive
lut 17 18:50:48 fedora audit[53873]: CRED_REFR pid=53873 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
lut 17 18:50:48 fedora sudo[53873]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
lut 17 18:50:48 fedora audit[53873]: USER_START pid=53873 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
lut 17 18:50:48 fedora systemd[1]: Starting FUSE filesystem over Google Drive...
lut 17 18:50:48 fedora audit[53884]: AVC avc:  denied  { execute } for  pid=53884 comm="(camlfuse)" name="google-drive-ocamlfuse" dev="sda3" ino=2083703 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0
lut 17 18:50:48 fedora systemd[53884]: google-drive.service: Failed to locate executable /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse: Permission denied
lut 17 18:50:48 fedora systemd[53884]: google-drive.service: Failed at step EXEC spawning /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse: Permission denied
lut 17 18:50:48 fedora systemd[1]: google-drive.service: Control process exited, code=exited, status=203/EXEC
lut 17 18:50:48 fedora systemd[1]: google-drive.service: Failed with result 'exit-code'.
lut 17 18:50:48 fedora systemd[1]: Failed to start FUSE filesystem over Google Drive.
lut 17 18:50:48 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
lut 17 18:50:48 fedora sudo[53873]: pam_unix(sudo:session): session closed for user root
lut 17 18:50:48 fedora audit[53873]: USER_END pid=53873 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
lut 17 18:50:48 fedora audit[53873]: CRED_DISP pid=53873 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
lut 17 18:50:48 fedora systemd[1]: google-drive.service: Scheduled restart job, restart counter is at 1.
lut 17 18:50:48 fedora systemd[1]: Stopped FUSE filesystem over Google Drive.
lut 17 18:50:48 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:50:48 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:50:48 fedora systemd[1]: Starting FUSE filesystem over Google Drive...
lut 17 18:50:48 fedora audit[53890]: AVC avc:  denied  { execute } for  pid=53890 comm="(camlfuse)" name="google-drive-ocamlfuse" dev="sda3" ino=2083703 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0
lut 17 18:50:48 fedora systemd[53890]: google-drive.service: Failed to locate executable /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse: Permission denied
lut 17 18:50:48 fedora systemd[53890]: google-drive.service: Failed at step EXEC spawning /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse: Permission denied
lut 17 18:50:48 fedora systemd[1]: google-drive.service: Control process exited, code=exited, status=203/EXEC
lut 17 18:50:48 fedora systemd[1]: google-drive.service: Failed with result 'exit-code'.
lut 17 18:50:48 fedora systemd[1]: Failed to start FUSE filesystem over Google Drive.
lut 17 18:50:48 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
lut 17 18:50:48 fedora systemd[1]: google-drive.service: Scheduled restart job, restart counter is at 2.
lut 17 18:50:48 fedora systemd[1]: Stopped FUSE filesystem over Google Drive.
lut 17 18:50:48 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:50:48 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:50:48 fedora systemd[1]: Starting FUSE filesystem over Google Drive...
lut 17 18:50:48 fedora audit[53891]: AVC avc:  denied  { execute } for  pid=53891 comm="(camlfuse)" name="google-drive-ocamlfuse" dev="sda3" ino=2083703 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0
lut 17 18:50:48 fedora systemd[53891]: google-drive.service: Failed to locate executable /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse: Permission denied
lut 17 18:50:48 fedora systemd[53891]: google-drive.service: Failed at step EXEC spawning /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse: Permission denied
lut 17 18:50:48 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
lut 17 18:50:48 fedora systemd[1]: google-drive.service: Control process exited, code=exited, status=203/EXEC
lut 17 18:50:48 fedora systemd[1]: google-drive.service: Failed with result 'exit-code'.
lut 17 18:50:48 fedora systemd[1]: Failed to start FUSE filesystem over Google Drive.
lut 17 18:50:49 fedora systemd[1]: google-drive.service: Scheduled restart job, restart counter is at 3.
lut 17 18:50:49 fedora systemd[1]: Stopped FUSE filesystem over Google Drive.
lut 17 18:50:49 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:50:49 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:50:49 fedora systemd[1]: Starting FUSE filesystem over Google Drive...
lut 17 18:50:49 fedora audit[53892]: AVC avc:  denied  { execute } for  pid=53892 comm="(camlfuse)" name="google-drive-ocamlfuse" dev="sda3" ino=2083703 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0
lut 17 18:50:49 fedora systemd[53892]: google-drive.service: Failed to locate executable /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse: Permission denied
lut 17 18:50:49 fedora systemd[53892]: google-drive.service: Failed at step EXEC spawning /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse: Permission denied
lut 17 18:50:49 fedora systemd[1]: google-drive.service: Control process exited, code=exited, status=203/EXEC
lut 17 18:50:49 fedora systemd[1]: google-drive.service: Failed with result 'exit-code'.
lut 17 18:50:49 fedora systemd[1]: Failed to start FUSE filesystem over Google Drive.
lut 17 18:50:49 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
lut 17 18:50:49 fedora systemd[1]: google-drive.service: Scheduled restart job, restart counter is at 4.
lut 17 18:50:49 fedora systemd[1]: Stopped FUSE filesystem over Google Drive.
lut 17 18:50:49 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:50:49 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:50:49 fedora systemd[1]: Starting FUSE filesystem over Google Drive...
lut 17 18:50:49 fedora audit[53893]: AVC avc:  denied  { execute } for  pid=53893 comm="(camlfuse)" name="google-drive-ocamlfuse" dev="sda3" ino=2083703 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0
lut 17 18:50:49 fedora systemd[53893]: google-drive.service: Failed to locate executable /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse: Permission denied
lut 17 18:50:49 fedora systemd[53893]: google-drive.service: Failed at step EXEC spawning /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse: Permission denied
lut 17 18:50:49 fedora systemd[1]: google-drive.service: Control process exited, code=exited, status=203/EXEC
lut 17 18:50:49 fedora systemd[1]: google-drive.service: Failed with result 'exit-code'.
lut 17 18:50:49 fedora systemd[1]: Failed to start FUSE filesystem over Google Drive.
lut 17 18:50:49 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
lut 17 18:50:49 fedora systemd[1]: google-drive.service: Scheduled restart job, restart counter is at 5.
lut 17 18:50:49 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:50:49 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-drive comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:50:49 fedora systemd[1]: Stopped FUSE filesystem over Google Drive.
lut 17 18:50:49 fedora systemd[1]: google-drive.service: Start request repeated too quickly.
lut 17 18:50:49 fedora systemd[1]: google-drive.service: Failed with result 'exit-code'.
lut 17 18:50:49 fedora systemd[1]: Failed to start FUSE filesystem over Google Drive.
lut 17 18:50:55 fedora gnome-shell[1756]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x556ec29ac360] is on because it needs an allocation.
lut 17 18:50:55 fedora gnome-shell[1756]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x556ec4fdcf20] is on because it needs an allocation.
lut 17 18:50:55 fedora gnome-shell[1756]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x556ec4fe06a0] is on because it needs an allocation.
lut 17 18:51:16 fedora systemd[1]: fprintd.service: Deactivated successfully.
lut 17 18:51:16 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 17 18:51:16 fedora audit: BPF prog-id=0 op=UNLOAD
^Alut 17 18:51:19 fedora gnome-shell[1756]: pushModal: invocation of begin_modal failed
lut 17 18:51:21 fedora gnome-shell[1756]: Ignoring length property that isn't a number at line 1853, col 24

 

Link to comment
Share on other sites

15 minut temu, fraktal15 napisał:

lut 17 18:50:48 fedora audit[53884]: AVC avc: denied { execute } for pid=53884 comm="(camlfuse)" name="google-drive-ocamlfuse" dev="sda3" ino=2083703 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0

Tak jak podejrzewałem selinux, musisz utworzyć własną politykę selinux do tego mogą być pomocne takie polecenia jak sealert ausearch i audit2allow

Link to comment
Share on other sites

8 minut temu, sunrise napisał:

Tak jak podejrzewałem selinux, musisz utworzyć własną politykę selinux do tego mogą być pomocne takie polecenia jak sealert ausearch i audit2allow

czy jest ktoś w stanie mi pomóc z tą polityką?

Link to comment
Share on other sites

Możemy spróbować. Sealert na pewno coś tam pokaże, ale automat audit2search czasem się myli i nie proponuje właściwych polityk Selinuksa. Obstawiam brak bin_t na pliku google-drive-ocamlfuse. Można spróbować tak:

semanage fcontext -a -t bin_t '/home/panekadamek/.opam/default/bin/google-drive-ocamlfuse'
restorecon -v /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse
systemctl restart google-drive

Trzymanie plików wykonywalnych w katalogu domowym też zapewne nie pomaga. Ale może bin_t wystarczy.

  • Like 1
Link to comment
Share on other sites

Godzinę temu, SeeM napisał:

Możemy spróbować. Sealert na pewno coś tam pokaże, ale automat audit2search czasem się myli i nie proponuje właściwych polityk Selinuksa. Obstawiam brak bin_t na pliku google-drive-ocamlfuse. Można spróbować tak:

semanage fcontext -a -t bin_t '/home/panekadamek/.opam/default/bin/google-drive-ocamlfuse'
restorecon -v /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse
systemctl restart google-drive

Trzymanie plików wykonywalnych w katalogu domowym też zapewne nie pomaga. Ale może bin_t wystarczy.

Jeśłi miałem to wkleić do konsoli i dało odpowiedź:

semanage fcontext -a -t bin_t '/home/panekadamek/.opam/default/bin/google-drive-ocamlfuse'
restorecon -v /home/panekadamek/.opam/default/bin/google-drive-ocamlfuse
systemctl restart google-drive
ValueError: Polityka SELinuksa nie jest zarządzana lub nie można uzyskać dostępu do przechowalni.
Job for google-drive.service failed because the control process exited with error code.
See "systemctl status google-drive.service" and "journalctl -xeu google-drive.service" for details.

Proszę o wyrozumiałość, ale ja się dopiero uczę.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...