| derosa | Hi, I have a bug report that got fixed upstream. I know I should request a ¿sync, merge? of the sid package for jaunty. Could anyone mentor me? | 09:41 |
|---|---|---|
| derosa | It's bug 387743 | 09:42 |
| ubottu | Launchpad bug 387743 in kdeedu "i18n Jupiter's moons applications crash kstars" [Unknown,Fix released] https://launchpad.net/bugs/387743 | 09:42 |
| derosa | Sorry, wrong bug, I mean bug 115416 | 10:01 |
| ubottu | Launchpad bug 115416 in ktechlab "crash when selecting a component (happened at least 5 times with differnet compounts)" [Medium,Confirmed] https://launchpad.net/bugs/115416 | 10:01 |
| derosa | It's going to be fixed in karmic, but I think it should be in jaunty-updates, as the bug renders the program unusable | 10:02 |
| ogra | derosa, write that in the bug report and follow the SRU process | 10:03 |
| ogra | http://wiki.ubuntu.com/StableReleaseUpdates | 10:03 |
| derosa | I will, thanks | 10:04 |
| burbas | Hi! I have a little problem with a USB->Serial-adapter on a thin client. How can I map this device to the ltsp-servers /dev? | 10:26 |
| ogra | you cant | 10:37 |
| ogra | use whatever you use to access the serial port as localapp | 10:37 |
| burbas | Okay. Which is the best way to do this? Just run ltsp-localapps "programname" /dev/mylocaldevice ? | 10:41 |
| ogra | what do you want to run exactly ? | 10:41 |
| ogra | /dev/mylocaldevice should be set in the config of the app | 10:42 |
| burbas | I have a program that collects data from a device conncted to the thin-clients serialport. This app takes the port as an argument. | 10:42 |
| ogra | i'm not sure ltsp-localapps hands over arguments, try it :) | 10:43 |
| burbas | Okay :). Thanks for the tips anyway | 10:43 |
| ogra | if it doesnt work, just put a script in place that calls it with the arg | 10:43 |
| burbas | Hmmm.. If I run a program with ltsp-localapps, does the std-devices (stdout, stderr) be pointed to the terminal that im running from or some kind of pseudo-shell? | 10:57 |
| burbas | nm. The bufferts was redirected :)) | 11:33 |
| Dynamit | hello i want to start edubuntu on one computer but when i doe's i get this error image to large for low memmory ...... how can i fix this problem | 15:30 |
| Dynamit | but an virtual pc whit 512 mib ram work but not this old computer | 15:33 |
| Dynamit | that i want to boot edubuntu on | 15:33 |
| cberlo | Hi folks. Maybe I'm just missing a key piece of documentation somewhere, but can anyone tell me how to configure my Edubuntu LTSP server with a static IP on eth1? | 19:44 |
| cberlo | ...and this would be on a Jaunty Jackalope install... | 19:45 |
| cberlo | NetworkManager seems to kick in after a while and kills my configuration. I've edited /etc/network/interfaces and put in a 192.168.0.1 address for eth1, but after the DHCP server has been started, NetworkManager seems to be requesting an address (for eth1 itself??) and I wind up losing the configuration on that NIC altogether. | 19:46 |
| cberlo | Anyone? | 19:46 |
| alkisg | cberlo: upload your /etc/network/interfaces to pastebin | 19:46 |
| cberlo | Been a while here... what's the pastebin address? | 19:47 |
| alkisg | pastebin.ubuntu.com | 19:47 |
| cberlo | http://pastebin.ubuntu.com/197915/ | 19:49 |
| cberlo | eth0 is automagically configured through DHCP on my external network through NetworkManager. | 19:49 |
| alkisg | cberlo: uh, Networkmanager should _not_ be managing eth1, since it's declared in the interfaces file | 19:50 |
| alkisg | So if you left click on its panel applet, it should be saying "eth1 - not managed" | 19:51 |
| cberlo | Yep, that's about what I figured. So..... is there a way to manually stop it from doing that? It does show up when I view network connections through NetMgr. | 19:51 |
| alkisg | cberlo: have a look at /etc/NetworkManager/system-connections/, I've seen NM screwing up the connection files a lot of times, maybe it's a similar bug. | 19:53 |
| cberlo | Okay, will check that. I did have some issues getting the basic install going (bad CD-ROM drive) so maybe something get installed in a way I didn't intend... | 19:54 |
| cberlo | I suspect solving issue #1 here will solve issue #2 (which I haven't mentioned yet): can't login from a client after mucking with IP address and dhcp stuff manually. | 19:54 |
| alkisg | cberlo: maybe you could also try apt-get purge network-manager - to completely remove it's settings, and reinstall it... don't know. | 19:55 |
| alkisg | Yeah, solve the #1 issue first and you can look at #2 later | 19:56 |
| cberlo | Strange. No references there, either. 192.168.0.1 is briefly configured, then gets "unconfigured". | 19:56 |
| alkisg | Maybe it's on a "user" connection, not on a "system" connection. | 19:57 |
| alkisg | I.e. on your home dir, let me find it... | 19:57 |
| cberlo | Did find an auto config within NM that said "Automatic Ethernet" and another called "Auto eth0" -- I want the Auto eth0, but I just deleted the other. Let's see what happens... | 19:59 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!