[00:25] <apachelogger> afiestas: didn't you have a patch for bug 898390
[00:41] <apachelogger> "Follow feature freeze"
[00:41] <apachelogger> I think I need to write you people a 101 on how to write work items :P
[00:42] <Kurdistan> hi channel
[00:43] <apachelogger> [kubuntu-members] Make sure https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting is up to date and easily found from kubuntu.org: TODO
[00:43] <apachelogger> [kubuntu-members] Document on above wiki page which packages are kubuntu specific: TODO
[00:43] <apachelogger> that is wrong
[00:43] <apachelogger> the reporting stuff should not be on the wiki to begin with
[00:43] <Kurdistan> gnumdk is netrunner repo?
[00:43] <Kurdistan> I think so
[00:43] <apachelogger> gnumdk?
[00:44] <Kurdistan> apachelogger, https://launchpad.net/~gnumdk/+archive/ppa
[00:44] <yofel> apachelogger: where should it be?
[00:45] <Kurdistan> apachelogger, it was dicsussion about gnumdk.
[00:45] <Kurdistan> and I think he have some to do with kubuntu based netrunner
[00:45] <yofel> ah, you mean ejat
[00:45] <Kurdistan> yofel, exactly.
[00:45] <yofel> yeah, looks like it was the package from there
[00:46] <apachelogger> yofel: help.ubuntu
[00:46] <yofel> apachelogger: well, *that* links to our page
[00:46] <apachelogger> wiki = contributors
[00:46] <apachelogger> help = users
[00:46] <yofel> ah wait
[00:46] <yofel> right
[00:46] <yofel> agreed
[00:46] <Kurdistan> I will be much more in kubuntu channel then before
[00:47] <Kurdistan> thats what I can give right now and easy packing
[00:47]  * yofel hugs Kurdistan
[00:47] <Kurdistan> only problem is uni :)
[00:47] <Kurdistan> but when I have time I will be here 
[00:48] <Kurdistan> yofel, thats least I can do.
[00:48] <Kurdistan> kubuntu and kde is growing inside me 
[00:48] <Kurdistan> I got loved with kde in 4.6.5
[00:49] <Kurdistan> if we can fix smal issue with kubuntu, it will på top of the top.
[01:12] <afiestas> apachelogger: mope
[01:12] <afiestas> *nope
[01:13] <apachelogger> afiestas: go fix it then :P
[01:13] <afiestas> nah
[01:13] <apachelogger> I mean, it worked before 4.8 (at least for markey) so the regression cannot that big
[01:13] <apachelogger> though rather annoying impact
[01:13] <afiestas> I didn't broke it :p
[01:15] <Kurdistan> what is the regression?
[01:16] <yofel> screen resolution getting reset on every login
[01:18] <Kurdistan> yofel, hmm. is it "kubuntu" specific or upstream?
[01:19] <yofel> upstream from what I know
[01:26] <Kurdistan> yofel, oki.
[01:26] <Kurdistan> hmm it seems one http://i.imgur.com/2u5qd.jpg is affected of this bug
[01:26] <Kurdistan> and this person does not use nvidia beta drivers
[01:26] <Kurdistan> latest stable nvidia with kde 4.8.0
[01:27] <Kurdistan> starting to think it can be kde/kubuntu bug
[01:28] <Kurdistan> problem accure when log in and log out
[01:44] <yofel> Kurdistan: hm, thinking of it, I've seen a black background issue in gtk apps sometimes, but it's like totally random and usually fixed by rebooting
[01:44] <yofel> it doesn't affetc Qt though
[01:44] <yofel> *affect
[01:47] <Kurdistan> yofel, yes it fixes with reboot
[01:47] <Kurdistan> or restarting x
[01:48] <Kurdistan> yofel, will try tomorrow if it effects qt
[02:44] <Kurdistan> bye channel. sleep.
[10:53] <Kurdistan> yofel, you hade right my friend this bug only effects gtk application.
[10:53] <yofel> lol
[10:53] <yofel> even ubuntu's software center agrees that KDE apps are supreme :D
[10:53] <yofel> http://people.ubuntu.com/~yofel/pics/softcent.png
[10:54] <Kurdistan> yofel, is there any bug-report about this?
[10:54] <yofel> no idea, I haven't filed one because I couldn't figure any way out how to reliably reproduce that
[10:55] <Kurdistan> yofel, I have just reproduce it.
[10:55] <Kurdistan> is seems 3 person include me are all nvidia users also
[10:55] <yofel> ...
[10:55] <yofel> well, same for me
[10:55] <Kurdistan> yofel, can you log in/out let say 3 time?
[10:56] <Kurdistan> this will happen then
[10:57] <yofel> hm, ok
[10:59] <yofel> oh fun, happened on first logout
[10:59] <yofel> now what to file a bug against.....
[10:59] <Kurdistan> yofel, then this is a kde bug and not nvidia
[10:59] <yofel> well, file it against oxygen-gtk, maybe they'll know where to look
[11:00] <yofel> except that this isn't theme specific at all
[11:00] <yofel> could be a bug in gtk as well
[11:01] <yofel> but then it would be gtk2 and gtk3
[11:01]  * yofel is clueless
[11:01] <Kurdistan> yofel, same here. 
[11:02] <Kurdistan> yofel, only fix is restart computer or restarting x.
[11:02] <yofel> hm
[11:02]  * yofel kills kdm
[11:02] <Kurdistan> yofel, you think it can be kdm related?
[11:03] <yofel> fixed
[11:03] <yofel> hm
[11:03] <yofel> as I said, I don't know. It could be anything that's related to gtk rendering
[11:05] <Kurdistan> can some one with other gaphical card test it?
[11:05] <Kurdistan> let se if it is nvidia only
[11:05] <Kurdistan> yofel, you are also running kde 4.8.0?
[11:06] <yofel> 4.8 precise
[11:06] <yofel> ah wait, I've an intel card in my eeePC
[11:07] <Kurdistan> yofel, okey, this can be kde 4.8.0 bug
[11:07] <yofel> I don't think so
[11:07]  * yofel throws the nvidia driver off his system
[11:08] <Kurdistan> yofel, I am chatting with slackware user now. let see if he have the same issue.
[11:10] <Kurdistan> yofel, this bug did not effect your eeePC with intel?
[11:13] <yofel> now let's see if I can reproduce this with nouveau without locking my GPU up...
[11:14] <Kurdistan> yofel, hehe good luck.
[11:20]  * yofel files a bug against nvidia
[11:21] <Kurdistan> yofel, so this was nvidia specific?
[11:21] <Kurdistan> you are a angel
[11:22] <yofel> intel: unreproducable, nouveau: unreproducable, nvidia 290: breaks after 1 or 2 tries
[11:22] <Kurdistan> yofel, remenber to mention
[11:22] <Kurdistan> also latest nvidia beta driver 295.17 breaks it
[11:23] <yofel> hm....
[11:23] <yofel> now I need a working browser that I can file this with...
[11:23] <yofel> -.-
[11:24] <yofel> konqueror to the rescue :D
[11:25] <Kurdistan> yofel, hehe
[11:27] <yofel> hm
[11:27] <Kurdistan> yofel, same problem with konqueror?
[11:28] <yofel> no, but some Qt applications are affected after all
[11:28] <yofel> ksnapshot looks broken here
[11:29] <Kurdistan> yofel, hmm. that was intressting.
[11:30] <yofel> but I can't find a patter there. ksnapshot is rendered like dolphin from your snaphot, but everything else seems fine
[11:30] <yofel> *pattern
[11:30]  * yofel digs throug nvnews
[11:33] <Kurdistan> yofel, can not find anything useful from nvnews
[11:33] <yofel> hm, why am I getting an nspluginviewer crash when I don't even have the wrapper installed o.O
[11:34] <yofel> ah, that's part of konqueror-nsplugins
[11:38] <Kurdistan> yofel, did you write bug-report for this to nvidia (nvnews)?
[11:40] <yofel> sry, filed a bug about nspluginviewer firt
[11:40] <yofel> *first
[11:43] <Kurdistan> yofel, take your time.
[11:44] <Kurdistan> I wonder if this is nvidia+kde 4.8.0 specific or not.
[11:45] <yofel> IIRC I've seen that with 4.7 too, so I rather thing it's an issue with the recent nvidia blobs
[11:46] <yofel> trying an older one might work, but X in precise is too new for that I think
[11:46] <yofel> on oneiric you could have a chance
[11:46] <yofel> Kurdistan: I've given up on nvnews. I'm horrible with captchas, add what you want on bug 930614
[11:48] <Kurdistan> yofel, thx like I mention also 295.17 (beta) drivers are effected
[11:48] <yofel> sure, and set the bug to confirmed while you're at it
[11:49] <Kurdistan> yofel, will do. lets se my password for launchpad.
[12:01] <Kurdistan> yofel, so fixed my password. now I will confirmed.
[12:07] <Kurdistan> yofel, done.
[12:46] <shadeslayer> Quintasan: I'm moving the telepathy kde packages into the team ppa
[12:48] <yofel> now... what did I want to do again when I woke up...
[13:19] <BluesKaj> Hey folks
[13:19] <Kurdistan> hi BluesKaj 
[13:19] <BluesKaj> hey Kurdistan
[13:19] <Kurdistan> BluesKaj, you had nvidia card?
[13:19] <BluesKaj> yes
[13:19] <Kurdistan> https://launchpad.net/bugs/930614
[13:22] <BluesKaj> I haven't had any problems Kurdistan , and I have nvidia on 2 pcs runnining 12.04
[13:24] <Kurdistan> BluesKaj, have you tried login out/in
[13:24] <Kurdistan> ? 2-3 times in road
[13:24] <BluesKaj> i did yesterday
[13:29] <Kurdistan> BluesKaj, okey intressting. 
[13:29] <Kurdistan> it affects me, yofel and some user in swedish loco.
[13:30] <Kurdistan> we all have kde 4.8.0 and nvidia cards
[13:30] <yofel> BluesKaj: used any GTK stuff after that?
[13:30] <yofel> as this mostly affects gtk
[13:33] <BluesKaj> yofel,  yes , synaptic, it doesn't accept text in the qquick search box , so one has to use the seperate search , but otherwise I haven't noticed anyhing
[13:33] <Tm_T> afiestas hmmm
[13:34] <BluesKaj> I can try relogging in 
[13:34] <schnelle> Kurdistan, yofel: I am using opensorce ati drivers and I don't have that problems.
[13:34] <BluesKaj> schnelle,  this is nvidia
[13:34] <schnelle> but for me logout on opensorce ati drivers doesn't work by default
[13:34] <yofel> schnelle: yeah, seems to be nvidia blob only
[13:34] <Kurdistan> schnelle, it seems not effecting intel and ati then.
[13:34] <Kurdistan> only blob so far
[13:35] <Tm_T> afieastas' appmenu-"hud" thingy doesn't seem to work here /:
[13:35] <BluesKaj> ok ,brb I hope
[13:35] <schnelle> yes, but i want to say, by default logout doesn't work for me since... mmm ever. I have to edit kdmrc file and uncomment "TerminateServer=true" line
[13:36] <schnelle> so you can try to uncomment that line, reboot for change to take effect, and then logout/login to see does this tweak helps
[13:36] <yofel> that'll help
[13:36] <yofel> as we know that killing X helps
[13:37] <schnelle> yofel: why kubuntu doesn't ship this line uncommented by default? 
[13:37] <schnelle> for many ati opensource users (and intel) logout doesn't work by default
[13:38] <schnelle> untill TerminateServer=true is uncommented
[13:38] <yofel> rephrase that: why does KDE ship that with false as default
[13:38] <Kurdistan> is there a fix for this?
[13:38] <yofel> Kurdistan: well, see what schnelle just said, and tell that the other person that's affected
[13:38] <Kurdistan> yofel, will try that. 
[13:39] <schnelle> KUrdistan: you have to reboot after uncommeting the "TerminateServer=true" line
[13:40] <BluesKaj> all seems fine here , but I don't use much GTK , so I guess I'm not much help :)
[13:42] <yofel> apachelogger: what happened to your plymouth stuff?
[13:42] <Kurdistan> schnelle, thx will do.
[13:44] <schnelle> will precise use kdm or lightdm?
[13:45] <yofel> kdm I guess
[13:45] <yofel> I have no idea what the progress on lightdm is
[13:45] <Kurdistan> it this will fix the issue should we have this from start in 12.04?
[13:46] <Kurdistan> *if this
[13:46] <yofel> well, I would have to talk to the kdm devs why this is false in the first place, then see if we can consider that
[13:48] <schnelle> in my experience, with ati and nvidia proprietary drivers, logout works, with opensource drivers i have to uncomment that line to make logout work
[13:48] <yofel> works fine with nouveau and intel
[13:48] <Kurdistan> schnelle, my uncomment you mean remove # and were is kdmrc?
[13:48] <schnelle> yes
[13:48] <yofel> kdmrc is /etc/kde4/kdm/kdmrc
[13:48] <Kurdistan> I can not find it in .kde
[13:49] <Kurdistan> I see wrong dire... :)
[13:50] <Kurdistan> schnelle, I do not even have TerminateServer=true in kdmrc
[13:51] <schnelle> very strange
[13:51] <yofel> Kurdistan: can you pastebin your kdmrc?
[13:51] <schnelle> i have it on all my installations
[13:51] <Kurdistan> yofel, I will do.
[13:53] <Kurdistan> yofel, http://paste.ubuntu.com/837832/
[13:55] <yofel> Kurdistan: add the setting to the [X-:*-Core] section
[13:56] <Riddell> ideas and mentors needed for KDE..
[13:56] <Riddell> 13:36 < Teo`> Everyone, GSoC 2012 ideas time! If you have an idea that you want to see implemented by a student during GSoC, don't keep it to  yourself :D Please add it to the Ideas page http://community.kde.org/GSoC/2012/Ideas
[13:56] <Kurdistan> yofel, why does not I have this but schnelle ?
[13:57] <yofel> Kurdistan: no idea, your file doesn't have much to do with the default one
[13:57] <yofel> Kurdistan: see mine: http://paste.kde.org/278678
[13:57] <Kurdistan> yofel, damn that was real different
[13:58] <shadeslayer> I added one
[13:58] <shadeslayer> :P
[13:59] <Kurdistan> yofel, http://paste.ubuntu.com/837840/
[13:59] <Kurdistan> it should like this?
[13:59] <schnelle> Kurdistan, yofel: yes mine looks line yofel's too
[13:59] <yofel> I think yes
[13:59] <schnelle> *like
[13:59] <Kurdistan> thats wierd yours like different from mine
[14:03] <Kurdistan> brb rebooting
[14:03] <Kurdistan> and testing :)
[14:06] <BluesKaj> yofel,  your looks like a conf file 
[14:06] <BluesKaj> yours
[14:11] <Kurdistan> it worked
[14:11] <Kurdistan> like a charm
[14:12] <Kurdistan> :) log out/login several time. np anymore.
[14:12] <Kurdistan> schnelle, :) you fixed it.
[14:12] <schnelle> for me this is "must do" for years ;)
[14:12] <Kurdistan> schnelle, hehe okey.
[14:14] <schnelle> i hope someone ( yofel :)  ) get in touch with kdm devs, and if they say that "it is safe", kubuntu could ship this as default
[14:15] <schnelle> there is no kdm channel on freenode
[14:15] <schnelle> it seems...
[14:18] <Kurdistan> schnelle, that would be wonderful if thats happens.
[14:18] <Kurdistan> it seems to work perfect here
[14:18] <Kurdistan> and I thought first it was nvidia driver bug
[14:18] <Kurdistan> :P was hard against nvidia in there channel
[14:20] <schnelle> Kurdistan: well, kdm + opensorce ati driver = logout never worked by default
[14:20] <schnelle> gdm + ati driver = always worked
[14:20] <schnelle> so i think it is kdm issue
[14:20] <Kurdistan> schmidtm, okey. i think you have right. 
[14:20] <Kurdistan> it most be kdm issue
[14:20] <schnelle> but i am totally noob about this, so i am just guessing... :)
[14:21] <PaulW2U> Hi all, I think you're describing launchpad bug #651294 which is marked as fix released.
[14:22] <Kurdistan> schnelle, :P not so noob if you could solve this.
[14:22] <PaulW2U> But I have to make the kdm modification each time I installed Kubuntu. :o(
[14:22] <Kurdistan> PaulW2U, mine problem is not really that x crashers.
[14:22] <schnelle> paulW2U: me too
[14:22] <Kurdistan> it is problem with rendering issue after login for gtk mainly and some qt
[14:22] <PaulW2U> No I don't see a crash either but if you look at the duplicate reports ...
[14:23] <schnelle> yes but the solution is the same: uncomment "TerminateServer=true" line
[14:23] <Kurdistan> PaulW2U, will read.
[14:24] <Kurdistan> PaulW2U, it is more a kdm bug then xorg-server I think.
[14:28] <Kurdistan> :( boring now I have only one bug left on my system.
[14:28] <Kurdistan> that is application that are closed there icon still shows up. not always.
[14:28] <Kurdistan> :( what should I do if that fixes also.
[14:29] <Kurdistan> *panel bug
[14:33] <yofel> go install precise in a VM, although that works resonable well here....
[14:33] <BluesKaj> Kurdistan,  that panel bug has been around since 11.04 on my pc
[14:33] <Kurdistan> BluesKaj, yeah I know. :(
[14:34] <schnelle> Kurdistan: it is Qt bug. There is a ppa with patched Qt: ppa:hrvojes/qt
[14:34] <schnelle> upgrade qt from this ppa and panel bugs go away! :)
[14:34] <Kurdistan> BluesKaj, it seems not effect ati user. my parents computer did not have that problem if I remenber right.
[14:35] <Kurdistan> schnelle, does it work for you?
[14:36] <Kurdistan> then we should apply that patch.
[14:36] <schnelle> i wrote last night to kubuntu-devel last night and asked kubuntu-devs to include patches in precise
[14:36] <schnelle> Kurdistan: it works perfect
[14:36] <Kurdistan> schnelle, what was the response?
[14:37] <schnelle> it should be in for precise
[14:37] <schnelle> https://lists.ubuntu.com/archives/kubuntu-devel/2012-February/005794.html
[14:38] <schnelle> so, i am using patched qt from ppa:hrvojes/qt, and all panel bugs are gone
[14:40] <Kurdistan> schmidtm, were is the patch?
[14:41] <Kurdistan> kubuntu 12.04 will be bugg free for me. :)
[14:43] <schnelle> read my message from kubuntu-devel (link above), i explained everything about patches there :)
[14:44] <Kurdistan> schnelle, will read.
[14:44] <Kurdistan> I am trying the patch
[14:46] <BluesKaj> Kurdistan,  ok, I have 2 pcs with nvidia , so didn't know it had to do with the nvidia module
[14:46] <schnelle> when you  upgrade qt from ppa:hrvojes/qt, you have to reboot
[14:47] <Kurdistan> schnelle, will do. :) will only add ppa
[14:48] <tsimpson> reboot?! I'm tempted to throw !language at you..
[14:51] <Kurdistan> schnelle, will restart the laptop :). lets hope it fix the problem for me.
[14:57] <shadeslayer> Riddell: oh awesome, I'll check it out on rekonq master ( re kde bug 238303)
[14:58] <Kurdistan> schnelle, it works great.
[14:59] <schnelle> Kurdistan: yay! :) for me only veromix plasmoid was broken after upgrade. so i removed it and then i reinstalled it. 
[15:00] <schnelle> no more panel bugs! :)
[15:00] <Kurdistan> schnelle, thx again.
[15:00] <shadeslayer> apachelogger: I believe that is by design
[15:00] <shadeslayer> ( re rekonq making the back button available only after the page loads )
[15:01] <shadeslayer> whee deadlock in rekonq
[15:02] <shadeslayer> and book
[15:02] <shadeslayer> s/book/boom/
[15:02] <kubotu> shadeslayer meant: "and boom"
[15:05] <apachelogger> yofel: oh, right, I should upload that
[15:05] <apachelogger> shadeslayer: then the design is broken
[15:05] <apachelogger> page loading can take looong
[15:05] <shadeslayer> apachelogger: then please tell that to the rekonq mailing list :)
[15:05] <shadeslayer> lemme find the exact commit for you
[15:09] <shadeslayer> hmm ... can't seem to find it, but I remember this was discussed somewhere
[15:09] <BluesKaj> so where's the patch ?, all I get is links to other related bugs
[15:10] <Kurdistan> BluesKaj, do you mean panel bugg?
[15:11] <Kurdistan> you have the patches here: https://launchpad.net/~hrvojes/+archive/qt
[15:11] <BluesKaj> Kurdistan,  yes
[15:11] <BluesKaj>  sometimes launchpad is the most annoying page 
[15:12] <Kurdistan> BluesKaj, +1
[15:12] <Kurdistan> it fixed the problem for me. now even application launches faster
[15:12] <Kurdistan> :)
[15:18] <BluesKaj> Kurdistan, good , updgrading now
[15:19] <Kurdistan> BluesKaj, restart your computer after.
[15:20] <yofel> logging out is probably enough...
[15:20] <yofel> probably
[15:28] <Kurdistan> I hope every thing went good for blueskaj
[15:34] <Kurdistan> BluesKaj, wb.
[15:35] <Kurdistan> did the patch work you? it worked here.
[15:36] <BluesKaj> yes , Kurdistan , schnelle ..works geat , thanks :)
[15:37] <BluesKaj> great 
[15:37] <Kurdistan> BluesKaj, is only for me, or does application now open crazy fast? :)
[15:38] <Kurdistan> most be the bug that made application load slower to pop up
[15:39] <Kurdistan> :) it is so fast it feels to run lxde :P
[15:40] <BarkingFish> afternoon guys. Anyone about?  I think we have some problems on the latest set of updates.
[15:41] <BluesKaj> yes Kurdistan , seems quite bit faster , especially system settings that used to take quite a while
[15:41] <BarkingFish> I have 27 updates to put through, but apper is screaming about Unsigned packages, which I go to confirm that I want to download and install, I click yes - and it takes me back to the start of the install process and asks me the same question repeatedly, until i click no.
[15:42] <Kurdistan> BluesKaj, exactly. even firefox loads crazy fast.
[15:42] <yofel> could be that the ppa has some preload stuff on too
[15:42] <BarkingFish> This is what I get: "You are about to install unsigned packages that can compromise your system, as it is impossible to verify if the software came from a trusted source.  Are you sure you want to proceed with the installation?"
[15:43] <BarkingFish> if it's in our repositories, surely it's been put together with a signature, right?
[15:43] <BluesKaj> BarkingFish,  well, if you're on 12.04 , unsigned packages is probly the norm ...using a package manager with a dev OS is bound to give the package manager apps fits :)
[15:43] <BarkingFish> I'm not though, I'm on 11.10
[15:43] <BarkingFish> I'm not upgrading till 12.04 is released
[15:43] <yofel> usually you shouldn't get unsigned warnings
[15:44] <BarkingFish> I guess I need to install the remaining updates one by one, and find which one is unsigned...
[15:44] <yofel> file a bug againt apper somewhere and then check with apt-get update if you're missing some key
[15:45] <Kurdistan> BarkingFish, have you upgrade to kde 4.8.0?
[15:45] <BarkingFish> no, still on 4.7.4
[15:46] <BarkingFish> I don't see any updates to 4.8.0
[15:47] <Kurdistan> BarkingFish, does this help: sudo rm -rf /var/lib/apt/lists/* 2. sudo apt-get update 3. sudo apt-get upgrade
[15:47] <BarkingFish> I'll tell you in a sec :)
[15:50] <Kurdistan> BarkingFish, yppa manager is a good tool. it fixes a lot of stuff with repo and errors.
[15:51] <Kurdistan> BarkingFish, https://launchpad.net/~webupd8team/+archive/y-ppa-manager
[15:51] <Kurdistan> it works great with kubuntu
[15:51] <BarkingFish> let me see how this goes first :D
[15:52] <yofel> just btw., this is the -dev channel, support is still in #kubuntu
[15:52]  * yofel is gone for  a while
[15:52] <Kurdistan> yofel, thats true.
[15:52] <BarkingFish> I'm gonna go make some coffee, this is taking a while :)
[15:52] <Kurdistan> BarkingFish, we can take it #kubuntu
[15:54] <BarkingFish> I'll keep it here for now, thanks Kurdistan - if it does turn out to be an unsigned package, these guys will need to know which one 
[15:54] <Kurdistan> BarkingFish, okey. did it help anything?
[15:55] <BarkingFish> It still wants to upgrade the remaining packages I didn't do in the one by one, so I have 23 to come down now
[15:55] <BarkingFish> I'll see if doing the upgrade in a terminal flags anything up
[15:57] <BarkingFish> I didn't realise the kernel had been updated too :)
[15:57] <BarkingFish> this is gonna take some time. 
[16:00] <Kurdistan> will log out. take care all.
[16:09] <shadeslayer> apachelogger: poke
[16:33] <grmls> hi
[16:36] <BarkingFish> hi again guys, sorry about the long break.
[16:37] <BarkingFish> Right, everything went through in the terminal upgrade, and it was only the same packages that apper was trying to work on.
[16:37] <BarkingFish> So what I'm going to do is file a bug against apper, as suggested, and make sure that the KDE guys are aware that it's being a PITA.
[16:45] <BarkingFish> oh this is fun.  KDE's bug reporter won't submit my bug :)
[16:56] <BarkingFish> Right, I've had to pass the bug to one of KDE's team to file, as the bugzilla won't submit my bug for some reason, I think the browser might be busted.
[16:56] <BarkingFish> rindolf is going to try and file, and once he does, I'll paste the bug number in here
[17:13] <BarkingFish> Ok guys, for the record - the apper bug is filed at KDE 293848
[17:16] <EagleScreen> anyone know who is upstream of libreoffice-kde? where to send feedback about that package?
[17:31] <BarkingFish> right guys, I'm gonna scoot for a bit. See you all later.
[17:57] <yofel> EagleScreen: libreoffice
[17:57] <yofel> EagleScreen: what's the feedback btw.?
[17:58] <EagleScreen> dropdown menus are ugly in KDE, they have no border
[17:58] <yofel> ah, true
[18:01] <shadeslayer> Riddell: yup, that commit fixed the buildlog bug
[18:01] <shadeslayer> huzzah
[18:06] <Riddell> sweet
[18:06] <Riddell> just needs rekonq packaged now :)
[18:07] <yofel> might as well do that, I'm done with gtk
[18:07] <yofel> or rather stuck on 2 mirs
[18:07] <Riddell> yofel: pinged the mir team?
[18:08] <yofel> there are bugs filed and ubuntu-mir subscribed, anything else to do?
[18:08] <yofel> I doubt they'll do much on a weekend
[18:10] <apachelogger> shadeslayer: huh?
[18:10] <shadeslayer> apachelogger: I was wondering how one disables Werror in CMake
[18:11] <shadeslayer> apachelogger: but then cmake-qt-gui to the rescue
[18:12] <shadeslayer> yofel: if you're there, can you check if the Telepathy Integration Module is running for you in kded?
[18:12]  * yofel adds telepathy back to the panel
[18:14] <yofel> I have an Instant Messaging Approver running, but no TIM
[18:14]  * BluesKaj waits patiently for rekonq flash crash fix :)
[18:15] <shadeslayer> eeep
[18:15] <yofel> shadeslayer: if that's supposed to be in 'kde-telepathy-integration-module', that package is empty
[18:15] <shadeslayer> yeah
[18:15] <shadeslayer> yofel: fixing
[18:15]  * shadeslayer does not know how that slipped past
[18:16] <yofel> add proper long install files to the packages
[18:16] <yofel> otherwise that happens really easy
[18:17] <shadeslayer> fffuuuuuu 
[18:17] <shadeslayer> yofel: yeah, install file was not renamed
[18:17] <yofel> bwahahaha
[18:17] <apachelogger> I lol'd
[18:17] <apachelogger> shadeslayer: why rename though?
[18:17] <shadeslayer> apachelogger: telepathy-kde-foo to kde-telepathy-foo
[18:18] <shadeslayer> apachelogger: following upstream changes
[18:18] <apachelogger> why does it have a name prefix though?
[18:18] <shadeslayer> name prefix?
[18:18] <apachelogger> isn't telepathy using atomic tarballs?
[18:18] <shadeslayer> I don't follow
[18:18] <apachelogger> foo.install rather than install
[18:19] <shadeslayer> as in, why does it have the install file?
[18:19] <apachelogger> no
[18:19] <apachelogger> why does the install file have a prefix
[18:22] <shadeslayer> apachelogger: I *really* don't understand what you're asking
[18:22] <apachelogger> perhaps you should RTFM then
[18:22] <apachelogger> then you will know what I mean
[18:23]  * shadeslayer brings up the new maintainers guide
[18:23] <yofel> I think you'll find that faster in the policy
[18:23] <apachelogger> the new maintainers guide is not the  manual for debian/install :P
[18:24] <apachelogger> Mamarok: is there going to be dinner or am I to raid the fridge for booty?
[18:24] <shadeslayer> I've never seen a debian/install file tbh
[18:24]  * apachelogger finds that hard to believe
[18:25] <shadeslayer> apachelogger: I've always seen files like foo.install
[18:26] <yofel> well, you usually have more than one binary package, and if you just install everything you theoretically need none
[18:26] <yofel> so it's a rare case
[18:26] <apachelogger> yofel: rare with kde because you people insist on manually doing dbg packages
[18:27] <yofel> well, we dropped those on the debian merge anyway
[18:27] <yofel> I'll try to hack pkgbinarymangler for 4.9 beta
[18:27] <apachelogger> so it should be fairly common :P
[18:27] <yofel> then we won't need them in the first place
[18:27] <apachelogger> that hardly belongs in there IMHO
[18:27] <shadeslayer> I still can't find it, but I'm guessing the debian/install file just specifies where to install stuff when you have a single binary package
[18:28] <apachelogger> yofel: pkg-kde-tools seems the more logical place
[18:28] <yofel> apachelogger: beta packages without debug symbols are useless, no matter how unlikely a bug is
[18:28] <yofel> ah, you meant that
[18:28] <yofel> ok
[18:28] <yofel> I'll look at that
[18:28] <apachelogger> dbg package generation is not really mangling as the symbols are stripped either way
[18:29] <apachelogger> with a dbg package they just do not get thrown away :)
[18:29] <apachelogger> !man dh_install
[18:29] <yofel> well, more like I need to take a closer look at pkg-create-dbgsym 
[18:29] <apachelogger> awww
[18:29] <apachelogger> ubottu: u mad?
[18:30] <apachelogger> shadeslayer: http://manpages.ubuntu.com/manpages/precise/en/man1/dh_install.1.html
[18:30] <shadeslayer> looking
[18:30] <shadeslayer> <3 krunner
[18:30] <apachelogger> one would think you know which component processes the install files so you can look at the manual when apachelogger instructs you to rtfm :P
[18:31] <shadeslayer> apachelogger: man page lists debian/package.install under Files
[18:31] <shadeslayer> :P
[18:31] <shadeslayer> nothing about debian/install
[18:32] <shadeslayer> and yeah, I know about dh_install, but thought the debian policy would probably give me better details about this file
[18:33] <apachelogger> well
[18:34] <apachelogger> let's bring the thougth a step further
[18:34] <yofel> I thought so, but it seems it doesn't, as the install files are specific to debhelper
[18:34] <apachelogger> if you have only one package
[18:34] <apachelogger> do you need an install file
[18:34] <apachelogger> muahhahaa
[18:34] <shadeslayer> not really I guess
[18:38] <yofel> well, undocumented feature it seems
[18:39] <yofel> now where was I..
[18:39] <shadeslayer> indeed
[18:39] <yofel> ah, rekonq
[18:40] <shadeslayer> go go yofel
[18:40]  * shadeslayer needs to finish off this test
[18:40] <apachelogger> yofel: oh, btw, I am reasonable certain the maintainer guide would explain debian/install
[18:40] <Kurdistan> :) this channel is to active to be a dev channel. :P
[18:40] <Kurdistan> (its good)
[18:40] <apachelogger> IIRC that guide has a fairly complete list of all common files one can find in debian/
[18:41] <apachelogger> even the not so common ones (emacs anyone? S:)
[18:41] <yofel> Kurdistan: well, this is -dev, -dev-discuss, -dev-OT, -dev-look-out-of-the-window-to-see-blue-ponies, ...
[18:41] <shadeslayer> don't forget -dev-apachelogger-loves-nakid-pics
[18:42] <Kurdistan> yofel, I am impresed. thats why I comment.
[18:42] <Kurdistan> other dev channel people are sleeping
[18:42] <yofel> well, we're less than a week before feature freeze. The channel has it's quiet times too
[18:42] <yofel> *its
[18:43] <Kurdistan> yofel, how is it going 12.04?
[18:43] <yofel> so far, nice
[18:43] <apachelogger> yofel: yeah quite times between 6 and 10 utc :P
[18:44] <yofel> ^^
[18:48] <Kurdistan> is it important that we need to follow 6 month release cycle?
[18:48] <Kurdistan> can we not release a version when the team feels it is good enough
[18:52] <shadeslayer> Kurdistan: now that we are a community supported distro we can
[18:52] <shadeslayer> but it's always better to follow the Ubuntu cycle
[18:52] <Kurdistan> shadeslayer, thats good. 
[18:52] <shadeslayer> iirc edubuntu has it's own cycle
[18:52] <Kurdistan> shadeslayer, I mean to release when its ready.
[18:53] <Kurdistan> shadeslayer, I do not care much about ubuntu cycle.
[18:53] <shadeslayer> righto
[18:53] <Kurdistan> I think even 1 week later can be positive for stable for our users
[18:54] <Kurdistan> I normally recommend people to install new buntu release 1 month after the release
[18:54] <Kurdistan> atlest
[19:00] <yofel> why, just why are we running KDE 4.8.00? (what's up with the double-0?)
[19:01] <yofel> probably the reason why it looks broken on the about page too
[19:01] <shadeslayer> yeah
[19:01] <shadeslayer> typo :P
[19:02] <yofel> ah well, 4.8.1 is in sight, so nvm
[19:03] <yofel> now, let's see if rekonq got any less broken
[19:04] <yofel> nope, although that's qtwebkit's fault
[19:08] <Kurdistan> yofel, it is still time to 4.8.1
[19:08] <rbelem> shadeslayer, Kurdistan, but to release at any time some packages would not go to the repos
[19:08] <Kurdistan> or am I wrong?
[19:08] <rbelem> would we use ppa?
[19:08] <yofel> well, 2 weeks IIRC, near enough
[19:08] <Kurdistan> rbelem, which package?
[19:08] <rbelem> Kurdistan, any package maintained by kubuntu
[19:09] <shadeslayer> rbelem: huh? I mean, you can easily get stuff into universe right?
[19:09] <yofel> rekonq up
[19:09] <shadeslayer> yofel++
[19:10] <Kurdistan> yofel, we will have it in backports when?
[19:11] <rbelem> shadeslayer, but not following the ubuntu release cycle we could not upload apcakges to the respos after some time, right?
[19:11] <yofel> Kurdistan: realase date or shortly after that
[19:11] <yofel> well, probably
[19:11] <yofel> well, I believe rbelem's right, so I don't think it's worth the hassle
[19:11] <shadeslayer> rbelem: not sure, I mean, we can surely release a couple of days later in order to fix critical bugs
[19:11] <yofel> except maybe delay release for a week if we need to fix stuff
[19:12] <Kurdistan> yofel, thats fast.
[19:12] <shadeslayer> I think what Kurdistan is trying to say is that we can now delay the release by a couple of days if we see show stopper bugs
[19:12] <yofel> Kurdistan: there's not much to do, just build and Q/A
[19:13] <Kurdistan> shadeslayer, exactly.
[19:13] <yofel> well, it's easy if you know what you do
[19:13]  * shadeslayer hates g_thread_new
[19:13]  * yofel hates any kind of object oriented naming in C
[19:14] <Kurdistan> it feels sometime ubuntu and other in buntu family hurry up to finish thing to release date
[19:14] <yofel> Kurdistan: we have more testing time for the LTS, but usually you're right
[19:14] <yofel> I remember being overworked in the days before oneiric final freeze
[19:15] <Kurdistan> I hope Kubuntu decided to release Kubuntu when critical bugs are fixed
[19:15] <Kurdistan> even if ubuntu have released
[19:16] <yofel> well, until now, we didn't have a choice
[19:16] <Kurdistan> that gives more time to all of kubuntu-dev
[19:16] <Kurdistan> yofel, yeah I know, but we can do that now. right?
[19:16] <yofel> probably, I'll tell you in half a year :P
[19:17] <Kurdistan> yofel, :( forgott thats after 12.04.
[19:20] <yofel> nah, for 12.04 the testing time is long enough 
[19:20] <yofel> so I think we'll have enough time
[19:25] <shadeslayer> yay
[19:25] <shadeslayer> yofel: I just got your IM request
[19:25] <shadeslayer> :P
[19:25] <yofel> lol
[19:25] <schnelle> guys, plasma-nm still have broken buttons, this bug is fixed upstream. https://bugs.kde.org/show_bug.cgi?id=290964
[19:25] <shadeslayer> It was probably because of the daemon thing which was not there in the packages
[19:25] <schnelle> don't forget to update it ;)
[19:27]  * yofel can't say he's ever seen those artifacts
[19:28] <schnelle> yofel: i see it in oneiric with kde 4.8 and also in precise
[19:28] <yofel> probably theme specific, I use produkt
[19:28]  * yofel fires up a VM
[19:29] <schnelle> yofel: i see it with default theme, so it can't be a good thing ;)
[19:29] <yofel> agreed
[19:30] <schnelle> yofel: is it possible to update plasma-nm after fature freeze? 
[19:31] <yofel> bug fixes are allowed till final freeze
[19:31] <yofel> just no new features
[19:31] <yofel> (without good reason)
[19:31] <schnelle> i can poke lamarque to ask him when he will realese new version of plasma-nm
[19:31] <schnelle> he is online now
[19:31] <yofel> ah, confirmed
[19:32] <schnelle> yofel: bug is not present in kde 4.7
[19:32] <yofel> I'll cherry pick that in case he doesn't make it
[19:32] <schnelle> only in 4.8
[19:32] <yofel> well, we ship an new pnm with 4.8 too
[19:36] <schnelle> yofel: if we want new (next) release of pnm in precise, can we update it after feature freeze (sorry i don't understand feture freeze very well)
[19:36] <yofel> sure, if it has only bugfixes
 hi lamarque. are you planing to release new version of plasma-nm soon? 
 no. I am busy at work and trying to fix some crashes before the release.
[19:43] <Kurdistan> schnelle, are you responsible for plasma-nm package?
[19:43] <schnelle> no :)
[19:45] <schnelle> yofel: he'll probably doesn't make it. don't forget to cherry pick that (now i am going to google what "cherry picking" exacly means :)
[19:46] <schnelle> *he probably won't make it
[19:46] <yofel> well, really just: pick one commit out of a bowl full of commits
[21:28] <apachelogger> halp, I had too much too eat
[21:28] <apachelogger> waaah
[21:29] <apachelogger> [kubuntu-members] ditch kaccessible: TODO
[21:29] <apachelogger> someone plz explain
[21:29] <apachelogger> rbelem: is active foo in the archive yet?
[21:36] <yofel> apachelogger: so, what's the status of dragon3?
[21:37] <apachelogger> sleeping
[21:38] <Daskreech> There be dragons?
[22:00] <jussi> Daskreech: no... Here be dragons...
[22:03] <Daskreech> jussi: Umm I forgot umm my lunch ... 
[22:03] <Daskreech> brb <_<
[22:05] <rbelem> apachelogger, i'm testing it currently
[22:05] <rbelem> apachelogger, i think i will upload it tomorrow
[22:28] <OffToHades> lemme just check, can anyone actually see me this time?
[22:40] <Riddell> oh well
[22:46] <Kurdistan> update of network manager (backport)
[22:46] <Kurdistan> what is the fix?
[22:46] <yofel> the buttons that schnelle talked about
[22:47] <Kurdistan> yofel, have you the log?
[22:48] <yofel> Kurdistan: http://irclogs.ubuntu.com/2012/02/11/%23kubuntu-devel.html#t19:25
[22:52] <Kurdistan> yofel, thx.
[22:52] <Kurdistan> yofel, you are a angel.
[22:52] <yofel> well, it *did* look bad
[23:43] <Riddell> Subject: [kde-packager] KDevelop 4.3 Beta 2 ready to be packaged 
[23:56] <BarkingFish> yofel: By the way, did you manage to ever fix xsettings-kde?
[23:56] <yofel> me not, but the fedora folks fixed it themselves, I just didn't noticed that hey had fixed it -.-
[23:56] <BarkingFish>  evening all :) sorry, wrong way round!
[23:56] <BarkingFish> any indication as to what was wrong?
[23:57] <Kurdistan> yofel, what did they ix?
[23:57] <Kurdistan> *fix
[23:57] <yofel> BarkingFish: http://pkgs.fedoraproject.org/gitweb/?p=xsettings-kde.git;a=summary - last commit is fixing the patch
[23:58] <Kurdistan> yofel, is the xsetting fixed?
[23:58] <yofel> it is
[23:58] <BarkingFish> ah :)  I'll have a peek when I can get on the net, connection is so slow that if I go to the web, i'll ping out on IRC :)
[23:58] <Kurdistan> yofel, nice. kde-gtk-config :) is not needed then?
[23:59] <BarkingFish> the snow here is playing hell with wifi. I'm picking up signals from 2 streets away, but can't get a decent connection to a beacon 10 metres from my front door :P
[23:59] <yofel> Kurdistan: not for now, we'll probably get it from debian next release. xsettings is a bit friendlier to other desktop envs