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


Channel log from 14 June 2011   (all times are UTC)

00:22gnunux (~emmanuel@194.167.18.244) joined #ltsp.
00:26TheMatrix3000 (~TheMatrix@oh-76-1-33-172.dhcp.embarqhsd.net) left irc: Read error: Connection reset by peer
00:27TheMatrix3000 (~TheMatrix@oh-76-1-33-172.dhcp.embarqhsd.net) joined #ltsp.
00:28Nick change: elias_a_ -> elias_a
00:35
<gnunux>
bonjour
01:01siraj (~siraj@plexyplanet.org) left irc: Ping timeout: 240 seconds
01:01siraj (~siraj@plexyplanet.org) joined #ltsp.
02:12Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
02:18dlezcano (~dlezcano@AToulouse-159-1-37-78.w92-134.abo.wanadoo.fr) left irc: Ping timeout: 255 seconds
02:42dobber (~dobber@89.190.197.77) joined #ltsp.
03:22elias_a (elias@hilla.kapsi.fi) left irc: Quit: Changing server
03:33TheMatrix3000 (TheMatrix@oh-76-1-33-172.dhcp.embarqhsd.net) left #ltsp.
03:53mdourado (~mario.dou@190.115.103.87.rev.vodafone.pt) joined #ltsp.
03:56
<mdourado>
I am trying to install Wine to run Internet Explorer on my LTSP server, but the image is 64 and everything give's me errors.. the image that I have on CHROOT is x86 but the installers of internet explorer are graphical.. how can I install applications on the CHROOT with a visual interface?
03:58
or that is anyother better solution for this? the thing is.. I have a client that uses a CRM that only runs at Internet Explorer.. the only solution that camed up to my mind is to run internet explorer "emulated"
04:04alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
04:06
<muppis>
mdourado, install IE somewhere locally and just copy .wine -directory under desired user's home directory.
04:08
<mdourado>
muppis I've logged in myself in one og the terminals with the administrator's access to install it.. but if the server has a 64bit instalation, when I login am I not running a 64bits OS? I am saying this because I am getting the erros of instaling in a 64bits OS
04:11
<muppis>
mdourado, your ltsp server is amd64 and clients are i386 ?
04:11
<mdourado>
yes the ltsp server is amd64 but the CHROOT image is i386
04:12
<alkisg>
Wine is 32 bit even on amd64 linux systems
04:12
Better ask in #wine-hq, it's not really ltsp related, you'll get better help there
04:13
(meaning, you'll probably need to install the 32bit version of internet explorer)
04:13
<mdourado>
the thing is.. I want to install Wine as a local app.. at the CHROOT.. but I don't have access to Home.. is this normal?
04:13
<alkisg>
Why would you install it as a local app?
04:13
And not normally as the running user?
04:14
<mdourado>
because I am having problems installing it at the running server
04:14
<alkisg>
chroot == more difficult than installing it in the running server
04:14
So if you can't manage the server installation, don't expect to make it in the chroot :)
04:15
So I suggest to go to #wine-hq and ask for help on how to install IE on a normal, non ltsp system (i.e. the ltsp server)
04:15
<mdourado>
alkisg I can install Wine at the running server.. what I can't is to install IE
04:15
<alkisg>
Right, that's why I'm saying that it's not ltsp-related
04:15
It's purely a wine question
04:16
People at #wine-hq surely know wine better than people here at #ltsp
04:16
<muppis>
mdourado, which version of IE you're trying to install?
04:16
<mdourado>
I've tried 6 7 and 8
04:17
<muppis>
Readed this? http://www.wine-reviews.net/wine-reviews/microsoft/internet-explorer-8-on-linux-with-wine.html
04:19
<mdourado>
okok thank you very much, I am currently at the wine channel trying to solve the problem,
04:19
thank you very much
04:24
alkisg btw, imagine that I can install Internet Explorer at the server.. will it be avaiable for all users?
04:26alkisg (~alkisg@ubuntu/member/alkisg) left irc: Ping timeout: 240 seconds
04:39
<muppis>
mdourado, if you deploy the .wine -directory to every user's home.
04:59andygraybeal (~andy.gray@obsidian.casanueva.com) joined #ltsp.
05:01alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
05:01dlezcano (~dlezcano@nat/ibm/x-azafrnamstbivyms) joined #ltsp.
05:10alkisg (~alkisg@ubuntu/member/alkisg) left irc: Ping timeout: 240 seconds
05:14ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Ping timeout: 276 seconds
05:15ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
05:21cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Ping timeout: 255 seconds
05:22cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
05:22TheMatrix3000 (~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com) joined #ltsp.
05:31bencer_ (~bencer@cl-141.lis-01.pt.sixxs.net) joined #ltsp.
05:32bencer (~bencer@heal.cauterized.net) left irc: Ping timeout: 250 seconds
05:36mdourado (~mario.dou@190.115.103.87.rev.vodafone.pt) left irc: Ping timeout: 260 seconds
05:38mdourado (~mario.dou@190.115.103.87.rev.vodafone.pt) joined #ltsp.
05:55
<mgariepy>
good morning everyone
05:57mgariepy (~mgariepy@ubuntu/member/mgariepy) left irc: Quit: Leaving
05:57brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) joined #ltsp.
05:59mgariepy (~mgariepy@2001:470:8829:1040:21e:c9ff:fe3c:ff2a) joined #ltsp.
05:59mgariepy (~mgariepy@2001:470:8829:1040:21e:c9ff:fe3c:ff2a) left irc: Changing host
05:59mgariepy (~mgariepy@ubuntu/member/mgariepy) joined #ltsp.
06:01Gadi (~romm@ool-18bbe47a.static.optonline.net) joined #ltsp.
06:02
<TheMatrix3000>
ok, question
06:02
im on LTSP
06:02
have a local user, and a ldap user
06:02
local user the gnome-power-manager works
06:02
ldap user gnome-power-manager applet doesn't work
06:07
<Gadi>
what are you using gnome-power-manager for? managing the power on the server?
06:07
<TheMatrix3000>
no
06:07
just it pops up by default in the top right
06:07
allows people to "restart" "shutdown" logoff
06:07
etc
06:07
<Gadi>
ah
06:08
thats not the power manager
06:08
I dont think
06:08
thats just to logout of the session
06:08
<TheMatrix3000>
ah, fastuserswitch applet
06:08
GNOME:_fastuserswitch applet thing
06:09
<Gadi>
I think that is controlled by a gconf key
06:09
you might want to check if the key differs under the different user accounts?
06:09
otherwise, check the user's ~/.xsession-errors
06:09
<TheMatrix3000>
k
06:09
<Gadi>
and see if the applet is crashing for some reason
06:10
<TheMatrix3000>
i just am puzzled why
06:10
<Gadi>
me, too
06:11
<TheMatrix3000>
it works for normal users, just not the ldap ones
06:11
<Gadi>
perhaps the user needs to be in a particular group for it to function properly?
06:11
what is the primary group of the ldap users?
06:11
<TheMatrix3000>
no, cause i make user bill in group bill
06:11
and it works
06:11
"_Users_"
06:11
show's as primary group
06:13alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
06:42
<TheMatrix3000>
alkisg, maybe you can help
06:42
the fastuserswitch applet isn't work
06:42
working* with ldap users
06:42
but works with local users
06:42
under ltsp
06:43Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Quit: I Leave
06:44mistik1 (mistik1@unaffiliated/mistik1) left irc: Ping timeout: 260 seconds
06:44Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
06:44Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Client Quit
06:45Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
06:46Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Client Quit
06:53bencer_ (~bencer@cl-141.lis-01.pt.sixxs.net) left irc: Quit: No Ping reply in 180 seconds.
06:54bencer (~bencer@heal.cauterized.net) joined #ltsp.
06:57ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Excess Flood
06:57ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
07:05NeonLicht (~NeonLicht@darwin.ugr.es) joined #ltsp.
07:05
<NeonLicht>
Hello.
07:07
<andygraybeal>
hi neonlicht :) (kraftwerk rules)
07:08
sup man? ... i'm making patch cables.. nicely labelled on each end
07:08
<NeonLicht>
I'm trying to force a thin client to take the screen resolution by adding 'CONFIGURE_X=True' and 'X_MODE_0 = 1440x900' to the relevant section on lts.conf to no avail. Should that be enough or am I missing someting, please? I've also tried to force it changing the driver by adding 'XSERVER = ati' (which I think should work) but nothing changes.
07:08
Indeed, andygraybeal, they do! :)
07:09
<andygraybeal>
alkisg, joined a bit ago, but hasn't spoken yet.. i'm sure he'd be the one to help out - - maybe others if they are awake.. it's not been too busy this morning so far. Gadi has been around, so that's plusses too.
07:10
<Gadi>
NeonLicht: CONFIGURE_X is deprecated and should not be used at all
07:11
if X_MODE_0 by itself does not work (which by default will be equivalent to XRANDR_MODE_0) ...
07:11
<NeonLicht>
It's documented on the current manual, Gadi :(
07:11
Gadi, meaning?
07:11
<Gadi>
then, you can add XRANDR_DISABLE = True
07:11
to disable the use of xrandr for modesetting and force the mode in the xorg.conf
07:12
but before you do that,
07:12
it would be best to log in, and check the ouput of "xrandr"
07:12
at a terminal
07:12
to see the available modes
07:13
and if you don't see the ones you want, you could either check the local Xorg log file to see why not
07:13
<NeonLicht>
OK... let see
07:13
local? what do you mean by local? local to the client (chroot)?
07:13
<Gadi>
or shoot in the dark and guess that the driver failed to get the modes from the monitor and manually set X_HORZSYNC and X_VERTREFRESH
07:13
do this:
07:14
1. log in at the client
07:14
2. type: ltsp-localapps xterm
07:14
3. inside the new xterm window, type: xrandr
07:14
4. inside the new xterm, look at /var/log/Xorg.7.log
07:15
(that new xterm is running on the local thin client)
07:15dlezcano (~dlezcano@nat/ibm/x-azafrnamstbivyms) left irc: Ping timeout: 240 seconds
07:15
<Gadi>
hopefully, something there will give you a clue as to what you need to do to get your mode
07:17
<NeonLicht>
OK, I see... the native resolution of the monitor isn't there...
07:17
<Gadi>
in the xrandr output?
07:18
<NeonLicht>
Yes, in the xrandr output.
07:18
07:18
<Gadi>
what card is it?
07:19
<NeonLicht>
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC AGP (rev 7a)
07:19
<Gadi>
and what driver does /var/log/Xorg.7.log say it uses?
07:20
that log file, should tell you everything
07:20
<NeonLicht>
Looking for it... don't find it...
07:20
<Gadi>
what distro?
07:20
<NeonLicht>
Debian Squeeze (server), Sid/Squeeze/Lenny (clients)
07:20
<Gadi>
in the xterm, type: ls /var/log
07:21
<NeonLicht>
I didn't mean I didn't find the log file, but the module...
07:21
<Gadi>
ah
07:21
there should be a whole bunch of lines that start with:
07:21
ATI ():
07:21
or VESA: ()
07:22
or CHROME ():
07:22
etc
07:22
<NeonLicht>
[ 105.738] (--) MACH64(0): ATI 3D Rage IIc graphics controller detected.
07:22
<Gadi>
ah
07:22
there ya go
07:22
<NeonLicht>
OK, and tones of lines like: [ 105.752] (II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
07:24
<Gadi>
and what does it say about the mode you want
07:24
<NeonLicht>
1600x900 (the native resolution of the monitor)isn't listed)
07:24
<Gadi>
1440x900 was it?
07:24
<NeonLicht>
[ 105.753] (II) MACH64(0): Not using driver mode "1440x900" (insufficient memory for mode)
07:25
<Gadi>
ah - perhaps you don't have enough video memory in the client card?
07:25
or in the client BIOS?
07:25
(if it uses shared video memory)
07:25
you could try dropping the color depth
07:26
<NeonLicht>
I guess it does...
07:26
<Gadi>
say: X_COLOR_DEPTH = 16
07:26
then, you may have enough memory
07:26
<NeonLicht>
OK, trying...
07:27
rebooting the terminal...
07:28tl1000s77 (~tl1000s77@173-13-114-113-NewEngland.hfc.comcastbusiness.net) joined #ltsp.
07:30dlezcano (~dlezcano@nat/ibm/x-gnqfygadqquqwlti) joined #ltsp.
07:33
<NeonLicht>
Same resolution... :(
07:34mdourado (~mario.dou@190.115.103.87.rev.vodafone.pt) left irc:
07:37
<Gadi>
same thing in the logs, too?
07:38
<NeonLicht>
Shame on me... I had a very low resolution set on lts.conf (old tests)... rebooting again with only X_COLOR_DEPTH = 16 on lts.conf now...
07:39
Shuld that be enough or do I need to force the resolution I want also?
07:40
<Gadi>
well, if you don't force the mode, it should use the monitor's preferred mode
07:41
sometimes the driver chooses the highest mode
07:41
depends on the driver and the info that the monitor reports
07:41
<NeonLicht>
I see... I have a higher resolution now... checking the log file...
07:42
[ 205.684] (II) MACH64(0): Modeline "1440x900"x0.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz)
07:42
It's there, but I don't think it's using it...
07:42
Maybe X_COLOR_DEPTH = 32 would help?
07:42
The chartacters are not sharp
07:44
[ 205.702] (--) MACH64(0): Virtual size is 1152x864 (pitch 1152) <--- I think it's using that one...
07:44
[ 205.697] (II) MACH64(0): Not using default mode "1440x900" (insufficient memory for mode) <--- again!
07:44
<Gadi>
there is an X_VIRTUAL you could set
07:45
<NeonLicht>
I think I'll try X_COLOR_DEPTH = 32
07:45
<Gadi>
how much memory does the log say it detects?
07:45
<NeonLicht>
video memmory or what?
07:48dead_root (~dead_root@76.75.3.174) joined #ltsp.
07:52
<Gadi>
yeah, it sounds like either the card does not have enough memory or the driver cannot detect the amount of memory
07:53
<NeonLicht>
X_COLOR_DEPTH = 32 doesn't seem to work at all... X doesn't even start...
07:53
<Gadi>
how about:
07:53
X_VIDEORAM = 131072
07:53
(that should tell it that it has 128MB of video ram to work with)
07:53
<NeonLicht>
With or without X_COLOR_DEPTH?
07:54
<Gadi>
try with X_COLOR_DEPTH=16
07:54
for starters
07:54
<NeonLicht>
OK
07:54
<Gadi>
(it hasn't worked yet with 16 or 32, right?)
07:54Lns (~Lns@76-191-128-251.dsl.dynamic.sonic.net) joined #ltsp.
07:54Lns (~Lns@76-191-128-251.dsl.dynamic.sonic.net) left irc: Changing host
07:54Lns (~Lns@pdpc/supporter/professional/lns) joined #ltsp.
07:56
<NeonLicht>
It's booting :)
07:59
[ 102.907] (II) MACH64(0): Not using driver mode "1440x900" (insufficient memory for mode)
07:59
:(
07:59
With X_COLOR_DEPTH = 16 and X_VIDEORAM = 131072
08:00
Using 1152x864, I believe.
08:01
Trying Without X_COLOR_DEPTH = 16 and X_VIDEORAM = 131072 now...
08:02
There is also an X_MONITOR_nn variable...
08:03
At least it's docummented on the 0.99 version of the docs.
08:03
<Gadi>
that is to add options to the "Monitor" section of the xorg.conf
08:03
which I don't think you need to do
08:03
<NeonLicht>
I see...
08:04
<Gadi>
do you get higher modes than 1440x900 or just lower modes?
08:04
<NeonLicht>
There are four people with similar thin clients waiting for this to work... :D
08:04
08:05
<Gadi>
is this an add-in card or is it onboard?
08:06
it could be that it is not getting the sync frequencies from the monitor at all
08:06
try this:
08:06
X_HORZSYNC = "31-80"
08:07
X_VERTREFRESH = "55-75"
08:07
<NeonLicht>
It's onboard.
08:07
<Gadi>
XRANDR_MODE_0 = 1440x900
08:08
<NeonLicht>
Just those three?
08:08
<Gadi>
yeah
08:08
<NeonLicht>
What about VIDEORA?
08:08
<Gadi>
just those 3
08:08
<NeonLicht>
VIDEORAM?
08:08
OK
08:08
<Gadi>
since it is onboard, I would also check the BIOS video settings
08:08
<NeonLicht>
rebooting...
08:08
<Gadi>
it could be that the BIOS is limiting the Video memory or AGP aperture
08:10
<NeonLicht>
BIOS says 2MB SGRAM
08:10
<Gadi>
aha!
08:10
<NeonLicht>
It also says no RAM reserved. (?)
08:10
<Gadi>
2MB is not much
08:10
<NeonLicht>
the weird thing is that those clients where working with the same monitors before
08:10
<Gadi>
at that resolution?
08:11
(1440x900)
08:11* highvoltage doesn't believe it
08:11
<NeonLicht>
Not sure if it was at that one, but at least at one 12x9 (not deformed images) and sharp characters.
08:12
No characters aren't sharp and the proportions aren't right.
08:12staffencasa (~staffenca@128-193-147-249.oregonstate.edu) joined #ltsp.
08:12
<NeonLicht>
Does the reserved memory in the BIOS setting have anything to do with video?
08:13
<Gadi>
is it reserving the memory for the video?
08:13
then, maybe, yes
08:14
<NeonLicht>
I don't know, that's my question.
08:14
<Gadi>
you need at least 2.6MB for 1440x900@16 bits
08:14
<NeonLicht>
I've set 15-16MB reserved... no idea what it's going to reserve it for...
08:14
<Gadi>
not sure - is it under the video memory menu?
08:14
or somewhere else?
08:17
<NeonLicht>
Below the video memory option, but not sure id it's related to it or not.
08:17
booted with wrong resolution again :(
08:18
Is it possible to somehow check how much memory X belives it has?
08:18
<Gadi>
should be in the log
08:19dobber (~dobber@89.190.197.77) left irc: Ping timeout: 258 seconds
08:21
<NeonLicht>
[ 101.815] (II) MACH64(0): Using 8 MB linear aperture at 0xFD000000. <--- I don't think it's that...
08:21ry (~ry@static-71-183-64-28.nycmny.fios.verizon.net) joined #ltsp.
08:21
<NeonLicht>
[ 101.819] (--) MACH64(0): 2048 kB of SGRAM (1:1) detected (using 2047 kB). <--- I'm afraid it's that one
08:22
<Gadi>
are you looking for a widescreen mode?
08:22
<NeonLicht>
Yes
08:23
Otherways the shapes are deformed
08:23
<Gadi>
if all you have is 2MB, you might be best with: 1152x720@16 bit
08:23
so take everything else out, and try: XRANDR_MODE_0 = 1152x720
08:23
X_COLOR_DEPTH=16
08:24
<NeonLicht>
OK...
08:24
<Gadi>
(if the driver has that mode)
08:24
<NeonLicht>
Perhaps that was what it was using before (a different LTSP server)
08:25
I woudn't mind to go to a lower resolution for the moment (until we get new graphic cards)
08:25
Because I guess getting new PCI cards will help...
08:30
1152x720 doesn't appear, 1152x864@75Hz does
08:32
It's using 840x640 now :(
08:34dobber (~dobber@213.169.45.222) joined #ltsp.
08:49Lns (~Lns@pdpc/supporter/professional/lns) left irc: Quit: Leaving
08:56
<NeonLicht>
It's using 832x624... weird!
08:56
[ 101.090] (WW) MACH64(0): Shrinking virtual size estimate from 1440x900 to 832x6
08:56
24
08:56
that line seems to be interesting...
08:57
It was actually trying to go to 1440x900, I think.
08:57
<alkisg>
NeonLicht: boot with X_COLOR_DEPTH=16, run xrandr, and paste the output
08:58
If you really only have 2 MB RAM on your video card, there's not much you can do other than select a lower mode
08:58
(or create a new one)
08:58
Of course you could use X_COLOR_DEPTH=8, but that would be much worse than the dim letters...
08:59
<NeonLicht>
What lower mode? I'd be happy to see anything different (I'd know I'm having any effect at all),
08:59
<alkisg>
You don't have to reboot the client to select different modes
08:59
<NeonLicht>
Don't I?
08:59
<alkisg>
Just boot the client with X_COLOR_DEPTH=16 and paste the output of xrandr
08:59
Of course not, you can select/define modes from the command line, with xrandr
09:00
Then once you found your desired mode, THEN you put it to lts.conf and reboot
09:00
You're sure you have only 2 MB, right? Is it a pre-2000 card?
09:06
When the client boots, at the first 1-2 seconds, even before displaying the BIOS POST, it should mention the videoram size
09:06brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) left irc: Ping timeout: 260 seconds
09:06
<NeonLicht>
2MB is what the BIOS says it has.
09:06
I haven't checked during boot... will do next time.
09:07
It's running at a higher resolution now, around 1280.
09:07
That's a huge step forward!
09:07
<alkisg>
The key is the xrandr output
09:08
Put it to pastebin and paste the URL here
09:09
If you want, you can join this irc channel from the client from this URL: http://webchat.freenode.net/?channels=ltsp
09:09
(for easier pasting)
09:10Nick change: gnunux -> Guest86163
09:10
<NeonLicht>
alkisg, http://www.pastie.org/2067372
09:11
<alkisg>
OK, all seem fine. Now, if the existing resolutions do not satisfy you, you can create new, arbitrary ones, it's really easy
09:11
<NeonLicht>
It seems it's using the maximun possible resolution for this card.
09:11JamesB192 (~quassel@gateway/tor-sasl/jamesb192) joined #ltsp.
09:11
<alkisg>
With `cvt` you get the new mode timings, and with xrandr you add the new mode
09:12
So you can e.g. select 1440x720, but that will have a bad aspect ratio
09:12
Or, 1280xsomething
09:12
Once you've found the best mode for you, you put it in lts.conf
09:12JamesB192 (quassel@gateway/tor-sasl/jamesb192) left #ltsp ("http://quassel-irc.org - Chat comfortably. Anywhere.").
09:13
<NeonLicht>
Modeline "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync <-- cvt gives me this
09:13
<alkisg>
No, not that one
09:13
1440*900*2=2592000
09:13
That's more than 2096128 which is your videoram
09:13
You need something lower than 2096128
09:14dobber (~dobber@213.169.45.222) left irc: Remote host closed the connection
09:14
<alkisg>
E.g. try 1280x800
09:15
That should give you an 1.6 aspect ratio, which is the same aspect ratio as 1440x900
09:15mikkel (~mikkel@80-71-132-15.u.parknet.dk) joined #ltsp.
09:16
<NeonLicht>
Modeline "1280x800_60.00" 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync
09:16
<alkisg>
After cvt, use `xrandr --addmode` to add the new mode
09:16
<NeonLicht>
And do I add the modeline to it?
09:16
<alkisg>
Then, xrandr --output xx --mode yyy to select it
09:16
Yes, see the man page of xrandr for the details, brb
09:16
<NeonLicht>
xx? yyy?
09:17
<alkisg>
Those just mean "put the correct parameters there" - see the man page, brb
09:23
Example:
09:23
$ cvt 1234 789
09:23
# 1240x789 59.89 Hz (CVT) hsync: 49.11 kHz; pclk: 79.75 MHz
09:23
Modeline "1240x789_60.00" 79.75 1240 1304 1432 1624 789 792 802 820 -hsync +vsync
09:23
<NeonLicht>
ama@ltsp20:~$ xrandr --output VGA --mode 1280x800
09:23
xrandr: Failed to get size of gamma for output default
09:23
<alkisg>
$ xrandr --newmode "1240x789_60.00" 79.75 1240 1304 1432 1624 789 792 802 820 -hsync +vsync
09:23
$ xrandr --addmode LVDS1 "1240x789_60.00"
09:23
$ xrandr --output LVDS1 --mode "1240x789_60.00"
09:24
<NeonLicht>
xrandr: Failed to get size of gamma for output default
09:24
<alkisg>
NeonLicht: what's the output of plain "xrandr" now?
09:24
Did you run `xrandr --newmode` ?
09:26
Also, where I put "LVDS1", you should put "default" there, not "VGA"
09:33drdata (~drdata@tw2.udallas.edu) joined #ltsp.
09:36drdata (drdata@tw2.udallas.edu) left #ltsp.
09:37
<NeonLicht>
Yes, I did. and it gave the error I told you.
09:37
Man, I have so many peopple around asking me things....
09:42dlezcano (~dlezcano@nat/ibm/x-gnqfygadqquqwlti) left irc: Ping timeout: 240 seconds
09:47
<alkisg>
NeonLicht: you told me the output of "--mode", not of "--newmode"
09:47
NeonLicht: ok, if you did --newmode, it should show up in the output of "xrandr". Can you pastebin that?
09:49
OK /me stops asking until NeonLicht has time to process all that...
09:50
<NeonLicht>
Sorry, I can't proccess it
09:50
I don't know what I pasted and what I did not, sorry
09:52
<alkisg>
No problem, if some time you need help with that, just ask again.
09:52
<NeonLicht>
I need help. I just can't understand what you last asked me.
09:52
<alkisg>
OK
09:52
Run these commands and paste ALL of their output to pastebin:
09:53
xrandr --newmode "1280x800_60.00" 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync
09:53
xrandr --addmode default "1280x800_60.00"
09:53
xrandr --output default --mode "1280x800_60.00"
09:53
xrandr
09:53
<NeonLicht>
xrandr: Failed to get size of gamma for output default
09:53
<alkisg>
ALL of their output to pastebin
09:53
<NeonLicht>
Thre first one gives that error, as I said before.
09:54
<alkisg>
Copy/paste both the commands and their output to pastebin, I'll see the errors there
09:55
<NeonLicht>
http://www.pastie.org/2067597
09:56
Ignore the first two ones, please, I copied them by mistake.
10:01
<alkisg>
I think the problem is the maximum width, it's configured to be less than 1280 in order to be able to support 1152x864 with the 2 MB videoram.
10:01
Can you try the following commands, to verify that your driver can display arbitrary resolutions?
10:02
xrandr --newmode "1152x800_60.00" 74.75 1152 1216 1328 1504 800 803 813 831 -hsync +vsync
10:02
xrandr --addmode default "1152x800_60.00"
10:02
xrandr --output default --mode "1152x800_60.00"
10:02
xrandr
10:02
<NeonLicht>
Again, the first one gives: xrandr: Failed to get size of gamma for output default
10:02
<alkisg>
OK, ignore that, continue with the rest..
10:02
<NeonLicht>
So does the second one.,
10:03
The third one too, but it also says: xrandr: Configure crtc 0 failed
10:03
<alkisg>
If the last one says " 1152x800_60.00 59.2* " (with a star right next to 1152x800) then your driver supports setting custom resolutions with xrandr
10:03
<NeonLicht>
http://www.pastie.org/2067629
10:03
<alkisg>
Otherwise it doesn't
10:04
1152x864 75.0*
10:04
So nope, it doesn't
10:04
You'd need to set a custom modeline and X_MODE_0 to get 1280x800 then
10:04
<NeonLicht>
So, don't I have any hope to go to a similar ration resolution?
10:04
OK, I see.
10:05
<alkisg>
Not with xrandr. But yes with a custom modeline in xorg.conf (generated by X_MODE_0)
10:07
<NeonLicht>
On lts.conf, right?
10:07
I've trying that before to no avail.
10:10
<alkisg>
Did you set a full mode line as returned by cvt?
10:10
Because if you just set the resolution to 1280x800, then this resolution doesn't exist, so it won't be used
10:10
<NeonLicht>
No, I didn't know about cvt b4
10:18
Can I add the full line on the lts.conf file?
10:24
<alkisg>
Yes, like in xrandr --newmode, but don't put quotes around the mode name
10:28
<NeonLicht>
OK, I try...
10:36
It ignored it completely... it runs again at 1152x864
10:39
<alkisg>
It looks like you're stuck with that mode then.
10:39
Has anyone used ACLs? https://help.ubuntu.com/community/UbuntuLTSP/ACLSupport
10:39
Do they work OK over nfs? (fat clients)
10:40* alkisg is trying to write a script to offer "read-write shared folders for groups of students"...
10:41
<NeonLicht>
ACLs?
10:41dlezcano (~dlezcano@AToulouse-159-1-37-78.w92-134.abo.wanadoo.fr) joined #ltsp.
10:42
<NeonLicht>
Is the NFS question intended for me, alkisg?
10:42
<alkisg>
Access Control Lists, they're for more advanced file system permissions. No, it's directed to anyone in the channel
10:44
<NeonLicht>
OK, that's what I thought :)
10:54
<knipwim>
alkisg: according to this post it works: http://ubuntuforums.org/showthread.php?t=1273189#post_message_9386982
10:55
<alkisg>
knipwim: thanks, sounds good, I'll try it now
10:57
<knipwim>
another random comment from the web: "Make sure your server is running NFSv4 and your client is mounting it as nfs4 and not just nfs. Then your ACL will work."
10:58
<alkisg>
Ouch. OK that will have to wait for 12.04 then, we're using nfs v3 now
11:01
<knipwim>
check, confirmation from a reliable source: http://nfs.sourceforge.net/#faq_a6
11:02
6th bullet
11:03
<alkisg>
7th bullet: "NFS Version 4 combines the disparate NFS protocols (stat, NLM, mount, ACL, and NFS) into a single protocol"...
11:03
Doesn't that mean that ACLs were there before nfs 4 too?
11:04
"The Linux NFS server in the mainline kernels does not support this protocol, but many distributions include patches that provide NFS_ACL support in their NFS implementation."
11:06
--- another thing.. has anyone noticed that /etc/profile isn't sourced by users that logon on ltsp clients?
11:06
So e.g. setting umask there doesn't work
11:09vagrantc (~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) joined #ltsp.
11:10
<alkisg>
Ah, reported there: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542270
11:11
<vagrantc>
oh, that one
11:11
<alkisg>
It doesn't look hard to fix :)
11:11
<vagrantc>
doesn't it make assumptions about what shell is used?
11:12
<alkisg>
Isn't the shell noted in /etc/passwd?
11:12
<vagrantc>
do you know which shells read /etc/profile?
11:13* alkisg hasn't looked for a solution, he just bumped into that problem
11:13
<vagrantc>
although i think we hard-code /bin/sh in LDM, no?
11:13brunolambert (~brunolamb@gw-sherb.rlnx.com) joined #ltsp.
11:13
<alkisg>
I think even /bin/sh should have a "login" parameter
11:13
man sh => A login shell first reads commands from the files /etc/profile and .profile if they exist
11:19
<NeonLicht>
Hey vagrantc! How are you doing? :)
11:20* vagrantc waves
11:21
<vagrantc>
NeonLicht: you?
11:21
er, i'm doing fine, you? :)
11:21
<NeonLicht>
Not bad, vagrantc thanks...
11:21
<vagrantc>
NeonLicht: still using ion3, or did you ever give tritium a try? :)
11:21
<NeonLicht>
Well, a few clients are driving me crazy, and alkisg has been helping me to diagnose the probs.
11:22
<vagrantc>
oh
11:22
<TheMatrix3000>
Have a problem, what would cause the fastuserswitch applet to work for Local Users but not LDAP users
11:22
<vagrantc>
alkisg is good at that :)
11:22
<NeonLicht>
Not anymore, vagrantc, I moved to NotIon already ;)
11:23* vagrantc 's curiosity is piqued
11:23
<NeonLicht>
Yes, vagrantc, he is... and way patient! He has helped me even when I couldn't thing much (I had four peopple around ---one of them installing Debian on is hox, and asking me on every step, hehe)
11:24
<TheMatrix3000>
lol
11:32
<NeonLicht>
s/thing/think/ :D
11:43dgroos (~dgroos@63.225.132.145) left irc: Ping timeout: 260 seconds
11:58bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) joined #ltsp.
12:02
<TheMatrix3000>
how do i force ltsp users not to have the window effects etc
12:06
basically force and disable users from using the "Extra" Visual Effects
12:06
<vagrantc>
search for disabling compiz
12:07
i don't know the magic off my head, but it's some gconf-tool thing
12:09
<alkisg>
sudo gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /desktop/gnome/session/required_components/windowmanager metacity
12:09* alkisg misses ltspbot
12:10* vagrantc too
12:10
<TheMatrix3000>
just run that command?
12:10
<alkisg>
TheMatrix3000: yes
12:11
It takes effect on the next user login, no reboot required
12:11
<TheMatrix3000>
ok
12:11
is there a document out there with that in it
12:11
<alkisg>
Not ltsp related, but maybe it's documented somewhere in the gnome docs
12:12
<TheMatrix3000>
basically we had our ltsp server load at 70.0 a minute ago
12:12
not good
12:12
<alkisg>
Are you using LDM_DIRECTX=True?
12:12
<TheMatrix3000>
how much ram and processor power would you recommend for 50 users
12:12
where would i see LDM_DIRECTX=True
12:12
<alkisg>
In lts.conf
12:13
It's a setting that lowers the cpu usage dramatically, at a cost in security
12:13
I.e. it disables X-traffic encryption
12:13
<TheMatrix3000>
oh
12:14
<alkisg>
This is documented in the ltsp docs, see the irc /topic for the link to the docs
12:14
<TheMatrix3000>
ok
12:15
<Hyperbyte>
alkisg, vagrantc... I don't have a problem hosting ltspbot, if that's the problem.
12:15
<TheMatrix3000>
alkisg, I will need to ltsp-update-image after wont i
12:16
<Hyperbyte>
TheMatrix3000, you only have to run ltsp-update-image if you modify files inside the /opt/ltsp/ folder
12:16
<alkisg>
Hyperbyte: no idea what the problem is, if you want, send a mail with your offer in the ltsp mailing list, maybe sbalneav will reply there
12:16
<TheMatrix3000>
well LDM_DirectX
12:16
that's in lts.conf
12:16
which is in the tftpboot/ltsp/i386 folder
12:17
oh
12:17
i see
12:17
<alkisg>
:)
12:17
<Hyperbyte>
You answered your own question. :-)
12:17
<TheMatrix3000>
didn't read deep enough
12:17
lol
12:17
<Hyperbyte>
You just have to reboot the clients in this case.
12:17
<TheMatrix3000>
ok
12:17
and how risky is that change
12:17shogunx (~shogunx@2001:4978:106:1:21e:33ff:fe47:32f5) left irc: Remote host closed the connection
12:17
<TheMatrix3000>
passwords are still secure right?
12:18
<Hyperbyte>
TheMatrix3000, no, not when someone sniffs network traffic.
12:18
That's the whole point behind X traffic encryption
12:18
<alkisg>
Login passwords, yes, but x traffic also contains all the keyboard buttons *after* login
12:18
<TheMatrix3000>
ah, yea...don't want to do that on this network
12:18
<Hyperbyte>
You have to ask yourself: are my users smart enough for this?
12:18
<alkisg>
So passwords for web sites outside of https will be sniffable
12:18
<TheMatrix3000>
well, i moved pidgin to ltsp-localapps
12:18
and it seems to have helped
12:19
<Hyperbyte>
alkisg, passwords for https too
12:19
<TheMatrix3000>
yea, that's no bueno
12:19
not doing that
12:19
<alkisg>
Yeah
12:20
<Hyperbyte>
TheMatrix3000, your choice. I have a company network, on which I run a MAC filter. So people can't connect their own devices.
12:20
I enabled LDM_DIRECTX
12:20
Even without the mac filter, I doubt anyone here would be smart enough to capture the network traffic and get the keypress sequences out
12:20
<TheMatrix3000>
true
12:20
good point
12:21
<Hyperbyte>
And if they did, they still wouldn't have the login passwords, since those are encrypted.
12:21
<TheMatrix3000>
ah ok
12:21
<highvoltage>
well, if people use the application server then chances are they can get a shell on it too
12:21
<Hyperbyte>
Only the passwords entered after login, which are usually passwords of their private accounts anyways, and I don't really care about those.
12:21
<highvoltage>
and having shell access on a machine isn't that far from getting root on a machine (if you follow security updates at all)
12:22
<TheMatrix3000>
[Default] LOCAL_APPS=True LOCAL_APPS_MENU = True LOCAL_APPS_MENU_ITEMS = firefox LDM_THEME = InsuranceAgentsBlueTheme TIMEZONE = America/New_York TIMESERVER = 192.168.4.2
12:22
thats my current one
12:22
<Hyperbyte>
highvoltage, yeah, I think the point of LDM_DIRECTX is to prevent someone from connecting to a random lan port and sniff passwords all day.
12:22
<TheMatrix3000>
so i just need to add that line in there right?
12:22
well i can always renable it
12:22
so
12:22
this will help until i set up and deploy ltsp-cluster
12:22shogunx (~shogunx@2001:4978:106:1:21e:33ff:fe47:32f5) joined #ltsp.
12:23
<highvoltage>
well fwiw I usually do LDM_DIRECTX too if security isn't a concern
12:23
<TheMatrix3000>
ok, basically set LDM_DIRECTX=True
12:23
and thats it
12:23
done
12:23
<alkisg>
Yup, and client reboot
12:25
Heh. `ssh -X user@localhost gedit` doesn't exit when the user closes gedit, because gconfd remains running. It seems that remote X will be breaking more and more in the future...
12:25
<vagrantc>
that sort of thing has been a problem for ages
12:26
LDM works around it by killing the ssh connection at some point (or at least used to)
12:28
<TheMatrix3000>
did i mention how awesoem you guys are
12:40
<Gadi>
alkisg: ssh -X user@localhost gedit </dev/null >/dev/null 2>&1 should exit
12:41
I believe it was the </dev/null that helped cure things
12:41
(at least with Xsession)
12:42
<alkisg>
Gadi: nope, still not working for me
12:42
<Gadi>
maybe that was just for a session
12:43
<alkisg>
Maybe gnome-session notifies gconfd to shut down
12:43
While when it auto-spawns (like with gedit), it doesn't know when to quit
12:46
Is there any way with ACLs to enforce a specific mode (0770) for all files/subdirs in a given (shared) directory? So that the users cannot ever change that mode? Or should I be looking at e.g. bindfs?
12:58alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
12:58dgroos (~dgroos@63.225.132.145) joined #ltsp.
13:01mistik1 (mistik1@unaffiliated/mistik1) joined #ltsp.
13:03alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
13:09vagrantc (~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) left irc: Quit: leaving
13:11Gadi (romm@ool-18bbe47a.static.optonline.net) left #ltsp.
13:23
<stgraber>
alkisg: posix ACLs with the default: ACL might achieve what you're looking for
13:24
<alkisg>
stgraber: thanks, looking for that...
13:24
<stgraber>
alkisg: setfacl -m group:blah:rwX -R <dir> && setfacl -m default:group:blah:rwX -R <dir>
13:25
<alkisg>
I tried that but in the standard, non-posix mode - let me try it again in posix mode
13:25
<stgraber>
alkisg: that should first set the rights for blah on all files and dirs, then set the default entry for all of them so that future created items inherit the same rights
13:25
<alkisg>
The default works for inheritance, but if the user decides that he doesn't want to share that file anymore, he can remove the group w bit
13:25
(which defeats the purpose of the shared folder)
13:30
<stgraber>
hmm, indeed. Not sure if you can use the sticky bit with posix acls, if you can, that might do the trick.
13:33
<TheMatrix3000>
so anyone here running ltsp cluser?
13:33
cluster*
14:06mikkel (~mikkel@80-71-132-15.u.parknet.dk) left irc: Quit: Leaving
14:09TheMatrix3000 (~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com) left irc: Quit: ~ Trillian Astra - www.trillian.im ~
14:35
<dead_root>
yes TheMatrix3000
14:43
<alkisg>
http://brainstorm.ubuntu.com/idea/3916/ ==> advices the use of bindfs too (or even ntfs :P)
14:43staffencasa (~staffenca@128-193-147-249.oregonstate.edu) left irc: Ping timeout: 260 seconds
14:55
<tl1000s77>
has anyone here had any luck mounting shares on a ltsp client with pam_mount?
15:01
<abeehc>
i had it working to some extent with 9.04
15:01
don't think i ever got it to unmount
15:08staffencasa (~staffenca@128-193-147-249.oregonstate.edu) joined #ltsp.
15:13
<tl1000s77>
I've had no luck with 10.04.2 so far with pam_mount
15:14
These are the errors from the log file...
15:14
sshd[2097]: pam_mount(pam_mount.c:172): conv->conv(...): Conversation error
15:14
sshd[2097]: pam_mount(pam_mount.c:454): warning: could not obtain password interactively either
15:15
<abeehc>
what are you trying to mount?
15:16
<tl1000s77>
a windows share
15:18
<abeehc>
you'll want to take the command you have in your pam_mount.conf and make sure your user can mount it from bash without having to enter a password
15:19alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
15:20
<abeehc>
nvm that command's not in there i guess
15:20
my latest one looks like this
15:20
http://pastebin.com/D4DJ4KRv
15:23
<tl1000s77>
I can't mount it as the user...I get "mount: only root can do that"
15:30
<Hyperbyte>
I have no idea how pam_mount works whatsoever, but don't you solve this by using /etc/fstab?
15:34bencer (~bencer@heal.cauterized.net) left irc: Quit: No Ping reply in 180 seconds.
15:34bencer (~bencer@cl-141.lis-01.pt.sixxs.net) joined #ltsp.
15:36dead_root (~dead_root@76.75.3.174) left irc: Quit: Leaving...
15:38F-GT (~phantom@ppp121-45-176-240.lns20.syd7.internode.on.net) left irc: Ping timeout: 240 seconds
15:40bencer (~bencer@cl-141.lis-01.pt.sixxs.net) left irc: Ping timeout: 260 seconds
15:46Gnoze5 (~Gnoze5@static-b4-252-232.telepac.pt) joined #ltsp.
15:46
<Gnoze5>
yellow
15:58veloutin (~vvinet@2001:470:8829:1000:227:eff:fe25:ee64) left irc: Remote host closed the connection
16:10brunolambert (~brunolamb@gw-sherb.rlnx.com) left irc: Ping timeout: 252 seconds
16:22bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) left irc: Ping timeout: 246 seconds
16:22bencer (~bencer@cl-141.lis-01.pt.sixxs.net) joined #ltsp.
16:53staffencasa (~staffenca@128-193-147-249.oregonstate.edu) left irc: Ping timeout: 246 seconds
17:50andygraybeals (~andy@80.sub-75-218-146.myvzw.com) joined #ltsp.
17:54loathing (~khudson@internal-nat.djnetworks.net) left irc: Ping timeout: 252 seconds
18:05Guerdal82|atWork (~Guerdal82@LLagny-156-35-33-131.w193-251.abo.wanadoo.fr) left irc: Ping timeout: 240 seconds
18:15F-GT (~phantom@ppp121-44-156-3.lns20.syd7.internode.on.net) joined #ltsp.
18:29mistik1_ (mistik1@unaffiliated/mistik1) joined #ltsp.
18:30mistik1 (mistik1@unaffiliated/mistik1) left irc: Ping timeout: 244 seconds
18:30Nick change: mistik1_ -> mistik1
18:32andygraybeals (~andy@80.sub-75-218-146.myvzw.com) left irc: Ping timeout: 240 seconds
18:35administrator_ (~administr@dhcp-0-50-ba-26-4e-ab.cpe.mountaincable.net) joined #ltsp.
18:36
<administrator_>
Anyone ever try using an HP t5565 thin client with LTSP?
18:36
We have some HP t5565 thin clients - they boot LTSP but can only run with 800x600 resolution
18:37mistik1_ (mistik1@unaffiliated/mistik1) joined #ltsp.
18:37mistik1 (mistik1@unaffiliated/mistik1) left irc: Ping timeout: 260 seconds
18:37Nick change: mistik1_ -> mistik1
18:37Nick change: administrator_ -> noobie_
18:38
<noobie_>
The integrated graphics card appears to be a VIA, but it setting XSERVER=via in LTS.conf makes the screen go blank
18:39
Anyone around who know anything about using HP thin clients?
18:42
We have a class room with 30 clients - 28 are old P4 desktops and they run fine - 2 are HP t5565 thin clients and the video is limited to 800x600 - any ideas?
18:45
Thud...oops sorry, BUMP.
18:58noobie_ (~administr@dhcp-0-50-ba-26-4e-ab.cpe.mountaincable.net) left irc: Quit: Ex-Chat
19:45otavio (~otavio@debian/developer/otavio) left irc: Quit: leaving
19:45otavio (~otavio@189.114.111.55) joined #ltsp.
19:45otavio (~otavio@189.114.111.55) left irc: Changing host
19:45otavio (~otavio@debian/developer/otavio) joined #ltsp.
20:12Guerdal82|atWork (~Guerdal82@LLagny-156-35-33-131.w193-251.abo.wanadoo.fr) joined #ltsp.
20:18chokesmaster (~chokesmas@bas7-sherbrooke40-2925312439.dsl.bell.ca) joined #ltsp.
20:52TheMatrix3000 (~TheMatrix@oh-76-1-33-172.dhcp.embarqhsd.net) joined #ltsp.
20:52
<TheMatrix3000>
if i build an ltsp cluster
20:53
can i just add servers to it?
20:53
like to the cluster
21:32TheMatrix3000 (TheMatrix@oh-76-1-33-172.dhcp.embarqhsd.net) left #ltsp.
22:49NeonLicht (~NeonLicht@darwin.ugr.es) left irc: Ping timeout: 240 seconds
22:50NeonLicht (~NeonLicht@darwin.ugr.es) joined #ltsp.
22:51vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) joined #ltsp.
23:19alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
23:25vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) left irc: Quit: leaving
00:00--- Wed Jun 15 2011