Hello, and Thank You for the reply!
I've spent some of the weekend scouring the logs you recommended and then
some, in between eye bleeds, and have yet to find an error referencing tcptrack
or konsole. However there was a bit of fortune, when I looked through the forums
for anyone experiencing the same issues as I had been with tcptrack on startup,
I came across a post about "iftop". I'm not sure why but when I tried to add
"iftop" through the GUI "Autostart" utility I was presented with an error stating
"'iftop' not found, please type a valid program name." This, while puzzling as
this is how I had added "tcptrack" to startup previously, was not a problem I
was going to hunt down. In turn I simply created the 'iftop.desktop' file in the
autostart directory. As per usual with my frustration typing I made a syntax
error in the configuration file, which turned out to be the bit of fortune. When
I booted and gksu had not prompted me for a administrator password I elected to
do a bit more eyeball bloodletting and scour the logs for an error containing
"iftop". As fortune would have it I found an error notification in the
"~/.xsession-errors" log, kindly reminding me of my syntax faux pas. Now that I
have a functioning configuration file for "iftop" its starts just like it should every
boot.
This leads me to believe that it is in fact the limitation of tcptrack, needing
a window of 80 characters or greater to open and run, as iftop scales with the
window size.
I perused the "Profiles" settings in "konsole" again but do not see
any setting for changing the "default" window size. I'm not sure where the configuration
file containing the default window metrics for KDE are nor that I would want to
change it to get tcptrack to startup on boot.
Thanks again.
|