FS#36773 - [mumble] Broken UI

Attached to Project: Community Packages
Opened by Philipp (hollunder) - Monday, 02 September 2013, 09:31 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 13 September 2013, 21:20 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
All I get to see is an unresponsive blank window and a CPU-load of 100%. In the task bar there's also the space for an icon, but no visible icon.
No idea what could be the cause.

Additional info:
* package version(s)
1.2.4-2

* config and/or log files etc.
$ mumble
PulseAudio: Connection failure: Connection refused
CELT bitstream 8000000b from /usr/lib/mumble/libcelt0.so.0.7.0
CELT bitstream 80000010 from /usr/lib/mumble/libcelt0.so.0.11.0
Locale is "en_US" (System: "en_US")
TextToSpeech: Compiled without support for speech-dispatcher
Database SQLite: "3.8.0.1"
Overlay: Removing old socket on "/home/murks/.MumbleOverlayPipe"
Overlay: Listening on "/home/murks/.MumbleOverlayPipe"
GlobalShortcutX: /dev/input/event2: Logitech Logitech(R) Precision(TM) Gamepad
GlobalShortcutX: Unable to open any keyboard input devices under /dev/input, falling back to XInput
GlobalShortcutX: Using XI2 2.0
SocketRPC: Removing old socket on "/home/murks/.MumbleSocket"
AudioInput: 40000 bits/s, 48000 hz, 480 sample
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

Steps to reproduce:
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Friday, 13 September 2013, 21:20 GMT
Reason for closing:  Works for me
Additional comments about closing:  Pretty sure this is not a packaging problem. Reopen if it actually turns out to be one.
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 07 September 2013, 16:36 GMT
Tell me how to reproduce this every time.
Comment by Philipp (hollunder) - Saturday, 07 September 2013, 23:48 GMT
In my case it simple is this way whenever I start it. Since it never worked I have no idea what might cause it. I did nothing but install it on Arch x86. Screenshot attached.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 11 September 2013, 14:55 GMT
I have never gotten that to be honest. I can't reproduce with the given information. Maybe you should ask upstream?
Comment by Philipp (hollunder) - Wednesday, 11 September 2013, 16:17 GMT
So far I've found three issues upstream that look somewhat similar:
http://mumble.sourceforge.net/FAQ/English#Mumble_starts_and_turns_into_white_window_with_no_response_.28_Windows_7_64bit.29
http://sourceforge.net/p/mumble/bugs/1020/
http://sourceforge.net/p/mumble/bugs/933/

The wierd thing is that the windows bug sounds closest to what I'm seeing.

Other information about my system that might be relevant:
openbox
no PA, only libpa
more than one audio device (built in intel, external USB)

I have trouble recovering my sf account, maybe I'll create a new one. I'm not convinced it is an Arch bug, I tend more towards a mumble bug at the moment.

Loading...