INTERACT FORUM
More => Old Versions => JRiver Media Center 23 for Linux => Topic started by: bob on August 07, 2017, 11:14:50 am
-
This is a first crack at a debian stretch AMD64 build of MC23 with GCC 6. It requires libraries that are equivalent to the default ones on stretch OR newer.
Please post bugs here. Please start a new thread for anything requiring discussion. Non-bug posts will be deleted.
Download:
http://files.jriver.com/mediacenter/test/MediaCenter-23.0.51-amd64.deb
Use the current Jessie revision instead. See the top of the forum for the latest version.
Also in the BETA repo.
23.0.51 (9/7/2017)
1. NEW: Enabled the use of VST Plugins.
23.0.41 (8/28/2017)
1. NEW: Implement non-US keyboard support.
2. Fixed: Under some situations, menus could appear blank with some hardware/desktop manager combinations.
23.0.36 (8/18/2017)
1. Fixed: Crashing in Theater View from GCC6 non-compliant code.
23.0.31-2 (8/7/2017)
1. Changed: Relaxed package requirements to ignore the minor revision of a package.
2. Fixed: Removed libicu requirement.
23.0.31 (8/7/2017)
1. NEW: First BETA build for debian stretch AMD64.
2. Fixed: Internal structures dealing with UI functions.
-
Greetings:
From 23.28 to 23.31, installing just quits. It will display "install" at 9%, then goes off the screen.
I even uninstalled 23.0.28, to get a fresh 23.0.31, still failed. It says source "unknown".
I am now back at 23.0.28.
As an addition to these issues:
The audio is skipping badly on versions 23.21 and 23.28. I wrote on another thread over the weekend, comparing to Windows version 23....xx.., we have a way to adjust the skipping and buffering in audio device setting or in DSP setting not sure exactly what specific area, but in the Linux distros, no way for this convenient adjustment.
I am on Ubuntu 1704 64 bit.
Thanks.
George Omoregie
-
We have an installer now? :)
-
Try installing the .deb from the Terminal.
-
FWIW, on TumbleWeed, libICU is up to v.59.1, so I had to create three symlinks:
ln -s libicudata.so.59.1 libicudata.so.57
ln -s libicuuc.so.59.1 libicuuc.so.57
ln -s libicui18n.so.59.1 libicui18n.so.57
I do have the 57.1 and 58.2 versions also (they appear to be orphans, however) but I set the links to 59.1 since it is the latest in TW. Seems to be working okay, haven't noticed anything weird yet.
-
Try installing the .deb from the Terminal.
I deleted the 23.0.31 downloaded, re-downloaded, tried to install. The installer screen thinks it is 32.0.28. Install quits again.
Then I remembered the tutorial about apt, some snippets etc. Went to the terminal, issued all commands.. every thing fine. Installed, then loaded what I thought was 23.0.31. I went to help and about, it still says 23.0.28.
Summary : No matter how I installed it, terminal or via installer, it still does not install MC 23.0.31.
I am back now on 23.0.28.
Hendriks: Did you replace this with a version that has the installer ?
I will be happy if you can take a look at the code why audio in (movies) playback is breaking, slipping, or whatever it is called buffering , In one word.. No Smooth audio Playback.. did audio analysis several times.
Thanks in advance.
George
-
FWIW, on TumbleWeed, libICU is up to v.59.1, so I had to create three symlinks:
ln -s libicudata.so.59.1 libicudata.so.57
ln -s libicuuc.so.59.1 libicuuc.so.57
ln -s libicui18n.so.59.1 libicui18n.so.57
I do have the 57.1 and 58.2 versions also (they appear to be orphans, however) but I set the links to 59.1 since it is the latest in TW. Seems to be working okay, haven't noticed anything weird yet.
Shouldn't be needing libicu, that may have been so in the past.
I am somewhat concerned about the compatibility of the AMD64 build with non-debian distros.
Here are the top level library depends:
libc6 (>= 2.24)
libasound2 (>= 1.1.3)
libuuid1 (>= 2.29)
libx11-6 (>= 2:1.6.4)
libxext6 (>= 2:1.3.3)
libxcb1 (>= 1.12)
libxau6 (>= 1:1.0.8)
libxdmcp6 (>= 1:1.1.2)
libstdc++6 (>= 6.3.0)
libgtk2.0-0 (>= 2.24.31)
libpango-1.0-0 (>= 1.40) or libpango1.0-0 (>= 1.40)
libpangoft2-1.0-0 (>= 1.40) | libpango-cairo-1.0-0 (>= 1.40)
libgl1-mesa-glx or libgl1
xdg-utils
-
Yeah, no go here on Arch Linux.
mediacenter23: error while loading shared libraries: libicuuc.so.57: cannot open shared object file: No such file or directory
Easily fixed though using the symlinks posted by Mike Noe above, thanks!
-
No go on Linux Mint either.
dpkg: dependency problems prevent configuration of mediacenter23:
mediacenter23 depends on libc6 (>= 2.24); however:
Version of libc6:amd64 on system is 2.23-0ubuntu9.
mediacenter23 depends on libasound2 (>= 1.1.3); however:
Version of libasound2:amd64 on system is 1.1.0-0ubuntu1.
mediacenter23 depends on libuuid1 (>= 2.29); however:
Version of libuuid1:amd64 on system is 2.27.1-6ubuntu3.3.
mediacenter23 depends on libx11-6 (>= 2:1.6.4); however:
Version of libx11-6:amd64 on system is 2:1.6.3-1ubuntu2.
mediacenter23 depends on libxcb1 (>= 1.12); however:
Version of libxcb1:amd64 on system is 1.11.1-1ubuntu1.
mediacenter23 depends on libstdc++6 (>= 6.3.0); however:
Version of libstdc++6:amd64 on system is 5.4.0-6ubuntu1~16.04.4.
mediacenter23 depends on libgtk2.0-0 (>= 2.24.31); however:
Version of libgtk2.0-0:amd64 on system is 2.24.30-1ubuntu1.16.04.1.
mediacenter23 depends on libpango-1.0-0 (>= 1.40) | libpango1.0-0 (>= 1.40); however:
Version of libpango-1.0-0:amd64 on system is 1.38.1-1
dpkg: error processing package mediacenter23 (--install):
dependency problems - leaving unconfigured
-
Mint is based on Ubuntu or debian, probably need a new release to catch up to Debian.
For libicu, boost seems to link against those. I'll check tomorrow if thats a build error or whats up with that. Those were not required in the past, as far as I know.
Edit:
Found it, icu should not be required anymore (or once again?) in the next build.
-
It's based on Ubuntu, which is based on Debian. But yeah, it's generally out-of-date as it uses Ubuntu 14.04 LTS as a base. I'm sure it'll change next year with 18.04 LTS. It also happens on Ubuntu 17.04 too with just one lib, so I guess that's an improvement. :P I'll likely switch back from Mint to Ubuntu at some point - really wanted to wait until 17.10 came out, but maybe I should give the Ubuntu daily alpha builds a go? Anyways...
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.
-
Its an unusual situation when Debian of all things appears to have "too new" stuff. :p
-
Its an unusual situation when Debian of all things appears to have "too new" stuff. :p
No kidding, it's usually always the other way around. Looks like Ubuntu 17.10 is *still* using libxcb 11.11.1 but hopefully that changes before the final release (thanks to the release of Debian 9).
But yeah, I got it working on Arch Linux at least, and it's working pretty good thus far (rolling distros FTW!). Otherwise it's pretty much incompatible with Linux Mint and Elementary OS due to them being based on the older, outdated Ubuntu 14.04 LTS release along with the newer Ubuntu 16.04 LTS release.
Ubuntu 17.04 does work fine regardless of the outdated libxcb1 warning. Actually, it works on Linux Mint too regardless of the warnings.
-
It's based on Ubuntu, which is based on Debian. But yeah, it's generally out-of-date as it uses Ubuntu 16.04 LTS as a base. I'm sure it'll change next year with 18.04 LTS. It also happens on Ubuntu 17.04 too with just one lib, so I guess that's an improvement. :P I'll likely switch back from Mint to Ubuntu at some point - really wanted to wait until 17.10 came out, but maybe I should give the Ubuntu daily alpha builds a go? Anyways...
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.
Fixed both issues in a new build.
It's in the repo, about to upload it to the beta location too..
-
Fixed both issues in a new build.
It's in the repo, about to upload it to the beta location too..
Groovy! Yeah, no more errors in Arch Linux (reversed the symlinks). I'll test Ubuntu 17.04 here in a few minutes to verify the error there is gone too. If so, I'll likely replace Linux Mint 18.2 with Ubuntu 17.10 once the final beta is released (and nuke Linux Mint in the meantime).
EDIT: Yep, no more lib error on Ubuntu 17.04, nice! I'll edit the tutorial soon recommending Linux Mint 18.2 and below, Elementary OS 0.4.1 and below, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS users to either stick with 23.0.28 64-bit or install the 32-bit version of MC.
-
Ubuntu 17.04 does work fine regardless of the outdated libxcb1 warning. Actually, it works on Linux Mint too regardless of the warnings.
As long as its the same major versions thats usually the case (it wouldn't start if it were different majors), but its hard to tell if there might be subtle bugs down the road from mismatches.
Considering we don't use any fancy new features of those library (in fact we used to build against older ones just last week), its probably going to be fine.
-
Yeah, that's true. But the package manager (Synaptic) flags MC as being a broken package and wants to remove it, so ignoring the error(s) may not be an easy option there. Probably easier just to install the i386 build.
-
Confirmed on TW, installs, runs fine now without the *icu dependency msgs.
I am somewhat concerned about the compatibility of the AMD64 build with non-debian distros.
Yeah, I get that, but MC on TW is so very boring-ly stable and performant (at least with audio). ;)
Too bad you guys couldn't leverage the Suse OBS somehow...
-
Could you guys give 23.0.36 a whirl?
-
Testing TheatreView on X and XWayland (Plasma5 DM, Mesa 17.1.6) on TW (single monitor). Seems good on both so far, ESC key not available on XWayland (Plasma issue, most likely) and on first use of TheaterView, the top menu bar doesn't show up until choosing a item and than going back. Otherwise, seemingly normal for Audio playback, changing zones, etc. No crashes yet.
I recv'd a "pkg not signed" error on install, but I think that might be a recent TW upgrade thing.
-
23.0.28 will work fine, but 31-2 and 36 will request GLIBCXX_3.4.21 and Others.
Then,Installing gcc 6.4 and making it correspond to GLIBCXX_ 3.4.21 will result in "segmentation fault".
23.0.28 also works under the GLIBCXX_3.4.21 environment. Do you still need a missing package?
-
What Linux distro are you using? 31-2 and 36 have newer lib dependencies.
-
What Linux distro are you using? 31-2 and 36 have newer lib dependencies.
RHEL base OS.
Regards,
-
RHEL base OS.
Regards,
ldd /usr/bin/mediacenter23
linux-vdso.so.1 => (0x00007fffabfd8000)
libcryptlib.so => /usr/lib/jriver/Media Center 23/libcryptlib.so (0x00007f0b42665000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0b42417000)
librt.so.1 => /lib64/librt.so.1 (0x00007f0b4220f000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f0b4200b000)
libboost_regex.so.1.59.0 => /usr/lib/jriver/Media Center 23/libboost_regex.so.1.59.0 (0x00007f0b41d28000)
libX11.so.6 => /lib64/libX11.so.6 (0x00007f0b419ea000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f0b417e5000)
libGL.so.1 => /lib64/libGL.so.1 (0x00007f0b41574000)
libXrandr.so.2 => /lib64/libXrandr.so.2 (0x00007f0b4136a000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f0b40fea000)
libm.so.6 => /lib64/libm.so.6 (0x00007f0b40ce7000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f0b40ad1000)
libc.so.6 => /lib64/libc.so.6 (0x00007f0b40710000)
/lib64/ld-linux-x86-64.so.2 (0x00007f0b4480c000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x00007f0b404ed000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f0b402c3000)
libxcb-dri3.so.0 => /lib64/libxcb-dri3.so.0 (0x00007f0b400c0000)
libxcb-present.so.0 => /lib64/libxcb-present.so.0 (0x00007f0b3febc000)
libxcb-randr.so.0 => /lib64/libxcb-randr.so.0 (0x00007f0b3fcae000)
libxcb-xfixes.so.0 => /lib64/libxcb-xfixes.so.0 (0x00007f0b3faa6000)
libxcb-render.so.0 => /lib64/libxcb-render.so.0 (0x00007f0b3f89b000)
libxcb-shape.so.0 => /lib64/libxcb-shape.so.0 (0x00007f0b3f697000)
libxcb-sync.so.1 => /lib64/libxcb-sync.so.1 (0x00007f0b3f490000)
libxshmfence.so.1 => /lib64/libxshmfence.so.1 (0x00007f0b3f28c000)
libglapi.so.0 => /lib64/libglapi.so.0 (0x00007f0b3f05d000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f0b3ee36000)
libXext.so.6 => /lib64/libXext.so.6 (0x00007f0b3ec23000)
libXdamage.so.1 => /lib64/libXdamage.so.1 (0x00007f0b3ea20000)
libXfixes.so.3 => /lib64/libXfixes.so.3 (0x00007f0b3e81a000)
libX11-xcb.so.1 => /lib64/libX11-xcb.so.1 (0x00007f0b3e617000)
libxcb-glx.so.0 => /lib64/libxcb-glx.so.0 (0x00007f0b3e3fd000)
libxcb-dri2.so.0 => /lib64/libxcb-dri2.so.0 (0x00007f0b3e1f8000)
libXxf86vm.so.1 => /lib64/libXxf86vm.so.1 (0x00007f0b3dff1000)
libdrm.so.2 => /lib64/libdrm.so.2 (0x00007f0b3dde2000)
libXrender.so.1 => /lib64/libXrender.so.1 (0x00007f0b3dbd8000)
libXau.so.6 => /lib64/libXau.so.6 (0x00007f0b3d9d3000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f0b3d772000)
-
Honestly? You'd probably have much better luck using MC with a Debian based OS, since everything besides Debian itself is considered unsupported. RHEL (or RHEL based) likely is pushing the limits where MC can work at.
Might even have better luck with Fedora too, since there's a tutorial for that.
Media Center 23.0.31-2 and above have increased lib version requirements, matching the recently released Debian Stretch. It sounds like the RHEL based OS is possibly using older libs so it's possible you won't be able to get it to work without switching OSes. Another example of this is, Media Center 23.0.31-2 and above won't install/work correctly anymore on Ubuntu 16.04 LTS or Linux Mint 18.2 (the package manager freaks out wanting to remove MC23) due to it requiring newer libs. At least that's until there's a new Ubuntu LTS update next year (which Mint too can base itself off of).
-
RHEL has a rather long lifecycle, the current version is originally from 2014, and the way those work, they don't really update software in it besides security fixes, so running something build for a distribution from 2017 is probably hard.
You can run the 32-bit version probably, which is our fallback for older systems.
-
I'm wondering if we should drop the AMD64 build back to Jessie.
As you say, it doesn't run on Ubuntu 16.04 either which is supposedly a long term release. The Stretch build will also not run on the QNAP.
It's not like we are going to get any new features out of using GCC 6 while the arm and i386 builds are still on 4.9.
-
IMO, have both but keep the Stretch build around labeled as an experimental build that is updated once-in-a-blue-moon (and has to be manually installed)?
Ubuntu LTS (along with Mint, elementary, etc.) will catch up once 18.04 LTS is released in around 7 months.
-
QNAP will not even run on 4.9 IIRC, and going back to 4.8 would really be painful. I don't really want to be tied to a severely old compiler for compatibility with some closed ecosystem.
-
QNAP will not even run on 4.9 IIRC, and going back to 4.8 would really be painful. I don't really want to be tied to a severely old compiler for compatibility with some closed ecosystem.
Yeah, looks like you are right, it's dependent on libstdc++-4.8
I think that's for boost though. I could build it without boost and see what else breaks...
As for maintaining 2 AMD64 builds, ugh. We spend too much time making builds already. It slows down other projects...
-
Well, could keep thing as-is then and keep/recommend the i386 build for compatibility with systems running older libs? But the last time I tried using the i386 build on an AMD64 system a few weeks back the build would instantly segfault every time on start on Linux Mint (all i386 dependencies were satisfied). I'll have to play with that more in a VM once I get more time.
-
Using Jessie as a base would generally be fine, since as you say yourself the other builds are based on that still - and we have to work on the lowest common denominator (and thats already quite an improvement from wheezy). But after all the work to get every platform on C++11, I would hate for Linux-amd64 to go back to 4.8, though (which only has incomplete C++11 support).
-
Using Jessie as a base would generally be fine, since as you say yourself the other builds are based on that still - and we have to work on the lowest common denominator (and thats already quite an improvement from wheezy). But after all the work to get every platform on C++11, I would hate for Linux-amd64 to go back to 4.8, though (which only has incomplete C++11 support).
Well it was cool that GCC 6 exposed those "bugs"...
I'm a bit hesitant to go back to Jessie for AMD64 since I updated my dev box to Stretch.
-
Hey bob, mattkhan and I are seeing some bugs related to streaming video formats to linux clients from windows servers over in this thread:
https://yabb.jriver.com/interact/index.php/topic,111976.0.html
Just wanted to make sure you'd seen it since (after I opened the thread) we appear to have isolated the issue to linux clients only
-
I think that's for boost though. I could build it without boost and see what else breaks...
Now that you said that, we only use boost for regex, but if we had C++11 everywhere, we could use C++11 built-in regex functionality, and get rid of boost entirely. :)
Its practically the same syntax as well, since the boost stuff was basically moved into the C++ library.
Something for my list, i guess.
-
Let me know when the 64-bit Stretch build lands in the stable repo. I'll rewrite the tutorial recommending users of Ubuntu 16.04 LTS, Linux Mint 18.x, etc. to use the i386 build.
-
Let me know when the 64-bit Stretch build lands in the stable repo. I'll rewrite the tutorial recommending users of Ubuntu 16.04 LTS, Linux Mint 18.x, etc. to use the i386 build.
I'm still up in the air whether or not to keep the amd64 build in Stretch. Been discussing this with Hendrik.
-
23.0.51
Unfortunately, I get empty (white), unresponsive window sometimes. What should I do for proper report?
vst seems to works!
but some plugins crashes MC and when open DSP studio after restart, only way to revert - delete lines with bad plugin in "Machine Settings.ini"
-
What distro are you using? What's your GPU? Are you using the open source or proprietary drivers for your GPU? What plug-ins are you using which causes the issues?
That should help narrow the problem down somewhat.
-
What distro are you using? What's your GPU? Are you using the open source or proprietary drivers for your GPU? What plug-ins are you using which causes the issues?
That should help narrow the problem down somewhat.
openSUSE Tumbleweed, I can give list of necessary libs
NVIDIA with blob
I'haven' any such issues with MC before (be honest, it runs fine about hour now).
If we talk about crashing against vst, i say - that's normal :) every app do that. But that apps has some protection, in simple words: it looks in logs regarding does loading last vst *.so cause crash or not, i guess
-
Any example VST plug-ins which always crash?
-
well, it was old version of https://www.overtonedsp.co.uk/download/download_rvb500/ which crashes JUCE hosts as well
recent version works fine
if you mind - I can upload "bad" file
But, really, it will be pretty to implement plugin protection.
-
The new "outfit" of the action window, especially the tag window, I find not helpful. It takes up too much space. There is not enough space to display the remaining MC window.
when I edit (highlight) a field in the tag editor, this field appears on all workspaces! Until now, it only appeared on the workspace, on which MC was also open.
-
well, it was old version of https://www.overtonedsp.co.uk/download/download_rvb500/ which crashes JUCE hosts as well
recent version works fine
if you mind - I can upload "bad" file
But, really, it will be pretty to implement plugin protection.
A lot of the VST plugins seems to me to be really poorly implemented on linux.
There is an issue as well with the platform the plugin is developed on and the libraries they are linked to. This is the disadvantage for developers trying to make VST plugins work on linux as opposed to windows.
-
The new "outfit" of the action window, especially the tag window, I find not helpful. It takes up too much space. There is not enough space to display the remaining MC window.
when I edit (highlight) a field in the tag editor, this field appears on all workspaces! Until now, it only appeared on the workspace, on which MC was also open.
You can get back the old tag window behavior if you hold down the shift key when you select tag from the right click menu.
The edit tag window behavior is not new though I never noticed it before. It's a side effect of the type of window being created (unmanaged). I'll look into it...
-
Hey Bob, looking forward to the tutorial to install the AMD64 Beta! Will I be able to install it over the stable 23.0.21 version? I apologize as my newbie Linux skills do not extend to installing 23.0.51 from a .deb file. I can run it from terminal but there is a library dependency problem with Ubuntu 17.0.4. BTW 23.0.51 fixes the DSP window issue : )
-
To fix the dependency issue, just run sudo apt-get install -f in a Terminal. Otherwise 23.0.51 should work fine in Ubuntu 17.04 and above. If you're using 16.04 LTS, it won't work.
-
Forgive my newbiness... how do you install the new 23.0.51 properly? A double click brings up an installer but the Install button does nothing.
-
To fix the dependency issue, just run sudo apt-get install -f in a Terminal. Otherwise 23.0.51 should work fine in Ubuntu 17.04 and above. If you're using 16.04 LTS, it won't work.
Bob,
I tried: sudo apt-get install MediaCenter-23.0.51-amd64.deb -f. It doesn't work for 17.04. Here is what i get after opening a terminal in the folder where I have the MC deb file:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package MediaCenter-23.0.51-amd64.deb
E: Couldn't find any package by glob 'MediaCenter-23.0.51-amd64.deb'
E: Couldn't find any package by regex 'MediaCenter-23.0.51-amd64.deb'
louis@Gort:~/Downloads$
-
I think you need to add the path to the .deb file for it to be found. If you don't know the path just right click the .deb file and copy the path. You DID download it didn't you? : )
-
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.
-
Do this from the Terminal (skip the first step if you've already downloaded the .deb file)...
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)...
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...
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!
-
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:
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:~$
-
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;
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. ;)
-
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.
-
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. :P
-
Isnt the point of using "-f" to ignore dependency issues? It should still run regardless.
-
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.
-
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.
-
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?
-
Right-clicking a playlist item in a list causes MC 20.0.54 to hang for a minute before continuing. Using Ubuntu 17.04.
-
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).
-
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?
-
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.
-
Yes, music is on a Windows SMB share. Problem does not show up when using remote control.
Which remote?
Is the share mounted??
-
Which remote?
Is the share mounted??
Any MC remote I've tried: Tremote and iPhone. Share is mounted from Windows SMB drive on network
-
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?
-
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 :(
-
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.
-
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
-
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)
-
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..
-
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.
-
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
-
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
-
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.
-
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
-
That doesn't show a mount.
It shows a samba resource.
Your file browser is querying the resource, it's not mounting it.
-
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!
-
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!
-
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
-
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
-
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!
-
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:
//hillwrk/f /mnt/media cifs noauto,x-systemd.automount,credentials=/home/mitchell/samba-credentials 0 0Confirmed that something is there after:
sudo mkdir /mnt/mediaDetails:
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)
-
Seem to be having newbie problems with creating a mounting point. Here is my fstab line:
//hillwrk/f /mnt/media cifs noauto,x-systemd.automount,credentials=/home/mitchell/samba-credentials 0 0Confirmed that something is there after:
sudo mkdir /mnt/mediaDetails:
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"?
-
A diagnostic step: what does the terminal say if you run "sudo mount /mnt/media"?
Results:
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
-
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"
-
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:
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)
-
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.
-
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:
//10.20.40.80/f /home/mitchell/Media cifs noauto,x-systemd.automount,credentials=/home/mitchell/samba-credentials 0 0Thanks for the help. This is a very useful forum.
-
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.
-
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!