Touch plugin V1.1.7 installation problem

This post is a split from the “Touch/Hyperpixel” post, as the two issues appear unrelated, so this issue has been moved to a separate post.

Below are the results of the tests you asked for.

=====

Result of “X -version” is:

X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.26-v7+ armv7l Raspbian
Current Operating System: Linux volumio_sunroom 4.19.86-v7+ #1283 SMP Fri Nov 29 18:32:25 GMT 2019 armv7l
Kernel command line: coherent_pool=1M 8250.nr_uarts=0 bcm2708_fb.fbwidth=800 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 splash quiet plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 console=ttyS0,115200 kgdboc=ttyS0,115200 console=tty1 imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh elevator=noop rootwait bootdelay=5 logo.nologo vt.global_cursor_default=0 loglevel=0
Build Date: 11 November 2016 11:59:59AM
xorg-server 2:1.18.4-2+rpi1 (debian.org/support)
Current version of pixman: 0.32.6
Before reporting problems, check wiki.x.org
to make sure that you have the latest version.

=====

Result of “chromium-browser -version” is:

/usr/bin/chromium-browser: line 138: lsb_release: command not found
/usr/bin/chromium-browser: line 139: lsb_release: command not found
Inconsistency detected by ld.so: dl-lookup.c: 871: _dl_setup_hash: Assertion `(bitmask_nwords & (bitmask_nwords - 1)) == 0’ failed!

[NOTE: get same lack of lsb_release report on the working system, but do not get the INCONSISTENCY error, so that third error line appears to
be important]

Next is result of “sudo journalctl -f” starting with plugin running, then stopping plugin, then starting it again.
I have added comment lines at about the points where I think I stopped/started the plugin, but I may be wrong sorry if
that is the case.

THIS BIT IS WHILE PLUGIN IS STILL RUNNING::::::
– Logs begin at Thu 2020-03-12 14:06:18 UTC. –
Mar 13 07:27:22 volumio_sunroom systemd[28013]: Starting Basic System.
Mar 13 07:27:22 volumio_sunroom systemd[28013]: Reached target Basic System.
Mar 13 07:27:22 volumio_sunroom systemd[28013]: Starting Default.
Mar 13 07:27:22 volumio_sunroom systemd[28013]: Reached target Default.
Mar 13 07:27:22 volumio_sunroom systemd[28013]: Startup finished in 28ms.
Mar 13 07:27:22 volumio_sunroom systemd[1]: Started User Manager for UID 1000.
Mar 13 07:27:22 volumio_sunroom sshd[26230]: lastlog_openseek: Couldn’t stat /var/log/lastlog: No such file or directory
Mar 13 07:27:22 volumio_sunroom sshd[26230]: lastlog_openseek: Couldn’t stat /var/log/lastlog: No such file or directory
Mar 13 07:33:08 volumio_sunroom sudo[9293]: volumio : TTY=pts/0 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/journalctl -f
Mar 13 07:33:08 volumio_sunroom sudo[9293]: pam_unix(sudo:session): session opened for user root by volumio(uid=0)

THINK THIS IS WHERE I STOPPED PLUGIN (or may be nearer to 07:34) :::::

Mar 13 07:33:52 volumio_sunroom sudo[19317]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0
Mar 13 07:33:52 volumio_sunroom sudo[19317]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 07:33:52 volumio_sunroom sudo[19323]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0
Mar 13 07:33:52 volumio_sunroom sudo[19317]: pam_unix(sudo:session): session closed for user root
Mar 13 07:33:52 volumio_sunroom sudo[19323]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 07:33:52 volumio_sunroom sudo[19323]: pam_unix(sudo:session): session closed for user root
Mar 13 07:33:53 volumio_sunroom volumio[955]: info: CoreCommandRouter::volumioGetVisibleSources
Mar 13 07:33:53 volumio_sunroom volumio[955]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources
Mar 13 07:33:53 volumio_sunroom volumio[955]: info: CoreCommandRouter::volumioGetState
Mar 13 07:33:53 volumio_sunroom volumio[955]: info: CoreStateMachine::getState
Mar 13 07:33:53 volumio_sunroom volumio[955]: info: CorePlayQueue::getTrack 0
Mar 13 07:33:53 volumio_sunroom sudo[19569]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0
Mar 13 07:33:53 volumio_sunroom volumio[955]: info: CoreCommandRouter::executeOnPlugin: appearance , getUiSettings
Mar 13 07:33:53 volumio_sunroom volumio[955]: info: CoreCommandRouter::executeOnPlugin: mpd , getConfigParam
Mar 13 07:33:53 volumio_sunroom sudo[19569]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 07:33:53 volumio_sunroom volumio[955]: info: CoreCommandRouter::executeOnPlugin: wizard , getShowWizard
Mar 13 07:33:53 volumio_sunroom volumio[955]: info: CoreCommandRouter::executeOnPlugin: system , getShowWizard
Mar 13 07:33:54 volumio_sunroom sudo[19569]: pam_unix(sudo:session): session closed for user root
Mar 13 07:33:54 volumio_sunroom volumio[955]: info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom
Mar 13 07:33:54 volumio_sunroom sudo[19594]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0
Mar 13 07:33:54 volumio_sunroom volumio[955]: info: Listing playlists
Mar 13 07:33:54 volumio_sunroom sudo[19594]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 07:33:54 volumio_sunroom sudo[19594]: pam_unix(sudo:session): session closed for user root
Mar 13 07:33:54 volumio_sunroom volumio[955]: info: CoreCommandRouter::executeOnPlugin: my_volumio , getMyVolumioStatus
Mar 13 07:34:07 volumio_sunroom volumio[955]: info: Un-/commenting gpu_mem settings in /boot/config.txt.
Mar 13 07:34:07 volumio_sunroom volumio[955]: info: Using /boot/config.txt instead of /boot/userconfig.txt.
Mar 13 07:34:07 volumio_sunroom volumio[955]: info: Disabling plugin touch_display
Mar 13 07:34:07 volumio_sunroom volumio[955]: info: Done.
Mar 13 07:34:07 volumio_sunroom sudo[22744]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl stop volumio-kiosk.service
Mar 13 07:34:07 volumio_sunroom sudo[22744]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 07:34:07 volumio_sunroom systemd[1]: Stopping Volumio Kiosk…
Mar 13 07:34:07 volumio_sunroom startx[11513]: xinit: connection to X server lost
Mar 13 07:34:07 volumio_sunroom pulseaudio[11657]: PulseAudio information vanished from X11!
Mar 13 07:34:07 volumio_sunroom bluetoothd[784]: Endpoint unregistered: sender=:1.23 path=/MediaEndpoint/A2DPSource
Mar 13 07:34:07 volumio_sunroom bluetoothd[784]: Endpoint unregistered: sender=:1.23 path=/MediaEndpoint/A2DPSink
Mar 13 07:34:08 volumio_sunroom sudo[22737]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/sed -i -e /Option “TransformationMatrix”/d /etc/X11/xorg.conf.d/95-touch_display-plugin.conf
Mar 13 07:34:08 volumio_sunroom sudo[22737]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 07:34:08 volumio_sunroom sudo[22737]: pam_unix(sudo:session): session closed for user root
Mar 13 07:34:08 volumio_sunroom startx[11513]: waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
Mar 13 07:34:08 volumio_sunroom volumio[955]: info: Touchscreen transformation matrix removed.
Mar 13 07:34:08 volumio_sunroom sudo[22770]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/sed -i -e /Identifier “Touch rotation”/a\ Option “TransformationMatrix” “undefined” /etc/X11/xorg.conf.d/95-touch_display-plugin.conf
Mar 13 07:34:08 volumio_sunroom sudo[22770]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 07:34:08 volumio_sunroom sudo[22770]: pam_unix(sudo:session): session closed for user root
Mar 13 07:34:08 volumio_sunroom volumio[955]: info: Touchscreen transformation matrix written.
Mar 13 07:34:08 volumio_sunroom startx[11513]: xinit: unexpected signal 15
Mar 13 07:34:09 volumio_sunroom systemd[1]: volumio-kiosk.service: main process exited, code=exited, status=1/FAILURE
Mar 13 07:34:09 volumio_sunroom systemd[1]: Stopped Volumio Kiosk.
Mar 13 07:34:09 volumio_sunroom systemd[1]: Unit volumio-kiosk.service entered failed state.
Mar 13 07:34:09 volumio_sunroom sudo[22744]: pam_unix(sudo:session): session closed for user root
Mar 13 07:34:09 volumio_sunroom volumio[955]: info: systemctl stop volumio-kiosk.service succeeded.
Mar 13 07:34:09 volumio_sunroom volumio[955]: info: Volumio Kiosk stopped

THEN I THINK THIS IS WHERE I STARTED PLUGIN AGAIN:::::

Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Enabling plugin touch_display
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Loading plugin “touch_display”…
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Applying required configuration parameters for plugin touch_display
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: PLUGIN START: touch_display
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Loading i18n strings for locale en
Mar 13 07:34:33 volumio_sunroom sudo[22850]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl daemon-reload
Mar 13 07:34:33 volumio_sunroom sudo[22850]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 07:34:33 volumio_sunroom systemd[1]: Reloading.
Mar 13 07:34:33 volumio_sunroom systemd[1]: [/lib/systemd/system/mpd.service:18] Unknown lvalue ‘ProtectKernelTunables’ in section ‘Service’
Mar 13 07:34:33 volumio_sunroom systemd[1]: [/lib/systemd/system/mpd.service:19] Unknown lvalue ‘ProtectControlGroups’ in section ‘Service’
Mar 13 07:34:33 volumio_sunroom systemd[1]: [/lib/systemd/system/mpd.service:20] Unknown lvalue ‘ProtectKernelModules’ in section ‘Service’
Mar 13 07:34:33 volumio_sunroom systemd[1]: [/lib/systemd/system/mpd.service:23] Unknown lvalue ‘RestrictNamespaces’ in section ‘Service’
Mar 13 07:34:33 volumio_sunroom sudo[22850]: pam_unix(sudo:session): session closed for user root
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: systemctl daemon-reload succeeded.
Mar 13 07:34:33 volumio_sunroom sudo[22870]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl start volumio-kiosk.service
Mar 13 07:34:33 volumio_sunroom sudo[22870]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 07:34:33 volumio_sunroom systemd[1]: Starting Volumio Kiosk…
Mar 13 07:34:33 volumio_sunroom systemd[1]: Started Volumio Kiosk.
Mar 13 07:34:33 volumio_sunroom startx[22875]: X.Org X Server 1.18.4
Mar 13 07:34:33 volumio_sunroom startx[22875]: Release Date: 2016-07-19
Mar 13 07:34:33 volumio_sunroom startx[22875]: X Protocol Version 11, Revision 0
Mar 13 07:34:33 volumio_sunroom startx[22875]: Build Operating System: Linux 4.4.26-v7+ armv7l Raspbian
Mar 13 07:34:33 volumio_sunroom startx[22875]: Current Operating System: Linux volumio_sunroom 4.19.86-v7+ #1283 SMP Fri Nov 29 18:32:25 GMT 2019 armv7l
Mar 13 07:34:33 volumio_sunroom startx[22875]: Kernel command line: coherent_pool=1M 8250.nr_uarts=0 bcm2708_fb.fbwidth=800 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 splash quiet plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 console=ttyS0,115200 kgdboc=ttyS0,115200 console=tty1 imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh elevator=noop rootwait bootdelay=5 logo.nologo vt.global_cursor_default=0 loglevel=0
Mar 13 07:34:33 volumio_sunroom startx[22875]: Build Date: 11 November 2016 11:59:59AM
Mar 13 07:34:33 volumio_sunroom startx[22875]: xorg-server 2:1.18.4-2+rpi1 (debian.org/support)
Mar 13 07:34:33 volumio_sunroom startx[22875]: Current version of pixman: 0.32.6
Mar 13 07:34:33 volumio_sunroom startx[22875]: Before reporting problems, check wiki.x.org
Mar 13 07:34:33 volumio_sunroom startx[22875]: to make sure that you have the latest version.
Mar 13 07:34:33 volumio_sunroom startx[22875]: Markers: (–) probed, (**) from config file, (==) default setting,
Mar 13 07:34:33 volumio_sunroom startx[22875]: (++) from command line, (!!) notice, (II) informational,
Mar 13 07:34:33 volumio_sunroom startx[22875]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Mar 13 07:34:33 volumio_sunroom startx[22875]: (==) Log file: “/var/log/Xorg.0.log”, Time: Fri Mar 13 07:34:33 2020
Mar 13 07:34:33 volumio_sunroom startx[22875]: (==) Using config directory: “/etc/X11/xorg.conf.d”
Mar 13 07:34:33 volumio_sunroom startx[22875]: (==) Using system config directory “/usr/share/X11/xorg.conf.d”
Mar 13 07:34:33 volumio_sunroom startx[22875]: modprobe: FATAL: Module g2d_23 not found.
Mar 13 07:34:33 volumio_sunroom sudo[22870]: pam_unix(sudo:session): session closed for user root
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: systemctl start volumio-kiosk.service succeeded.
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Volumio Kiosk started
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: CoreCommandRouter::volumioGetState
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: CoreStateMachine::getState
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: CorePlayQueue::getTrack 0
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Done.
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Raspberry Pi Foundation touch screen detected.
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Using /boot/config.txt instead of /boot/userconfig.txt.
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Un-/commenting gpu_mem settings in /boot/config.txt.
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Backlight module of a Raspberry Pi Foundation touch screen detected.
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Using Xorg socket /tmp/.X11-unix/X0
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: CoreCommandRouter::volumioGetState
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: CoreStateMachine::getState
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: CorePlayQueue::getTrack 0
Mar 13 07:34:33 volumio_sunroom sudo[22916]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0
Mar 13 07:34:33 volumio_sunroom sudo[22916]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 07:34:33 volumio_sunroom sudo[22916]: pam_unix(sudo:session): session closed for user root
Mar 13 07:34:33 volumio_sunroom sudo[22914]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/sed -i -e /Option “TransformationMatrix”/d /etc/X11/xorg.conf.d/95-touch_display-plugin.conf
Mar 13 07:34:33 volumio_sunroom sudo[22914]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 13 07:34:33 volumio_sunroom sudo[22914]: pam_unix(sudo:session): session closed for user root
Mar 13 07:34:33 volumio_sunroom volumio[955]: info: Touchscreen transformation matrix removed.
Mar 13 07:34:34 volumio_sunroom volumio[955]: info: Setting screensaver timeout to 120 seconds.
Mar 13 07:34:34 volumio_sunroom pulseaudio[23055]: Stale PID file, overwriting.
Mar 13 07:34:34 volumio_sunroom pulseaudio[23055]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
Mar 13 07:34:34 volumio_sunroom pulseaudio[23055]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
Mar 13 07:34:34 volumio_sunroom pulseaudio[23055]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method “GetProperties” with signature “” on interface “org.bluez.Manager” doesn’t exist
Mar 13 07:34:34 volumio_sunroom bluetoothd[784]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource
Mar 13 07:34:34 volumio_sunroom bluetoothd[784]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink

Just to make the history of this thread traceable: The conversation began here https://forum.volumio.org/touch-using-plugin-and-pimoroni-hyperpixel-touchscreen-t14117.html#p73429.

Yes, I had also been suspecting that chromium-browser is not working properly after you posted the results of “systemctl -l status volumio-kiosk”. Maybe this can be solved by reinstalling the plugin.

P.S.: The first to lines of the result of chromium-browser -version (saying “lsb_release: command not found”) look the same on my system, but after that - in the third line - I get a valid result with version 57.x (if I remember correctly).

I think I have already tried uninstalling then reinstalling the plugin.

Did that by going to : “Installed Plugins”
Then click “Uninstall” against the “Touch Display 1.1.7”

This uninstalled the plugin but took no time (showed a very brief progress bar of several seconds only, so I guess it did not uninstall any packages that were downloaded.

So I guess my next question is how do I FULLY uninstall the plugin, so that the next install goes through a full install and dependency download?

Also should I powercycle/reboot between uninstall and install steps?

I can wipe the SD card and start from a fresh 2.714 image if you want, but am happy to continue with trying to debug my system while it is in this state if it is of use to you.

Just done an “uninstall” - shutdown - “reinstall” - shutdown

The same INCONSISTENCY error persists.

During the UNINSTALL that took only a few seconds to install.
During the INSTALL that was far faster that the original install (that stalled at about 70% for a few minutes while packages were downloaded).
The reinstall listed a number of LGN steps (when selecting the more info tab in the install progress display) where some translation items were downloaded, but there was no long delay to download other packages.

So I guess some manual SSH package update is going to be necessary.

I am fairly sure that the problem system started as a fresh SD image of 2.714. If it was not, then it could have been from a 2-3 month old version. But only other plugins that may have been installed then uninstalled was the Snapcast one. But I thought that I had used that briefly only on a different RaspPi board.

You are right, uninstalling does not remove the packages, but I had hoped that the following installation would complete possibly missing packages.

I think you should try to reinstall the whole system. Make sure to wait long enough after the first boot (https://volumio.github.io/docs/User_Manual/Quick_Start_Guide) before you start using Volumio and especially before installing the plugin.

Success. Do not understand what could have gone wrong the previous time, either I had upgraded Volumio version to V2.714 from an older version, or had used and removed Shoutcast some time in past.

I think that during the progress reporting that I saw Chrome being downloaded and installed twice, as though there was a circular dependency, as the download was in the middle of two separate numbered sequences of download steps. Not sure if the version being installed was the same, or if Chrome had been updated and there may be a newer version found after installing an initial version request.

@gvolt thanks for the help, sorry that I appear to have wasted your time, and should have just tried to install from scratch. I must have been mistaken on the history of the SD card I was using, as I guess I could not have started from a fresh V2.714 and must have gotten there by some other route.

=====

For anyone interested,this is as best as I can remember the steps I took to get Touch plugin working on V2.714:

Using Win10 laptop and Win32DiskImager. RaspPi3B and RaspPi 7Inch display Version2 or higher.

Erased/formatted SD card
Downloaded Volumio V2.714
Burnt to SD card
First powerup - Waited for Volumio Hotspot
Setup FIRST TIME SETTINGS and WiFi access+password
Wait for reboot, closing browser and connecting back to home WiFi.
Access the Volumio target.
Test play NAS audio file.
Access Plugins
Select Touch plugin V1.1.7 and install.
Watched progress bar and detailed info output.
Gets to 70% then does a lot of downloading and LGN steps.
After many minutes it completes.
Accept prompts and wait for system.

Display eventually shows UI, but at this point it is upside down.
Change settings for plugin to rotate 180Degrees.
Set brightness to 127.
Prevent screen timeout while a track is playing.
Do system reboot.

All appears to be working fine.

Glad it works :slight_smile:

After a month of fault free operation, I had a problem with the Touch Screen plugin. I was playing a NAS track and wanted to pause playback, so pressed the PAUSE button on the PI GUI. But rather than pausing the playback, the GUI crashed out displaying the LOGIN prompt.

I then accessed the remote GUI from an Android device and paused the playback.

Then selected SHUTDOWN from the menu option and waited.
Then power cycled after the PI had shutdown.
The PI starts up but the Touchscreen GUI remains BLACK.

At this point I decided to try uninstall and reinstall but this did not fix the problem.

So I removed the SD card.
Erased/Formatted back to 16GB blank device.
Reflashed 2.714 from my previously saved IMG.
Went through the basic setup to get back to a headless volumio installation.
Then rebooted.
Then installed the Touch Screen plugin V 1.1.7.
Then enabled it.
Once that had finished, I left the default settings and did a shutdown then power cycle.

The PI started fine, except the screen was upside down and brightness at maximum (as expected from default settings).

I can not recall the exact order of changes or points where I did I a reboot request, but was along the lines:

Went to the setting page for the plug in,
Rotated display to 180 (selected continue rather than reboot). Clicked SAVE.
Changed timeout from 120 to 60 seconds. Clicked SAVE.
Set brightness to 127. Clicked SAVE.

Then requested reboot.
After PI had finished startup, the display was again BLACK. But the touch screen and timeout and brightness settings all appear to be working, as I can see the backlight turn on for the 60 seconds, but the display remains BLACK.

This appears to be the same failure mode that I originally encountered about a month ago.

Last time the solution was to reflash and reinstall the software. That is what I did just now, but the problem remains.

It would suggest that there is a critical sequence or some issue with the installation and changing of settings which is causing the black screen.

I know that last time the problem was resolved by a reinstall, but as that is what I just did I think it indicates that there is actually a flaw somewhere in the installation process.

I will at some point do another reflash/install, but before I do is there anything that you would like to try and capture from my system while it is in this state.

Hi Revell,

I have never experienced a crash as you described. Since you were able to connect to the GUI from another device I suspect a problem with chromium which might have been crashed.

Is this happening with an original Raspberry Touchscreen?

Do you see any error messages from the GUI when you enabled the plugin now?

After the plugin has started please execute systemctl status -l volumio-kiosk.service and post the result.

When I got the crash, a track was playing, GUI visible, and I tried to touch the PAUSE button, not sure if I accurately touched it, or possibly touched the very top of the screen. The GUI then disappeared, and was replaced by a black screen showing the LOGIN prompt, suggesting that the browser crashed or quit, (or probably unlikely switched to the login prompt as if the browser had been minimized, don’t think that’s possible on a command line).

The PI is a PI3+, display is a version 2 PI touchscreen, have two identical sets of hardware which have been working fine with Volumio 2.714 + Touch 1.1.7. (Also have headless PI Zero).

For the BLACK SCREEN unit, the output from “systemctl” is:

volumio@sunroom:~$ systemctl status -l volumio-kiosk.service
● volumio-kiosk.service - Volumio Kiosk
Loaded: loaded (/lib/systemd/system/volumio-kiosk.service; disabled)
Active: active (running) since Thu 2020-05-21 10:18:52 UTC; 5h 18min ago
Main PID: 1084 (startx)
CGroup: /system.slice/volumio-kiosk.service
├─ 1084 /bin/sh /usr/bin/startx /etc/X11/Xsession /opt/volumiokiosk.sh – -nocursor
├─ 1109 xinit /etc/X11/Xsession /opt/volumiokiosk.sh – /usr/bin/X :0 -nocursor -auth /tmp/serverauth.mntHWYEoO4
├─ 1110 /usr/lib/xorg/Xorg :0 -nocursor -auth /tmp/serverauth.mntHWYEoO4
├─ 1257 /bin/bash /opt/volumiokiosk.sh
├─ 1276 /usr/bin/ssh-agent /opt/volumiokiosk.sh
├─ 1281 /usr/bin/openbox --startup /usr/lib/arm-linux-gnueabihf/openbox-autostart OPENBOX
├─ 1339 /usr/bin/xbindkeys -f /etc/xbindkeysrc
├─ 1347 /usr/bin/pulseaudio --start
├─ 1400 /bin/sh /usr/bin/start-pulseaudio-x11
├─ 1401 /usr/bin/xprop -root -spy
└─30657 /usr/lib/chromium-browser/chromium-browser --enable-pinch --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --disable-pinch --kiosk --no-first-run --disable-3d-apis --disable-breakpad --disable-crash-reporter --disable-infobars --disable-session-crashed-bubble --disable-translate --user-data-dir=/data/volumiokiosk --no-sandbox localhost:3000

May 21 10:18:52 sunroom startx[1084]: Markers: (–) probed, (**) from config file, (==) default setting,
May 21 10:18:52 sunroom startx[1084]: (++) from command line, (!!) notice, (II) informational,
May 21 10:18:52 sunroom startx[1084]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
May 21 10:18:52 sunroom startx[1084]: (==) Log file: “/var/log/Xorg.0.log”, Time: Thu May 21 10:18:52 2020
May 21 10:18:52 sunroom startx[1084]: (==) Using config directory: “/etc/X11/xorg.conf.d”
May 21 10:18:52 sunroom startx[1084]: (==) Using system config directory “/usr/share/X11/xorg.conf.d”
May 21 10:18:52 sunroom startx[1084]: modprobe: FATAL: Module g2d_23 not found.
May 21 10:18:59 sunroom pulseaudio[1347]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
May 21 10:18:59 sunroom pulseaudio[1347]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
May 21 10:18:59 sunroom pulseaudio[1347]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method “GetProperties” with signature “” on interface “org.bluez.Manager” doesn’t exist
volumio@sunroom:~$

If I compare the log with that from my other PI that is still working, that unit gives:

volumio@volumio_bedroom:~$ systemctl status -l volumio-kiosk.service
● volumio-kiosk.service - Volumio Kiosk
Loaded: loaded (/lib/systemd/system/volumio-kiosk.service; disabled)
Active: active (running) since Thu 2020-05-21 15:56:28 UTC; 2min 3s ago
Main PID: 1075 (startx)
CGroup: /system.slice/volumio-kiosk.service
├─1075 /bin/sh /usr/bin/startx /etc/X11/Xsession /opt/volumiokiosk.sh – -nocursor
├─1099 xinit /etc/X11/Xsession /opt/volumiokiosk.sh – /usr/bin/X :0 -nocursor -auth /tmp/serverauth.5ocEv54P0V
├─1100 /usr/lib/xorg/Xorg :0 -nocursor -auth /tmp/serverauth.5ocEv54P0V
├─1204 /bin/bash /opt/volumiokiosk.sh
├─1253 /usr/bin/ssh-agent /opt/volumiokiosk.sh
├─1258 /usr/bin/openbox --startup /usr/lib/arm-linux-gnueabihf/openbox-autostart OPENBOX
├─1259 /usr/lib/chromium-browser/chromium-browser --enable-pinch --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --disable-pinch --kiosk --no-first-run --disable-3d-apis --disable-breakpad --disable-crash-reporter --disable-infobars --disable-session-crashed-bubble --disable-translate --user-data-dir=/data/volumiokiosk --no-sandbox localhost:3000
├─1289 /usr/bin/xbindkeys -f /etc/xbindkeysrc
├─1293 /usr/bin/pulseaudio --start
├─1302 /bin/sh /usr/bin/start-pulseaudio-x11
├─1303 /usr/bin/xprop -root -spy
├─1305 /usr/lib/chromium-browser/chromium-browser --type=zygote --no-sandbox --user-data-dir=/data/volumiokiosk --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so
└─1369 /usr/lib/chromium-browser/chromium-browser --type=renderer --disable-3d-apis --disable-breakpad --disable-pinch --enable-pinch --no-sandbox --enable-features=AutofillCreditCardSigninPromo<AutofillCreditCardSigninPromo,AutofillProfileCleanup<AutofillProfileCleanup,DocumentWriteEvaluator<DisallowFetchForDocWrittenScriptsInMainFrame,ExpectCTReporting<ExpectCTReporting,IncidentReportingDisableUpload<SafeBrowsingIncidentReportingService,IncidentReportingModuleLoadAnalysis<SafeBrowsingIncidentReportingServiceFeatures,IncidentReportingSuspiciousModuleReporting<SafeBrowsingIncidentReportingServiceFeatures,MaterialDesignUserManager<MaterialDesignUserManager,NegotiateTLS13<TLS13Negotiation,NetworkTimeServiceQuerying<NetworkTimeQueries,NewAudio

May 21 15:56:28 volumio_bedroom startx[1075]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
May 21 15:56:28 volumio_bedroom startx[1075]: (==) Log file: “/var/log/Xorg.0.log”, Time: Thu May 21 15:56:28 2020
May 21 15:56:28 volumio_bedroom startx[1075]: (==) Using config directory: “/etc/X11/xorg.conf.d”
May 21 15:56:28 volumio_bedroom startx[1075]: (==) Using system config directory “/usr/share/X11/xorg.conf.d”
May 21 15:56:28 volumio_bedroom startx[1075]: modprobe: FATAL: Module g2d_23 not found.
May 21 15:56:33 volumio_bedroom startx[1075]: waiting for X server to begin accepting connections modprobe: FATAL: Module g2d_23 not found.
May 21 15:56:34 volumio_bedroom startx[1075]: .
May 21 15:56:36 volumio_bedroom pulseaudio[1293]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
May 21 15:56:36 volumio_bedroom pulseaudio[1293]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
May 21 15:56:36 volumio_bedroom pulseaudio[1293]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method “GetProperties” with signature “” on interface “org.bluez.Manager” doesn’t exist
volumio@volumio_bedroom:~$

The output is almost identical except towards the end the order of some items are swapped, but probably more significant are the 2 EXTRA chromium-browser entries (I assume these are threads) which are missing from the problem unit.

Like on your working system I have three chromium threads, too. Atm I don’t have an idea what could have caused the crash… I have tapped on my touchscreen like mad and at high speed, also toggling between pausing and playing to see if this would lead to a crash - but nothing (luckily).

For the moment I suggest to try stopping the plugin, then removing the content of /data/volumiokiosk with sudo rm -rf /data/volumiokiosk/* and restarting the plugin to rule out corrupted files causing trouble. You may also check if /data/volumiokiosk is owned by volumio user (not root).

I tried deleting the directory contents, but got no further.
So gave up and have re-flashed, setup initial config,then installed the plugin.

This time I was sitting next to the PI while doing the setup.

After the initial plugin install, I enabled the plugin at the prompt that comes up after the install.
I got the display on the PI showing the GUI and as last time it was upside down.

So then went to the plugin settings and rotated the screen to 180 degrees then selected the reboot option and waited. (So far all GUI interactions being done via remote browser).

Once the reboot completed I then got a popup notification on the PI display from Chromium informing me that the profile was already in use,with option to UNLOCK or NOT.

Last time I did not see this popup (as I was not looking at the PI at this point but was looking at the remote browser waiting for re connection, so probably missed this popup, and then continued with remotely changing the timeout and brightness then reboot).

But this time as I saw the popup I selected the UNLOCK option, then continued to set brightness and timeout before doing another reboot. Following that reboot, the PI display was the correct way up, and timeout and brightness were as I had set, and have so far not had a profile locked popup.

So my guess is that possibly Chromium has been updated in past few months and has this profile lock behaviour (as I did not see that popup several months ago when I installed the plugin on my two PI3’s).

I am not sure how versions are controlled, or if Chromium will get the latest version in Rasbrian regardless of the versions of Volumio and plugin.

So fingers crossed I now have two working PI’s again.

Thanks for you attempts to fault find, not sure what/how the locked profile is controlled by Chromium or if there is a diagnostic step that can be added to the plugin launcher script to unlock this condition, but it also makes me question if chromium is writing data to the SD card, as far as I was aware, Volumio tries to limit SD card writes to the minimum to save the card,and also I assume protect against sudden power removal corrupting the SD card, I wonder if that could have been in any way related to my unexpected crash that caused the problem a few days ago, as obviously the browser crash left something broken on the SD card, but the break could have occurred any time in the past few months as the PI had been running continuously all that time without power down or reboot.

As a side note, (this thread is not the correct place to put it, but while you are looking),

I do find it a little frustrating when touching the screen to bring the PI out of screen saver mode, that I have to be careful of where I press as the press appears to get passed to Volumio as is the screen was already awake, so I often find that I cause the PI to do something I was not intending.

Is there a way of discarding the first screen press (or possibly first second or so of finger activity) so that the initial activity only wakes the screen, then the user has to un-touch the screen before any action gets accepted.

I am guessing that as Chromium is passing the activity and is unaware of the sleep state of the screen, that dropping/filtering the activity is less than straight forward and not something that the plugin can easily achieve.

Thanks for reporting back.

To me the profile locking situation did never occur. But if I spot it correctly you have changed the hostname of your system. There has been a bug report that this leads to a profile lock. Could this happened here, too?

Could you please post your chromium version to check if it differs from mine?

I am on it already. :wink: But yes, it seems to be not an easy solution - at least if you try to do it with already present tools. And I strongly aim to avoid dragging in more and more dependencies, making the plugin more and more “heavy”…

I did change the name from the default VOLUMIO during the initial installation of Volumio before installing the plugin, so I guess that may explain that. Though I had not seen the profile lock on the other times I installed on the two PI’s, think I changed the names prior to installing the plugin, during the initial 7 step setup for Volumio.

Chromium version reported by:

chromium-browser --version:

56.0.2924.84 Built on Ubuntu 14.04

Hm, I would not expect a profile lock if the plugin was installed after the system’s name had already been changed… Do you have any other plugins or additional packages installed that could be related to chromium or X?

Have you possibly been able to grab a concrete error message from the logs from the chromium “popup”?

P.S. Chromium version is the same here.

No sorry, have no error message/log, as have reinstalled from scratch, so any log on SD card have now gone.
Do not understand what I could have done that would have been different from anyone else installing the touch plugin from scratch.

I have no other plugins and hardware is basic PI3+ and PI 7" version 2 display. No other hardware, no USB devices,just WIFI network, no Ethernet, no HDMI just 3.5mm audio plug to self powered speakers.