Package: jackd2; Maintainer for jackd2 is Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>; Source for jackd2 is src:jackd2 (PTS, buildd, popcon).
Reported by: Arnaldo Pirrone <it9exm@gmail.com>
Date: Sat, 20 Nov 2021 23:57:02 UTC
Severity: grave
Tags: moreinfo
Found in version jackd2/1.9.19~dfsg-2
Done: Sebastian Ramacher <sramacher@debian.org>
Bug is archived. No further changes may be made.
View this report as an mbox folder, status mbox, maintainer mbox
Report forwarded
to debian-bugs-dist@lists.debian.org, it9exm@gmail.com, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Sat, 20 Nov 2021 23:57:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Arnaldo Pirrone <it9exm@gmail.com>:
New Bug report received and forwarded. Copy sent to it9exm@gmail.com, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Sat, 20 Nov 2021 23:57:03 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: jackd2 Version: 1.9.19~dfsg-2 Severity: grave X-Debbugs-Cc: it9exm@gmail.com Apparently there is something wrong with Jack and dbus. Also reported here: https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/ Find below the jack server logs. 00:41:32.228 Resetta le statistiche. 00:41:32.269 Connessioni di ALSA cambiate. 00:41:32.389 D-BUS: Servizio disponibile (org.jackaudio.service aka jackdbus). Cannot connect to server socket err = File o directory non esistente Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock 00:41:32.563 Cambiamento nel grafico delle connessioni di ALSA. 00:41:47.432 D-BUS: il server JACK non può essere avviato. Mi dispiace Sun Nov 21 00:41:47 2021: Starting jack server... Sun Nov 21 00:41:47 2021: JACK server starting in realtime mode with priority 10 Sun Nov 21 00:41:47 2021: self-connect-mode is "Don't restrict self connect requests" Cannot connect to server socket err = File o directory non esistente Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock Sun Nov 21 00:41:47 2021: Device reservation request with priority 2147483647 denied for "Audio1": org.freedesktop.DBus.Error.UnknownMethod (Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1) Sun Nov 21 00:41:47 2021: ERROR: Failed to acquire device name : Audio1 error : Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1 Sun Nov 21 00:41:47 2021: ERROR: Audio device hw:PCH,0 cannot be acquired... Sun Nov 21 00:41:47 2021: ERROR: Cannot initialize driver Sun Nov 21 00:41:47 2021: ERROR: JackServer::Open failed with -1 Sun Nov 21 00:41:47 2021: ERROR: Failed to open server Sun Nov 21 00:41:48 2021: Saving settings to "/home/it9exm/.config/jack/conf.xml" ... 00:41:49.469 Non sono riuscito ad avviare JACK come client. - Operazione fallita. - Impossibile connettersi al server JACK. Controlla la finestra dei messaggi per maggiori informazioni. Cannot connect to server socket err = File o directory non esistente Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.19-xanmod1 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages jackd2 depends on: ii debconf [debconf-2.0] 1.5.79 ii libasound2 1.2.5.1-1 ii libc6 2.32-4 ii libdbus-1-3 1.12.20-3 ii libexpat1 2.4.1-3 ii libgcc-s1 11.2.0-10 ii libjack-jackd2-0 1.9.19~dfsg-2 ii libreadline8 8.1-2 ii libsamplerate0 0.2.2-1 ii libsndfile1 1.0.31-2 ii libstdc++6 11.2.0-10 ii libsystemd0 249.6-2 ii libzita-alsa-pcmi0 0.3.2-2 ii libzita-resampler1 1.8.0-2 ii python3 3.9.8-1 ii python3-dbus 1.2.18-3 Versions of packages jackd2 recommends: ii jackd2-firewire 1.9.19~dfsg-2 ii libpam-modules 1.4.0-10 ii qjackctl 0.9.5-1 Versions of packages jackd2 suggests: pn jack-tools <none> pn meterbridge <none> -- debconf information: * jackd/tweak_rt_limits: true
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Sun, 21 Nov 2021 21:06:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Joenio Marques da Costa <joenio@joenio.me>:
Extra info received and forwarded to list. Copy sent to Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Sun, 21 Nov 2021 21:06:05 GMT) (full text, mbox, link).
Message #10 received at 1000293@bugs.debian.org (full text, mbox, reply):
Package: jackd2 Version: 1.9.19~dfsg-2 Severity: important The same error here in my Desktop environment. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-4-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages jackd2 depends on: ii debconf [debconf-2.0] 1.5.79 ii libasound2 1.2.5.1-1 ii libc6 2.32-4 ii libdbus-1-3 1.12.20-3 ii libexpat1 2.4.1-3 ii libgcc-s1 11.2.0-10 ii libjack-jackd2-0 1.9.19~dfsg-2 ii libreadline8 8.1-2 ii libsamplerate0 0.2.2-1 ii libsndfile1 1.0.31-2 ii libstdc++6 11.2.0-10 ii libsystemd0 249.5-2 ii libzita-alsa-pcmi0 0.3.2-2 ii libzita-resampler1 1.8.0-2 ii python3 3.9.7-1 ii python3-dbus 1.2.18-3+b1 Versions of packages jackd2 recommends: ii jackd2-firewire 1.9.19~dfsg-2 ii libpam-modules 1.4.0-10 ii qjackctl 0.9.5-1 Versions of packages jackd2 suggests: pn jack-tools <none> ii meterbridge 0.9.2-13+b1 -- debconf information: * jackd/tweak_rt_limits: false -- Joenio Marques da Costa Invited Researcher at Université Gustave Eifell Research Software Engineer at LISIS Developer at CorTexT platform & RISIS Core Facility http://umr-lisis.fr/membre/joenio
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Mon, 22 Nov 2021 10:54:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Sebastian Ramacher <sramacher@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Mon, 22 Nov 2021 10:54:02 GMT) (full text, mbox, link).
Message #15 received at 1000293@bugs.debian.org (full text, mbox, reply):
Control: tags -1 moreinfo On 2021-11-21 00:55:50, Arnaldo Pirrone wrote: > Package: jackd2 > Version: 1.9.19~dfsg-2 > Severity: grave > X-Debbugs-Cc: it9exm@gmail.com > > Apparently there is something wrong with Jack and dbus. > Also reported here: > https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/ > Find below the jack server logs. > > 00:41:32.228 Resetta le statistiche. > 00:41:32.269 Connessioni di ALSA cambiate. > 00:41:32.389 D-BUS: Servizio disponibile (org.jackaudio.service aka jackdbus). > Cannot connect to server socket err = File o directory non esistente > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock > 00:41:32.563 Cambiamento nel grafico delle connessioni di ALSA. > 00:41:47.432 D-BUS: il server JACK non può essere avviato. Mi dispiace > Sun Nov 21 00:41:47 2021: Starting jack server... > Sun Nov 21 00:41:47 2021: JACK server starting in realtime mode with priority > 10 > Sun Nov 21 00:41:47 2021: self-connect-mode is "Don't restrict self connect > requests" > Cannot connect to server socket err = File o directory non esistente > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock > Sun Nov 21 00:41:47 2021: Device reservation request with priority 2147483647 > denied for "Audio1": org.freedesktop.DBus.Error.UnknownMethod (Method > RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1) > Sun Nov 21 00:41:47 2021: ERROR: Failed to acquire device name : Audio1 error : > Method RequestRelease is not implemented on interface > org.freedesktop.ReserveDevice1 > Sun Nov 21 00:41:47 2021: ERROR: Audio device hw:PCH,0 cannot be acquired... > Sun Nov 21 00:41:47 2021: ERROR: Cannot initialize driver > Sun Nov 21 00:41:47 2021: ERROR: JackServer::Open failed with -1 > Sun Nov 21 00:41:47 2021: ERROR: Failed to open server > Sun Nov 21 00:41:48 2021: Saving settings to > "/home/it9exm/.config/jack/conf.xml" ... > 00:41:49.469 Non sono riuscito ad avviare JACK come client. - Operazione > fallita. - Impossibile connettersi al server JACK. Controlla la finestra dei > messaggi per maggiori informazioni. > Cannot connect to server socket err = File o directory non esistente > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock Unfortunately I'm not able to reprodue this issue. Are you running pipewire by any chance? Best Sebastian > > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable > APT policy: (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.14.19-xanmod1 (SMP w/4 CPU threads) > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages jackd2 depends on: > ii debconf [debconf-2.0] 1.5.79 > ii libasound2 1.2.5.1-1 > ii libc6 2.32-4 > ii libdbus-1-3 1.12.20-3 > ii libexpat1 2.4.1-3 > ii libgcc-s1 11.2.0-10 > ii libjack-jackd2-0 1.9.19~dfsg-2 > ii libreadline8 8.1-2 > ii libsamplerate0 0.2.2-1 > ii libsndfile1 1.0.31-2 > ii libstdc++6 11.2.0-10 > ii libsystemd0 249.6-2 > ii libzita-alsa-pcmi0 0.3.2-2 > ii libzita-resampler1 1.8.0-2 > ii python3 3.9.8-1 > ii python3-dbus 1.2.18-3 > > Versions of packages jackd2 recommends: > ii jackd2-firewire 1.9.19~dfsg-2 > ii libpam-modules 1.4.0-10 > ii qjackctl 0.9.5-1 > > Versions of packages jackd2 suggests: > pn jack-tools <none> > pn meterbridge <none> > > -- debconf information: > * jackd/tweak_rt_limits: true -- Sebastian Ramacher
Added tag(s) moreinfo.
Request was from Sebastian Ramacher <sramacher@debian.org>
to 1000293-submit@bugs.debian.org.
(Mon, 22 Nov 2021 10:54:02 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Sat, 27 Nov 2021 21:18:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Arnaldo Pirrone <it9exm@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Sat, 27 Nov 2021 21:18:03 GMT) (full text, mbox, link).
Message #22 received at 1000293@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
I guess so, I have both pipewire and pipewire-pulse in the output of ps Altgough I have no idea what that is for Il lun 22 nov 2021, 11:50 Sebastian Ramacher <sramacher@debian.org> ha scritto: > Control: tags -1 moreinfo > > On 2021-11-21 00:55:50, Arnaldo Pirrone wrote: > > Package: jackd2 > > Version: 1.9.19~dfsg-2 > > Severity: grave > > X-Debbugs-Cc: it9exm@gmail.com > > > > Apparently there is something wrong with Jack and dbus. > > Also reported here: > > > https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/ > > Find below the jack server logs. > > > > 00:41:32.228 Resetta le statistiche. > > 00:41:32.269 Connessioni di ALSA cambiate. > > 00:41:32.389 D-BUS: Servizio disponibile (org.jackaudio.service aka > jackdbus). > > Cannot connect to server socket err = File o directory non esistente > > Cannot connect to server request channel > > jack server is not running or cannot be started > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > 00:41:32.563 Cambiamento nel grafico delle connessioni di ALSA. > > 00:41:47.432 D-BUS: il server JACK non può essere avviato. Mi dispiace > > Sun Nov 21 00:41:47 2021: Starting jack server... > > Sun Nov 21 00:41:47 2021: JACK server starting in realtime mode with > priority > > 10 > > Sun Nov 21 00:41:47 2021: self-connect-mode is "Don't restrict self > connect > > requests" > > Cannot connect to server socket err = File o directory non esistente > > Cannot connect to server request channel > > jack server is not running or cannot be started > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > Sun Nov 21 00:41:47 2021: Device reservation request with priority > 2147483647 > > denied for "Audio1": org.freedesktop.DBus.Error.UnknownMethod (Method > > RequestRelease is not implemented on interface > org.freedesktop.ReserveDevice1) > > Sun Nov 21 00:41:47 2021: ERROR: Failed to acquire device name : Audio1 > error : > > Method RequestRelease is not implemented on interface > > org.freedesktop.ReserveDevice1 > > Sun Nov 21 00:41:47 2021: ERROR: Audio device hw:PCH,0 cannot be > acquired... > > Sun Nov 21 00:41:47 2021: ERROR: Cannot initialize driver > > Sun Nov 21 00:41:47 2021: ERROR: JackServer::Open failed with -1 > > Sun Nov 21 00:41:47 2021: ERROR: Failed to open server > > Sun Nov 21 00:41:48 2021: Saving settings to > > "/home/it9exm/.config/jack/conf.xml" ... > > 00:41:49.469 Non sono riuscito ad avviare JACK come client. - Operazione > > fallita. - Impossibile connettersi al server JACK. Controlla la finestra > dei > > messaggi per maggiori informazioni. > > Cannot connect to server socket err = File o directory non esistente > > Cannot connect to server request channel > > jack server is not running or cannot be started > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > Unfortunately I'm not able to reprodue this issue. Are you running > pipewire by any chance? > > Best > Sebastian > > > > > > > -- System Information: > > Debian Release: bookworm/sid > > APT prefers unstable > > APT policy: (500, 'unstable'), (1, 'experimental') > > Architecture: amd64 (x86_64) > > Foreign Architectures: i386 > > > > Kernel: Linux 5.14.19-xanmod1 (SMP w/4 CPU threads) > > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > > Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE > not set > > Shell: /bin/sh linked to /usr/bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > Versions of packages jackd2 depends on: > > ii debconf [debconf-2.0] 1.5.79 > > ii libasound2 1.2.5.1-1 > > ii libc6 2.32-4 > > ii libdbus-1-3 1.12.20-3 > > ii libexpat1 2.4.1-3 > > ii libgcc-s1 11.2.0-10 > > ii libjack-jackd2-0 1.9.19~dfsg-2 > > ii libreadline8 8.1-2 > > ii libsamplerate0 0.2.2-1 > > ii libsndfile1 1.0.31-2 > > ii libstdc++6 11.2.0-10 > > ii libsystemd0 249.6-2 > > ii libzita-alsa-pcmi0 0.3.2-2 > > ii libzita-resampler1 1.8.0-2 > > ii python3 3.9.8-1 > > ii python3-dbus 1.2.18-3 > > > > Versions of packages jackd2 recommends: > > ii jackd2-firewire 1.9.19~dfsg-2 > > ii libpam-modules 1.4.0-10 > > ii qjackctl 0.9.5-1 > > > > Versions of packages jackd2 suggests: > > pn jack-tools <none> > > pn meterbridge <none> > > > > -- debconf information: > > * jackd/tweak_rt_limits: true > > -- > Sebastian Ramacher >
[Message part 2 (text/html, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Fri, 03 Dec 2021 11:54:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Cráudio <claudiohpb@protonmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Fri, 03 Dec 2021 11:54:02 GMT) (full text, mbox, link).
Message #27 received at 1000293@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
I have the same problem! Sent with [ProtonMail](https://protonmail.com/) Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Em sábado, 27 de novembro de 2021 às 18:14, Arnaldo Pirrone <it9exm@gmail.com> escreveu: > I guess so, I have both pipewire and pipewire-pulse in the output of ps > Altgough I have no idea what that is for > > Il lun 22 nov 2021, 11:50 Sebastian Ramacher <sramacher@debian.org> ha scritto: > >> Control: tags -1 moreinfo >> >> On 2021-11-21 00:55:50, Arnaldo Pirrone wrote: >>> Package: jackd2 >>> Version: 1.9.19~dfsg-2 >>> Severity: grave >>> X-Debbugs-Cc: it9exm@gmail.com >>> >>> Apparently there is something wrong with Jack and dbus. >>> Also reported here: >>> https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/ >>> Find below the jack server logs. >>> >>> 00:41:32.228 Resetta le statistiche. >>> 00:41:32.269 Connessioni di ALSA cambiate. >>> 00:41:32.389 D-BUS: Servizio disponibile (org.jackaudio.service aka jackdbus). >>> Cannot connect to server socket err = File o directory non esistente >>> Cannot connect to server request channel >>> jack server is not running or cannot be started >>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>> unlock >>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>> unlock >>> 00:41:32.563 Cambiamento nel grafico delle connessioni di ALSA. >>> 00:41:47.432 D-BUS: il server JACK non può essere avviato. Mi dispiace >>> Sun Nov 21 00:41:47 2021: Starting jack server... >>> Sun Nov 21 00:41:47 2021: JACK server starting in realtime mode with priority >>> 10 >>> Sun Nov 21 00:41:47 2021: self-connect-mode is "Don't restrict self connect >>> requests" >>> Cannot connect to server socket err = File o directory non esistente >>> Cannot connect to server request channel >>> jack server is not running or cannot be started >>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>> unlock >>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>> unlock >>> Sun Nov 21 00:41:47 2021: Device reservation request with priority 2147483647 >>> denied for "Audio1": org.freedesktop.DBus.Error.UnknownMethod (Method >>> RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1) >>> Sun Nov 21 00:41:47 2021: ERROR: Failed to acquire device name : Audio1 error : >>> Method RequestRelease is not implemented on interface >>> org.freedesktop.ReserveDevice1 >>> Sun Nov 21 00:41:47 2021: ERROR: Audio device hw:PCH,0 cannot be acquired... >>> Sun Nov 21 00:41:47 2021: ERROR: Cannot initialize driver >>> Sun Nov 21 00:41:47 2021: ERROR: JackServer::Open failed with -1 >>> Sun Nov 21 00:41:47 2021: ERROR: Failed to open server >>> Sun Nov 21 00:41:48 2021: Saving settings to >>> "/home/it9exm/.config/jack/conf.xml" ... >>> 00:41:49.469 Non sono riuscito ad avviare JACK come client. - Operazione >>> fallita. - Impossibile connettersi al server JACK. Controlla la finestra dei >>> messaggi per maggiori informazioni. >>> Cannot connect to server socket err = File o directory non esistente >>> Cannot connect to server request channel >>> jack server is not running or cannot be started >>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>> unlock >>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>> unlock >> >> Unfortunately I'm not able to reprodue this issue. Are you running >> pipewire by any chance? >> >> Best >> Sebastian >> >>> >>> >>> -- System Information: >>> Debian Release: bookworm/sid >>> APT prefers unstable >>> APT policy: (500, 'unstable'), (1, 'experimental') >>> Architecture: amd64 (x86_64) >>> Foreign Architectures: i386 >>> >>> Kernel: Linux 5.14.19-xanmod1 (SMP w/4 CPU threads) >>> Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE >>> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set >>> Shell: /bin/sh linked to /usr/bin/dash >>> Init: systemd (via /run/systemd/system) >>> LSM: AppArmor: enabled >>> >>> Versions of packages jackd2 depends on: >>> ii debconf [debconf-2.0] 1.5.79 >>> ii libasound2 1.2.5.1-1 >>> ii libc6 2.32-4 >>> ii libdbus-1-3 1.12.20-3 >>> ii libexpat1 2.4.1-3 >>> ii libgcc-s1 11.2.0-10 >>> ii libjack-jackd2-0 1.9.19~dfsg-2 >>> ii libreadline8 8.1-2 >>> ii libsamplerate0 0.2.2-1 >>> ii libsndfile1 1.0.31-2 >>> ii libstdc++6 11.2.0-10 >>> ii libsystemd0 249.6-2 >>> ii libzita-alsa-pcmi0 0.3.2-2 >>> ii libzita-resampler1 1.8.0-2 >>> ii python3 3.9.8-1 >>> ii python3-dbus 1.2.18-3 >>> >>> Versions of packages jackd2 recommends: >>> ii jackd2-firewire 1.9.19~dfsg-2 >>> ii libpam-modules 1.4.0-10 >>> ii qjackctl 0.9.5-1 >>> >>> Versions of packages jackd2 suggests: >>> pn jack-tools <none> >>> pn meterbridge <none> >>> >>> -- debconf information: >>> * jackd/tweak_rt_limits: true >> >> -- >> Sebastian Ramacher
[Message part 2 (text/html, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Fri, 03 Dec 2021 12:03:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Cráudio <claudiohpb@protonmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Fri, 03 Dec 2021 12:03:03 GMT) (full text, mbox, link).
Message #32 received at 1000293@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
08:57:37.986 Reiniciar estatísticas. 08:57:38.009 Alteração de conexão ALSA. Cannot connect to server socket err = Arquivo ou diretório inexistente Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock 08:57:38.044 Alteração no gráfico de conexão ALSA. 08:57:44.807 JACK está iniciando... 08:57:44.808 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p1024 -Xseq Cannot connect to server socket err = Arquivo ou diretório inexistente Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock 08:57:44.829 JACK inicializou com PID=2198. no message buffer overruns no message buffer overruns no message buffer overruns jackdmp 1.9.19 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2021 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Device reservation request with priority 2147483647 denied for "Audio0": org.freedesktop.DBus.Error.UnknownMethod (Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1) Failed to acquire device name : Audio0 error : Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1 Audio device hw:0 cannot be acquired... Cannot initialize driver JackServer::Open failed with -1 Failed to open server 08:57:44.964 JACK foi parado 08:57:46.923 Não foi possível conectar-se ao servidor JACK como cliente. - Operação global falhou. - Não foi possível conectar-se ao servidor. Por favor, verifique a janela de mensagens para mais informações. Cannot connect to server socket err = Arquivo ou diretório inexistente Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock Sent with [ProtonMail](https://protonmail.com/) Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Em sexta-feira, 3 de dezembro de 2021 às 08:51, Cráudio <claudiohpb@protonmail.com> escreveu: > I have the same problem! > > Sent with [ProtonMail](https://protonmail.com/) Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > Em sábado, 27 de novembro de 2021 às 18:14, Arnaldo Pirrone <it9exm@gmail.com> escreveu: > >> I guess so, I have both pipewire and pipewire-pulse in the output of ps >> Altgough I have no idea what that is for >> >> Il lun 22 nov 2021, 11:50 Sebastian Ramacher <sramacher@debian.org> ha scritto: >> >>> Control: tags -1 moreinfo >>> >>> On 2021-11-21 00:55:50, Arnaldo Pirrone wrote: >>>> Package: jackd2 >>>> Version: 1.9.19~dfsg-2 >>>> Severity: grave >>>> X-Debbugs-Cc: it9exm@gmail.com >>>> >>>> Apparently there is something wrong with Jack and dbus. >>>> Also reported here: >>>> https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/ >>>> Find below the jack server logs. >>>> >>>> 00:41:32.228 Resetta le statistiche. >>>> 00:41:32.269 Connessioni di ALSA cambiate. >>>> 00:41:32.389 D-BUS: Servizio disponibile (org.jackaudio.service aka jackdbus). >>>> Cannot connect to server socket err = File o directory non esistente >>>> Cannot connect to server request channel >>>> jack server is not running or cannot be started >>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>> unlock >>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>> unlock >>>> 00:41:32.563 Cambiamento nel grafico delle connessioni di ALSA. >>>> 00:41:47.432 D-BUS: il server JACK non può essere avviato. Mi dispiace >>>> Sun Nov 21 00:41:47 2021: Starting jack server... >>>> Sun Nov 21 00:41:47 2021: JACK server starting in realtime mode with priority >>>> 10 >>>> Sun Nov 21 00:41:47 2021: self-connect-mode is "Don't restrict self connect >>>> requests" >>>> Cannot connect to server socket err = File o directory non esistente >>>> Cannot connect to server request channel >>>> jack server is not running or cannot be started >>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>> unlock >>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>> unlock >>>> Sun Nov 21 00:41:47 2021: Device reservation request with priority 2147483647 >>>> denied for "Audio1": org.freedesktop.DBus.Error.UnknownMethod (Method >>>> RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1) >>>> Sun Nov 21 00:41:47 2021: ERROR: Failed to acquire device name : Audio1 error : >>>> Method RequestRelease is not implemented on interface >>>> org.freedesktop.ReserveDevice1 >>>> Sun Nov 21 00:41:47 2021: ERROR: Audio device hw:PCH,0 cannot be acquired... >>>> Sun Nov 21 00:41:47 2021: ERROR: Cannot initialize driver >>>> Sun Nov 21 00:41:47 2021: ERROR: JackServer::Open failed with -1 >>>> Sun Nov 21 00:41:47 2021: ERROR: Failed to open server >>>> Sun Nov 21 00:41:48 2021: Saving settings to >>>> "/home/it9exm/.config/jack/conf.xml" ... >>>> 00:41:49.469 Non sono riuscito ad avviare JACK come client. - Operazione >>>> fallita. - Impossibile connettersi al server JACK. Controlla la finestra dei >>>> messaggi per maggiori informazioni. >>>> Cannot connect to server socket err = File o directory non esistente >>>> Cannot connect to server request channel >>>> jack server is not running or cannot be started >>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>> unlock >>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>> unlock >>> >>> Unfortunately I'm not able to reprodue this issue. Are you running >>> pipewire by any chance? >>> >>> Best >>> Sebastian >>> >>>> >>>> >>>> -- System Information: >>>> Debian Release: bookworm/sid >>>> APT prefers unstable >>>> APT policy: (500, 'unstable'), (1, 'experimental') >>>> Architecture: amd64 (x86_64) >>>> Foreign Architectures: i386 >>>> >>>> Kernel: Linux 5.14.19-xanmod1 (SMP w/4 CPU threads) >>>> Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE >>>> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set >>>> Shell: /bin/sh linked to /usr/bin/dash >>>> Init: systemd (via /run/systemd/system) >>>> LSM: AppArmor: enabled >>>> >>>> Versions of packages jackd2 depends on: >>>> ii debconf [debconf-2.0] 1.5.79 >>>> ii libasound2 1.2.5.1-1 >>>> ii libc6 2.32-4 >>>> ii libdbus-1-3 1.12.20-3 >>>> ii libexpat1 2.4.1-3 >>>> ii libgcc-s1 11.2.0-10 >>>> ii libjack-jackd2-0 1.9.19~dfsg-2 >>>> ii libreadline8 8.1-2 >>>> ii libsamplerate0 0.2.2-1 >>>> ii libsndfile1 1.0.31-2 >>>> ii libstdc++6 11.2.0-10 >>>> ii libsystemd0 249.6-2 >>>> ii libzita-alsa-pcmi0 0.3.2-2 >>>> ii libzita-resampler1 1.8.0-2 >>>> ii python3 3.9.8-1 >>>> ii python3-dbus 1.2.18-3 >>>> >>>> Versions of packages jackd2 recommends: >>>> ii jackd2-firewire 1.9.19~dfsg-2 >>>> ii libpam-modules 1.4.0-10 >>>> ii qjackctl 0.9.5-1 >>>> >>>> Versions of packages jackd2 suggests: >>>> pn jack-tools <none> >>>> pn meterbridge <none> >>>> >>>> -- debconf information: >>>> * jackd/tweak_rt_limits: true >>> >>> -- >>> Sebastian Ramacher
[Message part 2 (text/html, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Sat, 11 Dec 2021 16:51:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Arnaldo Pirrone <it9exm@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Sat, 11 Dec 2021 16:51:03 GMT) (full text, mbox, link).
Message #37 received at 1000293@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
I just learned about pipewire and love it. By following this I was able to work around this https://wiki.debian.org/PipeWire#For_JACK May this issue report help in getting a jackd2 install that works right away for the future releases. (Not sure if that's already true on a clean install) Il ven 3 dic 2021, 13:00 Cráudio <claudiohpb@protonmail.com> ha scritto: > 08:57:37.986 Reiniciar estatísticas. > 08:57:38.009 Alteração de conexão ALSA. > Cannot connect to server socket err = Arquivo ou diretório inexistente > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock > 08:57:38.044 Alteração no gráfico de conexão ALSA. > 08:57:44.807 JACK está iniciando... > 08:57:44.808 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p1024 -Xseq > Cannot connect to server socket err = Arquivo ou diretório inexistente > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock > 08:57:44.829 JACK inicializou com PID=2198. > no message buffer overruns > no message buffer overruns > no message buffer overruns > jackdmp 1.9.19 > Copyright 2001-2005 Paul Davis and others. > Copyright 2004-2016 Grame. > Copyright 2016-2021 Filipe Coelho. > jackdmp comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details > JACK server starting in realtime mode with priority 10 > self-connect-mode is "Don't restrict self connect requests" > audio_reservation_init > Device reservation request with priority 2147483647 denied for "Audio0": > org.freedesktop.DBus.Error.UnknownMethod (Method RequestRelease is not > implemented on interface org.freedesktop.ReserveDevice1) > Failed to acquire device name : Audio0 error : Method RequestRelease is > not implemented on interface org.freedesktop.ReserveDevice1 > Audio device hw:0 cannot be acquired... > Cannot initialize driver > JackServer::Open failed with -1 > Failed to open server > 08:57:44.964 JACK foi parado > 08:57:46.923 Não foi possível conectar-se ao servidor JACK como cliente. - > Operação global falhou. - Não foi possível conectar-se ao servidor. Por > favor, verifique a janela de mensagens para mais informações. > Cannot connect to server socket err = Arquivo ou diretório inexistente > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping > unlock > > > Sent with ProtonMail <https://protonmail.com/> Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > Em sexta-feira, 3 de dezembro de 2021 às 08:51, Cráudio < > claudiohpb@protonmail.com> escreveu: > > I have the same problem! > > > Sent with ProtonMail <https://protonmail.com/> Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > Em sábado, 27 de novembro de 2021 às 18:14, Arnaldo Pirrone < > it9exm@gmail.com> escreveu: > > I guess so, I have both pipewire and pipewire-pulse in the output of ps > Altgough I have no idea what that is for > > Il lun 22 nov 2021, 11:50 Sebastian Ramacher <sramacher@debian.org> ha > scritto: > >> Control: tags -1 moreinfo >> >> On 2021-11-21 00:55:50, Arnaldo Pirrone wrote: >> > Package: jackd2 >> > Version: 1.9.19~dfsg-2 >> > Severity: grave >> > X-Debbugs-Cc: it9exm@gmail.com >> > >> > Apparently there is something wrong with Jack and dbus. >> > Also reported here: >> > >> https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/ >> > Find below the jack server logs. >> > >> > 00:41:32.228 Resetta le statistiche. >> > 00:41:32.269 Connessioni di ALSA cambiate. >> > 00:41:32.389 D-BUS: Servizio disponibile (org.jackaudio.service aka >> jackdbus). >> > Cannot connect to server socket err = File o directory non esistente >> > Cannot connect to server request channel >> > jack server is not running or cannot be started >> > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping >> > unlock >> > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping >> > unlock >> > 00:41:32.563 Cambiamento nel grafico delle connessioni di ALSA. >> > 00:41:47.432 D-BUS: il server JACK non può essere avviato. Mi dispiace >> > Sun Nov 21 00:41:47 2021: Starting jack server... >> > Sun Nov 21 00:41:47 2021: JACK server starting in realtime mode with >> priority >> > 10 >> > Sun Nov 21 00:41:47 2021: self-connect-mode is "Don't restrict self >> connect >> > requests" >> > Cannot connect to server socket err = File o directory non esistente >> > Cannot connect to server request channel >> > jack server is not running or cannot be started >> > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping >> > unlock >> > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping >> > unlock >> > Sun Nov 21 00:41:47 2021: Device reservation request with priority >> 2147483647 >> > denied for "Audio1": org.freedesktop.DBus.Error.UnknownMethod (Method >> > RequestRelease is not implemented on interface >> org.freedesktop.ReserveDevice1) >> > Sun Nov 21 00:41:47 2021: ERROR: Failed to acquire device name : Audio1 >> error : >> > Method RequestRelease is not implemented on interface >> > org.freedesktop.ReserveDevice1 >> > Sun Nov 21 00:41:47 2021: ERROR: Audio device hw:PCH,0 cannot be >> acquired... >> > Sun Nov 21 00:41:47 2021: ERROR: Cannot initialize driver >> > Sun Nov 21 00:41:47 2021: ERROR: JackServer::Open failed with -1 >> > Sun Nov 21 00:41:47 2021: ERROR: Failed to open server >> > Sun Nov 21 00:41:48 2021: Saving settings to >> > "/home/it9exm/.config/jack/conf.xml" ... >> > 00:41:49.469 Non sono riuscito ad avviare JACK come client. - Operazione >> > fallita. - Impossibile connettersi al server JACK. Controlla la >> finestra dei >> > messaggi per maggiori informazioni. >> > Cannot connect to server socket err = File o directory non esistente >> > Cannot connect to server request channel >> > jack server is not running or cannot be started >> > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping >> > unlock >> > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping >> > unlock >> >> Unfortunately I'm not able to reprodue this issue. Are you running >> pipewire by any chance? >> >> Best >> Sebastian >> >> > >> > >> > -- System Information: >> > Debian Release: bookworm/sid >> > APT prefers unstable >> > APT policy: (500, 'unstable'), (1, 'experimental') >> > Architecture: amd64 (x86_64) >> > Foreign Architectures: i386 >> > >> > Kernel: Linux 5.14.19-xanmod1 (SMP w/4 CPU threads) >> > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE >> > Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), >> LANGUAGE not set >> > Shell: /bin/sh linked to /usr/bin/dash >> > Init: systemd (via /run/systemd/system) >> > LSM: AppArmor: enabled >> > >> > Versions of packages jackd2 depends on: >> > ii debconf [debconf-2.0] 1.5.79 >> > ii libasound2 1.2.5.1-1 >> > ii libc6 2.32-4 >> > ii libdbus-1-3 1.12.20-3 >> > ii libexpat1 2.4.1-3 >> > ii libgcc-s1 11.2.0-10 >> > ii libjack-jackd2-0 1.9.19~dfsg-2 >> > ii libreadline8 8.1-2 >> > ii libsamplerate0 0.2.2-1 >> > ii libsndfile1 1.0.31-2 >> > ii libstdc++6 11.2.0-10 >> > ii libsystemd0 249.6-2 >> > ii libzita-alsa-pcmi0 0.3.2-2 >> > ii libzita-resampler1 1.8.0-2 >> > ii python3 3.9.8-1 >> > ii python3-dbus 1.2.18-3 >> > >> > Versions of packages jackd2 recommends: >> > ii jackd2-firewire 1.9.19~dfsg-2 >> > ii libpam-modules 1.4.0-10 >> > ii qjackctl 0.9.5-1 >> > >> > Versions of packages jackd2 suggests: >> > pn jack-tools <none> >> > pn meterbridge <none> >> > >> > -- debconf information: >> > * jackd/tweak_rt_limits: true >> >> -- >> Sebastian Ramacher >> > > >
[Message part 2 (text/html, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Wed, 22 Dec 2021 15:00:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Cráudio <claudiohpb@protonmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Wed, 22 Dec 2021 15:00:03 GMT) (full text, mbox, link).
Message #42 received at 1000293@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Hi Arnold! Did this pipewire interface solve the bug for you? I found this guidance regarding the issue: https://www.reddit.com/r/ChrisTitusTech/comments/g0xexz/cant_run_jack/ In the official ALSA documentation: https://www.alsa-project.org/main/index.php/Asoundrc#JACK_plugin Does it make sense to you? Best Regards!Hi Arnold! Did this pipewire interface solve the bug for you? I found this guidance regarding the issue: https://www.reddit.com/r/ChrisTitusTech/comments/g0xexz/cant_run_jack/ In the official ALSA documentation: https://www.alsa-project.org/main/index.php/Asoundrc#JACK_plugin Does it make sense to you? Best Regards!Hi Arnaldo! Did this pipewire interface solve the bug for you? I found this guidance regarding the issue: https://www.reddit.com/r/ChrisTitusTech/comments/g0xexz/cant_run_jack/ In the official ALSA documentation: https://www.alsa-project.org/main/index.php/Asoundrc#JACK_plugin Does it make sense to you? Best Regards! Cráudio. Sent with [ProtonMail](https://protonmail.com/) Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Em sábado, 11 de dezembro de 2021 às 13:47, Arnaldo Pirrone <it9exm@gmail.com> escreveu: > I just learned about pipewire and love it. > > By following this I was able to work around this > https://wiki.debian.org/PipeWire#For_JACK > > May this issue report help in getting a jackd2 install that works right away for the future releases. (Not sure if that's already true on a clean install) > > Il ven 3 dic 2021, 13:00 Cráudio <claudiohpb@protonmail.com> ha scritto: > >> 08:57:37.986 Reiniciar estatísticas. >> 08:57:38.009 Alteração de conexão ALSA. >> Cannot connect to server socket err = Arquivo ou diretório inexistente >> Cannot connect to server request channel >> jack server is not running or cannot be started >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock >> 08:57:38.044 Alteração no gráfico de conexão ALSA. >> 08:57:44.807 JACK está iniciando... >> 08:57:44.808 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p1024 -Xseq >> Cannot connect to server socket err = Arquivo ou diretório inexistente >> Cannot connect to server request channel >> jack server is not running or cannot be started >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock >> 08:57:44.829 JACK inicializou com PID=2198. >> no message buffer overruns >> no message buffer overruns >> no message buffer overruns >> jackdmp 1.9.19 >> Copyright 2001-2005 Paul Davis and others. >> Copyright 2004-2016 Grame. >> Copyright 2016-2021 Filipe Coelho. >> jackdmp comes with ABSOLUTELY NO WARRANTY >> This is free software, and you are welcome to redistribute it >> under certain conditions; see the file COPYING for details >> JACK server starting in realtime mode with priority 10 >> self-connect-mode is "Don't restrict self connect requests" >> audio_reservation_init >> Device reservation request with priority 2147483647 denied for "Audio0": org.freedesktop.DBus.Error.UnknownMethod (Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1) >> Failed to acquire device name : Audio0 error : Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1 >> Audio device hw:0 cannot be acquired... >> Cannot initialize driver >> JackServer::Open failed with -1 >> Failed to open server >> 08:57:44.964 JACK foi parado >> 08:57:46.923 Não foi possível conectar-se ao servidor JACK como cliente. - Operação global falhou. - Não foi possível conectar-se ao servidor. Por favor, verifique a janela de mensagens para mais informações. >> Cannot connect to server socket err = Arquivo ou diretório inexistente >> Cannot connect to server request channel >> jack server is not running or cannot be started >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock >> >> Sent with [ProtonMail](https://protonmail.com/) Secure Email. >> >> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >> Em sexta-feira, 3 de dezembro de 2021 às 08:51, Cráudio <claudiohpb@protonmail.com> escreveu: >> >>> I have the same problem! >>> >>> Sent with [ProtonMail](https://protonmail.com/) Secure Email. >>> >>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>> Em sábado, 27 de novembro de 2021 às 18:14, Arnaldo Pirrone <it9exm@gmail.com> escreveu: >>> >>>> I guess so, I have both pipewire and pipewire-pulse in the output of ps >>>> Altgough I have no idea what that is for >>>> >>>> Il lun 22 nov 2021, 11:50 Sebastian Ramacher <sramacher@debian.org> ha scritto: >>>> >>>>> Control: tags -1 moreinfo >>>>> >>>>> On 2021-11-21 00:55:50, Arnaldo Pirrone wrote: >>>>>> Package: jackd2 >>>>>> Version: 1.9.19~dfsg-2 >>>>>> Severity: grave >>>>>> X-Debbugs-Cc: it9exm@gmail.com >>>>>> >>>>>> Apparently there is something wrong with Jack and dbus. >>>>>> Also reported here: >>>>>> https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/ >>>>>> Find below the jack server logs. >>>>>> >>>>>> 00:41:32.228 Resetta le statistiche. >>>>>> 00:41:32.269 Connessioni di ALSA cambiate. >>>>>> 00:41:32.389 D-BUS: Servizio disponibile (org.jackaudio.service aka jackdbus). >>>>>> Cannot connect to server socket err = File o directory non esistente >>>>>> Cannot connect to server request channel >>>>>> jack server is not running or cannot be started >>>>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>>>> unlock >>>>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>>>> unlock >>>>>> 00:41:32.563 Cambiamento nel grafico delle connessioni di ALSA. >>>>>> 00:41:47.432 D-BUS: il server JACK non può essere avviato. Mi dispiace >>>>>> Sun Nov 21 00:41:47 2021: Starting jack server... >>>>>> Sun Nov 21 00:41:47 2021: JACK server starting in realtime mode with priority >>>>>> 10 >>>>>> Sun Nov 21 00:41:47 2021: self-connect-mode is "Don't restrict self connect >>>>>> requests" >>>>>> Cannot connect to server socket err = File o directory non esistente >>>>>> Cannot connect to server request channel >>>>>> jack server is not running or cannot be started >>>>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>>>> unlock >>>>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>>>> unlock >>>>>> Sun Nov 21 00:41:47 2021: Device reservation request with priority 2147483647 >>>>>> denied for "Audio1": org.freedesktop.DBus.Error.UnknownMethod (Method >>>>>> RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1) >>>>>> Sun Nov 21 00:41:47 2021: ERROR: Failed to acquire device name : Audio1 error : >>>>>> Method RequestRelease is not implemented on interface >>>>>> org.freedesktop.ReserveDevice1 >>>>>> Sun Nov 21 00:41:47 2021: ERROR: Audio device hw:PCH,0 cannot be acquired... >>>>>> Sun Nov 21 00:41:47 2021: ERROR: Cannot initialize driver >>>>>> Sun Nov 21 00:41:47 2021: ERROR: JackServer::Open failed with -1 >>>>>> Sun Nov 21 00:41:47 2021: ERROR: Failed to open server >>>>>> Sun Nov 21 00:41:48 2021: Saving settings to >>>>>> "/home/it9exm/.config/jack/conf.xml" ... >>>>>> 00:41:49.469 Non sono riuscito ad avviare JACK come client. - Operazione >>>>>> fallita. - Impossibile connettersi al server JACK. Controlla la finestra dei >>>>>> messaggi per maggiori informazioni. >>>>>> Cannot connect to server socket err = File o directory non esistente >>>>>> Cannot connect to server request channel >>>>>> jack server is not running or cannot be started >>>>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>>>> unlock >>>>>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping >>>>>> unlock >>>>> >>>>> Unfortunately I'm not able to reprodue this issue. Are you running >>>>> pipewire by any chance? >>>>> >>>>> Best >>>>> Sebastian >>>>> >>>>>> >>>>>> >>>>>> -- System Information: >>>>>> Debian Release: bookworm/sid >>>>>> APT prefers unstable >>>>>> APT policy: (500, 'unstable'), (1, 'experimental') >>>>>> Architecture: amd64 (x86_64) >>>>>> Foreign Architectures: i386 >>>>>> >>>>>> Kernel: Linux 5.14.19-xanmod1 (SMP w/4 CPU threads) >>>>>> Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE >>>>>> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set >>>>>> Shell: /bin/sh linked to /usr/bin/dash >>>>>> Init: systemd (via /run/systemd/system) >>>>>> LSM: AppArmor: enabled >>>>>> >>>>>> Versions of packages jackd2 depends on: >>>>>> ii debconf [debconf-2.0] 1.5.79 >>>>>> ii libasound2 1.2.5.1-1 >>>>>> ii libc6 2.32-4 >>>>>> ii libdbus-1-3 1.12.20-3 >>>>>> ii libexpat1 2.4.1-3 >>>>>> ii libgcc-s1 11.2.0-10 >>>>>> ii libjack-jackd2-0 1.9.19~dfsg-2 >>>>>> ii libreadline8 8.1-2 >>>>>> ii libsamplerate0 0.2.2-1 >>>>>> ii libsndfile1 1.0.31-2 >>>>>> ii libstdc++6 11.2.0-10 >>>>>> ii libsystemd0 249.6-2 >>>>>> ii libzita-alsa-pcmi0 0.3.2-2 >>>>>> ii libzita-resampler1 1.8.0-2 >>>>>> ii python3 3.9.8-1 >>>>>> ii python3-dbus 1.2.18-3 >>>>>> >>>>>> Versions of packages jackd2 recommends: >>>>>> ii jackd2-firewire 1.9.19~dfsg-2 >>>>>> ii libpam-modules 1.4.0-10 >>>>>> ii qjackctl 0.9.5-1 >>>>>> >>>>>> Versions of packages jackd2 suggests: >>>>>> pn jack-tools <none> >>>>>> pn meterbridge <none> >>>>>> >>>>>> -- debconf information: >>>>>> * jackd/tweak_rt_limits: true >>>>> >>>>> -- >>>>> Sebastian Ramacher
[Message part 2 (text/html, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Thu, 30 Dec 2021 17:09:02 GMT) (full text, mbox, link).
Acknowledgement sent
to chris <inkbottle007@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Thu, 30 Dec 2021 17:09:02 GMT) (full text, mbox, link).
Message #47 received at 1000293@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
`pipewire` is providing its own replacement for `jack`, so if you are using `pipewire` maybe you should not have `jackd2` installed at all. I think I've done exactly the following: ``` aptitude --schedule-only install libspa-0.2-jack qsynth rosegarden; aptitude --schedule-only full-upgrade; aptitude install aptitude purge pulseaudio pulseaudio-module-bluetooth pulseaudio-module-gsettings aptitude purge qjackctl jackd jackd2 ``` Then, to start an app needing `jack`, I did: `pw-jack qsynth` (don't forget to add a soundfont in `settups/soudfounts`) then: `rosegarden 28316.mid` (you must go in `studio/manage midi devices` and select a mdi output) And it worked. I'm using unstable. Right after switching to pipewire, I did: ``` aptitude install libspa-0.2-bluetooth pipewire-audio-client-libraries aptitude purge pipewire-media-session aptitude reinstall wireplumber ``` Maybe as a user you should do: ``` systemctl --user --now disable pulseaudio.service pulseaudio.socket systemctl --user mask pulseaudio systemctl --user restart pipewire ``` Maybe there should be a dependency conflict between `pipewire `and `jackd`? Also, concerning <q cite="https://wiki.debian.org/PipeWire#For_JACK[1]"> Either run JACK clients using the pw-jack wrapper, or copy: # cp /usr/share/doc/pipewire/examples/ld.so.conf.d/pipewire-jack-*.conf /etc/ld.so.conf.d/ And run: # ldconfig </q> maybe it should be fixed at the debian package level, and hence a bug should be filled against `libspa-0.2-jack[2]`? I hope it helps, Chris -------- [1] https://wiki.debian.org/PipeWire#For_JACK [2] https://packages.debian.org/libspa-0.2-jack
[Message part 2 (text/html, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Sat, 15 Jan 2022 17:27:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Cráudio <claudiohpb@protonmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Sat, 15 Jan 2022 17:27:03 GMT) (full text, mbox, link).
Message #52 received at 1000293@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attentioHi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention! Cláudio. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Em quinta-feira, 30 de dezembro de 2021 às 14:03, chris <inkbottle007@gmail.com> escreveu: > `pipewire` is providing its own replacement for `jack`, so if you are using `pipewire` maybe you should not have `jackd2` installed at all. > > I think I've done exactly the following: > > ``` > > aptitude --schedule-only install libspa-0.2-jack qsynth rosegarden; aptitude --schedule-only full-upgrade; aptitude install > > aptitude purge pulseaudio pulseaudio-module-bluetooth pulseaudio-module-gsettings > > aptitude purge qjackctl jackd jackd2 > ``` > > Then, to start an app needing `jack`, I did: > > `pw-jack qsynth` (don't forget to add a soundfont in `settups/soudfounts`) > > then: > > `rosegarden 28316.mid` (you must go in `studio/manage midi devices` and select a mdi output) > > And it worked. > > I'm using unstable. > > Right after switching to pipewire, I did: > > ``` > > aptitude install libspa-0.2-bluetooth pipewire-audio-client-libraries > aptitude purge pipewire-media-session > aptitude reinstall wireplumber > ``` > > Maybe as a user you should do: > > ``` > > systemctl --user --now disable pulseaudio.service pulseaudio.socket > > systemctl --user mask pulseaudio > > systemctl --user restart pipewire > ``` > > Maybe there should be a dependency conflict between `pipewire `and `jackd`? > > Also, concerning > > <q cite="https://wiki.debian.org/PipeWire#For_JACK"> > > Either run JACK clients using the pw-jack wrapper, or copy: > > # cp /usr/share/doc/pipewire/examples/ld.so.conf.d/pipewire-jack-*.conf /etc/ld.so.conf.d/ > > And run: > > # ldconfig > </q> > > maybe it should be fixed at the debian package level, and hence a bug should be filled against `[libspa-0.2-jack](https://packages.debian.org/libspa-0.2-jack)`? > > I hope it helps, > > Chris
[Message part 2 (text/html, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Mon, 26 Sep 2022 13:27:02 GMT) (full text, mbox, link).
Acknowledgement sent
to linadavid0089@gmail.com:
Extra info received and forwarded to list. Copy sent to Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Mon, 26 Sep 2022 13:27:03 GMT) (full text, mbox, link).
Message #57 received at 1000293@bugs.debian.org (full text, mbox, reply):
-- Hello, how are you?
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>:
Bug#1000293; Package jackd2.
(Tue, 21 Mar 2023 04:09:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Robin Gareus <robin@gareus.org>:
Extra info received and forwarded to list. Copy sent to Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>.
(Tue, 21 Mar 2023 04:09:03 GMT) (full text, mbox, link).
Message #62 received at 1000293@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Hello fellow Debian users, I wish I had better news for you but at this point in time PipeWire is not a replacement for JACK when it comes to pro-audio. Neither in terms of reliability, performance or features. It is certainly not something to use in a studio with paying customers, or live on stage. There are still regular issues [1] coming up, configuration is still not easily accessible [2], freewheeling does not always work, and performance when using many clients is not yet equal to how JACK handles context-switches. JACK is mature and reliable, musicians can trust it live on stage, pipewire is still under heavy development and sadly not yet ready for prime-time. On the upside JACK and pipewire can co-exist. When jackd requests a device via d-bus, pipewire does (or should) release it. At this point it is even unclear if JACK will be ever be discontinued. A recent discussion at [3] investigates the possibility to run pipewire on top of JACK, but that is a different story. -- robin PS. I have been involved with development of both JACK, design of PipeWire and am developing pro-audio software such as Ardour (I am also a Debian user since Potato). [1] https://discourse.ardour.org/t/ardour-inputs-with-pipewire/108489 [2] https://discourse.ardour.org/t/how-does-pipewire-perform-with-ardour/107381/12 [3] https://lists.linuxaudio.org/hyperkitty/list/linux-audio-dev@lists.linuxaudio.org/thread/I3BSVFO6DU7S2L7ATA7WOSDS7BTS4BPH/ On Sat, 15 Jan 2022 17:14:16 +0000 =?utf-8?Q?Cr=C3=A1udio?= <claudiohpb@protonmail.com> wrote: > Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attentioHi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... > > Thank you for your attention! > > Cláudio. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > Em quinta-feira, 30 de dezembro de 2021 às 14:03, chris <inkbottle007@gmail.com> escreveu: > > > `pipewire` is providing its own replacement for `jack`, so if you are using `pipewire` maybe you should not have `jackd2` installed at all. > > > > I think I've done exactly the following: > > > > ``` > > > > aptitude --schedule-only install libspa-0.2-jack qsynth rosegarden; aptitude --schedule-only full-upgrade; aptitude install > > > > aptitude purge pulseaudio pulseaudio-module-bluetooth pulseaudio-module-gsettings > > > > aptitude purge qjackctl jackd jackd2 > > ``` > > > > Then, to start an app needing `jack`, I did: > > > > `pw-jack qsynth` (don't forget to add a soundfont in `settups/soudfounts`) > > > > then: > > > > `rosegarden 28316.mid` (you must go in `studio/manage midi devices` and select a mdi output) > > > > And it worked. > > > > I'm using unstable. > > > > Right after switching to pipewire, I did: > > > > ``` > > > > aptitude install libspa-0.2-bluetooth pipewire-audio-client-libraries > > aptitude purge pipewire-media-session > > aptitude reinstall wireplumber > > ``` > > > > Maybe as a user you should do: > > > > ``` > > > > systemctl --user --now disable pulseaudio.service pulseaudio.socket > > > > systemctl --user mask pulseaudio > > > > systemctl --user restart pipewire > > ``` > > > > Maybe there should be a dependency conflict between `pipewire `and `jackd`? > > > > Also, concerning > > > > <q cite="https://wiki.debian.org/PipeWire#For_JACK"> > >
[OpenPGP_signature (application/pgp-signature, attachment)]
Reply sent
to Sebastian Ramacher <sramacher@debian.org>:
You have taken responsibility.
(Fri, 02 Jun 2023 19:48:05 GMT) (full text, mbox, link).
Notification sent
to Arnaldo Pirrone <it9exm@gmail.com>:
Bug acknowledged by developer.
(Fri, 02 Jun 2023 19:48:05 GMT) (full text, mbox, link).
Message #67 received at 1000293-done@bugs.debian.org (full text, mbox, reply):
On 2023-03-21 04:59:25 +0100, Robin Gareus wrote: > Hello fellow Debian users, > > I wish I had better news for you but at this point in time PipeWire is not a > replacement for JACK when it comes to pro-audio. Neither in terms of > reliability, performance or features. It is certainly not something to use > in a studio with paying customers, or live on stage. > > There are still regular issues [1] coming up, configuration is still not > easily accessible [2], freewheeling does not always work, and performance > when using many clients is not yet equal to how JACK handles > context-switches. > > JACK is mature and reliable, musicians can trust it live on stage, pipewire > is still under heavy development and sadly not yet ready for prime-time. > > On the upside JACK and pipewire can co-exist. When jackd requests a device > via d-bus, pipewire does (or should) release it. > > At this point it is even unclear if JACK will be ever be discontinued. A > recent discussion at [3] investigates the possibility to run pipewire on top > of JACK, but that is a different story. As JACK and pipewire can co-exist, let's close this bug. Cheers -- Sebastian Ramacher
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Sat, 01 Jul 2023 07:29:10 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.