Re: Bug#793340: mumble: Another hard consequence
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
>
>>> 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.
It's exactly what I experience here, too. The problem is that the
issue is random.
Regards,
> That is a very vague description, but I wanted to let you know
> that Jean-Philippe's observation can be (vaguely) confirmed.
>
> Cheers Sebastian
>
- --
Jean-Philippe MENGUAL
HYPRA, progressons ensemble
Tél.: 01 84 73 06 61
Mail: contact@hypra.fr
Site Web: http://hypra.fr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWuQnzAAoJEGSAR7LXI4kcUqIP/jCAK4evtujhIkg0zYorhbLO
sIffdkYBJSyrlVRiHTqsWLBkLQ2vkBQstSGMNWOSz4ijdeiD/3ke5fRUhNroz1EQ
OmRk3mv9QlB8wZ6m26AWbBm99CUHbv4xsb9c2YCVs7M3hyx5gbEHlzLbdwxdeWXT
gp0b7TD1CM3Ot0nafDyIDhl+BQY5mo0P5To2+DixU/OmeLt3E6SZSJv3cAhrYxT2
EbTy6eC6wauOSPY8IiYxDCuBI13WBlz30ORaoyRZMY51mwYKpVfX9Eim0TJCwydL
hflmIz7yTO3q6sJ7RXDeZrIrWY9SibxGpvr0EasAythaWFXuh5YU67BMsHoaw5z3
uXIQEQMKy2iGp5maIMyY8Rwilo0gKmYUy8U96vl7PGBO1ZN5C8dA1kcJfxmZUJ8K
H7FqgTFzdqzf0RBC0u1ilWLPkYyeWu+Jwsx9rAVrw67pXpVELjTuYGgM15svPnpq
iulFsOyWvWv1HBrjDQ3Pe+ct+Iu2qWcX1hUH4bcObi6t6XR4Wm3vpvBm3zKZElwv
9/g5S/8GgOcQmNFIX8rO3Za9F7CVmvBuIqObZobu2gErJODaaA2eyEwR/2yPLfq3
rxNifvNgsmOBaCsidzbls0uvVXJd/1avybj3JmAzXn3xUS1ZepGi8kfqfjNVcbS1
Nf/iqwpgaHdAocvWr3nM
=Db+4
-----END PGP SIGNATURE-----
Reply to: