This bug was fixed in the package ltsp - 5.3.2-0ubuntu1
---
ltsp (5.3.2-0ubuntu1) precise; urgency=low
[ Stéphane Graber ]
* New upstream release (5.3.1)
- A lot of Debian specific fixes (code path not used by Ubuntu)
- Ensure /sys and /proc are always mounted when calling
** Changed in: ltsp (Ubuntu Precise)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in Ubuntu.
https://bugs.launchpad.net/bugs/813837
Title:
ltsp client not able to load boot file: ltsp/am
Bumping to high as LTSP 5.3 turned compression back on, adding a few
minutes of install time and so making this bug happen even on SSD. No
LTSP install seems possible until the d-i component is fixed.
** Changed in: ltsp (Ubuntu Precise)
Importance: Medium => High
--
You received this bug not
Moving to beta1 where we'll have the new upstream LTSP and some more
changes (including a rewrite of that d-i script).
** Changed in: ltsp (Ubuntu Precise)
Milestone: precise-alpha-2 => ubuntu-12.04-beta-1
--
You received this bug notification because you are a member of Edubuntu
Bugsquad, w
Marking lucid as Won't fix as the bug is in a udeb and if we don't fix
it in for the milestone, there's no point in fixing it at all.
The rational for not fixing in 10.04.4 is the high risk of regression
that comes with touching that script, for fixing a bug that only appears
so rarely that as far
** Changed in: ltsp (Ubuntu Lucid)
Milestone: ubuntu-10.04.4 => None
--
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in Ubuntu.
https://bugs.launchpad.net/bugs/813837
Title:
ltsp client not able to load boot file: ltsp/amd64.
moving milestone to alpha-2
** Changed in: ltsp (Ubuntu Precise)
Milestone: precise-alpha-1 => precise-alpha-2
--
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in Ubuntu.
https://bugs.launchpad.net/bugs/813837
Title:
ltsp cli
lowering importance because it is a race condition that is rarely met.
** Changed in: ltsp (Ubuntu Lucid)
Importance: High => Medium
** Changed in: ltsp (Ubuntu Precise)
Importance: High => Medium
--
You received this bug notification because you are a member of Edubuntu
Bugsquad, which i
** Changed in: ltsp (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) => Stéphane
Graber (stgraber)
** Also affects: ltsp (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: ltsp (Ubuntu Lucid)
Assignee: (unassigned) => Stéphane Graber (stgra
ltsp-image-build.log is truncated. The last line is the progress bar of
mksquashfs at 99%.
** Attachment added: "ltsp-image-build.log"
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/813837/+attachment/2224177/+files/ltsp-image-build.log
--
You received this bug notification because you
Here are the installer logs of a failed install.
The VM is set to 8GB of disk and 1GB of RAM.
After installation there are 52% of disk space left.
The same installation, with the same VM setup and same image, failed
once and succeeded another time. I tried 10.04.2 which failed and 10.04
which pas
The problem seems to be this piece of code in ltsp-client-
builder.postinst:
=
chroot /target ltsp-update-image >$COMPRESS_LOG 2>&1 &
OLDVAL=0
while [ -z ${LOOP} ]; do
rawval=$(tail -1 $COMPRESS_LOG |sed -e 's/^.* //')
if [ "$(echo $rawval|grep '[0-9]\%$')" ];then
val=$(echo $r
** Description changed:
Running lucid-alternate-amd64.iso (10.04.03)
Both the LTSP server and thin client (pxe boot) are able to obtain an IP
address from the internal dhcp server.
The thin client starts to connect and fails with an error unable to
- locate the filename
+ locate the
Or better change it in /etc/ltsp/dhcp.conf
--
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in Ubuntu.
https://bugs.launchpad.net/bugs/813837
Title:
ltsp client not able to load boot file: ltsp/amd64.tmp/pxelinux.0
To manage noti
14 matches
Mail list logo
