Re: Bug#793340: mumble: Another hard consequence

[Chris Knadle <Chris.Knadle@coredump.us>]

Jean-Philippe MENGUAL:
> Package: mumble
> Version: 1.2.12-1
> Followup-For: Bug #793340
> 
> Dear Maintainer,
> 
> Hi,
> 
> 1. When you say it's not reproducible, have you installed qt-at-spi?

Yes, unreproducible with qt-at-spi installed.  In a terminal I run 'orca'
which then starts screen reading everything -- then followed the steps that
had been reported:

	1. Run mumble
	2. Go to option menu (alt-o)
	3. Choose Settings
	4. Bro9se among tabs.
	5. Press tab key until OK button, and press Enter.
	6. Optionally, do this twice.

I did this both with and without connecting to a server -- no crashes.

I believe you when you say that this is happening on your system, I'm just
not able to reproduce it myself.  :(

One thing I note in the debug output in the original bug report (after
looking at it again) are repeats of this line:

   WARNING Qt AtSpiAdaptor: Could not find accessible on path:
   "/org/a11y/atspi/accessible/140532364506704"

Assuming this is indeed a full path description, "/org" is not a typical
root level directory, but "/opt" is.  Is this possibly a misconfiguration?

> Could debug symbols help?

They might, yes -- a backtrace won't be of much use without mumble-dbg being
installed.  With mumble-dbg installed, upstream might be able to make sense
of the gdb backtrace debug output if I'm unable to.

> 2. Another big problem when mumble isn't closed properly (segfault like
> here, kill, etc): it looses it configuration (push-to-talk key, audio
> settings, etc).
> Is it known?

Hmm.  I think this is the first I've heard of that.  I've looked through the
issues reported upstream and I don't think I see this (loss of configuration
on segfault/kill/crash) reported there either.

   -- Chris

-- 
Chris Knadle
Chris.Knadle@coredump.us