IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 12 July 2009   (all times are UTC)

00:41Ahmuck_ has quit IRC
00:45Ahmuck_ has joined #ltsp
00:54
<Ahmuck_>
chroot /opt/ltsp/i386 aptitude install package_name
00:54
ltsp-update-image
00:54
k, i've done this
00:55
and LOCAL_APPS_MENU=true in lts.conf
00:55
create /var/lib/tftpboot/ltsp/i386/lts.conf
00:55
this as well
00:55
however i don't see the apps on the thin client menu, nor are they on the server menu
01:01
<cyberorg>
Ahmuck, here is how we install localapps http://en.opensuse.org/LTSP/Localapps
01:02
Ahmuck, with http://en.opensuse.org/LTSP/Localapps application icon in the menu launches localapp and not the one on the server
01:02
*with LOCAL_APPS_MENU=true in lts.conf
01:07
<Ahmuck_>
ltsp-update-image should be run at the very last, even after the lts.conf
01:07
cyberorg: thx for the info and links. i've considered suse ltsp (kiwi) for a number of reasons
01:08
problem is, when i tried to install it via virtualbox, it failed on the install, so i did not look at it again
01:08
<cyberorg>
Ahmuck, it does not matter as lts.conf is fetched over tftp
01:08
<Ahmuck_>
i'll re-consider it
01:09
<cyberorg>
Ahmuck, next time you try use li-f-e DVD, it has ltsp pre-installed/configured
01:09
<Ahmuck_>
well, the /opt/ltsp/i386/eetc/lts.conf file suggest that one needs to ltsp-update-image after anything changes in the lts.conf
01:09* Ahmuck_ goes to search for life DVD
01:09
<cyberorg>
do not change that file, do the one in tftpboot folder
01:10
http://en.opensuse.org/Education/Live
01:12
<Ahmuck_>
what is on the edu dvd ?
01:12
i noticed a sugar cd as well
01:14
<cyberorg>
edu-desktop dvd li-f-e without LTSP, LAMP, sugar etc, li-f-e is all in one distro :)
01:14
<Ahmuck_>
let me rephrase the question. is the edu cd/dvd the same as all the other distros?
01:15
k, there is edu, then ltsp unstable, and sugar
01:15
<cyberorg>
ltsp one just hast ltsp, nothing extra, same with sugar, it comes with sugar only
01:16* cyberorg thought the names/sizes were obvious enough :)
01:17
<Ahmuck_>
it's 1:30 am
01:17
nothing's obvious at this hour :(
01:17
<cyberorg>
ah, that explains :D
01:18
<Ahmuck_>
so, there is a dvd that has all three?
01:18
ah, edu-deskto
01:18
er, desktop
01:18
all in one ?
01:18
<cyberorg>
i think you are also done configuring localapps, it should just work in the morning, just change lts.conf in the tftpboot folder
01:19
"li-f-e is all in one distro"
01:19
<Ahmuck_>
well, i thought i was too, but i booted the thin client, and no menu change
01:19
i'll try again
01:19
<cyberorg>
when you download, the image that is biggest has everything in it ;)
01:22
<Ahmuck_>
k, i suppose i'll report as a bug, the /opt/ltsp/i386/etc/lts.conf doc suggests looking in /usr/share/doc/ltsp-client/examples/lts-parameters.txt.gz for valid options, however, there is no /usr/share/doc/ltsp-client folder
01:27japerry_cat has quit IRC
01:27
<Ahmuck_>
i'll be reporting as well, volume control playback is using the server card for playback rather than the client card. i would have expected ltsp server to detect the client card (as it appears to) and pass the sound to the client sound card. is this the SDL issue perhaps? the ltsp server is trying to send the sound through the network rather than using the clients sound card?
01:27japerry has joined #ltsp
01:29
<Ahmuck_>
cyberorg: in suse, the apps are not on the same menu, but on a separate menu where you click a local apps button?
01:29
"pass the sound function to the client sound card"
01:29
<cyberorg>
Ahmuck, i think they are on same menu on all distros
01:30
<Ahmuck_>
so, the application menu should have the "localapps" under applications --> graphics --> blender, etc?
01:30
assuming ur using gnome
01:31
<cyberorg>
no, if firefox is installed as localapps, clicking on firefox in the main-menu will launch local firefox
01:31
if you have LOCAL_APPS_MENU=true in lts.conf, without that it will start firefox on the server
01:33
<Ahmuck_>
hrm, i have that, however, i did "chroot /opt/ltsp/i386 aptitude install package_name" and installed the package, but it does not show up on the menu on the server or the client
01:33
i watched it install
01:34fotanus has quit IRC
01:36
<Ahmuck_>
odd, the programs are there ... /opt/ltsp/i386/usr/games/ri-li
01:37fotanus has joined #ltsp
01:39
<Ahmuck_>
hrm, i'm way to tired now. i'm going home ... i get the impression that local apps is broke on ubuntu
01:39
i can see the programs there, but nothing works, even from the command line
01:40
<cyberorg>
then use "ltsp-localapps appsname" to launch it
01:53japerry has quit IRC
01:56
<Ahmuck_>
um, that worked
01:56
so now i'm confused
01:56
why is the server still serving up the "server" menu rather than the localapps menu
02:13
how odd. launching firefox does from server and i get out on the inet. launching as a localapp, and it's dead to the world
02:20fotanus has quit IRC
03:27Ryan52 has quit IRC
03:30Ryan52 has joined #ltsp
04:36ogra has quit IRC
04:36ogra has joined #ltsp
04:55try2free has joined #ltsp
05:32pmatulis has joined #ltsp
06:16F-GT has quit IRC
07:00ogra_ has joined #ltsp
07:04ogra has quit IRC
07:06F-GT has joined #ltsp
08:27try2free has left #ltsp
08:44Sarten-X[bikinis has quit IRC
08:56yanu has quit IRC
08:57yanu has joined #ltsp
09:00Sarten-X has joined #ltsp
09:01Diablo22 has joined #ltsp
10:37Diablo22 has quit IRC
11:35ltspbot has joined #ltsp
11:38leio_ has joined #ltsp
11:47lucascoala has quit IRC
11:52leio has quit IRC
11:58Egyptian[Home] has quit IRC
11:59Egyptian[Home] has joined #ltsp
13:29alkisg has joined #ltsp
13:54
<GGD>
is the fedora guru here?
13:57lucascoala has joined #ltsp
14:01vagrantc has joined #ltsp
14:34fotanus has joined #ltsp
15:12bobby_C has joined #ltsp
15:47
<GGD>
is the fedora guru here?
15:47
i have a question for him
15:52* vagrantc doesn't see warren
15:53
<GGD>
has he been here?
15:54
<Ryan52>
!seen warren
15:54
<ltspbot>
Ryan52: warren was last seen in #ltsp 1 week, 3 days, 23 hours, 19 minutes, and 14 seconds ago: <warren> g
15:54
<Ryan52>
GGD: ^----
15:56
<GGD>
oh ok
15:56
i didn't know
15:56
thanks
16:02
<Ryan52>
tho he's around and talking in another channel...not that I'm suggesting you bother him. :)
16:03* Ryan52 doesn't know whether or not he would get annoyed
16:31alkisg has quit IRC
16:33sepski has quit IRC
16:50jimi_ has joined #ltsp
16:51
<jimi_>
Is it possible to have a wifi thin client?
16:57
<klausade>
jimi_: no. bandwidth to bad and no wifi cards doing pxe. but you can "cheat" it by having a small local install that does wifi, and use simple xdmp or FreeNX, or vnc to connect to the server.
16:58
<jimi_>
I figured there wasnt any. Was just hoping to convert a few of these 2-3 year old machines that are wifi
16:59
<klausade>
jimi_: if they have a harddrive, then just install your favourite OS, and use some client to connect.
17:00
<jimi_>
klausade, hmm , i could do that, then i really dont need a terminal server running if i use xdmp
17:05Ahmuck_ has quit IRC
17:07Ahmuck_ has joined #ltsp
17:08
<klausade>
jimi_: you don't need a boot-server, you just need a server to log into.
17:08Ahmuck_ has joined #ltsp
17:09
<jimi_>
klausade, yeah , thats what imeant
17:12
<klausade>
jimi_: you could probably use thinstation. i used that sevaral years ago when I need 30 laptops to become wireless thinclients. we put support for wpa into thinstation, which we needed and thinstation didn̈́'t have at that time. that setup is still working today.
17:13
<jimi_>
haven't used thinstation before, is that the one that runs on java?
17:15
<klausade>
jimi_: no. have a look at http://www.thinstation.org/
17:16
<jimi_>
hmm
17:16
brb
17:16jimi_ has quit IRC
17:25bobby_C has quit IRC
17:42jimi_ has joined #ltsp
17:43
<jimi_>
klausade, back, so thinstation is a linux os, can you run it as is without connecting to a windows / linux server?
17:52vplug has joined #ltsp
17:53vplug has left #ltsp
18:00
<klausade>
jimi_: yes, it's a very very small linux os. it doesn't do much on it's own. mostly meant to just get some kind of client running, like rdesktop, ssh, freenx, ica, xdmp.
18:00
<jimi_>
ah ok, n/m
18:00
I will run thinstation in a VM then, and just pass it through to an already running/ installed / configed version of windows
18:06cliebow has joined #ltsp
18:09vagrantc has quit IRC
19:01pmatulis has quit IRC
19:18Faithful has quit IRC
19:33cliebow has quit IRC
19:40vagrantc has joined #ltsp
19:44GGD is now known as GGD_away
19:48jimi_ has quit IRC
20:12|Paradox| has quit IRC
20:12|Paradox| has joined #ltsp
20:20ooi has joined #ltsp
20:20|Paradox| has quit IRC
20:21ooi is now known as |Paradox|
20:24try2free has joined #ltsp
20:24try2free has quit IRC
20:49jim1 has joined #ltsp
20:49
<jim1>
hello!
20:50
i am having a problem connecting a thin client to a ltsp server...
20:58
<sbalneav>
Evening all
21:00
jim1: You might get more responses if you actually describe what the problem is
21:01
<jim1>
ahh yes... thank you... i was waiting for someone to reply... allow me to elaborate
21:03sene has joined #ltsp
21:14
<jim1>
I am running Ubuntu 9.04 Desktop with a double nic configuration and LTSP. I subnetted a block of internal IPs and can ping the entire network from the ltsp server. The ltsp server has full internet connectivity. The thin is a desktop PC that I recently stripped down with the intention of using it as a thin media pc in the living room. All Ethernet cards are linksys eg1032 gigabit adapters. When I boot the thin client, it acquires a
21:16
In troubleshooting I have updated the LTSP kernel, image and sshkeys any time I made any change to the configuration files
21:17
<sbalneav>
Sorry, your description was cut off after "it acquires a"
21:17
<jim1>
When I boot the thin client, it acquires an IP in the proper subnet, loads the Ubuntu splash screen and crashes with, "[62.760503] Kernel panic - not syncing: Attempted to kill init!" I am very familiar with Linux, but I am by no means an expert. I have researched this problem on the forums and other linux/ubuntu websites. I have yet to find a solution that works. Since I am new to LTSP, I researched the software and mainly followed
21:19
im sure that I am missing something small and simple... but I have no clue as to where to look first
21:19
<sbalneav>
Simplest would be first to eliminate the graphical splash screen.
21:20
cd /var/lib/tftpboot/ltsp/i386/pxelinux.cfg
21:20
edit default
21:20
remove the "quiet splash"
21:20
that will allow you to see what exactly's going on at boot.
21:21
<jim1>
thank you for the tip!
21:22
<sbalneav>
Do you have a firewall on the machine?
21:23
LTSP uses a nbd to mount a compressed root image
21:23
<jim1>
my firewall is configured on my router
21:23
<sbalneav>
it might be being blocked by a firewall, if you have one.
21:23
Ok, so nothing on the machine then.
21:24
What does the boot say, with the "quiet splash" removed?
21:26evilx__ has joined #LTSP
21:29
<Ahmuck_>
it's a video problem i bet
21:29
sbalneav: u familiar with localapps
21:30
<jim1>
The last thing it does before giving an error is load the USB driver for the mouse. After that:
21:30
IP-Config: no response after 60 secs - giving up
21:30
/init: .: line 1: can't open /tmp/net-eth0.conf
21:30
then the kernel error
21:32
I am not familiar with localapps... i have been using ubuntu for about two years though so I have become pretty familiar with editing files and I am sure that I have edited this file/folder before... i recognize the term
21:36
i am running a Galaxy GeForce 8400 GS in the server with a dual monitor configuration with 2 Panasonic S110i... the client is running a Chaintek GeForce FX5200 with a single monitor, a Samsung SyncMaster997DF... all are VGA...
21:37
all Nvidia drivers are up to date on the server
21:39
<sbalneav>
Sounds like it could be video related.
21:40
Try maybe setting XSERVER = vesa in the lts.conf file
21:40
Ahmuck_: see my responses in #edubuntu
21:42evilx_ has quit IRC
21:43
<jim1>
when I open /var/lib/tftpboot/ltsp/i386/lts.conf - there is nothing in the file, like i'm creating it... just add XSERVER - vesa in the file?
21:43
**XSERVER = vesa
21:44
<Ahmuck_>
yes
21:44
<sbalneav>
Well
21:44
[Default]
21:44
<Ahmuck_>
lts.conf file format is "this=that"
21:44
<sbalneav>
XSERVER = Vesa
21:44
err, vesa
21:44
no cap
21:44
<Ahmuck_>
where "THIS=that"
21:44
no caps?
21:44
ah, no caps on vesa
21:44
<sbalneav>
for vesa
21:45
<Ahmuck_>
sbalneav: ur responses in edubutu on localapps?
21:47
<jim1>
[Default]? I added the lts.conf file to the directory with "XSERVER=vesa" in the context... I rebooted the client twice with no luck
21:47
what does it mean that it cannot open "/tmp/net-eth0.conf"
21:48
<Ahmuck_>
don't you have to rebuild the client image for any change in the lts.conf?
21:48
nm
21:49tex is now known as chupacabra
21:49
<jim1>
im going to run the image through its update processes anyways and give it a shot
21:49
<Ahmuck_>
[default]
21:50
<jim1>
excuse me... but are you asking me to place the text [default] at the beginning of the lts.conf file with "XSERVER=vesa" below it
21:52
<Ahmuck_>
yes
21:53
it appears that if your using the lts.conf in /opt/ltsp/i386/etc/lts.conf that you would need to update the image according to the instructions in the file
21:55
<vagrantc>
use /var/lib/tftpboot/ltsp/i386/lts.conf
21:55
<Ahmuck_>
however, you should be using instead /var/lib/tftpboot/ltsp/i386/lts.conf file
21:56
vagrantc: good thing your hear. lts.conf file is confusing. for one, one file refers to /usr/share/doc/ltsp-client/examples/lts-parameters.txt.gz
21:56
<sbalneav>
Ahmuck_: No, docs
21:56
<Ahmuck_>
*here
21:56
<vagrantc>
lts-parameters.txt.gz is just documentation of the configuration options
21:56
hence, it's location in /usr/share/doc/
21:56
<Ahmuck_>
the other refers to lts_parameters.txt, which using locate comes up with nothing
21:57
ah, the file is wrong. it should be ltsp-server directory
21:57
not ltsp-client
21:57* Ahmuck_ shakes head a bit
21:58
<Ahmuck_>
so, i need to file a bug to get it changed?
21:58
<sbalneav>
We're in the midst of re-doing the docs.
21:59
<Ahmuck_>
ah, ok
21:59
<sbalneav>
The file should, really, disappear altogether, and be replaced by the lts.conf.5 manpage.
21:59
<Ahmuck_>
sooo, vagrantc i did that u suggested, however i did not have a local apps menu
21:59
<vagrantc>
ah well, i've only tinkered with local apps ... stgraber and gadi have worked with it a lot more.
22:00
<Ahmuck_>
i was able to launch some local apps using "local-apps appname"
22:00* vagrantc thought it was "ltsp-localapps" for quite some time
22:00
<vagrantc>
perhaps you're using an older version?
22:00
<sbalneav>
Ahmuck_: Are you running Jaunty?
22:01
<Ahmuck_>
sbalneav: yes
22:01
well, intrepid upgrade to jaunty
22:01
vagrantc: yes, ltsp-localapps
22:01
<vagrantc>
Ahmuck_: did you upgrade the chroot as well?
22:01
<Ahmuck_>
i've forgotten what i did at 1:00 am in the morning
22:01
yes
22:02
hrm, upgrade chroot?
22:02
that might be my whole problem with a lot of things. never occured to me
22:03
sudo chroot /opt/ltsp/i386 aptitude safe-upgrade
22:03
No packages will be installed, upgraded, or removed.
22:04
i assume i'm kosher
22:05
so at this point, i assume that the upgrade also upgraded the chroot
22:05
jim1: that work?
22:06
<sbalneav>
Ahmuck_: I'd ditch the chroot, rebuild it.
22:06
Unless you updated the sources.conf in the chroot.
22:06
<jim1>
sorry I got caught up on the phone for a minute and I was just finishing reading what you were saying... i am trying it now
22:07
<Ahmuck_>
ditching the chroot. rm -rf /usr/ltsp_something?
22:07vagrantc has quit IRC
22:08* Ahmuck_ scared vagrantc away
22:08
<sbalneav>
Ahmuck_: mv /opt/ltsp /opt/oldltsp
22:08
<Ahmuck_>
https://help.ubuntu.com/community/UbuntuLTSP/UpdatingChroot
22:08
i assume
22:10
client building now
22:14
<jim1>
yes the client is building now... thank you for the assistance
22:15
<Ahmuck_>
er, that link is 8.04 based. i assume that it applies to 9.04?
22:18
sbalneav: using that method, that link instructs me to re-install any previously installed packages
22:20
<sbalneav>
If you simply move the old one out of the way, and do an ltsp-build-client, you'll get a new jaunty chroot.
22:22
<Ahmuck_>
sbalneav: pm?
22:22
new jaunty chroot, as what's on the server i assume
22:24
<jim1>
I am still getting the exact same error.
22:25
<sbalneav>
pm?
22:26
Ahmuck_: Yes
22:26
<Ahmuck_>
sbalneav: private message?
22:29
<sbalneav>
Sure, if you'd like.
22:30sene has quit IRC
22:33sene has joined #ltsp
22:48knipwim_ has joined #ltsp
22:50
<sbalneav>
!docs
22:50
<ltspbot>
sbalneav: "docs" is For the most current documentation, see http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspDocumentationUpstream
22:53knipwim has quit IRC
22:57
<Ahmuck_>
in your lts.conf file in the appropriate stanza - what is the proper "stanza"
22:57
ie, [default] ?
22:57
stanza == section ?
22:58
<sbalneav>
yes.
22:58jim1 has left #ltsp
23:02
<sbalneav>
Updated the docs.
23:02
<Ahmuck_>
stanza should be replaced with section. i've not heard of stanza before, and it's only used in two places in the docs
23:03
<sbalneav>
Already done.
23:06shogunx has quit IRC
23:10sergiu has joined #ltsp
23:10sergiu has left #ltsp
23:10marks256 has joined #ltsp
23:11
<marks256>
anyone know how to get sound working on an LTSP client? using ubuntu 9.04 x64
23:11
clients are booting an i386 image however
23:11
<sbalneav>
Is it not working at all? Or not working for certain programs?
23:15
marks256: Is it not working at all? Or not working for certain programs?
23:16
<marks256>
sbalneav, not at all. if i mess with the volume on the client, it actually changes the volume on the server.
23:17
<Ahmuck_>
heh, happens here as well
23:18
<marks256>
all the tutorials i've found on the net are either A out of date, or B terrible at explainations.
23:18
<Ahmuck_>
what is NBD swap?
23:19
marks256: tutorials for ltsp?
23:19
NBD_SWAP ... swap space on the server or client?
23:19
<marks256>
Ahmuck, no, tutorials for getting sound to work on the client side.
23:20
<Ahmuck_>
what distro?
23:21
<marks256>
ubuntu 9.04
23:21
<Ahmuck_>
chapter 13 in the ltsp manual
23:21
?
23:22
<marks256>
where is that?
23:22
ltsp website documentation?
23:23
<sbalneav>
marks256: If you open the volume control, and select the device, what options are there?
23:23
<marks256>
sbalneav, i'll check quick. you mean on the client?
23:23
<sbalneav>
Yes, on a client.
23:23
Ahmuck_: What's your question about chapter 13?
23:23
<Ahmuck_>
i've got a amd64 proc with ubuntu ltsp 32 bit installed and intel 32 bit clients. part of my problem?
23:24
sbalneav: nothing, that's where "sound" is
23:24
however i didn't have to "enable" true to get it to work on my network
23:24
but i have strange volume problems
23:24
<sbalneav>
Ahmuck_: NBD_SWAP is swap space on the server.
23:24
<marks256>
sbalneav, i think i see my laptop in there. i'll try to play something quick
23:24
<sbalneav>
SOUND=True by default in Ubuntu.
23:25
<Ahmuck_>
one user listens to something on the client and sound comes out on the server
23:25
<sbalneav>
There should be a pulseaudio device.
23:25
That's the one you want.
23:25
<Ahmuck_>
another user adjusts sound on the client and it changes the server
23:25
etc. etc.
23:26
<sbalneav>
It's probably not picking the remote pulse audio device by default.
23:26
<marks256>
exactly. i have the same problem as Ahmuck
23:26
<sbalneav>
So, like I said, drop down the device selection in the volume control, and select the remote pulse device.
23:27
<marks256>
i've got a pulse audio mixer there. Do i use it?
23:27
i did but it doesnt work.
23:28
<Ahmuck_>
LOCAL_APPS boolean default False should be LOCAL_APPS boolean default false as in LOCAL_APPS=false
23:30
<marks256>
sbalneav, i still can't get it working. no matter what device i choose, no sound
23:31
sbalneav, i'm running x64 server with i386 clients. is that the problem?
23:31
<sbalneav>
Well, the pulseaudio mixer works fine here. I'm not running 64 bit on the server though.
23:31
Maybe, I'd have to test.
23:31
Or, you could just boot a 32 bit server kernel and try, as well.
23:32
<marks256>
sbalneav, i want all the memory in my server to be used though ;)
23:32
<Ahmuck_>
how interesting. user1 shows the server sound card in volume control --> device, whereas user2 shows a muted volume control and does not know there is a sound card and user three shows a intel sound card as an option all on the same machine
23:32
<sbalneav>
That's easy.
23:32
just install the -server kernel
23:32
it's got PAE enabled.
23:33
If it's the case that sound doesn't work in a mixed 64/32 environment, then it's a pulseaudio bug.
23:35
<marks256>
sbalneav, the server kernel will let me use 4+ gigs of ram on a 32 bit os?
23:35
<sbalneav>
Yes.
23:35
That's what I run.
23:36
My machines have 8 gigs of ram.
23:36
<marks256>
sbalneav, how do i do that?
23:37
<sbalneav>
sbalneav@sputnik:~$ uname -a
23:37
Linux sputnik 2.6.24-19-server #1 SMP Wed Aug 20 23:54:28 UTC 2008 i686 GNU/Linux
23:38
sbalneav@sputnik:~$ free total used free shared buffers cached
23:38
Mem: 8308360 1047308 7261052 0 62128 663920
23:38
-/+ buffers/cache: 321260 7987100
23:38
Swap: 2955920 314692 2641228
23:38
sbalneav@sputnik:~$ dpkg -l | grep linux-image-server
23:38
ii linux-image-server 2.6.24.19.21 Linux kernel image on Server Equipment.
23:38
install the package linux-image-server
23:39
that gets you a PAE enabled 32 bit kernel.
23:39
<marks256>
sbalneav, and i install that where
23:39
sbalneav, so basically sound should work by default on the clients?
23:40
<sbalneav>
Should. But those of us who develop for LTSP don't have ready access to 64 bit hardware sometimes, so 64 -> 32 sometimes doesn't get tested as well.
23:41
<Ahmuck_>
hrm, sounds fixed
23:41
or seems to be, and some other issues as well
23:41
<marks256>
Ahmuck, how'd you do it?
23:41
Ahmuck, i haven't been paying attention. :$
23:41
<Ahmuck_>
marks256: i won't know till later this week
23:42
<marks256>
Ahmuck, aww why :)
23:42
<Ahmuck_>
i had a 8.10 --> 9.04 upgrade. i rebuilt my thin client
23:43
<marks256>
Ahmuck, oh. i see.
23:44
sbalneav, i think i have an i386 version of ubuntu 9.04 here, but it is the desktop install. does that include the LTSP install on it, or will i have to do it manually?
23:45Diablo22 has joined #ltsp
23:45
<Ahmuck_>
hrm, and now it's gone
23:47
nn
23:47
<marks256>
Ok i got sound working on a machine (guess my laptops are just picky... i knew it always took extra work to get sound working on them...) but it it really glitchy! :o like... TERRIBLE
23:47
i'm on a 10/100 network though
23:48
<sbalneav>
marks256: No, you'll have to install the ltsp-server-standalone package after the fact.
23:49
<marks256>
sbalneav, ok. i'll still try i386, but sound IS working for me now. but it is really glitchy. any ideas why that may be?
23:49
<sbalneav>
glitchy in *what*? Listening to an ogg?
23:50shogunx has joined #ltsp
23:51
<marks256>
sbalneav, WTF! now it just STOPPED being gltchy! it's working great now... :??:
23:51
<Ahmuck_>
i found my sound problem
23:51
<marks256>
Ahmuck, what was it?
23:51
<Ahmuck_>
or the symtom
23:51
<marks256>
Ahmuck, explain :)
23:51alkisg has joined #ltsp
23:52
<Ahmuck_>
started the program, sound was working, and had five devices listed
23:52
sound was going and i could hear it on the client. then it stopped and i had two devices, both alsa
23:52
<marks256>
Ahmuck, so there are two alsas running?
23:53
<Ahmuck_>
no, i'm not sure what's going on
23:55
<sbalneav>
There will be two devices, the one on the server, and the one on the thin client.
23:55
<marks256>
Now sound just quit working for me. all together.
23:55
<sbalneav>
I'll ask again: in what?
23:55
What are you using to test sound?
23:56
<marks256>
sbalneav, rhythmbox
23:56
<Ahmuck_>
k, logging the client out and back in does not get sound back. rebooting does. in addition, the additional devices are listed upon reboot
23:57
<marks256>
Ahmuck, i think i have the same problem. i had an entire list of devices from all my clients, then all of a sudden only two appeared. So i'm restarting