thin client manager

[Bob Wooden]

I have attempted the process you suggested.  I have exited chroot.  I 
have "sudo ltsp-image-update.  Update completes properly.  And I reboot 
my client and still I get "Unavailable, install x11vnc on client" within 
the TCM screen. 

I am inserting questions within my "paste."

> -------------------- snip -----------------------------
>
> root at myhostname:/# apt-get install x11vnc
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> x11vnc is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
> 6 not fully installed or removed.
>   
This "6 not fully installed" continues?

> Need to get 0B/18.6MB of archives.
> After unpacking 0B of additional disk space will be used.
> Can not write log, openpty() failed (/dev/pts not mounted?)
> (Reading database ... 16399 files and directories currently installed.)
> Preparing to replace linux-image-2.6.22-14-386 2.6.22-14.46 (using .../linux-image-2.6.22-14-386_2.6.22-14.46_i386.deb) ...
> Done.
> Unpacking replacement linux-image-2.6.22-14-386 ...
> Examining /etc/kernel/postrm.d .
> run-parts: executing /etc/kernel/postrm.d/ltsp-update-kernels
> Cannot open ``/boot/nbi.img-2.6.22-14-386'':File exists
> run-parts: /etc/kernel/postrm.d/ltsp-update-kernels exited with return code 1
>   
The fact that it states that the "file exists" and then exits "with 
return code 1" I do not understand.
> Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-2.6.22-14-386.postrm line 320.
> dpkg: warning - old post-removal script returned error exit status 1
> dpkg - trying script from the new package instead ...
> Examining /etc/kernel/postrm.d .
> run-parts: executing /etc/kernel/postrm.d/ltsp-update-kernels
> Cannot open ``/boot/nbi.img-2.6.22-14-386'':File exists
> run-parts: /etc/kernel/postrm.d/ltsp-update-kernels exited with return code 1
> Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/tmp.ci/postrm line 320.
> dpkg: error processing /var/cache/apt/archives/linux-image-2.6.22-14-386_2.6.22-14.46_i386.deb (--unpack):
>  subprocess new post-removal script returned error exit status 1
> Examining /etc/kernel/postrm.d .
> run-parts: executing /etc/kernel/postrm.d/ltsp-update-kernels
>   
Here, the program is talking about "ltsp-update-kernels" and yet when I 
leave chroot, I update images?
> Cannot open ``/boot/nbi.img-2.6.22-14-386'':File exists
> run-parts: /etc/kernel/postrm.d/ltsp-update-kernels exited with return code 1
> Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/tmp.ci/postrm line 320.
> dpkg: error while cleaning up:
>  subprocess post-removal script returned error exit status 1
> Errors were encountered while processing:
>  /var/cache/apt/archives/linux-image-2.6.22-14-386_2.6.22-14.46_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> -------------------- snip -----------------------------
I am very much a newbie in this area.  So, I apologize for reading 
through this output and not understanding what is happening.

 From what I have been reading, others have gotten this to work, so I 
suspect it is something I have done wrong.  So, any suggestions would be 
greatly appreciated.

Bob



Charles Austin wrote:
> On Jan 29, 2008 10:43 AM, Bob Wooden <bobwdn at watsonboyce.com> wrote:
>   
>> I have now followed the "new" InstallX11VncOnLtspClients (listed below)
>> and they are much better, thank you.  But, I am still receiving the
>> following error messages:
>>
>>     
>>> ---------snip----------
>>>
>>> mainuser at hostname:/# apt-get install x11vnc
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> x11vnc is already the newest version.
>>>       
> OK, looks like x11vnc is already installed.  That is good.
>
> Have you tried to update the image?
>
> What happens in the TCM after updating the image and rebooting the client?
>
>
>   
>>> Can not write log, openpty() failed (/dev/pts not mounted?)
>>>       
> This is a product of the chroot environment, apparently.  I did not
> dig into why it happens, but it does not seem to affect performance.
>
>   
>>> (Reading database ... 16399 files and directories currently installed.)
>>> Preparing to replace linux-image-2.6.22-14-386 2.6.22-14.46 (using .../linux-image-2.6.22-14-386_2.6.22-14.46_i386.deb) ...
>>> Done.
>>> Unpacking replacement linux-image-2.6.22-14-386 ...
>>> Examining /etc/kernel/postrm.d .
>>> run-parts: executing /etc/kernel/postrm.d/ltsp-update-kernels
>>> Cannot open ``/boot/nbi.img-2.6.22-14-386'':File exists
>>> run-parts: /etc/kernel/postrm.d/ltsp-update-kernels exited with return code 1
>>> Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/
>>>               linux-image-2.6.22-14-386.postrm line 320.
>>> dpkg: warning - old post-removal script returned error exit status 1
>>> dpkg - trying script from the new package instead ...
>>> Examining /etc/kernel/postrm.d .
>>> run-parts: executing /etc/kernel/postrm.d/ltsp-update-kernels
>>> Cannot open ``/boot/nbi.img-2.6.22-14-386'':File exists
>>> run-parts: /etc/kernel/postrm.d/ltsp-update-kernels exited with return code 1
>>> Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/tmp.ci/postrm line 320.
>>> dpkg: error processing /var/cache/apt/archives/
>>>               linux-image-2.6.22-14-386_2.6.22-14.46_i386.deb (--unpack):
>>>  subprocess new post-removal script returned error exit status 1
>>> Examining /etc/kernel/postrm.d .
>>> run-parts: executing /etc/kernel/postrm.d/ltsp-update-kernels
>>> Cannot open ``/boot/nbi.img-2.6.22-14-386'':File exists
>>> run-parts: /etc/kernel/postrm.d/ltsp-update-kernels exited with return code 1
>>> Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/tmp.ci/postrm line 320.
>>> dpkg: error while cleaning up:
>>>  subprocess post-removal script returned error exit status 1
>>> Errors were encountered while processing:
>>>  /var/cache/apt/archives/linux-image-2.6.22-14-386_2.6.22-14.46_i386.deb
>>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>>       
>
> I have not seen this on my install.  Any experts care to jump in?
>
>   
>> And now I could use any good suggestions.  Please help.
>>
>>     
> Let us know what happens if you
> 1. exit chroot
> 2. sudo ltsp-update-image
> 3. reboot the client
>
> Charles
>
>