netforce2016 0 Posted March 3, 2016 Share Posted March 3, 2016 (edited) hi all, i am trying to install the amazing emby server into my linux mint 17.3, following several instructions. now the problem is there are apparently some dependencies unresolved wich blocks me from installing emby server. paste from my terminal: user@@Server ~ $ sudo apt-get install emby-serverReading package lists... DoneBuilding dependency tree Reading state information... DoneSome packages could not be installed. This may mean that you haverequested an impossible situation or if you are using the unstabledistribution that some required packages have not yet been createdor been moved out of Incoming.The following information may help to resolve the situation:The following packages have unmet dependencies: emby-server : Depends: mono-devel (>= 1.0) but it is not going to be installed Depends: lsb-base (>= 4.1+Debian11ubuntu7) but 4.1+Debian11ubuntu6mint1 is to be installedE: Unable to correct problems, you have held broken packages. if you have any ideas on how to fix this? thank you. i fixed it using this: http://emby.media/community/index.php?/topic/30210-broken-packages-cant-install-the-media-server-on-linux-mint-172/page-2&do=findComment&comment=290615 and then the default setup for 14.04 xUbuntu. (i recommend making a DEB file that works, to prevent users from f*cking up the setup/repos) Edited March 3, 2016 by netforce2016 Link to comment Share on other sites More sharing options...
geaves 13 Posted March 3, 2016 Share Posted March 3, 2016 i fixed it using this: http://emby.media/community/index.php?/topic/30210-broken-packages-cant-install-the-media-server-on-linux-mint-172/page-2&do=findComment&comment=290615 and then the default setup for 14.04 xUbuntu. (i recommend making a DEB file that works, to prevent users from f*cking up the setup/repos) Hm!! it does work. Linux Mint 17.3 is based upon Ubuntu 14.04 LTS, there are clear instructions for each distro, so if you installed emby using the instructions for say Ubuntu 15.10 then you will get the errors as the underlying o/s is 14.04. Link to comment Share on other sites More sharing options...
netforce2016 0 Posted March 3, 2016 Author Share Posted March 3, 2016 ok, on to the next problem. my files are on several encrypted (FUSE) filesystems. (veracrypt) now, emby cant access the folders on the filesystem. is there a way to either add permissions to the folder/drive for the user émby'or change the execution user of emby to my regular user? Link to comment Share on other sites More sharing options...
netforce2016 0 Posted March 3, 2016 Author Share Posted March 3, 2016 (edited) Hm!! it does work. Linux Mint 17.3 is based upon Ubuntu 14.04 LTS, there are clear instructions for each distro, so if you installed emby using the instructions for say Ubuntu 15.10 then you will get the errors as the underlying o/s is 14.04. ah yes, i didnt want to insult anyone. i did one thing wrong apparently, i shouldnt add the PPAkey for this. after i restarted all, and didnt add the key/cert, it works fine. tho i cannot get access to my encrypted ntfs drives (/media/veracrypt1 ~ veracrypt4) i tried modified commands from http://emby.media/community/index.php?/topic/31142-permissions/ but no change, not even after reboot... --- edit: i added the user emby to the main user group, and added the user to the main emby group, and also added the user emby to the fuse group (using kuser) still cannot access my drives thru emby interface. i can play the files on the disks with any software, including vlc media player and kodi. please help Edited March 3, 2016 by netforce2016 Link to comment Share on other sites More sharing options...
geaves 13 Posted March 3, 2016 Share Posted March 3, 2016 (edited) You'll need to 'mount' your shares so that Emby can 'see' them on your Mint box with an fstab entry. For instance my Emby is on an Ubuntu server but my files are on a nas4free box, (SMB shares) so on my server I have to create a mount point so that Emby can see them, in effect it's a symlink. So on the server under /media I have a folder movies, this then has an fstab entry //serverIP/movies /media/movies cifs user,users 0 0 because I am using smb shares, so now Emby can see those when I add media to Emby, I then set up path substitution. Sorry I'm cooking dinner so on and off here.... Edited March 3, 2016 by geaves Link to comment Share on other sites More sharing options...
netforce2016 0 Posted March 3, 2016 Author Share Posted March 3, 2016 You'll need to 'mount' your shares so that Emby can 'see' them on your Mint box with an fstab entry. For instance my Emby is on an Ubuntu server but my files are on a nas4free box, (SMB shares) so on my server I have to create a mount point so that Emby can see them, in effect it's a symlink. So on the server under /media I have a folder movies, this then has an fstab entry //serverIP/movies /media/movies cifs user,users 0 0 because I am using smb shares, so now Emby can see those when I add media to Emby, I then set up path substitution. Sorry I'm cooking dinner so on and off here.... yes i understand, but the disks i am speaking of are locally mounted disks, not shares. and for security reasons i am not gonna fstab my encrypted disks with a password in fstab (i know i can, but i wont) Link to comment Share on other sites More sharing options...
geaves 13 Posted March 3, 2016 Share Posted March 3, 2016 yes i understand, but the disks i am speaking of are locally mounted disks, not shares. and for security reasons i am not gonna fstab my encrypted disks with a password in fstab (i know i can, but i wont) Apologies, My only understanding of local disks' and that's from reading on here is that Emby requires permission to access the media folder, so adding Emby to your fuse group may not be enough, adding the Emby user to the share may be the solution. Link to comment Share on other sites More sharing options...
netforce2016 0 Posted March 3, 2016 Author Share Posted March 3, 2016 Apologies, My only understanding of local disks' and that's from reading on here is that Emby requires permission to access the media folder, so adding Emby to your fuse group may not be enough, adding the Emby user to the share may be the solution. in theory emby should have access rights to the path, i added the user emby as a member to the normal usergroup (users) wich is able to fully access the path. i am baffled at the moment, giving it a good thought. Link to comment Share on other sites More sharing options...
geaves 13 Posted March 3, 2016 Share Posted March 3, 2016 in theory emby should have access rights to the path, i added the user emby as a member to the normal usergroup (users) wich is able to fully access the path. i am baffled at the moment, giving it a good thought. I wonder if this may be helpful. Link to comment Share on other sites More sharing options...
thefirstofthe300 291 Posted March 3, 2016 Share Posted March 3, 2016 (edited) Hmm...I just went through adding a VeraCrypt volume and Emby was able to read it right out of the box for me. May I ask where your Emby install is pointing the movie folders at? Is it at the encrypted volumes themselves or at the mount point (something like /media/veracrypt1)? EDIT: Rereading this post I just noticed that the Veracrypt drives are NTFS drives. That makes things 100% more difficult for permissions due to limitations of the Windows filesystems. NTFS only gives one user read and write access on mount. The way to work around this is to run Emby as the user that mounts the Veracrypt volumes. You can accomplish this by editing /etc/emby-server.conf. Also, you will more than likely need to change the permissions on the database folder /var/lib/emby-server to be the user:group that Emby is now running as. Edited March 3, 2016 by thefirstofthe300 Link to comment Share on other sites More sharing options...
netforce2016 0 Posted March 4, 2016 Author Share Posted March 4, 2016 Hmm...I just went through adding a VeraCrypt volume and Emby was able to read it right out of the box for me. May I ask where your Emby install is pointing the movie folders at? Is it at the encrypted volumes themselves or at the mount point (something like /media/veracrypt1)? EDIT: Rereading this post I just noticed that the Veracrypt drives are NTFS drives. That makes things 100% more difficult for permissions due to limitations of the Windows filesystems. NTFS only gives one user read and write access on mount. The way to work around this is to run Emby as the user that mounts the Veracrypt volumes. You can accomplish this by editing /etc/emby-server.conf. Also, you will more than likely need to change the permissions on the database folder /var/lib/emby-server to be the user:group that Emby is now running as. i guess i need to buy a new harddisk then and migrate all my media to ext4 drives. cannot get this to work. was planning that anyway. i tried all options i could find, no success. Thnx for thinking with me Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now