Arch Linux User Repository

-bin variant uploaded https://aur.archlinux.org/packages/logitechmediaserver-bin

I can confirm the failing with Media::Scan as in the end of the logging of @ispotter when compiling on armv6h. At this moment I am clueless as well (even more than @stef.an as I am totally blank on this all). Only know 'new' ffmepg has been installed lately. Kind regards, Martin

Actually I also get this error on arm. The unresolved symbols can be dragged into armv6l-linux-thread-multi/auto/Media/Scan/Scan.so by patching src/slimserver-vendor-7.9.1.arch2/CPAN/buildme.sh: 215c215 < MSOPTS="--with-lms-includes=$BUILD/include" --- > MSOPTS="--with-lms-includes=$BUILD/include --with-lms-libs=$BUILD/lib" But then I fail on the next batch of unresolved symbols, starting with ff_mov_demux. This seems to imply that I need to link in ffmpeg.a.

Hi, you're right... It compiles fine on my arm box but not on x86_64. I'm searching for a solution but currently I'm kind of clueless :(

Hi Stef.an After upgrading to 7.9.1.arch2-1 from 7.9.1.arch1-1 scanning fails with the following: [17-09-11 14:25:56.6496] main::main (331) Error: Failed when running main scan: [Can't locate loadable object for module Media::Scan in @INC (@INC contains: /opt/logitechmediaserver/cache/InstalledPlugins /opt/logitechmediaserver/CPAN/arch/5.26/x86_64-linux-thread-multi /opt/logitechmediaserver/CPAN/arch/5.26/x86_64-linux-thread-multi/auto /opt/logitechmediaserver/CPAN/arch/5.26.0/x86_64-linux-thread-multi /opt/logitechmediaserver/CPAN/arch/5.26.0/x86_64-linux-thread-multi/auto /opt/logitechmediaserver/CPAN/arch/5.26/x86_64-linux-thread-multi /opt/logitechmediaserver/CPAN/arch/5.26/x86_64-linux-thread-multi/auto /opt/logitechmediaserver/CPAN/arch/x86_64-linux-thread-multi /opt/logitechmediaserver/CPAN/arch/5.26 /opt/logitechmediaserver/lib /opt/logitechmediaserver/CPAN /opt/logitechmediaserver /opt/logitechmediaserver /opt/logitechmediaserver/CPAN/arch/5.26/x86_64-linux-thread-multi /opt/logitechmediaserver/CPAN/arch/5.26/x86_64-linux-thread-multi/auto /opt/logitechmediaserver/CPAN/arch/5.26.0/x86_64-linux-thread-multi /opt/logitechmediaserver/CPAN/arch/5.26.0/x86_64-linux-thread-multi/auto /opt/logitechmediaserver/CPAN/arch/x86_64-linux-thread-multi /opt/logitechmediaserver/CPAN/arch/5.26 /opt/logitechmediaserver/lib /opt/logitechmediaserver/CPAN /usr/lib/perl5/5.26/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/5.26/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5/5.26/core_perl /usr/share/perl5/core_perl) at /opt/logitechmediaserver/Slim/Utils/Scanner/LMS.pm line 18. Compilation failed in require at /opt/logitechmediaserver/Slim/Utils/Scanner/LMS.pm line 18. BEGIN failed--compilation aborted at /opt/logitechmediaserver/Slim/Utils/Scanner/LMS.pm line 18. Compilation failed in require at /opt/logitechmediaserver/Slim/Media/MediaFolderScan.pm line 78. ] [17-09-11 14:25:56.6500] main::main (332) Error: Skipping post-process & Not updating lastRescanTime! Reverting to 7.9.1.arch1-1 has fixed it, during build with yaourt I noticed the following: chmod 755 blib/arch/auto/Media/Scan/Scan.so Manifying 1 pod document 1..1 not ok 1 - use Media::Scan; # Failed test 'use Media::Scan;' # at t/01use.t line 3. # Tried to use 'Media::Scan'. # Error: Can't load 'blib/arch/auto/Media/Scan/Scan.so' for module Media::Scan: blib/arch/auto/Media/Scan/Scan.so: undefined symbol: ms_abort at /usr/lib/perl5/5.26/core_perl/DynaLoader.pm line 193. # at t/01use.t line 3. # Compilation failed in require at t/01use.t line 3. # BEGIN failed--compilation aborted at t/01use.t line 3. # Looks like you failed 1 test of 1. make test failed, aborting Looks like the Media::Scan module might not be building properly. Regards Ian

The web interface doesn't load after the latest update. I'm not sure if it's due to a change in dependencies or if this is an upstream problem. I tried uninstalling, updating the system and re-installing. No luck. I even tried building 7.9.0 (using the git commit for this PKGBUILD) and that also did not work. I'm seeing this error in journald even though perl-io-socket-ssl is installed: Async::HTTP: Unable to load IO::Socket::SSL, will try connecting to SSL servers in non-SSL mode I see this error in /opt/logitechmediaserver/Logs/server.log Slim::Networking::IO::Select::__ANON__ (131) Error: Select task failed calling Slim::Web::HTTP::processHTTP: Can't call method "context" on an undefined value at /opt/logitechmediaserver/Slim/Web/Template/SkinManager.pm line 352. ; fh=Slim::Web::HTTP::ClientConn=GLOB(0x9265f88)

Hi Stef.an, many thanks for this hint ! uninstall. upgrade and then re-install did the trick. I was not aware of that procedure, thanks for the heads-up ! cheers, madsepperl

Hi madsepperl, this is not caused by 7.9.1, this version is already prepared for perl 5.26 This is the usual way to handle lms on perl upgrades: - uninstall lms (this leaves your libraray and data intact) - upgrade system - rebuilt and install lms If you're using yaourt, it might handle that for you but I'm not sure about that (yaourt -Syu instead of pacman -Syu).

since 7.9.1 is available, I get the following message on trying to upgrade: "error: failed to prepare transaction (could not satisfy dependencies) :: logitechmediaserver: installing perl (5.26.0-1) breaks dependency 'perl<5.25'" Is there anything I can do ? Or just wait for an upgrade ? Thanks !!

Sorry for my comment yesterday : I needed to recompil all perl modules I got from aur and now it works perfectly !!! Thanks again for all.

I've diagnosed what happened to me (see a couple of posts down). Here are the steps I took: 1. As a sanity check, installed on an x86_64 machine with lots of memory and everything worked as expected. 2. Uninstalled from the armv6h machine and reinstalled, using 'yaourt -S logitechmediaserver'. I noticed somewhere near the end of the build that there was a failure to write to /tmp (because it was 100% full). The build/install process carried on as if nothing was wrong, and zipped up a package and installed it. Trying to start the server gave me the same results as I reported below. 3. I saved the /opt/logitechmediaserver directory off to the side, then uninstalled again, and this time downloaded a snapshot using 'yaourt -G logitechmediaserver' and built locally using 'makepkg -s'. 4. After installing the result of that, everything was in good shape. I did a diff of the "good" logitechmediaserver directory with the "bad" one and noticed many discrepancies. I could report them but I don't think it's all that relevant - the main point is that some users will run out of space in /tmp if they install the way I did in step 2, and end up with a bad install. If there's a solution to this problem it would probably be to fail the build when the write error occurs, instead of packaging up the parts that didn't fail and installing the result. As always, thank you stef.an for all the excellent work.