mumble on Ubuntu 7.10

Help
Paul Hoell
2007-11-04
2012-10-30
  • Paul Hoell

    Paul Hoell - 2007-11-04

    Hello my heros of voicecom. ;)
    I love you software greatly, but at the moment, I'm not able to run the i386 deb from your page on Ubuntu 7.10. Version 1.0 worked great for me, but 1.1.0 doesn't anymore.
    The first issue is, the program seems to expect libssl.so and libcrypto.so, but in 7.10 they are called lib*.so.0.8.9 for reasons I just don't know. 2 symlinks solved this one.
    When mumble starts, everything is fine, but after 1-2 mins alsa output is disabled and not one sound is produced. This happens everytime now, i can't even finish the setupguide. It has nothing to do with my alsa, because music and games work great.
    I attach the terminaloutput i get while running mumble. The Xlib error occurs everytime i interact with mumble in any way.
    I hope you can help me, as I'd love to use your software.
    Thanks for your time.
    Paul

    ----------------Terminal-Output---------------------

    $ mumble
    Locale is de_AT
    OpenSSL Support: 1
    Overlay: Attempt for pixelsize 60 gave actual sizes 64.218750 -51.593750
    Overlay: Attempt for pixelsize 59 gave actual sizes 63.156250 -50.734375
    Overlay: Attempt for pixelsize 58 gave actual sizes 62.078125 -49.875000
    Overlay: Attempt for pixelsize 57 gave actual sizes 61.015625 -49.015625
    Overlay: Attempt for pixelsize 56 gave actual sizes 59.937500 -48.156250
    Overlay: Attempt for pixelsize 55 gave actual sizes 58.875000 -47.296875
    Overlay: Attempt for pixelsize 54 gave actual sizes 57.796875 -46.437500
    GlobalShortcutX: Unable to open any input devices under /dev/input, falling back to XEVIE
    GlobalShortcutX: XEVIE 1.0
    ALSAAudioOutput: Initialized
    ALSAAudioInput: Initing audiocapture default.
    ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.default
    ALSAAudioInput: Actual buffer 1280 samples [320(320) per period]
    Xlib: sequence lost (0x10000 > 0xa) in reply type 0x4!
    Xlib: sequence lost (0x10000 > 0xb) in reply type 0x5!
    Xlib: sequence lost (0x10000 > 0xc) in reply type 0x4!
    Xlib: sequence lost (0x10000 > 0xd) in reply type 0x5!
    Xlib: sequence lost (0x10000 > 0xe) in reply type 0x4!
    Xlib: sequence lost (0x10000 > 0xf) in reply type 0x5!
    Xlib: sequence lost (0x10000 > 0x2d0) in reply type 0x4!
    Xlib: sequence lost (0x10000 > 0x2d1) in reply type 0x5!
    Xlib: sequence lost (0x10000 > 0x2d4) in reply type 0x4!
    Xlib: sequence lost (0x10000 > 0x2d5) in reply type 0x5!
    Xlib: sequence lost (0x10000 > 0x31c) in reply type 0x4!
    Xlib: sequence lost (0x10000 > 0x31d) in reply type 0x5!
    Xlib: sequence lost (0x10000 > 0x31e) in reply type 0x4!
    Xlib: sequence lost (0x10000 > 0x31f) in reply type 0x5!
    Xlib: sequence lost (0x10000 > 0x320) in reply type 0x4!

     
    • Paul Hoell

      Paul Hoell - 2007-11-09

      Hello,
      over time I tested every possible combination i could find... With default in-/output, every other entry, with/without wizard, etc...
      Nothing changed a bit. I'm using 1.0.0 now, which gave the error once as well, but generally works great.
      I thought about compiling too, but I didn't want to install all the QT packages just for a testrun.
      I think I'll stick to 1.0.0 until there is a new version to try. Thanks for your time.

       
    • Thorvald Natvig

      Thorvald Natvig - 2007-11-04

      The SSL problem is a conflict between Qt and openssl on Ubuntu. People higher up the food chain there are looking at it, so I'm hopefull it will be resolved :)

      The Xlib: sequence lost problems are from Xevie. The same errors appear in the Xevie test program, so I'm fairly certain that's not my bug ;)

      The ALSA thing... You're the second person to report this. Does it happen if you're NOT going through the audio wizard, just idly sitting in the channel? Which sound card(s) are in your system, and which devices did you choose in Mumble?

       
    • Paul Hoell

      Paul Hoell - 2007-11-05

      Thanks for your concern.
      I deactivated xevie, for I don't need it anyways, so the errorspamming stopped.
      The Alsaerror, pops up first thing after i start mumble. It comes at the same time as the serverbrowser, even without having started anything yet.
      lspci says: Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) - is that enough?
      I tried every outputdevice, and i get the same error all the time.
      As i played around with the Alsadevice right now, i switched from and to the standard alsa device and the loopback just works suddenly.
      Restarting mumble brings up the same error again. Switching around, but changing nothing works again...
      I started the wizard then, which crashes everytime i try to select the timing (step 2). I then have to restart the program.
      I also get this error "warning: did you forget to call jitter_buffer_tick() by any chance?" quite often over the time.
      I hope it makes any sense.

      -------------------------Output-------------------------
      $ mumble
      Locale is de_AT
      OpenSSL Support: 1
      Overlay: Attempt for pixelsize 60 gave actual sizes 64.218750 -51.593750
      Overlay: Attempt for pixelsize 59 gave actual sizes 63.156250 -50.734375
      Overlay: Attempt for pixelsize 58 gave actual sizes 62.078125 -49.875000
      Overlay: Attempt for pixelsize 57 gave actual sizes 61.015625 -49.015625
      Overlay: Attempt for pixelsize 56 gave actual sizes 59.937500 -48.156250
      Overlay: Attempt for pixelsize 55 gave actual sizes 58.875000 -47.296875
      Overlay: Attempt for pixelsize 54 gave actual sizes 57.796875 -46.437500
      GlobalShortcutX: Unable to open any input devices under /dev/input, falling back to XEVIE
      Xlib: extension "XEVIE" missing on display ":0.0".
      GlobalShortcutX: XEVIE extension not found. Enable it in xorg.conf
      ALSAAudioOutput: Initialized
      ALSAAudioInput: Initing audiocapture default.
      ALSA lib pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.default
      ALSAAudioInput: Actual buffer 1280 samples [320(320) per period]
      ALSAAudioOutput: Destroyed
      Overlay: Attempt for pixelsize 60 gave actual sizes 64.218750 -51.593750
      Overlay: Attempt for pixelsize 59 gave actual sizes 63.156250 -50.734375
      Overlay: Attempt for pixelsize 58 gave actual sizes 62.078125 -49.875000
      Overlay: Attempt for pixelsize 57 gave actual sizes 61.015625 -49.015625
      Overlay: Attempt for pixelsize 56 gave actual sizes 59.937500 -48.156250
      Overlay: Attempt for pixelsize 55 gave actual sizes 58.875000 -47.296875
      Overlay: Attempt for pixelsize 54 gave actual sizes 57.796875 -46.437500
      ALSAAudioOutput: Initialized
      ALSAAudioInput: Initing audiocapture plug:"dsnoop:CARD=0".
      ALSAAudioInput: Actual buffer 1365 samples [341(320) per period]
      warning: The VAD has been replaced by a hack pending a complete rewrite
      ALSAAudioInput: Releasing ALSA Mic.
      ALSAAudioOutput: Destroyed
      Overlay: Attempt for pixelsize 60 gave actual sizes 64.218750 -51.593750
      Overlay: Attempt for pixelsize 59 gave actual sizes 63.156250 -50.734375
      Overlay: Attempt for pixelsize 58 gave actual sizes 62.078125 -49.875000
      Overlay: Attempt for pixelsize 57 gave actual sizes 61.015625 -49.015625
      Overlay: Attempt for pixelsize 56 gave actual sizes 59.937500 -48.156250
      Overlay: Attempt for pixelsize 55 gave actual sizes 58.875000 -47.296875
      Overlay: Attempt for pixelsize 54 gave actual sizes 57.796875 -46.437500
      ALSAAudioOutput: Initialized
      ALSAAudioInput: Initing audiocapture plug:"dsnoop:CARD=0".
      ALSAAudioInput: Actual buffer 1365 samples [341(320) per period]
      warning: The VAD has been replaced by a hack pending a complete rewrite
      ALSAAudioInput: Releasing ALSA Mic.
      ALSAAudioOutput: Destroyed
      Overlay: Attempt for pixelsize 60 gave actual sizes 64.218750 -51.593750
      Overlay: Attempt for pixelsize 59 gave actual sizes 63.156250 -50.734375
      Overlay: Attempt for pixelsize 58 gave actual sizes 62.078125 -49.875000
      Overlay: Attempt for pixelsize 57 gave actual sizes 61.015625 -49.015625
      Overlay: Attempt for pixelsize 56 gave actual sizes 59.937500 -48.156250
      Overlay: Attempt for pixelsize 55 gave actual sizes 58.875000 -47.296875
      Overlay: Attempt for pixelsize 54 gave actual sizes 57.796875 -46.437500
      ALSAAudioOutput: Initialized
      ALSAAudioInput: Initing audiocapture default.
      ALSAAudioInput: Actual buffer 1365 samples [341(320) per period]
      warning: The VAD has been replaced by a hack pending a complete rewrite
      ALSAAudioInput: Releasing ALSA Mic.
      ALSAAudioOutput: Destroyed
      Overlay: Attempt for pixelsize 60 gave actual sizes 64.218750 -51.593750
      Overlay: Attempt for pixelsize 59 gave actual sizes 63.156250 -50.734375
      Overlay: Attempt for pixelsize 58 gave actual sizes 62.078125 -49.875000
      Overlay: Attempt for pixelsize 57 gave actual sizes 61.015625 -49.015625
      Overlay: Attempt for pixelsize 56 gave actual sizes 59.937500 -48.156250
      Overlay: Attempt for pixelsize 55 gave actual sizes 58.875000 -47.296875
      Overlay: Attempt for pixelsize 54 gave actual sizes 57.796875 -46.437500
      ALSAAudioOutput: Initialized
      ALSAAudioInput: Initing audiocapture default.
      ALSAAudioInput: Actual buffer 1365 samples [341(320) per period]
      warning: The VAD has been replaced by a hack pending a complete rewrite
      warning: did you forget to call jitter_buffer_tick() by any chance?
      warning: did you forget to call jitter_buffer_tick() by any chance?
      warning: did you forget to call jitter_buffer_tick() by any chance?
      ALSAAudioInput: Releasing ALSA Mic.
      ALSAAudioOutput: Destroyed
      Overlay: Attempt for pixelsize 60 gave actual sizes 64.218750 -51.593750
      Overlay: Attempt for pixelsize 59 gave actual sizes 63.156250 -50.734375
      Overlay: Attempt for pixelsize 58 gave actual sizes 62.078125 -49.875000
      Overlay: Attempt for pixelsize 57 gave actual sizes 61.015625 -49.015625
      Overlay: Attempt for pixelsize 56 gave actual sizes 59.937500 -48.156250
      Overlay: Attempt for pixelsize 55 gave actual sizes 58.875000 -47.296875
      Overlay: Attempt for pixelsize 54 gave actual sizes 57.796875 -46.437500
      ALSAAudioOutput: Initialized
      ALSAAudioInput: Initing audiocapture default.
      ALSAAudioInput: Actual buffer 1365 samples [341(320) per period]
      warning: The VAD has been replaced by a hack pending a complete rewrite
      warning: did you forget to call jitter_buffer_tick() by any chance?
      warning: did you forget to call jitter_buffer_tick() by any chance?
      ALSAAudioOutput: Destroyed
      ALSAAudioInput: Releasing ALSA Mic.

       
    • Andrew Corrigan

      Andrew Corrigan - 2007-11-08

      What are your Input and Output set to in Configure/Settings/ALSA? If they are set to something else, try setting them both to the [default] one. Close Mumble and restart and don't use the Audio Wizard.

      I'm using Ubuntu 7.10 as well, but the 64bit version. So I can't use the default i386 package and instead I'm using a compile of SVN from Nov. 7th (which I had to do a qmake main.pro, make, and make release....I'm not sure if that's the proper way but doing just the first two steps wasn't leaving me with anything in the Release directory with either SVN or the 1.1.0 source)

      I'm finding the Audio Wizard changes my ALSA settings. I keep writing my findings up and then thinking I've verified what's happening and then the behaviour changes, so I'm having a hard time pin pointing what's happening. But my problem areas seem to be with the Audio Wizard setting the ALSA device to dsnoop for loopback and the loopback test in the Configure/Settings settings. Both of which seem to change the input to dsnoop. If those two things change the ALSA devices, or if I change them manually, I seem to start getting the ALSA error message (Opening Chosen ALSA Output failed: Device or resource busy) quite a bit. I assume that's the error message being given to the other person. Once I receive this error message, I'm not sure that I have sound output in Mumble and it seems to interfere with the audio output of other programs, such as Rhythmbox until I open and close them again, but this is a symptom that seems sporadic as well.

       

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks