Closed matkoniecz closed 4 years ago
This is expected : this was a temporary mechanism to log specific events, not to give a whole lot of verbose info that is also printed to the terminal.
In general I would be happy to see more debug info about what is going wrong. For now I think that I did all obvious things like
this was a temporary mechanism to log specific events
What is the current mechanism to get more info what is going wrong?
The Open source Nvidia drivers are known to cause some issues under Linux. I guess this is what's going on.
Note that proprietary Nvidia drivers also are likely to cause issues, in my case system failed to boot (removal of nvidia driver package using recovery mode fixed the issue).
I would recommend checking your backups before doing this.
Note: in Lubuntu going to Start Menu -> Preferences -> Software Sources -> Additional Drivers has option to easily change to a preselected (hopefully fitting) driver.
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1553328/comments/22 claims
The nouveau isn't threadsafe and the Qt renderer uses threaded GL by default.
what would mean (if still up to date) that maybe changing some qt setting may help
Typical session:
debug file that I specified is created but empty and is not containing even what I see in stdout.
Lubuntu 19.10 - Mnemosyne build from source is crashing/freezing all the time (but it is not what I reporting as I am unable to track the root cause for now).
I upgraded OS, sadly for Ubuntu 19.10 Mnemosyne version in packages is completely broken (at least for me) (also problem but not what I report as AFAIK packages are maintained by other people).
Sadly, I no longer have a nice crashes during compilations (like #73) but instead Mnemosyne is freezing/crashing - sometimes on the startup, sometimes on answering, on maximalising the window.