You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -312,6 +312,14 @@ Modules in beta are still included in releases for the most part but not enabled
312
312
313
313
First, please make sure you're running the latest automated build. If your issue is linked to a bug it is likely that is has already been fixed in later releases
314
314
315
+
## SDR++ crashes then it won't start again no matter what
316
+
317
+
This is a bug in 1.0.0 that was fixed in 1.0.1
318
+
319
+
In some cases, if a crash happened while the config was being saved, the config file woul be corrupted and SDR++ would refuse to start because of it.
320
+
321
+
This has now been fixed. If a config file is corrupted it'll just reset it to its default state.
322
+
315
323
## "hash collision" error when starting
316
324
317
325
You likely installed the `soapysdr-module-all` package on Ubuntu/Debian. If not it's still a SoapySDR bug caused by multiple soapy modules coming in conflict. Uninstall anything related to SoapySDR then install soapysdr itself and only the soapy modules you actually need.
0 commit comments