[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#793340: mumble: Crash with a screen reader



Hi,

ok I Cc debian-kde too, as it's related to Qt.

Surprised you can't reproduce. Have you tried with MATE? Or another DE?

Other problems you mention are true, but I don't mention them as it's more general accessibility problems. They're boring, but not critical as they don't make mumble crash.

Well... maybe it's a related-hardware problem (memory leak or something like this).

Regards,

Le 23/07/2015 21:45, Chris Knadle a écrit :
tag 793340 unreproducible
thanks

On 07/22/2015 07:52 PM, Jean-Philippe MENGU‘AL wrote:
Package: mumble
Version: 1.2.8-2
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

    * What led up to the situation?

Using MATE, Orca, qt-at-spi.

    * What exactly did you do (or not do) that was effective (or
      ineffective)?

1. Run mumble on a server:
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've tried running orca + mumble under MATE on both Sid amd64 (native)
and Jessie amd64 (in a VM) and am not able to reproduce the Segfault.

There are additional sections of configuration once the "Advanced"
configuration option is set, such as choosing to use "Text-to-speech"
outputs under the Messages configuration area.  Unfortunately this part
of the configuration dialog doesn't seem to have been programmed with
keyboard shortcuts for these options.  Orca says "Advanced checkbox not
checked" when tabbing on the Advanced checkbox, and "Messages" is 5
items below "Audio Input".

    * What was the outcome of this action?

Segfault

    * What outcome did you expect instead?

Should be back to the main window.

*** End of the template - remove these template lines ***

I attach debug file.
I've had a look at it, and based on the many lines of:

    AtSpiAdaptor::relationSet currently has a problem with child ids.

this looks like there's an issue with Mumble along with QSpiAccessible
on your system, but I don't see anything clear in the debug output as to
why.

I'm CCing the Debian Accessibility Team which is who is listed as the
maintainer of qt-at-spi in the hope that they might have more insight
into this issue.

If needed, I can provide more. Tell me instructions to give
you relevant info from gdb, valgrind, including packages to have debug
symbols.
The mumble-dbg package contains the debug symbols for both mumble and
mumble-server.  Concerning gdb, there's some useful information about
various commands available at:


https://www.debian.org/doc/manuals/debian-reference/ch12.en.html#_basic_gdb_execution

At present I'm not familiar with valgrind.

    -- Chris



--
Jean-Philippe MENGUAL

HYPRA, progressons ensemble

Tél.: 01 84 73 06 61

Mail: contact@hypra.fr

Site Web: http://hypra.fr


Reply to: