Is Chromium the only thin-client application making trouble?
If you open a terminal window on the thin-client (not the
server), do you get any response from ping 8.8.8.8? If not,
then the problem is a general networking issue and the following
link may be of interest:
On 09/02/2012 08:05 PM, Robert Lefebvre wrote:
Could someone please explain to me how to go about fixing the error when
booting the client and it reports
TFTP prefix: /ltsp/i386/
Trying to load: pxelinux.cfg/default
Could not find kernel image: vmlinuz
I can see vmlinuz at the root level
NAT works for me under Ubuntu 12.04, and I'll gladly share what I know.
Interventions from experts with more knowledge and/or confidence would
still be welcome.
It may be helpful to split the problem into two steps. First is getting
NAT to work at all, and connecting a thin client to the
On 06/13/2012 03:31 AM, Jan Middelkoop wrote:
And that concludes this drive-by introduction to pulseaudio in LTSP. As
for the specific problem you're having - the question you should be
asking yourself is: what have you changed since the last time you ran
ltsp-update-image? My experience is
On 06/13/2012 10:39 AM, Richard Doyle wrote:
E: [pulseaudio] module-console-kit.c: GetSessionsForUnixUser() call
failed: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute
program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
E: [pulseaudio] module.c: Failed to load module
that
the pulseaudio daemon needs to run on both machines in order for sound
to flow between them.
Gratitude now; further details later. - Philip
On 06/13/2012 03:31 AM, Jan Middelkoop wrote:
On 13-06-12 08:28, Philip Loewen wrote:
Unfortunately I don't really understand how pulseaudio is supposed to
work
This week I broke the sound system on my home LTSP network. Can anyone
suggest repairs?
Ubuntu LTSP relies on pulseaudio, which is not running on either the
server or the thin clients (TCs). Trying pulseaudio -v on the TC
gives lots of lines: here are ones describing errors, with a few lines
On 06/12/2012 11:47 PM, David Burgess wrote:
On Wed, Jun 13, 2012 at 12:28 AM, Philip Loewenphi...@tidepool.ca wrote:
Ubuntu LTSP relies on pulseaudio
It doesn't have to. We found better performance by disabling
pulseaudio by simply using the 'SOUND=False' option in lts.conf (on
the past
Here is an account of a learning/troubleshooting experience that
Google may some day find for the help of others.
Today I upgraded my home LTSP server to Ubuntu 11.10 using Ubuntu's
built-in command-line distribution upgrade tool, then worked through the
suggestions on the web page at
On 11-01-08 06:38 PM, Jam wrote:
On Sunday 09 January 2011 07:31:29 ltsp-discuss-requ...@lists.sourceforge.net
wrote:
But if you have some (thin) clients that see the internet and some (fat)
others that don't, then it's likely that your server settings are fine
and it's your fat clients that
Thanks, Gadi. Some terse replies appear below. - Philip
On 11-01-06 04:04 AM, Gideon Romm wrote:
Perhaps restarting X is bit what you want. Would this approach work
Install the bluetooth GUI in the chroot.
I had this in position before posting. It's how I got bluetooth pairing
in the
My server is connected to the internet through one interface, and to the
in-house subnet where LTSP clients live through a second interface. So I
had to run through steps like the ones you quote *on my server*; my
reference for this was
http://www.revsys.com/writings/quicktips/nat.html
But
I'm trying to get my new Apple Magic Trackpad to work with an LTSP
Client served from Ubuntu 10.10. Bluetooth pairing is giving me trouble,
because Ubuntu has chosen a modern bluetooth stack in which there
seems to be no known way to achieve a pairing without using a GUI. I
have figured out
Thank you very much for taking an interest. I replied immediately, with
the requested files in attachments, but it seems that my response never
got posted. (Perhaps the attachments got it rejected?) Your questions
stimulated further thinking, experimentation, and progress (yay!). Now I
have
Fantastic. This works. Now I can, too. ;)
(xrandr still says LVDS1 connected, but it's not sending LVDS1 any signal.)
Thank you very much!
On 10-12-12 09:52 AM, Gideon Romm wrote:
Try:
[00:01:2E:2C:AF:3E]
XRANDR_OUTPUT_0 = VGA1
XRANDR_MODE_0 = 1680x1050
XRANDR_OUTPUT_1 = LVDS1 --off
LTSP is really super. I have a multi-user setup in my house, installed
just days ago, and there is just one issue between me and thin client
perfection.
The fonts and pictures on my thin client are not as sharp under LTSP as
when the client hardware is just running its own copy of Linux. Can
16 matches
Mail list logo
