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

Re: Bug#793340: mumble: Another hard consequence



Hi,

Chris Knadle schrieb am 08.02.2016, 18:24 +0000:
[...]
>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?
AFAIK that's a dbus path, should be all right.

>> 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.
It won't be much help, but I've experienced a very similar issue, also with
qt-atspi / orca. I usually terminate Mumble using "killall mumble" and I lost my
audio settings twice. However, at some point the settings were saved.
That is a very vague description, but I wanted to let you know that
Jean-Philippe's observation can be (vaguely) confirmed.

Cheers
Sebastian

Attachment: signature.asc
Description: PGP signature


Reply to: