Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 21/08/2019, à 13:41

llardereau

Xfce4 & Anydesk (Teamwiever)

Bonjour a tous,

Voila depuis quelques semaines j'utilise via un VPS et un Ubuntu 18.04 LTS.
J'ai monté un XFCE4 et j'y accède en VNC.
Seulement je souhaiterai y accéder en Anydesk (ou Teamwiever)
J'ai réussi a faire l'installation en ligne de commande, je retrouve bien dans le répertoire "internet", mais quand je clique il ne se passe rien.
D'après ce que j'ai pu lire et compris (??) c'est peut être un problème de gestionnaire de session.
Pour être précis je n'ai qu'un utilisateur avec ouverture automatique sans rentrer de mot de passe.
Pourriez vous m'aider je voudrais comprendre pour avancer.
D'avance merci a vous tous.

Hors ligne

#2 Le 24/08/2019, à 11:38

chobbes

Re : Xfce4 & Anydesk (Teamwiever)

Bonjour,

tu parles de lancer Anydesk?
Quand un logiciel ne se lance pas en mode graphique, il faut taper sa commande dans un terminal et voir les éventuels messages d'erreur.
Ouvre donc un terminal et tape simplement la commande suivante

anydesk

Hors ligne

#3 Le 24/08/2019, à 11:41

rogn...

Re : Xfce4 & Anydesk (Teamwiever)

Comment a-t-il été installé ?
Snap, flatpak, autre ?

#4 Le 25/08/2019, à 10:07

llardereau

Re : Xfce4 & Anydesk (Teamwiever)

Déjà merci de vos retours et pour vous répondre

Anydesk en ligne de commande via Putty sur l'adresse IP ou en session VNC, je retourne sur le prompt

La méthode d'installation :
En Terminal dans la session en VNC

apt-get install gdebi
wget [url]https://download.anydesk.com/linux/anydesk_5.1.1-1_amd64.deb[/url]
gdebi anydesk_5.1.1-1_amd64.deb
dpkg  --configure -a
apt-get install -f

Dernière modification par llardereau (Le 26/08/2019, à 08:57)

Hors ligne

#5 Le 26/08/2019, à 06:22

rogn...

Re : Xfce4 & Anydesk (Teamwiever)

Ah d'accord. Bon déjà pour l'installation d'Anydesk, tu t'y es mal pris. Je conseille la version flatpak. Il faudrait que
1 - tu désinstalles la version gdebi
2 - et que tu installes le moteur flatpak puis le flatpak d'Anydesk.

sudo apt install flatpak
flatpak install anydesk

Et ce sur les deux machines.

Ensuite, pour l'utilisation : il faut que le poste distant ait un serveur graphique actif, autrement dit si tu ne fais que du prompt, tu peux oublier Anydesk ce n'est pas fait pour.
Sur le poste distant : Anydesk doit être lancé et l'ID connu. Par défaut : un utilisateur sur le poste distant peut accepter ou refuser le contrôle. Pour ton cas, il te faudra installer un accès non surveillé.
Sur le poste local : lancer anydesk puis saisir l'ID du poste distant et demander la connexion.

#6 Le 26/08/2019, à 07:50

llardereau

Re : Xfce4 & Anydesk (Teamwiever)

Ok gdebi desinstallé, flatpak installé.
Mais au lancement de l'install de Anydesk par flatpak :

Usage:
  flatpak install [OPTION…] LOCATION/REMOTE [REF...] - Install applications or runtimes
Help Options:
  -h, --help              Show help options
Application Options:
  --user                  Work on user installations
  --system                Work on system-wide installations (default)
  --installation=NAME     Work on specific system-wide installation(s)
  --arch=ARCH             Arch to install for
  --no-pull               Don't pull, only install from local cache
  --no-deploy             Don't deploy, only download to local cache
  --no-related            Don't install related refs
  --no-deps               Don't verify/install runtime dependencies
  --no-static-deltas      Don't use static deltas
  --runtime               Look for runtime with the specified name
  --app                   Look for app with the specified name
  --bundle                Assume LOCATION is a .flatpak single-file bundle
  --from                  Assume LOCATION is a .flatpakref application description
  --gpg-file=FILE         Check bundle signatures with GPG key from FILE (- for stdin)
  --subpath=PATH          Only install this subpath
  -y, --assumeyes         Automatically answer yes for all questions
  --reinstall             Uninstall first if already installed
  -v, --verbose           Print debug information during command processing, -vv for more detail
  --ostree-verbose        Print OSTree debug information during command processing
error: REMOTE and REF must be specified

La je suis dépassé....

Précision le poste distant a un serveur graphique puisque j'y accède déjà en VNC, mon besoin est d'y accéder en Anydesk
Anydesk déjà installé sur mon poste local et j'accède a mes autres ressources.

Dernière modification par llardereau (Le 26/08/2019, à 08:58)

Hors ligne

#7 Le 26/08/2019, à 07:56

xubu1957

Re : Xfce4 & Anydesk (Teamwiever)

Bonjour,

Pour ajouter toi-même les balises code à tes précédents messages #4 et #6 :                       Merci                          wink

  • Cliquer sur  le lien « Modifier » en bas à droite du message

  • Sélectionner le texte

  • Cliquer sur le <> de l'éditeur de message

1530289742.png

comme indiqué dans le : Retour utilisable de commande

Dernière modification par xubu1957 (Le 26/08/2019, à 11:28)


Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

Hors ligne

#8 Le 26/08/2019, à 09:33

rogn...

Re : Xfce4 & Anydesk (Teamwiever)

Que donne flatpak list ?

#9 Le 26/08/2019, à 09:55

llardereau

Re : Xfce4 & Anydesk (Teamwiever)

Rien puisque je n'ai pas pu installer anydesk
A l'invite de

flatpak install anydesk

J'ai un message :

error: REMOTE and REF must be specified

Hors ligne

#10 Le 26/08/2019, à 10:02

rogn...

Re : Xfce4 & Anydesk (Teamwiever)

Ah tiens curieux il ne t'a pas mis flathub par défaut...
Dans ce cas là :

flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

puis redémarrer.
Source : https://flatpak.org/setup/Ubuntu/

Après redémarrage du système (on va le faire à la complet et pas à l'implicite).

flatpak install flathub com.anydesk.Anydesk

puis démarrage.

flatpak run com.anydesk.Anydesk

#11 Le 26/08/2019, à 11:14

llardereau

Re : Xfce4 & Anydesk (Teamwiever)

Alors a la commande

flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

Ras pas de message d'erreur
Ensuite a la commande :

flatpak install flathub com.anydesk.Anydesk
Required runtime for com.anydesk.Anydesk/x86_64/stable (runtime/org.gnome.Platform/x86_64/3.28) found in remote flathub
Do you want to install it? [y/n]: y
Installing in system:
org.gnome.Platform/x86_64/3.28             flathub 6d1d0ebbd724
org.freedesktop.Platform.ffmpeg/x86_64/1.6 flathub d757f762489e
org.gnome.Platform.Locale/x86_64/3.28      flathub 2823e3d81b74
com.anydesk.Anydesk/x86_64/stable          flathub 172c11be5b5d
  permissions: ipc, network, pulseaudio, x11, dri
  file access: home
  tags: proprietary
Is this ok [y/n]: y
Installing: org.gnome.Platform/x86_64/3.28 from flathub
[####################] 976 metadata, 20492 content objects fetched; 292154 KiB t
Now at 6d1d0ebbd724.
Installing: org.freedesktop.Platform.ffmpeg/x86_64/1.6 from flathub
[####################] 8 metadata, 12 content objects fetched; 2788 KiB transfer
Now at d757f762489e.
Installing: org.gnome.Platform.Locale/x86_64/3.28 from flathub
[####################] 4 metadata, 1 content objects fetched; 14 KiB transferred
Now at 2823e3d81b74.
Installing: com.anydesk.Anydesk/x86_64/stable from flathub
[####################] Downloading files: 246/246 6.6 MB (6.6 MB/s)    tar: anydesk-5.1.1/copyright: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/polkit-1/com.philandro.anydesk.policy: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/polkit-1: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/anydesk.desktop: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/scalable/apps/anydesk.svg: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/scalable/apps: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/scalable: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/32x32/apps/anydesk.png: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/32x32/apps: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/32x32: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/24x24/apps/anydesk.png: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/24x24/apps: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/24x24: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/16x16/apps/anydesk.png: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/16x16/apps: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/16x16: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/256x256/apps/anydesk.png: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/256x256/apps: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/256x256: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/48x48/apps/anydesk.png: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/48x48/apps: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor/48x48: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons/hicolor: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/icons: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/systemd/anydesk.service: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/systemd: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/anydesk: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/init/anydesk: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1/init: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: anydesk-5.1.1: Cannot change ownership to uid 105, gid 108: Operation not permitted
tar: Exiting with failure status due to previous errors

Now at 172c11be5b5d.

Puis a la commande

flatpak run com.anydesk.Anydesk
(process:2): GLib-GObject-WARNING **: 12:05:11.943: invalid (NULL) pointer instance
(process:2): GLib-GObject-CRITICAL **: 12:05:11.943: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:2): GLib-GObject-WARNING **: 12:05:11.943: invalid (NULL) pointer instance
(process:2): GLib-GObject-CRITICAL **: 12:05:11.943: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:4): GLib-GObject-WARNING **: 12:05:11.973: invalid (NULL) pointer instance
(process:4): GLib-GObject-CRITICAL **: 12:05:11.973: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:4): GLib-GObject-WARNING **: 12:05:11.973: invalid (NULL) pointer instance
(process:4): GLib-GObject-CRITICAL **: 12:05:11.973: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
root@vmi288698:~#
(process:8): GLib-GObject-WARNING **: 12:05:11.997: invalid (NULL) pointer instance
(process:8): GLib-GObject-CRITICAL **: 12:05:11.997: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:8): GLib-GObject-WARNING **: 12:05:11.997: invalid (NULL) pointer instance
(process:8): GLib-GObject-CRITICAL **: 12:05:11.997: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:11): GLib-GObject-WARNING **: 12:05:12.004: invalid (NULL) pointer instance
(process:11): GLib-GObject-CRITICAL **: 12:05:12.004: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:11): GLib-GObject-WARNING **: 12:05:12.004: invalid (NULL) pointer instance
(process:11): GLib-GObject-CRITICAL **: 12:05:12.004: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:14): GLib-GObject-WARNING **: 12:05:12.021: invalid (NULL) pointer instance
(process:14): GLib-GObject-CRITICAL **: 12:05:12.021: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:14): GLib-GObject-WARNING **: 12:05:12.021: invalid (NULL) pointer instance
(process:14): GLib-GObject-CRITICAL **: 12:05:12.021: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:16): GLib-GObject-WARNING **: 12:05:12.025: invalid (NULL) pointer instance
(process:16): GLib-GObject-CRITICAL **: 12:05:12.025: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:16): GLib-GObject-WARNING **: 12:05:12.025: invalid (NULL) pointer instance
(process:16): GLib-GObject-CRITICAL **: 12:05:12.025: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
sh: lsb_release: command not found

Hors ligne

#12 Le 26/08/2019, à 11:17

rogn...

Re : Xfce4 & Anydesk (Teamwiever)

Hm... l’utilisateur de la machine est un sudoer ou pas du tout ?

#13 Le 26/08/2019, à 12:31

llardereau

Re : Xfce4 & Anydesk (Teamwiever)

qu'un seul utilisateur "root"

Hors ligne

#14 Le 26/08/2019, à 12:55

rogn...

Re : Xfce4 & Anydesk (Teamwiever)

Mouais. Dangereux et non conventionnel cette façon de faire. Tu pourrais créer un utilisateur faisant partie du groupe sudo et qu'il puisse administrer le système ?
EDIT : donner d'abord le contenu de /usr/share/polkit-1/rules.d/org.freedesktop.Flatpak.rules

cat /usr/share/polkit-1/rules.d/org.freedesktop.Flatpak.rules

Ensuite, tu refais les manipulations que je t'ai demandé en  #10

Si tu tiens à rester avec root, les impacts seront différents et ça dépasse mes compétences.

Dernière modification par rogn... (Le 26/08/2019, à 13:12)

#15 Le 26/08/2019, à 13:23

llardereau

Re : Xfce4 & Anydesk (Teamwiever)

J'ai créé un utilisateur anydesk
Voila le résultat de EDIT cat /usr/share/polkit-1/rules.d/org.freedesktop.Flatpak.rules

root@vmiXXXXXX:~# cat /usr/share/polkit-1/rules.d/org.freedesktop.Flatpak.rules
polkit.addRule(function(action, subject) {
    if ((action.id == "org.freedesktop.Flatpak.app-install" ||
         action.id == "org.freedesktop.Flatpak.runtime-install"||
         action.id == "org.freedesktop.Flatpak.app-uninstall" ||
         action.id == "org.freedesktop.Flatpak.runtime-uninstall" ||
         action.id == "org.freedesktop.Flatpak.modify-repo") &&
        subject.active == true && subject.local == true &&
        subject.isInGroup("sudo")) {
            return polkit.Result.YES;
    }
});

Puis le résultat des manipulations en #10

root@vmiXXXXXX:~# sudo flatpak run com.anydesk.Anydesk
(process:2): GLib-GObject-WARNING **: 14:10:33.629: invalid (NULL) pointer instance
(process:2): GLib-GObject-CRITICAL **: 14:10:33.629: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:2): GLib-GObject-WARNING **: 14:10:33.629: invalid (NULL) pointer instance
(process:2): GLib-GObject-CRITICAL **: 14:10:33.629: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:4): GLib-GObject-WARNING **: 14:10:33.659: invalid (NULL) pointer instance
(process:4): GLib-GObject-CRITICAL **: 14:10:33.659: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:4): GLib-GObject-WARNING **: 14:10:33.659: invalid (NULL) pointer instance
(process:4): GLib-GObject-CRITICAL **: 14:10:33.659: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
root@vmiXXXXXX:~#
(process:7): GLib-GObject-WARNING **: 14:10:33.688: invalid (NULL) pointer instance
(process:7): GLib-GObject-CRITICAL **: 14:10:33.688: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:7): GLib-GObject-WARNING **: 14:10:33.688: invalid (NULL) pointer instance
(process:7): GLib-GObject-CRITICAL **: 14:10:33.688: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:10): GLib-GObject-WARNING **: 14:10:33.690: invalid (NULL) pointer instance
(process:10): GLib-GObject-CRITICAL **: 14:10:33.690: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:10): GLib-GObject-WARNING **: 14:10:33.690: invalid (NULL) pointer instance
(process:10): GLib-GObject-CRITICAL **: 14:10:33.690: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:14): GLib-GObject-WARNING **: 14:10:35.686: invalid (NULL) pointer instance
(process:14): GLib-GObject-CRITICAL **: 14:10:35.686: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:14): GLib-GObject-WARNING **: 14:10:35.686: invalid (NULL) pointer instance
(process:14): GLib-GObject-CRITICAL **: 14:10:35.686: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
sh: lsb_release: command not found
root@vmiXXXXXX:~# sudo flatpak run com.anydesk.Anydesk
(process:2): GLib-GObject-WARNING **: 14:10:33.629: invalid (NULL) pointer instance
(process:2): GLib-GObject-CRITICAL **: 14:10:33.629: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:4): GLib-GObject-WARNING **: 14:10:33.659: invalid (NULL) pointer instance
(process:4): GLib-GObject-CRITICAL **: 14:10:33.659: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:4): GLib-GObject-WARNING **: 14:10:33.659: invalid (NULL) pointer instance
(process:4): GLib-GObject-CRITICAL **: 14:10:33.659: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
root@vmiXXXXXX:~#
(process:7): GLib-GObject-WARNING **: 14:10:33.688: invalid (NULL) pointer instance
(process:7): GLib-GObject-CRITICAL **: 14:10:33.688: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:7): GLib-GObject-WARNING **: 14:10:33.688: invalid (NULL) pointer instance
(process:7): GLib-GObject-CRITICAL **: 14:10:33.688: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:10): GLib-GObject-WARNING **: 14:10:33.690: invalid (NULL) pointer instance
(process:10): GLib-GObject-CRITICAL **: 14:10:33.690: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:10): GLib-GObject-WARNING **: 14:10:33.690: invalid (NULL) pointer instance
(process:10): GLib-GObject-CRITICAL **: 14:10:33.690: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:14): GLib-GObject-WARNING **: 14:10:35.686: invalid (NULL) pointer instance
(process:14): GLib-GObject-CRITICAL **: 14:10:35.686: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:14): GLib-GObject-WARNING **: 14:10:35.686: invalid (NULL) pointer instance
(process:14): GLib-GObject-CRITICAL **: 14:10:35.686: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
sh: lsb_release: command not found
root@vmiXXXXXX:~#: command not found
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:2): GLib-GObject-WARNING **: 14:10:33.629: invalid (NULL) pointer instance
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:2): GLib-GObject-CRITICAL **: 14:10:33.629: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:2): GLib-GObject-WARNING **: 14:10:33.629: invalid (NULL) pointer instance
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:2): GLib-GObject-CRITICAL **: 14:10:33.629: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:4): GLib-GObject-WARNING **: 14:10:33.659: invalid (NULL) pointer instance
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:4): GLib-GObject-CRITICAL **: 14:10:33.659: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:4): GLib-GObject-WARNING **: 14:10:33.659: invalid (NULL) pointer instance
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:4): GLib-GObject-CRITICAL **: 14:10:33.659: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~# root@vmiXXXXXX:~#
root@vmiXXXXXX:~#: command not found
root@vmiXXXXXX:~# (process:7): GLib-GObject-WARNING **: 14:10:33.688: invalid (NULL) pointer instance
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:7): GLib-GObject-CRITICAL **: 14:10:33.688: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:7): GLib-GObject-WARNING **: 14:10:33.688: invalid (NULL) pointer instance
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:7): GLib-GObject-CRITICAL **: 14:10:33.688: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:10): GLib-GObject-WARNING **: 14:10:33.690: invalid (NULL) pointer instance
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:10): GLib-GObject-CRITICAL **: 14:10:33.690: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:10): GLib-GObject-WARNING **: 14:10:33.690: invalid (NULL) pointer instance
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:10): GLib-GObject-CRITICAL **: 14:10:33.690: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:14): GLib-GObject-WARNING **: 14:10:35.686: invalid (NULL) pointer instance
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:14): GLib-GObject-CRITICAL **: 14:10:35.686: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:14): GLib-GObject-WARNING **: 14:10:35.686: invalid (NULL) pointer instance
bash: syntax error near unexpected token `:'
root@vmiXXXXXX:~#
root@vmiXXXXXX:~# (process:14): GLib-GObject-CRITICAL **: 14:10:35.686: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
bash: syntax error near unexpected token `:'

Hors ligne

#16 Le 26/08/2019, à 13:25

rogn...

Re : Xfce4 & Anydesk (Teamwiever)

Tu as oublié

flatpak install flathub com.anydesk.Anydesk

Attention, les manipulations flatpak doivent être réalisées avec le compte anydesk et pas le root !

Dernière modification par rogn... (Le 26/08/2019, à 13:29)

#17 Le 27/08/2019, à 08:42

llardereau

Re : Xfce4 & Anydesk (Teamwiever)

Ok alors j'ai recommencé :

login as: anydesk
anydesk@'s password:
Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-58-generic x86_64)

anydesk@vmiXXXXXX:~$ flatpak install flathub com.anydesk.Anydesk
Installing in system:
com.anydesk.Anydesk/x86_64/stable flathub 172c11be5b5d
  permissions: ipc, network, pulseaudio, x11, dri
  file access: home
  tags: proprietary
Is this ok [y/n]: y
Installing: com.anydesk.Anydesk/x86_64/stable from flathub
[####################] Downloading files: 246/246 6.6 MB (6.6 MB/s)
error: Failed to install com.anydesk.Anydesk/x86_64/stable: Flatpak system operation Deploy not allowed for user

Alors j'ai tenté mais avec sudo

anydesk@vmiXXXXXX:~$ sudo flatpak install flathub com.anydesk.Anydesk
[sudo] password for anydesk:
anydesk is not in the sudoers file.  This incident will be reported.
anydesk@vmiXXXXXX:~$

Ton avis ?

Hors ligne

#18 Le 27/08/2019, à 09:07

rogn...

Re : Xfce4 & Anydesk (Teamwiever)

Who... c'est vraiment le bazar ton truc. yikes

Depuis le compte root :

adduser anydesk sudo

et puis retente l'installation depuis le compte anydesk.

#19 Le 27/08/2019, à 13:21

llardereau

Re : Xfce4 & Anydesk (Teamwiever)

Pas mieux avec le compte anydesk

anydesk@vmiXXXXXX:~$ flatpak install flathub com.anydesk.Anydesk
Installing in system:
com.anydesk.Anydesk/x86_64/stable flathub 172c11be5b5d
  permissions: ipc, network, pulseaudio, x11, dri
  file access: home
  tags: proprietary
Is this ok [y/n]: y
Installing: com.anydesk.Anydesk/x86_64/stable from flathub
[####################] Downloading files: 246/246 6.6 MB (6.6 MB/s)
error: Failed to install com.anydesk.Anydesk/x86_64/stable: Flatpak system operation Deploy not allowed for user

Je laisse tomber, merci je vais continuer avec VNC,
Je voulais anydesk car avec VNC j'ai des messages d'erreur "too many security failures"
Et je suis obligé de tuer le process VNC et de le relancer

Hors ligne