[00:33] <blurrorz> hi guys, im new to linux, i hope to get along!
[00:34] <wxl> you'll do fine blurrorz
[00:34] <blurrorz> haha thanks... :P
[00:35] <blurrorz> im trying to verify if my video drivers have installed with the lubuntu installation
[00:36] <wxl> if you see stuff, they probably have :)
[00:36] <blurrorz> haha yeah... but sometime its and old or more basic version of the driver...
[00:37] <wxl> seriously though, if there's no reason to be concerned, you're probably good to go
[00:37] <Nixus> same blurrorz, using lubuntu?
[00:38] <blurrorz> yeah
[00:38] <Nixus> cool
[00:38] <Nixus> anyone know how
[00:38] <Nixus> is there a way to change the direction the window minimize animation goes? whenever I minimize/maximize a window, It always goes dow
[00:39] <Nixus> as if the panel is down, but it's on top
[00:39] <Nixus>  
[00:39] <drkokandy> Nixus - have you logged out and logged back in since you made that change?
[00:39] <Nixus> yes
[00:39] <Nixus> even restarted
[00:39] <Nixus> 3 times*
[00:44] <Nixus> AH, ouchy, I can't seem to get my sound working :'-(
[00:45] <Nixus> anyone help?
[00:46] <ianorlin> try unmuting stuff in alsamixer is the easiest place to start but sound problems are quite annoying
[00:46] <ianorlin> also lspci to tell what kind of sound is useful
[00:48] <Nixus> hmm, kinda new here, can you explain in a n00b fashion? sorry
[00:48] <ianorlin> run lspci in a terminal to show what kind of sound chip you have
[00:48] <wxl> before you do that, though, run `alsamixer` in terminal and make sure nothing's muted
[00:49] <Nixus> audio device: Advanced Micro Devices, Inc.
[00:50] <Nixus> alsamixer shows: card: hd-audio generic chip: ati r6xx hdmi Item: s/pdif [off]
[00:50] <wxl> oh no not hdmi
[00:51] <Nixus> \o/
[00:51] <Nixus> so is it trying to output sound through hdmi?
[00:53] <wxl> it *MAY* be
[00:53] <wxl> hdmi sound can be a pain
[00:53] <wxl> check to see if anything is muted
[00:53] <Nixus> oh no!
[00:53] <wxl> if you see 00 at the bottom of the channels that's NOT muted
[00:53] <wxl> if you see MM it is muted
[00:54] <wxl> it would be green if it's not muted
[00:54] <ianorlin> I disabled it on my motherboard
[00:54] <ianorlin> and just use the headphone jack
[00:54] <Nixus> shows MM in cyan (blue)
[00:54] <ianorlin> but that would be in bios
[00:54] <wxl> MM is muted
[00:54] <Nixus> ok, I'll try
[00:55] <wxl> arrow over to the right channel and hit M
[00:55] <wxl> hi drkokandy
[00:55] <wxl> welcome
[00:55] <Nixus> right channel?
[00:55]  * wxl facepalms
[00:55] <wxl> you'll find i'm REALLY good at that
[00:56] <drkokandy> lol
[00:56] <Nixus> sorry
[00:56] <blurrorz> hey guys what do you guys use for rdp in lubuntu?
[01:00] <Nixus> ?
[01:00] <Unit193> blurrorz: Server or client?
[01:01] <blurrorz> client... sorry
[01:01] <Unit193> blurrorz: freerdp, or that plus remmina (pre vivid.)
[01:01] <blurrorz> ive tried rdesktop... but in fullscreen mode the lubuntu taskbar stays on top and hides the windows taskbar... its quite annoying lol
[01:03] <Nixus> so should I just disable hdmi in bios?
[01:05] <blurrorz> have you tried a search online about switching audio output in lubuntu? sometimes you can get your answer!
[01:07] <blurrorz> REMMINA seems nice... ill give it a try later... thanks
[01:08] <Nixus> hmmm. people are talking about being a slider in alsamixer, I don't seem to see one
[01:09] <blurrorz> are you on a laptop ?
[01:09] <Nixus> yes
[01:10] <blurrorz> theres a good chance you can find the exact model number of audio device
[01:10] <blurrorz> and then find a driver for ubuntu for your device...
[01:11] <blurrorz> theres a good chance you can find the exact model number of audio device... if you check online with your laptop model number
[01:15] <blurrorz> any luck ?
[01:17] <blurrorz> okay.. lol
[01:18] <drkokandy> aw
[01:18] <nicholas> haha!
[01:18] <nicholas> got it.
[01:19] <nicholas> someone else had the same thing on the lubuntu forum the same laptop. got it working my creating a file called "asoundrc" and put some stuff into it. worked like a charm!
[01:19] <nicholas> now, is there a way to get a volume indicator?
[01:19] <blurrorz> lol you changed nickname ?
[01:20] <blurrorz> dont you have a speaker icon on the taskbar ?
[01:20] <nicholas> yeh, change between nixus and this
[01:20] <blurrorz> :P
[01:20] <nicholas> didn't have an icon in the bar before, but have one now :-)
[01:20] <nicholas> but is there a popup one?
[01:21] <blurrorz> well if you click on it there should be a volume control popping up... other than that im not sure what you mean
[01:22] <nicholas> like here:
[01:22] <nicholas> http://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0CAcQjRw&url=http%3A%2F%2Fwww.digit.in%2Fforum%2Fsoftware-q%2F125548-need-volume-indicator-bar-windows-similar-linux-mint-volume-bar.html&ei=18S1VLyXE8P9yQTN74KICA&bvm=bv.83640239,d.aWw&psig=AFQjCNFUfS9-Ira0EXIV2TJEnhGcM7LI6w&ust=1421284947133808
[01:23] <nicholas> or here: http://i.stack.imgur.com/GEFwy.jpg
[01:25] <blurrorz> thats beyond my knowledge...  i dont know how you could change it to what it is by default...
[01:26] <nicholas> ok, thank you so much for your patience with me (me=n00b)
[01:27] <blurrorz> np
[01:28] <blurrorz> other than the way it looks is there any useful reason to change it to what you want ?
[01:29] <nicholas> well it's more convenient and more easily viewable than the puny little applet in the panel
[01:29] <nicholas> and it is more detailed, as it should have many levels
[01:30] <blurrorz> Lol :P ok then
[01:31] <nicholas> but not neccisary
[01:32] <blurrorz> yeah i figured :P
[01:34] <nicholas> oh, mama mea, just got it working. put xfce4-volumed :-)
[01:35] <nicholas> i used xfce before and was like, go figure, lxde already uses some xfce stuff (powermanager, etc) and yaya, happiest person :-)
[01:36] <nicholas> I'm out, gotta go! TY!
[01:39] <nicholas> NVM, can stay a bit longer
[01:39] <nicholas> says that the volume mute, volume lower and volume raise failed, even though it works... strange
[01:41] <blurrorz> yeah...
[01:41] <nicholas> works though! :-)
[01:41] <blurrorz> :P
[01:42] <nicholas> are there any major differences between openbox and xfwm4? IDK
[02:10] <blurrorz> hey thanks guys... remmina works great"!
[02:40] <sak> Hello guys. I am new to this channel so please forgive my ignorance. I am not sure if this is the place to discussion lubuntu ideas for quality assurance or ideas to implement in the upcoming lubuntu releases
[02:41] <ianorlin> no that is more the job of the lubuntu brainstorming team
[02:48] <sak> what is this chat used for if you don't mind me asking?
[02:53] <ianorlin> maybe #lubuntu-offtopic but not many on irc right now
[02:54] <holstein> sak: this channel is about support for the lubuntu operating system
[02:54] <holstein> !contribute | sak
[02:57] <sak> Holstein, when you say support, did you mean quality support or technical support?
[02:58] <holstein> sak: this is, as the /topic states, support.. for the users of the lubuntu operating sytem
[02:59] <holstein> sak: if one is using lubuntu, and wants support, one can ask for help here from a volunteer in the community here.. or, one can hang here and volunteer said support
[02:59] <holstein> sak: if you want to "contribute", you can see the contribute link for helping upstream, or, as ianorlin mentioned, the "dev" channel is typically #lubuntu-offtopic,..
[03:05] <sak> Thank you holstein. This will be a very useful channel as I am running Lubuntu on my laptop as I type ;-)
[09:37] <talsamon> hello, I tried to make a ".desktop-file", after this lxpanel don't work anymore, I purged lxpanel\* and reinstall it, then the desktop was puzzled - what happens with a so simple action ?, now I had to reinstall
[10:13] <talsamon> hello, any answer to my question ?
[11:40] <Newk> hi, i'm on lubuntu 14.04 and notice something strange.. when i change a menu-item with properties to "execute in terminal emulator" it does open LXTerminal but doesn't execute the command, nor does it set current dir to the set "working directory"
[15:06] <Newk> hi
[15:49] <talsamon> hello, how to fix, the lxpanel crashes in 14.10 ?
[16:47] <Newk> i get the impression this channel is not watched much
[16:48] <teward> Newk: it's not as active as other,s no.
[16:48] <ianorlin> Newk well feel free to help out
[16:49] <Newk> i dont know much about bugs in lxde
[16:49] <testdr> Newk: hi (here you got your missing greeting)
[16:49] <Newk> i try where i can
[16:50] <ianorlin> one way to learn about things is lurking and looking at man pages for stuff you don't know that is how I learned
[16:50] <Newk> (12:40:57) Newk: hi, i'm on lubuntu 14.04 and notice something strange.. when i change a menu-item with properties to "execute in terminal emulator" it does open LXTerminal but doesn't execute the command, nor does it set current dir to the set "working directory"
[16:51] <Newk> i bet i cannot find much about that in man pages
[16:52] <Newk> but it might give a hint if i knew more about the inner workings of lxde
[16:52] <testdr> Newk: i user something like this in the starter-command-line:   xterm   -e   "ps   xfa;  data;  read key"
[16:52] <ianorlin> ah I think this is a known bug
[16:53] <testdr> Newk: sorry -- typing error its not "data" ist "date" to display current time
[16:54] <Newk> why would i want to display current time?
[16:54] <testdr> Newk:  you may blame me - but i wont care -- this was only one of my samples, i use --
[16:55] <Newk> i dont blame anyone but my own lack of knowledge, thats why i' m here to ask
[16:56] <testdr> Newk: i gave you a sample - you dont want to try and check?
[16:56] <Newk> yes i was at it
[17:00] <Newk> testdr: that seemed to work!
[17:01] <testdr> Newk: fine - if this solves your problem -- cause normal xterm font is small - i usually use the optione "xterm  -fn  9x15 ......"
[17:01] <Newk> so i circumvent the issue by starting up a terminal with given commands beforehand instead of relying on the menu-configuration
[17:02] <Newk> i could start a sh script
[17:02] <testdr> Newk: yes - and you can blame me for this - i only noticed it works not how expected and therefor always used this "old way".
[17:02] <Newk> ok! glad you could help me out :D
[17:02] <Newk> thanx!
[17:03] <testdr> Newk: i dont know if some propertys of such starter-desktop-files is interpreted in full from other windowmanagers
[17:03] <ianorlin> I think starting console applications from menu is unforatnetly broken :(
[17:03] <testdr> Newk: for example: you wont get any activity-response (spining mouse-curser etc.) like in some other window-managers
[17:03] <Newk> i stuck to lxde for some time now.. i quite like it
[17:04] <Newk> i think its the best.. and curious what the fusion with qt will bring
[17:04] <ianorlin> https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1289881
[17:04] <testdr> ianorlin: starting applications from menu is working for me - but i have to copy such a starter-file into the global directorys, where all other app-starter-files are
[17:05] <ianorlin> no but htop doesn't for me as in this bug
[17:07] <Newk> testdr: yes you mean the applications folder with all those .desktop files.. if i want to add one i also copy ones from similar programs
[17:07] <testdr> yep
[17:08] <Newk> i once tried this program "main menu editor" it worked (though it uses java) but i sometimes got doubles
[17:09] <testdr> for the lxpanel-entries is possible to manually (with editor) add a local (in ~/bin/) desktop-file --- i never tried this menu-editor
[17:19] <Newk> testdr: do you know something i could add to; either that line for xterm. or to sh script so that it won't close xterm after execution... so i can read what was logged
[17:19] <testdr> Newk: my sample did use " ...;  read key"  a normal shell-command to wait for some input with return-key
[17:20] <Newk> ah that was that for!
[17:20] <Newk> i allready wondered :3
[17:20] <holstein> whats the goal? click a button, and run in terminal?
[17:20] <holstein> but, you want it to be the lxterm?
[17:21] <testdr> Newk: i did not write a shell-script for those few commands -- if you put everything into a shell-script (with bash-bang and executable) you can use a lot more functions
[17:21] <Newk> well that would be best so i can copy paste from it
[17:21] <Newk> hello holstein :)
[17:21] <holstein> you dont want to pipe some output?
[17:24] <Newk> no just to leave terminal op in the event of bugs so i can copy/paste them to report to dev
[17:24] <Newk> *open
[17:24] <holstein> terminal operation?
[17:24] <holstein> Newk: what bugs?
[17:25] <holstein> "they" may not want that.. i would try and just follow the normal bug reporting, and included tools, when possible..
[17:25] <holstein> !bug
[17:25] <Newk> could help for all kinds of testing
[17:25] <holstein> this is an interesting time for lxde, as its likely transitionning
[17:25] <holstein> transitioning*
[17:26] <holstein> it *could* help, but, its not necessary.. you can always look at logs, when asked, if the system hasnt locked or kernel panic'd
[17:26] <Newk> for everything that was executed there is a log?
[17:27] <holstein> Newk: i didnt say, or mean to imply that, but, thats not important, since, you need not log *everything* that was ran
[17:27] <testdr> ask the NSA - it might record everything?
[17:27] <holstein> for example, if its not in the ubuntu repos, is it going to get attention?
[17:27] <Newk> lol
[17:27] <holstein> you can find a *lot* of bugs for some things like skype, but, its closed, and there is not much that can be done
[17:28] <holstein> there actually should be a "cant fix" or "upstream should fix" flag
[17:28] <Newk> i would drop bugs at skype for that... not at ubuntu community
[17:29] <holstein> Newk: they dont welcome them, so, users file with ubuntu, which is fine, im just suggesting, dont get too hung up on logging *all* your output like that
[17:29] <Newk> skype did bug is enough when dropping support for alsa and only went for pulsaudio abstraction
[17:29] <testdr> holstein: at last - i cant wait for fixing bugs, i need working now. For example dnsmasq using without cache, why use it at all, if used without cache?
[17:29] <holstein> there are logs.. x logs, kernel logs.. if a "dev" sees the bug, they will ask for what they need
[17:30] <holstein> Newk: nothing about ubuntu/linux/pulse/alsa prevents skype from supporting it.. but, to stay constructive, for the end user, there is little need to constantly monitor log output, since, it cant be addressed anyway
[17:30] <Newk> yes that was what i was thinking from a testing user perspective
[17:30] <holstein> for you, you can just follow the normal bug reporting proceedure
[17:31] <holstein> look for existing bugs, isolate and test.. join existing bugs, or make new ones as needed, and get others, such as myself, to reproduce
[17:31] <holstein> and, also, exercise patience, as, lxde is transitioning..
[17:31] <holstein> testing the iso's *is* helpful
[17:31] <holstein> http://iso.qa.ubuntu.com/ and easy to address
[17:32] <Newk> yes with lxde i have patience... it came a long way already with allot ahead too
[17:32] <Newk> its my main usage in linux
[17:32] <Newk> even on that little raspberry i got
[17:33] <Newk> right now.. with pidgin
[17:35] <holstein> you can always ask for support in #ubuuntu for pidgin, since it wont be lxde/lubuntu specific..
[17:36] <holstein> #ubuntu
[17:37] <holstein> that channel is more active, and has more users, and the pidgin application is the *same*..
[17:37] <Newk> no i didnt meant i was testing that other then using it right now on raspberry to chat here... i was using that terminal thing for another program on another machine
[17:38] <Newk> thanx for the advice tho :D
[17:43] <Newk> testdr: -e flag works with lxterm too
[17:43] <testdr> Newk: then the man-page for lxterminal is correct
[17:44] <Newk> yes just did lxterm -h to find out
[17:44] <testdr> Newk: oops - lxterm is for my setup the same like xterm
[17:49] <Newk> indeed.. but lxterminal also supports -e i just found out
[17:49] <Newk> testdr: ^
[17:50] <Newk> read key is not ideal.. i rather have it give a prompt so that it would only close when i tell it to
[17:50]  * Newk googles
[18:52] <gil> Hi - is there an appropriate channel to discuss 15.04?
[18:55] <wxl> as good as any gil
[18:55] <gil> okay
[18:55] <wxl> we don't have a qa channel
[18:55] <wxl> or a dev channel for that matter
[18:55] <gil> I'm not sure what the official term for the little icons that you click to expand things? Widgets perhaps?
[18:55] <gil> For example, in the software updater, you can click a little triangle usually to expand more information
[18:55] <gil> but anyhow, in 15.04 these are all invisible for me
[18:56] <gil> was just wondering if this is a known issue
[18:56] <wxl> screenshot for me?
[18:56] <wxl> which 15.04 are we talking about?
[18:57] <gil> Okay I can't take a screenshot because I have no updates to do at the moment and I can't think of another interface that features them
[18:57] <gil> but if you check this out - http://www.opensourceforu.com/wp-content/uploads/2012/05/Ubuntu1204-04-Software-updates.png
[18:57] <gil> the small triangle next to Details
[18:57] <gil> that is what is invisible
[18:57] <wxl> which 15.04?
[18:59] <gil> wxl here's what shows for my version number - http://pastebin.com/3jVmBgD4   I did a force upgrade from 14.10 using software updater with the -d flag and have since kept it up to date
[18:59] <wxl> hm
[18:59] <wxl> assumedly that would give you the latest daily
[18:59] <wxl> i'm not 100% sure
[18:59] <wxl> what graphics driver are you using?
[19:00] <gil> It'll be the integrated intel driver for the 4000 chipset
[19:00] <gil> I'll find you an exact name
[19:02] <gil> wxl it's the i915 driver
[19:02] <wxl> do you have any other graphics issues?
[19:03] <gil> Nope, none at all
[19:03] <gil> it's only the little triangle widgets that vanish
[19:03] <wxl> ok so that's probably not an issue but i think i've heard of problems with that driver
[19:03] <wxl> so that's something to keep in the back of our mind
[19:04] <wxl> no problems with 14.10 i'm assuming?
[19:04] <gil> so it's not a major problem, in fact I've been surprised at how well the 15.04 works for me at this stage
[19:04] <wxl> well usually new versions build on the quality of previous ones, so ;)
[19:04] <gil> wxl there was one thing with 14.10 where every time I logged in I used to get a bunch of system error boxes appear
[19:04] <gil> about 5 or 6
[19:04] <wxl> things may get funky when we roll lxqt out
[19:04] <gil> I would just cancel them away and get on with it
[19:04] <wxl> that may be because you had a previous crash that's still sitting around
[19:04] <gil> but these boxes stopped appearing since I did the 15.04 u/g
[19:05] <wxl> yeah i imagine it would wipe those out in the process
[19:05] <wxl> if you have similar problems, either continue or wipe the files from /var/crash
[19:05] <gil> but that's it, rock solid apart from that :)
[19:05] <gil> ....oh yeah and chrome always crashes when I start it up cold
[19:05] <wxl> chrome or chromium?
[19:05] <gil> chrome
[19:05] <wxl> hm
[19:05] <wxl> how much memory you have?
[19:06] <gil> but I set it to ignore future crashes so I never really see it crash
[19:06] <gil> 4GB
[19:06] <wxl> hm
[19:06] <wxl> what version are you using?
[19:06] <gil> I'm on the stable branch
[19:06] <wxl> k
[19:06] <wxl> when you say "start it up cold" what is the alternative?
[19:06] <gil> Version 39.0.2171.99 (64-bit)
[19:07] <gil> okay so basically, I start up Lubuntu and log in, click the Chrome icon, I then get a crash dialog box and Chrome relaunches itself and then everything is fine
[19:07] <gil> stable for hours after that
[19:07] <wxl> so there's nothing you can do to not keep it from crashing?
[19:07] <gil> it's only the first time I launch chrome after a cold boot
[19:07] <gil> wxl no, it always does so on the first launch. However, I select "ignore future errors" or whatever the option is, and so I don't see the crash box on launch
[19:08] <wxl> hm
[19:08] <gil> until google push an updated version out so I see a crash dialog again
[19:08] <wxl> oh
[19:08] <wxl> interesting
[19:08] <wxl> this sounds like a chrome problem
[19:08] <gil> so then I select "ignore future errors"
[19:08] <wxl> i use chrome myself and have had no such issue
[19:08] <gil> and around we go again :)
[19:08] <wxl> there's probably a directory you need to wipe
[19:08] <wxl> however, in general, i would suggest ALWAYS submitting crashes
[19:08] <gil> Yeah I figured that was more of a Chrome issue, because generally lubuntu has been really really stable for me
[19:08] <wxl> else it may keep harassing you, whether it be chrome, lubuntu, or whatever :)
[19:09] <gil> I think I tried to submit it but was told it wasn't officially supported or what not, so I kind of gave up :-\
[19:09] <wxl> hm weird
[19:12] <wxl> well
[19:12] <wxl> gil: what version of lubuntu-artwork do you have?
[19:14] <gil> I have two apparently: lubuntu-artwork 0.50 and lubuntu-artwork-15-04 0.50
[19:14] <gil> brb 5 mins
[19:14] <wxl> iiiiinteresting
[19:15] <wxl> loading a vm up
[19:16] <wxl> oh man this is old
[19:16] <wxl> 0.48
[19:16] <wxl> updating
[19:16] <ianorlin> wxl the copyright file fo lubuntu-artwork hasn't been updated in a while either
[19:17] <wxl> yeah i saw the bug ianorlin
[19:17] <wxl> do you have any experience with this problem?
[19:17] <ianorlin> don't use chrome
[19:22] <gil> wxl back if you need me
[19:24] <wxl> 1s gil
[19:24] <wxl> it's not about chrome ianorlin
[19:24] <wxl> redescribe the problem with the triangle thingy gil
[19:24] <gil> ianorlin the little triangle icon you click to expand things, such as "details" in software updater
[19:24] <gil> it's invisible
[19:24] <gil> everything else draws fine
[19:25] <gil> it's just that triangle "widget?"
[19:28] <ianorlin> gil did you change widget in lxappearance
[19:29] <ianorlin> I filed a bug for that here https://bugs.launchpad.net/ubuntu/+source/gtk2-engines/+bug/1406807 because it only effected ones that weren't part of lubuntu-artwork
[19:30] <gil> ianorlin I tried to change widget after I noticed the issue, but I've had the issue so far in both Lubuntu-default and Mist
[19:31] <ianorlin> I can reproduce in mist but not lubuntu-default
[19:32] <gil> Can you give me an example GUI that features the triangle widget so I can try? The only one I can think of is software updater and I need updates to be able to do that :)
[19:40] <wxl> gil: 1s
[19:42] <wxl> running software updater
[19:42] <gil> This is weird. I was going to force version a package so I could get the software updater to find an update and display the widget for me to test it
[19:42] <gil> but synaptic's force version menu item seems to be permanently greyed out
[19:44] <gil> ahhh nvm seems some updates are coming down the pipe
[19:45] <gil> yeah, widgets reappear in Lubuntu-default so that works for me :)
[19:46] <gil> I wonder why it wasn't set to Lubuntu-default when I upgraded from 14.10 initially though?
[19:46] <ianorlin> keeps files in home folder
[19:46] <gil> Does 14.10 use Clearlooks as default?
[19:46] <ianorlin> no
[19:46] <ianorlin> but you still have the config in home folder that tells it what theme to have
[19:47] <gil> ianorlin okay. Not to complicate things, but I don't think I *ever* changed the look and feel until I installed 15.04 and noticed the missing widgets
[19:47] <wxl> so problem solved?
[19:47] <gil> but if that's the only way it could not have been set to Lubuntu-default I suppose I must have :-\
[19:47] <gil> but yeah, problem solved, wxl - non default widgets are wonky :)
[19:47] <ianorlin> some widgets are broken but work around
[19:48] <ianorlin> well dark-panel still works
[19:48] <gil> Now bring on lxqt! :D
[19:55] <wxl> gil: you may want to file a bug against those widgets
[19:56] <wxl> gil: file it against lubuntu-artwork and we'll figure out where it should go to
[19:56] <gil> wxl it's already filed I think
[19:57] <gil> wxl https://bugs.launchpad.net/ubuntu/+source/gtk2-engines/+bug/1406807
[19:57] <gil> Not sure why I didn't see that when I searched for it earlier
[19:57] <wxl> great thanks
[19:57] <wxl> please confirm it
[19:57] <wxl> brb
[19:58] <gil> kk