[00:24] * sbeattie looks at https://bugs.launchpad.net/ubuntu/+source/gvfs and cries at all the private bugs. [00:30] jpds: /22 [00:30] argh [00:30] Pici: wut? [00:30] jpds: that was me mistyping [00:31] Oh, right. [00:50] bdmurray, rhetorical question [00:50] A linked bug mean someone has basically triaged it right? [00:52] well, someone has bothered to look further. I don't know if that really means Triaged === asac_ is now known as asac [00:52] e.g., cross-linking between distributions not involving an upstream bug report [00:53] yeah, I am just wondering if someone has made a link [00:53] but the bug stays New [00:53] is someone looking at it? [00:54] or is someone flailing "hey, debian fixed this 3 months ago!" or whatever [00:54] which bug? [00:54] I mean in general [00:54] maybe neither. If the Debian bug's status is something other than New, perhaps it has been triaged. [00:55] jcastro: sometimes the reporter will link upstream/to another distro [00:56] right [00:57] it may just to point out that some other distro has the same problem [00:59] jcastro: linked specifically to the upstream project, where it is then confirmed upstream, I would consider triaged [00:59] greg-g: +1 [00:59] * micahg also does that, +1 [00:59] ok I will start doing it from now on [01:00] jcastro: that's assuming there's enough info upstream [01:00] right [01:00] which usually there is [01:00] assuming there's enough for a maintainer to just pull in a patch or a sync or something [01:00] make sense? [01:00] well, yes, this is a point -- but it is a good start [01:01] jcastro: yes, it does [01:02] so like "This looks developed enough for you to just pull in, so low hanging fruit vs. sitting there all day trying to figure it out." [01:02] well, who's asking a maintainer or a triager? [01:04] I guess it depends on the person [01:04] if it's a triager, most certainly, if it's a maintainer, then if they have a quick 5 minute solution, I'd say go for it [01:04] but either way it's triaged [01:04] * jcastro nods === micahg1 is now known as micahg [04:02] I am curious about bug #491181. Do we troubleshooting Firefox plugins? [04:02] Launchpad bug 491181 in firefox-3.5 "firefox 3.5.5 icedtea bug java app" [Undecided,New] https://launchpad.net/bugs/491181 [04:03] (I'm new to triaging bugs.) [05:02] hey dogatemycomputer, sorry I haven't responded to your email yet, but I can help with this question [05:02] so, yeah, if the plugin is provided in the Ubuntu repositories, we try to find the cause and forward it upstream to the developers of the software [05:06] first of all, we should assign this to the icedtea plugin package, which, after searching https://edge.launchpad.net/ubuntu/ for a package with "icedtea" in the name gives me https://edge.launchpad.net/ubuntu/+source/icedtea-gcjwebplugin [05:07] so, you want to change the affected project to that, see if you can reproduce it, if you can, confirm it. Then, the really awesome thing would be to find the upstream for it and report the bug there. [05:07] awesomely, this reporter has a backtrace attached, making triage for a developer that much easier [05:08] dogatemycomputer: ^^ [05:08] dogatemycomputer: but now, as it is midnight, I'm headed to bed. I'll look at your email tomorrow. Again, sorry about that. === richie is now known as Richie [06:21] greg-g: thanks for the help! The bug does not include enough information to reproduce it. I copy/pasted the "Missing Steps to Recreate Bug" canned response. If he can tell me how to reproduce it then I will try and confirm it. [06:22] greg-g: I am not clear if you are implying I should confirm it simply because the backtrace is attached or if you are saying that will just make it easier for them to track it down? [06:31] dogatemycomputer: bug #? [06:33] micahg: I am curious about bug #491181. Do we troubleshooting Firefox plugins? [06:33] Launchpad bug 491181 in icedtea-gcjwebplugin "firefox 3.5.5 icedtea bug java app" [Undecided,Incomplete] https://launchpad.net/bugs/491181 [06:38] first, that's not the right package dogatemycomputer [06:38] the package is icedtea6-plugin [06:39] actually, it's openjdk-6 [06:54] hi, anyone around? [06:54] yoasif: sure :) [06:55] micahg, https://bugs.launchpad.net/ubuntu/+source/frozen-bubble/+bug/386104 this seems to be a packaging issue, it's live in karmic and it's an easy fix -- libsdl1.2debian-alsa should be removed from recommends and changed to libsdl1.2debian-pulseaudio [06:55] Launchpad bug 386104 in libsdl1.2 "[karmic] skipping audio when using libsdl1.2debian-alsa" [Undecided,Confirmed] [07:00] yoasif: let me take a look [07:00] micahg, awesome [07:03] dtchen: are you around? [07:08] yoasif: the problem is the package depends on a dummy package with 7 options, alsa being the first [07:08] yeah [07:08] alsa doesn't work properly... not sure if it's a problem with the package [07:08] or ubuntu's implementation of pulseaudio [07:08] idk [07:08] but the pulseaudio package fixes it [07:46] my cpu fan speed is not detected in karmic but it worked well in hardy [07:46] i get acpi resource conflict message during boot [07:49] can anyone help me with this [07:49] where in boot? [07:49] @ wat point? [07:50] before the splash screen comes up [07:51] but u can bypass it no prob right? [07:53] thats not a problem,the problem is i loaded the modules from the sensor-detect command and there is some conflict in assigning acpi resources [07:53] so my cpu fan speed is not shown by sensors command [07:54] but it was working well in hardy === YDdraigGoch is now known as Richie [08:08] michahg: I found icedtea-gcwebplugin . Are you saying that it should be openjdk-6 instead? [08:09] michahg: nevermind. looks like you already made the change. Thanks! [08:09] michahg: Is there someplace I could find this information or is this just one of those things you learn as you go? [08:13] dogatemycomputer: in the attached plugins file it had the version of the plugin, the one you selected has a version of 1.0, the openjdk-6 package is at 1.6.something [08:15] michahg: Thank you for catching that. I appreciate it. greg-g is my mentor. I'm sure he will see your comment so he also knows in the future. [08:15] dogatemycomputer: it's a simple mixup, I happen to be the main triager for Firefox at the moment, that's how I knew where to look [08:16] micahg: ahhh.. this is probably my 5th day of trying to triage bugs. :-) [08:17] micahg: for a translation bug.. I posted the canned response. Should I mark the bug invalid? [08:18] dogatemycomputer: canned response? what bug #? [08:18] micahg: bug #491248 [08:18] Launchpad bug 491248 in ubuntuone-client "russian translation of share dialog" [Undecided,Invalid] https://launchpad.net/bugs/491248 [08:18] dogatemycomputer: where does it say to do that? [08:18] micahg: The canned response found here: https://wiki.ubuntu.com/Bugs/Responses#About%20an%20incorrect%20translation [08:19] dogatemycomputer: ugh, I don't think that's right, I'll have to bring it up with someone in the morning [08:19] micahg: Thank you for taking the time to report this bug and helping to make Ubuntu better. However, Ubuntu gets its translations from the translations portion of Launchpad (http://translations.launchpad.net/ubuntu/), where translation teams work on making Ubuntu more useful in their language. If you want to change a translation in Ubuntu there is the right place. [08:19] dogatemycomputer: please don't do that :) [08:19] pastebin is more effective, but the link was fine [08:20] micahg: I already did. What should I do now? [08:20] dogatemycomputer: idk, I have to check if the policy's changed [08:20] I thought we just open an upstream bug task to ubuntu translations [08:20] and mark the package bug triaged until it's done [08:21] micahg: well.. I guess I will leave it alone for now unless some documentation appears that tells me what to do otherwise or someone changes it. I don't want to start guessing when i'm this new. [08:21] dogatemycomputer: yeah, don't worry about it, I'll check in the morning [08:23] micahg: If you want me to contact someone then just let me know. I don't mind pinging someone to find out if the wiki should be updated. [08:24] micahg: have a good night!! [08:24] night dogatemycomputer === seb128_ is now known as seb128 === seb128 is now known as seb128_ === seb128_ is now known as seb128 === yofel_ is now known as yofel === etaliverto is now known as etali [13:24] hi hi [14:42] Boo [14:45] bbuu! [15:31] pedro_: I think we can go ahead and create the mentorship group; I will update the wiki to refer to it [15:32] hggdh, cool, i was waiting for some feedback to create it , will do it [15:32] yes, we really need to organise this ;-) [15:33] so true :-) [15:33] so bugsquad-mentorship or ubuntu-bugsquad-mentorship ? [15:34] the bugsquad team is called "bugsquad" on lp [15:34] bugsquad-mentorship, I guess [15:37] done -> https://edge.launchpad.net/~bugsquad-mentorship [15:37] will add the mentors we have on the wiki to it now [15:45] hmm , is mentorship right , or is it -mentors? [15:47] mac_v_, it's mentorship since we are not going to have only mentors on that group [15:48] pedro_: ah , got it :) [15:48] students are going to be added there as well [15:51] pedro_: i unable to find the mentorship wiki , has it been written yet or...? [15:52] https://wiki.ubuntu.com/BugSquad/Mentors [15:52] mac_v_, ^ that one you mean? [15:53] pedro_: ah, yup , thanks , i was searching for "mentorship" :( [15:54] heh no problem :-) [15:57] mac_v_: just bear in mind we are changing the procedure on mentorship right now [15:58] * pedro_ -> lunch [16:01] hggdh: hmm , ok. Just one doubt :) ... what would be the difference between bugsquad and the beugsuqd-mentorship , if the members can be both mentors and mentees? do they have higher privileges on lp? [16:02] mac_v_: mentors will need to be bug-controllers (or very experienced bugsquadders), or maintainers [16:02] s/beugsuqd/bugsquad [16:03] hggdh: yeah , thats the mentor/mentee difference , but i meant difference between the two groups [16:03] graduation from the mentorship will land the mentee into bug-control (this is the idea) [16:03] ah , ok [16:04] bugsquad-mentorship is where you apply for mentorship, and where mentors look for mentees [16:04] bugsquad is going to be a closed group [16:04] what do you mean by "closed group"? [16:04] (i.e., you will have to apply, and be accepted) [16:05] does this mean that ORs won't be able to modify statuses on bug reports? [16:05] hggdh: then bugsquad/bugcontrol difference? and what will happen to existing bugsquad members? [16:06] current bugsquad members will receive an email stating their membership is expiring, and will have to reapply [16:06] we are pretty sure that most of the 1800 current members are not there anymore [16:07] why is bugsquad being closed? [16:07] heh [16:07] ok thats fair nuff [16:07] yup , the members are not active ;) [16:07] so is this more to get a better idea of the active membership? [16:07] but what will being approved look like? [16:07] because BS isnt supposed to have BC's reqs [16:08] maco, indeed [16:09] right now it will be the same [16:09] but we need to know how many bs's are actually there [16:10] so everybody reapplies and then is auto-approved? [16:10] or are you saying BS need to fill out form like BC now? [16:10] hggdh, regarding that email... I think we need to be careful not to turn off some of the more casual members [16:10] hggdh: that can be done by asking members just re-apply [16:10] hggdh: but couldnt the mentor/mentee be done within bugsquad team itself? [/me knows its too many questions , but didnt understand why a separate -mentorship team was needed] [16:11] if the members has done good in the BS , then they can go to BC ;) [16:11] member* [16:12] WeatherGod: this wil be the same as what happens now with bc [16:12] iirc BC is every 6months , which is quite good [16:13] hggdh, I understand, but usually people involved in BC are much more committed to this [16:13] hggdh, we could use this opportunity to renew interest in BS [16:14] even if we can get back a few members, that would be useful [16:16] WeatherGod: yes, the pre-reqs for bc are more stricter than bs. [16:17] there is also a chance that, upon receiving the renewal email, a (currently MIA) bs will come back [16:17] mac_v_: I do not think mentor/mentee would work within bs [16:17] that is what I am hoping... it will matter by how the email is worded [16:18] heh [16:18] yes. I would expect it will be very similar to what we have on bc [16:21] hggdh: hmm , most of the members listed as mentors on the wiki are also members of BC , it could have just been mentioned that these members are BC and are available for mentorship at these times , and the BS will have only mentees , who can graduate to BC... [but having both mentors and mentees in - mentorship didnt seem right] [16:22] anyways , you probably have a reason for the new team :) [16:22] and I'm just not understanding it ;) [16:23] mac_v_'s explanation makes sense to me [16:23] mac_v_: the bs-mentorship list carries all mentors (permanently); mentees have to apply (the group is closed), and remain members only while being mentored [16:24] this is easier than to manually list all mentors in the Wiki (we can just link to LP) [16:24] and the current process (fully manual) was not working [16:25] so, at any instant, we can find who is a mentee [16:25] hehe , easier to pull up by the ear ;p [16:25] also, wouldn't this allow some people to remain members of BS instead of being forced to graduate to BC? [16:26] yes [16:26] BRB, gotta drive my wife to the airport [16:26] ok, that makes sense [16:26] ok [16:28] a parting thought: I would like to continue this discussion when I get back [16:28] np === mac_v_ is now known as mac_v === yoasif__ is now known as yoasif_ === yoasif_ is now known as yoasif [18:22] k, I am back [18:25] hiya [18:26] any new comments or questions on the mentorship? [18:27] actually, I got sidetracked going over old bugs from a few weeks ago [18:28] I think we are largely in agreement, it probably just needs a little bit of polish to make sure everything is clear and well-organized [18:29] it does. What has happened is we started it with some ideas, and found that it got complex to manage [18:30] so we are adjusting as we go [18:30] it definitely would be good to streamline and automate the mentoring process [18:31] it just seemed a bit haphazard when I jumped in [18:31] this is the idea. You got in early -- and helped show the shortcomings ;-) [18:32] one thing that would be nice is that one could see potential mentors and see what areas of expertise [18:32] oh, this mentor this is relatively new? [18:32] s/this/thing/ [18:33] yes, it is. We did have it, but it was completely unstructured (some of us did mentor before, but not formally) [18:33] ah [18:33] I guess the mentor's areas of interest is one thing that should still be kept in the wiki page [18:34] yeah, but one could see the project areas that a person is involved in through their launchpad page === Afwas_ is now known as Afwas [18:36] we probably also want to make clear what sort of goals need to be achieved to be considered "graduated", maybe? [18:38] the GettingInvolved page still says to email ubuntu-bugcontrol maillist to request a mentor, is that still the case? [18:40] someone here speak French? [18:40] I need this statement made into good French [18:40] which restricted drivers did you end up installing [18:41] WeatherGod: Try ##french [18:41] ok [18:42] WeatherGod: another channel might be #ubuntu-fr [18:43] WeatherGod: I will adjust the wiki to state one has to request admission to the bs-mentorship group [18:44] hggdh: that might be better place to go... [18:45] what does it mean when an IRC group has double '#'? [18:45] etali: wow you were fast ;-) [18:48] WeatherGod: ##channels are topical or unoffical channels. See http://freenode.net/policy.shtml#channelnaming and #freenode for more information [18:52] Pici: thanks [18:53] hggdh: the #ubuntu-fr was very helpful [18:53] hggdh: dogatemycomputer pointed this out to me last night: https://wiki.ubuntu.com/Bugs/Responses#About%20an%20incorrect%20translation [18:53] •hggdh• - hehe, was following the discussion, figured I'd apply while I still had the URL handy :) [18:53] hggdh: doesn't seem right [18:55] micahg: this is sort of weird indeed [18:56] hggdh: I thought we open an upstream task to Ubuntu Translations... [18:56] hggdh: should I add it to the meeting agenda? [18:56] hggdh: I think we need a 2 hr meeting next week :) [18:56] I think you should -- it is a bug, after all [18:56] micahg: hggdh: also, the wording of that canned response is poor [18:57] pedro_: ^^^ any comments? [18:57] "If you want to change a translation in Ubuntu there is the right place"? [18:57] heh [18:58] Probably should be "fix" or "correct" a translation [18:58] and "that" instead of "there" [18:59] with a comma after Ubuntu [18:59] indeed. [18:59] But I wonder if we should also clear it up [18:59] WeatherGod: anyway, these errors justify the corrections you proposed. Care to get it done? ;-) [19:00] (and please add a comment about what you changed) [19:00] hggdh: sure, I'll clear it up [19:01] thank you [19:01] s/clear/clean/ [19:01] np [19:01] dogatemycomputer: did everything make sense last night? I see micahg helped out finding the right package (thanks micahg!). [19:01] hggdh, that sounds weird indeed [19:01] no, I meant better state what should be done [19:01] after making that change could you folks ping dpm to comment on that as well? [19:02] he's coordinating the translations on Ubuntu so he might have a better stock response for that [19:02] btw tomorrow is the translations bug day so perfect time to raise that with him :-) [19:02] cool. pedro_, is there a channel for the translators? [19:04] #ubuntu-translators IIRC [19:04] yes, that's the channel [19:04] thank you [19:05] np [19:06] k, put the question to them, waiting on feedback [19:06] ok, why doesn't Ubuntu's wiki system have "edit" links for sections... like wikipedia has? [19:07] it makes it so difficult to find the text you want to edit on a large page like that [19:07] yes. One way is to use an external editor [19:07] oh? [19:08] but now I have to remember the command, long time I do not use it [19:12] WeatherGod: editmoin [19:13] ok, I will look into it [19:14] thanks [19:32] WeatherGod: https://help.ubuntu.com/community/ReportingBugs#Filing%20translation%20bugs [19:34] I'd give my right arm if Canonical decided to only support a small number of hardware.. [19:34] * kklimonda is dying from answering questions about why some weird/obscure hardware doesn't work well/at all.. [19:34] welcome to PC hell [19:35] it is certainly better than it was a few years ago (at least, so it seems) [19:36] hggdh, it looks fine to me [19:36] I would probably do without the "if a" [19:37] otherwise, looks informative [19:37] sorry about being in such a grammar mode.... I am in the middle of revising journal articles for submission [19:38] :-) I have done revisions also [19:39] isn't bug triaging a nice distraction from writing? [19:39] :-P [19:39] WeatherGod: either you or I can update the stock response linking to the topic above [19:40] ah, update it to point to the correct url? [19:41] oh, wait, no, I see [19:41] well, this is the stock response... what do we want to say? [19:42] I am assuming this would be the response to use when switching the report over to the ubuntu-translations project? [19:44] so, just setting it to a new url isn't right [19:44] I think it would go like: thank you, etc, etc. Translations bugs should be assigned to the [[ https://bugs.launchpad.net/ubuntu-translations|Ubuntu Translations project ]]; as such, we adjusted the package to it [19:44] so something in this area [19:45] s/so/or/ [19:45] adiroiban on #ubuntu-translators told me the process there is in flux right now [19:47] "Thank you for taking the time to report this bug and helping to make Ubuntu better. Translations in Ubuntu are handled by the Ubuntu Translations project, so we are going to push this bug report over to that project" [19:47] heh, still needs something better [19:48] maybe "... so that the correction can be made"? [19:48] not bad at all [19:48] or be addressed [19:48] just make the Ubuntu Translations project a link [19:48] of course [19:48] how about "move" instead of "push" [19:48] good idea [19:48] no "so that corrections can be made" sounds rather stiffy [19:48] probably translate better, too [19:49] and move instead of push, indeed [19:49] ok [19:50] for the link, can I just do [[ubuntu-translations]]? [19:50] WeatherGod: thank you very much (and thank you, micahg1, for raising this up) [19:50] WeatherGod: try it, and see if it resolves [19:50] kklimonda: heh [19:51] hggdh: a big lag? ;) [19:51] :-D [19:51] doing some ten different things at the same time... [20:00] ok, done [20:04] WeatherGod: perfect! Thank you (again) [20:05] np [20:05] maybe I should get back to doing the work I am actually paid to do [20:05] :-P [20:07] well, I firmly believe I need money. The hell is that this is fun [20:08] heh [20:15] how should bug 464087 get marked [20:15] Launchpad bug 464087 in update-manager "Upgrade to Kubuntu 9.10 failed because site became unavailable" [Undecided,New] https://launchpad.net/bugs/464087 [20:15] it could be construed as a wishlist for better load-balancing of the servers before the next release [20:19] hum. Not as much load-balancing, as graceful recovery from TCP errors [20:19] whatever the case... I am not a network engineer [20:20] it is something that we need to be better prepared for the LTS [20:20] I think many of the bugs we encountered were from faulty upgrades [20:20] well, at least some of them [20:23] I agree, in part: u-m should be able to either recover or fail in a nice way [20:24] heh. It seems my sound got, er, lost [20:24] we should also test all packages with piuparts - there were some problematic updates in 9.04->9.10 [20:25] agreed [20:25] hggdh: lost? [20:25] like no longer here [20:26] ok, let me pull out my debug sheet here... [20:26] is your computer on? [20:26] :-P [20:26] :-) [20:27] have you tried to turn it off and on again? ;) [20:27] no, no... you got to unplug it and reverse the cords [20:27] ah, polarity issues [20:28] yeah... and be sure to just completely uninstall pulseaudio... because some guy in a Fedora forum said that would work [20:36] hggdh, how should that bug report get marked? [20:38] argh, people who uninstall pulseaudio "just in case" should be burned... [20:39] heh [20:39] WeatherGod: search for previous bugs on u-m with requests for nicier erroring out [20:40] ok [20:40] if none, then re-title this one to something like "update-manger should gracefully error out or recover from Internet failures" [20:40] and we will mark it triaged/wishlist [20:41] gotcha [21:04] hi [21:05] I'm having problems with the follwing page giving me timeout since yesterday evening (it's evening now again in my timezone ;) ) [21:05] https://bugs.launchpad.net/ubuntu/+filebug [21:07] elMariachi: that link works great here... actually much faster than usual. Having said that, do you know what package/application you are trying to report a bug against? It would be great if you could issue a "ubuntu-bug " command in a terminal/shell window. That collects info and automatically sorts it into the correct bucket. The main ubuntu bug bucket is overflowing. [21:08] mrand: no i cant say which package it is [21:08] elMariachi, I talked to you yesterday, right [21:08] right [21:08] what was your bug, again? [21:09] the freeze thingy [21:09] but with different hardware [21:09] at boot, right? [21:09] right [21:09] no, at login to normal gnome session [21:09] failsafe works fine [21:09] it seeeeems to be connected to the usage of compiz [21:09] mrand, I have no clue exactly what is at fault [21:10] but I am working on untangling a messy bug report [21:10] mrand: I'm getting this error message: Error ID: OOPS-1432G2939 [21:10] https://lp-oops.canonical.com/oops.py/?oopsid=1432G2939 [21:10] I am having them all subscribe me to it, so don't worry about the overflowing Ubuntu bin right now [21:10] gotcha [21:13] elMariachi: can you browse any of launchpad? [21:13] yes [21:13] mrand, odd bug, isn't it? [21:14] actually the timeout happens, when i hit the continue button [21:14] the page itself loads [21:14] sorry, forgot to say that :/ [21:15] Ok, so it's the next page that has all the fancy "could it be this bug" list that is failing. [21:16] if that is the next page ;) [21:16] You could maybe try bugs.edge.launchpad.net. I don't hold out high hope though, cause it has the same thing. [21:17] there is this message box saying, that i can disable redirection for two ours [21:17] that doesn't change anything.. [21:17] hours [21:18] WeatherGod: what do you think about just having elMariachi try to submit it using "ubuntu-bug gnome-session" and then move it as needed? Oh wait, unfortunately I think that still takes you to that screen on the browser, so it'll likely not work either. [21:18] too bad the cli version of ubuntu-bug isn't released (that I'm aware of) [21:18] I thought it was [21:18] (I don't know, I am using Fedora right now) [21:20] we can file the bug against anything we want, I just want to see it filed [21:20] just a crazy thought.... [21:20] could there be issues with Firewalls or Proxies? [21:21] sorry, gotta go to bed.. i'm gonna try to file it against compiz tomorrow [21:21] That's what I'm thinking, but that's out of my area of comfortable knowledge. [21:21] sorry for your troubles [21:21] same here [21:21] naaa, dont worry [21:21] im using the os that we all dislike in the meantime [21:21] WeatherGod: there is apport-cli -p , but that only works if there is a crash report pending [21:22] ah, that might be what I am thinking [21:27] apport-cli -f -p packagename then K for keep [21:27] then you can copy the bug report to another system and file it from there [21:27] WeatherGod: ^ [21:27] hmmm, good to know... I got another guy who is having network issues [21:28] still, I wonder if the guy in question can access the webpage from anywhere else [21:28] guess we will find out tomorrow [21:31] hggdh, with regards to the u-m bug report [21:31] I am finding some other reports that also stated possible overloaded servers, but are very light on details [21:31] is it ok for now to create a "chain" of dupes? [21:55] WeatherGod: yes, it is [21:56] ok, I will chain up some of the ones I found to the "meaner" one in the hopes of finding another report to use as the master [21:57] k === dreimark_ is now known as dreimark === seb128_ is now known as seb128 [22:50] !info sreadahead [22:50] ubot4: hi [22:50] Hi! Welcome to #ubuntu-bugs! Feel free to ask questions and help people out. The channel guidelines are at http://wiki.ubuntu.com/IrcGuidelines. Enjoy your stay! [22:50]