[00:20] <valorie> apachelogger: I fooled it into thinking it was a final release
[00:21] <apachelogger> valorie: nothing is ever final, who's final?
[00:21] <valorie> ScottK, I think it was, gave me an entry to put in my accept.hosts file
[00:21] <apachelogger> actually maybe it'd be final, but then it'd be dead, so probably not final considering there's a relase
[00:21] <valorie> now I've removed it, so I can't recall what it was exactly
[00:22] <ScottK> jr set up a fake metarelease file that valorie  pointed at to simulate saucy having been released.
[00:22] <valorie> looked exactly like it's always looked when I waited for a notification rather than loading up the beta or whatever
[00:23] <apachelogger> ah, distro upgrade
[00:23]  * apachelogger almost had  segfault there
[00:24] <apachelogger> it's just a silly issue
[00:24] <apachelogger> chances are .1 fixes it though
[00:24] <apachelogger> or at least makes it less likely
[00:24] <apachelogger> that is if my guess at the cause is actually right
[00:25] <apachelogger> and if it's not that it would most likely be a bug in metarelease, which would be odd but at least out of our realm of responsiblity
[00:25] <apachelogger> -> bed
[00:26] <valorie> ok, final wasn't the right term, sorry
[00:26] <valorie> sweet dreams of unicorns
[00:27] <ahoneybun> on jury duty
[00:27] <ahoneybun> *oh
[00:27] <ahoneybun> hey valorie 
[00:27] <valorie> oooo, they let you use your phone?
[00:27] <valorie> that's cool
[00:27] <valorie> I haven't done jury duty for years
[00:27] <valorie> and yet some get called every 6 months or so
[00:28] <valorie> wierd system we have
[00:33] <ahoneybun> no I'm home now
[00:34] <ahoneybun> but I got picked out of like  40
[00:34] <ahoneybun> there are 8 of us in total
[00:35] <valorie> yes, it's odd how huge the pool is, and then how few are chosen
[00:35] <valorie> I was on a jury of 8 as well
[00:37] <ahoneybun> yea
[02:03] <ahoneybun> hey lordievader 
[02:07] <manchicken> !seen jontheechidna
[02:08] <manchicken> Anybody seen Jon T?
[02:21] <ScottK> Not for awhile.
[02:54] <ahoneybun> hey Riddell 
[02:54] <ahoneybun> hey valorie I got a answer back about ubuntuguide
[02:54] <valorie> cool
[02:54] <valorie> I was just now reading through it
[02:55] <ahoneybun> oh
[02:55] <valorie> what did s/he say?
[02:55] <ahoneybun> I got 2 emails from different people dealing with it
[02:55] <ahoneybun> one is a long and the other not so much
[02:56] <valorie> anything of significance?
[02:56] <ahoneybun> trying to put it in a pastie
[02:57] <ahoneybun> http://paste.ubuntu.com/6362426/
[02:58] <ahoneybun> but the short one says we should combine our effects
[02:58] <valorie> from two different people?
[02:58] <valorie> your pasted person sounds a bit grumpy
[03:01] <ahoneybun> yea I think one forwarded the other the email
[03:03] <valorie> huh
[03:03] <ahoneybun> he is the main person in charge of the wiki
[03:03] <valorie> kde bnc was kicking up a fuss
[03:04] <ahoneybun> I emailed someone and then they forwarded it to the main man
[03:05] <valorie> ok
[03:05] <valorie> anyway, I think we should offer to join forces
[03:06] <valorie> because I like their system
[03:06] <valorie> and having grumpy people doing side projects sounds like a bad idea anyway
[03:06] <valorie> too much grumpiness already
[03:07] <ahoneybun> valorie, well he says he is doing maintenance of the site not really writing on it
[03:07] <valorie> somebody is doing the writing.....
[03:09] <ahoneybun> does it have the translation we need?
[03:11] <ahoneybun> so we want to host the docs there?
[03:11] <valorie> I don't see any translations for it
[03:12] <valorie> however, they could install the translation system that the KDE wiki uses
[03:12] <ahoneybun> oh
[03:13] <valorie> so I think it would be good to do a nice discussion with them
[03:13] <valorie> they may not know about the translation tool
[03:14] <ahoneybun> ok I sent a email about it
[03:14] <valorie> cool, please CC me on that stuff
[03:14] <valorie> so I can enter into the conversation
[03:15] <valorie> sec
[03:15] <ahoneybun> oh the next email I'll add you into it
[03:15] <ahoneybun> sorry
[03:22] <valorie> np; I just thought of it
[03:22] <valorie> gonna watch the news for a bit; bbl
[03:23] <ahoneybun> ok
[07:03] <soee> good morning
[07:07] <Quintasan> \o
[07:08] <soee> o/
[07:25] <lordievader> Good morning.
[10:44] <menace> how can i change the status of a bug? i added the crash handler text as requested in https://bugs.kde.org/show_bug.cgi?id=327130
[10:47] <apachelogger> menace: you cannot, that's up to a dev/triager
[14:16] <yossarianuk> hi - a work colleague's machine is having an issue downloading the nvidia package (only) - he tried using additional drivers to install 319.60
[14:16] <yossarianuk> it just stayed @ 0 %
[14:17] <yossarianuk> cancelled that,  did apt-get clean -  apt-get update - then tried to download with apt-get -d install nvidia-319-updates
[14:17] <yossarianuk> it just keeps downloading the package -  over and over (and over, etc) forever
[14:18] <yossarianuk> its only nvidia packages this is occurring on - other packages download/install fine.
[14:18] <yossarianuk> any ideas why 
[14:18] <Riddell> yossarianuk: I don't know I'm afraid, support in #kubuntu
[14:18] <yossarianuk> ok - i did ask there but didn;t get a solution...
[14:22] <apachelogger> yossarianuk: -d = download
[14:22] <apachelogger> as in: download-only
[14:23] <yossarianuk> apachelogger: sorry i should have said I was using the -d option.
[14:23] <yossarianuk> it gets to 100% and restarts 
[14:23] <yossarianuk> only for nvidia packages
[14:24] <yossarianuk> and only for the driver packages, not the settings package
[14:24] <yossarianuk> which is odd
[14:24] <apachelogger> try another mirror then
[14:24] <apachelogger> kdesudo software-properties-kde
[14:24] <yossarianuk> ok - will do
[14:24] <apachelogger> it may well be that the download fails/aborts/corrupts and that's why it tries to download again
[14:24] <yossarianuk> I'll copy over my sources.list
[14:24] <yossarianuk> thanks
[14:29] <shadeslayer> Riddell: could you test muon from the 2.1 branch?
[14:30] <Riddell> shadeslayer: some fixes are done?
[14:30] <shadeslayer> yep
[14:30] <Riddell> lovely
[14:31] <shadeslayer> and could you reproduce kde bug 327125
[14:31] <shadeslayer> because I can, but it should be fixed
[14:31] <Riddell> I'll try
[14:31] <shadeslayer> so maybe its just my system being weird
[14:53] <Riddell> shadeslayer: umm well first thing is muon-updater has the banner saying "A new version of Kubuntu is available." which isn't true
[14:53] <shadeslayer> I don't have that here
[14:53] <apachelogger> omgomogmgomg
[14:54] <apachelogger> Riddell: paste .cache/upstart/startkde.log
[14:54] <shadeslayer> maybe because of http://pastebin.kde.org/pugpuag13
[14:54] <BluesKaj> 'Morning all
[14:54] <Riddell> shadeslayer: sometimes it also gives a python traveback on startup http://pastebin.kde.org/pdpqmrwh4
[14:54] <apachelogger> Riddell: and try python3 /usr/share/kde4/apps/muon-notifier/releasechecker; echo $?
[14:54] <Riddell> shadeslayer: snap
[14:54] <apachelogger> that traceback is normal
[14:54] <apachelogger> metarelease seems overly shitty
[14:56] <Riddell> apachelogger: releasechecker gives me that traceback and $? is 1
[14:56] <apachelogger> :@
[14:56] <apachelogger> sillest issue in the world
[14:57] <apachelogger> Riddell: well, startkde.log plz
[14:57]  * apachelogger ponders enabling debug on releasechecker
[14:57] <shadeslayer> apachelogger: btw kde bug 326178 seems like a issue in s-p-k
[14:58] <Riddell> apachelogger: http://starsky.19inch.net/~jr/tmp/startkde.log if you really want it
[15:05] <apachelogger> shadeslayer: no
[15:05] <apachelogger> shadeslayer: discover invokes spk with the flag that makes it not update the cache
[15:05] <apachelogger> but discover itself does not update the cache
[15:05] <apachelogger> so no one updates the cache
[15:05] <shadeslayer> except that I think that s-p-k ignores that flag
[15:05] <apachelogger> Riddell: it's very fortunate that I removed the related debug ysterday xD
[15:06] <apachelogger> ok, log doesn't help
[15:06] <apachelogger> Riddell: can you reproduce the distro version thing across restarts of muon?
[15:07] <apachelogger> easy enough to tesT?
[15:07] <apachelogger> shadeslayer: ^
[15:07] <shadeslayer> I cannot
[15:07] <shadeslayer> I am on trusty
[15:08] <apachelogger> and trust doesnt have spk?
[15:08] <Riddell> apachelogger: it sometimes has that new disto notice and sometimes gives the python traceback
[15:08] <apachelogger> that's better than what I get
[15:09] <apachelogger> lemme fix you up a new relesechecker real quick
[15:09] <shadeslayer> apachelogger: all I get is the traceback and no new release
[15:09] <apachelogger> actually
[15:09] <shadeslayer> because I am on the latest release maybe?
[15:10] <apachelogger> Riddell: export DEBUG_UPDATE_MANAGER=1
[15:10] <apachelogger> Riddell: then try to trigger the bogus notification and paste the CLI output
[15:10] <apachelogger> shadeslayer: for spk? what?
[15:10] <shadeslayer> apachelogger: for muon checking release
[15:11] <apachelogger> I am talking about spk with you and about relesechecking with Riddell :P
[15:11] <apachelogger> see, I am supposed to get confused, not you :P
[15:16] <Riddell> apachelogger: http://paste.ubuntu.com/6365144/
[15:16] <apachelogger> Riddell: oh and please open ksysguard and filter for muon ... check that there is only ever one python3 running
[15:16]  * apachelogger needs to fix his name resolution
[15:17] <apachelogger> hm
[15:17] <Riddell> apachelogger: looks like only one python3 is run, tried it three times
[15:17]  * genii kicks repeatedly and viciously at his Muon
[15:18] <apachelogger> what if it is not the script that causes the race condition but metarelease itself
[15:18] <apachelogger> hmmmmmmmmmmm
[15:19] <apachelogger> or what if it used to be a script race and I turned it into a thread race yesterday
[15:22] <Riddell> you are making muon threaded?
[15:23] <apachelogger> Riddell: http://paste.ubuntu.com/6365183/
[15:23] <apachelogger> no, metareleas is threaded
[15:23] <apachelogger> in the worst possible way
[15:24] <apachelogger> __init__ starts download in a thread
[15:24] <apachelogger> but there is no way to tell when that thread/download is done through inter-locking because metarelease is no qobject or has callbacks or anything
[15:25] <apachelogger> so if you call download while the threaded download is running it will most certainly have reentrancy problems because download most likely writes to members (most certainly bool downloading)
[15:26] <apachelogger> all of the above is why sane code would not flipping thread a function call through __init__
[15:26] <apachelogger> but how oftne do I get to deal with sane code :(
[15:26] <apachelogger> interestingly enough aptdaemon-packagekit compat thing also manually calls download() so it supposedly has the same problem
[15:28] <apachelogger> anyway
[15:28] <apachelogger> Riddell: please try that new releasechecker see if it also exhibits the problem
[15:29] <Riddell> apachelogger: on the pastebin?
[15:29] <apachelogger> yeah
[15:30] <Riddell> ok, am also following frameworks meeting, will be slow
[15:32] <Riddell> apachelogger: http://paste.ubuntu.com/6365229/
[15:36] <apachelogger> Riddell: still reproting bogus availability?
[15:36]  * apachelogger needs to figure out how ubuntu checks for releases
[15:37] <Riddell> the same way isn't it?
[15:37] <apachelogger> well, but what calls it
[15:37] <Riddell> apachelogger: release upgrade banner does not show yay
[15:37] <apachelogger> the only reference I found was the packagekit compat and I am not sure that is used
[15:37] <apachelogger> hm
[15:37] <apachelogger> Riddell: best try for the next hour or so :P
[15:38] <apachelogger> so I think it can be a file race, but I turned it into a thread race yesterday, which made it more reliably reproducible
[15:51] <apachelogger>         # this is needed because gtk is not thread-safe
[15:52] <apachelogger> haha
[15:52] <apachelogger> so this is really how they are using it
[15:52] <apachelogger> basically a 1 second timer calling a function to check if the other thread is done yet
[15:52]  * apachelogger has headache now
[16:06] <davmor2> apachelogger: stop banging your head on the desk then
[16:08] <apachelogger> butbutbut
[16:08] <apachelogger> Riddell: git pull
[16:08] <apachelogger> should be fixed again
[16:09] <Riddell> apachelogger: muon?
[16:09] <apachelogger> yes
[16:10] <apachelogger> alas, you can still get a race however it's extremely unlikely and not very trivial to prevent
[16:12] <shadeslayer> apachelogger: +    # MetaReleaseCore internally runs .download() in a thraed. It has however no
[16:12] <shadeslayer> thraed
[16:12] <shadeslayer> ...
[16:21] <Riddell> shadeslayer: hmm I'm having it hang on Loading Software List http://starsky.19inch.net/~jr/tmp/muon.png
[16:21] <shadeslayer> same as me then
[16:22] <shadeslayer> Riddell: plz comment on https://bugs.kde.org/show_bug.cgi?id=327125
[16:23] <shadeslayer> Riddell: can you try deleting a PPA from muon-discover -> Sources
[16:23] <shadeslayer> because it crashes for me here
[16:23] <shadeslayer> I can also not disable PPA's in discover by unchecking the tickbox next to them
[16:24] <shadeslayer> see KDE bug 327178
[16:28]  * Riddell tries
[16:30] <Riddell> shadeslayer: yes I get a crash on deleteing one
[16:30] <shadeslayer> Riddell: yep, that's another one
[16:30] <shadeslayer> haven't reported a bug for that one
[16:30] <Riddell> shadeslayer: is there a bug or shall I report one?
[16:30] <Riddell> ok I'll do it
[16:30] <shadeslayer> http://pastebin.kde.org/poatgfnaf#line-84
[16:30] <shadeslayer> go ahead
[16:32] <shadeslayer> hummm
[16:33] <shadeslayer> works for me now
[16:33] <shadeslayer> okay nope
[16:33] <Riddell> shadeslayer: kde bug 327179
[16:34] <shadeslayer> Riddell: plz install dbg symbols?
[16:35] <Riddell> ah hmm, it's self compiled
[16:38] <Riddell> hmm crash seems to be in qt
[16:42] <shadeslayer> more like libqapt?
[16:42] <shadeslayer> #6  0x00007f298713ceaf in debListParser::LoadReleaseInfo(pkgCache::PkgFileIterator&, FileFd&, std::string) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
[16:42] <shadeslayer> for me
[16:42] <Riddell> nothing about qapt in my backtrade, maybe you should add yours to the bug report
[16:47] <shadeslayer> will do once I compile qapt with dbg symbols
[18:34] <shadeslayer> Riddell: I have a fix for the crash-on-removing-ppa's
[18:38] <shadeslayer> Riddell: http://pastebin.kde.org/pczpi1lkq
[18:43] <shadeslayer> ideally I'd disable the add source button till the user is done adding everything, or, only reload the list once the user is done adding everything
[18:50] <shadeslayer> ScottK: Riddell what's the policy on LGPL libs linking against openSSL?
[19:00] <soee> ee does the muon updater works ?
[19:01] <soee> looks like ... not
[19:24] <shadeslayer> soee: still fixing things
[19:24] <shadeslayer> 2.1 branch has alot of fixes
[19:25] <soee> shadeslayer, ok :) for me its not a problem :) i can do updates from muon or terminal -.-
[19:25] <soee> just clicked now updater when i saw it 
[20:33] <soee> thers no 4.11.3 release info yet ?
[20:37] <Riddell> shadeslayer: LGPL is fine with SSL I'm pretty sure
[20:43] <shadeslayer> ack
[20:43] <shadeslayer> d_ed is/was moaning about how the qcal ssl plugin is split from qca2
[20:43] <shadeslayer> on the ktp mailing list
[20:44] <shadeslayer> and I was curious as to why it's split into its own plugin when according to him it was inside qca2 at one point
[20:44] <shadeslayer> anyway, dinner
[20:44] <Riddell> shadeslayer: so GPL code can us eit
[20:44] <Riddell> shadeslayer: so GPL code can use it
[20:44] <Riddell> Qt was GPL until recently
[20:44] <Riddell> many applications are GPL
[21:16] <shadeslayer> ack
[22:15] <mamarley> debfx: I just posted an updated Upstart script for Quassel.  https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1244036
[22:15] <mamarley> It uses start-stop-daemon now, so it should solve the problem you were having.
[22:15] <mamarley> Also, I had to hardcode the path to quasselcore, otherwise start-stop-daemon wouldn't find it.
[22:15] <mamarley> Sorry for the delay; I have been quite busy with school.
[22:25] <mamarley> ScottK: You might be interested in this too^