[00:14] <apachelogger> Riddell: low fat settings has been axed btw
[00:14] <apachelogger> like a year ago
[00:14] <apachelogger> because MG was annoying me all day @pineda
[00:19] <soee> hmm what is this libkubuntu0 package that muon shows to be installed but it can not be ?
[00:35] <ahoneybun> soee firefox 27 was pushed to saucy
[00:38] <soee> ahoneybun: waiting for trusty :/
[00:38] <ahoneybun> oh
[00:42]  * mamarley wishes that the Ubuntu Mozilla Team people would put out the beta releases in their PPA in a more timely fashion :(
[01:13] <apachelogger> soee: it cannot be installed?
[01:14] <soee> apachelogger: muon shows stateus as "not installed" and request as "install" but if i apply vhanges it does nothing
[01:15] <soee> no error but package is not installed
[01:17] <apachelogger> meh
[01:17] <apachelogger> I won't get to bed today
[01:17] <apachelogger> soee: let me think of a way to debug that
[01:18] <apachelogger> soee: can you build muon yourself real quick?
[01:19] <soee> probably it will tage a little longer as i would have to install all dependencies to build a package (im after fresh install)
[01:19] <soee> lets do it tomorrow :)
[01:19] <apachelogger> soee: or maybe... do the following for starters.... killall qaptworker2; killall muon-updater; kdebugdialog ... then select all and apply
[01:20] <apachelogger> then start muon-updater from a terminal, hit ctrl-r to reload the cache and try to update
[01:20] <apachelogger> paste the output from the terminal
[01:22] <soee> its gone from the list
[01:23] <apachelogger> soee: does the update work?
[01:23] <soee> seems so http://pastebin.com/v2s8mdG8
[01:23] <apachelogger> muon-updater(30661) ApplicationUpdates::start: couldn't find any apt updates
[01:24] <apachelogger> soee: so it doesn't list any udpates at all?
[01:24] <soee> oen second
[01:24] <soee> muon-updater doesnt't show any, the package is listed in the muon thoug
[01:25] <apachelogger> ahhhhhhhhhhhh, now I get it
[01:25] <apachelogger> soee: so you try to install it via muon itself and that does not work?
[01:26] <soee> nope, it finishes updates but the package is listed as to be insalled always
[01:27] <soee> http://wstaw.org/w/2v2P/linki/
[01:27] <apachelogger> most peculiar
[01:29] <apachelogger> what I don't get though... why is it listed there at all
[01:29] <soee> noe idea :D
[01:29] <apachelogger> libkubuntu0 is a dependency of kde-runtime, so if the upgrade would install libkubuntu0 it would also have to upgrade kde-runtime
[01:29] <apachelogger> soee: what does apt-cache policy kde-runtime say?
[01:29] <soee> can i somehow clear cache of muon or something ?
[01:30] <apachelogger> you can close muon and reopen it :P
[01:30] <apachelogger> I am not sure that would change anything tho
[01:30] <soee> http://pastebin.com/C57vSiMb
[01:31] <apachelogger> this is the stranges thing in the world
[01:32] <soee> this show up like 2-3 days ago
[01:33] <apachelogger> actually
[01:34] <apachelogger> no, it all makes no sense :P
[01:34] <apachelogger> soee: somehow your qapt became incapable of listing updates
[01:35] <soee> oh? and others work just fine
[01:35] <apachelogger> soee: what's the output of sudo apt-get -s dist-upgrade
[01:36] <soee> http://pastebin.com/eVt3xpa7
[01:37] <apachelogger> right
[01:37] <apachelogger> not a qapt issue
[01:37] <apachelogger> phew
[01:37] <apachelogger> soee: your cache is busted
[01:37] <soee> :O
[01:37] <apachelogger> soee: cat /etc/apt/sources.list.d/*
[01:38] <apachelogger> (note how the dist-upgrade output makes no sense, it says libkubuntu0 is installed, but then goes on saying it needs to install libkubuntu0)
[01:38] <soee> http://pastebin.com/LF2USxLk
[01:39] <apachelogger> soee:  you may wan to at lreast remove the kubuntu-ppa entries in there
[01:39] <apachelogger> there's definitely not particularly save packages coming in from there
[01:39] <apachelogger> and xorg-edgers is always a gamble
[01:39] <apachelogger> soee: also what's apt-get check say?
[01:40] <apachelogger> also, sudo apt-get update && sudo apt-get install libkubuntu0
[01:40] <soee> http://pastebin.com/Zsm3rrFK
[01:42] <apachelogger> afk brushing teeth
[01:42] <apachelogger> soee: try the update install command, that might resolve the problem
[01:43] <soee> looks liek it installed it: http://pastebin.com/yPXxKqd6
[01:44] <soee> but now muon button Full Upgrade is active
[01:44] <soee> but if i click on it i have error message
[01:44] <soee> about unment deps
[01:45] <apachelogger> oh
[01:45] <apachelogger> well
[01:45] <apachelogger> first
[01:46] <apachelogger> soee: again  `sudo apt-get -s dist-upgrade`
[01:46] <soee> http://pastebin.com/dw4Xxdxv
[01:47] <apachelogger> soee: sudo apt-get install -s plasma-scriptengine-javascript
[01:47] <soee> ah ok so this previous package is fine now
[01:48] <apachelogger> yeah
[01:48] <apachelogger> my guess is that now some PPA is blocking the runtime stuff
[01:48] <apachelogger> s/runtime/scriptengine/
[01:48] <kubotu> apachelogger meant: "my guess is that now some PPA is blocking the scriptengine stuff"
[01:49] <soee> uhm to beig output ot pastebin i think ;/
[01:49] <soee> *big
[01:50] <soee> http://paste.ubuntu.com/6912493/
[01:53] <apachelogger> Inst plasma-scriptengine-javascript [4:4.12.2-0ubuntu1] (4:4.12.2+git20140210+bzr18249+pkg405~ubuntu14.04.1 Kubuntu Updates:14.04/trusty [amd64])
[01:53] <apachelogger> soee: the updates PPA has some issue
[01:53] <apachelogger> yofel: ^
[01:54] <apachelogger> soee: maybe wait
[01:54] <soee> sure
[01:54] <apachelogger> I guess yofel can find out why exactly it acts up
[01:55] <apachelogger> but basically upgrading that package would remove half the system which is why muon and dist-ugprade refuse to install it as an update
[01:55] <apachelogger> rightfully so
[01:55] <soee> yup, ok its not big issue for me, im happy that the problem with the first package is gone
[01:55] <apachelogger> soee: fwiw, if you feel like not using the bzr builds, you can apt pin origin Ubuntu with a higher priority forcing your system into official package versions
[01:56] <soee> thank you for your help apachelogger
[01:56] <apachelogger> I personally find it always a bit dangerous to use PPAs on the devel series
[01:56] <apachelogger> since sometimes things move so quick that brekage becomes a lot more likely with PPAs enabled ^^
[01:56] <apachelogger> and with that I am off to bed
[01:56] <apachelogger> nini
[01:57] <soee> thanks again
[06:41] <snele> guys I am using 14.04 for about 10 days now as my main/production system
[06:42] <snele> what I have noticied that muon updater never pops up to inform me about updates
[06:42] <snele> is this normal/expected for non-final release?
[07:01] <valorie> snele: I guess we are gathering feedback here: https://plus.google.com/107577785796696065138/posts/WxmRfrRTdKN
[07:02] <valorie> you are quite a gambler to be using an alpha release as your production system
[08:01] <jarkko_> The following packages have been kept back:
[08:01] <jarkko_>   usb-modeswitch-data
[09:52] <lordievader> Good morning.
[10:06] <apachelogger> valorie: feedback != bugs fwiw :P
[10:12]  * apachelogger actually wonders how shadeslayer blogged on monday but his blog says he blogged on sunday
[10:12] <apachelogger> such confusing
[10:28] <apachelogger> Riddell: kubuntu-meta migrated, ISOs are below size threshold again \o/
[10:30] <jarkko_> apachelogger: what's the size now?
[10:40] <apachelogger> <=1gib
[10:44] <apachelogger> shadeslayer: bug 1278814 
[10:44] <apachelogger> shadeslayer: bug 1278732
[10:44] <jarkko_> what's akonadi?
[10:49] <cortexA9> hello
[10:49] <apachelogger> shadeslayer: bug 1278816
[10:49] <apachelogger> hey cortexA9
[10:49] <cortexA9> hi apachelogger 
[10:50] <cortexA9> i have already that problem
[10:50] <cortexA9> at startup
[10:50] <cortexA9> boot only with 3.11 kernel
[10:50] <cortexA9> the others go on initramfs screen
[10:52] <cortexA9> apachelogger: is it a known issue?
[10:53] <apachelogger> can't confirm anyway
[10:53] <apachelogger>  ~  uname -a
[10:53] <apachelogger> Linux smith 3.13.0-8-generic #27-Ubuntu SMP Fri Feb 7 02:01:37 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[10:53] <apachelogger> cortexA9: whether it's known you'll have to ask the kernel guys
[11:31] <apachelogger> shadeslayer: bug 1278826
[11:34] <apachelogger> shadeslayer: bug 1278827
[11:37] <BluesKaj> 'Morning all
[11:50] <shadeslayer> apachelogger: thx
[11:51] <cortexA9> hi BluesKaj 
[11:52] <BluesKaj> hi cortexA9
[13:14] <jussi> do we even have an alternate cd anymore?= 
[13:15] <Peace-> jussi: alternate cd is not here from 1 2 release i guess 
[13:15] <Peace-> releases
[13:16] <jussi> Peace-: thats what I thought...
[13:16] <jussi> just that lordievader called !rescue before...
[13:16] <jussi> !rescue
[13:16] <jussi> does ubuntu have an alt cd ?
[13:16] <lordievader> I figured it would point to how to boot into the rescue mode, it didn't.
[13:17] <Peace-> jussi: i don't remember well but that option should be on normal cd 
[13:17] <Peace-> on ubuntu cd 
[13:17] <jussi> I dont think so...
[13:18] <Riddell> "There have been repeated failed attempts to gain access to a wallet. An application may be misbehaving."  should I be worried that plasma-nm can't talk to my kwallet suddenly?
[13:29]  * BluesKaj doesn't bother kwallet, it's a pita for home users like me, tuning it off solves a lot of annoyances
[14:00] <sgclark> Riddell: hopefully fixed dpic up
[14:05]  * Riddell takes a keek
[14:07] <Riddell> sgclark: looking lovely, uploaded to experimental PPA!
[14:08] <sgclark> thanks :) cirkuit coming soon
[14:36] <apachelogger> shadeslayer: btw, please try to make the touchpad blog post less technical ^^
[14:39] <shadeslayer> :S
[14:45] <apachelogger> Riddell, shadeslayer: I started appending stuff to https://wiki.ubuntu.com/TrustyTahr/Beta1/Kubuntu so we don't forget
[14:45] <Riddell> great
[14:51] <sgclark> phonon-backend-null_4.7.1-0ubuntu3_amd64.deb: Size mismatch what does this mean?
[14:52] <Riddell> sgclark: glitch in the matrix?
[14:52] <Riddell> try and apt-get update && apt-get install phonon-backend-null
[14:52] <sgclark> happening in pbuilder, updating now
[14:53] <sgclark> hrmm no help
[14:53] <Riddell> remove the cache?
[14:53] <Riddell> not sure how you do that with pbuilder
[14:54] <sgclark> ok
[14:54] <Riddell> rm /var/cache/pbuilder/aptcache/*
[14:54] <apachelogger> nah
[14:54] <apachelogger> apt-get clean
[14:54] <apachelogger> one does not delete the cache manually :P
[14:55] <Riddell> but how you run that for pbuilder?
[14:55] <Riddell> it doesn't use the normal apt cache
[14:55] <Riddell> pbuilder --clean  might help
[15:04] <sgclark> apt-get clean  did nthing, will try that
[15:06] <sgclark> nope, hmm
[15:07] <jarkko_> W: GPG error: http://fi.archive.ubuntu.com trusty Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
[15:11] <apachelogger> Riddell: usuallly pbuilder will share the apt cache unless explicitly told not to
[15:11] <apachelogger> so cleaning the host will clean it for pbuilder as well
[15:11] <Riddell> oh? so what is /var/cache/pbuilder/aptcache/ for?
[15:12] <apachelogger> hardlinks
[15:12] <apachelogger> that being said, if you were to use different partitions for the various caches it would also not be shared
[15:12] <apachelogger> shadeslayer: http://i.imgur.com/gzmL8ss.png can we get a screenshot there somehow?
[15:14] <shadeslayer> apachelogger: of what?
[15:16] <shadeslayer> apachelogger: I propose https://scontent-a-mxp.xx.fbcdn.net/hphotos-prn2/t1/p206x206/168621_192469560772608_4286474_n.jpg
[15:17] <apachelogger> better than the red thing for sure
[15:17] <apachelogger> shadeslayer: kdevelop or qt creator with some codez
[15:17] <apachelogger> or vim for all I care
[15:17] <apachelogger> something code anyway
[15:17] <shadeslayer> ack
[15:17] <apachelogger> or 
[15:17] <shadeslayer> snapshot of techbase
[15:17] <sgclark> cleaned host and pbuilder with  --autocleanaptcache fixed one phonon package but not another is broken. weird...
[15:18] <apachelogger> shadeslayer: ask apol whether we could simply make discover display the icon when no screnshot could be loaded
[15:18] <apachelogger> that would resolve this ugly red thing for most apps
[15:18] <shadeslayer> apachelogger: apol says that it's wrong to not have a screenshot
[15:19] <shadeslayer> we could just reuse the kdevelop screenshot?
[15:19] <apachelogger> if it is a nice one
[15:19] <apachelogger> just need something there, that red thing looks terribad
[15:20] <shadeslayer> add a card
[15:20] <shadeslayer> or report a bug
[15:20] <shadeslayer> and assign to me
[15:20] <apachelogger> report a card
[15:20] <shadeslayer> ^^
[15:20] <apachelogger> card a report
[15:20] <apachelogger> no wait
[15:20] <apachelogger> THIS IS SILLY
[15:20]  * apachelogger slaps shadeslayer with a fish and bugs a card
[15:21] <apachelogger> also one wonders why that package is 46k
[15:21] <apachelogger> much confusion has been had
[15:22] <kubotu> ::workspace-bugs:: [1278912] Wrong graph legend for network manager @ https://bugs.launchpad.net/bugs/1278912 (by Hồng Quân)
[15:23] <apachelogger> Size: 2764
[15:23] <apachelogger> very peculiar how disocver gets that value
[15:23] <apachelogger> oh well
[15:23]  * apachelogger quickly forgets about it again before this ends in a bug hunt
[15:36]  * apachelogger afk
[15:46] <shadeslayer> apachelogger: where do I leave comments about policy?
[15:47] <Riddell> e-mail? here? edit the wiki?
[15:48] <shadeslayer> Riddell: apachelogger http://paste.kde.org/pycfeqxpt
[15:51] <shadeslayer> Riddell: can you upload tomahawk for me
[15:51] <shadeslayer> link to dsc coming up in 5 minutes
[15:52] <apachelogger> shadeslayer: it's a wiki plz apply random fixer00 :P
[15:53] <apachelogger> shadeslayer: Whenever upstream does not approve of a patch on the basis of technical problems, it must not be included or must be removed. There is no exception to this rule. 
[15:53] <Riddell> hmm, that seems quite unflexible
[15:54] <apachelogger> that's the point of it
[15:54] <shadeslayer> Riddell: https://launchpad.net/~rohangarg/+archive/kde-extra/+files/tomahawk_0.7.0%2Bdfsg1-0ubuntu1%7Eppa1.dsc
[15:54] <shadeslayer> apachelogger: sure, I understand that, but we've broken that policy before
[15:54] <apachelogger> becaue if you patch shit and upstream does not agree then you are effectively forking the upstream software
[15:54] <Riddell> sometimes upstream can be wrong?
[15:54] <apachelogger> shadeslayer: the present version of the maverick policy was never approved I think
[15:55] <apachelogger> Riddell: then you are to fork the upstream software
[15:55] <apachelogger> or convince upstream of their wrongful ways
[15:56] <Riddell> ooh ahoneybun getting into packaging?
[15:56] <Riddell> shadeslayer: these are the same items or separate?   * Update copyright file a bit * Add LGPL-2.1 license
[15:56] <shadeslayer> Riddell: separate
[15:57] <shadeslayer> Riddell: complete copy of the license was missing
[15:57] <shadeslayer> so I added it
[15:57] <shadeslayer> apachelogger: right, we had a policy in theory, just not written down that we don't ship patches unless approved by upstream
[15:57] <shadeslayer> apachelogger: yet we shipped the kwallet patch
[15:57] <apachelogger> it was written down
[15:57] <shadeslayer> when upstream had a differing opinion
[15:57] <apachelogger> it was not approved
[15:57] <shadeslayer> apachelogger: fine, my point remains
[15:57] <apachelogger> effectively we did not have a policy
[15:57] <apachelogger> shadeslayer: yes, and doing that caused tention with upstream developers
[15:58] <shadeslayer> right so even if upstream differs in opinion we don't ship said patch?
[15:58] <apachelogger> which is why the rewrite of the policy is as undynamic as it is (the previous version also wasn't exactly flexible ^^)
[15:58] <apachelogger> shadeslayer: exactly
[15:58] <apachelogger> or you official fork upstream
[15:58] <apachelogger> making yourself upstream
[15:58] <shadeslayer> apachelogger: does that mean post new policy we remove the kwallet patch then ?
[15:59] <apachelogger> which will also create social problems but if there is technical failure I get to call people names
[15:59] <apachelogger> shadeslayer: yes, I thought we had done that already?
[15:59] <shadeslayer> we have? 
[16:00] <apachelogger> last fortnight QA yielded kwallet init dialogs
[16:00] <apachelogger> (and IIRC the dialog actually defaulted to gpg which was a bit odd in itself ^^)
[16:00] <shadeslayer> ack
[16:00] <shadeslayer> cool then, but I'd clarify in policy tbh
[16:00] <apachelogger> Whenever upstream does not approve of a patch on the basis of technical problems, it must not be included or must be removed. There is no exception to this rule. 
[16:01] <apachelogger> I think that's pretty clear? :P
[16:01] <shadeslayer> apachelogger: what about a difference of opinion on how said upstream software should behave 
[16:01] <apachelogger> Whenever upstream does not approve of a patch on the basis of technical problems, it must not be included or must be removed. There is no exception to this rule. 
[16:01] <apachelogger> note that last sentence
[16:01] <shadeslayer> I see
[16:01] <shadeslayer> ok
[16:02] <shadeslayer> apachelogger: - Clarify if software in Extragear and scratch repos counts as official KDE Software
[16:02] <shadeslayer> anything on the KDE infra counts as KDE Software?
[16:03] <apachelogger> I would rather think so, yes
[16:03] <Riddell> any software which comes from KDE
[16:03] <apachelogger> only kde related nonsense ought to go there
[16:03] <Riddell> which could be outside the kde infrastructure according to the manifesto (but not anything so far)
[16:04] <shadeslayer> alright, what happened to Patch type C?
[16:04] <apachelogger> so everything on kde infra is nonsenese related to KDE, thus KDE may feel responsible or not
[16:04] <apachelogger> if they do, then hooray, if not then oh well
[16:04] <apachelogger> shadeslayer: what do you mean?
[16:04] <apachelogger> ah
[16:04] <apachelogger> shadeslayer: type d is d because of DANGER
[16:04] <apachelogger> xD
[16:05] <apachelogger> quite literally when I read the old policy again the first thing that popped to mind when reading that last patch type description was a danger sign with a godzillion exclamation marks ^^
[16:07] <apachelogger> Riddell: yeah, of course that part of the manifesto makes it impossibru to generally identify such software, so I think if we just hold on to either hosted on git.kde or using bugs.kde we have a pretty good ruleset for identification
[16:08] <apachelogger> which would also have covered amarok during the git migration through gitorious as bugs were still handled on bugs.kde
[16:08] <apachelogger> equally kaffeine I think was developed on sf.net but bugs on kde
[16:09] <Riddell> Quintasan: fancy packaging ktp 0.7.1 ?
[16:09] <Quintasan> Riddell: How long till Freeze? I might want to get it into Debian if it's not there.
[16:10] <Riddell> um, no rush I think
[16:10] <Quintasan> Riddell: I'll start working on it then
[16:10] <shadeslayer> Quintasan: it's packaged
[16:10] <shadeslayer> I haven't QA'd it 
[16:11] <Quintasan> eh
[16:11] <Quintasan> shadeslayer: for Ubuntu or Debian?
[16:11] <shadeslayer> youboontoo
[16:11] <shadeslayer> https://launchpad.net/~rohangarg/+archive/nightly?field.series_filter=trusty
[16:11] <Riddell> ooh groovy
[16:12] <shadeslayer> if anyone wants to, plz test and upload ^^
[16:13] <Riddell> Quintasan: can you test?
[16:14] <Quintasan> Riddell: Certainly
[16:14] <Quintasan> shadeslayer: How about you do that for Debian and poke me or detrout so we can just sync in then
[16:14] <shadeslayer> Riddell: how do I revert a part of a pushed commit?
[16:14] <shadeslayer> Quintasan: ENOTIME today
[16:14] <shadeslayer> Riddell: in bzr ofcourse
[16:14] <Quintasan> shadeslayer: I'm talking about future occurences
[16:14] <shadeslayer> Quintasan: sure
[16:15] <Quintasan> Splendid.
[16:15] <Riddell> shadeslayer: bzr uncommit  (can't do part as far as I know)
[16:18] <shadeslayer> ffffuuuuu
[16:18] <shadeslayer> https://launchpadlibrarian.net/165569934/buildlog_ubuntu-precise-amd64.cmake_2.8.12.2-0ubuntu1~ubuntu12.04.1~ppa1_FAILEDTOBUILD.txt.gz
[16:20] <Riddell> why are you building cmake for precise?
[16:20] <shadeslayer> Riddell: kde-workspace won't build without cmake from trusty
[16:21] <Riddell> hmm gosh
[16:22] <shadeslayer> Riddell: FWIW I'm doing KF5
[16:22] <shadeslayer> possibly using scripts
[16:23] <shadeslayer> lets see how that goes
[16:23] <Riddell> shadeslayer: alpha 1?  awesomeness
[16:23] <shadeslayer> yeah
[16:23] <Riddell> adapting the kubuntu-automation script would seem the way to go
[16:23] <shadeslayer> *nod*
[16:24] <kubotu> ::workspace-bugs:: [1278912] Wrong graph legend for network manager @ https://bugs.launchpad.net/bugs/1278912 (by Hồng Quân)
[16:57] <shadeslayer> Riddell: I don't reckon you have a mapping of KDE source names to Kubuntu source names
[17:04] <shadeslayer> yofel: ping
[17:04] <Riddell> shadeslayer: for kf5? they should all be the same except attica
[17:04] <shadeslayer> okay
[17:05] <sgclark> Riddell: http://paste.ubuntu.com/6916031/
[17:06] <Riddell> sgclark: tsk clashing files, that can just be renamed at install time
[17:06] <shadeslayer> Riddell: do you have a clue how bzr-buildpackage works?
[17:07] <shadeslayer> i.e. where it looks for the orig tarball
[17:07] <Riddell> shadeslayer: it works multiple ways and looks in multiple places for the orig tar
[17:07] <shadeslayer> Riddell: locally?
[17:07] <Riddell> yes locally first, and in the bzr branch for UDD branches, then it'll fall back on debian/watch I think
[17:07] <shadeslayer> right, but where locally
[17:07] <Riddell> locally it just looks in .. I think
[17:08] <Riddell> it'll also try to apt-get source
[17:08] <soee> shadeslayer: if you try to refresh list of drivers in kubuntu-driver-manager whole system settings app crashes :)
[17:08] <shadeslayer> soee: yeah known issue
[17:09] <soee> ah  ok :) anyway looks nice so far
[17:09] <shadeslayer> soee: only when you hit it twice though right?
[17:09] <sgclark> Riddell: patch the source or is there a way to rename in debian files?
[17:09] <soee> shadeslayer: ee i run it first time it fetched list of drivers, i clicked to refresch and crash
[17:09] <shadeslayer> mmm that's pretty bad
[17:09] <shadeslayer> weird how it worked when I released it >.>
[17:10] <shadeslayer> soee: I have a backtrace, I need to rework large parts and update
[17:10] <soee> shadeslayer: it will land by default in 14.04 ?
[17:10] <shadeslayer> yep
[17:10] <soee> ok, nice
[17:10] <Riddell> sgclark: I think I'd do it by overriding the install rule and mv the file before running dh_install
[17:12] <sgclark> ok
[17:12] <soee> i have also some new entry in sys-settings called Diagnostic
[17:12] <soee> is it also new ?
[17:14] <shadeslayer> soee: yep
[17:21] <Riddell> agateau: well my attempts to remaster an image with your ubiquity patches on it have failed to got something I can boot my computer from, works ok on a virtual machine but it doesn't run the first pre-login screen
[17:21] <Riddell> I can't find any logs to say that it's even trying so it might just be my remastering that's broken
[17:22] <Riddell> currently I'm thinking it'll be easiest to just upload it and see what breaks
[17:22] <Riddell> oem installer still works and with a nice background now
[17:22] <Riddell> new partition bar is pretty but could do with some more testage
[17:24] <shadeslayer> Riddell: you might want to start working on attica
[17:25] <shadeslayer> Riddell: patches fail to apply
[17:25] <shadeslayer> same for frameworkintegration
[17:28] <Riddell> pourquoi moi?
[17:28] <Riddell> shadeslayer: you can just remove both patched
[17:28] <Riddell> I sent them upstream
[17:28] <shadeslayer> kapidox.install is empty?
[17:29] <Riddell> it's a 1 .deb package I think
[17:29] <Riddell> not needed
[17:29] <Riddell> frameworkintegration fix_icons_path.diff can go, I think the other patch is still needed
[17:29] <shadeslayer> I'm saying that you have a debian/kapidox.install :)
[17:30] <Riddell> yes, you can just remove it
[17:33] <shadeslayer> Riddell: was Rename-CheckXML-to-resolve-conflict.diff forwarded?
[17:35] <Riddell> shadeslayer: yep
[17:36] <shadeslayer> Riddell: Rename-manpages-to-resolve-conflict-with-kde4.diff ?
[17:37] <Riddell> shadeslayer: also upstream
[17:40] <soee> 14.04 will use lightdm? There were some rumors that it will be replaced (maybe when KF5 shows up)?
[17:41] <Riddell> it won't be replaced in 14.04
[17:41] <Riddell> we hope to go with whatever upstream chooses after that, SDDM is the competition
[17:41] <cortexA9> Riddell: hello :)
[17:41] <Riddell> hi cortexA9 
[17:41] <soee> Riddell: ok good to know
[17:44] <shadeslayer> Riddell: rename_dbus.diff in Solid?
[17:44] <sgclark> Riddell: cirkuit ready
[17:44] <Riddell> sgclark: upstream
[17:44] <Riddell> no
[17:44] <Riddell> shadeslayer: upstream
[17:44] <sgclark> ?
[17:44] <sgclark> ok
[17:45] <Riddell> sgclark: will look in a sec
[17:47] <shadeslayer> Riddell: no-install-dbus-interfaces.diff for kglobalaccel?
[17:47] <Riddell> shadeslayer: upstreamed
[17:47] <Riddell> they've all been upstreamed, I've been a good boy :)
[17:47] <shadeslayer> oh, so drop all patches then?
[17:47] <Riddell> hmm well maybe the kauth ones were after the alpha
[17:48] <shadeslayer> Riddell: I belive upstreamed too
[17:56] <shadeslayer> Riddell: plz have a look at attica
[17:56] <shadeslayer> I am unsure about those patches
[17:56] <Riddell> shadeslayer: they've both gone upstream
[17:57] <shadeslayer> same for kio?
[17:59] <Riddell> shadeslayer: yep
[17:59] <yofel> shadeslayer: pong?
[18:00] <Riddell> sgclark: comments http://paste.kde.org/pzjwo5bpd
[18:00] <shadeslayer> yofel: nvm
[18:00] <yofel> k
[18:04] <sgclark> Riddell: package name does not match so-name is reason to split. putting executable in lib package seemed wrong
[18:05] <shadeslayer> Riddell: uploading first set of packages
[18:05] <shadeslayer> Riddell: still need to work through a few of them
[18:06] <sgclark> Riddell: it would not build without dpic
[18:07] <sgclark> Riddell: scratch last one
[18:08] <sgclark> Riddell: lost me on #9, I never saw that
[18:13] <shadeslayer> Riddell: all of these need to be done
[18:13] <shadeslayer> http://paste.kde.org/psafkbfir
[18:13] <shadeslayer> I have to stop since the alloted time for KF5 is done :)
[18:17]  * Riddell wonders when shadeslayer became such a slave to schedule
[18:18] <Riddell> sgclark: line 9 is what I get when first running it
[18:18] <Riddell> rm ~/.kde/share/apps/cirkuit and run again and you should get it
[18:18] <Riddell> I think that's just how the program works but seems like a strange way to work
[18:19] <sgclark> ok I get it, but I don't know what I can do to fix it
[18:19] <Riddell> sgclark: if it needs dpic to build then keep it in build-deps but also add it to Depends for the .deb package
[18:19] <shadeslayer> Riddell: ever since I realized I had no life outside of work because I spent way too much time doing the small things :)
[18:19] <Riddell> sgclark: no fix needed, if that's what upstream wants that's what upstream will get
[18:19]  * yofel passes shadeslayer a cup of coffee
[18:19] <sgclark> will fix dpic, you were right not needed for build
[18:19] <Riddell> sgclark: can you get the programme to do anything useful?
[18:20] <shadeslayer> :)
[18:20] <sgclark> Riddell: I don't know how to build circuits 
[18:21] <Riddell> circuits?
[18:21] <sgclark> Riddell: that is what this program is for, printed circuit board creation
[18:21] <Riddell> oh you mean the real ones you model in citkuit :)
[18:21] <sgclark> right lol
[18:22] <sgclark> it seems examples are not installed though, hmm
[18:23] <Riddell> but you can download them
[18:23] <Riddell> when I try one it complains about missing a file in texlive-latex-extra, installing
[18:23] <Riddell> only 300MB
[18:31] <sgclark> Riddell: fixed dpic to depend on runtime. in ubuntu one. 
[18:32] <sgclark> I am sure folks that actually build circuits in programs like these would know how to make this program useful. I saw alot of praise on their website
[18:36] <Riddell> sgclark: hey if I install texlive-latex-extra then it begins to work
[18:37] <Riddell> so add that to the depends
[18:37] <sgclark> ok will do
[18:37] <Riddell> ooh pretty diagrams
[18:37] <Riddell> yes you do need to know what you're doing to use this programme I think
[18:37] <Riddell> but the examples are nice
[18:43] <shadeslayer> so man FTBFS's :)
[18:50] <sgclark> Riddell: that did the trick :) fixed uploaded
[18:51] <Riddell> sgclark: copyright still says LGPL
[18:51] <sgclark> oops
[18:57] <sgclark> Riddell: fixed uploaded
[19:00] <shadeslayer> Riddell: http://kshadeslayer.wordpress.com/?p=326&shareadraft=52fa7345203a7 < review plz
[19:01] <Riddell> sgclark: upstream lists a few more dependencies needed http://wwwu.uni-klu.ac.at/magostin/cirkuit.html
[19:02] <sgclark> Riddell: ok
[19:02] <Riddell> sgclark: can you try adding a watch file, upstream hasn't got a nice neat download page unfortunately but you should be able to point it at http://wwwu.uni-klu.ac.at/magostin/cirkuit.html for links
[19:04] <shadeslayer> apachelogger: ping
[19:06] <Riddell> shadeslayer: reads good
[19:07] <apachelogger> shadeslayer: pong
[19:07] <shadeslayer> Riddell: cheers
[19:07] <shadeslayer> apachelogger: halp
[19:07] <shadeslayer> apachelogger: http://paste.kde.org/pytifsehy
[19:08] <shadeslayer> apachelogger: code is http://paste.kde.org/pbjmje1f0
[19:08] <shadeslayer> hm, no proper licensing in there
[19:09] <shadeslayer> apachelogger: anyway, the problem is, when I hit refresh now, my older connect calls are still active, hence the ui gets double the number of entries
[19:10] <shadeslayer> so I could a) make the QDBusPendingCallWatcher variable a private member and disconnect calls in the refresh function
[19:10] <shadeslayer> or b) I could make it more async the way I made driver fetching more async
[19:10] <sgclark> Riddell: deps added, attempt at watch file added, uploaded
[19:10] <apachelogger> shadeslayer: Qt::SingleConnection or somesuch
[19:10] <shadeslayer> oh
[19:10] <shadeslayer> apachelogger: cheers
[19:11] <apachelogger> it's an argument for connect
[19:12] <apachelogger> http://qt-project.org/doc/qt-4.8/qt.html#ConnectionType-enum
[19:12] <shadeslayer> thx
[19:13] <apachelogger> shadeslayer: the timeout code is still wrong btw
[19:13] <shadeslayer> apachelogger: oh?
[19:14] <apachelogger> each function should have timer.stop() at the beginning and timer.start at the end
[19:14] <apachelogger> i.e. you do not want to autoterminate while things are happening
[19:14] <apachelogger> that's why I originally said the timeout should be relatively low
[19:14] <shadeslayer> hmmm
[19:15] <shadeslayer> apachelogger: well, I'm thinking of eliminating timer since it can take more than 25 seconds as witnessed on David's machine
[19:15] <apachelogger> shadeslayer: you still need autotermination
[19:15] <apachelogger> it shoud not happen while you are inside a function though
[19:15] <shadeslayer> apachelogger: true, however autotermination needs figuring out
[19:15] <apachelogger> which is why you need to stop and start the timer respectively
[19:16] <apachelogger> shadeslayer: that's what I just explained....
[19:16] <apachelogger> you have a timer that is active whenever you are idle
[19:16] <shadeslayer> oh
[19:16] <shadeslayer> ahah
[19:16] <shadeslayer> got it
[19:16] <apachelogger> watch out for syncness though
[19:16] <shadeslayer> apachelogger: Qt::UniqueConnection right?
[19:17] <apachelogger> if one calls function a and then function b, be should not start the timer
[19:17] <apachelogger> shadeslayer: yes
[19:17] <apachelogger> I am wondering though
[19:17] <apachelogger> shadeslayer: when would it call connect twice?
[19:17] <shadeslayer> QDBusPendingCallWatcher async = new QDBusPendingCallWatcher(driverForDeviceMap, this);
[19:17] <shadeslayer> object is destroyed with kcm exit
[19:18] <shadeslayer> old connects still in place
[19:18] <apachelogger> ah
[19:18] <apachelogger> in the cpp code
[19:18] <shadeslayer> yep
[19:18] <apachelogger> why did you paste me the python then :P
[19:18] <shadeslayer> because I was going for solution a)
[19:18] <apachelogger> ah
[19:19] <apachelogger> well, fwiw, I personally prefer manual disconnnects but I am weird with explicitness of code
[19:19] <apachelogger> much like I prefer manual point management over using qpointer
[19:19] <apachelogger> forces one to know what one is doing ^^
[19:19] <shadeslayer> apachelogger: btw are you sure this will work
[19:19] <apachelogger> alas, if one doesn't know then shit goes wrong ;)
[19:19] <shadeslayer> because apparently everything must match, even the object
[19:19] <apachelogger> shadeslayer: what? uniqueconnection?
[19:19] <shadeslayer> yews
[19:20] <shadeslayer> "i.e., if the same signal is already connected to the same slot for the same pair of objects,"
[19:20] <apachelogger> shadeslayer: a connection cannot be duplicated unless it is exactly the same 
[19:20] <shadeslayer> objects are different in this case
[19:20] <shadeslayer> since I have a new call in  there
[19:20] <apachelogger> post dat cpp plz
[19:21] <shadeslayer> apachelogger: http://paste.kde.org/pmalqfntr
[19:21] <apachelogger> shadeslayer: how is that causing the typerror you pasted?
[19:21] <shadeslayer> apachelogger: it's not
[19:22] <apachelogger> you are confusing me
[19:22] <shadeslayer> the typerror was caused when I was going for solution a
[19:22] <shadeslayer> apachelogger: fine, let's start from the beginning
[19:22] <apachelogger> well solution a is nonense
[19:23] <shadeslayer> apachelogger: let me show you
[19:23] <apachelogger> just tell me what the problem is
[19:24] <apachelogger> although I think I see it already ^^
[19:24] <Riddell> sgclark: "Initial release closes: LP: #12345"  you're supposed to replace that 12345 with the bug number :)
[19:25] <sgclark> Riddell: gah, oops, sorry lol
[19:25] <Riddell> sgclark: I'll upload to experimental
[19:25] <sgclark> Riddell: did you fix that then?
[19:25] <Riddell> sgclark: yep
[19:25] <sgclark> Riddell: thanks!
[19:25] <Riddell> we'll get a third opinion on it then upload to the archive
[19:25] <sgclark> Riddell: anything else I can work on?
[19:26] <shadeslayer> apachelogger: when I hit refresh now : http://im9.eu/picture/l15690
[19:26] <Riddell> sgclark: you could update the verson of gtk2-engines-oxygen ?
[19:27] <shadeslayer> Qt::UniqueConnection does not help btw
[19:27] <apachelogger> yeha that's expected
[19:27] <ScottK> Riddell: We're waiting on Qt 5.2 for your Frameworks 5 packages to go in, right?
[19:27] <shadeslayer> apachelogger: because async is not the same object?
[19:27] <apachelogger> shadeslayer: and you are sure that happens because of 4 calls into driverMapFinished?
[19:27] <apachelogger> i.e. did you actually insert a qdebug in there and check
[19:28] <Riddell> ScottK: we would need 5.2 for the kf5 packages, dunno if I want to upload them to the archive in alpha state
[19:28] <Riddell> sgclark: and gtk3 https://projects.kde.org/
[19:28] <shadeslayer> apachelogger: yep http://paste.kde.org/ptfpqam8r
[19:29] <Riddell> sgclark: uploaded to experimental!
[19:29]  * Riddell cycles off
[19:29] <sgclark> Riddell: ok, I am unclear on updating exsisting packages, will try to figure it out
[19:29] <ScottK> Riddell: 5.2 is in Debian, so maybe it should go to Debian Experimental first anyway.  Then we can decide what to do.
[19:29] <Riddell> sgclark: just ask anyone here
[19:29] <apachelogger> oh god paste.kde :@
[19:30] <apachelogger> shadeslayer: oh, quite possibly at the begging of the slot you want to call data.disconnect() and at the end data.deleteLater()
[19:30] <shadeslayer> apachelogger: I do call data.deleteLater
[19:31] <apachelogger> oh well
[19:31] <apachelogger> is that code pushed>?
[19:32] <shadeslayer> nope
[19:32] <shadeslayer> I don't call data->disconnect() though
[19:32] <shadeslayer> trying with that
[19:32] <shadeslayer> apachelogger: doesn't work :(
[19:33] <apachelogger> shadeslayer: is that code pushed?
[19:34] <shadeslayer> apachelogger: pushed
[19:34] <shadeslayer> apachelogger: without data->disconnect though
[19:36] <apachelogger> shadeslayer: void Module::driverDictFinished(QVariantMapMap data) is being called twice
[19:36] <apachelogger> and that does not seem to have a delete or disconnect
[19:37] <shadeslayer> oh hmm
[19:37] <apachelogger> ah
[19:37] <apachelogger> m_manager is scoped
[19:37] <apachelogger> shadeslayer: that needs the uniqueconnection :P
[19:37] <shadeslayer> makes sense
[19:38] <apachelogger>     connect(m_manager, SIGNAL(dataReady(QVariantMapMap)), SLOT(driverDictFinished(QVariantMapMap)), Qt::UniqueConnection);
[19:38] <apachelogger> :P
[19:38] <shadeslayer> right
[19:38] <apachelogger> shadeslayer: learn to printf debug plz :P
[19:38] <shadeslayer> >.>
[19:39] <apachelogger> shadeslayer: there's a ui state bug I just noticed, while you are loading the reload button is still enabled
[19:39] <apachelogger> so I can still forcefully trigger the device duplication if I simply keep hitting the button
[19:39] <apachelogger> http://i.imgur.com/fJdpnCv.png
[19:39] <shadeslayer> heh
[19:40] <apachelogger> shadeslayer: FWIW, it may be worthwhile to introduce a saveguard against this duplication
[19:40] <apachelogger> since I guess you have the device id somewhere it would be easy to simply check whether deviceid is already in the list of widgets and only add if not
[19:45] <apachelogger> shadeslayer: I hope you took notes of what I spewed because I am not :P
[19:45] <shadeslayer> apachelogger: fixed the reload button
[19:46] <shadeslayer> but not sure about the duplication thing
[19:46] <shadeslayer> *might* be possible
[19:46] <shadeslayer> can't say
[19:46] <shadeslayer> apachelogger: will have a look tomorrow in any case
[19:46] <shadeslayer> apachelogger: can you check if your crash is fixed?
[19:48] <shadeslayer> apachelogger: also, I'm not sure what data structure to use to track state for the apply button :)
[19:48] <shadeslayer> I was thinking of a sorted QStringList
[19:48] <shadeslayer> but that seems inefficient
[19:49] <shadeslayer> anyt thoughts on a better way?
[19:49] <ahoneybun> shadeslayer: love the look of the new driver manager
[19:49] <sgclark> I am trying to figure out how to update existing packages, stuck at stage 1. uscan warning: In debian/watch no matching files for watch line. But there is a new version, ideas?
[19:49] <shadeslayer> ahoneybun: good to hear :)
[19:49] <apachelogger> shadeslayer: huh?
[19:49] <apachelogger> shadeslayer: you know when you are fetching and you know when you are done fetching, no?
[19:50] <apachelogger> so fetching = setEnabled(false) and !fetching = setEnabled(true)
[19:50] <shadeslayer> apachelogger: for the apply button?
[19:50] <apachelogger> yes
[19:50] <shadeslayer> apachelogger: My question was more related to when you do : select driver a -> select driver b -> select driver a -> apply button is still enabled
[19:51] <shadeslayer> or if you just click driver a again
[19:51] <shadeslayer> then the apply button becomes enabled
[19:52] <apachelogger> there's like a godzillion optionsfor that
[19:52] <shadeslayer> I'm all ears
[19:52] <apachelogger> bool DriverWidget::hasChanged()
[19:52] <apachelogger> int DriverWidget::m_defaultSelection
[19:53] <apachelogger> or actually
[19:53] <apachelogger> perhaps wire up signals between DriverWidget instances and the KCM's changed signal
[19:54] <apachelogger> I'd definitely simply have an int denoting the default selection and then evaluate changedness by comparing the selected driver entry with the default one
[19:54] <shadeslayer> hmmm
[19:54] <shadeslayer> ojk
[20:07] <sgclark> ok I fixed the watch file, but it has debian git-import-orig and I get ( is not a git repository) error. 
[20:17] <shadeslayer> apachelogger: how do you get the kde infra to send emails via scratch repos ? :P
[20:19] <shadeslayer> apachelogger: and do you reckon http://paste.ubuntu.com/6916989/ the correct fix for bug 1278826
[20:23] <apachelogger> possibly
[20:23] <apachelogger> doesn't look all too wrong anyway
[20:23] <shadeslayer> apachelogger: and re https://trello.com/c/aR2V1zm7/97-firefox-import-bookmarks-from-rekonq-kde-somehow , documentation should be written in https://wiki.ubuntu.com/TrustyTahr/Beta1/Kubuntu ?
[20:23] <shadeslayer> or linked to https://wiki.ubuntu.com/TrustyTahr/Beta1/Kubuntu and a new page on techbase
[20:31] <soee> ha this is not true: Mozilla Firefox 27 :D
[20:31] <soee> atm it is Mozilla Firefox 25
[20:33] <shadeslayer> soee: nope, it's 27
[20:33] <shadeslayer> or it should be
[20:33] <shadeslayer> atleast saucy has 27
[20:33] <soee> yes i agree it should be but isnt :) there is beta in proposed
[20:33] <shadeslayer> yeah
[20:42] <shadeslayer> so hungry :(
[20:45] <shadeslayer> I broke something http://im9.eu/picture/s15690
[20:46]  * mamarley wonders why no-one seems to use sub-pixel rendering anymore...
[20:46] <apachelogger> shadeslayer: release notes
[20:46] <apachelogger> the official ones
[20:46] <apachelogger> no clue where we do those
[20:46] <apachelogger> Riddell or ScottK proably know
[20:46] <shadeslayer> apachelogger: https://wiki.ubuntu.com/TrustyTahr/Beta1/Kubuntu
[20:47] <shadeslayer> aren't those the release notes?
[20:47] <shadeslayer> either way, can't do shit, moin moin is broken
[20:47] <shadeslayer> mamarley: we have a task to investigate sub pixel rendering, want to take that up?
[20:48] <mamarley> Investigate it?
[20:48] <shadeslayer> mamarley: https://trello.com/c/0tn1vYPN
[20:48] <shadeslayer> mamarley: idk, that's what the card says :P
[20:49] <shadeslayer> I've been running the settinsg on that bug for a bit
[20:49] <shadeslayer> and I can't tell the difference
[20:49] <mamarley> Hmm...  Just about everyone uses LCDs these days, so enabling it by default would probably make sense.
[20:50] <ScottK> shadeslayer: That's a pretty ancient python there.
[20:51] <mamarley> There is, however, a "bug" in Qt that causes subpixel rendering to be disabled on just about any translucent surface (such as the KDE panel.)
[20:51] <shadeslayer> ScottK: I'd be surprised if they were running a new python on the wiki :P
[20:51] <ScottK> The last Ubuntu release that had python2.6 was lucid.
[20:52] <shadeslayer> ScottK: heh, aren't all the buildd's running warty ;)
[20:52] <ScottK> Not anymore.
[20:53] <shadeslayer> oh ? :D
[20:53] <shadeslayer> Did that change recently?
[20:53] <shadeslayer> phew, KDE integration patches apply cleanly
[20:53] <ScottK> For a long time the powerpc buildds ran dapper even after hardy was released.
[20:53] <ScottK> Other than that, sparc was the only one that substantially lagged.
[20:54] <ScottK> Generally they're running the last LTS.
[20:56] <shadeslayer> I see
[20:58]  * shadeslayer heads home
[20:59] <shadeslayer> cya tomorrow
[21:30] <shadeslayer> ScottK: do you know where I could a migration guide for users so that they could import their KDE Bookmarks into Firefox?
[21:30] <shadeslayer> *could put a
[21:35] <shadeslayer> apachelogger: https://notes.kde.org/p/kubuntu-migration-guide
[21:36] <shadeslayer> needs screenshots
[22:07] <Riddell> anyone able to review dpic and cirkuit in https://launchpad.net/~kubuntu-ppa/+archive/experimental/+packages ?
[22:09] <ScottK> shadeslayer: No.  Sorry.
[22:14] <Riddell> shadeslayer: did you use kubuntu-automation?
[22:36] <apachelogger> shadeslayer: please use fix committed when a change is in a VCS but not uploaded
[22:37] <apachelogger> otherwise we run risk of forgetting to upload
[22:39] <apachelogger> shadeslayer: please run by our docs heros
[22:43] <shadeslayer> Riddell: not quite
[22:44] <shadeslayer> apachelogger: I was planning to do a upload tomorrow
[22:45] <shadeslayer> Riddell: http://paste.kde.org/psxhbeosr
[22:51] <soee_> another more or less happy user https://plus.google.com/u/0/112543117923336622039/posts/CNiFeLCLRrg :)
[22:54] <shadeslayer> valorie: ahoneybun review plz https://notes.kde.org/p/kubuntu-migration-guide
[22:57] <ahoneybun> shadeslayer: I can tell you I don't have "keditbookmarks"
[22:57] <shadeslayer> o_o
[22:57] <ahoneybun> without the quotes
[22:57] <shadeslayer> your install sounds broken
[22:58] <shadeslayer> because that comes from kde-baseapps-bin
[22:58] <ahoneybun> well if we will have firefox as default in 14.4 should we not just link/write about using firefox bookmark export/import usage?
[22:59] <ahoneybun> g2g
[23:00] <shadeslayer> well, this is for people who use KDE software to manage their bookmarks