Topic: JRiver Media Center 23.0.51 for Debian STRETCH AMD64 Beta (Read 23389 times)

Rizlaw · « **Reply #50 on:** September 08, 2017, 12:51:15 pm »

As I stated in my post, I opened a terminal IN THE FOLDER where the deb file was located, so there is no need for a "path". And yes, I did download the file thank you.

Awesome Donkey · « **Reply #51 on:** September 08, 2017, 01:03:02 pm »

Do this from the Terminal (skip the first step if you've already downloaded the .deb file)...

Code: [Select]

wget http://files.jriver.com/mediacenter/test/MediaCenter-23.0.51-amd64.deb
Then try this (if you've already downloaded the .deb file, look to the instructions under this command) - I haven't tested this, as I don't have any Ubuntu installs at the moment (waiting for 17.10)...

Code: [Select]

sudo dpkg -i 'MediaCenter-23.0.51-amd64.deb'
If the above fails or you've already downloaded the .deb file, instead of 'MediaCenter-23.0.51-amd64.deb' simply drag and drop the downloaded .deb file into the Terminal so it posts the full path to the .deb file. Also always make sure there's a space between -i and the 'pathtothe.deb'. Then press Enter to install (and input your password when prompted).

Otherwise if you encounter an error about unresolved dependencies, try this...

Code: [Select]

sudo apt-get install -f
That *should* do it. Hopefully.

P.S. If you're using Debian Wheezy/Jessie, Ubuntu 16.04 LTS or Linux Mint 18.x, this Stretch AMD64 build of 23.0.51 will NOT function correctly for you. Those OSes have libraries that are older than the increased minimum versions of libraries. If you try to install this build on an older OS, it *may* install and it *may* even function after installing, but the package manager (e.g. Synaptic) will freak out about the newer lib requirements and it will flag MC 23 as a broken package! If you're using these older OSes, it's *highly* recommended to use the i386 build instead!

Rizlaw · « **Reply #52 on:** September 08, 2017, 01:11:57 pm »

AD,

That completely borked my MC23 install. It's totally gone. Here's most of the terminal info after step 1 of 3 as suggested:

Code: [Select]

ouis@Gort:~$ sudo dpkg -i 'MediaCenter-23.0.51-amd64.deb'
(Reading database ... 299799 files and directories currently installed.)
Preparing to unpack MediaCenter-23.0.51-amd64.deb ...
Unpacking mediacenter23 (23.0.51) over (23.0.21) ...
dpkg: dependency problems prevent configuration of mediacenter23:
 mediacenter23 depends on libxcb1 (>= 1.12); however:
  Version of libxcb1:amd64 on system is 1.11.1-1ubuntu1.

dpkg: error processing package mediacenter23 (--install):
 dependency problems - leaving unconfigured
Processing triggers for bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for gnome-menus (3.13.3-6ubuntu5) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for shared-mime-info (1.8-1) ...
Errors were encountered while processing:
 mediacenter23
louis@Gort:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following packages will be REMOVED:
  mediacenter23
0 upgraded, 0 newly installed, 1 to remove and 4 not upgraded.
1 not fully installed or removed.
After this operation, 171 MB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 299725 files and directories currently installed.)
Removing mediacenter23 (23.0.51) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
Processing triggers for bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for shared-mime-info (1.8-1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu5) ...
louis@Gort:~$

Awesome Donkey · « **Reply #53 on:** September 08, 2017, 01:16:23 pm »

Looks like you're installing it on an older OS that doesn't have the newer lib requirements these Stretch AMD64 builds have. Is it the 16.04 LTS in your sig? This build won't work there. I don't have a 17.04 VM right now, so I can't test 23.0.51 there. if it's breaking in 17.04 make sure your OS is up-to-date with all updates. If so and it's still breaking, it's possible all Ubuntu releases are currently incompatible with the Stretch AMD64 build.

The giveaway is this part of the log;

Code: [Select]

pkg: dependency problems prevent configuration of mediacenter23:
 mediacenter23 depends on libxcb1 (>= 1.12); however:
  Version of libxcb1:amd64 on system is 1.11.1-1ubuntu1.

MC23 depends on 1.12 or higher libxcb1 but the system only has 1.11.1 so the package manager is flagging MC as a broken package and is removing it.

You *might* have to use the i386 build. Look at my edited post above with the P.S.

Rizlaw · « **Reply #54 on:** September 08, 2017, 01:22:05 pm »

AD,

Bob's post seemed to state that it would work in 17.04. Obviously it doesn't. So, I guess I have to try and fix the errors and reinstall the last version of MC that worked until 17.10 is released.

Awesome Donkey · « **Reply #55 on:** September 08, 2017, 01:24:39 pm »

Bob, I'm starting to think you might be right in downgrading to Jessie level for AMD64 since the install is currently failing on all Ubuntu distros, it seems. Maybe until MC24, when Ubuntu 18.04 LTS is out (along with hopefully Linux Mint 19). It makes sense, you could wait a year after a Debian release before moving on up to the latest stable release so the Debian derivatives can catch up.

Hendrik · « **Reply #56 on:** September 08, 2017, 01:41:14 pm »

Isnt the point of using "-f" to ignore dependency issues? It should still run regardless.

Rizlaw · « **Reply #57 on:** September 08, 2017, 02:04:50 pm »

Hendrik,

It seems "-f" doesn't work in Ubuntu 17.04; at least for me. As for reverting to Debian Jessie for AMD64 MediaCenter, that's a discussion far above my pay grade. I am back to 23.0.21 and that works fine on 17.04 (albeit without the latest improvements to MC). If all this grief is fixed with the upcoming 17.10 release of Ubuntu, my vote is to stay the course with Debian Stretch AMD64.

bob · « **Reply #58 on:** September 08, 2017, 02:48:23 pm »

apt-get install
uses the repo.
It's not in latest yet.

I'm going to backoff the AMD64 build to Jessie and upload one. Perhaps later today.

Wybe · « **Reply #59 on:** September 19, 2017, 03:30:48 am »

Which version is at the moment the latest stable version for Debian Stretch amd 64? Can I use version 23.0.54 (mentioned in a different topic), or is there a difference in the version and route for Jessie and Stretch?

hillcreative · « **Reply #60 on:** September 19, 2017, 08:37:40 am »

Right-clicking a playlist item in a list causes MC 20.0.54 to hang for a minute before continuing. Using Ubuntu 17.04.

bob · « **Reply #61 on:** September 19, 2017, 08:52:44 am »

Quote from: Wybe on September 19, 2017, 03:30:48 am

Which version is at the moment the latest stable version for Debian Stretch amd 64? Can I use version 23.0.54 (mentioned in a different topic), or is there a difference in the version and route for Jessie and Stretch?

The build is now done on Jessie.
That works fine on Stretch (which is what I'm running).

bob · « **Reply #62 on:** September 19, 2017, 08:55:14 am »

Quote from: hillcreative on September 19, 2017, 08:37:40 am

Right-clicking a playlist item in a list causes MC 20.0.54 to hang for a minute before continuing. Using Ubuntu 17.04.

Not seeing that here.
Are there any URLs in the playlist or something on a removable drive or network share perhaps?

hillcreative · « **Reply #63 on:** September 19, 2017, 10:14:46 am »

Quote from: bob on September 19, 2017, 08:55:14 am

Not seeing that here.
Are there any URLs in the playlist or something on a removable drive or network share perhaps?

Yes, music is on a Windows SMB share. Problem does not show up when using remote control.

bob · « **Reply #64 on:** September 19, 2017, 02:32:31 pm »

Quote from: hillcreative on September 19, 2017, 10:14:46 am

Yes, music is on a Windows SMB share. Problem does not show up when using remote control.

Which remote?
Is the share mounted??

hillcreative · « **Reply #65 on:** September 19, 2017, 03:26:35 pm »

Quote from: bob on September 19, 2017, 02:32:31 pm

Which remote?
Is the share mounted??

Any MC remote I've tried: Tremote and iPhone. Share is mounted from Windows SMB drive on network

bob · « **Reply #66 on:** September 19, 2017, 04:20:08 pm »

Quote from: hillcreative on September 19, 2017, 03:26:35 pm

Any MC remote I've tried: Tremote and iPhone. Share is mounted from Windows SMB drive on network

When you do the
df -k
and
mount

commands on your linux machine and post the results here?

hillcreative · « **Reply #67 on:** September 19, 2017, 04:56:32 pm »

Quote from: bob on September 19, 2017, 04:20:08 pm

When you do the
df -k
and
mount

commands on your linux machine and post the results here?

Could you be more specific. I'm a Linux newbie

JimH · « **Reply #68 on:** September 19, 2017, 05:40:08 pm »

Those are linux commands. You enter them at the command line, usually a $ prompt or a # prompt. Try Google if you still don't understand.

gilesw · « **Reply #69 on:** September 19, 2017, 08:09:25 pm »

I'm new to jriver so i've installed a clean debian stretch as it's now the stable debian release. However using vnc to connect I get the bit white screen like others:-

ii mediacenter23 23.0.61 amd64 Media Player

https://www.dropbox.com/s/rro4n1q4etw0z6y/Screenshot%202017-09-20%2002.08.45.png?dl=0

hillcreative · « **Reply #70 on:** September 19, 2017, 08:27:59 pm »

Quote from: bob on September 19, 2017, 04:20:08 pm

When you do the
df -k
and
mount

commands on your linux machine and post the results here?

Filesystem 1K-blocks Used Available Use% Mounted on
udev 4011060 0 4011060 0% /dev
tmpfs 806776 9724 797052 2% /run
/dev/sda1 114854020 8374840 100601832 8% /
tmpfs 4033880 37020 3996860 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 4033880 0 4033880 0% /sys/fs/cgroup
tmpfs 806776 172 806604 1% /run/user/1000
/dev/sdb1 57431032 53272 54430644 1% /media/mitchell/SSD Internal
mitchell@NanoPC:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=4011060k,nr_inodes=1002765,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=806776k,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=2665)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=806776k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sdb1 on /media/mitchell/SSD Internal type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)

gilesw · « **Reply #71 on:** September 20, 2017, 04:28:33 pm »

Well for what it's worth I had a white box because I was using a 16bit colour depth for vnc not 24 and tigervnc-standalone-server.

Stretch is supported for a /really/ long time so I would like to use it for my new build. I'm going to drop my library in and see how long it stays running..

bob · « **Reply #72 on:** September 21, 2017, 09:09:19 am »

Quote from: gilesw on September 20, 2017, 04:28:33 pm

Well for what it's worth I had a white box because I was using a 16bit colour depth for vnc not 24 and tigervnc-standalone-server.

Stretch is supported for a /really/ long time so I would like to use it for my new build. I'm going to drop my library in and see how long it stays running..

As you've discovered, MC requires 24 bit color.

bob · « **Reply #73 on:** September 21, 2017, 09:15:28 am »

Quote from: hillcreative on September 19, 2017, 08:27:59 pm

Filesystem 1K-blocks Used Available Use% Mounted on
udev 4011060 0 4011060 0% /dev
tmpfs 806776 9724 797052 2% /run
/dev/sda1 114854020 8374840 100601832 8% /
tmpfs 4033880 37020 3996860 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 4033880 0 4033880 0% /sys/fs/cgroup
tmpfs 806776 172 806604 1% /run/user/1000
/dev/sdb1 57431032 53272 54430644 1% /media/mitchell/SSD Internal
mitchell@NanoPC:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=4011060k,nr_inodes=1002765,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=806776k,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=2665)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=806776k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sdb1 on /media/mitchell/SSD Internal type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)

There is no mounted SMB share listed here.
Just because a file browser can show there are files on your share doesn't mean it's mounted.
Check this post:
https://yabb.jriver.com/interact/index.php/topic,109431.msg757225.html#msg757225

hillcreative · « **Reply #74 on:** September 21, 2017, 02:46:55 pm »

Quote from: bob on September 21, 2017, 09:15:28 am

There is no mounted SMB share listed here.
Just because a file browser can show there are files on your share doesn't mean it's mounted.
Check this post:
https://yabb.jriver.com/interact/index.php/topic,109431.msg757225.html#msg757225

Interesting as this plays audio with MC 23.0.54

bob · « **Reply #75 on:** September 21, 2017, 02:51:16 pm »

Quote from: hillcreative on September 21, 2017, 02:46:55 pm

Interesting as this plays audio with MC 23.0.54

How?
You have a mounted internal drive /media/mitchell/SSD Internal which I suppose might contain media files but there is no share mounted and MC doesn't automount shares.

hillcreative · « **Reply #76 on:** September 21, 2017, 02:52:26 pm »

Quote from: bob on September 21, 2017, 09:15:28 am

There is no mounted SMB share listed here.
Just because a file browser can show there are files on your share doesn't mean it's mounted.
Check this post:
https://yabb.jriver.com/interact/index.php/topic,109431.msg757225.html#msg757225

Screenshot shows mount as SMB

bob · « **Reply #77 on:** September 21, 2017, 02:59:16 pm »

That doesn't show a mount.
It shows a samba resource.
Your file browser is querying the resource, it's not mounting it.

hillcreative · « **Reply #78 on:** September 21, 2017, 03:13:31 pm »

Quote from: bob on September 21, 2017, 02:59:16 pm

That doesn't show a mount.
It shows a samba resource.
Your file browser is querying the resource, it's not mounting it.

That confuses me as MC is playing the samba source as shown. I'll do some research on how to properly mount a SMB share and report back. Thanks for the help!

bob · « **Reply #79 on:** September 21, 2017, 03:17:46 pm »

Quote from: hillcreative on September 21, 2017, 03:13:31 pm

That confuses me as MC is playing the samba source as shown. I'll do some research on how to properly mount a SMB share and report back. Thanks for the help!

I'd like to know how it's playing the file via smb without mounting.
You could look at the filename path in MC's database for one you suspect you are playing back from the share to see what it says...

Anyway the post I referred you to previously has information on how to mount samba shares. Good luck!

hillcreative · « **Reply #80 on:** September 21, 2017, 04:04:10 pm »

Quote from: bob on September 21, 2017, 03:17:46 pm

I'd like to know how it's playing the file via smb without mounting.
You could look at the filename path in MC's database for one you suspect you are playing back from the share to see what it says...

This is the path the library XML shows:
/run/user/1000/gvfs/smb-share:server=hillwrk,share=f/WAV Music Master/00012643.wav

mwillems · « **Reply #81 on:** September 21, 2017, 05:34:37 pm »

That's gvfs exposing the samba share as a pseudo-file system. I wouldn't expect anything other than nautilus (the gnome file manager) or maybe thunar (another gtk file manager) to be able to see that.

I've posted persistent mounting instructions for samba shares a few times, let me see if I can find my posts.
EDIT:
Here we go: https://yabb.jriver.com/interact/index.php/topic,110697.msg765193.html#msg765193

hillcreative · « **Reply #82 on:** September 21, 2017, 05:37:24 pm »

Quote from: mwillems on September 21, 2017, 05:34:37 pm

I've posted persisent mounting instructions for samba shares a few times, let me see if I can find my posts.
EDIT:
Here we go: https://yabb.jriver.com/interact/index.php/topic,110697.msg765193.html#msg765193

Thanks!

hillcreative · « **Reply #83 on:** September 21, 2017, 09:09:03 pm »

Quote from: mwillems on September 21, 2017, 05:34:37 pm

I've posted persistent mounting instructions for samba shares a few times, let me see if I can find my posts.
EDIT:
Here we go: https://yabb.jriver.com/interact/index.php/topic,110697.msg765193.html#msg765193

Seem to be having newbie problems with creating a mounting point. Here is my fstab line:

Code: [Select]

//hillwrk/f /mnt/media cifs noauto,x-systemd.automount,credentials=/home/mitchell/samba-credentials 0 0Confirmed that something is there after:

Code: [Select]

sudo mkdir /mnt/mediaDetails:

Code: [Select]

Filesystem     1K-blocks    Used Available Use% Mounted on
udev             4011056       0   4011056   0% /dev
tmpfs             806776    9672    797104   2% /run
/dev/sda1      114854020 8248396 100728276   8% /
tmpfs            4033880   36944   3996936   1% /dev/shm
tmpfs               5120       4      5116   1% /run/lock
tmpfs            4033880       0   4033880   0% /sys/fs/cgroup
tmpfs             806776     160    806616   1% /run/user/1000
mitchell@NanoPC:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=4011056k,nr_inodes=1002764,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=806776k,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /mnt/media type autofs (rw,relatime,fd=24,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14077)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14115)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=806776k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

mwillems · « **Reply #84 on:** September 21, 2017, 09:26:53 pm »

Quote from: hillcreative on September 21, 2017, 09:09:03 pm

Seem to be having newbie problems with creating a mounting point. Here is my fstab line:
Code: [Select]
//hillwrk/f /mnt/media cifs noauto,x-systemd.automount,credentials=/home/mitchell/samba-credentials 0 0Confirmed that something is there after:
Code: [Select]
sudo mkdir /mnt/mediaDetails:
Code: [Select]
Filesystem 1K-blocks Used Available Use% Mounted on udev 4011056 0 4011056 0% /dev tmpfs 806776 9672 797104 2% /run /dev/sda1 114854020 8248396 100728276 8% / tmpfs 4033880 36944 3996936 1% /dev/shm tmpfs 5120 4 5116 1% /run/lock tmpfs 4033880 0 4033880 0% /sys/fs/cgroup tmpfs 806776 160 806616 1% /run/user/1000 mitchell@NanoPC:~$ mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=4011056k,nr_inodes=1002764,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=806776k,mode=755) /dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) systemd-1 on /mnt/media type autofs (rw,relatime,fd=24,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14077) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14115) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=806776k,mode=700,uid=1000,gid=1000) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

What does "confirmed that something is there" mean? You confirmed that the directory /mnt/media existed or you found files inside /mnt/media?

Two guesses:
1) I suspect your server address may not be correct. If you note in my advice I suggested that you use the IP address of the server, not the server name. That's because there's no guarantee that the name will resolve correctly unless you've edited your hosts file or are running a local DNS server or something.
2) Did you reboot? In your df output it looks like nothing is mounted at /mnt/media which suggests that either mounting isn't working or you haven't rebooted it.

A diagnostic step: what does the terminal say if you run "sudo mount /mnt/media"?

hillcreative · « **Reply #85 on:** September 21, 2017, 09:41:13 pm »

Quote from: mwillems on September 21, 2017, 09:26:53 pm

A diagnostic step: what does the terminal say if you run "sudo mount /mnt/media"?

Results:

Code: [Select]

mitchell@NanoPC:~$ sudo mount /mnt/media
[sudo] password for mitchell: 
mount: wrong fs type, bad option, bad superblock on //hillwrk/f,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

Changed hillwrk to ip address in fstab line with same results

mwillems · « **Reply #86 on:** September 21, 2017, 10:08:13 pm »

Well, one way to get that error message is if you don't have cifs-utils installed, but that would be really odd on a modern linux distro. I don't see that you posted what distro you're running, but if it's debian-based try "sudo apt-get install cifs-utils"

hillcreative · « **Reply #87 on:** September 21, 2017, 10:58:46 pm »

Quote from: mwillems on September 21, 2017, 10:08:13 pm

Well, one way to get that error message is if you don't have cifs-utils installed, but that would be really odd on a modern linux distro. I don't see that you posted what distro you're running, but if it's debian-based try "sudo apt-get install cifs-utils"

Running Ubuntu 17.04 Installed cifs-utils. Ran diagnostics with result:

Code: [Select]

mitchell@NanoPC:~$ sudo mount /mnt/media
[sudo] password for mitchell: 
mount error(16): Device or resource busy
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

franswilco · « **Reply #88 on:** September 22, 2017, 08:09:43 am »

Thank you.

As a long time Mac and Windows user, I just tried Linux for the first time. There's a lot more tweaking involved to set up the overall system. Something I don't mind. I am using JRiver for quite some time now on Windows. Here are my first impressions with the Linux program. I hope this helps:

- I run a dual screen setup. JRiver opens quite randomly from screen to screen. After manually moving JRiver to the screen I want, any additional JRiver pop-up windows still open on the other (wrong) screen. I solved this using gDevilspie, but it is still annoying, because every time a JRiver pop-up open for the first time (the DSP pop up for instance), I have to manually add that pop up screen to gDevilpie, in order for it to open on the right screen the next time I try it.

- Going to Import - > Import -> Media Import, I select the Browser button. The "Select Path" system pop up window opens behind the JRiver pop up window.

- The mouse cursor changes from system default to a different arrow from time to time. Is there a way to disable this? I don't see the logic or benefit for JRiver to overwrite my system's default mouse pointer.

- Fonts do not look well anti-aliased. Anti-aliasing as a whole on Debian 9 / KDE doesn't look as good as it does on Windows or Mac, so I'm not sure if JRiver can be improved. I'm a web developer, so I do have a thing for well anti-aliased fonts, I guess. Window's pretty terrible compared to Mac, but Debian 9 / KDE is another thing entirely, so it seems.

- My biggest issue is that JRiver is noticeably slower to respond (screen rendering, clicking on songs to play, etc) on Linux Debian 9 (KDE) than on Windows. It's also more unstable. I do have to add I have installed the latest 64 bit version that I did not try on Windows yet.

I am looking to replace my HTPC set-up from Windows to Linux entirely, but only if the OS and my two main programs (JRiver / Plex (now Kodi on Linux)) behave as well as, or better than, they do on Windows. So far I am not yet convinced.

hillcreative · « **Reply #89 on:** September 22, 2017, 08:09:54 am »

I think there is something wrong with permissions when using sudo mkdir /mnt/media as it automatically does this in the root folder. When instead I install the mounting point in /home/user_name/Media all is well and it mounts!
modified fstab entry line that works for me:

Code: [Select]

//10.20.40.80/f /home/mitchell/Media cifs noauto,x-systemd.automount,credentials=/home/mitchell/samba-credentials  0  0

Thanks for the help. This is a very useful forum.

bob · « **Reply #90 on:** September 22, 2017, 09:09:54 am »

Quote from: franswilco on September 22, 2017, 08:09:43 am

Thank you.

As a long time Mac and Windows user, I just tried Linux for the first time. There's a lot more tweaking involved to set up the overall system. Something I don't mind. I am using JRiver for quite some time now on Windows. Here are my first impressions with the Linux program. I hope this helps:

- I run a dual screen setup. JRiver opens quite randomly from screen to screen. After manually moving JRiver to the screen I want, any additional JRiver pop-up windows still open on the other (wrong) screen. I solved this using gDevilspie, but it is still annoying, because every time a JRiver pop-up open for the first time (the DSP pop up for instance), I have to manually add that pop up screen to gDevilpie, in order for it to open on the right screen the next time I try it.

- Going to Import - > Import -> Media Import, I select the Browser button. The "Select Path" system pop up window opens behind the JRiver pop up window.

- The mouse cursor changes from system default to a different arrow from time to time. Is there a way to disable this? I don't see the logic or benefit for JRiver to overwrite my system's default mouse pointer.

- Fonts do not look well anti-aliased. Anti-aliasing as a whole on Debian 9 / KDE doesn't look as good as it does on Windows or Mac, so I'm not sure if JRiver can be improved. I'm a web developer, so I do have a thing for well anti-aliased fonts, I guess. Window's pretty terrible compared to Mac, but Debian 9 / KDE is another thing entirely, so it seems.

- My biggest issue is that JRiver is noticeably slower to respond (screen rendering, clicking on songs to play, etc) on Linux Debian 9 (KDE) than on Windows. It's also more unstable. I do have to add I have installed the latest 64 bit version that I did not try on Windows yet.

I am looking to replace my HTPC set-up from Windows to Linux entirely, but only if the OS and my two main programs (JRiver / Plex (now Kodi on Linux)) behave as well as, or better than, they do on Windows. So far I am not yet convinced.

Are you running a nvidia video card with the Nouveau X server?
The issues you are describing (popup windows, etc) don't occur with intel video, nvidia cards with nvidia drivers, etc.
Nouveau has known issues, especially with MC.

franswilco · « **Reply #91 on:** September 22, 2017, 11:20:37 am »

Quote from: bob on September 22, 2017, 09:09:54 am

Are you running a nvidia video card with the Nouveau X server?
The issues you are describing (popup windows, etc) don't occur with intel video, nvidia cards with nvidia drivers, etc.
Nouveau has known issues, especially with MC.

Hi Bob,

I have a fairly modest system built around bit-perfect audio and 1080P playback. I am running an AMD A6-A3500 APU, 8GB RAM and a Radeon HD6450 card (because the motherboard itself doesn't support driving both HDMI and the DVI connector. Bummer! I have about 5 hard drives (WD Green's, SATA internal). The system disk is a Samsung EVO SSD.

I have the following packages installed:

- xserver-xorg-video-radeon-dbg
- amd-microcode
- xserver-xorg-video-ati-dbg

Any help is appreciated because I am completely new to Linux!

INTERACT FORUM

Author Topic: JRiver Media Center 23.0.51 for Debian STRETCH AMD64 Beta (Read 23389 times)