On Thu, 2007-09-13 at 23:03 -0500, Scott Balneaves wrote: > On Thu, Sep 13, 2007 at 10:11:10PM -0400, Todd O'Bryan wrote:
If developers want detailed information, they're going to have to tell us exactly what they want. :-) Seriously, though, I didn't really know what you'd need or where to send it. I'll pull together a profile of the lab and save it somewhere to send along with bug reports. > If people want these problems fixed, they're going to have to start giving > us DETAILED information. > > Here's what we need: > > a COMPLETE description of your server, including: > Motherboard type/model number > Amount of memory > video card in server > output of lspci -vv > > A COMPLETE description of your network, including: > brands of switches used > 10/100/1000? > etc. > > a COMPLETE description of your thin clients, including: > Motherboard type/model number > Amount of memory > video card in client > output of lspci -vv > > listing of your lts.conf file, if any > listing of your .xsession-errors > any relevent output from dmesg, /var/log "relevant" is the hard question here. With 25 or so students working at once, is there an easy way to figure out what we should send and what we shouldn't? I mean, is it worth it to zip up the last hour or so of the log and tell you which client died? > and, if a program crashes, locks up, etc: > > What steps you can take to make it fail > if a document/website/email/attachment etc > causes the failure, a copy of that sent to one of the developers. It seems to be fairly intermittent. My students were trying to use Impress yesterday and it would often freeze when they were trying to crop images, but not always at the same time or with the same image. Could it be that OO.org has adopted Firefox's strategy of trying to cache stuff in the XWindows memory? Lab details to follow soon... -- edubuntu-users mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
