[04:40] I'm surprised, the university has us using a linux lab, (gnome3, yech) and we can remotely submit assignments via scp/ssh. [04:40] (and that linux lab is what we're using for this class) [05:04] morning [06:18] Riddell, i did upgrade during the night 12.04 -> 12.10 [06:18] but had no time to reboot machine and check if everyting is ok [06:19] but upgrade finished without any errors [06:33] kubotu: order coffee [06:33] * kubotu slides coffee with milk down the bar to apachelogger. [06:33] kubotu: order a lot more coffee [06:33] * kubotu slides a lot more coffee down the bar to apachelogger [06:38] good news everyone! [06:38] libs is building, pim-runtime continues to fail, still 3 packages missing [06:39] oh, actually it's more than 3 [06:39] Oo [06:54] * shadeslayer looks [06:54] yay, stupid chrome still hit by that stupid bug [06:55] apachelogger: have you seen martin's email to kde-packagers about some critical bug [06:56] pim-runtime ftbfs is weird [06:57] !find libxerces [06:57] Found: libxerces2-java, libxerces2-java-doc, libxerces2-java-gcj, libxerces-c-dev, libxerces-c-doc [06:57] * shadeslayer fixes [07:00] bleh [07:02] shadeslayer: no [07:02] todo: [07:02] - workspace [07:02] * kwin patch [07:02] whut [07:02] ok [07:02] awesum [07:02] my notes file apparently has [07:02] don't ask me how [07:03] text files are getting all intelligent Oo [07:04] apachelogger: this is the first I'm facing this .. but should kdepim-runtime dep on libxerces-c-dev or libxerces-c3.1 [07:04] because libxerces-c3.1 was pulled in automatically earlier [07:04] but libxerces-c-dev was never pulled in [07:04] 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] mmm ... need to sync github ff-kde with precise packaging [07:08] shadeslayer: where is the error anyway? [07:08] apachelogger: can't find libs to link against I believe ( needs libxerces-c3.1 ) [07:09] ah [07:09] 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] *nod* [07:09] why it appears the lib had a packaging error if the -dev was not pulled in [07:09] that was pulled in automagically earlier [07:09] OR that dep is new [07:09] the former [07:09] bogus packaging then [07:09] mhmm [07:09] OR that .so is in fact not public [07:10] (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] ETOOTIREDTOPARSEERROR [07:13] shadeslayer: please push your missing change to kdentwork [07:14] only things missing should be network and mplayerthumbs now [07:14] and former needs packaging to begin with [07:14] kk [07:15] actually latter [07:15] * apachelogger needs moar coffeee [07:16] I just had coffee and I'm barely awake :| [07:17] [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] apachelogger: ^ kfixed [07:17] you probably want to drop that patch [07:18] I pushed it into SVN as well, so was most likely included in 4.9.1 [07:19] * shadeslayer tickles apachelogger [07:21] I do like dropping patches [07:24] shadeslayer: not the case [07:24] oh [07:24] does SVN have branches? [07:24] because I just pushed to master [07:24] SVN has definitely no master :P [07:24] also what's with the patch naming there? [07:25] hehe [07:25] simple_and_generic_names.ftw [07:26] shadeslayer: u fixing pim-runtime? [07:27] apachelogger: I'm not sure what would be the /right/ way to do things there [07:27] add the build dep? :P [07:27] sure, but on the library or the header files :P [07:27] the one that contains the .so?! [07:28] !find /usr/lib/i386-linux-gnu/libxerces-c.so [07:28] Package/file /usr/lib/i386-linux-gnu/libxerces-c.so does not exist in quantal [07:28] wat [07:28] !find libxerces-c.so quantal [07:28] Package/file libxerces-c.so does not exist in quantal [07:28] tehehehe [07:28] funny [07:29] !info libxerces-c-dev [07:29] libxerces-c-dev (source: xerces-c): validating XML parser library for C++ (development files). In component universe, is optional. Version 3.1.1-3 (quantal), package size 2849 kB, installed size 15281 kB [07:29] !info libxerces-c-dev quantal [07:29] ... [07:29] I broke it [07:29] :D [07:30] apachelogger: have you mooed today [07:31] !find libxerces-c-3.1.so [07:31] Package/file libxerces-c-3.1.so does not exist in quantal [07:31] @_@ [07:31] libxerces-c-dev [07:31] ya [07:37] 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] Who can fix this ? [07:37] I was told by didrocks that I might find the experts here :) [07:38] MCR1: sounds like a bug in the qgtk widget style [07:39] MCR1: do you get the same crash when running the app with "-style plastique" options [07:39] ? [07:39] apachelogger: fix uploaded [07:40] agateau: one moment, checking :) [07:40] thx [07:42] 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] agateau: QNativeImage: Unable to attach to shared memory segment. [07:43] X Error: BadDrawable (invalid Pixmap or Window parameter) 9 [07:43] Major opcode: 62 (X_CopyArea) [07:43] wow [07:44] O_O [07:45] trimage essentially opens in a 5000x5000 pixel window with completely black content [07:45] agateau: if you're bored, assistant is crashing too (different issue altogether) [07:45] tsdgeos: I am not bored :) [07:46] daminit! [07:46] MCR1: if "-style plastique" does not work, you can try running qtconfig and change the style from there [07:46] MCR1: the gtk widget assert reminds me of a problem when overlay scrollbars where used with qgtk style [07:47] MCR1: iirc there is an environment variable to disable overlay scrollbars which you could try to set before running qbzr or trimage [07:48] (overlay scrollbars ought to be deactivated in Qt directly) [07:48] in quantal anyway [07:48] agateau: Okay, with style plastique qbzr now seems to work [07:48] MCR1: (or you can just uninstall overlay scrollbars temporarily) [07:48] agateau: It was using GTK+ before [07:48] 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] agateau: but trimage still fails to open... [07:49] http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qt/view/head:/debian/patches/kubuntu_93_disable_overlay_scrollbars.diff [07:50] trimage error: "sni-qt/3721" WARN 09:49:15.767 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE [07:50] then: QNativeImage: Unable to attach to shared memory segment. [07:50] apachelogger: looks good, can you check for the gtk patch? [07:50] I could [07:50] that requires more time then [07:50] and I am already distracted enough [07:50] shadeslayer: please go look for patch in gtk [07:51] :) [07:51] I'm looking at preinst stuff [07:51] and not caffeinated enough [07:51] 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] 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] agateau: Yes, I do not exactly know if it is 5000x5000, but it is scary big ;) [07:53] 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] MCR1: can you try to 1) set the Qt style back to GTK 2) run qbzr with "LIBOVERLAY_SCROLLBAR=0 qbzr"? [08:00] apachelogger: gtk patch is still there [08:03] 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] MCR1: you can run qbzr directly iirc [08:04] ? [08:05] oh, no you can't [08:05] qbzr is a set of plugins to bzr [08:05] so simply set the var for bzr [08:05] 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] apachelogger: you not loving the bazaar ? [08:06] agateau: WORX :) [08:06] no! [08:06] bazaar sounds to me like somethign a japanese soldier would shout when charging... :P [08:07] that would be tora tora tora :) [08:07] indeed [08:07] shadeslayer: please be reviewing lp:~kubuntu-packagers/kubuntu-packaging/mplayerthumbs [08:08] oh noes [08:08] looking [08:08] the netwox is failing [08:09] apachelogger: are you sure you want to have a install file? [08:09] it's just one package :P [08:10] 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] *of trimage [08:11] MCR1: can you try the LIBOVERLAY_SCROLLBAR trick with trimage as well? [08:12] shadeslayer: are you sure you want to insinuate that I have a useless install file? [08:12] yes ofc. - but I guess there it was another problem, because I already changed the style to plastique, but I'll try... [08:12] it's two packages :P [08:12] nope [08:12] well [08:12] shadeslayer: before trying to smartass me, check your facts you lazy bum :P [08:13] apachelogger: again, I don't think the install file is required :P [08:13] it is [08:13] why [08:13] dh does not care that a package has a -dbg suffix [08:13] to it there are two packages [08:13] agateau: The trick does not do the trick for trimage unfortunately... [08:13] meaning debian/tmp does not get automatically thrown into package A) [08:14] and why are you not using dh --with-kde ? [08:14] dunno, stole that from dragon [08:14] ... [08:14] I recon the include takes care of that [08:14] on that not [08:14] e [08:15] seems that it does [08:15] yes [08:15] the build system we use is utterly untransparent and whatnot [08:15] also ever changing [08:15] I find this bad and a solution must therefore be found [08:16] MCR1: ok, so trimage problem is a different bug [08:16] apachelogger: ok, ship it [08:16] needs FFe [08:17] unless the binary from 4.8 is still in [08:17] which would be spooky [08:17] heh [08:17] yah, needs FFe [08:17] anyone in mood for a FFe? [08:17] MCR1: fixing it is going to require running Quantal Qt in gdb to figure out what the problem is [08:17] I've annoyed the release team too much :P [08:17] MCR1: that is not going to happen today [08:18] Subject: Review Request: Add phonon-vlc option to disable PulseAudio support [08:18] why this should be fun [08:18] * agateau is still download quantal iso from his loosy connection [08:18] also wrong channel [08:18] :) [08:18] 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] shadeslayer: pim-runtime still failing [08:19] * shadeslayer opens furryfox [08:19] agateau: Thx a lot for your fast help. Ping me if you need any testing or so... [08:20] [ 95%] make[4]: *** No rule to make target `/usr/lib/libboost_thread-mt.so', needed by `resources/kolabproxy/akonadi_kolabproxy_resource'. Stop. [08:20] yay [08:21] !find libboost_thread-mt.so [08:21] Package/file libboost_thread-mt.so does not exist in quantal [08:21] MCR1: ok [08:21] most likely needs libboost-thread-dev [08:22] lol [08:22] apachelogger: stop eet :P [08:22] what's with ET? [08:26] shadeslayer: you may want to add libboost-dev [08:27] mhmm [08:28] apachelogger: libboost1.49-dev is already there [08:29] Suggests: libboost-thread1.49-dev [08:32] ah [08:32] silly [08:35] apachelogger: fixed [08:37] apachelogger: how about we start setting up 4.9.1 imports and give packaging with recipes a shot later on [08:38] bzr with recipes will make so much sense >.> [08:38] 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] then after spending 10 days in QA, we can release to Archive [08:39] shadeslayer: ok, you've just gone mad [08:39] why? :P [08:39] you are talking about relying lunchpad to do things [08:39] actually, recipes are quite reliable [08:40] we use them for neon don't we ? :D [08:40] yeah [08:40] I wonder if there's a API to setup git imports [08:40] I did not notice you are packaging from tags [08:40] which BTW is not supported [08:40] we .. are? [08:40] so what you end up doing then is looking at git to identify which commit is tagged [08:41] and then pin point the bzr revision that is that commit and set that in your recipe [08:41] afaik we just import git master and package it up [08:41] yeah [08:41] do we do that for stable? [08:41] sure, instead of importing master, impor the 4.9 branch [08:41] do we do that for stable? [08:41] lp supports importing git branches [08:42] apachelogger: no, but we should [08:42] Oo [08:42] so instead of packaging a QA'd snapshot of git we package a not QA'd snapshot of git [08:42] why that sounds like an improvement [08:43] use specific revisions then [08:43] yeah [08:43] read what I wrote about that [08:43] apachelogger: it's just a bit of work, but then lp does most of the heavylifting [08:44] shadeslayer: a bit? [08:44] 200 times manual look up of a commit [08:44] *manual* [08:44] heh [08:48] ok, bad idea [09:10] aaannnnddd kdepim-runtime fails again [09:10] lol [09:10] :) [09:11] 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] #$@#@%#$#@ [09:11] seriously? [09:12] yes [09:12] are you sure kolabproxy is not new? [09:12] idk [09:12] that seems like a lot of missing lib foo for a patch release TBH [09:12] !find kolabproxy [09:12] Package/file kolabproxy does not exist in quantal [09:12] it's in /usr/bin/akonadi_kolabproxy_resource [09:12] apachelogger: the underlying stack changed alot I think [09:12] kdepim-runtime: /usr/bin/akonadi_kolabproxy_resource [09:12] so, if we rebuild kdepim-runtime from archives, I'm certain it'll fail [09:35] Riddell, did you read my message ? [09:36] soee: your upgrade worked? [09:37] record it on http://iso.qa.ubuntu.com/qatracker/milestones/232/builds/22516/testcases ! [09:37] 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] Riddell, but it wasn't iso [09:38] just simple distibution upgrade [09:40] yes that's an important test case, recorded on same tracker website [09:40] also it was 64bit [09:42] o some of this: http://iso.qa.ubuntu.com/qatracker/milestones/232/builds/22627/testcases ? [09:43] no upgrade is separate, search for upgrade kubuntu on http://iso.qa.ubuntu.com/qatracker/milestones/232/builds [09:44] ok, done [09:47] thanks [09:57] beta 1 uses lightdm right as kdm was removed completly during upgrade process ? [09:59] yes [10:07] mmm .. anyone have a idea how I can actually *lower* the resolution on KVM? [10:08] or set a fixed resolution [10:26] 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] oh my [10:34] I can only hope he didn't lose alot of money [10:34] no idea how that bitcoin stuff works tbh [10:34] wikipedia has the good info [10:35] I cannot explain as I always end up spewing sarcasm all over the coins [10:35] maybe I shouldn't have distracted him with Edinburgh Festival shows [10:50] * apachelogger goes all meh on release packaging [10:50] shadeslayer: runtime still ftbfsing? [10:51] apachelogger: I didn't fix it yet [10:51] was fixing some other stuff [11:17] ok, I can look at it now [11:22] apachelogger: hm, no dev package for curl [11:22] well .. there's libcurl4-gnutls-dev [11:22] and libcurl4-nss-dev [11:23] hmmm ... nvm [11:26] * shadeslayer crosses fingers and hopes pim-runtime builds now [11:39] hm [11:39] ~quantalX~ppaX or ~quantal~ppaX or ~ppaX~quantalX? [11:39] * apachelogger thinks the last one is wrong [11:40] ~quantalX~ppaX is typical [11:40] but why number the series? [11:41] hmm, just to fit in nicely with backports ~quantalX [11:41] but I guess it's not necessary [11:41] perhaps ScottK has a rationale for the X [11:45] fit in nicely isn't a good rationale? [11:45] no, I meant why backports has it [11:45] ah [11:45] nvm [11:45] now I get it [11:48] http://paste.kde.org/544838/ [11:48] bash supremacy I say [11:50] Hey all [11:54] yay [11:55] apachelogger: fix kdepim runtime so version stuff [11:57] shadeslayer: hm? [11:57] simply bump everything to .1 [11:57] doing some other stuff [11:57] fix it fix it fix it [11:57] albert had this great idea of bumping that stuff globaly [11:57] nah [11:58] * apachelogger is fed up with .1 [11:58] should have been done in 12 hours, yet it's 3 days now [11:58] this is always the case with SC releases [11:59] they always take longer than it seems they ought to [11:59] nah [11:59] the automation is not scaling [11:59] and bugged [12:03] hm [12:03] bulldog98: what is khighestversion doing? [12:08] oh, who would have known, I already hacked a script for ppa uploads [12:08] slightly dumb version tho [12:52] 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] imho [12:52] hi btw [12:53] yes that would be my preferred setting [12:53] having support for both is fine but only 1 by default generally [12:55] I agree, at least for quassel and kde-telepathy it would be nice... I will take a look at it [12:57] bambee: well telepathy doesn't have message-indicator alas [13:00] apachelogger: get’s the latest version from the secret loctaion [13:01] get’s the versionnumber === rdieter_laptop is now known as rdieter [13:32] ::qt-bugs:: [1046820] touch support seems broken since qt4-x11-4.8.1 @ https://bugs.launchpad.net/bugs/1046820 (by Canmor Lam) [13:32] ::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] 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] hmm that might be an idea [14:02] umm...it's ~ubuntu12.04.1 :) [14:03] I favor this move [14:03] however [14:04] the work... brrrr.... [14:04] do we have a file on the system that actually maps a series name to a number? [14:04] apachelogger: distro-info maybe [14:06] /usr/share/distro-info/ubuntu.csv [14:06] oh la la [14:06] micahg: thx [14:06] Is there a test case for installing Beta-1 to a VMWare Player? [14:07] considering it is a proprietary tool I do not think so [14:08] apachelogger: Thx. Basically what I have at work...I could let it run while on my day job. [14:11] mparillo: that's just the install test case [14:11] so any of the test cases can be done in vmware [14:24] So, is there a dummies guide on how to get started testing Beta-1? [14:26] Riddell: question, does Kubuntu Beta 1 add org.kde.showActivityManager to the panel? [14:37] shadeslayer: there's an activity manager plasmoid on the panel yes [14:37] hm [14:37] that's weird [14:37] because we don't add that [14:37] I don't see it anywhere in the 00-defaultLayout.js script [14:37] let me double check [14:37] yep it's there [14:37] AND if I run panel = new Panel via desktop console in my quantal install it gives me a blank panel [14:38] no activity manager stuff [14:38] apachelogger: ^^ ideas? [14:38] I have a desktop toolbox that includes activities , at the top right [14:39] 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] it's very similar to the panel toolbox but the icon is a grey bar with "Desktop " , written on it [14:42] wish i could get rid of it ...don't use activities\ [14:43] shadeslayer: if you do new Panel you get a new Panel, duh [14:46] apachelogger: a empty one [14:46] right [14:47] but where does the showActivityManager widget come from? [14:48] shadeslayer: does it magically add itself when creating a new activity? [14:48] shadeslayer: we add it? [14:48] apachelogger: no we don't :P [14:49] why do we not? [14:49] idk [14:49] oh [14:49] actually I know where it comes from [14:49] Riddell: possible, but the panel is created after the activity [14:49] le update scripts of the upstream [14:49] :| [14:49] cuz the upstream apparently thinks forcing stuff down people's throat helps PR or something [14:50] ah [14:50] ah yes indeed : addShowActivitiesManagerPlasmoid.js [14:50] ooh, ready! [14:50] * shadeslayer facepalms [14:50] yay [14:50] Riddell, im home. System works fine :) [14:50] proofreaders, how's this? https://wiki.kubuntu.org/QuantalQuetzal/Beta1/Kubuntu [14:50] soee: great [14:54] Should it read CD-sized instead of CD sizes? [14:55] 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] hah [14:56] screenshot has fedora icon in kicker [14:56]