repetier-touch-screen-display-do-not-show-up-after-boot

i have a printer with Repetier installed with raspberry pi board and 7” touch display , recently i updated the pi board in it and now it doesn’t boot up in Repetier touch ui. I don’t know how to fix it. Reflashing card is not an option.

Comments

  • Run sudo raspi-config and select as boot option console with autologin and it will work after next reboot. Updating seems to reset that selection all the time. For next image I will try a different start option.
  • Ok i get some workarounds now when i restart printer touchscreen comes with a white screen written requested file not found, then if i press alt+F4 the app starts. How to get rid of that white screen 
  • Check file

     /home/pi/.config/openbox/autostart 

    to contain this:

    # Uncomment the following 3 commands to have display always on
    #xset s off         # don't activate screensaver
    #xset -dpms         # disable DPMS (Energy Star) features.
    #xset s noblank     # don't blank the video device
    rm /home/pi/.config/chromium/SingletonLock
    chromium-browser  --app-auto-launched --disable-pinch --incognito --noerrdialogs --disable-suggestions-service --disable-translate --disable-save-password-bubble --disable-session-crashed-bubble --disable-infobars --touch-events=disabled --disable-gesture-typing --kiosk --app=http://127.0.0.1:3344/modules/front2/app/app.html

    That is the best start method I know surpressing all error dialogs which I want to use on next image. You can use

    nano  /home/pi/.config/openbox/autostart 

    to edit the file.
  • ok i did as you suggest
     situation before apply- system boots up and after some time a white seen appears with 'Requested file not found' then i have to press Alt+F4 to get the touch user interface
     situation after apply-system boots up and after some time a white seen appears with 'Requested file not found' then i press Alt+F4 to get the touch user interface but again the same white screen appears and next time when i press Alt+F4 a black screen comes forever.

    Possible Reason-
    you suggested=
    # Uncomment the following 3 commands to have display always on
    #xset s off         # don't activate screensaver
    #xset -dpms         # disable DPMS (Energy Star) features.
    #xset s noblank     # don't blank the video device
    rm /home/pi/.config/chromium/SingletonLock
    chromium-browser  --app-auto-launched --disable-pinch --incognito --noerrdialogs --disable-suggestions-service --disable-translate --disable-save-password-bubble --disable-session-crashed-bubble --disable-infobars --touch-events=disabled --disable-gesture-typing --kiosk --app=http://127.0.0.1:3344/modules/front2/app/app.html

    but in official site https://www.repetier-server.com/booting-into-touchscreen-mode-for-linux/ =
    # Uncomment the following 3 commands to have display always on
    #xset s off         # don't activate screensaver
    #xset -dpms         # disable DPMS (Energy Star) features.
    #xset s noblank     # don't blank the video device
    
    chromium-browser --noerrdialogs --disable-suggestions-service --disable-translate 
    --disable-save-password-bubble --disable-session-crashed-bubble --disable-infobars 
    --touch-events=enabled --disable-gesture-typing 
    --kiosk http://127.0.0.1:3344/modules/front2/www/app.html
    
    have highlighted the differences
    
    What should i do next
  • http://127.0.0.1:3344/modules/front2/www/app.html is the old link that changed with 0.91.x to app/app.html. Server will automatically forward the old url to the new one.

    Something in chromium is stored causing the problem so I'd say delete the chromium settings and restart.
    rm -rf /home/pi/.config/chromium
    and restart.

    This is assuming the server is running correctly. If the server is not started, the error is correct and changes to chromium do not help. So what is with regular access with pc browser to http://serverip:3344 - does that work? If not please check /var/lib/Repetier-Server/logs/server.log to see until where it comes to get an idea why starting fails.
Sign In or Register to comment.