[04:40] <JontheEchidna> I'm surprised, the university has us using a linux lab, (gnome3, yech) and we can remotely submit assignments via scp/ssh.
[04:40] <JontheEchidna> (and that linux lab is what we're using for this class)
[05:04] <shadeslayer> morning
[06:18] <soee> Riddell, i did upgrade during the night 12.04 -> 12.10
[06:18] <soee> but had no time to reboot machine and check if everyting is ok
[06:19] <soee> but upgrade finished without any errors
[06:33] <apachelogger> kubotu: order coffee
[06:33]  * kubotu slides coffee with milk down the bar to apachelogger.
[06:33] <apachelogger> kubotu: order a lot more coffee
[06:33]  * kubotu slides a lot more coffee down the bar to apachelogger
[06:38] <apachelogger> good news everyone!
[06:38] <apachelogger> libs is building, pim-runtime continues to fail, still 3 packages missing
[06:39] <apachelogger> oh, actually it's more than 3
[06:39] <apachelogger> Oo
[06:54]  * shadeslayer looks
[06:54] <shadeslayer> yay, stupid chrome still hit by that stupid bug
[06:55] <shadeslayer> apachelogger: have you seen martin's email to kde-packagers about some critical bug
[06:56] <shadeslayer> pim-runtime ftbfs is weird
[06:57] <shadeslayer> !find libxerces
[06:57]  * shadeslayer fixes
[07:00] <shadeslayer> bleh
[07:02] <apachelogger> shadeslayer: no
[07:02] <apachelogger> todo:
[07:02] <apachelogger> - workspace
[07:02] <apachelogger>   * kwin patch
[07:02] <shadeslayer> whut
[07:02] <shadeslayer> ok
[07:02] <shadeslayer> awesum
[07:02] <apachelogger> my notes file apparently has
[07:02] <apachelogger> don't ask me how
[07:03] <apachelogger> text files are getting all intelligent Oo
[07:04] <shadeslayer> apachelogger: this is the first I'm facing this .. but should kdepim-runtime dep on libxerces-c-dev or libxerces-c3.1
[07:04] <shadeslayer> because libxerces-c3.1 was pulled in automatically earlier
[07:04] <shadeslayer> but libxerces-c-dev was never pulled in
[07:04] <shadeslayer> and I've never seen a build dep on just a library ... always on lib headers
[07:06]  * shadeslayer is going to install precise this weekend, quantal's X is absolutely unusable
[07:08] <shadeslayer> mmm ... need to sync github ff-kde with precise packaging
[07:08] <apachelogger> shadeslayer: where is the error anyway?
[07:08] <shadeslayer> apachelogger: can't find libs to link against I believe ( needs libxerces-c3.1  )
[07:09] <apachelogger> ah
[07:09] <apachelogger> make[4]: *** No rule to make target `/usr/lib/i386-linux-gnu/libxerces-c.so', needed by `resources/kolabproxy/akonadi_kolabproxy_resource'.  Stop.
[07:09] <shadeslayer> *nod*
[07:09] <apachelogger> why it appears the lib had a packaging error if the -dev was not pulled in
[07:09] <shadeslayer> that was pulled in automagically earlier
[07:09] <apachelogger> OR that dep is new
[07:09] <shadeslayer> the former
[07:09] <apachelogger> bogus packaging then
[07:09] <shadeslayer> mhmm
[07:09] <apachelogger> OR that .so is in fact not public
[07:10] <apachelogger> (i.e. usually that .so would be a link to the sonamed version e.g. xerces-c.so.0.0.0, but it is only needed to find that sonamed version, thus only a dev requirement, so it should only be in -dev)
[07:12] <shadeslayer> ETOOTIREDTOPARSEERROR
[07:13] <apachelogger> shadeslayer: please push your missing change to kdentwork
[07:14] <apachelogger> only things missing should be network and mplayerthumbs now
[07:14] <apachelogger> and former needs packaging to begin with
[07:14] <shadeslayer> kk
[07:15] <apachelogger> actually latter
[07:15]  * apachelogger needs moar coffeee
[07:16] <shadeslayer> I just had coffee and I'm barely awake :|
[07:17] <CIA-58> [kdenetwork] Rohan Garg * 184 * debian/ (6 files in 2 dirs) * Compile with telepathy-qt support for krfb - Add fix_missing_header_include.diff to fix libvncviewer FTBFS
[07:17] <shadeslayer> apachelogger: ^ kfixed
[07:17] <shadeslayer> you probably want to drop that patch
[07:18] <shadeslayer> I pushed it into SVN as well, so was most likely included in 4.9.1
[07:19]  * shadeslayer tickles apachelogger
[07:21] <apachelogger> I do like dropping patches
[07:24] <apachelogger> shadeslayer: not the case
[07:24] <shadeslayer> oh
[07:24] <shadeslayer> does SVN have branches?
[07:24] <shadeslayer> because I just pushed to master
[07:24] <apachelogger> SVN has definitely no master :P
[07:24] <apachelogger> also what's with the patch naming there?
[07:25] <shadeslayer> hehe
[07:25] <shadeslayer> simple_and_generic_names.ftw
[07:26] <apachelogger> shadeslayer: u fixing pim-runtime?
[07:27] <shadeslayer> apachelogger: I'm not sure what would be the /right/ way to do things there
[07:27] <apachelogger> add the build dep? :P
[07:27] <shadeslayer> sure, but on the library or the header files :P
[07:27] <apachelogger> the one that contains the .so?!
[07:28] <shadeslayer> !find /usr/lib/i386-linux-gnu/libxerces-c.so
[07:28] <shadeslayer> wat
[07:28] <apachelogger> !find libxerces-c.so quantal
[07:28] <shadeslayer> tehehehe
[07:28] <apachelogger> funny
[07:29] <apachelogger> !info libxerces-c-dev
[07:29] <apachelogger> !info libxerces-c-dev quantal
[07:29] <apachelogger> ...
[07:29] <apachelogger> I broke it
[07:29] <shadeslayer> :D
[07:30] <shadeslayer> apachelogger: have you mooed today
[07:31] <shadeslayer> !find libxerces-c-3.1.so
[07:31] <shadeslayer> @_@
[07:31] <apachelogger> libxerces-c-dev
[07:31] <shadeslayer> ya
[07:37] <MCR1> Hi. Some people have troubles running python-qt4 applications on Quantal like the packages qbzr or trimage. They all fail with the same error: Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed.
[07:37] <MCR1> Who can fix this ?
[07:37] <MCR1> I was told by didrocks that I might find the experts here :)
[07:38] <agateau> MCR1: sounds like a bug in the qgtk widget style
[07:39] <agateau> MCR1: do you get the same crash when running the app with "-style plastique" options
[07:39] <agateau> ?
[07:39] <shadeslayer> apachelogger: fix uploaded
[07:40] <MCR1> agateau: one moment, checking :)
[07:40] <apachelogger> thx
[07:42] <MCR1> agateau: wooow, this time a new crash. I could not start qbzr with this option, but when I tried trimage I got these errors:
[07:43] <MCR1> agateau: QNativeImage: Unable to attach to shared memory segment.
[07:43] <MCR1> X Error: BadDrawable (invalid Pixmap or Window parameter) 9
[07:43] <MCR1> Major opcode: 62 (X_CopyArea)
[07:43] <agateau> wow
[07:44] <shadeslayer> O_O
[07:45] <MCR1> trimage essentially opens in a 5000x5000 pixel window with completely black content
[07:45] <tsdgeos> agateau: if you're bored, assistant is crashing too (different issue altogether)
[07:45] <agateau> tsdgeos: I am not bored :)
[07:46] <tsdgeos> daminit!
[07:46] <agateau> MCR1: if "-style plastique" does not work, you can try running qtconfig and change the style from there
[07:46] <agateau> MCR1: the gtk widget assert reminds me of a problem when overlay scrollbars where used with qgtk style
[07:47] <agateau> MCR1: iirc there is an environment variable to disable overlay scrollbars which you could try to set before running qbzr or trimage
[07:48] <apachelogger> (overlay scrollbars ought to be deactivated in Qt directly)
[07:48] <apachelogger> in quantal anyway
[07:48] <MCR1> agateau: Okay, with style plastique qbzr now seems to work
[07:48] <agateau> MCR1: (or you can just uninstall overlay scrollbars temporarily)
[07:48] <MCR1> agateau: It was using GTK+ before
[07:48] <agateau> apachelogger: I wrote a set of patches to disable overlay scrollbars for oneiric, don't know if they are still there
[07:49]  * agateau bets either the qt side or the gtk side of the patch got dropped
[07:49] <MCR1> agateau: but trimage still fails to open...
[07:49] <apachelogger> http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qt/view/head:/debian/patches/kubuntu_93_disable_overlay_scrollbars.diff
[07:50] <MCR1> trimage error: "sni-qt/3721" WARN  09:49:15.767 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
[07:50] <MCR1> then: QNativeImage: Unable to attach to shared memory segment.
[07:50] <agateau> apachelogger: looks good, can you check for the gtk patch?
[07:50] <apachelogger> I could
[07:50] <apachelogger> that requires more time then
[07:50] <apachelogger> and I am already distracted enough
[07:50] <apachelogger> shadeslayer: please go look for patch in gtk
[07:51] <agateau> :)
[07:51] <shadeslayer> I'm looking at preinst stuff
[07:51] <shadeslayer> and not caffeinated enough
[07:51] <agateau> MCR1: the sni-qt can be ignored I think, the real problem is the 5000x5000 window
[07:51]  * apachelogger pokes with a long pointy stick of foofoo
[07:52] <agateau> I do not run Quantal yet, so it's difficult to help more
[07:52]  * MCR1 tries to pull coffee into the LAN cable...
[07:52]  * agateau creates a Quantal VM
[07:52] <MCR1> agateau: Yes, I do not exactly know if it is 5000x5000, but it is scary big ;)
[07:53] <MCR1> agateau: The compiz close animation of it almost kills my system ;)
[07:55]  * MCR1 hopes that the Compiz issues with virtual machines have already been fixed
[07:55]  * MCR1 tries to update his vbox quantal installation...
[08:00] <agateau> MCR1: can you try to 1) set the Qt style back to GTK 2) run qbzr with "LIBOVERLAY_SCROLLBAR=0 qbzr"?
[08:00] <agateau> apachelogger: gtk patch is still there
[08:03] <MCR1> agateau: The syntax to run qbzr is "bzr qbzr log" for example, so I am not sure how to add LIBOVERLAY_SCROLLBAR=0 to that...
[08:04] <agateau> MCR1: you can run qbzr directly iirc
[08:04] <MCR1> ?
[08:05] <agateau> oh, no you can't
[08:05] <apachelogger> qbzr is a set of plugins to bzr
[08:05] <apachelogger> so simply set the var for bzr
[08:05] <agateau> MCR1: then try LIBOVERLAY_SCROLLBAR=0 bzr qlog
[08:05]  * agateau hasn't used bzr for a long time :)
[08:06]  * apachelogger envys agateau
[08:06] <agateau> apachelogger: you not loving the bazaar ?
[08:06] <MCR1> agateau: WORX :)
[08:06] <apachelogger> no!
[08:06] <jussi> bazaar sounds to me like somethign a japanese soldier would shout when charging... :P
[08:07] <agateau> that would be tora tora tora :)
[08:07] <apachelogger> indeed
[08:07] <apachelogger> shadeslayer: please be reviewing lp:~kubuntu-packagers/kubuntu-packaging/mplayerthumbs
[08:08] <apachelogger> oh noes
[08:08] <shadeslayer> looking
[08:08] <apachelogger> the netwox is failing
[08:09] <shadeslayer> apachelogger: are you sure you want to have a install file?
[08:09] <shadeslayer> it's just one package :P
[08:10] <MCR1> agateau: So basically we found out that liboverlay_scrollbars are breaking GTK+ qt apps in Quantal, yes ? Now 1.How do we fix it ? 2.What about the scary big window ? :-D
[08:11] <MCR1> *of trimage
[08:11] <agateau> MCR1: can you try the LIBOVERLAY_SCROLLBAR trick with trimage as well?
[08:12] <apachelogger> shadeslayer: are you sure you want to insinuate that I have a useless install file?
[08:12] <MCR1> yes ofc. - but I guess there it was another problem, because I already changed the style to plastique, but I'll try...
[08:12] <apachelogger> it's two packages :P
[08:12] <shadeslayer> nope
[08:12] <shadeslayer> well
[08:12] <apachelogger> shadeslayer: before trying to smartass me, check your facts you lazy bum :P
[08:13] <shadeslayer> apachelogger: again, I don't think the install file is required :P
[08:13] <apachelogger> it is
[08:13] <shadeslayer> why
[08:13] <apachelogger> dh does not care that a package has a -dbg suffix
[08:13] <apachelogger> to it there are two packages
[08:13] <MCR1> agateau: The trick does not do the trick for trimage unfortunately...
[08:13] <apachelogger> meaning debian/tmp does not get automatically thrown into package A)
[08:14] <shadeslayer> and why are you not using dh --with-kde ?
[08:14] <apachelogger> dunno, stole that from dragon
[08:14] <shadeslayer> ...
[08:14] <apachelogger> I recon the include takes care of that
[08:14] <apachelogger> on that not
[08:14] <apachelogger> e
[08:15] <shadeslayer> seems that it does
[08:15] <shadeslayer> yes
[08:15] <apachelogger> the build system we use is utterly untransparent and whatnot
[08:15] <apachelogger> also ever changing
[08:15] <apachelogger> I find this bad and a solution must therefore be found
[08:16] <agateau> MCR1: ok, so trimage problem is a different bug
[08:16] <shadeslayer> apachelogger: ok, ship it
[08:16] <apachelogger> needs FFe
[08:17] <apachelogger> unless the binary from 4.8 is still in
[08:17] <apachelogger> which would be spooky
[08:17] <shadeslayer> heh
[08:17] <apachelogger> yah, needs FFe
[08:17] <apachelogger> anyone in mood for a FFe?
[08:17] <agateau> MCR1: fixing it is going to require running Quantal Qt in gdb to figure out what the problem is
[08:17] <shadeslayer> I've annoyed the release team too much :P
[08:17] <agateau> MCR1: that is not going to happen today
[08:18] <apachelogger> Subject: Review Request: Add phonon-vlc option to disable PulseAudio support
[08:18] <apachelogger> why this should be fun
[08:18]  * agateau is still download quantal iso from his loosy connection
[08:18] <apachelogger> also wrong channel 
[08:18] <shadeslayer> :)
[08:18] <MCR1> agateau: Yes, unfortunately - maybe it is best I'll file a bug against the trimage package as well, but I am not sure if it is still actively developed...
[08:18] <apachelogger> shadeslayer: pim-runtime still failing
[08:19]  * shadeslayer opens furryfox
[08:19] <MCR1> agateau: Thx a lot for your fast help. Ping me if you need any testing or so...
[08:20] <shadeslayer> [ 95%] make[4]: *** No rule to make target `/usr/lib/libboost_thread-mt.so', needed by `resources/kolabproxy/akonadi_kolabproxy_resource'.  Stop.
[08:20] <shadeslayer> yay
[08:21] <shadeslayer> !find libboost_thread-mt.so
[08:21] <agateau> MCR1: ok
[08:21] <shadeslayer> most likely needs libboost-thread-dev
[08:22] <shadeslayer> lol
[08:22] <shadeslayer> apachelogger: stop eet :P
[08:22] <apachelogger> what's with ET?
[08:26] <apachelogger> shadeslayer: you may want to add libboost-dev
[08:27] <shadeslayer> mhmm
[08:28] <shadeslayer> apachelogger: libboost1.49-dev is already there
[08:29] <shadeslayer>   Suggests: libboost-thread1.49-dev
[08:32] <apachelogger> ah
[08:32] <apachelogger> silly
[08:35] <shadeslayer> apachelogger: fixed
[08:37] <shadeslayer> apachelogger: how about we start setting up 4.9.1 imports and give packaging with recipes a shot later on
[08:38] <shadeslayer> bzr with recipes will make so much sense >.>
[08:38] <shadeslayer> you could have a dedicated PPA for 4.9 where whenever someone fixes something in the 4.9 branch it gets packaged and uploaded to the QA ppa
[08:39] <shadeslayer> then after spending 10 days in QA, we can release to Archive
[08:39] <apachelogger> shadeslayer: ok, you've just gone mad
[08:39] <shadeslayer> why? :P
[08:39] <apachelogger> you are talking about relying lunchpad to do things
[08:39] <shadeslayer> actually, recipes are quite reliable
[08:40] <shadeslayer> we use them for neon don't we ? :D
[08:40] <apachelogger> yeah
[08:40] <shadeslayer> I wonder if there's a API to setup git imports
[08:40] <apachelogger> I did not notice you are packaging from tags
[08:40] <apachelogger> which BTW is not supported
[08:40] <shadeslayer> we .. are? 
[08:40] <apachelogger> so what you end up doing then is looking at git to identify which commit is tagged
[08:41] <apachelogger> and then pin point the bzr revision that is that commit and set that in your recipe
[08:41] <shadeslayer> afaik we just import git master and package it up
[08:41] <apachelogger> yeah
[08:41] <apachelogger> do we do that for stable?
[08:41] <shadeslayer> sure, instead of importing master, impor the 4.9 branch
[08:41] <apachelogger> do we do that for stable?
[08:41] <shadeslayer> lp supports importing git branches
[08:42] <shadeslayer> apachelogger: no, but we should
[08:42] <apachelogger> Oo
[08:42] <apachelogger> so instead of packaging a QA'd snapshot of git we package a not QA'd snapshot of git
[08:42] <apachelogger> why that sounds like an improvement
[08:43] <shadeslayer> use specific revisions then
[08:43] <apachelogger> yeah
[08:43] <apachelogger> read what I wrote about that
[08:43] <shadeslayer> apachelogger: it's just a bit of work, but then lp does most of the heavylifting
[08:44] <apachelogger> shadeslayer: a bit?
[08:44] <apachelogger> 200 times manual look up of a commit
[08:44] <apachelogger> *manual*
[08:44] <shadeslayer> heh
[08:48] <shadeslayer> ok, bad idea
[09:10] <shadeslayer> aaannnnddd kdepim-runtime fails again
[09:10] <apachelogger> lol
[09:10] <soee> :)
[09:11] <shadeslayer> make[4]: *** No rule to make target `/usr/lib/x86_64-linux-gnu/libcurl.so', needed by `resources/kolabproxy/akonadi_kolabproxy_resource'.  Stop.
[09:11] <shadeslayer> #$@#@%#$#@
[09:11] <apachelogger> seriously?
[09:12] <shadeslayer> yes
[09:12] <apachelogger> are you sure kolabproxy is not new?
[09:12] <shadeslayer> idk
[09:12] <apachelogger> that seems like a lot of missing lib foo for a patch release TBH
[09:12] <shadeslayer> !find kolabproxy
[09:12] <Riddell> it's in /usr/bin/akonadi_kolabproxy_resource
[09:12] <shadeslayer> apachelogger: the underlying stack changed alot I think
[09:12] <Riddell> kdepim-runtime: /usr/bin/akonadi_kolabproxy_resource
[09:12] <shadeslayer> so, if we rebuild kdepim-runtime from archives, I'm certain it'll fail
[09:35] <soee> Riddell, did you read my message ?
[09:36] <Riddell> soee: your upgrade worked?
[09:37] <Riddell> record it on http://iso.qa.ubuntu.com/qatracker/milestones/232/builds/22516/testcases !
[09:37] <soee> Riddell, upgrade yes without eny erros but i had no time to reboot and check how system works im gonna do it when i came home today
[09:38] <soee> Riddell, but it wasn't iso
[09:38] <soee> just simple distibution upgrade 
[09:40] <Riddell> yes that's an important test case, recorded on same tracker website
[09:40] <soee> also it was 64bit
[09:42] <soee> o some of this: http://iso.qa.ubuntu.com/qatracker/milestones/232/builds/22627/testcases ?
[09:43] <Riddell> no upgrade is separate, search for upgrade kubuntu on http://iso.qa.ubuntu.com/qatracker/milestones/232/builds
[09:44] <soee> ok, done
[09:47] <Riddell> thanks
[09:57] <soee> beta 1 uses lightdm right as kdm was removed completly during upgrade process ?
[09:59] <Riddell> yes
[10:07] <shadeslayer> mmm .. anyone have a idea how I can actually *lower* the resolution on KVM?
[10:08] <shadeslayer> or set a fixed resolution
[10:26] <Riddell> ug our old kubuntu friend stylman in trouble http://yro.slashdot.org/story/12/09/05/1238214/bitfloor-joins-list-of-compromised-bitcoin-exchanges 
[10:31] <shadeslayer> oh my
[10:34] <shadeslayer> I can only hope he didn't lose alot of money
[10:34] <shadeslayer> no idea how that bitcoin stuff works tbh
[10:34] <apachelogger> wikipedia has the good info
[10:35] <apachelogger> I cannot explain as I always end up spewing sarcasm all over the coins
[10:35] <Riddell> maybe I shouldn't have distracted him with Edinburgh Festival shows
[10:50]  * apachelogger goes all meh on release packaging
[10:50] <apachelogger> shadeslayer: runtime still ftbfsing?
[10:51] <shadeslayer> apachelogger: I didn't fix it yet
[10:51] <shadeslayer> was fixing some other stuff
[11:17] <shadeslayer> ok, I can look at it now
[11:22] <shadeslayer> apachelogger: hm, no dev package for curl
[11:22] <shadeslayer> well .. there's libcurl4-gnutls-dev
[11:22] <shadeslayer> and libcurl4-nss-dev
[11:23] <shadeslayer> hmmm ... nvm
[11:26]  * shadeslayer crosses fingers and hopes pim-runtime builds now
[11:39] <apachelogger> hm
[11:39] <apachelogger> ~quantalX~ppaX or ~quantal~ppaX or ~ppaX~quantalX?
[11:39]  * apachelogger thinks the last one is wrong
[11:40] <Riddell> ~quantalX~ppaX is typical
[11:40] <apachelogger> but why number the series?
[11:41] <Riddell> hmm, just to fit in nicely with backports ~quantalX
[11:41] <Riddell> but I guess it's not necessary
[11:41] <apachelogger> perhaps ScottK has a rationale for the X
[11:45] <Riddell> fit in nicely isn't a good rationale?
[11:45] <apachelogger> no, I meant why backports has it
[11:45] <apachelogger> ah
[11:45] <apachelogger> nvm
[11:45] <apachelogger> now I get it
[11:48] <apachelogger> http://paste.kde.org/544838/
[11:48] <apachelogger> bash supremacy I say
[11:50] <BluesKaj> Hey all
[11:54] <shadeslayer> yay
[11:55] <shadeslayer> apachelogger: fix kdepim runtime so version stuff
[11:57] <apachelogger> shadeslayer: hm?
[11:57] <apachelogger> simply bump everything to .1
[11:57] <shadeslayer> doing some other stuff 
[11:57] <shadeslayer> fix it fix it fix it
[11:57] <apachelogger> albert had this great idea of bumping that stuff globaly
[11:57] <apachelogger> nah
[11:58]  * apachelogger is fed up with .1
[11:58] <apachelogger> should have been done in 12 hours, yet it's 3 days now
[11:58] <Riddell> this is always the case with SC releases
[11:59] <Riddell> they always take longer than it seems they ought to
[11:59] <apachelogger> nah
[11:59] <apachelogger> the automation is not scaling
[11:59] <apachelogger> and bugged
[12:03] <apachelogger> hm
[12:03] <apachelogger> bulldog98: what is khighestversion doing?
[12:08] <apachelogger> oh, who would have known, I already hacked a script for ppa uploads
[12:08] <apachelogger> slightly dumb version tho
[12:52] <bambee> I never understood why IM clients has both notifications support: message indicator & KDE notifications, I mean it's a kind of double notification for a single message. It would be nice to be able to disable them. For example, only get notifications for the indicator message (at work it is more inconspicuous )
[12:52] <bambee> imho
[12:52] <bambee> hi btw
[12:53] <Riddell> yes that would be my preferred setting
[12:53] <Riddell> having support for both is fine but only 1 by default generally
[12:55] <bambee> I agree, at least for quassel and kde-telepathy it would be nice... I will take a look at it
[12:57] <Riddell> bambee: well telepathy doesn't have message-indicator alas
[13:00] <bulldog98_> apachelogger: get’s the latest version from the secret loctaion
[13:01] <bulldog98_> get’s the versionnumber
[13:32] <kubotu> ::qt-bugs:: [1046820] touch support seems broken since qt4-x11-4.8.1 @ https://bugs.launchpad.net/bugs/1046820 (by Canmor Lam)
[13:32] <kubotu> ::qt-bugs:: [1046825] package libqtcore4 4:4.8.1-0ubuntu4.2 failed to install/upgrade: lectura insuficiente en b... @ https://bugs.launchpad.net/bugs/1046825 (by starky_00)
[13:58] <ScottK> BTW, backports has switched to a version number model, e.g. ~12.04.1 instead of name based (~precise1) so that we survive alphabet rollover here in a few years.
[14:01] <Riddell> hmm that might be an idea
[14:02] <micahg> umm...it's ~ubuntu12.04.1 :)
[14:03] <apachelogger> I favor this move
[14:03] <apachelogger> however
[14:04] <apachelogger> the work... brrrr....
[14:04] <apachelogger> do we have a file on the system that actually maps a series name to a number?
[14:04] <micahg> apachelogger: distro-info maybe
[14:06] <apachelogger> /usr/share/distro-info/ubuntu.csv
[14:06] <apachelogger> oh la la
[14:06] <apachelogger> micahg: thx
[14:06] <mparillo> Is there a test case for installing Beta-1 to a VMWare Player?
[14:07] <apachelogger> considering it is a proprietary tool I do not think so
[14:08] <mparillo> apachelogger: Thx. Basically what I have at work...I could let it run while on my day job.
[14:11] <Riddell> mparillo: that's just the install test case
[14:11] <Riddell> so any of the test cases can be done in vmware
[14:24] <mparillo> So, is there a dummies guide on how to get started testing Beta-1?
[14:26] <shadeslayer> Riddell: question, does Kubuntu Beta 1 add org.kde.showActivityManager to the panel?
[14:37] <Riddell> shadeslayer: there's an activity manager plasmoid on the panel yes
[14:37] <shadeslayer> hm
[14:37] <shadeslayer> that's weird
[14:37] <shadeslayer> because we don't add that
[14:37] <shadeslayer> I don't see it anywhere in the 00-defaultLayout.js script
[14:37] <Riddell> let me double check
[14:37] <Riddell> yep it's there
[14:37] <shadeslayer> AND if I run panel = new Panel via desktop console in my quantal install it gives me a blank panel
[14:38] <shadeslayer> no activity manager stuff
[14:38] <shadeslayer> apachelogger: ^^ ideas?
[14:38] <BluesKaj> I have a desktop toolbox that includes activities , at the top right 
[14:39] <shadeslayer> nah, we're talking about the default panel on the live CD :)
[14:39]  * shadeslayer is a bit confused as to where that comes from tbh
[14:41] <BluesKaj> it's very similar to the panel toolbox but the icon is a grey bar with "Desktop " , written on it 
[14:42] <BluesKaj> wish i could get rid of it ...don't use activities\
[14:43] <apachelogger> shadeslayer: if you do new Panel you get a new Panel, duh
[14:46] <shadeslayer> apachelogger: a empty one
[14:46] <shadeslayer> right
[14:47] <shadeslayer> but where does the showActivityManager widget come from?
[14:48] <Riddell> shadeslayer: does it magically add itself when creating a new activity?
[14:48] <apachelogger> shadeslayer: we add it?
[14:48] <shadeslayer> apachelogger: no we don't :P
[14:49] <apachelogger> why do we not?
[14:49] <shadeslayer> idk
[14:49] <apachelogger> oh
[14:49] <apachelogger> actually I know where it comes from
[14:49] <shadeslayer> Riddell: possible, but the panel is created after the activity
[14:49] <apachelogger> le update scripts of the upstream
[14:49] <shadeslayer> :|
[14:49] <apachelogger> cuz the upstream apparently thinks forcing stuff down people's throat helps PR or something
[14:50] <Riddell> ah
[14:50] <shadeslayer> ah yes indeed : addShowActivitiesManagerPlasmoid.js
[14:50] <Riddell> ooh, ready!
[14:50]  * shadeslayer facepalms
[14:50] <shadeslayer> yay
[14:50] <soee> Riddell, im home. System works fine :)
[14:50] <Riddell> proofreaders, how's this? https://wiki.kubuntu.org/QuantalQuetzal/Beta1/Kubuntu
[14:50] <Riddell> soee: great
[14:54] <mparillo> Should it read  CD-sized  instead of  CD sizes?
[14:55] <mparillo> Is there an extra character at the end of: Regular users who want to help us test by finding, reporting, and/or fixing bugs involving installation, updgrades, and regular usage.`
[14:56] <shadeslayer> hah
[14:56] <shadeslayer> screenshot has fedora icon in kicker
[14:56] <shadeslayer> haha
[14:56] <shadeslayer> https://wiki.kubuntu.org/QuantalQuetzal/Beta1/Kubuntu?action=AttachFile&do=view&target=desktop.png
[14:57] <mparillo> You link to KDE 4.9, but say: The latest testing release of KDE's Plasma Workspaces and Applications ? Is it still a testing release?
[14:57] <tsimpson> duplicate "for" in the first line: "preparing for for the final"
[14:57] <tsimpson> love how no-one managed to see that :p
[14:58] <shadeslayer> :D
[14:58] <mparillo> Does Calligra eq  the 'KDE Office Suite'?
[14:59] <shadeslayer> Pointing users to a wiki page for feedback is a bit sad :(
[14:59] <apachelogger> social media I say
[14:59] <apachelogger> also 
[14:59] <shadeslayer> in order to edit said wiki page, you'd need to create a lp account
[14:59] <apachelogger> shadeslayer: do you have a problem with fedora *fistwave*
[14:59] <shadeslayer> apachelogger: aye :P
[15:00]  * apachelogger smacks shadeslayer and leaves for today
[15:00]  * shadeslayer shuts the door and tickles apachelogger
[15:00] <mparillo> Space before ,: 'happening ,'
[15:00] <tsimpson> shadeslayer: well, to report bugs you need an lp accout too. one would hope pre-release testers would be reporting bugs
[15:01] <shadeslayer> tsimpson: sure, but what if you find no bugs but have genera feedback
[15:01] <shadeslayer> *general
[15:02] <shadeslayer> Things like, how was your experience with KDE and Kubuntu
[15:02] <tsimpson> add an "or email us ...." to the feedback page
[15:02] <shadeslayer> what can be done differently
[15:02] <shadeslayer> like apachelogger said, needs social media :P
[15:02] <shadeslayer> twitter and identi.ca I say :)
[15:03] <shadeslayer> twitter/identi.ca/g+/facebook/email < in that order
[15:03] <tsimpson> or put a nice, fancy form on kubuntu.org
[15:03] <shadeslayer> well
[15:03] <Riddell> mparillo: yes but it's unclear if "office" is a good term for all its applications
[15:03] <shadeslayer> forms are nice as long as it's radio buttons and does not exceed more than 5 questions :D
[15:04] <shadeslayer> s/it's/it has
[15:04] <Riddell> mparillo: fancy just making these changes yourself?
[15:04] <tsimpson> I'd think it'd be more of a name: contact email: feedback:
[15:04] <shadeslayer> hm, that could work
[15:05] <shadeslayer> can you do that with drupal?
[15:06] <Riddell> shadeslayer: the feedback wiki pages aren't very popular any more, I guess wikis are out of fashion
[15:06] <shadeslayer> I'm still all for social media :P
[15:07] <Riddell> shadeslayer: the trouble is our social media presence isn't great
[15:07] <tsimpson> I have 0 experience with drupal, but I'd certainly hope it can do simple HTML forms
[15:07] <shadeslayer> mhmm
[15:07] <shadeslayer> iirc we had a twitter account
[15:07] <shadeslayer> we have a somewhat active G+ account
[15:07] <Riddell> kubuntu_news that is magically linked to our website in ways nobody knows
[15:07] <shadeslayer> have not opened identi.ca in eons
[15:07] <shadeslayer> :D
[15:08] <Riddell> I'm yet to work out how g+ works, can people leave feedback on it?
[15:08] <Riddell> identi.ca is just spam collection now I think
[15:08] <shadeslayer> They just need to mention +Kubuntu I believe
[15:12] <tsimpson> as you mention all the social media stuff, I just had a look around kubuntu.org and I can't find a link to any of them. maybe a good idea to add some links. maybe in the form of icons, eg in the footer
[15:13] <shadeslayer> indeed
[15:13] <shadeslayer> believe it or not, no one is going to mail Kubuntu Devel with feedback
[15:13] <shadeslayer> maybe right after "Technologies Used"
[15:13] <shadeslayer> we can add "Talk to us"
[15:13] <shadeslayer> or sth
[15:17] <mparillo> If you list the social media links as a wishlist in Launchpad under kubuntu-website, I can try to do something with them.
[15:18] <Riddell> tsimpson: same issue, we don't have official social media accounts
[15:18] <mparillo> Riddell: I think I got all the proof-reading suggestions (except for the Fedora kickoff application launcher one).
[15:18] <Riddell> mparillo: great, thanks
[15:18] <shadeslayer> ok, who uploaded that screenshot ? :P
[15:30] <Riddell> shadeslayer: which?
[15:30] <shadeslayer> the one with the fedora icon in the kickoff
[15:30] <Riddell> where's that?
[15:31] <Riddell> aah
[15:31] <Riddell> claydoh would have taken that from kde.org I guess
[15:43] <Riddell> shadeslayer: do you care about the amd64+mac image enough to test it?
[15:43] <shadeslayer> irrelevant, my mac can boot all of those images since my hardware is vastly different
[15:44] <shadeslayer> those mac+amd64 images are for specific machines, don't know which ones
[15:58] <mparillo_> Fedora screenshot replaced.
[16:06] <Riddell> mparillo_: yo da man
[16:06] <shadeslayer> haha
[16:07] <shadeslayer> indeed

[16:08] <Riddell> now work out what sensible thing can be done to encourage feedback on g+ and anything else and we'll be there
[16:10] <Riddell> mparillo_: fancy drafting up a post for kubuntu.org ?
[16:10] <mparillo_> A release announcement?
[16:11] <mparillo_> And for feedback, I think I can put the place(s) for feedback on the Community page. I just need to know the consensus of the best sites / vehicles for that.
[16:11] <Riddell> well https://wiki.kubuntu.org/QuantalQuetzal/Beta1/Kubuntu is the release announcement
[16:11] <Riddell> so just a short post pointing at that, the download location, upgrade instructions and maybe a few bullet points of features
[16:12] <Riddell> oh and the technical overview https://wiki.ubuntu.com/QuantalQuetzal/TechnicalOverview/Beta1
[16:12] <mparillo_> The technical overview is ubuntu-wide?
[16:12] <Riddell> yes
[16:13] <Riddell> I think the best sites will be those with account we control, which is only g+
[16:14] <mparillo_> Which is your g+ account? I know there is a fan account that was in the news a while back?
[16:15] <Riddell> that's the one, https://plus.google.com/107577785796696065138/posts
[16:20] <mparillo_> KDE Paste ~/paste/544940
[16:20] <cyphermox> ScottK: thanks for reminding me about plasma-networkmanagement
[16:20] <cyphermox> Sorry I keep forgetting about this bit
[16:20] <ScottK> You're welcome.
[16:20] <ScottK> No problem.
[16:21] <cyphermox> I'm going to look at the code now and propose a patch/merge if there is something wrong
[16:22] <cyphermox> ScottK: networkmanagement is still the right source, right?
[16:22] <Riddell> mparillo_: lovely
[16:23] <Riddell> mparillo_: stick that up now with the published box unticked so it's easy to do when the announce goes out
[16:24] <ScottK> cyphermox: Yes.
[16:27] <cyphermox> looks unaffected to me
[16:27] <cyphermox> well, actually just that people have the choice to create networks the way they want them, which doesn't block the evil wpa-none from being used
[16:36] <Riddell> mparillo_, anyone, I'm off out for a few hours, if the release happens before I return do post http://paste.kde.org/544940/ on the website
[16:39] <mparillo_> News Quantal Beta 1 Out has been created. That is Saved, but with the Published button not checked.
[16:45] <mparillo_> Riddell: The news article is posted; it is not published.
[17:38] <apachelogger> shadeslayer: ping
[17:43] <apachelogger> shadeslayer: all your runtime changery is not bzr
[17:59] <jussi> apachelogger: shadeslayer sleeps now... ;)
[18:00] <apachelogger> as if he deserves sleep for repeatedly not pushing changes to bzr :(
[18:00] <mikhas> harsh
[18:01] <mikhas> I can understand people that try to keep their sanity by avoiding bizarre whenever possible. =p
[18:02] <apachelogger> me too, doesn't help the fact that we use it right now and people not running one command when they do an upload causes more work for me
[18:02] <apachelogger> on a positive note .1 ought to be done for quantal
[18:03] <apachelogger> any quantal ninjas around?
[18:05] <apachelogger> JontheEchidna: ping
[18:05] <JontheEchidna> apachelogger: pong
[18:06] <apachelogger> JontheEchidna: do you still have 2 ssh keys?
[18:06] <apachelogger> one dss and one rsa
[18:08] <JontheEchidna> hmm
[18:08] <apachelogger> shadeslayer bulldog98_ yofel_ ^ same question
[18:08] <JontheEchidna> there's an id_dsa and a id_rsa in my ~/.ssh
[18:09] <yofel_> apachelogger: about being on quantal? yes, I'll update in a bit
[18:09] <apachelogger> JontheEchidna: http://paste.kde.org/544988/
[18:09] <apachelogger> chek the sigs please
[18:09] <apachelogger> yofel_: no, about the keys
[18:09] <apachelogger> :O
[18:10] <apachelogger> bambee: 4 ssh keys?
[18:10] <yofel_> uh, I have a few
[18:10] <apachelogger> srsly :O
[18:10]  * yofel_ checks
[18:10] <yofel_> I don't share keys between PC's
[18:10] <apachelogger> ah, I guess 2 makes sense then
[18:10] <JontheEchidna> apachelogger: yup, those are it
[18:10] <apachelogger> perhaps you wanna pick one? :P
[18:11] <apachelogger> just a though :P
[18:11] <JontheEchidna> ?
[18:11] <yofel_> yeah, those are the 2 that should be there
[18:11] <apachelogger> JontheEchidna: why two keys if they are on the same machine? :P
[18:12]  * yofel_ has some DSA keys lying around as well, but those are only 1K and obsolete
[18:12] <apachelogger> new key file online, if you guys could review your keys that would be good
[18:13] <yofel_> file is missing from what I see
[18:13] <yofel_> only the backup one is there
[18:13] <apachelogger> ah, I broke it
[18:13] <apachelogger> stupid command sequences all wrong
[18:17] <yofel_> only the backup one is there
[18:17] <yofel_> oops
[18:18] <apachelogger> asked sho to fix it again ^^
[18:18] <yofel_> I moved the old file back
[18:18] <yofel_> still had the shell open
[18:19] <apachelogger> ah, we can shell now?
[18:19] <apachelogger> ah, sftp shell you mean?
[18:19] <yofel_> uh, shell always worked for me
[18:19] <yofel_> even back on ktown before it was taken down
[18:19] <apachelogger> I thought it was deactivated at some point
[18:19] <apachelogger> good to know though
[18:20] <apachelogger> now the cleaned file should be online
[18:20] <apachelogger> also sent a mail to those who's keys I removed
[18:34] <yofel> apachelogger: upgrade went fine and 4.9 seems to work ok
[18:34] <yofel> do we have a TODO item somewhere about updating the lightdm background?
[18:34] <yofel> uses old Ariya
[18:39] <shadeslayer> apachelogger: kdepim-runtime hackery was not pused to bzr because I assumed you were still working on it
[18:40] <shadeslayer> and I'm *very* tired
[18:40] <apachelogger> there's a new ariya?
[18:40] <shadeslayer> and yes, I can still get into ftpmaster from my work machine
[18:40] <apachelogger> yofel: 
[18:40] <shadeslayer> there is?
[18:41] <yofel> apachelogger: well, ksplash uses a new theme now, not the desktop background anymore. Lightdm uses the desktop background
[18:43] <apachelogger> yofel: the one without stripes?
[18:48] <yofel> right
[19:02] <ScottK> Riddell: You back?  It's close and mparillo_ has vanished.
[19:25] <ScottK> Nice.  Kubuntu.org is down.
[19:27] <JontheEchidna> people must be anticipating the release :P
[19:28] <JontheEchidna> seems back up at any rate
[19:30] <ScottK> Yep.
[19:31] <ScottK> I'm all set to hit publish when the release is official.  The images are there now.
[19:48] <kubotu> ::qt-bugs:: [1046820] touch support seems broken since qt4-x11-4.8.1 @ https://bugs.launchpad.net/bugs/1046820 (by Canmor Lam)
[20:08] <ScottK> apachelogger: Is upstream_Ensure-that-the-start-Client-to-build-up-the-ClientM.patch the patch for the regression that mgraesslin was whining about?
[20:36] <apachelogger> ScottK: aye
[20:36] <ScottK> Excellent.  Thanks.
[20:37] <apachelogger> oh
[20:37] <apachelogger> ftbfs
[20:37] <apachelogger> wohoo
[20:37] <apachelogger> hrm
[20:38] <apachelogger> did upstream always do all around soname changes for minor updates?
[20:38] <apachelogger> that is somewhat of a pita
[21:00] <yofel> apachelogger: the version usually changes with the kdelibs version, that why I usually use libfooABIVER* in install files
[21:00] <yofel> when doing new stuff
[21:02] <apachelogger> aho
[21:02] <apachelogger> yofel: yeah, I changed them to wildcard mostly now
[21:02] <apachelogger> though i think this ought to be discussed with le debian
[21:02] <apachelogger> because quite frankly changing it to wildcard after every merge is a bit silly
[21:03] <yofel> true
[21:14] <ScottK> Wildcard is also risky you miss the need for a rename.
[21:19] <apachelogger> ScottK: not so much if you do X.Y.*
[21:20] <ScottK> True.
[21:44] <ScottK> Did you get icecc figured out?
[21:47] <ScottK> Who's around that can update kubuntu.org when beta1 comes out?  IIRC Riddell  is snoozing or something and I have to leave soon.
[21:47] <ScottK> The announce is already written, it just needs someone to tick publish and save it.
[21:48] <Riddell> hi
[21:48] <Riddell> I'm back
[21:49] <Riddell> ScottK: got the URL that needs the tick?
[21:49] <apachelogger> ScottK: not quite, though I got sidetracked with .1
[21:49] <ScottK> Glad you're back.
[21:49] <ScottK> apachelogger: OK.  I'll try to remember to harass you periodically.
[21:50] <apachelogger> all I know for sure is that it does not seem to work but the scheduler is detected et al, it simply doesn't distribute the build
[21:50] <apachelogger> which can of course have a number of reasons
[21:50] <apachelogger> and is tedious to debug really
[21:54] <ScottK> I'm out for now.  See you all later.
[21:54] <Riddell> ciao
[21:56]  * yofel is off to bed - good night
[22:05] <Riddell> beta 1 is out!
[22:05] <Riddell> http://www.kubuntu.org/news/12.10-beta-1
[22:15] <highvoltage> yay
[22:33] <JontheEchidna> rewrite src/worker/org.kubuntu.qaptworker.xml (79%)
[22:33] <JontheEchidna> git you so smart
[22:36] <JontheEchidna> I tried to call a d-bus method and got kicked off the bug: http://paste.kde.org/545090/ :(
[22:37] <JontheEchidna> *off the bus