Bug#811170: mumble: Hang at startup

2016-01-18 Thread Chris Knadle
Elia Argentieri:
> I jumped to conclusions as it turned out that Pulseaudio has nothing to
> do with this issue.
>
> The issue was caused by the package ifupdown2 which I installed some
> days ago to solve some strange dependencies and removed ifupdown.
> Purging ifupdown2, reinstalling ifupdown and rebooting solved the
> issue.
>
> Thank you very much for your time.

Okay then the issue might be Mumble hangs when the network isn't
available... there's an open bug upstream about that, though in that case
the connection was made first and then the network taken down:

   https://github.com/mumble-voip/mumble/issues/1983

I'm glad you figured out the cause in this case... I'll keep it in mind in
case this problem comes up again.

Thanks
   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us



Bug#811170: mumble: Hang at startup

2016-01-16 Thread Elia Argentieri
Package: mumble
Version: 1.2.12-1
Severity: important

Dear Maintainer,

when I start mumble it takes a very long time to show the main window or even
something in the terminal. It just hangs there for a long time like 1 or 2
minutes until it shows up and works correctly.

Since it didn't say anything useful by its own, I run it with gdb and attached
the log.

It seems thread 2 is stuck at a mutex in pulseaudio's code.
Perhaps this has to do with recent system updates?

Regards,
EA

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (800, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mumble depends on:
ii  libasound2 1.0.29-1
ii  libavahi-client3   0.6.32~rc+dfsg-1
ii  libavahi-common3   0.6.32~rc+dfsg-1
ii  libavahi-compat-libdnssd1  0.6.32~rc+dfsg-1
ii  libc6  2.21-6
ii  libg15daemon-client1   1.9.5.3-8.3
ii  libgcc11:5.3.1-5
ii  libopus0   1.1.1-1
ii  libprotobuf9v5 2.6.1-1.3
ii  libpulse0  7.1-2
ii  libqt4-dbus4:4.8.7+dfsg-5
ii  libqt4-network 4:4.8.7+dfsg-5
ii  libqt4-sql 4:4.8.7+dfsg-5
ii  libqt4-sql-sqlite  4:4.8.7+dfsg-5
ii  libqt4-svg 4:4.8.7+dfsg-5
ii  libqt4-xml 4:4.8.7+dfsg-5
ii  libqtcore4 4:4.8.7+dfsg-5
ii  libqtgui4  4:4.8.7+dfsg-5
ii  libsndfile11.0.25-10
ii  libspeechd20.8-7
ii  libspeex1  1.2~rc1.2-1
ii  libspeexdsp1   1.2~rc1.2-1
ii  libssl1.0.21.0.2e-1
ii  libstdc++6 5.3.1-5
ii  libx11-6   2:1.6.3-1
ii  libxi6 2:1.7.5-1
ii  lsb-release9.20150917

mumble recommends no packages.

Versions of packages mumble suggests:
pn  mumble-server  
pn  speech-dispatcher  

-- no debconf information
Starting program: /usr/bin/mumble 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdd7d0700 (LWP 4306)]

Program received signal SIGTSTP, Stopped (user).
0x74f9ea6d in connect () at ../sysdeps/unix/syscall-template.S:81
81  ../sysdeps/unix/syscall-template.S: File o directory non esistente.

Thread 2 (Thread 0x7fffdd7d0700 (LWP 4306)):
#0  0x7281b86d in poll () at ../sysdeps/unix/syscall-template.S:81
No locals.
#1  0x75806831 in poll (__timeout=-1, __nfds=3, __fds=0x7fffd8006ca0) 
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
No locals.
#2  poll_func (ufds=0x7fffd8006ca0, nfds=3, timeout=-1, userdata=0xd3fce0) at 
pulse/thread-mainloop.c:69
mutex = 
#3  0x757f7e51 in pa_mainloop_poll (m=m@entry=0xd40730) at 
pulse/mainloop.c:844
__func__ = "pa_mainloop_poll"
__PRETTY_FUNCTION__ = "pa_mainloop_poll"
#4  0x757f84ee in pa_mainloop_iterate (m=0xd40730, block=, retval=0x0) at pulse/mainloop.c:926
r = 0
#5  0x757f85a0 in pa_mainloop_run (m=0xd40730, retval=retval@entry=0x0) 
at pulse/mainloop.c:944
r = 
#6  0x758067c6 in thread (userdata=0xd3b430) at 
pulse/thread-mainloop.c:88
m = 0xd3b430
mask = {__val = {18446744067267100671, 18446744073709551615 }}
#7  0x70a20038 in internal_thread_func (userdata=0xd3b320) at 
pulsecore/thread-posix.c:81
t = 0xd3b320
#8  0x74f96284 in start_thread (arg=0x7fffdd7d0700) at 
pthread_create.c:333
__res = 
pd = 0x7fffdd7d0700
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140736909346560, 
-772166350341516780, 0, 140737488346831, 13896688, 140736909346560, 
772099271592923668, 772190561161990676}, mask_was_saved = 0}}, priv = {
pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 
pagesize_m1 = 
sp = 
freesize = 
__PRETTY_FUNCTION__ = "start_thread"
#9  0x7282474d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
No locals.

Thread 1 (Thread 0x77f25900 (LWP 4302)):
#0  0x74f9ea6d in connect () at ../sysdeps/unix/syscall-template.S:81
No locals.
#1  0x7728e1ef in new_g15_screen () from 
/usr/lib/libg15daemon_client.so.1
No symbol table info available.
#2  0x005c695e in G15LCDEngineUnix::G15LCDEngineUnix (this=0xd5b990) at 
G15LCDEngine_unix.cpp:43
No locals.
#3  0x005c6a0b in G15LCDEngineNew () at G15LCDEngine_unix.cpp:37
No locals.
#4  0x005789d2 in LCDDeviceManager::initialize (this=0xa9c1c0 ) 
at LCD.cpp:76
e = 
engine = 
_container_ = {c = {{p = {static shared_null = {ref = 

Bug#811170: mumble: Hang at startup

2016-01-16 Thread Chris Knadle
Greetings.

Elia Argentieri:
> Package: mumble
> Version: 1.2.12-1
> Severity: important
> 
> Dear Maintainer,
> 
> when I start mumble it takes a very long time to show the main window or even
> something in the terminal. It just hangs there for a long time like 1 or 2
> minutes until it shows up and works correctly.

Hmm.  I haven't heard this happening on Debian and I don't see a report
similar to this in the mumble bug tracker at github.  (There is one, but
it's on windows: https://github.com/mumble-voip/mumble/issues/1071)

> Since it didn't say anything useful by its own, I run it with gdb and attached
> the log.
>
> It seems thread 2 is stuck at a mutex in pulseaudio's code.
> Perhaps this has to do with recent system updates?

I had a look at the gdb output, but I don't trust that I know how to read it
-- I don't see anything obvious.  If you think the log shows being stuck at
a mutex then you probably already know more about this than I do.

Maybe it's a bug in PulseAudio... or it could possibly be an issue with
PulseAudio settings.  I do occasionally see users talk about a number of
issues related to mumble and PulseAudio in #mumble on Freenode -- I'd
suggest asking about this there.

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us