After connection only Root channel is visible

[ctwx]

Hi there,

Today I installed on my ASUS EeePC 1201T Mumble. My operating system is openSUSE 11.4 32 bit. After connecting (it doesn't matter which server I choose...) only the "Root" channel is shown.

http://img805.imageshack.us/img805/8383/20110823mumble.th.png

Uploaded with ImageShack.us

Here is the console output:

CELT bitstream 8000000b from /usr/lib/mumble/libcelt0.so.0.7.0
CELT bitstream 8000000e from libcelt0.so.1.0.0
CELT bitstream 80000010 from /usr/lib/mumble/libcelt0.so.0.11.0
Locale is en_US
TextToSpeech: Compiled without support for speech-dispatcher
Database SQLite: "3.7.5" 
Overlay: Removing old socket on "/home/christian/.MumbleOverlayPipe" 
Overlay: Listening on "/home/christian/.MumbleOverlayPipe" 
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/christian/.MumbleSocket" 
AudioInput: 40000 bits/s, 48000 hz, 480 sample CELT
PulseAudio: Starting input alsa_input.pci-0000_00_14.2.analog-stereo
AudioInput: Initialized mixer for 1 channel 44100 hz mic and 0 channel 48000 hz echo
warning: The VAD has been replaced by a hack pending a complete rewrite
Sad panda 
OpenSSL Support: 1 (OpenSSL 1.0.0c 2 Dec 2010)
SSL: Adding recommended CA UTN-USERFirst-Client Authentication and Email
PulseAudio: Forcibly disconnected from PulseAudio

 

Any ideas?

Thanks

[kissaki]

warning: The VAD has been replaced by a hack pending a complete rewrite
Sad panda

So, you know what that is?

Did you check what it is?

Did you fiddle with your systems audio devices or drivers?

 

PulseAudio: Forcibly disconnected from PulseAudio

So, this is probably a result of the above and the reason for your issue.

Mumble seems to get into a state of hung-up / waiting for device which does not answer anymore or sth.

You can still use the client interface normally when connected like that?

Did you check if there is still network communication going on?

[ctwx]

So, you know what that is?

No. The first seems to be a notice by the developers. It happends before I click on "connect".

The "Sad Panda" happended I think because I clicked on "abort" first.

 

Did you check what it is?

No, because I don't think that it is the problem.

 

Did you fiddle with your systems audio devices or drivers?

No. I had the same problem with Slackware. Sound works fine on my Netbook. It's just mumble that doesn't work.

 

PulseAudio: Forcibly disconnected from PulseAudio

So, this is probably a result of the above and the reason for your issue.

Mumble seems to get into a state of hung-up / waiting for device which does not answer anymore or sth.

Seems to me like a timeout. I think the problem is, that the server(s) doesn't send the channel list back.

 

You can still use the client interface normally when connected like that?

Yes.

 

Did you check if there is still network communication going on?

I checked with Wireshark. Look here: http://imageshack.us/photo/my-images/51/20110824mumblewireshark.png/

The dark is happening when it's "connected" although I'm not.

Thanks

[ctwx]

I tested something: I installed VirtualBox and created a Virtual Machine with Xubuntu and I installed Mumble. In this VM Mumble worked without any problems....

[kissaki]

The image you posted shows (TCP Retransmission) that you sent a TCP packet for connecting but did not receive the expected answer from the server telling you he received the packet.

Does it disconnect / time out somewhen?

Or will it stay in the semi-connected state where it only shows the root channel?

[ctwx]

Does it disconnect / time out somewhen?

It disconnects after a minute or two.

Thanks for you answer.

[kissaki]

Try without router,

check your routers settings and/or try through another internet connection.

And check your firewall, if you have one running. Try disabling it.

[ctwx]

I cannot try without router. But I doubt it's the fault of the router. On my PC in the same network, I have the same package installed without any problems. I tried to deactivate the openSUSE firewall without any success.