Update: resolution issue in xterm fixed.
Rob, on the terminal try:
xterm -font -*-lucidatypewriter-medium-*-*-*-18-*-*-*-*-*-*-*
if it's too small yet try:
xterm -font -*-lucidatypewriter-medium-*-*-*-20-*-*-*-*-*-*-*
Here are more font styles and a full explanation:
http://linuxhelp.blogspo
Update:
What a foolish answer the past! The key is in how does xterm
gives sizes to its fonts. It's easy to workaround.
Greetings,
Lucio.
On Sat, May 16, 2009 at 6:51 AM, Lucio Lastra wrote:
> Hi Rob,
>
> I tried resizing the window but the fonts remain the same.
> I don't know if it can be
Hi Rob,
I tried resizing the window but the fonts remain the same.
I don't know if it can be changed or set up in a way it matches
your resolution. You should look for a Sage developer, he/she
probably know the answer.
If you find the answer please write me back so I can fix it if
possible.
By t
Hi Lucio,
In fluxbox, choose Sage off the menu. On a 1920x1240 (or so)
widescreen laptop, the terminal window might only use about 640x480
(or less?). it looks pretty tiny and then the fonts are barely
legible.
You can still read everything, but it would get old pretty quick. And
I couldn't s
Hi Rob,
the only issue that remains is the resolution you talked about.
When does it happen, at boot or during your sagelwlcd under fluxbox?
Greetings,
Lucio.
On Sat, May 9, 2009 at 5:26 PM, Lucio Lastra wrote:
> Hi Rob,
>
> I tried and already can add a "POWER OFF" option and "EXIT"
> will
Hi Rob,
I tried and already can add a "POWER OFF" option and "EXIT"
will be quit fluxbox as now.
I'm thinking on "startupmanager" to load a boot splash that
hides the details on startup and insulates more the users. But
have to measure how it performs with it. I'm also researching
automate startx
Lucio,
Sounds good. When you "EXIT" fluxbox maybe this is a way to initiate
a shutdown:
In KUbuntu w/ KDE3 I use the file /etc/kde3/kdm/Xreset to run some
commands when logging out of an X session, and maybe you could
initiate a shutdown from there?
Or maybe what would be best is to keep "E
Hi Rob,
First off, thank you very much for your time and feedback :)
I'll try to automate the start and the shutdown, otherwise I'll
put the messages in order to make clear how to do it. I'll also
work on the resolution.
The changes will be made in the next release along with the
ones Alfredo re
Hi Lucio,
Tried another machine - works great! Three suggestions:
1. Can you put up a few lines that tell a user to type "startx" when
they get the first prompt (assuming you can't just totally automate
it)?
2. Both machines I used have high-resolution screens so the terminal
window was very
Hi Lucio,
Not on vmware. Burned a CD and am running it on an x86 laptop.
I'll experiment some more this afternoon or evening and report back.
Rob
On May 8, 12:34 am, Lucio Lastra wrote:
> Update:
>
> Rob, are you running sagelwlcd on vmware?
>
> I found some information about "line 198" in
Update:
Rob, are you running sagelwlcd on vmware?
I found some information about "line 198" in here:
http://groups.google.com/group/sage-support/browse_thread/thread/f90e2df58cdf5495
but seems to be related only when running sagelwlcd under vmware on Windows
XP.
Anyways, I strongly recommend to
Hi Rob,
does this problem happens systematically (each time you run
sagelwlcd after typing "sudo startx") or just happened to you
once? I tried in several machines and didn't have any troubles
at all.
I'm downloading sagelwlcd to check if there's no data corruption
and research about what your pr
Hi Lucio,
Got a command prompt, entered startx, chose Sage off the fluxbox
menu. Got a terminal window and the Sage banner.
A few seconds later and the terminal window closed. Now every time I
choose Sage off the menu, the terminal just blinks and immediately
closes.
Running ./sage from a fr
13 matches
Mail list logo
