Hallo
Yesterday i got the link for installation of qlcplus on Pi
i have prepared the SD Card according to the PDF Instruction.
but its not starting qlcplus.
I am using Pi B
HDMI Monitor connected to HDMI Port
LAN Connection for Internet
USB Mouse and Key Board
I am getting the following error message:
sudo qlcplus
qt.qpa.screen: QXcbConnection: Could not connect to display
Could not connect to any X display.
I have visited all these links, followed the suggested
editing of the config file but still its not working.
viewtopic.php?f=7&t=13854
viewtopic.php?f=7&t=13940
viewtopic.php?f=7&t=14093
viewtopic.php?f=7&t=14006
can any body please help me?
pi not starting with qlcplus
- mcallegari
- Posts: 4807
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Hi, are you using the full provided image or have you just installed the Debian package?
- mcallegari
- Posts: 4807
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
the right command to launch QLC+ on the official image is
Code: Select all
sudo service qlcplus start
-
- Posts: 42
- Joined: Mon Jan 06, 2020 2:40 am
- Real Name: Mr Mike
My setup is a bit different, so I'm not sure how much help I'll be, but a few things to try:
Open up a command line/terminal window and run It should hopefully come back with something like ":0" or "localhost:0", or maybe "localhost:10.0"
I'm assuming you are already using a GUI interface on your Pi, so the command above should show you something. Another thing to try would be to run qlcplus manually, without using 'sudo' before it.
I have to imagine that with this failure being so early in the program execution, adding the "-d 3 --log" flags with running qlcplus won't help at all. But if you get past this current error, it could be helpful if you're still seeing problems.
FYI, my setup is a headless (no mouse/keyboard/display) Pi 2B running a manually complied QLC+ using VNC so I can access the GUI remotely. As part of the VNC server startup, it automatically executes
Open up a command line/terminal window and run
Code: Select all
echo $DISPLAY
I'm assuming you are already using a GUI interface on your Pi, so the command above should show you something. Another thing to try would be to run qlcplus manually, without using 'sudo' before it.
I have to imagine that with this failure being so early in the program execution, adding the "-d 3 --log" flags with running qlcplus won't help at all. But if you get past this current error, it could be helpful if you're still seeing problems.
FYI, my setup is a headless (no mouse/keyboard/display) Pi 2B running a manually complied QLC+ using VNC so I can access the GUI remotely. As part of the VNC server startup, it automatically executes
Code: Select all
qlcplus -f resize --nowm --open $HOME/my_workspace.qxw -d 3 --log
-
- Posts: 8
- Joined: Fri Apr 24, 2020 6:25 am
- Real Name: Santanu
Hi all,
Thanks for your prompt reply. I still haven't been able to root cause the issue. But I made a few observations:
Thanks for all your help,
Stay safe!
Santanu
Thanks for your prompt reply. I still haven't been able to root cause the issue. But I made a few observations:
- I tested the image qlcplus_raspbian_buster_20190825.7z on my friend's RPI 4, and it worked seamlessly. However, the same process fails on my RPI 1 Model B. Thus, this might be an issue with older PI hardware.
- After Pi boots, I ran the following command:
, and it generates the following output:
Code: Select all
sudo service qlcplus status
Code: Select all
● qlcplus.service - LSB: Q Light Controller Plus Loaded: loaded (/etc/init.d/qlcplus; generated) Active: active (exited) since Sun 2020-05-17 03:08:08 BST; 21min ago Docs: man:systemd-sysv-generator(8) Process: 293 ExecStart=/etc/init.d/qlcplus start (code=exited, status=0/SUCCESS) May 17 03:08:05 raspberrypi systemd[1]: Starting LSB: Q Light Controller Plus... May 17 03:08:07 raspberrypi qlcplus[293]: Starting Q Light Controller Plus: qlcplus. May 17 03:08:08 raspberrypi systemd[1]: Started LSB: Q Light Controller Plus.
- Even if I run , nothing happens.
Code: Select all
sudo service qlcplus start
produces no output either.Code: Select all
ps aux | grep qlcplus
- I further tried setting , and then launching qlcplus manually, but still get the error
Code: Select all
export DISPLAY=:0
Code: Select all
qt.qpa.screen: QXcbConnection: Could not connect to display :0 Could not connect to any X display.
Thanks for all your help,
Stay safe!
Santanu
-
- Posts: 6
- Joined: Mon Apr 27, 2020 7:21 pm
- Real Name: Sander
Hi Sanatu,
qlcplus should be starting automatically as already mentioned. As per the manual for the RPi image there is not X server included in the image:
Powered by Qt 5.11.3 directly running on OpenGL for fast 2D rendering of the User Interface. Xorg is not present in the image.
So you cannot start the qlcplus binary directly like you do. You could try adding --log to the QLCPLUS_OPTS in the /etc/init.d/qlcplus file and see if some clue shows up in /root/QLC+.log.
Is your RPi getting an IP address? Because qlcplus starts default with the web interface enabled I can imagine it has trouble starting without an IP for the system.
What does the command journalctl say?
qlcplus should be starting automatically as already mentioned. As per the manual for the RPi image there is not X server included in the image:
Powered by Qt 5.11.3 directly running on OpenGL for fast 2D rendering of the User Interface. Xorg is not present in the image.
So you cannot start the qlcplus binary directly like you do. You could try adding --log to the QLCPLUS_OPTS in the /etc/init.d/qlcplus file and see if some clue shows up in /root/QLC+.log.
Is your RPi getting an IP address? Because qlcplus starts default with the web interface enabled I can imagine it has trouble starting without an IP for the system.
What does the command journalctl say?
-
- Posts: 1
- Joined: Sat Jan 30, 2021 3:29 pm
- Real Name: Johan O Rauchfuss
I have the same problem.
Web interface works perfect.
I have only tried the newest firmware.
Web interface works perfect.
I have only tried the newest firmware.
- mcallegari
- Posts: 4807
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Guys, Pi 1 model is quite old now and I'm not sure if it even makes sense to support it furthermore.
There might be issues with the graphics stack, since there's been a lot of development going to access the GPU from standard Mesa packages.
I have one myself but I don't have much chance to do tests. At the moment I have major network issues that I can't solve. Will be solved in a couple of months, when I move (again) to a new house.
There might be issues with the graphics stack, since there's been a lot of development going to access the GPU from standard Mesa packages.
I have one myself but I don't have much chance to do tests. At the moment I have major network issues that I can't solve. Will be solved in a couple of months, when I move (again) to a new house.