, what can you
suggest?
thanks in advance
*Roland Giesler*
--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical
Here is a more detailed analysis of the results and logs:
This is what happens on the thin client (I can only take a screenshot):
[image: Inline image 1]
This is the log on the server:
Nov 21 14:59:03 Ashton dnsmasq-dhcp[317]: 2840456473 available DHCP
range: 172.16.0.20 --
Subsequently I did manage to upgrade both busybox and udhcpc to v
1.15.3http://www.edgebaston.co.za/eMail-Query.aspx?CLIENTID=5314eMail=da...@edgebaston.co.zaName=David%20FinlaysonCONTACTID=4698(as
Alkis suggested in
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/505916) and made the
changes
. I thought of making a copy of it in /opt
or so. My install script could then make a symlink from the user's
Autostart pointing to the binary.
They could download and install it under Windows at home for themselves
then.
What do you think?
Rolf
Am 19.11.2013 11:26, schrieb Roland Giesler
After updating the chroot and ensuring that ldm is the latest version is
per the site above, when I start my thin client I still don't get the
sessions in the chooser and neither is my ldm_session setting lts.conf
accepted.
Does anyone have advice?
Roland Giesler
On 15/08/2013 00:35, Roland Giesler wrote:
I can report that if I kill lightdm running in the server at startup,
the problem goes away.
I did: sudo pkill lightdm
When I now log in on a thin client in Gnome-classic, I get logged in.
It turns out that this is not quite true. I'm using
LTSP Server: Ubuntu 12.04 64bit
I have a quirk I can't pinpoint and not sure if it's due to LTSP or
not. When a thin client starts Xsession (after booting successfully),
the user selects Gnome classic from the preferences menu on the LDM
login screen. The user then logs on. The error Xsession:
On 14/08/2013 15:41, Roland Giesler wrote:
What can I furthermore do to pinpoint this and resolve the problem?
As suggested on IRC, I tried startx for the user on the server and all
run well, no error. Logging in the from lightdm on the server, is also
not a problem, I can change the session
I can report that if I kill lightdm running in the server at startup,
the problem goes away.
I did: sudo pkill lightdm
When I now log in on a thin client in Gnome-classic, I get logged in.
What is causing this?
Where should I report this?
thanks
Roland
0x1A7E38F8.asc
Description:
If you don't want to use network booting, then they will provide you
with a pre-installed Ubuntu image on an SD card.
regards
Roland Giesler
+27 (0)72-450-2817
http://www.giesler.za.net
Disclaimer: The sender invokes the rule of exemptus responsibilitus
pertaining to caffeine soluted inductions
successfully? If so, you should see what
your log says. If you put SCREEN_08=shell into your lts.conf, you will be
able to press ctrLaltF8 on the client and inspect the local log at
/var/log/syslog. That would give you some indication of what it going
wrong.
regards
Roland Giesler
!
In the past, Debian LTSP used NFS and Ubuntu used NDB for connecting thin
client.
If it's always true, you need to configure the NBD server and set NBD
parameter in the chroot.
Bye
Manu
Le 06/05/2013 19:12, Roland Giesler a écrit :
I used a Debian Wheezy server I created in a VM over
I have an Ubuntu 64bit server (12.04) with a Debian Wheezy i386 chroot.
Installation was done from a Server-CD, then I added
ltsp-server-standalone, removed isc-dhcp-server and added dnsmasq. The
client boots, but gets to
Begin: Mounting root filesystem Begin: Running script/nfs-top, done
...
I used a Debian Wheezy server I created in a VM over the weekend to build a
chroot i386 for my Ubuntu server. (ltsp-build-client -a i386)
Then I copied /opt/ltsp/i386 from the Wheezy VM to /opt/ltsp/i386 on Ubuntu
Precise. (I tarred the directory, copied it over and untarred it again)
Then ran
14 matches
Mail list logo
