[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1000293: marked as done (Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1)

Your message dated Fri, 2 Jun 2023 21:46:29 +0200
with message-id <ZHpHFbG9MdKpmCoX@ramacher.at>
and subject line Re: Bug#1000293: Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1
has caused the Debian Bug report #1000293,
regarding Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1000293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000293
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
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

--- End Message ---
Reply to: