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


Channel log from 23 April 2010   (all times are UTC)

00:00epaphus has quit IRC
00:06mischko has quit IRC
00:18try2free has joined #ltsp
00:24try2free has left #ltsp
00:34alkisg has joined #ltsp
01:06Egyptian[Home] has quit IRC
01:08map7 has quit IRC
01:13vagrantc has quit IRC
01:21Egyptian[Home] has joined #ltsp
01:43
<gnunux>
hi
01:49Kicer86 has joined #ltsp
02:27
<jonkke>
Hello
02:32alkisg has quit IRC
02:37ogra_cmpc has quit IRC
02:39ogra_cmpc has joined #ltsp
02:50
<Kicer86>
hi johnny
02:51
tfu jonkke
02:51
;)
03:03alexqwesa_ has quit IRC
03:03alkisg has joined #ltsp
03:19vmlintu has joined #ltsp
03:32alexqwesa_ has joined #ltsp
03:40
<jonkke>
Kicer86: tfu?
03:46
<Kicer86>
ah polish word ;P
03:46
i never how to say it in english ;)
03:47
you say it when you say something wrong ;) what you didn't mean to say
03:48
<jonkke>
ok :)
03:52ogra_cmpc has quit IRC
03:53ogra_cmpc has joined #ltsp
04:11alkisg has quit IRC
04:33
<jonkke>
anyone remember anything about ltsp 4.2?
04:36
server1 has: working ltsp4.2 enviroment and dhcp server.
04:36
server2 has another ltsp4.2.
04:36
i'm trying to push one client to server2, with dhcpd.conf "next-server" attribute. it loads pxelinux.0, bzImage and initramfs.gz from server 2, but then starts enviroment from server1. do i need more setting to force one client to enter test enviroment
04:37
:)
04:40
always nice to ask help from someone. just asking helps :)
04:40
i need option root-path attribute too
04:40
thanks for help :P
05:31Faithful has quit IRC
05:45Faithful has joined #ltsp
05:51highvoltage has quit IRC
05:54highvoltage has joined #ltsp
06:07hersonls has joined #ltsp
06:22pmatulis has joined #ltsp
06:24Kicer86 has quit IRC
06:25Kicer86 has joined #ltsp
06:32multikatt has joined #ltsp
06:34alkisg has joined #ltsp
06:34
<multikatt>
Hey! I'm setting up a ltsp cluster enviroment but i'm having trouble getting cronjobs working on the thin clients. I'm trying to follow the guide on https://help.ubuntu.com/community/UbuntuLTSP/AutomatedTCShutodwn
06:35
Nothing at all happens when i try to just add a cronjob in the webgui and i can't use lts.conf as it's appearantly not in use when running ltsp cluster
06:36
any ideas?
06:38
<Appiah>
it is used
06:38
just edited somewhere else
06:41scottmaccal has joined #ltsp
06:50
<multikatt>
ok, thanks. But i'm trying to follow this https://help.ubuntu.com/community/UbuntuLTSP/ChrootCronjobs. But if i run ltsp-localapps xterm and in that xterm run getltscfg CRONTAB_01, shouldn't that give me my crontab entry?
06:50
i get nothing, same thing with getltscfg -a
07:00alkisg has quit IRC
07:01
<multikatt>
disregard that; when i run getltscfg -a or getltscfg [whatever] i get syntax error in /etc/lts.conf, line=1
07:02
first line of /etc/lts.conf on the thin clients is RCFILE_02 = /etc/ltsp/crontab.sh
07:14scottmaccal has quit IRC
07:19garymc has joined #ltsp
07:20alkisg has joined #ltsp
07:20
<garymc>
Hi, Ive been asked to add a user to our ltsp server ubuntu version. I can access via putty but I forgot the command to add a user. Any know it? ive tried addusr adduser etc etc
07:21
<multikatt>
useradd?
07:21
<alkisg>
sudo adduser
07:21
<garymc>
it says only one of two name allowed when I type that
07:21
<alkisg>
(adduser is preferred to useradd on debian-based systems)
07:21
Can you paste the whole "conversation"?
07:22
!pastebot
07:22jammcq has quit IRC
07:22
<ltspbot`>
alkisg: "pastebot" :: The LTSP pastebot is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebot, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
07:24
<garymc>
yeah i needed to do "sudo adduser Jeff"
07:24
i was missing the jeff bit
07:24
thanks guys
07:24garymc has quit IRC
07:26komunista has joined #ltsp
07:28
<komunista>
hi all
07:37
<multikatt>
hey
07:38
i got that lts.conf thing working, didn't know you had to put [Default] in the top of the file. Thanks all!
07:45alkisg has quit IRC
07:49epaphus has joined #ltsp
07:56epaphus has quit IRC
07:59ogra has quit IRC
08:00ogra has joined #ltsp
08:07ogra_cmpc has quit IRC
08:08ogra_cmpc has joined #ltsp
08:11Gadi has joined #ltsp
08:33cliebow has joined #ltsp
08:43
<komunista>
please, exist some howto/guide to swap from NFS to NBD on Debian?
08:44
<cliebow>
that would be vagrantc's bailiwick..I dont think debian is up to speed on that..yet
08:49
<komunista>
hmm, I execute ltsp-update-image, and I see that pxe config was updated, inetd too and client properly boot - with nfs and portmap stopped...
08:52vmlintu has quit IRC
09:05
<munson>
ya not sure the resason why that happens cuz i done the same thing and my pxelinux.cfg/default when back to its default
09:05Lumiere has quit IRC
09:05
<munson>
when=went
09:07Lumiere has joined #ltsp
09:11epaphus has joined #ltsp
09:12cyberorg has quit IRC
09:16
<Gadi>
if you use nfs, you should never run ltsp-update-image
09:16
it is only for nbd (where there is an image in need of updating)
09:18
komunista: there is no swap over nfs anymore - only swap over nbd. for this to work, there should be an nbdswapd entry in you /etc/inetd.conf and your inetd service should be running
09:19
also, NBD_SWAP=True in lts.conf
09:20cyberorg has joined #ltsp
09:20
<munson>
hmm
09:21
thx for info i was wondering why lol
09:21
<komunista>
Gadi: thanks, I know about NBD swap usage, but I want try NBD boot in debian
09:22
<munson>
anyhow what lines do i need to put into my pxelinux.cfg/default to make these thin clients boot to seperate hd /dev/sdb1 which is windows xp partition
09:23
<Gadi>
http://sourceforge.net/mailarchive/message.php?msg_name=20081106230627.GT8315%40ryukin.fglan
09:25
<komunista>
thanks, I read this some months agou, but I was not success with LTSP 5.0
09:25
now all seems to works
09:25jcastro has quit IRC
09:26jcastro has joined #ltsp
09:29
<komunista>
but thanks for pointing :-)
09:30
<Gadi>
munson: you need to add a menu entry like:
09:30
LABEL local
09:30
<munson>
can pm me if u want
09:30
<Gadi>
MENU LABEL Boot Local Windows
09:30
KERNEL chain.c32
09:30
APPEND hd1 0
09:30alkisg has joined #ltsp
09:31
<Gadi>
you can check out the syslinux website for syntax on menus and such
09:31
<munson>
boot local windows? im using diskless thin clients
09:31
<Gadi>
you just asked: "what lines do i need to put into my pxelinux.cfg/default to make these thin clients boot to seperate hd /dev/sdb1 which is windows xp partition
09:31multikatt has quit IRC
09:32
<munson>
kk iĺl try it bud
09:32
<Gadi>
doesnt sound diskless to me
09:32
:)
09:33
<munson>
the server is the OS hosting and the thin clients are the hp thin client small ass box standard thin client machine
09:33
<Gadi>
ok
09:33
so /dev/sdb1 is on the server?
09:33
<munson>
yup yup
09:33
<Gadi>
you can't just boot random server partitions
09:34
<munson>
damn
09:34
<Gadi>
the clients are downloading a kernel from the server and mounting the image as their OS filesystem
09:34
<munson>
ok do i need to make a ramdisk image or somethin?
09:34
<Gadi>
you could boot /dev/sdb1 in a virtual machine on the server
09:34
??
09:34
are you using LTSP?
09:35
<munson>
ya i have virtualbox but not what i wanted.....yes ltsp
09:35
<Gadi>
so ltsp has done everything for you already
09:35
are the clients booting?
09:35
<munson>
yes to this servers OS
09:35
<Gadi>
not exactly
09:35
they boot the kernel in: /var/lib/tftpboot/ltsp/i386/vmlinux
09:36
er, /var/lib/tftpboot/ltsp/i386/vmlinuz
09:36
<munson>
KERNEL vmlinuz
09:36
APPEND initrd=initrd.img
09:36
<Gadi>
and then they mount the filesystem image in: /opt/ltsp/images/i386.img
09:36
<munson>
ya i got that
09:36
<Gadi>
that's what they boot
09:37
the they ssh into the server and push a display back
09:37
they never actually boot the server OS
09:37
<munson>
sure does look like it loads it up
09:38
<Gadi>
looks can be deceiving
09:38
:)
09:38
<munson>
i mean its goin thru the initial bootup of linux installin the modules and all then xwindows pops up and im on
09:38
<Gadi>
right
09:38
that's all in i386.img
09:39
<munson>
aah ok
09:39
<Gadi>
but after you enter in your username/password, it does an: ssh -X user@server /etc/X11/Xsession
09:39
<munson>
i c....sooo not able to boot to another partiion then w/o making a winxp.img file ? i made one usindg dd if=/dev/sdb1 of=winxp.img
09:39
<Gadi>
and you are running your session on the server
09:40
<munson>
kk
09:41
<Gadi>
bbiab
09:41
<munson>
kk same...bio break
09:46emence has joined #ltsp
09:47
<emence>
how can you add new ltsp users on the latest ubuntu ltsp server?
09:47
<alkisg>
Like in any other ubuntu system. users-admin or adduser
09:47
<munson>
use the useradd i tihnk
09:47
<alkisg>
adduser is preferred to useradd on debian-based systems
09:48
<emence>
the useradd is not creating home directories
09:48
<munson>
oh
09:48
<alkisg>
munson: Windows can't boot on different hardware, so you'd need a different img for each client
09:49
<munson>
so how would i go about making an image for these pieces of crap thin client boxes w/o disk in them
09:49
<alkisg>
Windows image?
09:49
<munson>
ya windows xp for starters
09:49
<alkisg>
OK, you're not in the correct channel for starters :)
09:49
<emence>
when i try and login, i get an unable to update .ICEauthority
09:50
and the desktop hangs
09:50
<munson>
lol u know what i meant hehe...i trying to multiboot ltsp thin clients
09:51
<alkisg>
munson: what you're trying to do is called "boot windows from lan" - multibooting is just a tiny, trivial part.
09:51
You can use AoE, iscsi etc, but all those are not related to #ltsp.
09:51
<munson>
ok ya sounds bout right if its possible using ltsp
09:51
<alkisg>
ltsp is for booting linux
09:51
It can't be used for windows, it's not at all related
09:51
<munson>
figured so but didnt know if it was possible
09:52
<alkisg>
You can use remote desktop and connect to windows servers, but not boot windows
09:52
Lots of people use ltsp for that: boot linux and then use remote desktop to connect to windows 2008 servers etc
09:52
<munson>
well this xp is on seperate partition on this server box
09:52
<alkisg>
Yeah, forget about that, it won't work
09:52
<munson>
kk
09:52
<alkisg>
You can't boot windows from an installed partition on the server
09:53
(not only with ltsp - it's not doable)
09:53
(windows doesn't support that - not even the license supports it)
09:54
<munson>
well damn waisting my time then ;( crap i thought it´d be cool to have menu like grub and choose which OS for these thin clients to boot to
09:55
<alkisg>
I do have a menu for that
09:55
To boot thin clients, fat clients, live cd, hiren's boot cd, recovery etc
09:55
But windows doesn't support booting from a server partition. It's not a menu problem; it's a windows problem.
09:56
<munson>
ya got seperate drive i just installed xp on ;(
09:56
<alkisg>
Yeah, windows sucks :)
09:56
<munson>
was hoping somethin will work
09:56
<alkisg>
It doesn't allow that.
09:57
<munson>
yup i hate windoz too but damn scenario is im in school and when teacher gives classes on OS´s i wanted the thin clients to boot to that OS during class
09:57
<alkisg>
Right, you can use remote desktop or AoE for that
09:57
Not a partition on the server though.
09:58
<munson>
i know i can use virtualbox but wanted to stay away from that
09:58
<alkisg>
I didn't talk about virtualbox
09:59
<munson>
AoE i never tried that
10:00
<alkisg>
Here's the pxe menu that I send to my clients: http://imagebin.org/94072
10:01
(some enties are hidden)
10:01
<munson>
so i´d have to use this thin clients setup to load up the seperate box which has xp on it instead of using pxelinux.cfg/default to point to it
10:01
<alkisg>
No, if you have 100 clients you'd need to create 100 AoE images.
10:02
Read about AoE in google.
10:03
<munson>
ya i will...and that Windows XP (local disk) that is just xp on the thin client?
10:03
damn too bad these actual thin clients are diskless
10:04
<alkisg>
Right
10:04
<munson>
k
10:06
ya i was readin info bout using memdisk from syslinux to boot into windows so i was trying to figure out if possible but as u said not possible for these thin clients
10:07
got my hopes up lol
10:08
well lunch break...bbl
10:09
<alkisg>
It ***is*** possible with aoe or iscsi.
10:09
Just not with a "server partition"
10:16gnunux has quit IRC
10:16
<cliebow>
if a thin client had a disk it weould be a chubby client..portl;y client
10:16
porcine client
10:17staffencasa has joined #ltsp
10:24CAN-o-SPAM has joined #ltsp
10:32vagrantc has joined #ltsp
10:38alkisg has quit IRC
10:40Faithful has quit IRC
10:45
<komunista>
some day ago here was diskusion about shutdown/reboot LTSP clients via gnome session/panel
10:46
I found workaround, which works by menu merging and some gconf lockdown - for remove original logout item
10:47
but all is done manualy in my home dir, but IMHO, it is possible to automate in way simillar to localapps menu items
10:49
<vagrantc>
so the regular logout menu supports the ltsp shutdown/reboot feature?
10:49
<komunista>
not
10:49
I read your debian bug report to lxsession
10:50
and I get the xprop syntax from this and made simple script
10:50
then I create .menu and .desktop files for call this script and it works!
10:51
<vagrantc>
oh, there's also an example in ltsp-trunk/localapps/doc/examples
10:51
but the provided examples don't override the logout menu... they just provide another logout menu
10:52
<komunista>
IMHO if these .menu and .desktop files will be created by ldm start, it can be automatized...
10:53
<vagrantc>
could you paste the files somewhere?
10:53
<komunista>
removing original logout item I do by gconf-editor and setting /apps/panel/global/disable_log_out to true
10:53
yes, no problem, moment
10:54
<vagrantc>
ah, so you disable the logout, and then provide an alternative?
10:54
<komunista>
yes, it is my idea
10:55Faithful has joined #ltsp
10:55
<komunista>
but I do not know how to do this by ldm
10:55
<vagrantc>
the other approach if gnome-session-save returns an different exit code for shutdown, reboot, logout, etc. is to run a wrapper script for gnome-session-save
10:56
komunista: we'll figure it out :)
10:56
basically, you just need to plugin to LDM's hooks...
10:59
<komunista>
vagrantc: http://paste.lubomirr.eu/404
10:59
the very simple script, .menu file and one .desktop file as example
11:02
<vagrantc>
how does ltsp-quit know weather to reboot or logout?
11:02
er, reboot or shutdown?
11:03
<komunista>
by parameter, for example (from .desktop)
11:03
Exec=/usr/local/bin/ltsp-quit.sh shutdown
11:03
<vagrantc>
ah, so you have one .desktop file for each?
11:03
<komunista>
yes
11:04
I not familiar with zenity, but maybe it is possible by this...
11:04
<vagrantc>
certainly possible
11:04
though if gnome-session-save gives different exit codes, might be able to just use that
11:06
<komunista>
man page gnome-session-save have nothing about return codes...
11:06
<vagrantc>
yeah, i probably though about that in the past...
11:06* vagrantc is happy to see it in lxde :)
11:07
<komunista>
yes, it is nice :-)
11:11
<vagrantc>
komunista: so, when the user logs out, do these settings stay with the user?
11:11
<komunista>
hmm, gnome-session-save --logout-dialog give for me only selection logout or cancel
11:11
<vagrantc>
komunista: if they logged in directly on the server, it would cause problem?
11:12
ah, right... the dialog probably ignores shutdown/reboot when LTSP is enabled.
11:12
<komunista>
yes, for thisp roblem I mentioned the localapps menu
11:12
*this problem
11:13
<vagrantc>
i don't know if the localapps menu can modify the ~/.config/menus part
11:13
so far i've just seen desktop files (and icons) get dropped in there.
11:14
<komunista>
I read these local apps scripts some months ago
11:14
and fr version 5.0
11:14
*for
11:14
<vagrantc>
but if $XDG_DATA_DIRS can override menu stuff too...
11:15
<komunista>
but if I remember, the itam are created on the fly
11:15
and on logout these are removed
11:15
<vagrantc>
would: gconf-editor and setting /apps/panel/global/disable_log_out to true
11:15
would that reset itself?
11:16
<komunista>
set it to false
11:16
<vagrantc>
on logout?
11:16
<komunista>
yes, to true on login and to false on logout
11:17
then if the user login localy, all must be OK, similar as localapps
11:18
creating lts.conf option to enable/disable this will be good idea
11:19
<vagrantc>
well, for localapps, it works because the directory the .desktop files would be ignored on future logins, in case the user was uncleanly logged out, for example ... whereas gconf data might be stored in the user's home directory
11:23
<komunista>
I not very familiar with gconf (I am not gnome user), but here must be solution
11:24
<vagrantc>
me neither :)
11:26
<komunista>
this is sufficient solution for me, because my users never login other than via LTSP. but maybe other gnome users can help with this
11:28
<vagrantc>
hmmm... gnome-session-save --shutdown-dialog
11:29
komunista: for the option to be in upstream LTSP, we'll want it as cleanly implemented as possible ... generally no mucking with the user's configuration in a way that won't revert itself on logout
11:30
<komunista>
I understand you
11:31alkisg has joined #ltsp
11:31* vagrantc waves to alkisg
11:32
<Gadi>
put this in /etc/X11/Xsession.d/00ltspgconf: if [ -n "$LTSP_CLIENT" ]; then gconftool-2 --load /some/gconf/file.xml || true; fi
11:33
<vagrantc>
ta-da!
11:33
<Gadi>
(then do a gconftool-2 --dump /apps/panel/global/disable_log_out > /some/gconf/file.xml)
11:33
<vagrantc>
that will allow to temporarily change settings?
11:33
<Gadi>
(you could have an else to revert it back on local logins
11:33
<komunista>
with --shutdown-dialog I get only cancel option and counter to shutdown, after counter get 0, only logout occurred
11:34cliebow has quit IRC
11:35
<vagrantc>
wow... the shutdown dialog i get seems to count down in increments of 10 ...
11:36
<komunista>
from 60 to 30 by 10, then by small step
11:36
<vagrantc>
it went 60 seconds, 50, 40, 30, 20, 19, 18, 17...
11:36
that's weird.
11:37
<alkisg>
Hi vagrantc, hi all
11:37
<komunista>
hi
11:37
<vagrantc>
hmmm.. i don't get a menu at all with gnome-session-save ...
11:38
on debian/squeeze
11:39
<komunista>
vagrantc: I have debian testing too
11:41* vagrantc wonders if recent versions of gnome include the patches that prevent shutdown of the server from thin clients?
11:42
<alkisg>
When was that a problem?
11:42Gadi has left #ltsp
11:42
<alkisg>
Remote sessions, like ssh / nx etc, are not considered "active" in consolekit
11:42
<vagrantc>
right.
11:42
<alkisg>
So they cannot shutdown the computer through gnome dbus calls...
11:43
<vagrantc>
pre-consolekit ubuntu carried patches to prevent that from happening
11:43
<alkisg>
Ah, ok, that's too ancient for me :D
11:43
<vagrantc>
but apparently it's solved by using consolekit ...
11:43
and now we need to unsolve it to use the ltsp shutdown/reboot feature :)
11:44* komunista sometime shutdown his server from NX :-)
11:44
<alkisg>
Nah, we'd shutdown the server if we solved it :)
11:44
We want to shutdown the client instead
11:44
<vagrantc>
well, display the shutdown or reboot option in a way that triggers the ltsp features :)
11:44
<alkisg>
Either that, or get the gnome-session exit code
11:44
(1=reboot, 2=shutdown or something)
11:44
<vagrantc>
yeah, that's what i was thinking would be the way to go
11:45
hopefully
11:45
then we could have a single .desktop file that checks the exit status and behaves accordingly
11:46
<alkisg>
We could also ask the gnome people to hide reboot/shutdown for not-active CK seats
11:46
...but I'd prefer it if we made them actually work :)
11:46
<vagrantc>
well, we don't have to hide reboot/shutdown, we want it to do something different
11:47
<alkisg>
Can sbalneav help in this? I mean, if we have a valid patch, can he help in pushing it upstream?
11:48
<vagrantc>
maybe...
11:48
all we need is the code. :)
11:53
<alkisg>
Nah, gnome-session/main.c just uses `return 0`
11:55
<vagrantc>
i wonder if gnome-session would allow for some sort of hooks mechanism?
11:55
that way it wouldn't have to be specific to ltsp.
11:56
i get the impression, unlike lxde, they won't go for LTSP-specific features directly in gnome ... but if a generic mechanism could be established... :)
11:56
<alkisg>
Sure, returning a different value for shutdown vs reboot isn't ltsp specific
11:56
A hook would also do but it'd be unnecessarily complicated
11:56
<vagrantc>
but that still requires a fair amount of hacking on our part
11:57* alkisg has yet to find where the actual reboot takes place...
11:57
<vagrantc>
and we'll have to work around the fact that consolekit will prevent it from displaying shutdown/reboot
11:58
<alkisg>
It will? They're planning to do that?
11:59
<vagrantc>
i thought we just established they're already doing that... ?
11:59
09:42 < alkisg> Remote sessions, like ssh / nx etc, are not considered "active" in consolekit
11:59
or does that still present the button?
12:00
<alkisg>
They're not active, they perform logout instead of shutdown/reboot, but the menu items are still there
12:08
<komunista>
and some as this? http://proj.penguindevelopment.org/shutdown-dialog/shutdown-dialog-latest.tar.gz
12:08
it is in python
12:12* vagrantc goes back to wondering how on earth to create virtual hal/udisks devices
12:13
<vagrantc>
seems like with udisks, we've need to create virtual /dev/FOO entries...
12:13
since udisks just seems to act on device nodes.
12:29lucascoala has joined #ltsp
12:30
<johnny>
have you guys talked to upstream about this?
12:30emence has quit IRC
12:30
<vagrantc>
upstream what?
12:31
<johnny>
gnome-session for one
12:31
<vagrantc>
and udisks/devicekit/policykit for the other?
12:31
<johnny>
sure
12:31
whoever ... just talk to the people who can help you come up with something generic to help solve your problem
12:32
the problem might be interesting enough for somebody interested to jump right on it :)
12:32
that's what happened when i suggested the change to packagekit
12:33
<alkisg>
vagrantc: what's a virtual udisk? What's the purpose?
12:34
<vagrantc>
alkisg: in order to get ltspfs devices recognized on lxde, kde and i think xfce...
12:34
<alkisg>
Ah, so ltspfs should "register" the disk somehow?
12:34
<vagrantc>
and it might be so broad as fuse devices.
12:34
right
12:36* vagrantc loves wiki pages that link to themselves.
12:39
<vagrantc>
so http://www.freedesktop.org/wiki/Software/udisks gives extensive information on what to report in bugs on udisks... but not *where* to report bugs on udisks...
12:39
not that this is even a bug, really...
12:40
<alkisg>
udisks --mount ?
12:40
<vagrantc>
alkisg: it expects a path to a device node... and as far as i can tell, it doesn't work over ssh.
12:41
tightly integrating into udev is great for a desktop... but seems to make remote access a nightmare.
12:45
<johnny>
vagrantc, actually, devicekit disks gui can work over ssh
12:46
too bad his site is down with some wordpress upgrade message..
12:47
you really should talk to davidz vagrantc
12:47Gadi_eeepc has joined #ltsp
12:51hersonls has quit IRC
12:52hersonls has joined #ltsp
12:57hersonls has quit IRC
12:58hersonls has joined #ltsp
12:58wood has joined #ltsp
13:00
<vagrantc>
johnny: well, i'm composing a mail to devkit-devel@lists.freedesktop.org
13:07hersonls has quit IRC
13:07hersonls has joined #ltsp
13:11Lns has joined #ltsp
13:14lucascoala has left #ltsp
13:30
<mutex>
hi
13:30
I am trying to run x11vnc when a user logs in
13:30
so I can watch their desktop
13:30
every conceivable way of starting it seems to fail
13:30
/etc/init.d
13:31
/usr/share/ldm/rc.d
13:31
where should it be going ?
13:31
if I run as user directly it seems to work fine
13:33
any thoughts ?
13:35
<alkisg>
mutex, why don't you use italc for that?
13:35
You could put it to /etc/xdg/autostart
13:35
(I mean x11vnc)
13:35
<jbrett>
mutex: are they gnome desktops? If so, you could just set vino to automatically run.
13:35
<alkisg>
(on the server, not on the chroot)
13:36
vino needs to be configured to listen on different ports for each user
13:36
<jbrett>
ah, yeah.
13:36* jbrett forgot he was on #ltsp ;)
13:36
<alkisg>
:)
13:36
<mutex>
I don't have any reason not to use italc
13:36
jbrett: they are ubuntu ltsp terminals
13:36
I'd like it if everything ran on the local terminal
13:37
<alkisg>
italc is very well integrated toubuntu
13:37
You just need to do apt-get install italc-master on the server, and logoff/logon.
13:37
<mutex>
sounds cool
13:37
I will give it a shot
13:57alkisg has quit IRC
14:03
<mutex>
so the other thing
14:03
is that my system only boots about 1/4 times
14:03
the rest of the time X never makes it
14:04
sometimes it stops booting due to 'mount' errors
14:04
other times on vt7 it says 'nc: '-f-' invalid option'
14:04
then prints the netcat help message
14:04
there is no '-f' for netcat as far as I am aware
14:06Gadi_eeepc has quit IRC
14:08lucascoala has joined #ltsp
14:08lucascoala has joined #ltsp
14:09lucascoala has left #ltsp
14:21Kicer86 has quit IRC
14:24evilx has quit IRC
14:30Gadi_eeepc has joined #ltsp
14:37ogra_cmpc has quit IRC
14:39munson has quit IRC
14:39ogra_cmpc has joined #ltsp
14:43hersonls has quit IRC
14:50pmatulis has quit IRC
15:01CAN-o-SPAM has quit IRC
15:15ogra_cmpc has quit IRC
15:16ogra_cmpc has joined #ltsp
15:19otavio has quit IRC
15:19otavio has joined #ltsp
15:30
<Lns>
vagrantc: ping?
15:30* vagrantc awaits content
15:30
<Lns>
=) Hey
15:31
Have you had the issue in Lenny / Gnome regarding System -> Lock Screen not working? I'm bumping my head against a wall, the menu entry does nothing yet my screensaver is "active" for gnome
15:31
not sure what the command it uses is
15:32
<vagrantc>
i encountered that earlier today on squeeze
15:32
though i don't use gnome often enough to know if it ever worked...
15:32
<Lns>
hehe
15:32
<vagrantc>
Lns: anything revealing in ~/.xsession-errors?
15:32
<Lns>
lesse
15:33
" ** Message: Screensaver is not running! "
15:33
is what prints to the file when i click the menu entry
15:33
weird
15:34
hmm, and when I go to System -> Preferences -> Screensaver
15:35
then click on "power management".. it gives me this: " ** (gnome-power-preferences:27594): WARNING **: DBUS error: Could not get owner of name 'org.gnome.ScreenSaver': no such name
15:35
** (gnome-power-preferences:27594): DEBUG: proxy is NULL, maybe the daemon responsible for org.gnome.ScreenSaver is not running?"
15:35
So .. gnome-screensaver is not running ;)
15:36
is that because i'm on a terminal and it doesn't execute ?
15:36ogra_cmpc has quit IRC
15:36
<vagrantc>
Lns: on my install, gnome-screensaver isn't installed...
15:37
xscreensaver is, though
15:37
<Lns>
Hmm
15:37
I have it on mine, but not xscreensaver ;)
15:38
I didnt' do any manual installs besides updating gnome using lenny-backports
15:39* vagrantc doesn't see any gnome stuff in backports
15:39
<Lns>
?
15:39
oh maybe i didn't then...jeez where's my head
15:39
i'm on 2.22.3
15:40
<vagrantc>
apt-show-versions can help you put your head back on, at least with regard to where your packages are from :)
15:40
<Lns>
ooo, thx for that =)
15:41
K I have gnome-session/lenny uptodate 2.22.3-2
15:41
<vagrantc>
apt-cache policy is also really useful, and doesn't require installing extra stuff
15:42
<Lns>
vagrantc: ok - so I manually launch gnome-screensaver, it goes into bg.. then I go system -> lock screen and on the terminal I launched g-s on it gives me this: http://pastebin.org/171057
15:42
and of course gnome-screensaver crashes
15:47alkisg has joined #ltsp
15:49ogra_cmpc has joined #ltsp
15:57bobby_C has joined #ltsp
16:01rjune has quit IRC
16:05
<vagrantc>
Lns: hrm.
16:06
<Lns>
vagrantc: I'm ooto for a bit but I should be back around an hour or so.. lemme know what i can do, if you plan on looking into it :)
16:06
<vagrantc>
The error was 'XF86VidModeClientNotLocal'.
16:06
that doesn't sound promising
16:06
<Lns>
yeah
16:07
bbl :)
16:11epaphus has quit IRC
16:11
<komunista>
vagrantc: I finally get one logout menu item and python logout dialog, only in client, not in local login.
16:12
<vagrantc>
komunista: good work!
16:14
<komunista>
I can send to you deb package, if you want try it
16:14
or send link to download
16:14
only python dependencies are not precise
16:15
it is native package - not compiled, not source
16:16bobby_C has quit IRC
16:19
<komunista>
vagrantc: http://info.slavino.sk/ltsp-logout_0.3_all.deb
16:23alkisg has quit IRC
16:29
<vagrantc>
komunista: interesting...
16:30
komunista: probably also need a dependency on python-gtk* or whatever ships pygtk
16:32vbundi has left #ltsp
16:33
<komunista>
I am not programmer, then I wrote to one friend, perhaps he help my
16:34
I need to add item to .desktop file to show only in gnome too
16:34
<vagrantc>
python-gobject, looks to me.
16:34
<komunista>
vagrantc: do you have icons on buttons in dialog?
16:34
<vagrantc>
komunista: looks like a decent workaround overall
16:35
komunista: haven;t tried it yet, just looking at the code :)
16:35
<komunista>
on my machine I have icons, but on LTSP not :-(
16:36rjune has joined #ltsp
16:36
<komunista>
it can be safely used without ltsp, just run python script, to see dialog
16:38
and select Cancel - of course :-)
16:40
<vagrantc>
komunista: completely broke the applications menu and the system menu seems somewhat broken...
16:40
<komunista>
:-/
16:41
I have all menu OK
16:41
<vagrantc>
komunista: debian/squeeze?
16:42
<komunista>
yes
16:42
fresh installation in VBox
16:42
<vagrantc>
i have a fairly minimal gnome install...
16:42ogra_cmpc has quit IRC
16:43ogra_cmpc has joined #ltsp
16:44
<vagrantc>
komunista: and it completely breaks lxde :(
16:44
<komunista>
yes, I wrote - is needed to add item -show only in gnome to .desktop file
16:45
LXDE is not problem
16:46
<vagrantc>
sure
16:47
komunista: in a working setup, does XDG_CONFIG_DIRS contain anything?
16:47
<komunista>
here is my menu in client http://info.slavino.sk/ltsp-menu1.png
16:47
XDG_CONFIG_DIRS is unset
16:49
hmm
16:49
<vagrantc>
well, my applications menu is definitely empty...
16:50
maybe it wasn't working before i installed ltsp-logout
16:51
<komunista>
perhaps is needed set the $XDG_CONFIG_DIRS to "/etc/xdg/:/usr/share/ltsp/xdg/"
16:51
<vagrantc>
purging ltsp-logout it worked again...
16:52
<komunista>
in gnome or in LXDE?
16:52
<vagrantc>
gnome
16:53
<komunista>
can you do "set | grep XDG" withou ltsp-logout?
16:54
<vagrantc>
XDG_DATA_DIRS=/usr/share/gnome:/usr/locale/share/:/usr/share/
16:55
<komunista>
the same
16:55
<vagrantc>
XDG_SESSION_COOKIE=<bunch_of_cookie_data>
16:55
<komunista>
the same for me
16:55
and with ltsp-logout is only XDG_CONFIG_DIRS added
16:55* vagrantc wonders if setting XDG_DATA_DIRS=/usr/share/ltsp/xdg:/usr/share/gnome...
16:56
<komunista>
I tried this, but this do not works for me - I canot login with this
16:57
but the /usr/share/ltsp/xdg directory is added by .menu file <AppDir> item
16:57
<vagrantc>
sure
16:58
<komunista>
if is your applications menu empty, then problem can be in XDG_CONFIG_DIRS
16:59
this variable, if is unset, is represented as /etc/xdg/
16:59
<vagrantc>
so we need to set a default if we want to add to it...
16:59
<komunista>
maybe to add to the file /Etc/X11/Xsession/10ltspgconf
16:59
<vagrantc>
that worked
17:00
if [ "$XDG_CONFIG_DIRS" ]; then
17:00
<komunista>
ahh, I have some old .menu files in my $HOME
17:00
<vagrantc>
export XDG_CONFIG_DIRS="$XDG_CONFIG_DIRS:/usr/share/ltsp/xdg/"
17:00
else
17:00
export XDG_CONFIG_DIRS="/usr/share/ltsp/xdg/:/etc/xdg"
17:01
though i'd recommend XDG_CONFIG_DIRS="/usr/share/ltsp/xdg:$XDG_CONFIG_DIRS"
17:01
<komunista>
OK, I correct both in my files
17:02
<vagrantc>
still no icons
17:02
<komunista>
I'll wait to my friend response...
17:03
<vagrantc>
i don't have any gnome-icon-theme* installed
17:04
correction, i have gnome-icon-theme installed
17:06
<komunista>
the strace on my machine tell:
17:06
open("/usr/share/icons/gnome/scalable/actions/reload.svg", O_RDONLY) = 3
17:06
open("/usr/share/icons/gnome/scalable/actions/gnome-shutdown.svg", O_RDONLY) = 3
17:06
open("/usr/share/icons/gnome/scalable/actions/stop.svg", O_RDONLY) = 3
17:06
but I have KDE on my machine...
17:07
screenshot on my machine: http://info.slavino.sk/ltsp-logout.png
17:13
yes, I can't login to LXDE
17:22
for LXDE I need more playing :-)
17:38
<johnny>
hmm..
17:38
i wonder if there are official lubuntu-desktops i can use for fat clients
17:44
<dberkholz>
johnny: unfortunately we're not gonna have a summer of code student for ltsp, although dracut will happen
17:46
<johnny>
dracut and a stable baselayout 2 would be nice..
17:51
<komunista>
vagrantc: LXDE do not works for me at all, without ltsp-logout, please for you works?
17:51
I get only on eline in .xsession-errors - about beginning gdm session
17:51
nothing more
17:51
and LXDE session dies
18:02highvoltage has quit IRC
18:04
<komunista>
lxsession[1539]: segfault at 0 ip 00007fc98ecd9220 sp 00007fff60848e88 error 4 in libc-2.10.2.so[7fc98ec60000+14a000]
18:04
good night
18:08highvoltage has joined #ltsp
18:10komunista has quit IRC
18:27staffencasa has quit IRC
18:47litlebuda has joined #ltsp
19:07Egyptian[Home] has quit IRC
19:11Ryan52 has quit IRC
19:13Lns has quit IRC
19:20Egyptian[Home] has joined #ltsp
19:53litlebuda has quit IRC
20:17ogra_cmpc has quit IRC
20:18ogra_cmpc has joined #ltsp
20:24wood has quit IRC
20:38wood has joined #ltsp
21:31F-GT has quit IRC
21:39try2free has joined #ltsp
21:47F-GT has joined #ltsp
21:55rjune has quit IRC
21:57try2free has quit IRC
22:51shogunx has quit IRC
23:04ogra_cmpc has quit IRC
23:05ogra_cmpc has joined #ltsp
23:19F-GT has quit IRC
23:24japerry has joined #ltsp
23:36F-GT has joined #ltsp