Ubuntu
ltsp package

LDM_DIRECTX doesn't work with NFS root

Bug #234006 reported by Francis Giraldeau on 2008-05-22

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
ltsp (Ubuntu)	Fix Released	Undecided	Unassigned
Hardy	Fix Released	Low	Unassigned	Ubuntu ubuntu-8.04.1
Intrepid	Fix Released	Undecided	Unassigned

Bug Description

When thin-client are configured to use NFS root, then the option LDM_DIRECTX causes a login failure.

I discovered that the file /root/.Xauthority and the directory /root/.ssh are not created with NFS root setup, because /root is read-only.

It simple to fix, /root need to be put in the rw directory list for mount bind in $CHROOT/etc/default/ltsp-client-setup

--- ltsp-client-setup 2008-05-22 09:09:29.000000000 -0400
+++ ltsp-client-setup.ldm-directx-nfs-fix 2008-05-22 09:09:15.000000000 -0400
@@ -13,7 +13,7 @@

# tmpfs/bind directions that get mounted with only directory structure
# preserved
-rw_dirs="/var/lib/xkb /var/log /var/spool /var/tmp /tmp /var/lib/discover /etc/console-setup"
+rw_dirs="/var/lib/xkb /var/log /var/spool /var/tmp /tmp /var/lib/discover /etc/console-setup /root"

# tmpfs/bind directions that get mounted with directory structure and data
# copied

Tags:

Oliver Grawert (ogra) on 2008-05-30

Changed in ltsp:
importance:	Undecided → Low
milestone:	none → ubuntu-8.04.1
status:	New → Fix Committed

Revision history for this message

Martin Pitt (pitti) wrote on 2008-05-30:

Accepted into -proposed, please test and give feedback here

Revision history for this message

Oliver Grawert (ogra) wrote on 2008-06-17:

Tested and verified this, seemed to work for me.
it would be nice if the original reporter could comment on the fix as well since that setup is uncommon and rarely used nowadays, i dont want the package to be blocked from entering hardy-updates by a missing bug comment.

Revision history for this message

Martin Pitt (pitti) wrote on 2008-06-17:

Since the original reporter submitted the patch, we can safely assume that it actually worked for him. Tested by Oli, too, thus considering verified.

Steve Langasek (vorlon) on 2008-06-17

Changed in ltsp:
milestone:	ubuntu-8.04.1 → none

Revision history for this message

Martin Pitt (pitti) wrote on 2008-06-17:

Copied to hardy-updates.

Changed in ltsp:
milestone:	none → ubuntu-8.04.1
status:	Fix Committed → Fix Released

Revision history for this message

Francis Giraldeau (francis-giraldeau) wrote on 2008-06-19:

I did tested from hardy-updates and this bug is resolved.

Revision history for this message

Stéphane Graber (stgraber) wrote on 2008-08-10:

This bug is fixed in Intrepid.
root@ltsp-server:~# cat /opt/ltsp/i386/etc/default/ltsp-client-setup | grep rw_dirs
rw_dirs="/var/lib/xkb /var/log /var/spool /var/tmp /tmp /var/lib/discover /etc/console-setup /root"

Marking it fix released for Intrepid as well.

Changed in ltsp:
status:	New → Fix Released

Revision history for this message

gcc (chris+ubuntu-qwirx) wrote on 2009-03-16:

Note that whenever you build or rebuild an LTSP chroot environment, you must include the "updates" components or you will not get this bug fix:

ltsp-build-client --components main,restricted,updates

I think it might be a good idea to release a new ltsp-client-core for hardy that includes updates in the default list of components automatically.

Revision history for this message

Stéphane Graber (stgraber) wrote on 2009-03-16: Re: [Bug 234006] Re: LDM_DIRECTX doesn't work with NFS root

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

gcc wrote:
> Note that whenever you build or rebuild an LTSP chroot environment, you
> must include the "updates" components or you will not get this bug fix:
>
> ltsp-build-client --components main,restricted,updates
>
> I think it might be a good idea to release a new ltsp-client-core for
> hardy that includes updates in the default list of components
> automatically.
>

Updates is a pocket not a component so adding it to the list of
components won't work.
The valid list of components are:
- main
- restricted
- universe
- multiverse

The valid list of pockets are:
- <release>
- <release>-updates
- <release>-security
- <release>-proposed
- <release>-backports

Stéphane
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkm+axoACgkQjxyfqkjBhuy36gCgiqSOQz4oR95X1clbWqXLEG4F
RU0An3ZObsX1VZNRHOo+9yWs+x92A960
=+AJ5
-----END PGP SIGNATURE-----

Revision history for this message

Oliver Grawert (ogra) wrote on 2009-03-16:

just on a sidenote: that would have to be ltsp-server (which sets the options and creates teh sources.list of the client)
but as stephane already pointed out, it's a non trivial change to add another pocket vs adding a component. one possible fix would be to set ---copy-sourceslist by default and rely on the fact that the server has $release-updates enabled properly ... so the servers sources.list ends up in the client env.

Revision history for this message

gcc (chris+ubuntu-qwirx) wrote on 2009-03-16:

#10