RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Dialog Boxes contain x's and q"s instead of shading

    Scheduled Pinned Locked Moved Help and Support
    dialog box x q
    44 Posts 8 Posters 6.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      brunozero @mitu
      last edited by

      @mitu said in Dialog Boxes contain x's and q"s instead of shading:

      Raspbian

      I'm sorry I'm noob, just a regular user who noticed the error, has this error been with the hardware? is there any solution for him or his cause?

      mituM 1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator @brunozero
        last edited by

        @brunozero You can use @Efriim's solution to reconfiure your language/locale and choose an ISO-8859-1 locale.

        1 Reply Last reply Reply Quote 0
        • mituM
          mitu Global Moderator
          last edited by mitu

          OK, found the culprit - it's the raspi-config update from Jan 2019 that changes the auto-login service (https://github.com/RPi-Distro/raspi-config/commit/d33487cbeac581d2ce91d8372f5feb1e2b5b7e3a).
          TL;DR version - when configuring the auto-login (via raspi-config), the $TERM variable is replaced with the value from the current running session and added to the auto-login config file, instead of being added literally as $TERM in the auto-login configuration file.

          So, if I ran raspi-config from a SSH session, my $TERM is xterm-256color - this gets added to the auto-login session, but the Linux terminal doesn't have the same capabilities (should be $TERM=linux).
          This does not happen if you run raspi-config from the console, via the keyboard.

          H B 2 Replies Last reply Reply Quote 1
          • H
            hhromic @mitu
            last edited by

            @mitu that's a great debugging job, very good catch. I can confirm indeed this is happening. In my case $TERM got expanded to linux so I never noticed. Indeed this is a bug and good to see you already posted an issue on the Foundation's GitHub. Very well done.

            1 Reply Last reply Reply Quote 0
            • B
              brunozero @mitu
              last edited by

              @mitu thanks for solving, but how do I apply the correction? I opened the link and got a lot of lines of code :(, unfortunately I do not know how to do this

              mituM 1 Reply Last reply Reply Quote 0
              • A
                Aqualime
                last edited by

                I installed a clean 4.4 image and performed a full update. Obviously the same issue as above. I just wanted to make sure the error we are getting is related to the messy text in the setup menu. I'm not sure I understood.

                Exception OSError: (9, 'Bad file descriptor') in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored
                
                mituM 1 Reply Last reply Reply Quote 0
                • mituM
                  mitu Global Moderator @brunozero
                  last edited by

                  @brunozero You'll have to edit the /etc/systemd/system/getty@tty1.service.d/autologin.conf file and replace - on the 3nd line:

                  ExecStart=-/sbin/agetty --autologin pi --noclear %I xterm-256color
                  

                  with

                  ExecStart=-/sbin/agetty --autologin pi --noclear %I $TERM
                  

                  then reboot.

                  B 1 Reply Last reply Reply Quote 1
                  • mituM
                    mitu Global Moderator @Aqualime
                    last edited by

                    @Aqualime For the 2nd error you reported, there is a fix pending, when it will be accepted to the RetroPie-Setup repository you'll only have to update the script.

                    1 Reply Last reply Reply Quote 1
                    • B
                      brunozero @mitu
                      last edited by brunozero

                      @mitu Thanks a lot, I already turned off the rpb but before turning off I updated the script and apparently the error problem stopped, but tomorrow I confirm, if I still continue I run your solution, thank you very much

                      1 Reply Last reply Reply Quote 0
                      • LolonoisL
                        Lolonois
                        last edited by

                        FWIW the Issue is pending in raspi-config

                        https://github.com/RPi-Distro/raspi-config/issues/88

                        1 Reply Last reply Reply Quote 0
                        • mituM
                          mitu Global Moderator
                          last edited by

                          Well, the issue got fixed in the raspi-config repository, so the next raspi-config release should make the problem go away.

                          1 Reply Last reply Reply Quote 2
                          • First post
                            Last post

                          Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                          Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.