Jean-Philippe MENGUAL: > No problem to merge, I thought it was 2 issues: one related to c!ash; > another to loss of conf data.
This sounds like two different consequences from the same cause -- crashing when running Mumble along with Orca and qt-at-spi. > I'm not sure it is to be handled the same > way. Typically, you may be able to reproduce this one with killall > mumble or killall mumble -9. Or, as you say, poweroff the computer > leaving mumble on. If Mumble is started with an empty configuration but never closed before doing a killall -9 then it will loose many (but not all) of the client settings. I think this likely explains why Sebastian Humenda was experiencing this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793340#37 Once Mumble is configured and closed once normally a killall -9 doesn't loose settings -- or at least that's what I see with my testing so far. (I tried about a dozen or so times.) > For the crash, when you say you don't reproduce, have you tried with > Orca and qt-at-spi installed? I said that I had in the previous bug, and at the time I had tested this both on Sid and with a Testing VM. (I did not re-test right now.) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793340#32 > Is master/daily release the same than testing one? They are. gnome-orca 3.20.2, qt-at-spi 0.4.0-3. Testing: https://packages.debian.org/testing/gnome/gnome-orca https://packages.debian.org/testing/misc/qt-at-spi Unstable: https://packages.debian.org/unstable/gnome/gnome-orca https://packages.debian.org/unstable/misc/qt-at-spi In order to be able to work on this bug I'd need information about what's causing it, we have no information on that right now, and I can't reproduce it. -- Chris -- Chris Knadle chris.kna...@coredump.us
