I have the official 7-inch Raspberry Pi Touchscreen connected to a Raspberry Pi 3 Model B Rev 1.2. I’m trying to get the touchscreen to work with RoPieee. I see text on the screen…
*** Welcome to RoPieee! ***
<snip>
... We're ready. RoPieee is RUNNING ...
…but I don’t ever see the Now Playing screen.
I’ve read through some relevant threads[0][1][2], but haven’t been able to resolve the issue yet.
The initial install, and subsequent reinstalls, were performed with the screen attached.
I made sure the Zone name, “RoPieee Office”, matches the Roon Control Zone in the Display tab.
I enabled the Extension in Roon.
I reseated the ribbon cable between the Pi and the display.
I haven’t been getting voltage errors, but I went ahead and tried powering both the display and the RPi with two USB cables.
I’ve used Etcher to reflash the latest stable build of ropieee five times so far.
I’ve tried two different microsd cards.
I’ve restarted the Roon Server (running on Ubuntu) and rebooted the RoPieee on multiple occasions.
I tried unplugging the green and yellow cables that go between the the RPi and the touchscreen.
The RoPieee is connected to an Ethernet cable, and I reserved an IP address for the device via my router.
I submitted feedback (Identifier: eaef19d361bb4bb7), but have reflashed that microsd card since then.
I just submitted another feedback (Identifier: 265a96fef923fb77), after flashing a brand new microsd card. Something I just noticed was a core-dump for the ropieee-touchui service…
I ran # journalctl -xe, and noticed the following…
<snip>
Mar 17 00:02:52 ropieee-office systemd[1]: ropieee-touchui.service: Service RestartSec=10s expired, scheduling restart.
Mar 17 00:02:52 ropieee-office systemd[1]: ropieee-touchui.service: Scheduled restart job, restart counter is at 39.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Automatic restarting of the unit ropieee-touchui.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Mar 17 00:02:52 ropieee-office systemd[1]: Stopped Ropieee Touchscreen UI.
-- Subject: A stop job for unit ropieee-touchui.service has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A stop job for unit ropieee-touchui.service has finished.
--
-- The job identifier is 4355 and the job result is done.
Mar 17 00:02:52 ropieee-office systemd[1]: Starting Ropieee Touchscreen UI...
-- Subject: A start job for unit ropieee-touchui.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit ropieee-touchui.service has begun execution.
--
-- The job identifier is 4355.
Mar 17 00:02:52 ropieee-office ropieee-touchui[5435]: qt.qpa.plugin: Could not load the Qt platform plugin "eglfs" in "" even though it was found.
Mar 17 00:02:52 ropieee-office ropieee-touchui[5435]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc.
Mar 17 00:02:52 ropieee-office systemd[1]: Started Process Core Dump (PID 5436/UID 0).
-- Subject: A start job for unit systemd-coredump@39-5436-0.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit systemd-coredump@39-5436-0.service has finished successfully.
--
-- The job identifier is 4429.
Mar 17 00:02:52 ropieee-office systemd[1]: ropieee-touchui.service: Main process exited, code=dumped, status=6/ABRT
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- An ExecStart= process belonging to unit ropieee-touchui.service has exited.
--
-- The process' exit code is 'dumped' and its exit status is 6.
Mar 17 00:02:52 ropieee-office systemd[1]: ropieee-touchui.service: Failed with result 'core-dump'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit ropieee-touchui.service has entered the 'failed' state with result 'core-dump'.
Mar 17 00:02:52 ropieee-office systemd[1]: Failed to start Ropieee Touchscreen UI.
-- Subject: A start job for unit ropieee-touchui.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit ropieee-touchui.service has finished with a failure.
--
-- The job identifier is 4355 and the job result is failed.
Mar 17 00:02:52 ropieee-office systemd-coredump[5437]: Process 5435 (ropieee-touchui) of user 0 dumped core.
Stack trace of thread 5435:
#0 0x0000000075c94104 raise (libc.so.6)
-- Subject: Process 5435 (ropieee-touchui) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
--
-- Process 5435 (ropieee-touchui) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Mar 17 00:02:52 ropieee-office systemd[1]: systemd-coredump@39-5436-0.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit systemd-coredump@39-5436-0.service has successfully entered the 'dead' state.
This is the first time I’ve tried using the screen (for the RoPieee project). I don’t have any spare Raspberry Pi’s at the moment, but I can order another if need be.
Ugh. I flashed a mircosd card and used a Raspberry Pi 3 B+ instead of the Raspberry Pi 3 B that I had been using earlier. Unfortunately, ropieee-touchui.service is still core-dumping.
I suppose I could buy another touchscreen, but that would be annoying given that I can’t return the one I’m currently using…
