Author Topic: Screensaver issues  (Read 1042 times)

F1forHELP

  • Regular Poster
  • **
  • Posts: 40
    • View Profile
Screensaver issues
« on: January 01, 2017, 11:36:50 pm »
This happened to me with 12.04, and the behavior is consistent with 14.04.

Build a fresh core using LMCE-1404-20161119175532-i386.iso.  Log in via ssh and update everything.  When the orbiter times out, I am shown pictures as you would expect.

Create disk less image successfully.

My first orbiter created from the image displays a clock for a screen saver.  Three subsequent media directors added to the system display pictures not a clock.

Looking in the web-admin under files & media / screensaver the path is listed as /home/public/data/pictures/flickr/ and the flikr script is active.  (It would have to be for the server and two other orbiters)  Under advanced / configuration / devices and looking in the tree under Generic PC as MD / Onscreen Orbiter / Photo screen saver the configuration is identical among the four listed orbiters.

All of these computers are using the U1 basic interface.

Thoughts, suggestions for troubleshooting?

phenigma

  • LinuxMCE God
  • ****
  • Posts: 1719
    • View Profile
Re: Screensaver issues
« Reply #1 on: January 01, 2017, 11:40:11 pm »
Sounds like the photo screen saver program may not be running or have an error.  Check the logs on that MD.

Sent from my Nexus 5 using Tapatalk


F1forHELP

  • Regular Poster
  • **
  • Posts: 40
    • View Profile
Re: Screensaver issues
« Reply #2 on: January 02, 2017, 05:57:08 pm »
Looking in /var/log/pluto/56_LaunchPhoto_Screen_Saver.sh.log I found

Cannot init the video mode! (Couldn't find matching GLX visual)

followed by multiple entries similar to below

Failed to load '/home/public/data/pictures/flickr/2017/01/01/31917161801.jpg'

Check the file to make sure it exists from the director

ll /home/public/data/pictures/flickr/2017/01/01/31917161801.jpg
-rw-r--r-- 1 root root 175768 Jan  1 20:22 /home/public/data/pictures/flickr/2017/01/01/31917161801.jpg

Looking at my other media directors I do not have a LaunchPhoto_Screen_Saver log

Checking the installed video (from lspci)

00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2)

Installed nvidia software

dpkg -l | grep nvid
ii  nvidia-352                                  367.57-0ubuntu0.14.04.1                                          i386         Transitional package for nvidia-367
ii  nvidia-367                                  367.57-0ubuntu0.14.04.1                                          i386         NVIDIA binary driver - version 367.57
ii  nvidia-opencl-icd-367                       367.57-0ubuntu0.14.04.1                                          i386         NVIDIA OpenCL ICD
ii  nvidia-prime                                0.6.2.1                                                          i386         Tools to enable NVIDIA's Prime
ii  nvidia-settings                             331.20-0ubuntu8                                                  i386         Tool for configuring the NVIDIA graphics driver

Recommendations on resolving the video mode / GLX issue?

phenigma

  • LinuxMCE God
  • ****
  • Posts: 1719
    • View Profile
Re: Screensaver issues
« Reply #3 on: January 11, 2017, 09:20:07 pm »
You could try re-installing the video driver and ensure the appropriate libraries are installed.  Is this UI1 or UI2?  It looks like it's trying to start the GL screensaver (requiring libgl1-mesa-glx or the appropriate version for the hardware enablement stack on your system, you can check /etc/pluto.conf for the current version).

F1forHELP

  • Regular Poster
  • **
  • Posts: 40
    • View Profile
Re: Screensaver issues
« Reply #4 on: January 23, 2017, 04:09:25 am »
Thanks for pointing me in the correct direction.

The installed video card is an
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2)

The nvidia-352 driver was installed by default.

Once I loaded the nvidia-304 (correct for this generation of older hardware) driver and rebooted, the photo screen saver started working.

Issue resolved.