Has anybody by chance *successfully* changed the background image at the login screen? I've followed all of the guides that supposedly did the trick yet I keep coming up with a blank slate gray screen instead. I'm unsure of what to do and I'd REALLY like to see it changed.

12:11

<alkisg>

Roasted_: here's a how-to

12:11

1) ltsp-build-client

12:11

2) boot a client

12:11

3) run ltsp-update-image. just to verify that this is not your problem

12:12

4) open the existing .png with gimp and change it a big. Don't put your png just yet

12:12

5) ltsp-update-image

12:12

If you see the changed png, all is well, you can put your own there

12:12

You're doing something very wrong, but I don't know what, so take it step by step

12:13

Did you upload your png somewhere?

12:14

<vagrantc>

Roasted_: which guides did you follow?

12:14

<Roasted_>

vagrantc, https://help.ubuntu.com/community/EdubuntuFAQ

12:15

alkisg, I did not. let me do that quick.

12:15

<vagrantc>

Roasted_: i don't see anything in there about changing the LDM theme

12:15

<Roasted_>

scroll down

12:15

there's 3 commands

12:15

then it says edit accordingly or something

12:15

<vagrantc>

ah, found it

12:16

those instructions are very bad

12:16

<Roasted_>

it's all I could find

12:16

seems as if documentation in this area is pretty scarce

12:16

<vagrantc>

though they would work... until you upgraded your package

12:16

<Roasted_>

they would work?

12:16

I tried it like 9 times

12:16

failed each time

12:16

alkisg, I don't think I can upload this. each image hosting site I go to is un-overrideable by our filter cause theyre all classified as adult.

12:17

<alkisg>

Roasted_, for example, if you use a broken .png, then any instructions would fail

12:17

<Roasted_>

alkisg, maybe that's my issue.

12:17

I'll try locating another png and see whats up

12:17

<alkisg>

Change the existing one

12:17

<Roasted_>

how, just making a change to it in gimp?

12:17

<alkisg>

Open it with gimp, draw something, save

12:17

<Roasted_>

then run the update-image?

12:17

<alkisg>

Yes, but:

12:18

if it's already broken, it won't be fixed

12:18

<Roasted_>

if what's already broken, the png?

12:18

<alkisg>

Didn't you say you tried reverting to the old image, and failed as well?

john_s: and is that an IP address in /opt/ltsp/i386/etc/ssh/ssh_known_hosts?

17:08

<john_s>

vagrantc: that ip is in know hosts

17:09

<vagrantc>

john_s: when you ssh from a console, what does ~/.ssh/known_hosts add?

17:10

compare that with /etc/ssh/ssh_known_hosts

17:13

<john_s>

vagrantc: on which device am I looking for /etc/ssh/ssh_known_hosts ?

17:13

sorry

17:14

<vagrantc>

well, if you looking from the perspective of the server, /opt/ltsp/etc/ssh/ssh_known_hosts

17:14

if you're looking from the perspective of the thin client, /etc/ssh/ssh_known_hosts

17:14

they should be the same ... if they're different, something's amiss

17:15

er, /opt/ltsp/i386/etc/ssh/ .../

17:15

i keep forgetting the i386 today

17:16

<john_s>

ah ha!

17:17

from the tc perspective /etc/ssh/ssh_known_hosts contains stale ssh entries for the old ip

17:17

do does that mean that I am either too stupid to correctly run ltsp-update-sshkeys

17:17

or does it mean something else?

17:18

shouldn't ltsp-update-sshkeys update that entr?

17:18

err.. entry

17:19

<vagrantc>

yes, it should

17:19

ltsp-update-image didn't take, for some reason

17:20

ls -l /opt/ltsp/images

17:20

<Roasted>

hm, fired up my laptop here (test server with ltsp) to do some work at home and my desktop isnt booting to it. I get the ubuntu splash screen after the initial pxe boot but iltimately I get initramfs - unable to connect to nbd server. All of the google sources I looked at said to do a build-image, but I did that. Is that normally the fix or is there so mething Im missing?

17:20

<vagrantc>

Roasted: that doesn't sound likely to fix initramfs problems

17:21

<Roasted>

it sits at the ubuntu screen for a long, long time, and errors out to the nbd error

17:21

and below is initramfs

17:21

<john_s>

vagrantc: I am afraid you are going to kick me

17:21

<Roasted>

its REQUIRED to reboot the server after build-image, right

17:21

<vagrantc>

john_s: i don't do kicks, only throws

17:21

Roasted: no

17:21

<Roasted>

oh

17:21

<vagrantc>

Roasted: the thin client

17:21

<john_s>

aikido?

17:22

<Roasted>

I did a build-image then update-image on my server

17:22

<vagrantc>

john_s: yes :)

17:22

<Roasted>

and rebooted the thin client

17:22

and yet no dice

17:22

<john_s>

how did I guess

17:22

:-)

17:22

<vagrantc>

speaking of which, i'd best go soo

17:22

n

17:23

<john_s>

vagrantc: thanks you very much for your help. I realized that I didn't append --arch="i386" to my client rebuild

17:23

<Roasted>

vagrantc, is that an error you ran into before??

17:24

<john_s>

vagrantc: gomen nasai!

17:25

<vagrantc>

Roasted: i've heard it, but don't use NBD much (debian defaults to using NFS)

17:26

john_s: the i386/amd64 thing is all sorts of confusing...

17:26

<john_s>

vagrantc:works now!

17:27

<vagrantc>

john_s: glad to hear it!

17:27

<john_s>

vagrantc: I agree, I like it for memory support. I used to use big-mem kernal.