From: Max-FT <Max-FT@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Regression in Mumble 1.3.0_3
Date: Sat, 11 Apr 2020 01:33:52 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20858@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
New issue by Max-FT on void-packages repository
https://github.com/void-linux/void-packages/issues/20858
Description:
### System
* xuname:
*Void 5.6.2_1 x86_64 GenuineIntel uptodate rFFF*
* package:
*Mumble 1.3.0_3*
### Expected behavior
Mumble starts up in a second or so (on a SATA SSD)
### Actual behavior
Significantly delayed start up, due to mumble trying to connect to the JACK daemon when it isn't installed w/ output
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
exec of JACK server (command = "/usr/bin/jackd") failed: No such file or directory
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
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
<W>2020-04-10 18:04:11.864 JackAudioSystem: unable to open client due to 2 errors:
<W>2020-04-10 18:04:11.864 JackAudioSystem: JackFailure - overall operation failed
<W>2020-04-10 18:04:11.864 JackAudioSystem: JackServerFailed - unable to connect to the JACK server
### Steps to reproduce the behavior
Upgrade to mumble 1.3.0_3
next reply other threads:[~2020-04-10 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 23:33 Max-FT [this message]
2020-04-11 2:11 ` ScrelliCopter
2020-04-11 2:56 ` ScrelliCopter
2020-04-11 6:18 ` [ISSUE] [CLOSED] " Hoshpak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20858@inbox.vuxu.org \
--to=max-ft@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).