Impossible de lancer Ardour5 – Ubuntu 19.04
Pour raison de test, je viens d’installer Ubuntu 19.04. Globalement, ça va plutôt bien, mais je ne parviens pas à lancer Ardour5. Voici le message que j’obtiens en ligne de commande :
Copy to clipboard
$ ardour5 WARNING: Your system has a limit for maximum amount of locked memory! This might cause Ardour to run out of memory before your system runs out of memory. You can view the memory limit with 'ulimit -l', and it is normally controlled by /etc/security/limits.conf bind txt domain [gtk2_ardour5] to /usr/share/ardour5/locale Ardour5.12.0 (construit avec 1:5.12.0-3 et GCC version 7.3.0) ardour: [INFO]: Votre configuration-système limite Ardour à 524288 fichiers ouverts ardour: [INFO]: Chargement du fichier de configuration-système /etc/ardour5/system_config ardour: [INFO]: CPU vendor: GenuineIntel ardour: [INFO]: AVX-capable processor ardour: [INFO]: CPU brand: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz ardour: [INFO]: Using SSE optimized routines ardour: [INFO]: Chargement du fichier de style par défaut (/etc/ardour5/default_ui_config) pour l'interface graphique Gtk-Message: 18:33:39.714: Failed to load module "canberra-gtk-module" Couleur shuttle bg introuvable ardour: [INFO]: Chargement du fichier de couleur /usr/share/ardour5/themes/dark-ardour.colors
Je n’obtiens même pas une fenêtre d’erreur, rien d’autre que cette sortie texte.
En tout cas, je suis très surpris de la limite en mémoire. En effet, mon utilisateur fait bien parti du groupe audio :
Copy to clipboard
$ groups yoann adm cdrom sudo audio dip plugdev lpadmin sambashare
Par ailleurs, j’ai bien configuré PAM pour ne pas limiter la mémoire pour le groupe audio :
Copy to clipboard
$ cat /etc/security/limits.conf # /etc/security/limits.conf # #Each line describes a limit for a user in the form: # #<domain> <type> <item> <value> # #Where: #<domain> can be: # - a user name # - a group name, with @group syntax # - the wildcard *, for default entry # - the wildcard %, can be also used with %group syntax, # for maxlogin limit # - NOTE: group and wildcard limits are not applied to root. # To apply a limit to the root user, <domain> must be # the literal username root. # #<type> can have the two values: # - "soft" for enforcing the soft limits # - "hard" for enforcing hard limits # #<item> can be one of the following: # - core - limits the core file size (KB) # - data - max data size (KB) # - fsize - maximum filesize (KB) # - memlock - max locked-in-memory address space (KB) # - nofile - max number of open file descriptors # - rss - max resident set size (KB) # - stack - max stack size (KB) # - cpu - max CPU time (MIN) # - nproc - max number of processes # - as - address space limit (KB) # - maxlogins - max number of logins for this user # - maxsyslogins - max number of logins on the system # - priority - the priority to run user process with # - locks - max number of file locks the user can hold # - sigpending - max number of pending signals # - msgqueue - max memory used by POSIX message queues (bytes) # - nice - max nice priority allowed to raise to values: [-20, 19] # - rtprio - max realtime priority # - chroot - change root to directory (Debian-specific) # #<domain> <type> <item> <value> # #* soft core 0 #root hard core 100000 #* hard rss 10000 #@student hard nproc 20 #@faculty soft nproc 20 #@faculty hard nproc 50 #ftp hard nproc 0 #ftp - chroot /ftp #@student - maxlogins 4 @audio - rtprio 90 @audio - memlock unlimited # End of file
Également :
Copy to clipboard
$ cat /etc/pam.d/common-session # # /etc/pam.d/common-session - session-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define tasks to be performed # at the start and end of sessions of *any* kind (both interactive and # non-interactive). # # As of pam 1.0.1-6, this file is managed by pam-auth-update by default. # To take advantage of this, it is recommended that you configure any # local modules either before or after the default block, and use # pam-auth-update to manage selection of other modules. See # pam-auth-update(8) for details. # here are the per-package modules (the "Primary" block) session [default=1] pam_permit.so # here's the fallback if no module succeeds session requisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around session required pam_permit.so # The pam_umask module will set the umask according to the system default in # /etc/login.defs and user settings, solving the problem of different # umask settings with different shells, display managers, remote sessions etc. # See "man pam_umask". session optional pam_umask.so # and here are more per-package modules (the "Additional" block) session required pam_unix.so session required pam_limits.so session optional pam_systemd.so # end of pam-auth-update config
Pourtant, même après avoir fermé puis rouvert la session, en fait même après avoir relancé le système, j’obtiens ce résultat :
Copy to clipboard
$ ulimit -l 65536
Tout se passe comme si ma configuration n’avait pas été prise en compte et je n’ai pas la moindre idée de comment corriger cela. Je n’ai rien trouver qui puisse aider avec DMesg. Quelqu’un a-t-il une idée ?
Cordialement.
