Bug#793340: mumble: Another hard consequence

2016-02-08 Thread Jean-Philippe MENGUAL
-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.

Bug#793340: mumble: Another hard consequence

2016-02-08 Thread Jean-Philippe MENGUAL
Hi, Here's now a bigger debug log: 1. mumble-dbg is installed 2. As you'll see I try: a) Running - run, connect, it crashes at connection time b) Settings: - I try what I described, indeed I no longer reproduce. - I try then: > 1. Run mumble > 2. Go to option menu (alt-o) > 3. C

Bug#793340: mumble: Another hard consequence

2016-02-08 Thread Sebastian Humenda
Hi, Chris Knadle schrieb am 08.02.2016, 18:24 +: [...] >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" > >A

Bug#793340: mumble: Another hard consequence

2016-02-08 Thread Chris Knadle
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 readi

Bug#793340: mumble: Another hard consequence

2016-02-03 Thread 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? Could debug symbols help? 2. Another big problem when mumble isn't closed properly (segfault like here, kill, etc): it looses it configuration (pu