[00:30] whew..... thats hectic [00:30] stumping for ubuntu :) === santiago-php is now known as santiago-ve [04:32] HELLO [04:32] HOW CAN I join developing and helping the community [04:33] wwwwwwwwwwwaaaaaaaaaaa [04:39] harris: the Kubuntu community? The basic template for Ubuntu development is a good start. [04:41] I already joined the KUBUNTU TESTER [04:42] is that okay? KUBUNTU is my first FOSS O.S. === KhaoticMind is now known as KhaoticMindMr === KhaoticMindMr is now known as KhaoticMind === santiago-php is now known as santiago-ve [13:21] https://bugs.edge.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/222819 <- kdesu problem? [13:21] Launchpad bug 222819 in kubuntu-meta "cdromupgrade: command not found" [Undecided,New] [14:29] Nightrose: unlikely, needs testing though === d_miller is now known as d-miller === hunger_t is now known as hunger === txwikinger is now known as txbot === txbot is now known as txwikinger === txwikinger is now known as txbot === txbot is now known as txwikinger [20:45] wolfger: you should check who is debating there and who should be, but is not [21:08] hi there === neversfelde_ is now known as neversfelde [21:09] is that console color bug fixed ? [21:14] Sevenhill: is it marked as fix released? [21:15] apachelogger: I have typed a little patch for .bashrc [21:15] on the other hand i couldn't find a description on bugzilla [21:15] so i'm creating a bugreport now [21:15] and i will add my patch to ther [21:15] e [21:17] apachelogger: could you please check #223256 [21:18] bug #223256 [21:18] Launchpad bug 223256 in console-tools "console color is not set correctly by .bashrc" [Undecided,New] https://launchpad.net/bugs/223256 [21:23] Sevenhill: what exactly is the problem? [21:23] apachelogger: the .bashrc script's comments say the if you uncomment force_color_prompt=yes statement [21:23] it makes console colorful prompt [21:24] whether if your console support or not [21:24] on the other hand the if statement is coded wrongly [21:25] it never makes the color_prompt variable yes if you select force_color_prompt=yes [21:25] with this patch it is making that statment : http://launchpadlibrarian.net/13970587/color.patch [21:31] Sevenhill: I really don't see the problem [21:32] if force_color is set it runs an if query to increase the probability the terminal really supports colors [21:32] if so it sets color_promot to yes [21:32] otherwise it does nothing [21:32] with the patch it sets it anyway :) [21:32] but if is coded wrong on .bashrc [21:33] why? [21:33] fdoving: try it with typing not uncommenting the force_color_prompt=yes statment [21:33] your patch would enable color support even if the terminal wouldn't probably support it [21:33] Sevenhill: you mean leave force_color uncommented? [21:33] yes [21:34] it is supposed to not work then [21:34] that's what the first level if query is for [21:34] but [21:34] if [ -n "$force_color_prompt" ]; then [21:34] isn't it if $force_color_prompt is not setted ? [21:35] Sevenhill: no, if it's nonzero [21:35] ok [21:35] how can i explain it [21:35] so with your patch one could just remove the two ifs, and set color_prompt=$force_colored_prompt [21:36] no [21:36] Oo [21:36] yes [21:36] it makes it color_promt=$force_colored_prompt if $force_colored_prompt is setted [21:36] Sevenhill: which is wrong [21:37] we only want color_promt to be yes when if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then is true [21:37] if user set the force_color_prompt yes [21:37] it must not to check wheter support or not [21:37] users are often wrong. [21:38] so the force_color_prompt is no-function in there [21:38] -.- [21:38] it is, but it doesn't -really-force. [21:38] you have to set force_color in order to get colro support [21:38] *color even [21:38] it checks for setaf support, which is needed to make colors. [21:39] if it means that it must have some other name [21:39] force means force [21:39] # uncomment for a colored prompt, if the terminal has the capability; turned [21:39] # off by default to not distract the user: the focus in a terminal window [21:39] # should be on the output of commands, not on the prompt [21:39] maybe reading descriptions is as good as renaming the variable [21:40] Sevenhill: please change the variable name to something more meaningful and upload the patch [21:40] otherwise please close the report as invalid [21:40] hmm [21:41] maybe we make the force_color_prompt as normal ( i mean like my code) but make the system default checks wheter system support or not color [21:43] the variable should probably be named 'enable_color_prompt' or somehting like that. [21:45] :D yes exactly what i want :D [21:45] and also one variable that makes it for force to make it colorful [21:46] Sevenhill: what terminal app are you using? [21:47] konsole [21:47] (kde's terminal) [21:47] Oo [21:47] Sevenhill: what does `tput setaf 1` do? [21:47] usta@usta-desktop:~$ tput setaf 1 [21:47] usta@usta-desktop:~$ [21:48] so [21:48] why does if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then [21:48] fail for you? [21:48] it should change colors. [21:48] i have no idea [21:48] to red [21:48] Sevenhill: echo $_ [21:48] in the same shell [21:49] usta@usta-desktop:~$ tput setaf 1 [21:49] usta@usta-desktop:~$ echo $_ [21:49] 1 [21:49] should work. [21:49] Sevenhill: please add debug output to your .bashrc [21:50] how ? [21:50] Sevenhill: http://paste.ubuntu.com/8426/ [21:50] something like this [21:50] then source .bashrc [21:50] 2 sec plz [21:51] first cp /etc/skel/.bash ~usta [21:51] then i will change like that [21:51] (i mean .bashrc ) [21:55] 2 sec [21:59] offf [22:00] there is a problem about that if [22:00] http://paste.ubuntu.com/8429/ [22:00] fdoving and apachelogger : http://paste.ubuntu.com/8429/ [22:00] Sevenhill: you have to enable force_colored_prompt=yes [22:01] apachelogger: i made it [22:01] ah [22:01] sorry [22:01] Sevenhill: there is typo Oo [22:01] force_colored [22:01] vs [22:01] force_color [22:01] I guess that can't work :P [22:01] :D [22:02] so i have found a bug :D [22:02] after all [22:02] Sevenhill: change the variable to enable_color_promt and upload the patch please [22:02] but [22:03] om [22:03] ok [22:03] ! :D [22:03] Sorry, I don't know anything about d - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi [22:03] !! [22:03] ubotu: why won't you react to that? :P [22:03] nice work, i didn't see that typo :) === TheImp is now known as TheInfinity [22:06] Oo [22:06] omg [22:06] plasma looks cool today [22:07] current? [22:07] http://aplg.kollide.net/images/osiris/snapshot101.png [22:08] fdoving: just finished compiling [22:08] me too. [22:08] Nightrose: I haz a better plasma than ye :P [22:08] apachelogger: woahhhh awesome :P [22:08] I likez [22:08] i just cleared the config and restarted plasma. [22:08] the panel looks weird. [22:09] I didn't see a panel in days [22:09] and I don't know why :( [22:10] try to clear your plasma config. [22:10] fdoving: didn't help [22:10] clean rebuild? [22:10] http://frode.kde.no/misc/plasma-1.png [22:11] yeah, should try that some day [22:11] fdoving: doesn't look that much better ;-) [22:11] it was fine just 2 hours ago, and silly me updated :) [22:12] systray haven't worked for weeks though. [22:12] yeah [22:12] kind of annoying. [22:12] only thing that annoys me really about the plasma b0rkage [22:13] fdoving and apachelogger : could you please recheck it ? : http://launchpadlibrarian.net/13971784/color_new.patch [22:14] good thing it's not as slow as installing sp1 on vista. i dont know how many 100% statuses i've seen. once when downloading, then when installing, then when shutting down, then when starting up again. [22:14] bug #223256 [22:14] Launchpad bug 223256 in console-tools "console color is not set correctly by .bashrc" [Undecided,New] https://launchpad.net/bugs/223256 [22:14] Sevenhill: I would make it color_prompt not colored [22:14] since the variable it invokes is also called color_prompt and not colored_prompt [22:15] but that's just a nice-looking bonus feature ;-) [22:15] looks good otherwise [22:15] :D could you please commit that patch for me ? [22:16] and make that bug as accepted :D [22:16] who did set console-tools as effected? [22:16] maybe i ( wrongly ) [22:17] not sure [22:17] [ i need to improve my english :) ] [22:22] apachelogger: so did you commit it ? or who will commit it ? [22:42] Sevenhill: a main developer will as soon as he stumbles upon the bug, which might not be that soon because intrepid development didn't open yet [22:43] but will it commit or not ? [22:43] Sevenhill: yes [22:43] status triaged means that the bug is ready to be reviewed by a responsible developer [22:44] apachelogger: thx [22:47] Sevenhill: why did you make the bug affecting Ubuntu? [22:48] apachelogger: i didn't do anything [22:48] Filed here by: Omer F. USTA [22:48] When: 39 minutes ago [22:49] i only choose console-tools ( at first) and type my bug entry [22:49] nothing else [22:50] then when we realize that it is about typo bug i renamed bug [22:50] and i upload new patch [22:50] yeah, screw it [22:51] * apachelogger goes to bed, if it distrubes someone who is going threw the ubuntu bugs he probably will do something ;-) [22:51] * Nightrose hugs apachelogger [22:51] nini [22:51] night [22:51] i found also a bug in vim in kubuntu [22:52] the bash syntax highlighting is not working correctly [22:52] Sevenhill: I rather would think it is a bug in upstream vim than in ubuntu [22:53] apachelogger: they say that if you got patch talk otherwise shutup === Jucato_ is now known as Jucato [23:14] Sevenhill: bug #? [23:15] mornin [23:15] afternoon actually timze zone change ;) [23:16] ryanakca: for about vim ? === _Czessi is now known as Czessi [23:23] wow denver airport's internet is slow [23:24] but they have an awesome amouont of power plugs [23:24] Sevenhill: yes [23:24] jjesse: lol :) [23:24] ryanakca: try tracking down a power outlet in o'hare aiprot [23:24] ryanakca: i haven't entered a bug report after i get that answer [23:24] power is needed after watching movies for two hours :) [23:25] ryanakca: if you want to look for bug just open a new file and paste the content of this page's script : [23:25] http://techbase.kde.org/index.php?title=Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc [23:25] then open it with in vim ( :syntax on ) [23:26] you will see the problem after prepend function in page [23:27] jjesse: lol :) [23:28] Sevenhill: file it in Ubuntu, file it upstream, link upstream's to the Ubuntu one in Launchpad, submit a patch, forward it upstream, etc :) [23:28] ryanakca: seriously.... spend 2.5 hours in a plane and then you will be crying for power [23:29] ryanakca: i'm not good at regex for writing a newer version of syntax file :) [23:29] jjesse: i couldn't find any outlets in O'hare. and i though Logan was pretty bad on the way there [23:29] *thought [23:30] yuriy: the only outlets i can ever find in o'hare are always full [23:30] there are none in the actual gate areas for some stupid reason [23:30] Sevenhill: ok, well, do steps 1-3 [23:31] Hopefully someone will be brave enough to make / submit a patch [23:31] also i had hoped to actually do somthing useful while i was sitting at the airport.. but $8 for an hour of internet just seemed a bit much [23:31] Also, I'd attach the problem file to the bug report. [23:31] i'm in airports enough that i pay 21.95 for the month from boingo wireless [23:31] ouch... 8$? [23:31] jjesse: you or your company? [23:31] $8 is cheap [23:31] ryanakca: my company [23:32] expense report it :) [23:32] ah, ok, I was going to say :) [23:32] no way i was going to pay it mysself [23:32] i'm too cheap of a bastard [23:32] ryanakca: it's for a day, but unless you're unlucky you'll never be using it for more than an hour [23:32] wasn't logan's more then that [23:32] nope [23:32] washington dc was 19.95/day [23:32] eek [23:33] this john adams mini series on hbo is awesome [23:47] hrmm should i take the bump on the oversold flight and hang out in the airport for 3 more hours [23:49] jjesse: how long is the flight? [23:50] flight is an hour [23:50] I'd take the bump... but that's just me :) [23:50] yeah but i wouldn't get in until 11pm [23:50] and then i would have an hour drive after that [23:50] until my home room [23:51] oh, sorry, I thought it was on 'or'... it's an 'and' :) [23:51] like all airlines they oversell flights [23:51] so the next flight would be in 3 hours to my destination [23:52] i would fly for an hour, then have an hour to drive to the hotel [23:52] which owuld make it a really really late night [23:52] ya'll know how you can send text messages to your phone from email? [23:53] (or any phone) [23:53] telephonenumber@serviceprovider.com [23:53] so i can send telephonenumber@vztext.com [23:53] bah <_< .... thought I found out something new :) [23:53] from email and it will show up as a a text message