Your message dated Mon, 24 Dec 2018 08:23:39 +0000 with message-id <[email protected]> and subject line Re: Bug#823737: anki: Sudden "Segmentation fault" crashes from time to time has caused the Debian Bug report #823737, regarding anki: Sudden "Segmentation fault" crashes from time to time to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 823737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823737 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: anki Version: 2.0.32 Severity: Important * What led up to the situation? I have no idea. * What exactly did you do (or not do) that was effective (or ineffective)? I started Anki from a terminal. It produced following output: http://freetexthost.com/p50w1wgpya I ran "apt upgrade" in hope that it will fix it, but it didn't. Instead it made Anki way less talkative, now it says just "Segmentation fault" after a crash. * What was the outcome of this action? Anki forgets some recent changes of its database before crash. * What outcome did you expect instead? I expect Anki to work all day long without a single crash and forgetting any changes of its database that I made. Information about my system. Linux kernel: Linux debian 4.5.0-2-686-pae #1 SMP Debian 4.5.2-1 (2016-04-28) i686 GNU/Linux Qt 4.8.7 PyQt 4.11.4 Installed addons for Anki: Editor Autocomplete Limit searches to current deck Stats: Expected number of cards Content of apt.conf: APT::Install-Suggests "0"; APT::Install-Recommends "0"; APT::Install-Recommends "false"; APT::Install-Suggests "false"; APT::AutoRemove::RecommendsImportant "false"; APT::AutoRemove::RecommendsImportant "0"; APT::AutoRemove::SuggestsImportant "false"; APT::AutoRemove::SuggestsImportant "0"; All installed packages: https://drive.google.com/file/d/0B21fx2NRbanxWFFxWjQwX2NTTFk/view?usp=sharing Output of reportbug: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.5.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages anki depends on: ii libjs-jquery 1.12.3-1 ii libjs-jquery-flot 0.8.3+dfsg-1 ii libjs-jquery-ui 1.10.1+dfsg-1 ii python 2.7.11-1 ii python-beautifulsoup 3.2.1-1 ii python-httplib2 0.9.1+dfsg-1 ii python-pyaudio 0.2.8-1+b3 ii python-qt4 4.11.4+dfsg-1+b3 ii python-simplejson 3.8.2-2 ii python-sqlalchemy 1.0.12+ds1-1 pn python:any <none> Versions of packages anki recommends: ii python-matplotlib 1.5.1-1+b2 Versions of packages anki suggests: pn dvipng <none> ii lame 3.99.5+repack1-9+b1 pn mplayer2 <none>
--- End Message ---
--- Begin Message ---Version: 2.1.7+dfsg-1 On Sun, May 08, 2016 at 03:48:24PM +0600, Vazgen Davidyatns wrote: > Package: anki > Version: 2.0.32 > Severity: Important > * What led up to the situation? > I have no idea. > * What exactly did you do (or not do) that was effective (or > ineffective)? > I started Anki from a terminal. It produced following output: > http://freetexthost.com/p50w1wgpya > I ran "apt upgrade" in hope that it will fix it, but it didn't. Instead it > made > Anki way less talkative, now it says just "Segmentation fault" after a > crash. > * What was the outcome of this action? > Anki forgets some recent changes of its database before crash. > * What outcome did you expect instead? > I expect Anki to work all day long without a single crash and forgetting > any > changes of its database that I made. Dear Vazgen, At long last, there is a new verion of Anki now in testing (2.1.7+dfsg-1). It appears that this bug has been fixed - at least, I have not been able to reproduce it, so I am closing this bug report. If you still have problems with the new version, please do let us know and reopen this report. Apologies for the long wait. Julian
--- End Message ---
