-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new 0.3 force close when opening in windows 10 #47
Comments
I cannot reproduce this even on a newly installed Windows 10 (virtual machine). You can try clearing the database of LRCGET to see if it works: Paste the following path to File Explorer:
Then delete all the files inside (db.sqlite3, db.sqlite3-shm, db.sqlite3-wal). |
Mmmh, I just did as you said, but it is still crashing See the video here: abd here continuing by deleting 0.3 and reinstalling 0.2.1 |
Could you try to run this in the PowerShell (Windows button right click > Windows PowerShell)?
(assuming you installed LRCGET at It will allow you to see more verbose logs, so more information to guess what went wrong. It should look like the picture below: You can check the installed location by right clicking to LRCGET shortcut > Properties > check the Target field: |
Here is the default location for me: Here the results:
|
and it still doesn't work... |
I expected some kind of panicked message in stdout/stderr but there is none. I still have no idea what went wrong here. I will make a custom built version for you to debug this, but it'll take some time, maybe 1-2 more days. |
Could it be because the installation location is different from yours? |
I don't think so. There are two kinds of setup file for Windows:
One will install it in the |
I just tried the .msi and had the same result I also deleted the .exe file, redownload it, reinstall it but no luck there too What is bothering me is that each time I reinstall the 0.2.1 version it works |
@tranxuanthang forget it, it works! I don't know why it didn't before but now it is working as expected. I'll test it against my music librairie (a few TB) a let you know how it is. I'm sorry for the inconvenience, great work ! |
Although I'm curious about what actually went wrong, I'm glad it works for you now! |
When I tried yesterday I was accessing my PC remotely from my phone via Anydesk and I had the force closes. Now I'm on my phone again and just tried with Anydesk and it force closes again. Maybe it can help find what is the issue? |
Hello, I could reproduce the same issue on my windows server (2019, based on windows 10): When connecting remotely to it (using RDP via MRemoteNG), the default settings is to disable the sound. No audio device was available in Windows. As soon as I activated the audio playback (Bring to this computer), the programe started working. Thanks for your help |
I can confirm that it has something to do with the audio device. Enabling audio playback fixed it for me as well. |
I'm still struggling, with this, how would you do it with the Anydsek software? |
@tranxuanthang any fix for this coming soon? |
From what their knowledge base says, you can enable audio through any desk by going to Settings > Audio. Beyond that, I have no clue, I'm not using Anydesk. |
Unabeling or disabling audio doesn't work for me... |
Seems I share a similar predicament. This app crashes on startup on my Win10 machine. I have tried the 2 installers, different versions and install locations, updating & restarting PC. No version of LRCGET appears to work on my machine and the PowerShell command returns nothing. |
@guitarallstar Did you run any script to debloat Windows or remove Microsoft Edge? Please check this issue #45 to see if it works for you. |
Yes sir I must have debloated. I apologize I did not see this other ticket with a solution, but that did indeed fix it after installing Edge and restarting PC. Thanks! |
I completly uninstall and remove data from the previous version and restarted my pc
I use LRCGET_0.3.0_x64-setup.exe
It is installing but it doesn't launch properly, it forced close
Edit: i re installed 0.2.1 and it is running normaly so thzre should be a problem with 0.3....
The text was updated successfully, but these errors were encountered: