Thanks for your reaction. I am by no means an expert so I may have the
terminology wrong. I have a stand alone Beagleboard system, keyboard/mouse
connected via usb dongle. The system starts up normally, in grafics mode, I
can invoke internet, no problem, LAN connected. Going to XTerm I get the
linux prompt, still in grafics mode. A simple TKInter test program works.
Going to linux (XTRL/ALT/F1) I can invoke startx that brings me back were I
came from: the grafics environment (LXDE). Starting the TKInter test
program from the Linux prompt gives me the famous error message in the
title. In Xterminal "echo $DISPLAY" renders :1, in plain linux: a blank
line. Starting my application in XTerm gives a fully blank screen.
Still very puzzling.......
I hope you or someone else can bring me further.
On 11 August 2017 at 15:26, Przemek Klosowski <przemek.klosow...@gmail.com>
> On Fri, Aug 11, 2017 at 6:33 AM, Harke Smits <yrra...@gmail.com> wrote:
>> Hello Learned group,
>> I have a BBB with Debian version 2017-03-19, the latest release as far as
>> I know, with a 4D systems display. I have made a Python script using
>> TkInter, running fine on another BBB system with an older Debian version.
> OK, so you are interacting with your BBB directly, not from another
> computer via SSH or serial, right?
>> I made a simple testscript using TkInter as well. Running the testscript
>> form XTerm or UXTerm (what is the difference?) works: a simple window pops
>> Running the same from Debian bash directly displays the well known error
>> above. I googled a lot but no answer found yet.
> What do you mean by 'from the debian bash'? Normally, you're sitting in
> front of a graphical desktop (i.e. running the X server or Wayland)
> displaying a terminal emulator (e.g. XTerm) that runs a shell (e.g. bash).
> The shell command (e.g. xclock) starts the process that issues X11 commands
> that go to the current $DISPLAY and show up as windows.
> If you're not running the X server, i.e. sitting at the raw text terminal
> console (all black screen with white text), you cannot and will not see
> The older system with similar software runs fine from autostart. Maybe I
>> need to do here as well? I can not find autostart in the lastest Debian
>> version: it must be in a different directory that I know of.
>> Finally: if I run the original script (running fine on the older system)
>> I just get a blank screen and system halts.
> If you want to use your system in graphics mode you should autostart X.
> Usually it is done by asking it to go to the graphical run state (5 in the
> old sysV init scripts, graphical.target in systemd)
> For debugging, you can type 'startx' to start X manually.
> For more options, visit http://beagleboard.org/discuss
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> To unsubscribe from this group and all its topics, send an email to
> To view this discussion on the web visit https://groups.google.com/d/
> For more options, visit https://groups.google.com/d/optout.
For more options, visit http://beagleboard.org/discuss
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.