[00:00] <yofel> BarkingFish: commit message was: fix use-after-free bug in my patch
[00:00] <Kurdistan> yofel, thats great. :)
[00:00] <BarkingFish> hm. I hadn't spotted anything wrong, seriously. Guess I need to brush up a bit.
[00:00] <yofel> I've looked at it, but it's not easy to read a diff of a diff
[00:01] <BarkingFish> 0.o
[00:01] <BarkingFish> I'll take your word for it :)
[00:02] <Kurdistan> :) why when apply a patch/diff some time output is garbage? 
[00:03] <BarkingFish> I have no idea. However, I do know it's just gone midnight here, so I'm gonna go finish knitting my scarf and go to bed.  See you guys tomorrow, sorry for the short stay but I'm tired.
[00:04] <BarkingFish> bbfn guys
[01:09] <Kurdistan> any one awake?
[01:09] <Kurdistan> some one with packing skills. 
[01:11] <yofel> me
[01:12] <yofel> not for long thoug
[01:12] <yofel> h
[01:14] <Kurdistan> yofel, I can make package, but how if the thing I wanted to build does not have debian folder
[01:14] <Kurdistan> with all neccesery stuff
[01:15] <yofel> running 'dh_make' will make an intial folder with the files in it, but you'll still need to know how to make it work in the end
[01:16] <Kurdistan> yofel, thats the thing.
[01:16] <Kurdistan> because normally when I take from source
[01:17] <Kurdistan> I have already debian folder and I know how to modify to get it work
[01:17] <Kurdistan> dh_make will it give empty rules
[01:17] <Kurdistan> changelog
[01:17] <Kurdistan> compat
[01:17] <yofel> hm, yeah, initial packaging can be tricky, see the ubuntu packaging guide or the debian new maintainers guide on how to make a package
[01:17] <Kurdistan> etc?
[01:18] <yofel> or ping me tomorrow, I'm too tired now
[01:18] <Kurdistan> yofel, :) I will bing you tomorrow. have nice sleep.
[01:18] <yofel> dh_make will add the files not totally empty, but still not in a state that works out of the box I think
[01:18] <yofel> + it adds a lot of files that you won't need
[01:19] <Kurdistan> yofel, okey :) I will chatt with you about this tomorrow.
[01:19] <Kurdistan> thx again for your time yofel 
[01:19] <yofel> sure
[01:19] <Kurdistan> if I learn this I can help kubuntu much more
[01:19] <Kurdistan> basic packing I know
[01:20] <Kurdistan> kernel compile to
[01:26]  * Kurdistan is going to sleep. bed time. have nice evening/day channel.
[09:13] <grmls> hi
[09:16] <Riddell> hi grmls 
[09:17] <grmls> hi riddell
[09:21] <grmls> i have an question. yesterday i found a bug by installing kubuntu oem dvd amd64. this bug recorded in launchpad but why is this bug not recorded in http://iso.qa.ubuntu.com/qatracker/milestones/206/builds/11115/testcases/81/results. whats my mistake? (sry for my bad english)
[09:25] <Riddell> grmls: we did not test oem for alpha 2
[09:25] <Riddell> lack of time/volunteers.  so if there's a bug that's very useful for you to have found
[09:25] <Riddell> what's the number?
[09:26] <grmls> #930741
[09:27] <Riddell> bug 930741
[09:28] <Riddell> yeah I didn't even test keyboard changes
[09:29] <Riddell> milestoned for beta so we don't forget it
[09:30] <grmls> oh im new. i dont need test oem in alpha 2? so i try better a other iso 
[09:35] <Riddell> grmls: we should have tested it yes, and if we'd had enough testers we would have
[09:35] <Riddell> so it's very good you testing it now and finding bugs
[09:39] <grmls> is there an iso with high preference?
[09:43] <Riddell> grmls: ?  whatever can do and isn't already much tested is what we want from iso testing
[09:49] <grmls> okay
[11:01] <yofel> morning
[11:01] <rbelem> morning
[11:06] <grmls> hi yofel
[11:10] <debfx> ScottK: what's the workaround for the bug you posted on kubuntu-devel?
[11:15] <debfx> yay I can logout again
[11:16] <debfx> thanks yofel for sharing that workaround :)
[11:16] <yofel> sure :)
[11:17] <debfx> we definitely need to enable that
[11:18] <yofel> as apachelogger said, enabling that shortly before final freeze is probably best
[11:18] <yofel> although I would turn it off again once Q opens up
[11:42] <debfx> it has been broken for a few releases so imho there is no point in waiting
[11:43] <yofel> well, I added myself a TODO item for this so I don't forget about it
[12:19] <Kurdistan> hi channel
[13:31] <BluesKaj> 'morning all
[13:31] <Kurdistan> BluesKaj, morning.
[13:31] <BluesKaj> hi Kurdistan
[13:31] <Kurdistan> nm widget buttons looks good now
[13:32] <Kurdistan> :) backport updates yesterday fixed it.
[13:33] <BluesKaj> ok, no NM in my system , so I din't know the widget was broken 
[13:33] <Kurdistan> BluesKaj, what are you using?
[13:33] <Kurdistan> kde network manager?
[13:34] <yofel> he's not even using network manager
[13:34] <BluesKaj>  no, /etc/network/interfaces file and /etc/resolv.conf 
[13:34] <yofel> me neither on my desktop
[13:34] <Kurdistan> BluesKaj, server?
[13:35] <BluesKaj> Kurdistan,  there's no need for NM on an ethernet connection , well mostly 
[13:35] <Kurdistan> BluesKaj, I see.
[13:35] <Kurdistan> I am using laptop :).
[13:38] <BluesKaj> ok , if you have any desktop ethernet nics then this example is one of the tutorials I used,  http://www.cyberciti.biz/faq/setting-up-an-network-interfaces-file/
[13:40] <apachelogger> debfx, yofel: turning it on now will potentially prevent more annoying bug reports to the broken products
[13:47] <BluesKaj> yofel,  I see /etc/resolv.conf is now overwritten by /etc/resolvconf/resolv.conf.d/head ... why the change? , altho i found a workaround by adding my dns settings to the "head" file which in turn transfers them to /etc/resolv.conf 
[13:47] <debfx> the potential of it being fixed is very minimal however
[13:48] <Kurdistan> BluesKaj, I like the widget.
[13:48] <yofel> BluesKaj: from what I read about it, ubuntu is trying to unity resolv.conf editing and now uses resolvconf by default
[13:48] <yofel> that's all I know
[13:48] <yofel> s/unity/unify
[13:48] <BluesKaj> Kurdistan,  well, to each his own :) 
[13:51] <BluesKaj> yofel,  it does prevent ppl from screwing up their resolv.conf thereby losing their internet connection , it makes some sense alright
[13:56] <Kurdistan> why is kmail always buggy when I try?
[13:57] <Kurdistan> I feel kubuntu could change out some qt stuff for like thunderbird
[13:57] <Kurdistan> and firefox instead of rekonq
[13:59] <yofel> no, we discussed that often enough. For 12.04 we're not switching anything.
[14:05] <Kurdistan> yofel, okey. still kmail have always been buggy.
[14:05] <Kurdistan> kmail if it was not buggy it is really good.
[14:05] <yofel> no, it has been buggy since it started using akonadi to be precise
[14:06] <yofel> kmail1 was great
[14:06] <Kurdistan> yofel, I started with kde in real with kde 4.6.5
[14:06] <Kurdistan> so I am not so :) well known how it was before
[14:06] <yofel> doing LTS upgrade testing with kdepim is going to be so not funny...
[14:08] <Kurdistan> yofel, :).
[14:21]  * BluesKaj avoids kmail/kontact and disables akonadi ..have no need for it since my ISP contracted my email service out to hotmail anyway so I just use webmils like bell mail and gmail
[14:22] <BluesKaj> krusader does for me what nepomuk does for ohers , but it's not as invasiv
[14:23] <BluesKaj> invasive
[14:31] <apachelogger> debfx: the more annoyance the higher the likelyhood gets :)
[14:43] <BluesKaj> for those of you whao are having GPG key errors , here's a neat little app/ppa that will help get the missing keys a rid you of the error messages ..it's probly been posted befoe but I think it needs reposting , http://www.webupd8.org/2010/05/automatically-import-all-missing.html 
[14:46] <ScottK> debfx: Sorry.  I thought it was in the bug.
[14:49] <ScottK> debfx: Added to the bug: https://bugs.launchpad.net/ubuntu-release-notes/+bug/641712/comments/24
[14:55] <debfx> those options look a bit more scary
[14:55] <apachelogger> yofel: kmail works fine here
[14:56] <yofel> apachelogger: not for me
[14:56] <yofel> ScottK: I'll look at them and talk to ossi later
[14:56] <yofel> debfx: or do you want to?
[14:57] <apachelogger> did someone upload kde-hud btw?
[14:57] <ScottK> yofel: Thanks.
[14:58] <yofel> apachelogger: I made some test package that I never tried, no idea if someone else did something
[14:58] <apachelogger> awesome
[14:58] <ScottK> debfx: I've been using them since at least maverick with no issue.  Unless someone has an alternative solution, I think it's likely a better default because the password change thing is a rather common problem to have.
[14:59] <ScottK> But I'm not sure, which is why I'm glad yofel is going to talk to ossi.
[15:01] <apachelogger> ScottK: it can lead to weird issues when external windows/widgets come into play
[15:01] <apachelogger> e.g. different auth plugins
[15:02] <apachelogger> or onscreen kbds
[15:02] <ScottK> How common is that compared to just wanting to set a password for a new user.
[15:02] <ScottK> I agree it's not ideal.
[15:02] <apachelogger> which is why  want a qml greeter
[15:02] <apachelogger> so the entire we-have-to-manage-windows-but-have-no-window-manager situation can be avoided
[15:06] <BluesKaj> apachelogger, so hud is available 
[15:06] <apachelogger> eh?
[15:07] <BluesKaj> apachelogger,  I thought it was only available in gnome/unity
[15:07] <apachelogger> there is a prototype using krunner
[15:07] <BluesKaj> hud that is
[15:09] <BluesKaj> ok
[15:10] <debfx> yofel: won't complain if you do it :)
[15:10] <yofel> I'll do it then ^^
[16:05] <apachelogger> eh
[16:05] <apachelogger> debfx: whatever happend to synl10n in pkg-kde-tools?
[16:07] <apachelogger> Darkwing: whatever happend with starship troopers?
[16:08] <tsimpson> they made a terrible sequel...
[16:13]  * BluesKaj wonders how a pangolin can be precise ...methinks canonical needs consierably more logic in the OS name choices...talk about lame :)
[16:14] <yofel> s/canonical/sabdfl/
[16:14] <kubotu> yofel: You did something wrong... Try s/you/me/ or tell me "help sed"
[16:27] <apachelogger> who is this sabdfl?
[16:41] <yofel> someone who's favorite color seems to be orange
[16:41] <yofel> *whose
[16:43] <jussi> !sabdfl 
[16:43] <jussi> :D
[16:43] <jussi> apachelogger: he is yur overlord...
[16:45] <apachelogger> never seen him here
[16:45] <apachelogger> EBADMANAGEMENT
[16:59] <Tm_T> hmmm kubuntu_remove_startkde_cruft.diff
[16:59] <Tm_T> what is that about?
[17:00] <yofel> where did you find that?
[17:01] <Tm_T> kde-workspace apparently
[17:01] <Tm_T> see the conversation, especially the bottom of it here https://bugs.kde.org/show_bug.cgi?id=183143
[17:02] <Tm_T> they are not lost, just not applied
[17:03] <Tm_T> apachelogger: you have never seen sabdfl here? seriously?
[17:03] <yofel> ~seen sabdfl
[17:03] <kubotu> sabdfl was last seen 7 months, 3 days, 3 hours, 43 minutes and 11 seconds ago, quitting IRC (Read error: Connection reset by peer)
[17:03] <yofel> not in a while ^^
[17:03] <Tm_T> not in a while != never (;
[17:07] <Tm_T> yofel: that packaging and patches should be here, right? https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/kde-workspace
[17:07] <yofel> yeah, found it
[17:09] <Tm_T> I wonder if that bug could be fixed, so I finally can reboot my work laptop (:
[17:09] <Tm_T> haven't tried that fix there yet
[17:10] <yofel> Tm_T: are you on oneiric or precise?
[17:10] <Tm_T> oneiric
[17:10] <Tm_T> 4.8.0
[17:10] <Tm_T> all was fine before that upgrade
[17:10] <yofel> k, I'll make a quick test package with that patch disabled
[17:10] <Tm_T> I believe that patch cannot apply cleanly anyway on 4.8.0
[17:10] <yofel> well, it does
[17:11] <Tm_T> interesting
[17:11] <Tm_T> "apply on startup" should be true I suppose
[17:11] <Tm_T> as (not) applying the config is the problem
[17:13] <yofel> er no, all we do is remove the lines, so if I remove the patch it'll be false
[17:13] <yofel> but I guess the lines below are needed
[17:13] <Tm_T> ye
[17:14] <Tm_T> it's all a mess if you ask me in overall, so what works and what not is hard to figure out without testing /:
[17:23] <debfx> apachelogger: what's that?
[17:25] <apachelogger> debfx: a target that would update our kde-l10n copy scripts
[17:27] <bulldog98> Tm_T: I’ve got a patch that could be included
[17:27] <bulldog98> into kde-workopace
[17:27] <Tm_T> bulldog98: tested one?
[17:27] <debfx> aha, well gone with the rest of translation stripping
[17:27] <bulldog98> Tm_T: my own
[17:28] <yofel> bulldog98: which is?
[17:28] <Tm_T> bulldog98: yes but is it tested?
[17:28] <Tm_T> and what it is supposed to fix exactly (:
[17:28] <bulldog98> yofel: it’s a patch I wrote yesterday to fix tiling with activities
[17:29] <bulldog98> https://git.reviewboard.kde.org/r/103953/
[17:29] <yofel> we can cherry pick that after review
[17:29] <bulldog98> ok
[17:30] <yofel> Tm_T: are you on amd64 or i386
[17:31] <Tm_T> amd64
[17:32] <Tm_T> I wonder if I can test that randr issue at home any sensible way
[17:32] <Tm_T> ah, yes
[17:36] <shadeslayer_> yofel: Tm_T stop calling it amd64, the politically correct term is x86_64 :(
[17:36] <yofel> I know, tell that launchpad
[17:36] <yofel> and dpkg
[17:37] <shadeslayer_> I usually get queries like " Oh I have a Intel CPU, will this ISO install on my PC?"
[17:38] <yofel> oh yeah
[17:38] <shadeslayer_> dpkg uses amd64 as well?
[17:38] <shadeslayer_> dpkg--
[17:38] <yofel> well, yeah: xz-utils_5.1.1alpha+20110809-3_amd64.deb
[17:38] <yofel> blame ia64 for that naming
[17:39] <shadeslayer_> :)
[17:39] <shadeslayer_> apachelogger: plz2comment on http://bugs.kde.org/attachment.cgi?id=68732
[17:39] <shadeslayer_> eeeep
[17:39] <shadeslayer_> https://bugs.kde.org/show_bug.cgi?id=293030
[17:40] <shadeslayer_> specifically comment 5
[17:42] <apachelogger> shadeslayer_: what am I to comment|?
[17:42] <shadeslayer_> apachelogger: explain what you tried to explain to me a couple of days ago :P
[17:43] <apachelogger> well
[17:43] <apachelogger> alex already explained why this does not work
[17:43] <apachelogger> which is what I said, not a bug
[17:43] <apachelogger> simply a policy decision
[17:44] <shadeslayer_> *shrug* 
[17:44] <Tm_T> yofel: nah, removing or adjusting the patch makes no difference here
[17:44] <shadeslayer_> not well enough to dive into CMake ....
[17:44] <Tm_T> yofel: kde desktop has always native resolution no matter what saved settings say
[17:45] <yofel> so even adding those lines to /usr/bin/startkde it still doesn't work?
[17:45] <Tm_T> this is not funny
[17:45] <Tm_T> yofel: yup
[17:45] <yofel> hm
[17:46] <yofel> well, I found another issue while looking at this, so thanks for poking anyway..
[17:46] <shadeslayer_> lol
[17:46] <shadeslayer_> is that a IE ad in the Ubuntu HUD video on OMGUbuntu
[17:48] <Kurdistan> shadeslayer_, hud will be cooler with kde
[17:48] <Kurdistan> :P
[17:48] <Kurdistan> krunner plugin are working progress
[17:48] <shadeslayer_> Most of the stuff shown is already doable with krunner
[17:49] <shadeslayer_> Also, stuff like setting a IM message by using the HUD is what I proposed last year 
[17:50] <shadeslayer_> being able to chat with online contacts etc stuff like that
[17:50] <shadeslayer_> directly from krunner
[17:50] <Kurdistan> krunner rules
[17:50] <Kurdistan> :)
[17:52] <Kurdistan> what happend to fat fast setting or something like that
[17:52] <Kurdistan> to run kubuntu with low specs
[17:53] <apachelogger> shadeslayer_: you could like totally upload kde-hud
[17:53] <yofel> Tm_T: it does seem like the patch was re-enabled on accident though
[17:53] <apachelogger> to some ppa
[17:54] <yofel> it was disabled in 4.7
[17:54] <shadeslayer_> apachelogger: meta package that pulls in KDE? :P
[17:54]  * yofel still hasn't found out where that patch came from in the first place
[17:54] <apachelogger> yofel: please inform shadeslayer_ about kde-hud
[17:54] <apachelogger> or afiestas
[17:55] <apachelogger> or someone
[17:55] <shadeslayer_> apachelogger: ah that, the search thing from help menu's?
[17:55] <shadeslayer_> I saw that last year
[17:55] <shadeslayer_> but then no one made any progress :(
[17:56]  * yofel is still digging through the forest of workspace patches
[17:56] <superfly> krunner is awesome once you disable a couple of the plugins... most notable the nepomuk one.
[17:57] <superfly> *notably
[17:57] <Kurdistan> superfly, +1
[17:57] <yofel> great, where's jonthetaco when you need him
[17:57] <yofel>   * Add kubuntu_72_remove_startkde_cruft.diff to remove test for a setting in
[17:57] <yofel>     kcmrandrrc that doesn't exist anymore. (KDE expects krandrtray to handle
[17:57] <yofel>     resolution setting on startup now...)
[17:58] <yofel> Tm_T: do you have krandrtray running?
[17:58]  * superfly won't talk about the big mess that is Kontact/Akonadi
[17:58] <apachelogger> yofel: what's the question?
[17:59] <apachelogger> <-- rewrote startkde in cpp once, just for the sake of seeing if it was any faster
[17:59] <apachelogger> it was not :P
[17:59] <yofel> apachelogger: https://bugs.kde.org/show_bug.cgi?id=183143 which people claim is our fault
[17:59] <yofel> which might very well be the case
[18:00] <yofel> more like the current patch doesn't do what the original one was supposed to do
[18:00] <apachelogger> lemme enter markey
[18:01] <yofel> Riddell: you don't by chance remember why you re-enabled that?
[18:04] <apachelogger> yofel: utter rubbish
[18:04] <apachelogger> yofel: the kcm does not even write those lines
[18:04] <apachelogger> only startupcommand thingy
[18:04] <yofel> well, why is that in startkde then?
[18:04] <apachelogger> so the startkde rubbish is still crap and actually should be removed upstream
[18:04] <apachelogger> I wonder why we did not remove it back when the patch was introduced
[18:05] <apachelogger> yofel: because no one in kde gives a shit about display settings...
[18:05] <apachelogger> which is why it does not work to begin with
[18:05] <yofel> go tell them then
[18:05] <apachelogger> no
[18:05] <apachelogger> I am doing phonon QA
[18:05] <yofel> I'm utterly confused by now
[18:05] <apachelogger> also afiestas is doing fixy fixy for that stuff anyway
[18:10] <yofel> uhm, ok, after taking a quick glance, yeah, krandr is a mess...
[18:12] <apachelogger> take kephal into the picture and you'll start crying :P
[18:15] <Kurdistan> have nice day every one. going to log out. 
[18:15] <Kurdistan> yofel, thx again. 
[18:15] <yofel> np
[18:27] <yofel> hm, no, removing the patch doesn't work here either
[18:28] <apachelogger> u no trust me? :O
[18:28] <apachelogger> :'(
[18:52]  * yofel is speechless after reading kstartupconfig/kstartupconfig.c
[19:13] <yofel> actually, calling this an utter mess is an understatement
[19:14] <yofel> after looking at this for over an hour I *still* have no idea what is *supposed* to set the resolution at login
[19:29] <apachelogger> yofel: nothing
[19:29] <apachelogger> the only reasonable way right now would krandrtray in autostart
[19:29] <apachelogger> which worked for some time
[19:29] <apachelogger> but is broken now
[19:29] <apachelogger> god knows why
[19:29] <yofel> yeah, I'm reading the comments now and will post a request for someone to explain this to me
[19:30] <yofel> as I've given up on this
[19:30] <yofel> what SANE C code in the world uses goto?!?
[19:35] <shadeslayer_> yofel: pretty much all of it
[19:35]  * shadeslayer_ hates goto
[19:36] <shadeslayer_> I was reading libnice code and it has goto's all over the place to handle error conditions
[19:36] <yofel> well, feel free to read kstartupconfig.c - that is a perfect example for unmaintainable code
[19:36] <shadeslayer_> nah thanks, I'm having a field day with glib threads
[19:37] <shadeslayer_> I have a trivial problem in my code, can't figure it out
[19:37] <shadeslayer_> yofel: https://gist.github.com/1803805 < Some sane C code
[19:37] <yofel> will look at it in a bit
[19:38] <shadeslayer_> and even that uses goto
[19:49] <BarkingFish> evening all :)
[19:49] <BarkingFish> Hi dantti :D
[19:50] <shadeslayer_> I'm off to sleep, cya
[19:50] <BarkingFish> bbfn shadeslayer_ 
[19:50] <BarkingFish> have a good night.
[20:23]  * apachelogger dances in the kitchen
[20:23] <apachelogger> yofel: goto is the single most useful feature of C
[20:24] <apachelogger> particularly in kstartupconfig, cause as you might have noticed, it is tuned towards performance :P
[20:25] <yofel> it saves... what? a tenth of a second?
[20:26] <apachelogger> depends on why it is used
[20:26] <apachelogger> for example in my OS I have plenty of goto to work around missing scoped pointers
[20:27] <apachelogger> if you collapse code into one function you almost always have to use goto
[20:27] <apachelogger> otherwise it would become unreadable
[20:33] <yofel> fix gcc instead
[20:43] <apachelogger> it's just a jump to the left
[20:47] <Darkwing> apachelogger: Ummmm...
[21:12] <yofel> Tm_T: can you see if you have this? https://bugs.kde.org/show_bug.cgi?id=183143#c103
[21:18] <apachelogger> I lol'd
[21:18] <apachelogger> yofel: someone clearly updated the patch to break stuff
[21:18] <apachelogger> winwinwin
[21:19] <yofel> Riddell did it while merging from debian for 4.7.3
[21:19] <yofel> I'm dropping the patch
[21:20] <apachelogger> yofel: ack
[21:26] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/kde-workspace] Philip Muškovac * 614 * debian/ (4 files in 2 dirs) * Drop kubuntu_remove_startkde_cruft.diff as it breaks krandrstartup * Refresh kubuntu_startkde_set_country.diff
[21:31] <apachelogger> markey, Mamarok: ^
[21:31] <apachelogger> yofel: that done ... krandrtray still does not apply the setting as expected
[21:31] <apachelogger> :/
[21:33] <yofel> telling krandr to save the settings as default and dopping the patch did work on my eeepc
[21:33] <apachelogger> yes
[21:34] <apachelogger> but krandrtray is not compatible with that :P
[21:34] <yofel> well, *that* isn't our fault ^^
[21:34] <apachelogger> just saying
[22:53] <Riddell> yofel: mm no sorry, it's quite possible I messed up on the randr stuff when merging
[23:02] <apachelogger> Riddell: no worries, that was not immediately obvious
[23:05] <yofel> nah, we should've completely removed it in the first place
[23:13] <Kurdistan> hi. is it only for me but when I boot up, kmix start up later then all other widgets?
[23:14] <Kurdistan> noticeable delay
[23:34] <ScottK> New python-qt4 and sip4 packaged in Debian.  I'll sync them tomorrow.
[23:35] <Riddell> thanks ScottK 
[23:35] <ScottK> NP.
[23:35] <apachelogger> which reminds me that I have to do some pyth0rn haxx0ring tomorrow \o/
[23:36] <ScottK> I uploaded qscintialla2 earlier today.
[23:36] <ScottK> (it was a merge)
[23:36] <apachelogger> and that reminds me that jockey-kde does not work properly for me