DebuggingLTSP
Revision 10 as of 2008-09-12 20:02:54
Clear message
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
This page lists some helpful steps when filing an ltsp bug
- It is very helpful if you include version numbers of the ltsp (or ltspfs) packages in your bug report (see below how to get the right version numbers for the various packages).
- If you modified any defaults in your thin client chroot, please mention this.
- Did you change anything in your lts.conf file (until gutsy in /opt/ltsp/i386/etc/, later in /var/lib/tftpboot/ltsp/i386/), if so, please attach it.
Get the versions of the packages:
dpkg -l ltsp-server dpkg -l ltsp-server-standalone dpkg -l --root=/opt/ltsp/i386 ldm dpkg -l --root=/opt/ltsp/i386 ltsp-client dpkg -l --root=/opt/ltsp/i386 ltsp-client-core # gutsy only
Is your bug related to local devices:
dpkg -l ltspfs dpkg -l --root=/opt/ltsp/i386 ltspfsd
Bugs not directly with LTSP, but affect LTSP environments
- Policykit not allowing remote sessions (Both ssh -X that ltsp uses, and NX sessions) to access admin functionality:
https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/221363
Orphane processes
gvfs-fuse sessions hanging around: https://bugs.edge.launchpad.net/ubuntu/+source/gvfs/+bug/252796
gconfd-2 hanging around: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/221363
LNS watchdog.txt from a school site that contains syslog info from gnome-watchdog