From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Mumble: Segmentation fault
Date: Thu, 05 Sep 2019 22:53:51 +0200 [thread overview]
Message-ID: <20190905205351.anGC503LhfszoxrUOVW4dtqjm5MoubEfnVR7PjxUT1U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14222@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
Closed issue by shumvgolove on void-packages repository
https://github.com/void-linux/void-packages/issues/14222
Description:
Mumble segfaults on startup:
```
Locale is "en_US" (System: "en_US")
TextToSpeech: Failed to contact speech dispatcher.
Database SQLite: "3.29.0"
Overlay: Removing old socket on "/home/sh/.MumbleOverlayPipe"
Overlay: Listening on "/home/sh/.MumbleOverlayPipe"
GlobalShortcutX: Using XI2 2.3
SocketRPC: Removing old socket on "/home/sh/.MumbleSocket"
AudioInput: 96000 bits/s, 48000 hz, 480 sample
OSSOutput: Initialized
Segmentation fault
```
`$ dmesg` returns this error:
```
[ 1536.944422] OSSInput[5914]: segfault at 10 ip 00005555d798adea sp 00007f277e03c950 error 4 in mumble[5555d780d000+1bd000]
[ 1536.944426] Code: 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 89 fb 48 83 ec 38 4c 8b 25 a5 1d 2e 00 64 48 8b 04 25 28 00 00 00 48 89 45 c8 31 c0 <49> 8b 44 24 10 8b 48 14 85 c9 0f 85 c6 02 00 00 48 8d 05 7f 18 2e
```
I think [this](https://github.com/mumble-voip/mumble/issues/3685) is related to issue.
next prev parent reply other threads:[~2019-09-05 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 13:32 [ISSUE] " voidlinux-github
2019-09-05 13:36 ` voidlinux-github
2019-09-05 13:41 ` voidlinux-github
2019-09-05 13:42 ` voidlinux-github
2019-09-05 13:48 ` voidlinux-github
2019-09-05 19:23 ` voidlinux-github
2019-09-05 19:29 ` voidlinux-github
2019-09-05 19:43 ` voidlinux-github
2019-09-05 19:47 ` voidlinux-github
2019-09-05 20:53 ` voidlinux-github [this message]
2019-09-05 21:15 ` voidlinux-github
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=20190905205351.anGC503LhfszoxrUOVW4dtqjm5MoubEfnVR7PjxUT1U@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).