Re: [SlimDevices: SqueezeCenter] QLogitechMediaServer for Qnap with QTS 4.2 or higher and x86_64/I686/X86 support !

2018-03-24 Thread QDon
Well there is a root user on my TVS-882BR where LMS was installed. I ran a test using my TVS-663 which does not have LMS installed. Guess what? A 'root' user was not created. Code: [/opt] # cat /etc/passwd admin:x:0:0:administrator:/share/homes/admin:/bin/sh

Re: [SlimDevices: SqueezeCenter] QLogitechMediaServer for Qnap with QTS 4.2 or higher and x86_64/I686/X86 support !

2018-03-24 Thread digimaster
Just checked on my Qnap ts-453a, and yes there is a root user. But it deactivated, i can not use it. I would suggested do as they ask, make a backup from you're Cache en prefs directory from the SlimServer directory. Put them some where save, like in the download share. Then remove

Re: [SlimDevices: SqueezeCenter] QLogitechMediaServer for Qnap with QTS 4.2 or higher and x86_64/I686/X86 support !

2018-03-24 Thread earthbased
digimaster wrote: > You done something in the SlimServer/ directory. > Do the chmod -R 0755 SlimServer/, and chown -R squeezeboxuser:everyone > SlimServer/ from the .qpkg/LogitechMediaServer/ directory. > Keep in mind when you in the structure off LMS ( the SlimServer/ > directory ), to always

Re: [SlimDevices: SqueezeCenter] QLogitechMediaServer for Qnap with QTS 4.2 or higher and x86_64/I686/X86 support !

2018-03-24 Thread KeBul
QDon wrote: > > > Why does LMS set up a user named 'root' ? > > This might help you determine if your QNAP has a root user configured... http://www.matthiaseinig.de/2009/12/06/qnap-activate-root-account-on-nas/ I've checked my QNAP's passwd and shadow files and they show there is no root

Re: [SlimDevices: SqueezeCenter] QLogitechMediaServer for Qnap with QTS 4.2 or higher and x86_64/I686/X86 support !

2018-03-24 Thread earthbased
digimaster wrote: > Ha ha it's not creating a root user. > And why don't I have the issue. > My Qnap is a ts-453a with QTS 4.3.4 > > Send from my mobile Phone My TS-251A has a 'root' user but is DISABLED like 'squeezeboxserver' user. I assumed the ADMIN user was just an alias for 'root'.

Re: [SlimDevices: SqueezeCenter] QLogitechMediaServer for Qnap with QTS 4.2 or higher and x86_64/I686/X86 support !

2018-03-24 Thread digimaster
QDon wrote: > The latest response from QNAP is as follows: > > -*Qlogitechmedia creats a root user on the QNAP when it is installed, > which is causing the problem we just need to remove the root users and > the issue with qcenter should go away. The developers failed to tell me > that we would

Re: [SlimDevices: SqueezeCenter] QLogitechMediaServer for Qnap with QTS 4.2 or higher and x86_64/I686/X86 support !

2018-03-24 Thread QDon
digimaster wrote: > Thought so as QLogitechMediaServer is based on the QNap Software. > So if it was causing a problem with QCenter, there would be a fault is > there own software. > Must say could get a bit angry, regarding there messages to you saying > this. > But i think they where think

Re: [SlimDevices: SqueezeCenter] QLogitechMediaServer for Qnap with QTS 4.2 or higher and x86_64/I686/X86 support !

2018-03-24 Thread digimaster
No you done something in the SlimServer/ directory. Do the chmod -R 0755 SlimServer/, and chown -R squeezeboxuser:everyone SlimServer/ from the .qpkg/LogitechMediaServer/ directory. Keep in mind when you in the structure off LMS ( the SlimServer/ directory ), to always do that before restarting

Re: [SlimDevices: SqueezeCenter] QLogitechMediaServer for Qnap with QTS 4.2 or higher and x86_64/I686/X86 support !

2018-03-24 Thread earthbased
New .QKPG error: Code: [18-03-24 09:15:15.7434] Slim::Display::Lib::Fonts::__ANON__ (85) Warning: Unable to load TrueType font support: Can't locate loadable object for module Font::FreeType in @INC (@INC contains:

Re: [SlimDevices: SqueezeCenter] QLogitechMediaServer for Qnap with QTS 4.2 or higher and x86_64/I686/X86 support !

2018-03-24 Thread digimaster
Mnyb wrote: > When you setup LMS the playlist directory and music directory should not > be the same and the playlist dir should not be in the path of the music > dir . > > Then having only read permissions on the music dir and having read/write > on the playlist dir is no problem. > > And