Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#23033 - [mumble] crashing on launch

Attached to Project: Community Packages
Opened by Rovanion Luckey (Rovanion) - Thursday, 24 February 2011, 16:45 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 08 March 2011, 02:39 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Mumble launches but does not display any interface.
Output of terminal:
$ mumble
CELT bitstream 8000000b from /usr/lib/mumble/libcelt0.so.0.7.0
CELT bitstream 80000010 from /usr/lib/mumble/libcelt0.so.0.11.0
PulseAudio: Connection failure: Connection refused
Locale is sv_SE
TextToSpeech: Compiled without support for speech-dispatcher
Database SQLite: "3.7.5"
*** WARNING *** The program 'mumble' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=mumble>
Overlay: Removing old socket on "/home/hanna/.MumbleOverlayPipe"
Overlay: Listening on "/home/hanna/.MumbleOverlayPipe"
GlobalShortcutX: Unable to open any keyboard input devices under /dev/input, falling back to XInput
GlobalShortcutX: Using XInput 2.0
GlobalShortcutX: XInput 4:Virtual core XTEST pointer
GlobalShortcutX: XInput 5:Virtual core XTEST keyboard
GlobalShortcutX: XInput 6:Power Button
GlobalShortcutX: XInput 7:Power Button
GlobalShortcutX: XInput 8:CHESEN PS2 to USB Converter
GlobalShortcutX: XInput 9:CHESEN PS2 to USB Converter
GlobalShortcutX: XInput 10:Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)
SocketRPC: Removing old socket on "/home/hanna/.MumbleSocket"
AudioInput: 40000 bits/s, 48000 hz, 480 sample CELT
ALSAAudioOutput: Initialized
ALSAAudioInput: Initing audiocapture default.
ALSAAudioInput: Actual buffer 48000 hz, 1 channel 4096 samples [1024 per period]
AudioInput: Initialized mixer for 1 channel 48000 hz mic and 0 channel 48000 hz echo
ALSAAudioOutput: ALSA reports 10000 output channels. Clamping to 2.
ALSAAudioOutput: Actual buffer 48000 hz, 2 channel 3072 samples [1024 per period]
ALSAAudioOutput: Initializing 2 channel, 48000 hz mixer
AudioOutput: Initialized 2 channel 48000 hz mixer

Additional info:
Mumble 1.2.3

Steps to reproduce:
Install mumble from comunity and run on x86_64
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Tuesday, 08 March 2011, 02:39 GMT
Reason for closing:  No response
Additional comments about closing:  Closing this until further activity. It rather surely is not a bug with the mumble package but perhaps with your audio hardware that hangs indefinitely.

Please reopen when you get more info.
Comment by Jelle van der Waa (jelly) - Thursday, 24 February 2011, 19:38 GMT
doesn't happen here
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 24 February 2011, 20:53 GMT
Move ~/config/Mumble and try again. Did you export your DISPLAY to some other socket before starting it?
Comment by Rovanion Luckey (Rovanion) - Friday, 25 February 2011, 12:12 GMT
I have re/moved my Mumble config file and it changed nothing, it still crashes. To my knowing I did not export my DISPLAY to anything.
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 25 February 2011, 12:50 GMT
Can you give me a gdb backtrace?

Also post output of pacman -Qs celt
Comment by Rovanion Luckey (Rovanion) - Friday, 25 February 2011, 12:56 GMT
I have re/moved my Mumble config file and it changed nothing, it still crashes. To my knowing I did not export my DISPLAY to anything.
Comment by Rovanion Luckey (Rovanion) - Friday, 25 February 2011, 12:59 GMT
$ pacman -Qs celt
local/celt-0.7 0.7.1-2
Low-latency audio communication codec

And here is what I think would be a backtrace:

#0 0x00007ffff5d7234c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007ffff3fe5c1b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#2 0x00007ffff3fe4d10 in QThread::wait(unsigned long) () from /usr/lib/libQtCore.so.4
#3 0x00000000005a7a02 in ?? ()
#4 0x00000000005a7a39 in ?? ()
#5 0x000000000051b27e in ?? ()
#6 0x000000000054c6db in ?? ()
#7 0x000000000054c918 in ?? ()
#8 0x00000000005b940a in ?? ()
#9 0x00007ffff40e331f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#10 0x00007ffff4f42e1e in QAbstractSlider::valueChanged(int) () from /usr/lib/libQtGui.so.4
#11 0x000000000054edfb in ?? ()
#12 0x00000000004a7648 in ?? ()
#13 0x00007ffff3188dcd in __libc_start_main () from /lib/libc.so.6
#14 0x000000000043ce19 in ?? ()
#15 0x00007fffffffe648 in ?? ()
#16 0x000000000000001c in ?? ()
#17 0x0000000000000001 in ?? ()
#18 0x00007fffffffe962 in ?? ()
#19 0x0000000000000000 in ?? ()
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 25 February 2011, 13:05 GMT
Remove your locally installed celt. Though that shouldn't be the reason. The backtrace looks like a thread deadlock. Hm.
Comment by Rovanion Luckey (Rovanion) - Friday, 25 February 2011, 13:29 GMT
No, removing celt-0.7 did nothing.
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 25 February 2011, 20:25 GMT
Can you try to join #mumble@freenode.net and ask one one of the devs what might be the problem here? Just point them to this bug as it already has some info. This doesn't look like a packaging problem.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 28 February 2011, 22:10 GMT
Any news?
Comment by Rovanion Luckey (Rovanion) - Tuesday, 01 March 2011, 13:45 GMT
I went in there and asked yesterday. They asked me to run the debug with debug symbols on the application, unfortunately I won't be able to do so in a couple of days because I don't have acess to the coputer in question.

But do you know where I can get hold of a mumble with debug symbols? Should I compile it myself and if so, how do I compile with debug symbols?
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 07 March 2011, 00:22 GMT
In the PKGBUILD, add !strip to the options=() and replace "make release" with "make debug", then makepkg.

Loading...