Dennis,
I did both since I realized you were right on both.
I had fixed the Tkinter problem a couple or three weeks ago and somehow
when I was trying to get systemd to work, I must have clobbered Tkinter
or something. So now I am reloading Debian Wheezy, bone50. I also was
having trouble with the latest Wheezy, 79. Don't know why. I was using
putty to start my GUI program with a keyboard and mouse connected to the
BBB thru a USB hub, per suggestion by Steve Plant on the BBB users
forum. I have myProg.py loaded at /home/debian/Desktop and found that I
had to start it with sudo python myProg.py. That has worked fine for a
couple of weeks or so and I was dismayed to see the Tkinter error show
up again. I have a 4D Systems 4DCAPE-70T attached to the BBB to give me
the GUI display and like I say, it was working terrifically for the past
two or three weeks.
Hopefully I will be able to get systemd to start my GUI program. I would
like it to start up upon resetting the BBB. Or maybe I can have a script
on the Debian desktop that I can get to trigger my GUI program? Somehow
I need to make it easy for the users to start the code, not requiring
the mouse and keyboard. Any suggestions?
I couldn't make any sense of the Debian bone79, just seeing the blank
screen like you said. Very strange, the bone79.
Thanks, John
On 4/9/2016 11:25 AM, Dennis Lee Bieber wrote:
On Fri, 8 Apr 2016 21:11:22 -0700, John Baker
<johnba...@ieee.org> declaimed the following:
You are right Dennis. Excellent suggestions. Now I can get systemd to
work and can run my simple Python program and write file to memory using
stdout.
Out of curiosity, which suggestion did it (incorrect Python invocation,
or stdout redirection), or were both required?
Now to get my GUI program to run. I think I may have clobbered something
in the Debian or Tkinter or something since my GUI program is giving me
a Tkinter error, the same one I had a couple of weeks ago and got past.
But it's reared its ugly head again. Very annoying. I suspect I have to
reload the Tkinter.
Ugly error:
_tkinter.TclError: no display name and no $DISPLAY environment variable
Since Tkinter just invokes the external Tcl/Tk libraries, I'd interpret
the above to mean just what it says... Tk can't find an environment
variable providing the reference to the X-window display server. Did you
log-in through the windowing system?
If you're trying to run a GUI via systemd I don't think you'll have
much luck -- systemd (or other init process system) don't have
displays/consoles (which is why stdio likely had to be redirected; one is
probably supposed to be using the system logging functions for such).
I'll admit I'm very stale on Linux -- I'm still pondering what changes
occurred between the March 2015 image and the November 2015 image (I'm
still running Wheezy -- Jessie appears to have broken too much stuff, at
least with regards to books). I know I used to have a "task bar" at the
bottom of the screen with the former (along with the Beagle), but the
latter just has a context menu offering console terminal, web browser, and
switching desktop screens (and is otherwise completely blank/black -- if it
wasn't for the mouse pointer I'd have thought the display wasn't even
connected). I'm also not certain Cloud 9 is still functioning in the
November image.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
