[00:35] <skaet> Riddell, ScottK - images for Kubuntu are now up on the beta 1 tracker.   http://iso.qa.ubuntu.com/qatracker/milestones/302/builds.   
[00:35] <skaet> hmm... just notice the back scroll,   sorry for the chatter.
[00:36] <skaet> On a separate but related noted,   https://wiki.ubuntu.com/SaucySalamander/Beta1/Kubuntu is available for your input now.
[07:40] <Riddell> sweet, we made slashdot :)
[07:41] <lordievader> Whoo, nice :D
[07:48] <Riddell> a random e-mailer points out a launchpad milestone I had failed to notice "WTG on breaking the 100k karma point barrier dude."  my day just gets better and better
[08:08] <smartboyhw> Hmm, the topic is TOO long
[08:17] <yofel> removed Alpha2 and 12.04.3 notes
[08:18] <smartboyhw> !testers | http://iso.qa.ubuntu.com/qatracker/milestones/302/builds
[08:23] <lordievader> smartboyhw: I'm already on it, testing amd64
[08:24] <smartboyhw> lordievader, good
[08:48] <Crumble__> hello all!  I apologize if I am not allowed to be here... but i need some help.  It is in regards to a linux mce install.  and a very strange df -h output. any help is appreciated.
[08:57] <lordievader> Crumble__: User support for Kubuntu is in #kubuntu.
[08:57] <Crumble__> thankyou lordievader  :)  have a good one
[08:57] <lordievader> Oem install still has problems... 
[09:04] <soee> test 13.10 beta 1 ?
[09:04] <smartboyhw> Riddell, you want to enable the upgrade tests or not?
[09:04] <soee> im running saucy at home, except i have 2 NM widgets all is fine :)
[09:04] <smartboyhw> soee, we mean fresh install
[09:04] <smartboyhw> lordievader, ouch 
[09:04] <smartboyhw> What problems?
[09:05] <smartboyhw> (We won't be respinning for OEM install problems I think BTW)
[09:05] <soee> smartboyhw, ok ill test in on VM at gome
[09:05] <soee> *home
[09:05] <smartboyhw> soee, great.
[09:05] <smartboyhw> Do the i386 might be good, since lordievader is doing amd64
[09:06] <kubotu> ::workspace-bugs:: [1206371] kwin is not starting: cannot find libwayland-egl.so.1 @ https://bugs.launchpad.net/bugs/1206371 (by Chupligin Sergey)
[09:07] <soee> can i do i386 on VM running in amd64 ?
[09:07] <smartboyhw> soee, yes
[09:07] <smartboyhw> Not the opposite though:P
[09:07] <soee> ok so np
[09:21] <Riddell> sigh, ubiquity broken on arm bug 1220139
[09:22] <Riddell> smartboyhw: yeah we should test upgrades
[09:22] <smartboyhw> Riddell, please add the testcases yourself:P
[09:25] <Riddell> ScottK: re bug 1220139 there's no known problem with pyqt/sip is there? I thought it was only pykde that had an issue
[09:25] <Riddell> everything else pyqt worked
[09:25] <Riddell> bug 1220139
[09:25] <Riddell> humph, well I made it public now
[09:26] <smartboyhw> Bug 1220139
[09:34] <lordievader> smartboyhw: They are minor, #1154535, #1204524
[09:34] <smartboyhw> Bug 1154535
[09:34] <smartboyhw> Bug 1204524
[09:35] <smartboyhw> lordievader, OK
[09:35] <lordievader> err that ^
[10:14] <mck182_> how the heck is it possible that regular package updates remove kde-window-manager package?
[10:15] <smartboyhw> mck182_, -.-
[10:15] <smartboyhw> What packages are you updating?
[10:15] <mck182_> just got returned a laptop with "unable to move windows"...apparently the user just installed offered updates to kde 4.11
[10:16] <mck182_> somehow that removed kwin
[10:16] <mck182_> that should just never ever happen :S
[10:20] <debfx> a bit hard to tell without sources.list{,d/*} and apt logs
[11:07] <Riddell> mck182_: the only thing I can think of that might cause that is if they have an obscure kwin theme installed which is incompatible with 4.11, we did recompile all the ones we could which are in the archive, but you're right it's not a good experience
[11:07] <Riddell> thanks for your testing lordievader 
[11:07] <lordievader> No problem, Riddell :)
[11:20] <yofel> mck182_, Riddell: another thing is a weird issue I've seen with the mesa backports in precise. E.g. if you have the quantal backports installed and kde 4.10  then the upgrade to 4.11 can in some circumstances kill kde-window-manager.
[11:20] <yofel> the dependency resolver is rather strange when it comes to alternate deps and deciding what to install
[11:20] <mck182_> yofel: that might be what happened
[11:20] <Riddell> agateau: meh wireless ubiquity module causes crash when in ubiquity only mode bug 1220193
[11:37] <Riddell> lordievader: did you try oem?
[11:38] <Riddell> I just did it and keeps the oem user but also keeps auto login as owm user which is just confusing
[11:45] <Riddell> ah I already commented as much on bug 1204524
[11:48] <Riddell> yuck rekonq is crashy :(
[11:50] <Riddell> bug 1219695
[11:51] <Riddell> do we (release team) let it in?
[11:55] <Riddell> agateau: another issue I think I found on wireless bug 1220212 probably easy to fix this one
[11:56] <xnox> Riddell: that's chicken & egg problem, the solution is to move wireless step before "prepare" screen, that hasn't been done in the gtk_ui yet.
[11:57] <Riddell> xnox: aah good to know we're not alone :)
[12:01] <lordievader> Riddell: Jup got exactly the same on the oem test.
[12:03] <BluesKaj> Howdy folks
[12:04] <Riddell> hi BluesKaj, able to do any beta testing?
[12:04] <xnox> Riddell: where is qt.conf on Ubuntu ?
[12:05] <BluesKaj> Riddell:  maybe , what's up ?
[12:05] <Riddell> xnox: I have a ~/.config/Trolltech.conf
[12:05] <Riddell> xnox: I'd guess qt.conf is the qt5 equivalent but I'm not sure
[12:05] <Riddell> BluesKaj: beta 1 candidates need testing
[12:06] <Riddell> http://iso.qa.ubuntu.com/qatracker/milestones/302/builds
[12:06] <xnox> Riddell: ":/qt/etc/qt.conf using the resource system"
[12:06] <xnox> what's the resource system on linux ?! =)
[12:08] <xnox> Riddell: i've straced it to find out =)
[12:08] <BluesKaj> Riddell: I'm running kubuntu13.10 , and currently I'm fooling with ubuntu/unity ... I'll switch over and dist-upgrade 
[12:09] <BluesKaj> Riddell:  or are you looking for ppl to install the beta image ?
[12:11] <Riddell> BluesKaj: yes install the candidate images or upgrade from raring
[12:12] <Riddell> xnox: I'd guess it's the file system :)
[12:12] <BluesKaj> I haave kubuntu 13.10 and ubuntu 13.10 on separate partitions already, Riddell
[12:13] <BluesKaj> ok will try the new beta image 
[12:13] <Riddell> BluesKaj: a reinstall doesn't hurt :)
[12:16] <BluesKaj> Riddell:  np , I'll install the image to /
[12:37] <Mirv> I wonder if yofel or someone would be interested in merging latest pkg-kde-tools changes (well, one commit + version number bump) from Debian, or shall I do that? it'd be needed so that qtscript-opensource-src could be synced directly from Debian instead of patching the build dependency
[12:37] <yofel> don't count on me until next week, but go ahead if you want to do it
[12:38] <Riddell> Mirv: I can look at it, is it in the FFe?
[12:38] <Mirv> ok, I can do/prepare that if no-one else does, just a heads-up. it was added to the Qt 5.1.1 FFe bug #1219695
[12:38] <Mirv> Riddell: now it is yes, as Scott asked for it
[12:39] <Mirv> Riddell: thanks. although it can't be uploaded before the FFe is formally accepted, but it'd be nice to have that ready.
[12:39] <Riddell> Mirv: well I can accept that too since you did ask nicely
[12:41] <Mirv> Riddell: heh, that's fine as well
[13:08] <Riddell> Mirv: voila
[13:08] <Mirv> \o/
[13:08] <Riddell> Mirv: some new source packages in there?
[13:13] <Mirv> Riddell: yes, four, they haven't been addressed separately in the text. adding a comment about those.
[13:59]  * Riddell blogs http://blogs.kde.org/2013/09/03/kubuntu-commercial-support
[14:02] <smartboyhw> Riddell, \o/
[14:04] <smartboyhw> Riddell, BTW I do suppose you know that you are the only active blogger on KDE Blogs that submits blog posts more than 3 times a month? :P
[14:06] <Riddell> I do feel a little guilty that kde sysadmins maintains it mostly for my benefit
[14:06] <smartboyhw> Riddell, if you make your own blog, then I'm going to file a sysadmin ticket to shut it down\o/
[14:09] <BluesKaj> Riddell:  got some errors on boot after the install seemed to work ok . After the error appears , there's no KB response at the shell prompt.Here's the error list: http://pastebin.com/6feJgQKJ
[14:10] <BluesKaj> I tried to install twice ..guess I'll have to install 13.04 again and release upgrade 
[14:11] <Riddell> BluesKaj: um yeah something very broken there
[14:11] <BluesKaj> ok , later
[14:44] <Riddell> hmm, upgrades on virtual machines are slow,I wonder if it's worth the effort compared to just bare metal
[15:25] <BluesKaj> ok, Riddell , solved the error and uuid recognition problemn with the beta1 install , I merely open an older kernel and rebooted , then the new install booted properly 
[15:28] <Riddell> um hmm that's not an ideal issue
[15:28] <Riddell> BluesKaj: do you think you have any hardware which the default kernel wouldn't like?
[15:31] <BluesKaj> Riddell, Idid have a previous problem with Ubiquity hanging and unable to move any further on Kubuntu 12.10 iirc ,and 13.04 . Also 13.10 alpha daily would do the same . I suspected HW recognition problems , but I could never track it down exactly
[15:33] <BluesKaj> this has been the first successful clean install from a live-cd since 12.04 due to the troubles above
[15:34] <Riddell> for some definition of successful
[15:34] <BluesKaj> anyway Riddell , I'm happy it worked out 
[15:35] <BluesKaj> ubuntu 13.10 installs ok tho , i have it on a separate partition
[15:36] <Riddell> BluesKaj: do you have a uefi laptop?
[15:36] <BluesKaj> no I'm running an older HP desktop
[15:37] <BluesKaj> with a couple of media pci cards in it
[16:34] <Arhi> hello
[16:37] <Arhi> Can I ask a question? Becouse i have problem with install
[16:40] <Arhi> huh...
[17:08] <shadeslayer> Arhi: #kubuntu for support
[18:17] <shadeslayer> !find /usr/lib/i386-linux-gnu/libpython2.7.so raring
[18:19] <shadeslayer> yofel: [  4%] make[4]: *** No rule to make target `/usr/lib/i386-linux-gnu/libpython2.7.so', needed by `lib/libcompoundviewer.so.4.11.1'.  Stop.
[18:20]  * yofel runs
[18:20] <shadeslayer> yofel: thoughts on explicitly adding libpython2.7-dev to kalzium build deps?
[18:20] <yofel> do that if it helps
[18:20] <shadeslayer> won't it help?
[18:20] <shadeslayer> why did amd64 build though
[18:20] <yofel> if that's the file it's looking for, it will
[18:20] <yofel> and the correct location
[18:21] <shadeslayer> why does amd64 pull in libpython2.7-dev
[18:21] <shadeslayer> :/
[18:28] <shadeslayer> yofel: we don't have a ppa:kubuntu-ppa/ninjas right?
[18:29] <yofel> we don't
[18:29] <shadeslayer> okay cool
[18:29] <shadeslayer> I uploaded to ppa:kubuntu-ppa/ninjas and didn't get a rejection email so far
[18:40] <shadeslayer> can someone atleast QA Saucy so that we can upload it?
[18:41] <shadeslayer> *QA KDE 4.11.1
[18:44] <soee> when Raring possible?
[18:44] <shadeslayer> soonish
[18:45] <shadeslayer> !find /usr/lib/libboost_python.so raring
[18:45] <shadeslayer> whut
[18:46] <shadeslayer> !find libboost_python.so raring
[18:46] <shadeslayer> o_o
[18:46] <tsimpson> !find libboost_python-py27.so
[18:47] <shadeslayer> ahh
[19:29]  * shadeslayer is compiling a patched kernel to fix his cable problems
[19:29]  * yofel wonders why everyone has kernel issues today
[19:32] <shadeslayer> not exactly
[19:32] <shadeslayer> I've been told that the cable might not be terminating the load correctly on one pin
[19:32] <shadeslayer> so I patched the kernel so that my mini DP always outputs TMDS mode
[19:32] <yofel> uh huh...
[19:33] <yofel> well, I guess that's better than me removing kernels to not hit the panics caused by bug 1220284
[19:33] <shadeslayer> yofel: http://paste.fedoraproject.org/36763/13782233/raw/
[19:33] <shadeslayer> ouch
[19:34] <shadeslayer> ofcourse, this patch doesn't really solve the problem, and I'll still have to get a replacement cable
[19:34] <shadeslayer> except now it's financially unfeasible to go to the place I got this cable from :P
[19:34] <yofel> heh
[19:35] <shadeslayer> cable cost me 2 EUR, cost of travel + time spent > 2 EUR
[19:35] <shadeslayer> so I'll just buy another one from a nearby vendor for a bit more cost
[19:38] <shadeslayer> hmm
[19:38] <shadeslayer> yofel: what do you recommend for kalzium
[19:38] <shadeslayer> adding those 2 python deps fixed it
[19:39] <yofel> well, for the backports just hack that into the hook IMO
[19:39] <yofel> or you'll have to backport avogadro
[19:39] <shadeslayer> I see
[19:39] <shadeslayer> korundum exhibits similar symptoms
[19:39] <shadeslayer> nepomuk-core-dev isn't pulled in
[19:40] <yofel> I think there it's kdepimlibs assuming nepomuk exists
[19:40] <shadeslayer> nope
[19:40] <shadeslayer> -- Skip KorundumModules bindings: Kate;Nepomuk
[19:40] <yofel> though I wonder why it would work in saucy
[19:40] <shadeslayer> and nepomuk-core-dev is pulled in in saucy
[19:41] <yofel> Setting up nepomuk-core-dev (4:4.11.1-0ubuntu1~ubuntu13.04~ppa1) ...
[19:41] <shadeslayer> yofel: can you take up korundum? I don't want to look at packaging right now
[19:41] <yofel> in raring too o.O
[19:41] <shadeslayer> oh
[19:42] <yofel> heh
[19:42] <yofel> oh lol
[19:42] <yofel> -- Could NOT find Nepomuk (missing:  SHAREDDESKTOPONTOLOGIES_FOUND) 
[19:42] <shadeslayer> pft
[19:42]  * shadeslayer goes about fixing his Qt patch
[19:43] <yofel> wait a second: shouldn't nepomuk kinda depend on sdo o.O?
[19:45] <yofel> hm, kde-runtime depends on it
[19:45] <yofel> I'll add it to nepomuk-core-dev depends anyway 
[21:40] <Riddell> http://www.eweek.com/developer/kubuntu-linux-emerges-from-ubuntus-shadow.html/
[23:01] <ronnoc> nice article, Riddell :)