No problem to merge, I thought it was 2 issues: one related to c!ash; another to loss of conf data. 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.
For the crash, when you say you don't reproduce, have you tried with Orca and qt-at-spi installed? Is master/daily release the same than testing one? Regards, Le 10/08/2016 à 23:45, Chris Knadle a écrit : > > > Jean-Philippe MENGUAL: >> Package: mumble >> Version: 1.2.16-1 >> Severity: important >> >> Dear Maintainer, >> >> *** Reporter, please consider answering these questions, where appropriate >> *** >> >> * What led up to the situation? >> >> Well, various crashes, cf bug 793340 > > I haven't been able to reproduce #793340 and haven't had the Mumble > client crash on me. (I use the Mumble client daily.) > > This is essentially a duplicate bug of #793340 so it would have been > better to respond to #793340 if there was new information about it. It > probably makes sense to merge this bug with #793340 AFAICT. > >> Mumble crashed trying joining a server, changing settings, etc. > > Crashed trying to join a server? The only time I know where Mumble > really gets screwed up trying to connect to a server is when there are > multiple versions of OpenSSL loaded, which happens due to Qt4 not being > compiled with the new version of OpenSSL, so both load. /That/ will > lead to some very strange behavior. See #804487. > >> It also happens I close the session, letting mumble be stopped by Systemd. > > So if I understand correctly: you leave the client open and then > shutdown, and that causes mumble to crash? > >> * What exactly did you do (or not do) that was effective (or >> ineffective)? >> >> After crash, restart. It's not systematic, but very often: audio settings >> have >> disappear. I need to set them again. >> >> Besides, today, I lost my certificate! It needed to be renewed fully on >> mumble, >> and I couldn't connect to my server. > > The only time I've seen this (so far) is with #804487 during OpenSSL > transitions on Sid. I recall an OpenSSL transition was pending -- did > that occur, and Qt4 not get binNMUed yet? > >> * What was the outcome of this action? >> >> Settings should be saved. Loosing privacy is really a problem I think, beyond >> loss of audio settings (which is boring). > > I totally agree re: loosing the mumble certificate. :( At the moment > the best I can suggest is to make a copy of the certificate in > ~/Documents rather than relying solely on the automatically-made backup, > because during OpenSSL transitions there is some strange behavior: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804487#62 > > There's also more about this at bug #1876 upstream: > > https://github.com/mumble-voip/mumble/issues/1876 > > That's my best guess as to what might be going on here. > > -- Chris > -- Jean-Philippe MENGUAL HYPRA, progressons ensemble Tél.: 01 84 73 06 61 Mail: cont...@hypra.fr Site Web: http://hypra.fr
