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