Nearly Running on Raspberry Pi / RetroPie / Debian Jessie #327

Open
opened 2016-12-27 05:02:31 +01:00 by wmodes · 9 comments
wmodes commented 2016-12-27 05:02:31 +01:00 (Migrated from github.com)

Thank you for your instructions for installing on Debian Jessie. It allowed me to compile it, but now I don't know enough to take the next step.

I'm trying to get cool-retro-term to work on RetroPie for text games.

To start, I installed the deps:

$ sudo apt-get install build-essential qmlscene qt5-qmake qt5-default qtdeclarative5-dev qml-module-qtquick-controls qml-module-qtgraphicaleffects qml-module-qtquick-dialogs qml-module-qtquick-localstorage qml-module-qtquick-window2

In order to compile it without memory errors, I needed to increase my swapfile size. But then I was good to go. Though it took a while, it compiled successfully.

$ git clone --recursive https://github.com/Swordfish90/cool-retro-term.git
$ cd cool-retro-term
$ qmake && make

But when I run it, I get an error.

$ ./cool-retro-term
QXcbConnection: Could not connect to display

There are gaps in my understanding around X-windows requirements. What am I missing?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40413478-nearly-running-on-raspberry-pi-retropie-debian-jessie?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github).
Thank you for your instructions for installing on Debian Jessie. It allowed me to compile it, but now I don't know enough to take the next step. I'm trying to get cool-retro-term to work on RetroPie for text games. To start, I installed the deps: $ sudo apt-get install build-essential qmlscene qt5-qmake qt5-default qtdeclarative5-dev qml-module-qtquick-controls qml-module-qtgraphicaleffects qml-module-qtquick-dialogs qml-module-qtquick-localstorage qml-module-qtquick-window2 In order to compile it without memory errors, I needed to increase my swapfile size. But then I was good to go. Though it took a while, it compiled successfully. $ git clone --recursive https://github.com/Swordfish90/cool-retro-term.git $ cd cool-retro-term $ qmake && make But when I run it, I get an error. $ ./cool-retro-term QXcbConnection: Could not connect to display There are gaps in my understanding around X-windows requirements. What am I missing? <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40413478-nearly-running-on-raspberry-pi-retropie-debian-jessie?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github). </bountysource-plugin>
tomchiverton commented 2017-01-05 19:52:39 +01:00 (Migrated from github.com)

I don't know how RetroPie works - does it run as an X app, or just take over drawing the whole display in place of X ? CRT requires an X server...

I don't know how RetroPie works - does it run as an X app, or just take over drawing the whole display in place of X ? CRT requires an X server...
wmodes commented 2017-03-27 02:54:36 +02:00 (Migrated from github.com)

@tomchiverton Definitely a question for those who are more X and video savvy. Sorry.

@tomchiverton Definitely a question for those who are more X and video savvy. Sorry.
tomchiverton commented 2017-03-28 20:04:42 +02:00 (Migrated from github.com)

Is your shell session an SSH connection to the computer ? Or is it an on-screen, on-device terminal ?

Is your shell session an SSH connection to the computer ? Or is it an on-screen, on-device terminal ?
wmodes commented 2017-03-29 00:08:51 +02:00 (Migrated from github.com)

I am ssh'd in but running video in the console's xterm.

--
Wes Modes
http://modes.io

Sent from my Apple ][e

On Mar 28, 2017, at 11:04 AM, Tom Chiverton notifications@github.com wrote:

Is your shell session an SSH connection to the computer ? Or is it an on-screen, on-device terminal ?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I am ssh'd in but running video in the console's xterm. -- Wes Modes http://modes.io Sent from my Apple ][e > On Mar 28, 2017, at 11:04 AM, Tom Chiverton <notifications@github.com> wrote: > > Is your shell session an SSH connection to the computer ? Or is it an on-screen, on-device terminal ? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. >
dburongarcia commented 2017-04-26 00:49:04 +02:00 (Migrated from github.com)

Did you manage to get it working? I am surprised that there is such a little information about using CRT with the Raspberry Pi... I hope you made it.

Did you manage to get it working? I am surprised that there is such a little information about using CRT with the Raspberry Pi... I hope you made it.
dburongarcia commented 2017-09-03 13:47:18 +02:00 (Migrated from github.com)

Hi, if anyone is interested, after many different tries I found that the best way to use CRT with RPi is using ArchLinuxARM and http://www.chaos-reins.com/qpi/ Its creator, Donald Carr supplied more info for CRT in https://www.youtube.com/watch?v=NVUPV3yJv04 It works great, very fast. There are only problems with menus (as many other users are experiencing)

Hi, if anyone is interested, after many different tries I found that the best way to use CRT with RPi is using ArchLinuxARM and http://www.chaos-reins.com/qpi/ Its creator, Donald Carr supplied more info for CRT in https://www.youtube.com/watch?v=NVUPV3yJv04 It works great, very fast. There are only problems with menus (as many other users are experiencing)
pascalandy commented 2017-10-28 18:37:03 +02:00 (Migrated from github.com)

Same issue when trying it within a Docker container:

docker run -dit ubuntu:16.04;
docker exec -it e2b205592884 bash;

apt-get update && \
apt-get upgrade && \
apt-get install -qqy \
git build-essential qmlscene qt5-qmake qt5-default qtdeclarative5-dev \
qml-module-qtquick-controls qtdeclarative5-qtquick2-plugin libqt5qml-graphicaleffects \
qml-module-qtquick-dialogs qtdeclarative5-localstorage-plugin qtdeclarative5-window-plugin;

# Get it from GitHub
git clone --recursive https://github.com/Swordfish90/cool-retro-term.git && \

# Build it
cd cool-retro-term && \

# Compile (Fedora and OpenSUSE user should use qmake-qt5 instead of qmake)
qmake && make && \

# Have fun!
./cool-retro-term
Same issue when trying it within a Docker container: ``` docker run -dit ubuntu:16.04; docker exec -it e2b205592884 bash; apt-get update && \ apt-get upgrade && \ apt-get install -qqy \ git build-essential qmlscene qt5-qmake qt5-default qtdeclarative5-dev \ qml-module-qtquick-controls qtdeclarative5-qtquick2-plugin libqt5qml-graphicaleffects \ qml-module-qtquick-dialogs qtdeclarative5-localstorage-plugin qtdeclarative5-window-plugin; # Get it from GitHub git clone --recursive https://github.com/Swordfish90/cool-retro-term.git && \ # Build it cd cool-retro-term && \ # Compile (Fedora and OpenSUSE user should use qmake-qt5 instead of qmake) qmake && make && \ # Have fun! ./cool-retro-term ```
ways commented 2017-10-28 21:41:41 +02:00 (Migrated from github.com)

@wmodes

But when I run it, I get an error.

$ ./cool-retro-term
QXcbConnection: Could not connect to display

Try
$ DISPLAY=:0 ./cool-retro-term

@wmodes > But when I run it, I get an error. > $ ./cool-retro-term > QXcbConnection: Could not connect to display Try $ DISPLAY=:0 ./cool-retro-term
dayne commented 2019-07-09 03:28:16 +02:00 (Migrated from github.com)

This issue should be considered resolved/closed as core issue was due to @wmodes being SSH'ed into the system without a valid DISPLAY target set to launch it on the Pi's running X server.

Likely it would have worked fine if it been launched from an X session terminal on the Pi or like @ways described by manually setting DISPLAY=:0 ./cool-retro-term (assuming Xauth stuff allowed it).

This issue should be considered resolved/closed as core issue was due to @wmodes being SSH'ed into the system without a valid `DISPLAY` target set to launch it on the Pi's running X server. Likely it would have worked fine if it been launched from an X session terminal on the Pi or like @ways described by manually setting `DISPLAY=:0 ./cool-retro-term` (assuming Xauth stuff allowed it).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#327
No description provided.