+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: [SOLVED] local UI gone after changing host/player name (/showthread.php?tid=6162)
Pages:
1
2
RE: local UI gone after changing host/player name - Tim Curtis - 01-18-2024
(01-18-2024, 03:55 AM)TheOldPresbyope Wrote: I found a nine-year old reference to the same problem on a Ubuntu forum!
If you examine the ~/.config/chromium directory you'll see a set of "Singleton" links
Code:lrwxrwxrwx 1 pi pi 20 Jan 17 21:57 SingletonCookie -> 18100444628333534977
lrwxrwxrwx 1 pi pi 11 Jan 17 21:57 SingletonLock -> moode-19804
lrwxrwxrwx 1 pi pi 50 Jan 17 21:57 SingletonSocket -> /tmp/.org.chromium.Chromium.IYiZFF/SingletonSocket
Turn off the local display using the WebUI then delete these links. You can do this by executing the following three command from an ssh session (I did it in three steps to minimize risk if you mistype the rm command.)
Code:cd ~/.config/chromium
rm -rf Singleton*
cd
Then reboot moOde for luck and reenable the local display from the WebUI.
This worked for me. Hope it works for you.
I guess the easy way to avoid this problem is to turn off the local display before changing host name.
Regards,
Kent
Wow, that's pretty obscure. I'll add to the TODO list for upcoming 8.3.8
RE: local UI gone after changing host/player name - Wallyboy - 01-18-2024
(01-18-2024, 11:21 AM)Tim Curtis Wrote:(01-18-2024, 03:55 AM)TheOldPresbyope Wrote: I found a nine-year old reference to the same problem on a Ubuntu forum!
If you examine the ~/.config/chromium directory you'll see a set of "Singleton" links
Code:lrwxrwxrwx 1 pi pi 20 Jan 17 21:57 SingletonCookie -> 18100444628333534977
lrwxrwxrwx 1 pi pi 11 Jan 17 21:57 SingletonLock -> moode-19804
lrwxrwxrwx 1 pi pi 50 Jan 17 21:57 SingletonSocket -> /tmp/.org.chromium.Chromium.IYiZFF/SingletonSocket
Turn off the local display using the WebUI then delete these links. You can do this by executing the following three command from an ssh session (I did it in three steps to minimize risk if you mistype the rm command.)
Code:cd ~/.config/chromium
rm -rf Singleton*
cd
Then reboot moOde for luck and reenable the local display from the WebUI.
This worked for me. Hope it works for you.
I guess the easy way to avoid this problem is to turn off the local display before changing host name.
Regards,
Kent
Wow, that's pretty obscure. I'll add to the TODO list for upcoming 8.3.8
Thank You guys for all of the help. That solved my problem!