=== jesse_ is now known as Guest88347 [09:14] i am trying to customise the edubuntu usplash screen [09:15] I already did it but [09:15] with the server the new usplash works fine but [09:16] the thin clients stop running in the usplash [09:17] anyone knows why? thanks [09:19] I am using a different kernel version in the clients, maybe that is the reason [09:19] but I cant update the kernel in the clients, after chroot to ltsp [09:20] have u done ltsp-update-kernels? [09:21] yep [09:22] but do i need chroot??? [09:24] from the server ltsp-update-kernels says "Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386" [09:24] but the kernel is not updated [09:26] in the clients i cant connect to the repositories "Could not resolve ‘gb.archive.ubuntu.com’" [09:26] I am not behind a proxy [09:26] Marie_untu: copy the sources.list from the server to the thin client [09:26] i did it [09:27] but it seems that the chroot has not internet connection, dont know why [09:27] you are doing chroot /opt/ltsp/i386? [09:27] in the clients I have connection but in the chroot i havent [09:27] yep [09:27] and then apt-get update [09:27] yes [09:28] check to see whats in the sources.list in the thin client [09:28] the same as in the server [09:28] from the server u can do apt-get update? [09:29] yes [09:29] from the server i can [09:29] have u modified the chroot at all? [09:29] i checked and yes the repositories are the same in booth [09:29] installed anyhting extra? [09:29] nope [09:29] hmm. [09:30] i have search at google and the only thing i get is that if i am behind a proxy i should have some problems [09:30] but i am not behind a proxy [09:32] try setting up resolv.conf in the thin client [09:32] it shouldn't be necessary, but try [09:33] ok, how can i set up resolv.conf? [09:33] copy it across from the server [09:33] /etc/resolv.conf to /opt/ltsp/i386/etc/resolv.conf [09:34] ok [09:35] koooool [09:35] now [09:35] thanks man [09:35] enjoy [09:35] so to update the kernels i must use ltsp-update-kernels?? [09:36] but from the server or from the chroot? [09:36] the chroot i guess [09:36] do apt-get update && apt-get upgrade in client [09:36] then ltsp-update-kernels [09:36] then ltsp-update-image [09:36] ok [09:36] in client you mean in the chroot? [09:36] yes [09:36] ok cheers mate [09:37] i ll try that, hope the usplash will work that way [09:37] i ll be around [09:37] av a nice day [09:37] thanks, same [09:56] hi again nubae [09:56] ok i did the apt-get update and upgrade, everything ok [09:57] then from the server i did ltsp-update-kernel and it says "Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386" [09:57] but the kernel in the clients still the same 1.6.14-16 [09:58] sorry 2.6.24-16 [09:58] instead of 2.6.24-19 [10:00] ok wait, i forgot ltsp-update-image [10:01] coz in the chroot "uname -a" shows the 2.6.24-19 version [10:03] right ltsp-update-image is important :-) [10:07] ooops [10:07] not working [10:08] whats the problem? [10:08] in the /opt/ltsp/i386/boot the same 2.6.24-16 kernel appears [10:08] not the -19 [10:09] what is in /var/lib/tftpboot/ltsp/i386? [10:10] the 2.6.24-16 version, not the -19 [10:10] hmmm [10:10] a bit strange [10:11] it is if update-kernels is telling u it modified it [10:11] nop [10:11] it just says "Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386" [10:12] but not any of "`/opt/ltsp/i386/boot/vmlinuz' -> `/var/lib/tftpboot/ltsp/vmlinuz' `/opt/ltsp/i386/boot/vmlinuz-2.6.15-20-386' -> `/var/lib/tftpboot/ltsp/vmlinuz-2.6.15-20-386' `/opt/ltsp/i386/boot/initrd.img' -> `/var/lib/tftpboot/ltsp/initrd.img' `/opt/ltsp/i386/boot/initrd.img-2.6.15-20-386' -> `/var/lib/tftpboot/ltsp/initrd.img-2.6.15-20-386' " or whatever [10:12] as the edubuntu cookbook says it may appear after ltsp-kernels-update [10:13] wait, do ltsp-update-kernels now [10:13] very strange, because in the chroot uname says "Linux ubu-laptop 2.6.24-19-generic" [10:14] then check the files in /var/lib/tftpboot [10:14] same, the -19 version doesnt appear there [10:15] then update-kernels isn't working it seems [10:15] yep, it seems so [10:15] so what can i do, any idea? [10:15] why? :) [10:16] manually copy /opt/ltsp/boot to /var/lib/tftpboot/ltsp/i386 [10:16] to be honest i didnt make any change to the system at all [10:16] ok [10:16] but u should really look at the underlying causes, it makes no sense [10:17] ok, thanks [10:18] but do you know any underlying cause that can be causing the problem?? [10:18] or how can i debug it? [10:19] well I would take a look at the ltsp-update-kernels script and see whats failing [10:19] ok wait, i remember now, [10:20] when i changed the usplash i manually update the initramfs [10:20] and the i copied the kernel to the /var/lib/tftpboot [10:21] it could be that the reason? [10:21] yep [10:21] do you know what can i do to solve it? [10:21] u dont need to manually do initramfs iirc, ltsp-update-kernels should take care of that (maybe...) [10:21] ok ok, thanks [10:21] u definetly dont need to copy it across though [10:22] so that cause the problem [10:22] so that probably messed it uü [10:22] up [10:22] permissions and such [10:22] ok, i write it down that :) [10:22] so now, how can i restore it? [10:22] recreate the chroot with build-ltsp-client [10:23] or maybe just delete /var/lib/tftpboot/ltsp/i386 [10:23] and then do ltsp-update-kernels [10:23] ok I ll try that [10:23] it is gonna channge any of my clients configuration or users? [10:24] if u have a lts.conf file yes [10:24] nop i havent [10:25] the only special thing i have are the user accounts, that i guess they will still the same after that [10:25] isnt it [10:25] yeah [10:25] anyway i ll do a back up just in case [10:25] thanks veeeeery much :) [10:30] ok, delete /var/lib/tftpboot/ltsp/i386 and then ltsp-update-kernels doens work, same results [10:30] build-ltsp-client says "command not found" [10:30] ltsp-build-client [10:31] u have to delete /opt/ltsp/i386 though first, or back it up [10:31] ok :) [10:32] wait, I have a backup before I change the initrdimg [10:32] should i restore it by removing the /opt/ltsp/i386 and copy the backed up folder? [10:33] or it is better to build the client again? [10:34] never mind, dont answer, silly question [10:34] :) [10:34] thanks veeery much, again [10:34] cya aroundç [11:25] ok [11:25] nubae [11:25] after built the ltsp client [11:25] the problem still there [11:25] same as before [11:26] using kernel -16 not -19 [11:26] ltsp-update-kernels same results [11:27] the thing is I changed the usplash on the server, so I update-initramfs in the server so the usplash can be updated [11:27] so do that in the client too [11:28] and then, without copying the image manually... do ltsp-update-keys [11:29] ok, but the thing the server is using -19 and the clients still with the -16 [11:30] im a bit fustrated now :) [11:31] u need to go into chroot and apt-get update and apt-get upgrade [11:31] i did it [11:31] client updated and upgraded [11:31] but then ltsp-update-kernels not working [11:32] doenst change the kernel [11:33] so i should copy the kernel manually [11:33] but i just want to resolve the ltsp-update-kernel problem [11:36] which kernel version are you using in the clients??? [11:36] maybe it doesnt allow to upgrade to the -19??!! [11:38] should I manually copy the /boot/initrd.img-2.6.24-19-generic to /opt/ltsp/i386/boot and to/var/lib/tftpboot/ltsp/i386???? [12:07] heyyy, anyone knows any related problem with ltsp-update-kernels and the update-initramfs???? [12:09] aptitude search usplash [12:09] ooops [12:16] this is a hell :) [12:16] why when i change the usplash to the clients it doesnt boot??? [12:17] why? :0 [12:21] is anybody out there?? [13:28] heya all === Rondom_ is now known as Rondom [14:43] Morning all === nixternal_ is now known as nixternal [15:02] ogra: I filed bug 273147 and bug 274803 [15:02] Launchpad bug 273147 in ltspfs "Usb stick (flash drive) does not pop up on the Gnome desktop" [High,Triaged] https://launchpad.net/bugs/273147 [15:02] Launchpad bug 274803 in ltsp "Allow shutdown to be started as root on thin clients (localapps)" [Wishlist,Triaged] https://launchpad.net/bugs/274803 [15:03] well, I updated the first and filed the second [15:03] morning sbalneav [16:06] I have a problem updating the kernels on the clients [16:07] the server is running the 2.6.24-19-generic and the clients the 2.6.24-16-generic [16:07] I have already upgraded the clients in the chroot [16:08] when i execute the ltsp-update-kernels the clients' kernel is not updated, it still the -16-generic [16:09] the only thing I changed is the usplash in the server, and then i executed update-initramfs [16:10] any idea? it is a bug or a misconfiguration problem? [16:24] ok, next quest. [16:25] how can I change manually the kernel in the clients?? [16:30] is anybody out there?? [16:31] Marie_untu: So, you've done an apt-get upgrade in the chroot? [16:31] yep [16:31] and its upgrade sucessfully [16:32] so if you do a chroot /opt/ltsp/i386 [16:32] but then i do ltsp-update-kernels, and the kernels are not updated [16:32] dpkg -l | grep linux-image, you see that the 2.6.24-19-generic's there? [16:33] ok i did dpkg but the -19-generic is not there [16:34] ok, then it didn't get upgraded in the chroot. [16:34] so how can i upgrade the kernels [16:35] in the chroot i did apt-get upgrade 4 times or more [16:36] What are you running, hardy? [16:36] yep [16:36] 8.04 [16:36] as I said before the only thing I changed is the usplash in the server, and then i executed update-initramfs [16:36] Usually the hardy-updates apt line isn't included in the ltsp chroot's apt setup [16:37] maybe that have something to do with that [16:37] Well, the usplash in the server doesn't have anything to do with the clients [16:37] here's what I'd do. [16:37] exit out of the chroot [16:37] cp /opt/ltsp/i386/etc/apt/sources.list /opt/ltsp/i386/etc/apt/sources.list.orig [16:38] ok i did that already [16:38] cp /etc/apt/sources.list /opt/ltsp/i386/etc/apt/sources.list [16:38] sources.list is the same in both [16:39] grep hardy-updates /opt/ltsp/i386/etc/apt/sources.list [16:39] I even built the image again [16:40] Do you get any lines showing up from the above grep statement? [16:41] yep [16:42] deb http://gb.archive.ubuntu.com/ubuntu/ hardy-updates main restricted [16:42] deb-src http://gb.archive.ubuntu.com/ubuntu/ hardy-updates main restricted [16:42] deb http://gb.archive.ubuntu.com/ubuntu/ hardy-updates universe [16:42] deb-src http://gb.archive.ubuntu.com/ubuntu/ hardy-updates universe [16:42] deb http://gb.archive.ubuntu.com/ubuntu/ hardy-updates multiverse [16:42] deb-src http://gb.archive.ubuntu.com/ubuntu/ hardy-updates multiverse [16:43] when i execute ltsp-update-kernels it says: "Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386" but the kernel still the same -16-generic [16:43] well, that's because you've only got the -16 installed in the chroot. [16:43] what happens if you do a dist-upgrade in the chroot? [16:44] "bash: dist-upgrade: command not found" [16:45] chroot /opt/ltsp/i386 apt-get dist-upgrade [16:45] I'm assuming you did the apt-get update first, right? [16:46] ok! [16:46] it seems the kernel is upgrading [16:47] but why it is not upgraded with the lstp-upgrade-kernels [16:47] it is maybe a bug??? [16:47] Well, ltsp-upgrade-kernels just copies the kernel in the chroot to the tftp area [16:47] so, if you've got an older kernel in the chroot, that's all it's going to copy [16:48] so, you have to get the chroot updated first, then you can do the ltsp-upgrade-kernels [16:48] heyyy [16:48] as well, after the upgrade's done, you'll want to do the ltsp-update-image again. [16:48] but i upgraded the chroot firts [16:48] ok i can imaging [16:49] well, you didn't, because you still had only a -16 in the chroot. [16:49] so this is why i ask here, because i apt-get updated the chroot around 10 times [16:50] so now if i want to change the usplash in the chroot [16:50] But you didn't do a dist-upgrade [16:51] i just need to cp usplash-new.so to /ltsp/i386/usr/lib/usplash [16:51] it didn't update until you did that. [16:51] yep i just dist-upgrade right now [16:52] hold down, the dist-upgrade takes the kernel from the server or from the repositorie??? [16:53] ok, from the repositorie [16:53] so if I change the usplash now in the chroot and then I update the initramfs it should work [16:53] isnt it??? [16:54] I have been with this usplash issue all day!!!! :0 [16:57] heyy sbalneav [16:57] thanks very much :) [17:19] I have Ubuntu 8.04 + LTSP 5. It works for the most part. There are inconsistancies which appear to relate to a graphics card problem, although I am not convinced of that. One issue we have noticed is when the user on the thin client changes to a screen saver it returns that Thin client to the login screen. Someone here suggested it was a bug. I would like to track it down. Yesterday I got my Thinclients set up so I can get a root shell in the [17:19] Thin client by pressing Ctrl+Atl+F2 [17:19] Where should I look to see what is actually happening when it returns the user to the LDM login screen [17:20] Sorry, was afk for a bit [17:22] jc2it: probably is a bug, but quite frankly, you don't want any other screen saver other than "Black screen" on a thin client anyway [17:22] And I know that one works :) [17:24] Yes this is true the screen does blank. The reason I was focusing on the screen saver is because I think it might lead to some of the other issues that are harder to describe [17:25] Sometimes, opengl instructions don't go remotely across the network, resulting in X server resets, which will kick you back to a login prompt. [17:27] so does this mean that the x.org log would track such an event? [17:27] on the client [17:27] or server [17:29] On the client, usually [17:29] Sometimes you can also get an error in the users $HOME/.xsession-errors [17:45] how can I change the usplash screen on the clients, I have already the usplash-theme.so [17:45] I can change it sucessfully in the server, but I cant in the clients [17:46] any idea?? [17:51] anybody out there??? [17:58] in /home//.xsession-errors [17:59] gnome-screensaver-preferences: Fatal IO error 104 (Connection reset by peer) on X server 192.168.0.239:6.0. [18:06] anyone around knows how the clients' usplash works???? [18:07] is anybody in here?? please at least say hi [18:08] or just say, nope no idea, go away :) or something similar [18:24] Marie_untu: still the same problem? [18:27] heyyy [18:27] not really [18:27] the kernel is updated sucessfully [18:27] what did u do to fix it? [18:27] now i cant change the usplash on the client [18:28] apt-get dist-upgrade in the chroot [18:28] ah yes... [19:14] ogra: one more bug for you :) bug 274902 [19:14] Launchpad bug 274902 in ltsp "PULSE_SERVER not set for localapps" [Undecided,New] https://launchpad.net/bugs/274902 [19:59] Back from lunch [20:00] Marie_untu: You'd need to rebuild the initramfs in the chroot, then re-run ltsp-update-kernels [20:50] sbalneav: btw, I filed bug 274902 as an Ubuntu bug but I guess it's something that'd need to go upstream as xrexecd.sh is an upstream script. [20:50] Launchpad bug 274902 in ltsp "PULSE_SERVER not set for localapps" [Undecided,New] https://launchpad.net/bugs/274902