After a few days of trying to get this working with a hardy upgrade and
making a total mess of things, I thought I would share how I fixed it -
for anyone else struggling like I did.
Assuming https://wiki.ubuntu.com/DebugLocalDev has been followed and
Step 4 fails...
1: Make sure your client
oops...
above sudo cp /etc/apt/sources.list /opt/ltsp/i386/etc/ should read:
sudo cp /etc/apt/sources.list /opt/ltsp/i386/etc/apt/
sorry to anyone copying n pasting.
--
Local devices don't work because an X11 authentication problem
https://bugs.launchpad.net/bugs/160420
You received this bug
fixed in hardy with ltspfs_0.5.0~bzr20080109
** Changed in: ltsp (Ubuntu)
Status: New = Fix Released
--
Local devices don't work because an X11 authentication problem
https://bugs.launchpad.net/bugs/160420
You received this bug notification because you are a member of Ubuntu
Bugs, which
SZABO Zsolt's patch to $client/usr/share/ldm/rc.d/S20-delayed-mounter
and /usr/sbin/ltspfsmounter should be implemented.
It is an arbitrary and hard-to-find bug to NOT be able to use ssh -X to
the server - and Seriously Ugly.
Andy
--
Local devices don't work because an X11 authentication
Giovanni (and others),
Could you please enlighten me about the proposed procedure (` .. so
don't login with 'ssh -X user' .. `). How can I prevent this from
happening; which files need to be patched?
The bug starts to be real problem (we are working around it since gutsy
got releases).
Thanks,
@Ronald
It means if you log in into your LTSP server to do administration tasks,
you should do it with a command like this ssh [EMAIL PROTECTED] instead
of ssh -X [EMAIL PROTECTED]. Also you should check the X11Forwarding
option isn't enabled in your ssh server (it's disabled by default).
BTW,
Hello,
I still have some problems with local devices as described in
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/172540 (local
devices not working - LTSPFS_TOKEN not set) but I can confirm what Alex
Magaz found:
--
Alex Magaz wrote on 2007-11-15:
I discovered it always fails when
@stephan-e
Ok, it got it also. ltsp-update.image was needed. Thank you.
Bot some mysterious things remain. USB-Sticks (most important) and CDRoms work.
But i was not able to access the floppy. Without above changes still the first
user could see
and open a inserted floppydisk. With these
the missing desktop links are caused by the fact that KDE doesnt monitor the
contents of /media/. In gnome gnomevfs uses inotify to watch its contents, it
then just triggers the gnome mechanisms to add new devices.
https://blueprints.launchpad.net/ubuntu/+spec/ltspfs-virtual-hal-devices
I finally got some time to test again, and now all works without
problems.
But, out of curiosity, I've been trying to make it fail to find the
cause of the problem. After some tests, I discovered it always fails
when you are logged into the server with ssh -X . I was always logged in
when
@Alex Magaz and stephan-e
I've tested this yesterday only shortly (only made the changes and boot one
client), this
doesn't solve my problem. But maybe i have to do an ltsp-update-image or reboot
the server itself.
I'm also not sure that these env-setting is bad, cause when doing xforwarding
@gerbra
ltsp-update-image is needed because a file under /opt/ltsp/i386/ is
modified.
We applied the two modifications upon 20 servers and 215 PC this monday.
It's seems ok.
My problem perhaps is another (some poster in this thread mentioned that also):
local devices worked perfectly for the
i had the same problem , and commenting out the DISPLAY variable and
adding the -X to the delayed mount script solved the problem
--
Local devices don't work because an X11 authentication problem
https://bugs.launchpad.net/bugs/160420
You received this bug notification because you are a member
i had the same problem , and commenting out the DISPLAY variable and
adding the -X to the delayed mount script solved the problem
--
Local devices don't work because an X11 authentication problem
https://bugs.launchpad.net/bugs/160420
You received this bug notification because you are a member
@stephan-e: what modifications do you mean? The link you posted above leads to
a message that is not releated to
this discussion.
Could you detailed explain what you modified?
And yes, i have also this bug.
Why has this bugreport such a low importance?
And why is is since ~7 days not assigned
I've been swamped at work after returning from UDS, I'll have a look at
this this week.
Scott
** Changed in: ltsp (Ubuntu)
Assignee: (unassigned) = Scott Balneaves (sbalneav)
--
Local devices don't work because an X11 authentication problem
https://bugs.launchpad.net/bugs/160420
You
@gerbra: If I'm not wrong, this is the correct link
http://article.gmane.org/gmane.linux.terminal-server.general/22270
After doing the modifications, I've finally got the pendrive mounted
under /media/maikel!!! Although I had to mount it manually and no icon
appeared on the desktop. I will do
Here are the modifications :
From: SZABO Zsolt [EMAIL PROTECTED]
Subject: Re: ltsp5: floppy as localdev
Newsgroups: gmane.linux.terminal-server.general
Date: 2007-11-07 15:29:25 GMT (4 days, 5 hours and 5 minutes ago)
On Wed, 7 Nov 2007, SZABO Zsolt wrote:
--- s10-delayed-mounter 2007-10-04
I think that the bug I filed some days ago
(https://bugs.launchpad.net/bugs/158989) is the same as the one here discussed.
Maybe the older one can be closed.
--
Local devices don't work because an X11 authentication problem
https://bugs.launchpad.net/bugs/160420
You received this bug
It's ok ; after the two modifications explained, don't forget ltsp-
update-image, reboot server and PC.
--
Local devices don't work because an X11 authentication problem
https://bugs.launchpad.net/bugs/160420
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Very interesting :
http://news.gmane.org/gmane.linux.terminal-server.general/cutoff=22279
I tried, it seems to work ! I'll do more tests tomorrow
--
Local devices don't work because an X11 authentication problem
https://bugs.launchpad.net/bugs/160420
You received this bug notification because
I am getting the same problem with Gutsy using Thin Clients (PC)
Immediately after a default installation or after doing updates, same
result :
- the first user connected use usb stick without problem
- when a second user logs in, his usb stick is not mounted automatically
- if the first user
I too am getting the same problem, The last step in DebugLocalDev file
ends in:
X connection to localhost:10.0 broken (explicit kill or server shutdown).
Error: /tmp/.maikel-ltspfs/usbdisk-sdb1 is not mounted
This is somewhat different, since I dont get the X 11 Connection
rejected. The only
I've straced the ldm process while login (snipped attached). I've found
that process 4092 (I suppose it's ssh) execs xauth which fails with this
message unable to generate an authority file name.
** Attachment added: ldm.strace.snip
http://launchpadlibrarian.net/10309462/ldm.strace.snip
--
To be sure I was not doing something wrong, I disabled two of the four
server's interfaces to avoid bug #159526. After this, I did a default
edubuntu installation, which finished without any errors. The only thing
I did after booting the machine, was adding a new user with users-admin
(all
Hi.
I got the same thing with Gutsy. It does pick up the usb device on a
single station but not on others and the station that works is not the
same that did yesterday.
--
Local devices don't work because an X11 authentication problem
https://bugs.launchpad.net/bugs/160420
You received this
If it helps someone, the Warning: No xauth data... message is from the
ssh command in spawn_ssh(). It doesn't find the .Xauthority file, but
why?
To be sure, I've tried to run the below command from a thin client text
console and it worked. Also, as expected, if I remove the file
27 matches
Mail list logo
