Re: [mnemosyne-proj-users] Re: Quitting unexpectedly

2018-02-14 Thread Devin Howard
Hi Mike Yes, please send me your Mnemosyne folder and I'll try it out and see if I can learn anything else. So far I haven't had much luck finding the issue so maybe this will help On Wed, Feb 14, 2018, 7:14 AM , wrote: > I came across this thread because my Mnemosyne was

[mnemosyne-proj-users] Re: Quitting unexpectedly

2018-02-14 Thread m . kefeder
I came across this thread because my Mnemosyne was crashing (segfault) on editing cards. I am on macOS 10.13.3, using 2.6 it segfaults when I try to edit an entry. (Just using it to memorize and score works fine, funnily enough adding new cards works too.) So I tested with 2.6-qt5.10 version,

[mnemosyne-proj-users] Re: Quitting unexpectedly

2018-02-12 Thread Dan Schmidt
Some more data: this morning I was suddenly unable to run Mnemosyne at all (macOS 10.13.3, upgraded from Sierra to High Sierra a few weeks ago but had been running every day since). I would get a "Trace/BPT trap: 5" error that appeared to be happening inside Qt from the stack trace. I had a few

[mnemosyne-proj-users] Re: Quitting unexpectedly

2018-02-05 Thread Devin Howard
Hi Emily I'm not really sure what the problem is, but I tried making a special build of Mnemosyne 2.6 just for macOS that uses a newer version of some internal software ("qt 5.10") You can find Mnemosyne-2.6-qt5.10.dmg at

[mnemosyne-proj-users] Re: Quitting unexpectedly

2018-01-22 Thread Devin Howard
Hi, I tried this out on my machine and I wasn't able to see an error. Could you directly email me your database files so I can try with your set of cards? It should be everything under /Users//Library/Mnemosyne If you send me that, perhaps I'll be able to find out what the issue is. As Peter