Hi @impeth ---- Thank you for touching base with me and providing the requested logs, very appreciated! Confirming that they have been downloaded and attached to your ticket for review.
Continuing forward, could you please try running the test proposed here and sharing your results with me. Being as this crash is happening when you are using “Roon remote” on the same device as “RoonServer” and the server function itself is not crashing I am eager to hear what the experience is like with a fresh instance of Roon remote installed (i.e “Roon” folder - > “Roon_Old” folder).
Hi @impeth ----- Thank you for the update and giving the proposed test a shot. The continued feedback is very appreciated! Confirming that the latest set of logs has been received as well.
Continuing forward, our tech team has asked if you would kindly perform/provide the following:
Launch the “terminal” on the MacMini currently hosting your Roon core.
Go to the “~” folder if you are not in that folder by default.
Run the following command and hit “enter”:
ls -la
Copy the print out from the terminal window after the above command has been ran and share it with us for evaluation.
Additionally, the tech team has also asked how you were able to add music to Roon the storage tab is causing crashing? Did you just enabled the enable the “default music folder” during the setup procedure?
In the beginning I was able to point to my local NAS where music was stored.
After several updates probably this changed. I changed path into my NAS & I deleted my old path.
But at a the same time I was unable to put the new folder (or any other folder) because every time it crashes!
Now I am listening only to TIDAL albums,
I attach the requested info.
Thank you for the follow up @impeth, very appreciated! I have passed the above over to our technicians for review. As soon as they give me their feedback I will reach out immediately.
Hi @impeth ---- Our techs have reached out to me and have asked if you could please provide a recording of the this crash occurring on your system so they can see the issue happening in real time.
Than you for the upload @impeth, confirming that it has been received and is with the team for review. As soon as the provide me an update I will reach back out asap.
Hi @impeth —— Thank you again for your patience here, it has been appreciated not only by myself but also by our technical staff who have been evaluating this issue you are experiencing.
Our team believes that they have identified the file that is causing the application to crash based on the provided terminal print out:
rw-r–r- - 1 yiannis staff 803 Jan 29 2017
In light of this discovery the team has asked if you could please perform the following:
Launch the “terminal”.
Go to the “~” folder if you are not in that folder by default.
In the “~” folder run the following command:
ls -il
Find the file in the output (i.e rw-r–r- - 1 yiannis staff 803 Jan 29 2017) and copy the file’s “inode”.
Note: The “inode” is a file’s number. Here is an example of an “inode” from my output which is the first number which is written in bold: 4322407819 - rw-r-r- 1 eric staff 360000 May 23 22:10 lambda_for.dat
Once the “inode” has been located and copied use the following command:
sudo find . -inum inode -exec rm -i {} \ ;
Note: in the command line above there should be no “space” between the " \ " and the " ; " . The community site is removing the backslash when I have no spaces.
Congratulations! Your team performed an IT microsurgery and worked!!!
Actually I did not have the patience to do the whole procedure, it was about a useless file, I removed it & everything worked fine again!!!