cursor disappears frequently in latest Gutsy build

What happens if the client has a keyboard, mouse, and monitor directly connected, as opposed to running through a KVM?

can you attach your /opt/ltsp/i386/etc/lts.conf ?

two questions and accordingly two answers:

1. i have tried running without kvm during this day with the screen saver active all day since i have not been home,
and no, i could not reproduce. but i do think this case is similar to when running the kvm without switching
like i did above with disappearing cursor 3 times during two days usage.

2. the lts.conf is enclosed, is there anything else i can do to help you better figure out whatever problem we may have?

Well, if it DOESN'T do it with the keyboard/mouse directly connected, I'm inclined to think it's something with the KVM. Either recent changes to Xorg have made it less kvm friendly, or your KVM's developing a hardware problem.

Not sure what you can do, other than perhaps to file a bug with Xorg.

Out of curiousity, why can't you get LDM to work?

Scott

i have tried ldm with several of my thin clients with no luck, with Gutsy,
ldm on feisty worked like charm :-)

i shall try to run more without kvm and report back, but beware:
as the computers are more or less unused while I am out working,
they may be "behind" screen saver all day. my personal theory is
that this problem happens either around when the screensaver
kicks in or when the screen gets put into power save mode.
during weekdays that will only happen a few times every day,
during weekends it will happen all the time.

so is there anybody brave or knowledgeable enough to have any
suggestion on some tests that i can do to find information needed
for turning this into something that can be used to improve the
quality of both xorg and ubuntu?

Keep on with the good work and thank you all for your suggestions
and input.

R.R.

to clarify upon what i said above:

when i first run into this problem on the 22th (saturday),
i had my screensaver configured to take over after
4 minutes of inactivity. after increasing this time to
10 minutes, the frequency of the problem decreased
drastically.

R.R.

> i have tried ldm with several of my thin clients with no luck, with Gutsy,
> ldm on feisty worked like charm :-)

I was kind of hoping to get a little more information on WHAT failed exactly, so we could
get it working for you. If it is a problem with something LTSP related, I'm less interested in
fixing it for startx, and more so for LDM.

Could you give us a little more info on how ldm's failing?

As for suggestions related to the KVM situation, I think it's important to determine for sure if:

1) It works as expected WITHOUT the KVM
2) We can quantify exactly WHAT kicks it off, with the KVM. Perhaps setting your screensaver
timeout to be something like 1 minute, and doing some testing will give us more insight.

Let us know.

Scott

thank you Scott for your suggestions regarding LDM. Actually I have submitted logfiles
and error messages for this problem in another bug report; unfortunately I am not
friendly enough with the launchpad to figure out where, at least it is nowhere to be
seen on my page with bugs that i have reported upon right now. As I am not feeling
well and since this day will turn out very busy, I will not be able to figure out where
until tonight.

Anyway, from the helpful comments and suggestions from Oliver on that case,
I figured that there was not much I could do beside setting up a development
environment and start figuring out what was happening myself; which could
be a splendid idea ;-)

So, yes, there should be reports and information on that case somewhere deep
inside the stomach of Launchpad and I am to tired to figure out where right now.

Sorry for the low information density provided in this message, thank you all
for your dedicated work and the splendid software that makes (at least) my
world work a little bit better.

i have upgraded my system a few times and now i am not
able to reproduce this problem again.

neither with or without kvm.

i will get back _if_ things turn fishy again 8-)

assuming we released a fix then :) feel free to reopen if the same happens again.